eNodeB Feature-Description PACKAGE 4.0 PDF

Samsung eNB (LTE)
Feature Description
for PKG 5.0.0
Provides the Feature ID, dependency & limitation, and detailed description from the
point of view of high level design.
Radio Access Network
Document Version 2.0

December 2015
Document Number: 2600-00I10TGAP

2015 SAMSUNG Electronics Co., Ltd.
All Rights Reserved. No part of this document may be photocopied, reproduced, stored in a retrieval
system, or transmitted, in any form or by any means whether, electronic, mechanical, or otherwise
without the prior written permission of SAMSUNG Electronics Co., Ltd.
No warranty of accuracy is given concerning the contents of the information contained in this
publication. To the extent permitted by law no liability (including liability to any person by reason of
negligence) will be accepted by SAMSUNG Electronics Co., Ltd., its subsidiaries or employees for
any direct or indirect loss or damage caused by omissions from or inaccuracies in this document.
SAMSUNG Electronics Co., Ltd. reserves the right to change details in this publication without notice.
SNMTC-v3-0312
This manual should be read and used as a guideline for properly installing and/or operating the
product. Owing to product variations across the range, any illustrations and photographs used in
this manual may not be a wholly accurate depiction of the actual products you are using.
This manual may be changed for system improvement, standardization and other technical
reasons without prior notice.
Samsung Networks documentation is available at http://www.samsungdocs.com
Contents
Preface vi
Relevance ........................................................................................................................................ vi
Conventions in this Document ........................................................................................................ vi
New and Changed Information ...................................................................................................... vii
Revision History ............................................................................................................................... ix
Organization of This Document ....................................................................................................... x
Related Documentation ................................................................................................................... x
Chapter 1 Air Performance Enhancement 1
LTE-ME2019, DL SU 2x2 MIMO (TM3 and TM4) .............................................................................. 1
LTE-ME2020, Rx Diversity ................................................................................................................. 6
LTE-ME2022, DL SU 4x4 MIMO (TM3 and TM4) .............................................................................. 9
LTE-ME2023, DL SU 4x2 MIMO (TM3 and TM4) ............................................................................ 15
LTE-ME5110, FDD Carrier Aggregation (5+5) ................................................................................. 20
LTE-ME6004, DL Smart ................................................................................................................... 26
LTE-ME6005, UL Smart (Interference Coordination for UL) ........................................................... 32
Chapter 2 Call Control 38
LTE-SW0111, UE Counting per Category ........................................................................................ 38
LTE-SW0114, Enhancements for Diverse Data Applications .......................................................... 41
LTE-SW0315, Extended Access Barring (SIB14) .............................................................................. 45
LTE-SW0321, UE Context Management ......................................................................................... 49
LTE-SW0322, E-RAB Management ................................................................................................. 56
LTE-SW0501, S1 Interface Management ........................................................................................ 63
LTE-SW0510, Geo Redundancy of MME ........................................................................................ 75
LTE-SW0521, X2 Interface Management ....................................................................................... 84
LTE-SW3010, PDCP Sublayer Support ............................................................................................ 92
LTE-SW4101, Capacity based Call Admission Control .................................................................... 94
LTE-SW4103, Preemption ............................................................................................................ 104
LTE-SW5500, CA Call Control ....................................................................................................... 112
Chapter 3 Load Control 125
LTE-SW2004, Blind Offloading to WCDMA .................................................................................. 125
LTE-SW2020, Load Distribution over Backhaul Links ................................................................... 128
LTE-SW2103, UL Congestion Prevention ...................................................................................... 131
LTE-SW2104, eNB Overload Protection ....................................................................................... 136
LTE-SW2108, Smart Congestion Mitigation ................................................................................. 139
Chapter 4 Mobility Control 142
LTE-SW1002, Idle Mobility Support ............................................................................................. 142
LTE-SW1004, S1 Handover ........................................................................................................... 158
LTE-SW1005, X2 Handover ........................................................................................................... 167
LTE-SW1202, PS Handover between LTE and UTRAN .................................................................. 177
LTE-SW1204, Redirection to UTRAN without SI ........................................................................... 189
LTE-SW1205, Redirection to UTRAN with SI ................................................................................ 195
LTE-SW1208, CSFB to UTRAN with Redirection with SI ............................................................... 202
LTE-SW1209, CSFB to UTRAN with PS Handover ......................................................................... 210
Contents
LTE-SW1301, Idle Mobility to GERAN .......................................................................................... 217

LTE-SW1302, PS Handover between LTE and GERAN .................................................................. 222
LTE-SW1304, Cell Change Order to GERAN without NACC .......................................................... 233
LTE-SW1305, Cell Change Order to GERAN with NACC................................................................ 239
LTE-SW1306, Redirection to GERAN without SI ........................................................................... 245
LTE-SW1307, Redirection to GERAN with SI ................................................................................ 250
LTE-SW1310, CSFB to GERAN with Redirection with SI................................................................ 256
LTE-SW1311, CSFB to GERAN with CCO without NACC ............................................................... 264
LTE-SW1312, CSFB to GERAN with CCO with NACC ..................................................................... 272
LTE-SW1313, CSFB to GERAN with PS Handover ......................................................................... 281
LTE-SW2011, Service based Intra-LTE Handover ......................................................................... 288
LTE-SW2014, SPID based Dedicated Priority ................................................................................ 295
Chapter 5 Radio Scheduler 305
LTE-ME1101, PDSCH Resource Allocation .................................................................................... 305
LTE-ME3203, Aperiodic CQI Reporting......................................................................................... 309
LTE-ME3206, Periodic Channel Status Reporting ......................................................................... 311
LTE-ME3307, UL Sub-frame Bundling .......................................................................................... 316
LTE-ME3309, Resource allocation enhancement for SIB ............................................................. 320
LTE-ME3503, CFI-based PUSCH adaptation ................................................................................. 324
Chapter 6 Radio Transmission 328
LTE-ME0102, FDD 3MHz Bandwidth ............................................................................................ 328
LTE-ME0201, Frame Structure Type 1 (FDD) ................................................................................ 333
Chapter 7 Services 336
LTE-SV0303, OTDOA ..................................................................................................................... 336
LTE-SV0404, VoLTE Quality Enhancement ................................................................................... 344
LTE-SV0503, Multicell and Multicast Coordination (MCE) ........................................................... 351
LTE-SV0504, eMBMS Resource Allocation ................................................................................... 358
LTE-SV0514, Adaptive Delay Reduction for eMBMS .................................................................... 363
LTE-SV0515, eMBMS Session Monitoring .................................................................................... 368
LTE-SV0517, eMBMS Service Restoration .................................................................................... 374
LTE-SV1100, TCP Optimization ..................................................................................................... 378
Chapter 8 RAN Sharing 382
LTE-SW5001, Multi-PLMN Support .............................................................................................. 382
Chapter 9 SON 390
LTE-SO0201, Intra-LTE ANR .......................................................................................................... 390
LTE-SO0301, PCI AutoConfiguration ............................................................................................ 416
LTE-SO0401, RACH Optimization ................................................................................................. 426
LTE-SO0602, Cell Outage Compensation ..................................................................................... 441
LTE-SO0702, Coverage and Capacity Optimization ...................................................................... 450
LTE-SO0802, Cell On/Off in Multi-carrier Sites ............................................................................ 457
LTE-SO0804, DL MIMO TX Branch On/Off .................................................................................... 464
LTE-SO0901, Minimization Drive Test Optimization .................................................................... 472
LTE-SO2011, Drive Test Optimization (Coverage and Capacity Optimization)............................. 480
LTE-SO2021, Tx Power Control (Coverage and Capacity optimization) ....................................... 491
LTE-SO2031, Antenna Tilt Optimization (Coverage and Capacity Optimization) ......................... 499
LTE-SO2032, Antenna Tilt Optimization (Cell outage compensation) .......................................... 512
LTE-SO2041, New Cell Site Recommendation .............................................................................. 522
Chapter 10 System Test and Analysis 530
LTE-OM9001, Cell Traffic Trace .................................................................................................... 530
Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 iv

Samsung Proprietary and Confidential
Contents
LTE-OM9002, Subscriber and Equipment Trace........................................................................... 536

LTE-OM9004, CSL (Call Summary Log) Report ............................................................................. 541
LTE-OM9010, VoLTE Monitoring .................................................................................................. 543
LTE-OM9100, Key Performance Indexes ...................................................................................... 548
LTE-OM9101, L1 and L2 Counters ................................................................................................ 554
Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 v

Preface
This document provides detailed descriptions of new/enhanced features in the

PKG 5.0.0 software release.
Some features, commands, parameters, or counters are not supported by all

software releases or approved for all markets.
Relevance
This manual applies to the following products/software.
Name Type
PKG 5.0.0 Software
Conventions in this Document

Samsung Networks product documentation uses the following conventions.
Symbols
Symbol Description
Indicates a task.
Indicates a shortcut or an alternative method.
Provides additional information.
Provides information or instructions that you should follow to avoid service

failure or damage to equipment.
Provides information or instructions that you should follow to avoid personal
injury or fatality.
Provides antistatic precautions that you should observe.
Menu Commands
menu | command
This indicates that you must select a command on a menu, where menu is the
name of the menu, and command is the name of the command on that menu.
Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 vi

Preface
File Names and Paths

These are indicated by a bold typeface. For example:
Copy filename.ext into the /home/folder1/folder2/bin/ folder.
User Input and Console Screen Output Text

Input and output text is presented in the Courier font. For example,
context <designated epc-context-name>
CLI commands are presented in bold small caps. For example,
Type the RTRV-NE-STS command in the input field.
New and Changed Information

This section describes information that has been added/changed since the previous
publication of this manual.
In this document release, LTE-SW5001, Multi-PLMN Support feature is newly
added and the contents of LTE-ME5110, FDD Carrier Aggregation (5+5)
feature and LTE-ME3203, Aperiodic CQI Reporting feature are enhanced
compared to Samsung eNB (LTE) Feature Description for PKG 5.0.0 Ver.
1.0.
The following table shows new and enhanced features for PKG 5.0.0 compared
to PKG 4.0.0.
Development Type Feature ID, Name
New features LTE-ME2019, DL SU 2x2 MIMO (TM3 and TM4)
LTE-ME2020, Rx Diversity
LTE-ME2022, DL SU 4x4 MIMO (TM3 and TM4)
LTE-ME5110, FDD Carrier Aggregation(5+5)
LTE-SW0111, UE Counting per Category
LTE-SW0114, Enhancements for Diverse Data Applications
LTE-SW0315, Extended Access Barring (SIB14)
LTE-SW3010, PDCP Sublayer Support
LTE-SW5500, CA Call Control
LTE-SW2004, Blind Offloading to WCDMA
LTE-SW2020, Load Distribution over Backhaul Links
LTE-SW2103, UL Congestion Prevention
LTE-SW2108, Smart Congestion Mitigation
LTE-SW1202, PS Handover between LTE and UTRAN
LTE-SW1204, Redirection to UTRAN without SI
LTE-SW1205, Redirection to UTRAN with SI
LTE-SW1208, CSFB to UTRAN with Redirection with SI
Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 vii
Preface

LTE-SW1209, CSFB to UTRAN with PS Handover
LTE-SW1302, PS Handover between LTE and GERAN
LTE-SW1304, Cell Change Order to GERAN without NACC
LTE-SW1305, Cell Change Order to GERAN with NACC
LTE-SW1306, Redirection to GERAN without SI
LTE-SW1307, Redirection to GERAN with SI
LTE-SW1310, CSFB to GERAN with Redirection with SI
LTE-SW1311, CSFB to GERAN with CCO without NACC
LTE-SW1312, CSFB to GERAN with CCO with NACC
LTE-SW1313, CSFB to GERAN with PS Handover
LTE-SW2011, Service based Intra-LTE Handover
LTE-SW5001, Multi-PLMN Support
LTE-ME3203, Aperiodic CQI Reporting
LTE-ME3206, Periodic Channel Status Reporting
LTE-ME3307, UL Sub-frame Bundling
LTE-ME3309, Resource allocation enhancement for SIB
LTE-ME3503, CFI-based PUSCH adaptation
LTE-ME0102, FDD 3MHz Bandwidth
LTE-ME0201, Frame Structure Type 1 (FDD)
LTE-SO0802, Cell On/Off in Multi-carrier Sites
LTE-SO0804, DL MIMO TX Branch On/Off
LTE-SO2032, Antenna tilt optimization(Cell outage
compensation)
LTE-SO2041, New cell site recommendation
LTE-SV0404, VoLTE Quality Enhancement
LTE-SV0504, eMBMS Resource Allocation
LTE-SV0514, Adaptive Delay Reduction for eMBMS
LTE-SV0517, eMBMS Service Restoration
LTE-SV1100, TCP Optimization
LTE-OM9010, VoLTE Monitoring
LTE-OM9100, Key Performance Indexes
LTE-OM9101, L1 and L2 Counters
Enhanced features LTE-ME6004, DL Smart
LTE-ME6005, UL Smart (Interference Coordination for UL)
LTE-SW0321, UE Context Management
LTE-SW0322, E-RAB Management
LTE-SW0501, S1 Interface Management
LTE-SW0510, Geo Redundancy of MME
LTE-SW0521, X2 Interface Management
LTE-SW4101, Capacity based Call Admission Control
LTE-SW4103, Preemption
LTE-SW2104, eNB Overload Protection
LTE-SW1002, Idle Mobility Support
LTE-SW1004, S1 Handover
LTE-SW1005, X2 Handover
LTE-SW1301, Idle Mobility to GERAN
LTE-SW2014, SPID based Dedicated Priority
LTE-ME1101, PDSCH Resource Allocation
Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 viii
Preface

LTE-SO0201, Intra-LTE ANR
LTE-SO0301, PCI AutoConfiguration
LTE-SO0401, RACH optimization
LTE-SO0602, Cell Outage Compensation
LTE-SO0702, Coverage and Capacity Optimization
LTE-SO0901, Minimization Drive Test Optimization
LTE-SO2011, Drive test optimization (Coverage and Capacity
optimization)
LTE-SO2021, Tx Power Control(Coverage and Capacity
optimization)
LTE-SO2031, Antenna tilt optimization(Coverage and Capacity
Optimization)
LTE-SV0303, OTDOA
LTE-SV0503, Multicell and Multicast Coordination (MCE)
LTE-SV0515, eMBMS Session Monitoring
LTE-OM9001, Cell Traffic Trace
LTE-OM9002, Subscriber and Equipment Trace
LTE-OM9004, CSL(Call Summary Log) Report
Revision History
The following table lists all versions of this document.
Document Number Product/Software Document Publication Date Remarks
Version Version
2600-00GAR0GAP PKG 3.0.0 1.0 2 February 2014 -
2600-00GAR0GAP PKG 3.0.0 2.0 4 February 2015 -
2600-00GM80GAP PKG 3.1.0 1.0 26 June 2014 -
2600-00GM80GAP PKG 3.1.0 2.0 9 April 2015 -
2600-00GXYAGAP PKG 4.0.0 1.0 20 Oct 2014 -
2600-00GXYAGAP PKG 4.0.0 2.0 14 January 2015 -
2600-00I10TGAP PKG 5.0.0 1.0 29 July 2015 -
2600-00I10TGAP PKG 5.0.0 2.0 4 December 2015 -
Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 ix

Preface
Organization of This Document

Section Title Description
Chapter 1 Air Performance Enhancement This chapter describes PKG 5.0.0 LTE features
related to Air Performance Enhancement.
Chapter 2 Call Control This chapter describes PKG 5.0.0 LTE features
related to Call Control.
Chapter 3 Load Control This chapter describes PKG 5.0.0 LTE features
related to Load Control.
Chapter 4 Mobility Control This chapter describes PKG 5.0.0 LTE features
related to Mobility Control.
Chapter 5 Radio Scheduler This chapter describes PKG 5.0.0 LTE features
related to Radio Scheduler.
Chapter 6 Radio Transmission This chapter describes PKG 5.0.0 LTE features
related to Radio Transmission.
Chapter 7 Services This chapter describes PKG 5.0.0 LTE features
related to Services.
Chapter 8 RAN Sharing This chapter describes PKG 5.0.0 LTE features
related to RAN Sharing.
Chapter 9 SON This chapter describes PKG 5.0.0 LTE features
related to SON.
Chapter 10 System Test and Analysis This chapter describes PKG 5.0.0 LTE features
related to System Test and Analysis.
Related Documentation
Samsung eNB (OAM) Feature Description for PKG 5.0.0
Samsung eNB (Transport) Feature Description for PKG 5.0.0
Samsung LTE eNB Command Reference for PKG 5.0.0
Samsung LTE eNB Parameter Description for PKG 5.0.0
Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 x

Chapter 1 Air Performance
Enhancement

INTRODUCTION
Multiple antenna techniques aim to improve data robustness or provide an increase
in data rates by utilizing special signal structure and exploiting un-correlated
fading channels for each transmitted signal. In case of two transmit antennas on an
eNB and two receive antennas on the same UE- it is known downlink 2x2 single-
user MIMO. The following figure shows concept of single user MIMO using m
transmit and n receive antennas.
As shown in the figure above, each receiver side antenna receives a composite
signal made up of transmitted signals modified by their channels. Under specific
channel conditions, the transmitter can structure the transmitted signals to, either
send modified copies of the same transmission (transmit diversity) or, send
different transmission (spatial multiplexing).
The former case provides signal robustness and the latter provides increase in data
rate.
BENEFIT
Provide improvement in cell capacity and throughput as UEs with better channel
conditions can benefit from the multiple streams transmission.
Served the improved throughput or reliable communication due to the multiple
streams transmission.
DEPENDENCY AND LIMITATION

Dependency
Need 2CRS supported terminal UE.
Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 1
Chapter 1 Air Performance Enhancement
2T RRU is required.
FEATURE DESCRIPTION
Samsung supports DL SU-MIMO Spatial Multiplexing (SM) in both Transmission
Mode 3 (TM3: open-loop SM) and Transmission Mode 4 (TM4: closed-loop SM)
employing either 2x2 antenna configuration that is 2 transmit eNB antennas and 2
receive UE antennas.
Transmit Diversity
Transmit diversity is default MIMO mode in LTE. This redundancy leads to
increase in signal-to-noise ratio and therefore, signal robustness. Transmission
Mode 2 provides transmit diversity by transmitting a single PDSCH codeword
using four antennas.
Spatial Multiplexing
In spatial multiplexing, there is no signal redundancy as with transmit diversity;
antenna ports transmit different symbols. There are two modes that can provide
spatial diversity; such as TM3 and TM4. TM3 uses a predetermined CDD-based
precoding and favorable to high speed UEs. TM4 uses a codebook-based
precoding and favorable to low speed UEs because scheduler adopts the best
precoder per UE based on the precoder fed-back by UE. For both TM3 and TM4,
rank adaptation based on fed-back rank information is supported so that the most
appropriate number of transmission layers (and codewords) can be adopted.
Mode Description Antenna Ports Layer Codewords Channel Rank UE Feedback
TM3 Open loop spatial 2 2 2 2 CQI, RI
multiplexing with
cyclic delay
diversity
TM4 Closed loop spatial 2 2 2 2 CQI, RI, PMI
multiplexing with
precoding matrix
Transmission Mode 3
TM3 is spatial multiplexing scheme that uses pre-determined precoding matrix.
The process of applying pre-coding is defined in 3GPP specification TS 36.211.
Open loop spatial uses Channel Quality Information (CQI) and Rank Indication
(RI) information fed-back from UE.
TM3 is suitable for scenarios when the UE is in good channel condition. A
stationary or pedestrian speed UE in good RF coverage scenario will get the most
benefit from this mode.
Codewords, layers mapping in open-loop spatial multiplexing (TM3) for 2 antenna
ports are tabulated as follows:
Number of Number CW, Layer mapping
codewords of layers


codewords of layers
2 2
Transmission Mode 4
TM4 is spatial multiplexing scheme that uses PMI index fed-back from UE, to
construct downlink PDSCH codeword to maximize signal to noise ratio at UE
receiver.
A PMI index is a pointer to a set of pre-coding weights that are applied to
downlink code-words prior to transmission. The process of applying pre-coding is
defined in 3GPP specification TS 36.211. TM 4 is suitable for scenarios when UE
is in slow time-varying channel because there is a delay associated with a PMI
report from UE and a corresponding downlink transmission that utilizes the
reported PMI index. A stationary or pedestrian speed UE in good RF coverage
scenario will get the most benefit from this mode.
Codewords, layers mapping in closed-loop spatial multiplexing (TM4) for 4
antenna ports are tabulated as follows:
codewords of layers
1 1
2 2

SYSTEM OPERATION
How to Active
To enable this feature, DL_ANT_COUNT should be set equal to or greater than
n2TxAntCnt.
Execute the CHG-CELL-IDLE command to change the parameter
DL_CRS_PORT_COUNT to two to enable 2x2 SU-MIMO.
Key Parameters
RTRV-CELL-IDLE/CHG-CELL-IDLE
Parameter Description
DL_ANT_COUNT This parameter is the number of Tx antennas used by an operating cell.
DL_CRS_PORT_COUNT This parameter is the number of downlink CRS ports that are supported by the
system.
RTRV-DL-SCHED/CHG-DL-SCHED
CELL_NUM This parameter describes user-defined cellId.
DL_MIMO_MODE This parameter specifies transmission mode. Each one is corresponding to
certain multiple antenna techniques.
TM1: Single-antenna port (port 0), DCI format 1 or 1A is used.
TM2: Transmit diversity, DCI format 1 or 1A is used.
TM3: Open-loop spatial multiplexing, DCI format 2A or 1A is used.
TM4: Closed-loop spatial multiplexing, DCI format 2 or 1A is used.
TM5: MU-MIMO, DCI format 1D or 1A is used. It is a test mode and it is not
supported.
TM6: Closed-loop rank-1 precoding, DCI format 1B or 1A is used. It is a test
mode and it is not supported.
TM7: Single-antenna port (port 5), DCI format 1 or 1A is used. It is supported
for only 8T8R TDD.
TM8: Dual layer transmission, or Single-antenna port (port 7/port 8), DCI
format 2B or 1A is used. It is supported for only 8T8R TDD.
TM9: UE specific RS based Transmission (Rel 10)
[Related Specifications] 3GPP TS 36.213
ALPHA Fairness weight in PF scheduler. If alpha is increased, scheduling fairness
increase such as Round Robin scheduling.
BETA Channel quality weight in PF scheduler. If beta is increased, scheduling
efficiency increases such as Max C/I.
GAMMA Priority weight in PF scheduler.
Counters and KPIs

There are no related counters and KPIs.

REFERENCE
[1] 3GPP TS 36.201 Evolved Universal Terrestrial Radio Access (E-UTRA);
Physical layer; General description
Physical Channels and Modulation
Multiplexing and channel coding
Physical layer procedures
Physical layer; Measurements
[6] 3GPP TS 36.300 Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall
description; Stage 2

LTE-ME2020, Rx Diversity
INTRODUCTION
Currently, receive diversity techniques are not specified in the LTE specification,
because receive diversity places no requirements in the transmitter. However, it
needs to be noted that receive diversity enables to make better quality on uplink
received signal. Samsung eNB support Rx diversity using Minimum Mean
Squared Error (MMSE) combining with Interference Rejection Combining (IRC)
receiver.
BENEFIT
Rx diversity enables to communicate in the more reliable transmission condition.

N/A
FEATURE DESCRIPTION
In Rx diversity, the receiver needs to combine multiple streams from different
antenna into a single stream. The challenge here is how to use the information
from all the antennas effectively. In fact, it is just a matter of choosing the
appropriate weight for each received signals (see the following figure).
There are multiple ways to choose the weight of receiver, but Samsung eNB uses
linear MMSE (LMMSE) receiver with IRC to suppress inter-cell interference.

Linear Minimum Mean Squared Error (LMMSE) Receiver with Interference Rejection
Combining (IRC)
To obtain receive diversity, Samsung eNB considers LMMSE criterion with IRC.
This advanced receiver employing IRC is effective in improving the cell-edge user
throughput. The IRC receiver utilizes the covariance of interference and noise
factors of multiple receiver branches, and combines the received signals for
multiple receiver branches so that the Mean Square Error (MSE) between the
combined signal and the desired signal is minimized, instead of Maximal Ratio
Combining (MRC).
The specific combining criterion is as follows:
1 The channel estimator of the eNB receiver estimates the channel of the desired
signal, and generates the covariance matrix of interference and noise.
oEstimate the channel matrix of the desired signal
oEstimate the covariance matrix of interference and noise
2 Using the estimated channel and the covariance matrix, MMSE weight is
calculated to perform IRC.
oMinimum Mean Squared Error (MMSE) criterion
oMMSE criterion achieves the optimal balance the noise enhancement and
interference suppression
oCombined weight
3 Interference rejection is achieved by MMSE combining at the eNB receiver.
The IRC scheme based on MMSE criterion achieves an optimal balance of noise
enhancement and interference suppression. Hence, IRC provides the enhanced
performance to UEs at the cell boundary that experience serious interference from
other cell. The receive diversity can be obtained from combining the calculated
weight with received signals for each receiver path.
SYSTEM OPERATION
How to Activate
This feature is an optional feature and can be activated and deactivated with the
parameter IRC_ENABLE.

Default IRC_ENABLE is 'FALSE (IRC OFF) (IRC_ENABLE= 0)'.

Execute the CHG-PUSCH-IDLE command to set IRC_ENABLE to 'TRUE (IRC
ON) (IRC_ENABLE = 1)'.
Execute the RTRV-PUSCH-IDLE command to retrieve the configuration
information for IRC_ENABLE.
The operator can disable this feature by setting IRC_ENABLE to 'FALSE (IRC
OFF)' (IRC_ENABLE= 0).
Key Parameters
RTRV-PUSCH-IDLE/CHG-PUSCH-IDLE
IRC_ENABLE This parameter is used to enable to use IRC
0: False (IRC OFF)
1: True (IRC ON)
Counters and KPIs

REFERENCE
[1] 3GPP TS 36.201 Evolved Universal Terrestrial Radio Access (E-UTRA); LTE
physical layer; General description
[2] Goldsmith, A. J. Wireless communications. Cambridge University Press, 2005


INTRODUCTION
fading channels for each transmitted signal. In case of four transmit antennas on an
eNB and four receive antennas on the same UE- it is known as downlink 4x4
single-user MIMO. Below figure, illustrates the concept of single user MIMO
using m transmit and n receive antennas.
The following figure is m x n single user MIMO concept:
different transmission (spatial multiplexing) or combination of both. Transmit
diversity provides signal robustness and spatial multiplexing increases data rate.
BENEFIT
The operator provides improvement in cell capacity and throughput as UEs with
better channel conditions can benefit from the multiple streams transmission.
The user can be served with improved throughput or reliable communication due
to the multiple streams transmission.

Dependency
4Tx RU is necessary.
Category 5 UE (4Rx ready UE) is necessary. (This feature's release schedule is
subject to change by UE availability that supports this feature.)

FEATURE DESCRIPTION
Samsung plans to support the DL SU-MIMO Spatial Multiplexing (SM) in both
Transmission Mode 3 (open-loop SM) and Transmission Mode 4 (closed-loop
SM) employing 4x4 antenna configuration that is 4 transmit eNB antennas and 4
receive UE antennas.
Transmission mode 3
TM 3 is spatial multiplexing scheme that uses pre-determined precoding matrix.
Open loop spatial multiplexing uses CQI (Channel Quality Information) and RI
(Rank Indication) information fed-back from UE.
TM 3 is suitable for scenarios when the UE is in good channel condition. A
stationary or pedestrian speed UE in good RF coverage scenario will get the most
benefit from this mode.
codewords of layers
1 2
2 2


codewords of layers
4
Transmission Mode 4
TM 4 is spatial multiplexing scheme that uses PMI index fed-back from UE, to
receiver.
defined in 3GPP specification TS 36.211. TM 4 is suitable for scenarios when the
UE is in slow time-varying channel because there is a delay associated with a PMI
requested PMI index. A stationary or pedestrian speed UE in good RF coverage
scenario will get the most benefit from this mode.
Codewords, layers mapping in close-loop spatial multiplexing (TM4) for 4 antenna
codewords of layers
1 1


codewords of layers
2 2
SYSTEM OPERATION
How to Activate
n4TxAntCnt
DL_CRS_PORT_COUNT to four to enable 4x4 SU-MIMO.
Execute the CHG-DL-SCHED command to change the downlink transmission
mode.
oci_tm3 is transmission mode 3.
oci_tm4 is transmission mode 4.
Key Parameters

system.
CELL_NUM This parameter is the number of cells. This value must not exceed the maximum
number of cells supported by the system. It is determined by FA/Sector. For
example, if the maximum capacity provided to the carrier per system is 1 FA/3
Sector, up to 3 cells are supported.
DL_MIMO_MODE This parameter specifies transmission mode. Each one is corresponding to
certain multiple antenna techniques.
TM1: Single-antenna port (port 0), DCI format 1 or 1A is used.
TM2: Transmit diversity, DCI format 1 or 1A is used.
TM3: Open-loop spatial multiplexing, DCI format 2A or 1A is used.
TM4: Closed-loop spatial multiplexing, DCI format 2 or 1A is used.
TM5: MU-MIMO, DCI format 1D or 1A is used. It is a test mode and it is not
supported.
TM6: Closed-loop rank-1 precoding, DCI format 1B or 1A is used. It is a test
mode and it is not supported.
TM7: Single-antenna port (port 5), DCI format 1 or 1A is used. It is supported
for only 8T8R TDD.
TM8: Dual layer transmission, or Single-antenna port (port 7/port 8), DCI
format 2B or 1A is used. It is supported for only 8T8R TDD.
TM9: UE specific RS based Transmission (Rel 10)
[Related Specifications] 3GPP TS 36.213
ALPHA Fairness weight in PF scheduler. The larger alpha is, the better the fairness is.
BETA Channel quality weight in PF scheduler. The larger beta is, the better the
channel efficiency is.
GAMMA Priority weight in PF scheduler. The larger gamma is the smaller scheduling
delay is. However, if it is very high, system capacity can be decreased because
scheduler considers delay excessively.
Counters and KPIs

REFERENCE



INTRODUCTION
fading channels for each transmitted signal. In case of four transmit antennas on an
eNB and two receive antennas on the same UE, it is known downlink 4x2 single-
user MIMO. The following figure shows concept of single user MIMO using m
transmit and n receive antennas.
different transmission (spatial multiplexing). The former case provides signal
robustness and the latter provides increase in data rate.
BENEFIT
The operator can provide improvement in cell capacity and throughput as UEs
with better channel conditions can benefit from the multiple streams
transmission.
The user can be served the improved throughput or reliable communication due
to the multiple streams transmission.

Dependency
Need 4CRS supported terminal UE.
4T RRU is required.
Currently TM3 is default MIMO mode and TM4 cannot be enabled.

TM4 will be officially supported after IOT and then MIMO mode selection
parameter (dlMimoMode) will be enabled.
FEATURE DESCRIPTION
Samsung supports the DL SU-MIMO Spatial Multiplexing (SM) in both
Transmission Mode 3 (TM3: open-loop SM) and Transmission Mode 4 (TM4:
closed-loop SM) employing either 4x2 antenna configuration that is 4 transmit
eNB antennas and 2 receive UE antennas.
Transmit Diversity
Transmit diversity is default MIMO mode in LTE. This redundancy leads to
increase in signal-to-noise ratio and therefore, signal robustness. Transmission
Mode 2 provides transmit diversity by transmitting a single PDSCH codeword
using 4 antennas.
Spatial Multiplexing
In spatial multiplexing, there is no signal redundancy as with transmit diversity;
antenna ports transmit different symbols. There are two modes that provide spatial
diversity: TM3 and TM4. TM3 uses a predetermined CDD-based precoding and
favorable to high speed UEs. TM4 uses a codebook-based precoding and favorable
to low speed UEs because scheduler adopts the best precoder per UE based on the
precoder fed-back by UE. For both TM3 and TM4, rank adaptation based on fed-
back rank information is supported so that the most appropriate number of
transmission layers (and codewords) can be adopted.
Mode Description Antenna Layer Codewords Channel UE
Ports Rank Feedback
TM3 Open loop spatial multiplexing 4 2 2 2 CQI, RI
with cyclic delay diversity
TM4 Closed loop spatial multiplexing 4 2 2 2 CQI, RI,
with precoding matrix PMI
Transmission Mode 3
TM3 is spatial multiplexing scheme that uses pre-determined precoding matrix.
Open loop spatial uses Channel Quality Information (CQI) and Rank Indication
(RI) information fed-back from UE.
TM3 is suitable for scenarios when UE is in good channel condition. A stationary
or pedestrian speed UE in good RF coverage scenario gets the most benefit from
this mode.
ports are shown in the table below.
codewords of layers


codewords of layers
2 2
Transmission Mode 4
TM4 is spatial multiplexing scheme that uses PMI index fed-back from UE, to
receiver.
defined in 3GPP specification TS 36.211. TM 4 is suitable for scenarios when the
UE is in slow time-varying channel because there is a delay associated with a PMI
reported PMI index. A stationary or pedestrian speed UE in good RF coverage
scenario gets the most benefit from this mode.
Codewords, layers mapping in closed-loop spatial multiplexing (TM4) for 4
antenna ports are shown in the following table.
codewords of layers
1 1
2 2

SYSTEM OPERATION
How to Activate
n4TxAntCnt.
DL_CRS_PORT_COUNT to four to enable 4x2 SU-MIMO.
Key Parameters
system.
CELL_NUM This parameter is the number of cells. This value must not exceed the maximum
ALPHA Fairness weight in PF scheduler. The larger alpha is, the better the fairness is.
BETA Channel quality weight in PF scheduler. The larger beta is, the better the
channel efficiency is.
GAMMA Priority weight in PF scheduler. The larger gamma is the smaller scheduling
delay is. However, if it is very high, system capacity can be decreased because
scheduler considers delay excessively.
Counters and KPIs

REFERENCE



LTE-ME5110, FDD Carrier Aggregation (5+5)

INTRODUCTION
The FDD Carrier Aggregation (5+5) feature enables an eNB to aggregate with
5+5MHz LTE Component Carriers (CCs). The purpose of multiple CCs
aggregation is to have wider channel bandwidth, which helps operators to increase
bitrates for end-users.
BENEFIT
An operator can combine individual CCs from different bands and bandwidths.
The feature ensures that all the spectrum resources are utilized effectively across
the network for improving efficiency and achieving peak throughputs.

Dependency
HW dependency
oSupport Channel Cards: CA could be restricted depending on the hardware
configuration.
Required Network Elements
oNetwork Elements Dependency: No special network element required null
Others: Device needs to support this feature.
Limitation
Due to UE availability of CA with 4x4MIMO, CA with 2x2MIMO can be
supported.
FEATURE DESCRIPTION
The Samsung eNB supports a combination of 5+5 MHz CCs in downlink. Each
aggregated carriers is referred to as CC.
Figure below illustrates the 5+5 aggregated LTE channels.
FDD
5 MHz
FDD
5 + 5 MHz CA
FDD
5 MHz

The operator can have the following three types of carrier allocation based on the
spectrum usage:
Intra-band Contiguous CA
Intra-band Non-contiguous CA
Inter-band Non-contiguous CA
For detailed description of CA functionality and its operational procedures, see
LTE-SW5500: CA Call Control.
SYSTEM OPERATION
Refer to the System Operation section of LTE-SW5500: CA Call Control feature
for configuration, key parameter, and detailed information on counters associated
with this feature.
REFERENCE
User Equipment (UE) radio transmission and reception
Radio Resource Control (RRC); Protocol specification
[7] 3GPP TR 36.814 Evolved Universal Terrestrial Radio Access (E-UTRA);
Further advancements for E-UTRA physical layer aspects
[8] 3GPP TR 36.912 Feasibility study for Further Advancements for E-UTRA
(LTE-Advanced)


INTRODUCTION
The FDD Carrier Aggregation (3+5) enables an eNB to aggregate with 3+5 MHz
LTE Component Carriers (CCs). The purpose of multiple CCs aggregation is to
have wider channel bandwidth, which helps operators to increase bitrates for end-
users.
BENEFIT
The operator can combine individual CCs from different band and bandwidths.
All the spectrum resources are utilized effectively across the network for
improving efficiency and achieving higher peak throughputs.

Dependency
Device needs to support this feature.
CA could be restricted depending on the HW configuration.
FEATURE DESCRIPTION
The following figure shows the 3+5 aggregated LTE channels.
spectrum usage:

For detailed description of CA functionality and its operational procedures, refer to

LTE-SW5500: CA Call Control feature description document.
SYSTEM OPERATION
with this feature.
REFERENCE
(LTE-Advanced)


INTRODUCTION
The FDD Carrier Aggregation (3+3) enables an eNB to aggregate with 3+3 MHz
LTE Component Carriers (CCs). The purpose of multiple CCs aggregation is to
have wider channel bandwidth, which helps operators to increase bitrates for end-
users.
BENEFIT
The operator can combine individual CCs from different band and bandwidths.
All the spectrum resources are utilized effectively across the network for
improving efficiency and achieving higher peak throughputs.

Dependency
Device needs to support this feature.
CA could be restricted depending on the HW configuration.
FEATURE DESCRIPTION
The following figure shows the 3+3 aggregated LTE channels.
spectrum usage:

For detailed description of CA functionality and its operational procedures, refer to

LTE-SW5500: CA Call Control feature description document.
SYSTEM OPERATION
with this feature.
REFERENCE
(LTE-Advanced)

LTE-ME6004, DL Smart
INTRODUCTION
The DL-Smart feature performs centralized coordination for the radio resource of
all cells connected to Smart Scheduler Server to enhance the cell performance. In
this case, each eNB allocates the physical radio resource to the UE based on the
results of the coordination.
BENEFIT
This will result in performance enhancement for DL data transmission.

Dependency
This feature works with Smart Scheduler server. Smart Scheduler server supports
C-RAN only, D-RAN only, or H-RAN mode.
The eNB operates RT or NRT mode depending on the mode of Smart Scheduler
server.
This feature needs time synchronization between cells.
This feature requires backhaul latency between eNB and Smart Scheduler Server
less than 30ms (in round-trip-time (RTT)) for DRAN or HRAN.
Limitation
The number of cells supporting a Smart Scheduler server is different according to
the type of the server.
MR based DL Smart is necessary when Carrier Aggregation (CA) is activated.
FEATURE DESCRIPTION
The network for DL-Smart is consisted of one Smart Scheduler and a large number
of eNBs. Samsung supports three types of DL-Smart networks as C-RAN, D-RAN,
and H-RAN. Each network diagram is referred from the following figures.
(A) C-RAN

(B) D-RAN
(C) H-RAN

Each eNB is connected with Smart Scheduler server and is classified as C-RAN
eNB or D-RAN eNB according to the transmission delay between Smart Scheduler
server and eNB.
In figure (A), C-RAN eNB is concentrated with Smart Scheduler, so C-RAN
network guarantees short transmission delay less than 1ms. Each RU distributed
from C-RAN eNB is connected with DU using the dark fiber.
D-RAN eNB is shown in figure (B) and is distributed from Smart Scheduler using
Ethernet network connection with transmission delay longer than 1ms.
Smart Scheduler server can support inter-cell interference coordination via same
structure for C-RAN and D-RAN. Thus, Smart Scheduler server can support DL-
Smart although C-RAN eNBs and D-RAN eNBs are interconnected in H-RAN
environment. H-RAN network is shown in figure (C).
In each network architecture, if there is no Smart Scheduler, eNBs can provide
stand-alone operation.
The following figure shows the software structure of Smart Scheduler network:

The following functions are performed by each SW block:

Coordinator in Smart Scheduler server
oNon real time (NRT) coordination.
oReal time (RT) coordination for C-RAN cells.
oTransfer NRT/RT resource allocation pattern to RT-Scheduler.
Pre-Scheduler in Smart Scheduler server
oSelection of the representative UE for each cell
oTransfer the metric of the representative UE to coordinator.
UE Manager in Smart Scheduler server
oSRS/MR based Tx power estimation of Cell
oGeneration of the preferred resource allocation pattern
RT-Scheduler in eNB
oSelects a candidate UE, and then transfer channel and traffic information of
the candidate UE to Smart Scheduler server. (When carrier aggregation
and DL Smart are enabled at the same time, RT-Scheduler receives MR for
the SCell from each UE and then transfers it to Smart Scheduler Server
periodically.)
oAllocates resource using NRT/RT resource allocation pattern
DL-Smart feature performs scheduling according to the following procedure:
1 RT-Scheduler block of the eNB selects the candidate UE for each cell.

2 UE Manager block of the Smart Scheduler generates the preferred resource

allocation pattern for each UE using DL/UL received power estimation.
3 Pre-Scheduler block selects the representative UE for each cell.
4 Coordinator block performs the coordination of radio resources for each cell
based on the scheduling metric, generates the resource allocation pattern based
on the coordination results and sends it to eNB.
5 RT-Scheduler block compensates the UE channel quality (CQI) based on the
resource allocation pattern and allocates the control channel and the data
channel to UE.
6 RT-Scheduler block confirms the resource allocation based on the resource
coordination information from Post-Scheduler block and generates
RLC/Modem control information.
SYSTEM OPERATION
How to Activate
To enable this feature, execute the CHG-CELLSCHR-CONF command.
If the flag of SMART_CELL_COORDI_ENABLE is false, the state of DL smart
is OFF.
If the flag of SMART_CELL_COORDI_ENABLE is true, the state of DL smart
is ON.
Key Parameters
RTRV-CELLSCHR-CONF/CHG-CELLSCHR-CONF
CELL_NUM The cell number. This value must not exceed the maximum number of
cells supported by the system.
SMART_CELL_COORDI_ENABL It is the SmartCell DL Coordination function ON (true)/OFF (false) flag,
E that is, the control flag of interworking function between eNB and the
Smart Scheduler Server.
Counters and KPIs

Family Name Type Description
Throughput distribution counter for ThroughputAvg Average UE throughput
CS ON OFF (1 of 2)
ThroughputTot Total UE throughput
ThroughputCnt Total number of UE throughputs
Thru0_20 Number of UE throughputs ranging from
0kbps to 20 kbps
... ...
16,880 kbps to 16,900 kbps
Throughput distribution counter for Thru16900_16920 Number of UE throughputs ranging from

Family Name Type Description

CS ON OFF (2 of 2) 16,900 kbps to 16,920 kbps
... ...
280,600 kbps to 306,200 kbps
REFERENCE
[8] 3GPP TR 36.819 Coordinated multi-point operation for LTE physical layer
aspects
[9] 3GPP TR 36.913 Requirements for Evolved UTRA (E-UTRA) and Evolved
UTRAN (E-UTRAN)

LTE-ME6005, UL Smart (Interference

Coordination for UL)
INTRODUCTION
The UL-Smart feature performs centralized coordination for the radio resource of
all cells to enhance the cell performance. In this case, each eNB allocates the
physical radio resource to UE based on the results of the coordination.
BENEFIT
This will result in performance enhancement for UL data transmission.

Dependency
This feature works with Smart Scheduler server which supports C-RAN only, D-
RAN only, or H-RAN.
This function needs time synchronization.
This feature follows DL Smart (LTE-ME6004) feature in terms of the network
architecture, interfaces, and so on.
Limitation
The number of cells supported by a Smart Scheduler server is different according
to the type of the server.
FEATURE DESCRIPTION
The network for UL-Smart is consisted of one Smart Scheduler and a large number
of eNBs. Samsung supports three types of UL-Smart networks as C-RAN, D-RAN,
and H-RAN. Each network diagram is referred from the following figures.
(A) C-RAN

(B) D-RAN
(C) H-RAN

Each eNB is connected with Smart Scheduler server and is classified as C-RAN
eNB, and D-RAN eNB according to the transmission delay between Smart
Scheduler server and eNB.
In figure (A), C-RAN eNB is concentrated with Smart Scheduler, so C-RAN
network guarantees short transmission delay less than 1ms. Each RU distributed
from C-RAN eNB is connected with DU using the dark fiber.
D-RAN eNB is shown in figure (B) and is distributed from Smart Scheduler using
Ethernet network connection with transmission delay longer than 1ms.
Smart Scheduler server can support inter-cell interference coordination via same
structure for C-RAN and D-RAN. Thus, Smart Scheduler server can support UL-
Smart although C-RAN eNB and D-RAN eNB are co-located in H-RAN
environment. H-RAN network is shown in figure (C).
In each network architecture, if there is no Smart Scheduler, eNBs can provide
stand-alone operation.
The following figure shows the software structure of Smart Scheduler network:

The following functions are performed by each SW block:

Coordinator in Smart Scheduler server
oDetermines inter-interference relation between serving cell and neighbor cells
based on SRS.
oGenerates allocation pattern using load information and inter-cell interference
relation to improve the performance of cell edge UE.
oTransfers resource allocation pattern to RT-Scheduler.
UE Manager in Smart Scheduler server
oDetermines (1) cell edge UEs based on SRS
oDetermines (2) which of cells receive inter-cell interference from UE of the
serving cell based on SRS.
oTransfers UEs information (1) and (2) to RT-Scheduler, and information (2)
to Coordinator.
RT-Scheduler in eNB
oTransfers load information, such as the amount of inter-cell interference
which UEs generate in the serving and amount of inter-cell interference
which the serving cell receives from neighbor cells, to Coordinator.
oAllocates resource using UEs information and resource allocation pattern.
UL-smart feature performs the scheduling according to the following procedure:
1 RT-Scheduler calculates the amount of inter-cell interference which UEs
generate in the serving and amount of inter-cell interference which the serving
cell receives from neighbor cells. And then RT-Scheduler transfers them to
Coordinator in Smart Scheduler server.

2 UE Manager determines (1) cell edge UE and (2) which of cell receive inter-cell
interference from UE of serving cell based on SRS. And then UE Manager
transfers UEs information (1) and (2) to RT-Scheduler, and information (2) to
Coordinator.
3 Coordinator determines inter-interference relation between cells based on SRS.
And then coordinator generates allocation pattern using load information and
inter-cell interference relation.
4 Coordinator transfers resource allocation pattern to RT-Scheduler.
5 RT-Scheduler allocates resource to UEs using UEs information and resource
allocation pattern for cell edge UEs to avoid inter-cell interference from
neighbor cells.
SYSTEM OPERATION
How to Activate
This feature is an optional feature and can be activated and deactivated.
Execute the RTRV-SMTUL-SCHED command to retrieve the configuration
information of smart uplink scheduling.
Execute the CHG-SMTUL-SCHED command to change the configuration
information of smart uplink scheduling in units of smart scheduler server.
oIf the value of ulSmartCsOnOff is '0', the state of UL smart is OFF.
oIf the value of ulSmartCsOnOff is not '0', the state of UL smart is ON. (The
recommended value of ulSmartCsOnOff is '3')
Key Parameters
RTRV-SMTUL-SCHED/CHG-SMTUL-SCHED
dbIndex This is just db index.
ulSmartCsOnOff This parameter enables or disables the coordinated scheduling (CS) of UL
smart.
If ulSmartCsOnOff = 0, coordinated scheduling is OFF (false).
If ulSmartCsOnOff = 1, coordinated scheduling using start RB index is ON
(true). RT-Scheduler can allocate the resource from the lowest RB index or
from the highest RB index for cell edge UE to avoid inter-cell interference
between neighbor cells.
If ulSmartCsOnOff = 2, coordinated scheduling using edge pattern is ON (true).
RT-Scheduler allocates the resource using edge pattern for cell edge UE to
avoid inter-cell interference between neighbor cells.
If ulSmartCsOnOff = 3, coordinated scheduling using start RB index and edge
pattern is ON (true). RT-Scheduler dynamically switches between CS using
start RB index and CS using edge pattern.

Counters and KPIs

There is no related counter and KPI.
REFERENCE
[8] 3GPP TR 36.819 Coordinated multi-point operation for LTE physical layer
aspects
[9] 3GPP TR 36.913 Requirements for Evolved UTRA (E-UTRA) and Evolved
UTRAN (E-UTRAN)

Chapter 2 Call Control
LTE-SW0111, UE Counting per Category

INTRODUCTION
The eNB performs counting for each category of RRC_Connected UE and collects
the statistics per eNB.
BENEFIT
UE counting per category supports to analyze the connected UEs' status per
category.

Limitation:
This statistics collection is impossible if eNB cannot acquire UE category
information from MME during idle to active transition.
If a time-out occurs because UE does not transmit ATTACH COMPLETE, the
statistics is counted but UE context release may be performed in MME.
FEATURE DESCRIPTION
This feature enables the operator to know the number of UE in the network for
each UE category. The eNB obtains UE category information during two possible
states - during attachment or idle to active transition.
The following figure shows during ATTACH procedure, eNB saves UE category
during UE Capability Enquiry/UE Capability Information procedure and counts
the statistics after ATTACH procedure is finished.

The following figure shows during Idle to Active procedure, eNB saves UE
category during Initial Context Setup Request/Initial Context Setup Response
procedure and counts the statistics after ATTACH is finished.
SYSTEM OPERATION
How to Activate
This feature is basically enabled and operator cannot disable.
Key Parameters
There are no related parameters.
Counters and KPIs

Family Display Type Name Type Description
Name
UE Category UE_Category_1 Number of UEs in the UE Category 1
UE_Category_2 Number of UEs in the UE Category 2


Name
REFERENCE
[1] The Vendors LTE solution shall support functionality to enquire UE capability
and record number of UEs per eNodeB and per cell for each UE category.
[2] 3GPP TS36.300 Evolved Universal Terrestrial Radio Access (E-UTRA) and
[3] 3GPP TS36.306 Evolved Universal Terrestrial Radio Access (E-UTRA); User
Equipment (UE) radio access capabilities (Release 9)
[4] 3GPP TS36.331 Evolved Universal Terrestrial Radio Access (E-UTRA); Radio
Resource Control (RRC); Protocol specification (Release 9)

LTE-SW0114, Enhancements for Diverse Data

Applications
INTRODUCTION
Multiple Diverse Data Applications like Instant Messaging, Interactive Content
Pull, Gaming, and HTTP Video Streaming are used in UE such as Smart Phones.
With increasing use of such applications, UE suffers low battery life time.
So, it is necessary to optimize the power consumption of UE. Therefore, eNB is
required to provide a better power efficient mode of operation.
BENEFIT
Reduction in Power Consumption.
Improvements in System efficiency.

Dependency
Release 11 UE to support UEAssistance Information.
During transmitting UEAssistance message to UE, if UE sets
powerPrefIndication to normal, UE starts or restart timer T340 with the value
of powerPrefIndicationTimer received from eNB during
RRCconnectionReconfiguration message.
The UE should not change the PowerPreferenceMode from Normal to
lowPowerConsumption until the T340 timer expires.
The UE upon initiating RRCConnectionreestablishment procedure, releases
powerPrefIndicationConfig, if configured and stop timer T340, if running.
FEATURE DESCRIPTION
The purpose of RAN Enhancements to Diverse Data Applications is for eNB to
provide UE a power saving operation. Upon configuring UE to provide power
preference indications, eNB waits for UE to provide its power saving preference.
Once the Preference is known from UE, eNB provides appropriate resolution
based on operator's configuration.
This feature is enabled based on the Device Type of UE. If UE DeviceType is set
to noBenFromBatConsumpOpt received from UE in UE-EUTRA-Capability-
v920-IE. Then this feature is disabled as no DRX solution could be provided since
UE does not need a Network Controlled Battery Saving Solution.

If UE DeviceType is not set to noBenFromBatConsumpOpt received from UE in

UE-EUTRA-Capability-v920-IE, then this feature is enabled.
1 If this feature is enabled, eNB configures UE to provide power preference
indication by sending RRC connection reconfiguration message to UE with
powerPrefIndicationConfig data structure set to setup. This configuration
message can be sent during any reconfiguration on the serving cell or in the
reconfiguration message during handover to E-UTRA.
powerPrefIndicationConfig-r11 is present in otherConfig-r9 structure. The
setup parameter part of the powerPrefIndicationConfig contains
powerPrefIndicationTimer-r11 parameter, which is a Prohibit timer for Power
Preference Indication reporting of UE. This prevents from frequent
PowerMode Change (T340 timer) of UE from Normal to Low.
2 The UE responds with RRC connection reconfiguration complete message.
3 The UE further notifies to eNB with its power saving preference by sending
UEAssistanceInformation message with setting either of two possible below
mentioned values
opowerPrefIndication is set to lowPowerConsumption (or)
opowerPrefIndication is set to normal.
The UE start or restart timer T340 with timer value set to the
powerPrefIndicationTimer received from eNB during
RRCconnectionReconfiguration message.
The UE should not change the PowerPreferenceMode from Normal to

lowPowerConsumption until the T340 timer expires.
The UE upon initiating RRCConnectionreestablishment procedure, UE should

release powerPrefIndicationConfig, if configured and stop timer T340, if running;
4 If eNB receives the message with parameter powerPrefIndication set to
olowpowerconsumption, then based on the Operator configuration,
The eNB may respond to UE with either a long value for long DRX
cycle or
Feature/Parameter Configuration Value/Description
DRX Long cycle length 80, 160, 320, 640, 1280, 2560 ms
The eNB may respond to UE with RRC connection release message to
save UE device power consumption.
oNormal, then normal operation resumes.

SYSTEM OPERATION
How to Activate
Execute the CHG-UEPWRSAVING-CONF command to set 'usedFlag' to 'USE'.
The operator can disable this feature by setting the parameter to 'NO_USE'.
Key Parameters
CHG-UEPWRSAVING-CONF/RTRV-UEPWRSAVING-CONF
USED_FLAG This parameter shows whether UE power saving function is supported or not.
PREF_IND_TIMER This parameter shows Prohibit timer (T340) for Power Preference Indication
reporting. Value in seconds. Value s0 means prohibit timer is set to 0 second
or not set, value s0dot5 means prohibit timer is set to 0.5 second, value s1
means prohibit timer is set to 1 second and so on
SUPPORT_METHOD This parameter shows the method to support UE power saving.
CHG-UEPWRSAVING-DRXINFO/RTRV-UEPWRSAVING-DRXINFO
QCI This parameter is the QoS Class Identifier (QCI). The range is 0-255.The
standard QCI defined in the standard document is 1-9. 0 and 10-255 can be
used by the operator optionally.
DRX_CONFIG_SETUP This parameter indicates whether to use the DRX for UE power saving.
Release: DRX is not used.
Setup: DRX profile is used
ON_DURATION_TIMER This parameter is onDurationTimer to monitor PDCCH in DRX mode.
(onDurationTimer-Specifies the number of consecutive PDCCH-subframe(s) at
the beginning of a DRX Cycle.)

DRX_INACTIVITY_TIMER This parameter is drxInactivityTimer to monitor PDCCH in DRX mode. (drx-
InactivityTimer - Specifies the number of consecutive PDCCH-subframe(s)
after successfully decoding a PDCCH indicating an initial UL or DL user data
transmission for this UE.)
DRX_RETRANSMISSION_T This parameter is drxRetransmissionTimer to monitor PDCCH in DRX mode.
IMER (drx-RetransmissionTimer - Specifies the maximum number of consecutive
PDCCH-subframe(s) for as soon as a DL retransmission is expected by the
UE.)
LONG_DRXCYCLE_START The long DRX cycle and drx start offset values to run onDurationTimer in DRX
_OFFSET_TYPE mode. For UE power saving, longDRCCycle can have multiples of sf80.
Counters and KPIs

There are no related counters or KPIs.
REFERENCE
description; Stage 2. Release 11
[2] 3GPP TS36.331 Evolved Universal Terrestrial Radio Access (E-UTRA); RRC
Control and Signalling. Release 11
[3] 3GPP TR 36.822 LTE Radio Access Network (RAN) enhancements for
diverse data applications. Release 11

LTE-SW0315, Extended Access Barring (SIB14)

INTRODUCTION
During network congestion, core Network will not be able to allocate backhaul
resources for all UE's. So, an overload control mechanism is required. Extended
Access Barring (EAB) bars low priority UE's such as MTC from accessing the
network during RAN overload period. These UE's are affected by relatively lesser
importance. To Support EAB, barring information is transmitted in SIB14 which is
broadcasted to UEs.
BENEFIT
Provides RAN overload control and overload control for shared RANs.
Provides Core Network Overload Control.

Dependency
Release 11 UE
Related Features
LTE-SW4105 Access Class Barring
FEATURE DESCRIPTION
Due to diverse applications and services deployed in LTE network, there could be
excess traffic resulting due to use of these applications and services. So, it is
necessary to mitigate E-UTRAN access during peak traffic. The peak traffic could
be from both core and access network. In case of core network, MME signaling or
O&M can trigger E-UTRAN to initiate EAB (From TS 23.401 Section 4.3.17.2
Point (d)). Also, peak traffic could be reduced by refraining low-priority UEs such
as MTC devices to having access to eNB. 3GPP Release 11 features provides
enhancements to GPRS to achieve this. This feature is Extended Access Barring.
During Peak Traffic, eNB reaches congestion state.
The MME notifies to eNB about the congestion state. The eNB can initiate EAB
when all MMEs connected to eNB request to restrict the load for UEs that are
connected to the network with low access priority. It is achieved through
OVERLOAD START message sent from MME to ENB. (From TS 23.401
Section 4.3.7.4.1).

When the congestion state has reached, eNB applies EAB. The EAB is access-
control mechanism, which is derived from the existing Access Class Barring
(ACB) method based on Access Class .In this mechanism, UE determines whether
it is subject to barring based on EAB information (present in SIB14 message) from
eNB. If UE in IDLE state determines that is subjected to barring, it refrains from
sending a connection-request message. The EAB parameters are conveyed through
SIB14 broadcast. To determine whether access barring applies, eNB provides the
following EAB information in SIB14 broadcast.
Access Class's bitmap information targetted by EAB.
UE category targeted by EAB.
Core-eNB Overload Indication:
In case of eNB to find the exact traffic area EAB to applied during Core Network
Overload, following action is taken.
If GUMMEI List IE is present in the received Overload START message, eNB
shall, if supported, use this information to identify to which traffic the above
defined rejections shall be applied. If an overload action is ongoing and eNB
receives a further OVERLOAD START message, the eNB shall replace the
ongoing overload action with newly requested one. [36.413 Section 8.7.6.2]

EAB Evaluation, UE and ENB Impact

UE Acquires SIB14 when:
oUpon receiving a PAGING message from eNB, identifies EAB Parameters
modification.
oIf it does not have stored a valid version of SIB14 upon entering RRC_IDLE.
The eNB should set SIB14 Flag as TRUE when sending SIB1 to indicate it as
present.
UE's access is denied if all the below mentioned conditions are true:
oUE belongs to access class (0- 9).
oUEs category is same as the category received in SIB14.
oUE's access class is same as access class received in SIB14.
The EAB is removed by eNB through SIB14 specifying as not Barred when eNB
receives OVERLOAD STOP from MME.
SYSTEM OPERATION
How to Activate
To change EAB activation, execute the CHG-SIB-INF/CHG-EAB-PARA
command to configure the parameters (SIB 14).

Key Parameters
CHG-SIB-INF/RTRV-SIB-INF
CELL_NUM This parameter is the number of cells. This value must not exceed the
maximum number of cells supported by the system. It is determined by
FA/Sector. For example, if the maximum capacity provided to the carrier per
system is 1 FA/3 Sector, up to 3 cells are supported.
sib14Period This parameter is the broadcast interval for SIB 14.
not_used: Does not broadcast SIB14.
CHG-EAB-PARA/RTRV-EAB-PARA
eabParamUsage This parameter is the usage flag of EAB barring status.
Counters and KPIs

REFERENCE
description; Stage 2. Release 11
Resource Control (RRC) protocol specification. Release 11
[3] 3GPP TS36.413 Evolved Universal Terrestrial Radio Access (E-UTRA); S1
Application Protocol (S1AP). Release 11
[4] 3GPP TS22.368 Service requirements for Machine-Type Communications
(MTC). Release 11
[5] 3GPP TS23.401 General Packet Radio Service enhancements for Evolved
Universal Terrestrial Radio Access Network. Release 11

LTE-SW0321, UE Context Management

INTRODUCTION
The eNB maintains UE contexts while UEs are in the RRC_CONNECTED state,
and supports Initial Context Setup, UE Context Release, and Modification
according to requests from MME.
BENEFIT
The operator can maintain UE context for its subscribers in the
RRC_CONNECTED state.

Limitation:
Need UE IOT for security context modification.
FEATURE DESCRIPTION
Initial Context Setup

The eNB performs Initial Context Setup procedures when it receives INITIAL
CONTEXT SETUP REQUEST message from MME. Initial Context Setup
procedures are used for call setup. The eNB creates UE context for UE so that it
can process UE associated signaling and data transmission/reception. On receiving
INITIAL CONTEXT SETUP REQUEST message from MME, eNB determines
whether the call setup is possible or not, based on the status of resources at that
moment. If there are available resources, eNB performs RRC Connection
Reconfiguration procedures with UE for resource reconfiguration and transmits
INITIAL CONTEXT SETUP RESPONSE to MME, according to 3GPP TS36.413.
Usually, Initial Context Setup procedures include E-RAB setup procedures.
The UE initiated Service Request triggers Initial Context Setup procedure is as
follows:

The UE performs the random access and RRC connection establishment

procedures with eNB for call setup.
1 The eNB transmits the Initial UE message to MME to establish the connection.
The NAS message received from UE and SERVICE REQUEST are included
in this message.
oThe eNB uses eNB-UE-S1AP-ID to uniquely identify UE
oThe EPS attach type may be EPS Attach (or) Combined EPS/IMSI Attach.
oThe UE Identity is specified is IMSI (If UE is not registered with the
network) and Old GUTI (Subsequent attach requests identify the UE with
the Old GUTI).
2 If necessary, the NAS security setup or authentication procedures are performed.
3 The MME transmits the Initial Context Setup request to eNB. Information
required for E-RAB(s) setup, UE contexts required by eNB to control UE, the
NAS message to be sent to UE and SERVICE ACCEPT are included in the
Initial Context Setup request.
oS1AP Initial Context Setup Request: Contains a request to establish a context
between MME-eNB and the message containing SGW tunneling
information.

oNAS Attach Accept: Message acknowledges the successful Attach to UE,

eNB will pass this message to UE.
oActivate Default Bearer Request: Message initiates the default bearer setup
on UE and eNB will pass this message to UE.
4 The eNB determines whether call setup is possible based on the information
received from MME. If possible, it performs the AS security activation
procedure with UE.
5 The eNB reallocates internal resources for DRB(s) setup and transmits RRC
Connection Reconfiguration to UE.
6 The UE sets up the additional DRB(s) specified by RRC Connection
Reconfiguration and responds to eNB with RRC Connection Reconfiguration
Complete.
7 The eNB responds to MME with the Initial Context Setup response. Setup
success/failure results for each E-RAB are included in the Initial Context
Setup response. If eNB detects a failure in the path to the SGW, it responds to
the MME with Initial Context Setup Failure message, where the cause value is
'Transport Resource Unavailable'.
oThis message confirms establishment of GTP tunnel on the S1-U Interface.
oThe message contains information about the RABs that are being established
at startup.
oEach RAB will have an E-RAB ID, transport layer IP address on eNB and
eNB GTP Tunneling ID (TEID) for eNB side.
8 The MME performs the Modify Bearer procedure with S-GW/P-GW.
When the path between eNB and Serving GW is in failure state, eNB responds
with INITIAL CONTEXT SETUP FAILURE message instead of INITIAL
CONTEXT SETUP RESPONSE message. It makes MME to disconnect the call of
UE.
UE Context Modification
The eNB performs the context modification procedure upon MMEs request.
It can change the security context, UE AMBR, and SPID through UE context
modification procedure. When receiving UE Context Modification request from
MME, the eNB changes UE context using the value included in the message and
transmits UE Context Modification response to MME. If the security context was
changed, it performs the RRC Connection Reconfiguration procedure with UE and
then responds to MME.
It uses UE context modification procedure to change UE context of the connected
UE.
The following UE contexts can be changed through UE context modification
procedure:
UE Aggregate Maximum Bit Rate (UE AMBR)
UE Security Capabilities

Security Key
Subscriber Profile ID for RAT/Frequency priority (SPID)
CSG Membership Status
Registered LAI
The UE context modification procedure is as follows:
If HSS initiated UE context modification procedure, HSS performs the subscriber

data modification procedure with MME.
1 If UE context modification is required, MME transmits the Context Modification
request to eNB.
2 The eNB changes UE context based on the information included in UE Context
Modification Request message and transmits UE Context Modification
Response message to MME. If the security context was changed, it performs
the RRC Connection Reconfiguration procedure with UE and responds to
MME.
UE Context Release
The eNB performs UE context release procedure upon MMEs request. The UE
context release procedure is used for releasing a call from the connected UE. The
MME initiated UE context release is performed based on MMEs decision or eNB
initiated UE context release is performed upon the request from the eNB. When
receiving UE Context Release Command message from MME, the eNB performs
the RRC Connection Release procedure with UE and transmits UE Context
Release Complete message to MME.
The UE context release procedure is used for call release (active-to-idle transition).
The UE context release procedure is as follows:

If eNB initiated UE context release procedure, then eNB transmits UE Context

Release request to MME to request for call release.
1 If S1 release is necessary, MME performs the Release Access Bearer procedure
with S-GW.
2 The MME transmits UE Context Release command to eNB for S1 release.
3 The eNB transmits RRC Connection Release to UE.
4 The eNB performs the RRC Connection Release procedure with UE and
responds to MME with UE Context Release Complete.
SYSTEM OPERATION
How to Activate
Key Parameters
CHG-SECU-INF/RTRV-SECU-INF
INTEGRITY_EA_PRIOR The integrity protection algorithm supported
by the eNB
EIA0: NULL
EIA1: SNOW 3G
EIA2: AES
CIPHER_EA_PRIOR The ciphering algorithm supported by the
eNB
EEA0: NULL
EEA1: SNOW 3G
EEA2: AES

Counters and KPIs

Name
ERAB_ESTAB EstabInitAttNbr INITIAL CONTEXT SETUP REQUEST count
EstabInitSuccNbr INITIAL CONTEXT SETUP RESPONSE count
ErabInitFailNbr_CP_CC_ Initial E-RAB setup fails due to call control timeout in the
TO protocol blocks (MAC, RLC, PDCP, GTP)
ErabInitFailNbr_CP_CC_ Initial E-RAB setup fails due to reset notification (eNB failure
FAIL or block restart) from ECMB or by the ECCB block
ErabInitFailNbr_UP_GTP Initial E-RAB setup fails due to the failure in the GTP block
_FAIL
ErabInitFailNbr_UP_MA Initial E-RAB setup fails due to the failure in the MAC block
C_FAIL
ErabInitFailNbr_UP_PD Initial E-RAB setup fails due to the failure in the PDCP block
CP_FAIL
ErabInitFailNbr_UP_RLC Initial E-RAB setup fails due to the failure in the RLC block
_FAIL
ErabInitFailNbr_RRC_SI Initial E-RAB setup fails due to receiving RRC signaling
G_FAIL
ErabInitFailNbr_RRC_SI Initial E-RAB setup fails due to RRC signaling timeout (not
G_TO received)
ErabInitFailNbr_CP_BH_ Initial E-RAB setup fails due to Backhaul QoS based CAC
CAC_FAIL
ErabInitFailNbr_CP_CAP Initial E-RAB setup fails due to Capacity based CAC
A_CAC_FAIL
ErabInitFailNbr_CP_QO Initial E-RAB setup fails due to Air QoS based CAC
S_CAC_FAIL
ErabInitFailNbr_S1AP_C Initial E-RAB setup fails due to the S1AP specification cause
U_FAIL
ErabInitFailNbr_S1AP_LI Initial E-RAB setup fails due to the S1 SCTP link failure
NK_FAIL
ErabInitFailNbr_S1AP_S Initial E-RAB setup fails due to receiving S1AP signaling
IG_FAIL
ERAB_ERASE_E EraseAttbyEnb_CP_CC_ eNB initiated UE Context Release fails due to call control
NB TO timeout in the protocol blocks (MAC, RLC, PDCP, GTP)
EraseAttbyEnb_CP_CC_ eNB initiated UE Context Release fails due to reset
FAIL notification (eNB failure or block restart) from ECMB or by the
ECCB block
EraseAttbyEnb_UP_GTP eNB initiated UE Context Release fails due to the failure in
_FAIL the GTP block
EraseAttbyEnb_UP_MA eNB initiated UE Context Release fails due to the failure in
C_FAIL the MAC block
EraseAttbyEnb_UP_MA eNB initiated UE Context Release fails due to user inactivity
C_UE_INACT
EraseAttbyEnb_UP_PD eNB initiated UE Context Release fails due to the failure in
CP_FAIL the PDCP block
EraseAttbyEnb_UP_RLC eNB initiated UE Context Release fails due to the failure in
_FAIL the RLC block
EraseAttbyEnb_RRC_H eNB initiated UE Context Release fails due to HO preparation
C_TO timeout (not received HO command)


Name
EraseAttbyEnb_RRC_SI eNB initiated UE Context Release fails due to receiving RRC
G_FAIL signaling
EraseAttbyEnb_RRC_SI eNB initiated UE Context Release fails due to RRC signaling
G_TO timeout (not received)
EraseAttbyEnb_S1AP_C eNB initiated UE Context Release fails due to the S1AP
U_FAIL specification cause
EraseAttbyEnb_S1AP_R eNB initiated UE Context Release fails due to the S1AP
O_TO relocoverall timeout (not received)
EraseAttbyEnb_S1AP_S eNB initiated UE Context Release fails due to S1AP signaling
IG_TO timeout (not received)
EraseAttbyEnb_X2AP_R eNB initiated UE Context Release fails due to the X2AP
O_TO relocoverall timeout (not received)
ERAB_ERASE EraseAtt UE CONTEXT RELEASE COMMAND count
EraseSucc UE CONTEXT RELEASE COMPLETE count
ERAB_TIME EstabTimeAvg Average time of Initial E-RAB set-up and additional E-RAB
setup
EstabTimeMax Max. time of Initial E-RAB set-up and additional E-RAB setup
EstabTimeTot Total time of Initial E-RAB set-up and additional E-RAB setup
EstabTimeCnt Counts of Initial E-RAB set-up and additional E-RAB setup
ERAB_SESSION SessionTimeUEAvg Average In-Session time
_UE
SessionTimeUETot Total In-Session time
SessionTimeUECnt Counts of In-session time
S1SIG S1ConnEstabAtt INITIAL UE MESSSAGE count
S1ConnEstabSucc INITIAL CONTEXT SETUP REQUEST count
S1ConnEstabFail_CpCc S1 Connection Establishment fails due to reset notification
Fail (eNB failure or block restart) from ECMB or by the ECCB
block
S1ConnEstabFail_S1ap S1 Connection Establishment fails due to the S1AP
CuFail specification cause
S1ConnEstabFail_S1apL S1 Connection Establishment fails due to the S1 SCTP link
inkFail failure
S1ConnEstabFail_S1ap S1 Connection Establishment fails due to receiving S1AP
SigFail signaling
S1ConnEstabFail_S1ap S1 Connection Establishment fails due to S1AP signaling
SigTo timeout (not received)
REFERENCE
Resource Control (RRC); Protocol specification
[3] 3GPP TS36. 413 Evolved Universal Terrestrial Access Network (E-UTRAN);
S1 Application Protocol (S1AP)

LTE-SW0322, E-RAB Management

INTRODUCTION
The ERAB is a bearer connection between eNB and Serving GW. The MME
initiates E-RAB setup, modification, and release procedures, and it also can
request eNB to modify E-RAB QoS characteristics. The eNB support all those
procedures according to 3GPP TS36.413.
Once eNB and MME setup an E-RAB connection, eNB and S- GW can transmit
user packets unlink and downlink through GTP tunnel. They distinguish each E-
RAB bearer by Tunnel Endpoint Identifier (TEID).
BENEFIT
The operator can provide EPS bearer service to its subscribers and manage E-RAB
resources for user data transport.

N/A
FEATURE DESCRIPTION
E-RAB Setup
The E-RAB setup procedure is used to add an E-RAB for a new service to a
connected UE. The E-RAB for a new service can be added to the connected UE
through E-RAB setup procedure. When receiving the E-RAB Setup Request
message from MME, the eNB considers the current resource usage status and
determines whether a new bearer can be added. If a new E-RAB can be added,
eNB performs the RRC Connection Reconfiguration procedure with UE for
resource reconfiguration of the new DRB and transmits the E-RAB Setup
Response message to MME.
Each E-RAB will have the following information:
E-RAB ID
The Transport Layer IP Address on the eNB
The eNB GTP Tunneling ID (TEID) for the eNB side.
QCI to assign session priority.
The maximum bit rate for the E-RAB.
Guaranteed bit rate for the eRAB.
The E-RAB setup procedure is as follows:

1 The P-GW transmits the Create Bearer request to S-GW to add the new E-RAB.
2 The S-GW transmits the Create Bearer request to add the new E-RAB.
3 The MME transmit the E-RAB Setup request to start the E-RAB setup procedure.
QoS information of the E-RAB(s) to be added, the NAS message to be sent to
UE, and ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
are included in the E-RAB Setup request.
4 When receiving the E-RAB Setup request from MME, the eNB determines
whether a new E-RAB(s) can be added. If possible, eNB reallocates internal
resources and transmits RRC Connection Reconfiguration to UE.
5 The UE adds the new DRB(s) specified by RRC Connection Reconfiguration
and replies to eNB with RRC Connection Reconfiguration Complete.
6 The eNB responds to MME with the E-RAB Setup response. Setup
success/failure results for each E-RAB are included in the E-RAB Setup
response.
7 The UE transmits the NAS message and ACTIVATE DEDICATED EPS
BEARER CONTEXT RESPONSE.
8 The eNB transmits the NAS received from UE to MME.
9 The MME transmits the Create Bearer response to S-GW.
10 The S-GW transmits the Create Bearer response to P-GW.

E-RAB Modification
Use the E-RAB modification procedure to change the QoS setting of a bearer (E-
RAB) already in service. To use the E-RAB modification procedure, operator can
change UE AMBR for non-GBR bearer and E-RAB Level QoS parameters (QCI,
ARP and GBR QoS Information) for GBR bearer.
The E-RAB modification procedure is as follows:
1 The P-GW transmits Update Bearer Request to S-GW to change QoS setting.
2 The S-GW transmits Update Bearer Request to MME to change QoS setting.
3 The MME starts the E-RAB modification procedure by transmitting E-RAB
Modify Request to eNB. The E-RAB Modify Request has the QoS information
of E-RAB(s) to change, NAS message to send to UE, and MODIFY EPS
BEARER CONTEXT REQUEST.
4 When eNB receives E-RAB Modify Request from MME, it selects if it is
possible to change the QoS setting of the E-RAB(s). If possible, it re-allocates
internal resources and transmits RRC Connection Reconfiguration to the MS.
5 The MS changes the QoS setting of DRB(s) that is specified in RRC Connection
Reconfiguration and replies RRC Connection Reconfiguration Complete to
eNB.

6 The eNB replies E-RAB Modify Response to MME. The E-RAB Modify
Response has the success or failure of QoS setting change per E-RAB.
7 The UE transmits NAS message, MODIFY EPS BEARER CONTEXT
RESPONSE.
8 The eNB transmits the NAS message received from UE to MME.
9 The MME transmits Update Bearer Response to S-GW.
10 The S-GW transmits Update Bearer Response to P-GW.
E-RAB Release
The E-RAB release procedure is used to release specific bearer service of a
connected UE. This procedure is performed by request from MME. Also, MME
requests E-RAB release based on its own decision (MME initiated E-RAB release)
or as following action after an indication from eNB (eNB initiated E-RAB release).
When E-RAB RELEASE REQUEST message is received from MME, eNB
performs RRC connection reconfiguration procedure with UE to release the
corresponding DRB (data radio bearer). When the DRB is released successfully,
eNB returns E-RAB RELEASE RESPONSE message to MME.
The E-RAB release procedure is as follows:

If eNB initiated E-RAB release procedure, eNB transmits the E-RAB Release
indication to MME to notify the release of a specific E-RAB. The MME transmits
the Delete Bearer command to S-GW for E-RAB release.
1 The S-GW transmits the Delete Bearer command for E-RAB release. The P-GW
transmits the Delete Bearer request to S-GW for E-RAB release.
2 The S-GW transmits the Delete Bearer request to MME for E-RAB release.
3 The MME initiates the E-RAB release procedure by transmitting the E-RAB
Release command. ID(s) of the E-RAB(s) to be released, the NAS message to
be sent to UE and DEACTIVATE EPS BEARER CONTEXT REQUEST are
included in the E-RAB Release command.
4 When receiving the E-RAB Release command from MME, eNB transmits RRC
Connection Reconfiguration to UE.
5 The UE releases the DRB(s) specified by RRC Connection Reconfiguration and
then replies to eNB with RRC Connection Reconfiguration Complete.
6 The eNB responds to MME with the E-RAB Release response.
7 The UE transmits the NAS message and DEACTIVATE EPS BEARER
CONTEXT RESPONSE.
8 The eNB transmits the NAS received from UE to MME.
9 The MME transmits the Delete Bearer response to S-GW.
10 The S-GW transmits the Delete Bearer response to P-GW.
SYSTEM OPERATION
How to Activate
In case of standard QCI E-RABs, there is no additional activation procedure
required but to activate operator specific QCIs, execute the CHG-QCI-VAL
command to equip new QCIs to be used.
Key Parameters
QCIs can be configured by executing the CHG-QCI-VAL command with
following parameters:
QCI QoS Class Identifier (QCI) index. The range is from 0 to 255. The QCI defined in
the standard is 1 to 9.
The user can use QCI values 0 and 10-255.
STATUS Whether the QoS Class Identifier (QCI) is used.
EQUIP: The QCI is used in the eNB.
N_EQUIP: The QCI is not used in the eNB.

Counters and KPI

Name
ERAB_ESTAB_A EstabAddAttNbr ERAB SETUP REQUEST count
DD
EstabAddSuccNbr ERAB SETUP RESPONSE count
ErabAddFailNbr_CP_CC_ E-RAB setup fails due to call control timeout in the protocol
TO blocks (MAC, RLC, PDCP, GTP)
ErabAddFailNbr_CP_CC_ E-RAB setup fails due to reset notification (eNB failure or
FAIL block restart) from ECMB or by the ECCB block
ErabAddFailNbr_UP_GTP E-RAB setup fails due to the failure in the GTP block
_FAIL
ErabAddFailNbr_UP_MAC E-RAB setup fails due to the failure in the MAC block
_FAIL
ErabAddFailNbr_UP_PDC E-RAB setup fails due to the failure in the PDCP block
P_FAIL
ErabAddFailNbr_UP_RLC E-RAB setup fails due to the failure in the RLC block
_FAIL
ErabAddFailNbr_RRC_SI E-RAB setup fails due to receiving RRC signaling
G_FAIL
ErabAddFailNbr_RRC_SI E-RAB setup fails due to RRC signaling timeout (not
G_TO received)
ErabAddFailNbr_CP_BH_ E-RAB setup fails due to Backhaul QoS based CAC
CAC_FAIL
ErabAddFailNbr_CP_CAP E-RAB setup fails due to Capacity based CAC
A_CAC_FAIL
ErabAddFailNbr_CP_QOS E-RAB setup fails due to Air QoS based CAC
_CAC_FAIL
ErabAddFailNbr_S1AP_C E-RAB setup fails due to the S1AP specification cause
U_FAIL
ErabAddFailNbr_S1AP_LI E-RAB setup fails due to the S1 SCTP link failure
NK_FAIL
ErabAddFailNbr_S1AP_SI E-RAB setup fails due to receiving S1AP signaling
G_FAIL
ErabAddFailNbr_CP_CC_I E-RAB setup fails due to ongoing inter-eNB handover
NTERACTION
ERAB_REL_ RelAttbyEnbNbr_CP_CC_ eNB initiated E-RAB Release fails due to call control
ENB TO timeout in the protocol blocks (MAC, RLC, PDCP, GTP)
RelAttbyEnbNbr_S1AP_C eNB initiated E-RAB Release fails due to the S1AP
U_FAIL specification cause
ERAB_REL RelAttNbr ERAB RELEASE COMMAND count
RelSuccNbr ERAB RELEASE RESPONSE count
RelFailNbr_CP_CC_FAIL MME initiated E-RAB Release fails due to reset notification
(eNB failure or block restart) from ECMB or by the ECCB
block
RelFailNbr_S1AP_SIG_FA MME initiated E-RAB Release fails due to receiving S1AP
IL signaling
RelFailNbr_S1AP_CU_FAI MME initiated E-RAB Release fails due to the S1AP
L specification cause
RelActive Number of active E-RABs abnormally released by eNB


Name
RelFailNbr_CP_CC_INTE MME initiated E-RAB Release fails due to ongoing inter-
RACTION eNB handover
ERAB_NUM UsageNbr Average number of E-RABs during a time period
UsageNbrMax Maximum number of E-RABs during a time period
REFERENCE

LTE-SW0501, S1 Interface Management

INTRODUCTION
The S1 interface management procedure manages the signaling associations
between eNBs and MME. When eNB starts, it performs S1 setup procedures with
MME according to 3GPP TS36.413, and it manages the connection by exchanging
Keep Alive, S1 Reset, eNB/MME Configuration Update, and Error Indication
message.
The S1 interface management also include path management between eNB and
SGW. Once eNB and MME setup an E-RAB connection, eNB and S-GW can
transmit user packets unlink and downlink through GTP tunnel. They distinguish
each E-RAB bearer by Tunnel Endpoint Identifier (TEID). The eNB supports path
management function as per 3GPP TS29.281.
BENEFIT
The operator can manage the signaling associations between eNB and EPC such
as setting up, resetting S1 interface, and recovering from errors.
This feature provides path monitoring between eNB and SGW

Limitation
The eNB can connect to up to 16 MMEs at the same time.
The eNB can communicate with any SGWs informed by MME without the
limitation on the number of SGWs as long as there is IP connectivity between
eNB and SGW.
In some operator's network, IPsec tunnelling is used between eNB and SeGW. S1
signaling and data traffic is delivered from/to EPC through the IPsec tunnel.
FEATURE DESCRIPTION
There are two types of S1 interface:
S1-MME for control plane
S1-U for user plane
The S1-MME includes a direct SCTP connection between eNB and MME. The
eNB must establish single SCTP connection to each MME during initial
configuration phase. Also, SCTP connection is used to manage UE-associated S1-
AP connections and to carry handover related messages, eNB/MME configuration
message, and NAS TRANSPORT messages.

The S1-U is a direct GTP tunnel between eNB and SGW. The GTP tunnel is UE-
associated connection and created when UE attaches to the network. Through the
GTP tunnel, eNB delivers/receives user packets to/from S-GW. The GTP tunnel is
maintained while UE is in active mode and released when UE's state changes to
idle mode.
The following sub-sections describe the method of configure S1-MME and S1-U
interface related parameters and how eNB and MME manages S1 interface via S1-
AP procedures defined in 3GPP TS 36.413.
S1 Setup
The S1 Setup procedure is the first S1AP procedure after a TNL (Transport
Network Layer) association has been made. When this procedure is performed, the
application level configuration data between eNB and MME, if there is, is
removed and replaced with the newly received data. During S1 setup procedure,
eNB sends its basic application level configuration data such as Global eNB ID,
Supported Tracking Area list consisting of PLMN and Tracking Area Code, and
Default paging DRX and MME sends its list of served GUMMEIs, Relative MME
capacity and so on. If eNB initiating the S1 SETUP procedure on (or more) CSG
cell(s), the S1 SETUP REQUEST message shall contain the CSG ID(s) of the
supported CSG(s).
The S1 Setup successful procedure is as follows:
When MME cannot accept S1 Setup request, it should respond with S1 Setup
Failure and appropriate cause value. If S1 Setup Failure message includes Time to
Wait IE, eNB shall wait at least for the indicated time before reinitiating the S1
Setup towards the same MME.
If eNB fails to receive the S1 Setup Response message within certain amount of
time configured by S1_SETUP timer, it retransmits the S1 Setup Request again to
MME.
Note that the S1 management interface is essential for LTE service, there is no
retry count. It means that eNB retransmits S1 Setup Request to MME unlimitedly
until it receives S1 Setup Response successfully from MME.
TheS1 Setup unsuccessful procedure is as follows:

S1 Reset
When an abnormal situation occurs, S1 interface of all or some UEs can be
initialized through reset procedure which runs on S1-C. (However, the application
level configuration data, which was exchanged by S1 Setup procedure, is not
changed.)
The S1 Reset procedure is executed over S1-C interface which is a control plane
interface of S1. The eNB sends the Reset Acknowledge message to MMEs after
receiving the Reset message and then sends the RRC Connection Release message
to the target UEs. After that, UE related resources, which are controlled by eNB,
are released.
The S1 Reset MME triggered procedure is as follows:
Another example of S1 Reset is when eNB selects a specific S/W or H/W module
is in an abnormal state and unable to provide the normal service, which has
resulted in the loss of some or all transaction reference information, it sends the
Reset message to the MME.
When Samsung eNB determines the cell is not normal any more due to Channel
Card, DSP or RF unit, it sends S1 Reset to MME. The list of UEs, whose resources
should be released, can be specified by MME UE S1AP ID IE or eNB UE S1AP
ID IE of the UE-Associated logical S1-connection list IE in S1 Reset message.

Note that MME UE S1AP ID uniquely identifies a connected UE association

among many UE associations within MME and eNB UE S1AP ID does in the
same way within eNB. Hence, by informing these IDs to MME or eNB, MME or
eNB can easily identify which UEs are impacted by this Reset message and
releases them.
The S1 Reset eNB triggered procedure is as follows:
If eNB fails to receive the S1 Reset Acknowledge message within certain amount
of time configured by s1Reset timer, it retransmits the S1 Reset message again to
MME upto s1ResetRetryCount times.
Unlike Reset by MME, eNB does not send RRC Connection Release to UE right
after Reset if Reset is triggered by eNB. The reason is that in case of Reset by eNB,
the eNB is in an abnormal state and may not be able to send RRC Connection
Release to the corresponding UEs correctly. Hence, instead of sending RRC
Connection Release to UEs right away, the eNB relies on each UEs failure
detection mechanism such as Radio Link Failure (RLF) detection.
When UE detects RLF due to eNBs reset, it tries to send RRC Connection
Reestablishment request to eNB and if eNB is able to accept this request, the
connection continues. If it fails after several times of retries, UE will release RRC
connection by itself and goes to Idle. Later when RRC connection is needed, UE
will send RRC Connection Request to create new RRC connection.
Error Indication
When the received message cannot be processed normally and cannot be
responded with the appropriate failure message, eNB or MME can report this fact
to the peer with Error Indication procedure.
Currently, Samsung eNB sends Error Indication only when it fails to decode the
received messages. It means whenever eNB selects that it is impossible to parse
and interpret the bit stream of the received message, it sends the Error Indication
with Cause IE, however, it does not send Error Indication in case of sematic error
or logical errors and so on. For example, if eNB successfully decodes the received
message and it turns out to have a value out of range, eNB does not send Error
Indication and instead, discards or ignores the received IE or message.
In case the Error Indication procedure is triggered by utilising UE associated

signalling 'MME UE S1AP ID' and 'eNB UE S1AP' shall be included in the
ERROR INDICATION message as below procedure. Otherwise, the Error
Indication does not include 'MME UE S1AP ID' and 'eNB UE S1AP ID'.
The Error Indication eNB originated procedure is as follows:
The Error Indication MME originated procedure is as follows:
eNB Configuration Update

When eNB needs to update the application level data impacting UE-related context,
eNB can send eNB Configuration Update message to MME with which eNB has
an established S1 connection currently.
If the current TAC, eNB Name, or DefaultPagingDRX value set in the PLD is
changed during system operation, eNB includes not only the changed parameter
values but also the unchanged parameter values in eNB Configuration Update
message, and sends it to MMEs.
At this time, eNB must send the message to all MMEs with S1 Setup established.
When eNB Configuration Update message is sent, a timer starts configured by
s1Update and eNB expects eNB Configuration Update Acknowledge message to
be received before the timer expires.
When MME cannot accept eNB Configuration Update request, it shall respond
with eNB Configuration Update Failure and appropriate cause value. If eNB
Configuration Update Failure message includes the Time to Wait IE, eNB shall
wait at least for the indicated time before reinitiating the eNB Configuration
Update towards the same MME.
Both eNB and MME shall continue to operate the S1 with their respective
configuration data. If eNB configuration update acknowledge message is not
received before the s1Update timer expires, eNB kills the timer, resends the eNB
configuration update message upto S1_UPDATE_RETRY_COUNT times. If the
supported CSG ID(s) is/are to be updated in CSG or hybrid cell, the whole loss of
supported CSG IDs, including those that are not to be updated, shall be included in
the CSG Id List IE. The MME shall overwrite the whole list of CSG IDs

The eNB Configuration Update successful procedure is as follows:
The eNB Configuration Update unsuccessful procedure is as follows:
MME Configuration Update

Similar to eNB Configuration Update, when MME needs to update the application
level data impacting UE-related context, MME can send MME Configuration
Update message to eNB with which eNB has an established S1 connection
currently.
If the current TAC, CSGID, eNBName, or DefaultPagingDRX value set in the
PLD is changed during system operation, MME includes not only the changed
parameter values but also the unchanged parameter values in MME Configuration
Update message, and sends it to eNBs.
At this time, MME must send the message to all eNBs with S1 Setup established.
When MME Configuration Update message is sent, MME starts a timer
configured by S1AP timer and expects an MME Configuration Update
Acknowledge message from eNB before the timer expires.
Note that there is no retransmission for MME Configuration Update and thus, if
MME configuration update acknowledge message is not received before the timer
expires, MME kills the timer and MME configuration procedure is stopped.
Therefore, both eNB and MME shall continue to operate the S1 with their
respective configuration data.

If eNB sends MME Configuration Update failure, then there might be mismatch in
the Relative MME Capacity between MME and eNB. In some cases, eNB selects
MME according to the old Relative MME Capacity.
The MME Configuration Update successful procedure is as follows:
The MME Configuration Update Unsuccessful procedure is as follows:
Keep Alive between eNB and MME
The SCTP parameter names of the below description is used conceptually. Refer to
COM-IP0401 for exact SCTP parameter names of S1 interface.
The eNB and MME can monitor S1-MME connection by exchanging SCTP
HEARTBEAT/ HEARTBEAT ACK messages defined by SCTP protocol. The
HEARTBEAT message is periodically transmitted and the period is configured as
HEART_BEAT_INTERVAL. When transmitting HEARTBEAT message, eNB
delivers the current time in the Heartbeat Information field, which is also included
in the HEARTBEAT ACK message so that the sender and receiver can calculate
the Round Trip Time (RTT).
The Keep Alive between eNB and MME successful procedure is as follows:

When HEARTBEAT ACK message is not received, eNB tries to retransmit

HEARTBEAT message periodically. The maximum number of retransmission is
configured as NUM_PATH_RE_TX.
The period of retransmission is Heartbeat Retransmission Interval in the below
figure and calculated as HEART_BEAT_INTERVAL + RTO + RTO*[-0.5, 0.5],
where RTO is increased as exponential backoff if the previous HEARTBEAT
message is unanswered. The initial, minimum and maximum values are configured
as RTO_INITIAL, RTO_MIN, and RTO_MAX.
When HEARTBEAT ACK is not received after all the retransmission, the link
status is considered as abnormal. If MME SCTP connection is considered as
abnormal, MME_FAILOVER_TIMER is triggered and the call is not released
when the SCTP connection is restored before the timer expiry. However, when
MME_FAILOVER_TIMER expires, all active calls on the SCTP Connection are
released and MME_COMMUNICATION_FAIL alarm is generated. Note that,
eNB does not manage Idle calls.
While MME_COMMUNICATION_FAIL alarm is ON, eNB routes new call
attempts to another alive MMEs via S1-flex. For example, when there are three
MMEs (MME1, MME2, MME3), eNB normally maintains three S1 interfaces,
one for each MME1, MME2 and MME3 and distributes calls among them. In case
S1 interface to MME1 fails, eNB routes new call attempts to two remaining
MMEs (MME2 and MME3).
The Keep Alive between eNB and MME unsuccessful operation procedure is as
follows:

In case of S1 setup procedure, eNB transmits INIT message to establish SCTP

association. If it fails to get the response of INIT ACK message, eNB transmits
INIT message once again after one second. If it is not answered also, eNB repeats
this procedure with the period of CONNECT_INTERVAL until SCTP setup is
successful as described in the below figure.
The SCTP Setup between eNB and MME unsuccessful procedure is as follows:

Path Management between eNB and S-GW

According to 3GPP TS 29.281, eNB and S-GW can monitor S1-U path using
ECHO REQUEST/ECHO RESPONSE messages defined by GTP-U protocol.
Here, S1-U Path means a logical connection between eNB and S-GW. In other
words, only single S1-U Path exists between a certain eNB and a certain S-GW
even though there may be many S1 bearers between them. Hence, eNB manages
only one S1-U path for each S-GW by sending an Echo Request to find out if it is
alive.
The following figure shows path management procedures between eNB and three
S-GW, successful operation. In this case, there are three S1-U paths and for each
path, eNB sends the ECHO REQUEST message to S-GW periodically and waits
for ECHO RESPONSE message.
If eNB fails to receive the ECHO RESPONSE message, it resends the ECHO
REQUEST message up to the configured maximum retransmissions
N3_REQUEST. When eNB fails to receive the ECHO RESPONSE message even
after maximum resending, it will release all E-RAB connections with the failed S-
GW and triggers MME to release the related calls via S1-Reset procedure.
The Keep Alive between eNB and S-GW unsuccessful procedure is as follows:

SYSTEM OPERATION
How to Activate
Execute the CHG-MME-CONF command to configure MME by adding IP address
and set the status to be Equip and unlock active state of the corresponding MME.
Key Parameters
CHG-MME-CONF/RTRV-MME-CONF
MME_INDEX The index used to access the information. Since there are a total of 16 MMEs
that can be connected to an eNB, the index range is 0 to 15.
STATUS The EQUIP status information on MME.
N_EQUIP: The MME to connect does not exist.
EQUIP: The MME to connect exists
ACTIVE_STATE The state information on the specified MME in operation. The MMEs for which
the S1 Setup is established, if there is an undesired MME, this parameter
value must be changed to Inactive. The default is active. If the STATUS
parameter is set to Equip, it is better not to change this parameter value to
inactive.
Inactive: MME (S1 assigned) is not used.
Active: MME (S1 assigned) is used.
IP_VER The IP address version of MME. Either IPv4 or IPv6 is assigned.
MME_IPV4 Information on the IPV4 address of MME. This parameter value is valid only if
the IP_VER parameter is set to IPv4. It is not used if the IP_VER parameter is
set to IPv6.

MME_IPV6 Information on the IPV6 address of eNB. This parameter value is valid only if
the IP_VER parameter is set to IPv6. It is not used if the IP_VER parameter is
set to IPv4.
ADMINISTRATIVE_STATE The status of MME link:
Locked: A state where active calls connected to MME are all dropped, and
new call connections are not possible.
Unlocked: Connection to MME is normal.
Shutting down: A state where active calls connected to MME are maintained,
but new call connections are not possible.
SECONDARY_MME_IPV4 The secondary IP address of the IPv4 type set in MME node to support the
SCTP Multi Homing function. It is valid only if the IP_VER parameter is set to
IPv4.
This is for SCTP multi-homing

SECONDARY_MME_IPV6 The secondary IP address of the IPv6 type set in MME node to support the
SCTP Multi Homing function. It is valid only if the IP_VER parameter is set to
IPv6.
This is for IPv6.

S1_TUNNE_GROUP_ID This parameter defines IPSec Tunnel Group ID of MME.
(valid only if IPsec tunnel group function is supported)
Counters and KPIs

REFERENCE
[2] 3GPP TS36.412 Evolved Universal Terrestrial Radio Access Network (E-
UTRAN); S1 signalling transport
UTRAN); S1 Application Protocol (S1AP)
[4] 3GPP TS29.281 General Packet Radio System (GPRS) Tunnelling Protocol
User Plane (GTPv1-U)
[5] IETF RFC4960 Stream Control Transmission Protocol

LTE-SW0510, Geo Redundancy of MME

INTRODUCTION
This feature is a part of S1-flex of 3GPP complaint feature, which allows eNB to
interoperate with multiple MMEs for redundancy and high availability. It enables
operator to configure a pool of active and standby MMEs. The eNB selects a
standby MME for new UEs when all the active MMEs are down.
BENEFIT
The operator can explicitly configure a group of standby MMEs to use only when
all the active MMEs are out of service.
From SLR4.5, the eNB selects standby MMEs based on their Relative MME
Capacity (RMC) values. The operator can control the frequent selection of
certain standby MMEs using their RMC value, thereby increasing the service
availability and reducing OPEX.

The operator must ensure that the following conditions are met when enabling this
feature:
Hardware: No impact
Device: No impact
Interface: The MME must provide the relative capacity information through
S1AP interface for load balancing between MMEs.
Performance: No impact
Capacity: No impact
Pre-requisites: No impact
FEATURE DESCRIPTION
The S1-flex feature of Samsung enables eNB to be connected with a pool of active
and standby MMEs. The eNB sets up a dedicated S1 connection with the active
MME when UE connects to the network. If all the active MMEs are down, S1-flex
provides high availability by allowing eNB to route UE signaling messages to the
standby MME. When the failed MMEs are active and take over the functional role,
eNB establishes the new calls with active MMEs and maintains the ongoing calls
with standby MME.

Samsung eNB can have connections with up to 16 MMEs belonging to any MME
pool. Within 16 MMEs, eNB can be eNB 11 of overlapping area and either eNB
10 of MME Pool Area 1 or eNB 12 of MME Pool Area 2, as shown in the figure
below.
In this scenario:
The eNB 1 to 11 are connected to MME 1, MME 2, and MME 3 from MME Pool
Area 1
The eNB 11 to 16 are connected to MME 4, MME 5, and MME 6 from MME
Pool Area 2
The eNB 11 is at Overlapping Area and is active for both the pools
Selecting Standby MME

The eNB selects the active MMEs based on their RMC and backup mode
configuration. It receives the processing capacity relative to other MMEs from the
serving MME through the RMC IE after setting up the dedicated S1-MME
connection.
Before SLR 3.1, the standby MME method was not included in the feature. To
support the standby MME configuration, the backup mode parameter is introduced
in SLR 3.1. With this parameter, operator can set the backup mode, active or
standby, of MME among the connected MMEs.
In case of backward compatibility, the standby MME selection criteria from
multiple standby MMEs is enhanced.
The following table shows description of each selection criteria introduced after
SLR 3.1:
Software Release Standby MME Condition Standby MME Selection Scenario
Version Criteria
Before SLR 3.1 Before to SLR 3.1 package, Not applicable In the figure above, eNB 11
Samsung eNB does not considers all six MMEs,

Software Release Standby MME Condition Standby MME Selection Scenario

Version Criteria
support the configuration of MME 1 to 6, as equally
standby MME, which active if their RMC value is
implies the eNB cannot greater than zero and S1
continue services if all the SCTP connections are
active MMEs are down. active.
SLR 3.1 The eNB decides whether The eNB selects a standby Refer to !
MME is operating as MME based on the round
standby based on either of robin method among .
these conditions: multiple standby MMEs
BackupMode= Standby whose backup mode is
configured as standby or
RMC= 0
RMC value is equal to zero.
SLR 4.5 The eNB decides whether If there are multiple MMEs Refer to !
MME is operating as that meet the first condition,
standby under the then eNB selects the .
conditions: standby MME among them
At first, eNB checks the based on its RMC value
backup mode of MME is using round robin
standby approach.
If there is no MME that If there is no MME that
meets the first condition, meets the first condition,
then eNB checks the and are only MMEs with
RMC value is zero. RMC value zero, then eNB
uses the round robin
approach to select the
standby MME among them.
Selecting Standby MME in SLR 3.1

The following figure shows a scenario where MME 1, MME 2, and MME 3 are
configured as active while MME 4, MME 5, and MME 6 as standby at eNB 11.
The standby MME is selected among MME 4, MME 5, and MME 6 when all the
active MMEs are down.

Similarly, when there is multiple standby MMEs configured, eNB selects the final
MME among the standby MMEs by round robin method.
The following figure shows a scenario where eNB 11 selects the final standby
MME by round robin approach among the standby MMEs: MME 1, MME 2, and
MME 5 if all active MME 3, MME 4, and MME 6 are down.

Selecting Standby MME in SLR 4.5

The following figure shows a scenario where MME 3, MME 4, and MME 6 are
configured as active while MME 1, MME 2, and MME 5 as standby at eNB 11.
The standby MME is selected by weighted round robin approach among MME 1,
MME 2 and MME 5 when all of MM3, MME4, and MME6 are down.

Selecting Standby MME within MME Pool

This feature can be used to configure standby MMEs within the same MME pool.
The following figure shows a scenario where MME 3 and MME 1 are configured
as standby MME at eNB 1 and eNB 10 respectively belonging to same MME Pool
Area 1. The eNB1 uses MME 3 only when both MME 1 and MME 2 are down and
eNB 10 uses MME 1 only when both MME 2 and MME 3 are down.

Configuring Symmetric Standby MME

Samsung eNB allows configuration of standby MMEs from different MME pools
of other geographical zones. With this type of configuration, operator can set the
standby MMEs for a pool of active MMEs, which are located at different zones.
The following figure shows a typical scenario where MME Pool 1 and MME Pool
2 serve as standby MMEs for each other symmetrically:

SYSTEM OPERATION
How to Activate
To configure specific MME to be a standby MME mode (for geo redundancy
backup-mode), set BACKUP_MODE of corresponding MME to be Standby.
Key Parameters
CHG-MME-CONF/RTRV-MME-CONF (MME Information)
MME_INDEX The index used to access the information. Since there are a total of 16 MMEs
that can be connected to an eNB, the index range is 0 to 15.
STATUS The EQUIP status information on MME.
N_EQUIP: The MME to connect does not exist.
EQUIP: The MME to connect exists

ACTIVE_STATE The state information on the specified MME in operation. The MMEs for which
the S1 Setup is established, if there is an undesired MME, this parameter value
must be changed to Inactive. The default is active. If the STATUS parameter is
set to Equip, it is better not to change this parameter value to inactive.
Inactive: MME (S1 assigned) is not used.
Active: MME (S1 assigned) is used.
BACKUP_MODE This parameter defines MME's backup mode type.
Counters and KPIs

REFERENCE

LTE-SW0521, X2 Interface Management

INTRODUCTION
The X2 interface is used for direct communication of neighbor eNBs and handover
between eNBs. The X2 handover skips the steps comparing to S1 handover and
reduces the total handover time. In addition, it may reduce the HO time
exchanging the HO messages instead of exchanging the handover messages
between eNBs through MME depending on backhaul network structure. Also, the
X2 interface is for exchanging load information between neighbor eNBs.
The X2 interface has control plane and user plane. The control plane connect X2
and AP via the SCTP protocol and make it possible to exchange signaling
messages such as X2 handover, load information, and interference information.
The user plane uses GTP tunnels to forward the user data from the source eNB to
the target eNB at handover.
When a neighbor cell is added to eNB, the eNB automatically sets up X2
connection with eNB which includes the target cell. The IP address of target eNB
is required to set up X2 connection, use the Automatic Neighbor Relation (ANR)
function to find the steps for getting the IP address.
The X2 connection is a SCTP-based between eNBs in the X2 application layer.
The X2 interface management function includes all procedure such as setup and
monitoring the X2 connection, processing errors, and resetting to manage the X2
connection.
BENEFIT
The operator manages the signalling associations between eNBs, surveying X2
interface, and recovering from errors.
Efficient usage of the radio resources can be provided.

Limitation
Maximum 256 X2 connections are supported.
The X2 based handover between Home eNBs is allowed if no access control at
MME is needed.

FEATURE DESCRIPTION
X2 AP Setup
The X2AP setup procedure is for setting up the X2 interface between two eNBs
for the first time. Assuming that eNB 1 triggers X2 setup, the X2 AP setup
procedures for successful case is as follows.
1 The eNB1 sends its global eNB ID, served cell information, neighbor
information, MultibandInfoList, and GU group ID list information to eNB2
using the X2 Setup Request message. (In the perspective of HeNB, eNB 1
shall contain the CSG ID IE in the X2 SETUP REQUEST message for each
CSG or hybrid cell)
2 The eNB2 receives the X2 Setup Request message and stores the information
contained in it in appropriate locations. Then, eNB2 sends its global eNB ID,
served cell information, neighbor information, and GU group ID list
information to eNB1 using the X2 Setup Response message. (In the
perspective of HeNB, eNB2 shall contain the CSG ID IE in the X2 SETUP
RESPONSE message for each CSG cell or hybrid cell. The eNB receiving the
IE shall take this information into account when further deciding whether X2
handover between the source cell and target cell may be performed.)
The X2 AP setup procedure for unsuccessful case is as follows:
Samsung eNB2 sends X2 Setup failures to the eNB1 if:
received PLMN is not supported or
received ECGI is not eNB2's ECGI
1 The eNB1 receives the X2 setup failure message from eNB2.

2 The eNB1 waits as long as Time To Wait as included in the X2 setup failure
message and then resends the X2 setup request message to eNB2.

X2 AP Reset
If an abnormal failure occurs with the X2 interface between two interacting eNBs,
X2AP Reset procedure is performed to reconcile the resources between the two
eNBs.
The X2 AP reset procedure is as follows:
1 The eNB1 sends the X2 Reset Request message to eNB 2.

2 The eNB2 sends the X2 Reset Response message to eNB1. If there are any
procedures which eNB 1 is carrying out via the X2 Interface, eNB2 stops all of
them and performs the Call Release procedure for the call.
Samsung eNB sends X2 Reset Request message to its neighbor eNBs when the
cell of eNB is going to be released.
If eNB1 could not receive X2 Reset Response message, it does not resend X2
Reset Request message and there is no further actions
Keep Alive between eNBs

The eNB and neighbor eNB can monitor X2 connection by exchanging SCTP
HEARTBEAT/ HEARTBEAT ACK messages defined by SCTP protocol.
HEARTBEAT message is periodically transmitted and the period is configured as
HEART_BEAT_INTERVAL. When transmitting HEARTBEAT message, eNB
delivers the current time in the Heartbeat Information field, which is also included
in the HEARTBEAT ACK message so that the sender and receiver can calculate
the Round Trip Time (RTT).
In case of SCTP connection is disconnected, all active calls will be disconnected.
Note that idle mode UEs are not maintained in eNB and HERATBEAT message is
defined by SCTP layer.

When HEARTBEAT ACK message is not received, eNB tries to retransmit

HEARTBEAT message periodically. The maximum number of retransmission is
configured as NUM_PATH_RE_TX. The period of retransmission is Heartbeat
Retransmission Interval in the below figure and calculated as
HEART_BEAT_INTERVAL + RTO + RTO*[-0.5, 0.5], where RTO is increased
as exponential backoff if the previous HEARTBEAT message is unanswered. The
initial, minimum and maximum values are configured as RTO_INITIAL,
RTO_MIN and RTO_MAX. If HEARTBEAT ACK is not received after all the
retransmission, the link status is considered as abnormal.
In case of X2 setup procedure, eNB transmits INIT message to establish SCTP

association. If it fails to get the response of INIT ACK message, eNB retransmits
INIT message after one second. If it goes unanswered, eNB repeats this procedure
with the period of CONNECT_INTERVAL until SCTP setup is successful as
described in the below figure.

The operator could manage the neighbor eNB link status as follows:
locked: Cancels the relevant X2 handover procedure if there is any current X2
handover call, and blocks a new X2 handover out.
unlocked: Normally processes the X2 Handover.
shuttingDown: Normally processes the relevant X2 handover procedure if there is
any current X2 handover call, and blocks a new X2 handover out.
To recover X2 connection, operator can perform the following actions through
LSM. (Refer the detail to the system operation part)
Turn OFF/ON x2 connection with each neighbor eNB manually.
Send SCTP ABORT message only to neighbor eNBs which current X2 status is
enable.
Send SCTP ABORT message to all neighbor eNBs regardless of the current X2
interface status.
SYSTEM OPERATION
How to Activate
Pre-condition
SCTP connection is established and operational state is normal.
Activation
The NO_X2 value must be set to 'False'.
Deactivation
The NO_X2 value must be set to 'True'.

Key Parameters
The maximum number of X2 neighbor eNB is 256 or 512.
The following table shows the several system parameters of each neighbor eNB
information:
CRTE-NBR-ENB/DLT-NBR-ENB/CHG-NBR-ENB/RTRV-NBR-ENB
STATUS This parameter indicates the validity of the neighbor eNB.
N_EQUIP: The information is determined as invalid.
EQUIP: The information is determined as valid.
This parameter must be set accurately since it determines the X2 link and
handover execution.
NO_X2 This parameter determines whether to execute X2 link setup with the neighbor
eNB.
False: X2 link setup with the neighbor eNB is executed.
True: X2 link setup with the neighbor eNB is not performed.
The parameter must be set accurately for X2 link setup to be determined by the
setting.
NO_HO This parameter determines whether HO is possible with the neighbor eNB.
False: Handover is done with the neighbor eNB.
True: Handover is not done with the neighbor eNB.
The parameter must be set accurately for Handover to be executed as
determined by the setting.
ENB_ID This parameter indicates the eNB ID of the neighbor eNB to which the neighbor
cell belongs. Depending on the neighbor eNB type, the entry must be made in
20 bits for Macro eNB ID, and 28 bits for Home eNB. This information is used
during handover.
The eNB ID of the neighbor eNB must be entered accurately. If the information
does not match, the Handover will not be executed.
ENB_TYPE This parameter is the eNB type of the neighbor eNB.
Macro_eNB: Macro eNB.
Home_eNB: Home eNB.
ENB_MCC This parameter is the PLMN information (MCC) that represents the neighbor
eNB. Enter a 3-digit number whose each digit ranges from 0 to 9.
ENB_MNC This parameter is the PLMN information (MNC) that represents the neighbor
eNB. Enter a 2-digit or 3-digit number of whose each digit ranges from 0 to 9.
IP_VER IP address version indicating the IP address of a neighboring eNB. All
neighboring eNB IP version information must be the same.
IPV4: Indicates IPV4 address.
IPV6: Indicates IPV6 address.
NBR_ENB_IPV4 This parameter indicates the IP version 4 address of the neighbor eNB. This
information is used during X2 Link setup for the SCTP connection setup.
Accurately set the information to ensure proper X2 setup.
NBR_ENB_IPV6 This parameter indicates the IP version 6 address of the neighbor eNB. This
information is used during X2 Link Setup for the SCTP connection setup.
Accurately set the information to ensure proper X2 setup.
SECONDARY_NBR_ENB_ This parameter indicates the secondary IPv4 address of the neighbor eNB.
IPV4 This information is used during SCTP multi-homing connection setup.
SECONDARY_NBR_ENB_ This parameter indicates the secondary IPv6 address of the neighbor eNB.

IPV6 This information is used during SCTP multi-homing connection setup.
ADMINISTRATIVE_STATE This parameter is the neighbor eNB link status information.
locked: Cancels the relevant X2 handover procedure if there is any current X2
handover call, and blocks a new X2 handover out.
unlocked: Normally processes the X2 Handover.
shuttingDown: Normally processes the relevant X2 handover procedure if there
is any current X2 handover call, and blocks a new X2 handover out.
REMOTE_FLAG This parameter indicates whether the neighbor eNB is managed by the same
EMS or a different EMS.
False: Neighbor eNB is managed by the same EMS.
True: Neighbor eNB is managed by a different EMB.
The SCTP protocol manages using several system parameters for time interval of
heartbeat message broadcast, re-broadcasting times of heartbeat or data message,
and initial re-broadcast timeout value for Round Trip Time (RTO), minimum re-
broadcast timeout value for RTO, maximum re-broadcast timeout value for RTO,
and init message broadcast time interval for re-connection trial. Details are shown
in below table.
CHG-SCTP-PARA/RTRV-SCTP-PARA
HEART_BEAT_INTERVAL This parameter is the interval of transmitting a heartbeat message. A heartbeat
message is transmitted to check the validity of a link in the SCTP protocol.
NUM_PATH_RE_TX This parameter is the re-transmission count by which the SCTP path will be
failure if the response to the heartbeat or SCTP data is not received for more
than NUM_PATH_RE_TX.
RTO_INITIAL This parameter is the value used to calculate the SCTP round trip time (RTT). It
is the initial value of the Retransmission TimeOut which is used before the RTT
value is measured through packet transmission.
RTO_MIN The minimum value of the Retransmission TimeOut used to calculate the SCTP
Round Trip Time (RTT).
RTO_MAX The maximum value of the Retransmission TimeOut used to calculate the SCTP
Round Trip Time (RTT).
CONNECT_INTERVAL This parameter is the timer value to transmit the init msg. to attempt SCTP
connection periodically if a SCTP link is not set up for a peer node which is
equipped to the PLD.
NUM_ASSOC_RE_TX The number of times to retransmit heartbeat messages or SCTP data messages
in order to check whether the SCTP link is normal. The SCTP Association is
disconnected if responses to the heartbeats or SCTP data messages are not
received during specified (NUM_ASSOC_RE_TX) attempts.
Monitoring SCTP and X2 state of neighbor eNB are possible using RTRV-X2-
STS command.
The following table shows output information:
RTRV-X2-STS
NBR_ENB_INDEX This parameter is the index of the neighbor eNB.

NBR_ENB_ID This parameter is the ID of the neighbor eNB.
SCTP_STATE This parameter is the Stream Control Transmission Protocol (SCTP) status. It is
the physical connection status between the eNBs.
disable_SD_PlmnTg_MIS: shutdown by PLMN TGID (TunnelGroupId) setting
mismatch
disable_SD_PlmnTg_UA: shutdown by undecidable PLMN TGID
disable_SD_PlmnVr: shutdown by VR (Virtual Route) ID deletion.
disable_SD_NoX2: shutdown by NO_X2 setting
disable_SD_SonAnr: shutdown by one-way neighbor addition
disable_ABT_Inact: abort by SCTP INIT
disable_OOS: out of service (all case without above case)
X2AP_STATE This parameter is the X2AP status. It is the logical connection status between
eNBs. If SCTP is disabled, X2AP cannot be enabled.
Counters and KPIs

REFERENCE
UTRAN); S1 application protocol (S1AP)
UTRAN); X2 application protocol (X2AP)

LTE-SW3010, PDCP Sublayer Support

INTRODUCTION
In LTE system, the layer2 is split into three sublayers:
Medium Access Control (MAC)
Radio Link Control (RLC)
Packet Data Convergence Protocol (PDCP)
The PDCP sublayer is defined in 3GPP TS36.323 specification, which provides
the following services and functions:
Delivery of control/user plane data
Ciphering
Integrity protection
Header compression and so on
BENEFIT
The PDCP sublayer enables basic LTE service, which includes delivery of
control/user plane data.

N/A
FEATURE DESCRIPTION
The PDCP sublayer processes Radio Resource Control (RRC) messages in the
control plane and Internet Protocol (IP) packets in the user plane. The main
functions are header compression, security (integrity protection and ciphering),
and support for reordering and retransmission during handover. Each radio bearer
that uses the PDCP sublayer is configured to have one PDCP entity. Only
SRBs/DRBs mapped on DCCH and DTCH type of logical channels can use PDCP
sublayer functions.
The PDCP sublayer provides the following functions:
Header compression and decompression of user plane data
Transfer of control/user plane data
PDCP Sequence Number (SN) maintenance
Timer based discard of user plane data

Discard of duplicates
In-sequence delivery of upper layer PDUs at PDCP re-establishment of lower
layers for RLC AM
Duplicate detection/elimination of lower layer SDUs at PDCP re-establishment
for RLC AM
Ciphering and deciphering of user plane data and control plane data
Integrity protection and verification of control plane data
SYSTEM OPERATION
How to Activate
Key Parameters
Counters and KPIs

Name
Packet Loss Rate PdcpSduLossRateUL The calculated average loss rate of uplink SRB Packet that
is received in the PDCP
PdcpSduTotalULNum The number of UL PDCP SDUs
PdcpSduLossULNum The number of lost UL PDCP SDUs
REFERENCE
[2] 3GPP TS36.323 Evolved Universal Terrestrial Radio Access (E-UTRA);
Packet Data Convergence Protocol (PDCP) specification

LTE-SW4101, Capacity based Call Admission

Control
INTRODUCTION
The Call Admission Control (CAC) function is basically enabled to efficiently use
the limited radio resources, to guarantee the quality of user service even in case of
congestion, and to protect eNB system from being overloaded.
There are three types of call admission control functionalities:
Capacity-based Call Admission Control
QoS-based Call Admission Control
Pre-emption
The Capacity-based CAC makes a decision based on the capacity that operator
configures in advance. The QoS based CAC makes a decision based on the
required QoS level and available radio resources of that time. The QoS based CAC
has an effect only when MME requests GBR bearers. The Pre-emption allows a
priority call. These three functionalities work at the same time.
The operator can configure the capacity per cell and per eNB. To sustain a certain
level of QoS for non-GBR services, operator can limit the maximum number of
users allowed per cell. In addition, operator can configure the amount of resources
that are reserved for incoming handover calls. In this case, the call admission
algorithms make a decision based on the capacity that reflects the reserved
resources. In case of no resources, emergency calls are allowed by pre-empting
existing calls.
BENEFIT
By limiting the maximum number UEs or bearers per cell and per eNB,
considering radio and backhaul bandwidth, operator can control the minimum
QoS level provided for UEs.
The operator can protect the system from being shutdown due to overload or
congestion

N/A

FEATURE DESCRIPTION
Functional Architecture for CAC

The Capacity based CAC operates on the RRC connection establishment and E-
RAB bearer establishment while QoS based CAC and Pre-emption has impact on
E-RAB bearer establishment only. This feature covers capacity based CAC. In
case of other two CAC features, refer to LTE-SW4102 and LTE-SW4103.
The overall call admission control procedure is as follows:
Capacity Based CAC Scheme

The Capacity based CAC allows an incoming call or bearer as long as the total
number of calls/bearers does not exceed the pre-configured thresholds per cell and
eNB. There exist three kinds of thresholds: threshold for normal, threshold for
emergency and handover user, and the maximum. These thresholds per eNB can
be shown the figure below. Normal users can be allowed up to
NOR_ENB_CALL_COUNT per eNB. Emergency and HO users can be allowed
up to EM_HO_ENB_CALL_COUNT per eNB. These thresholds can be
configured for CAC via LSM by using CALL_CAC_THRESH_FOR_NORMAL
and CALL_CAC_THRESH_FOR_EMER_HO as follows:
NOR_ENB_CALL_COUNT = MAX_ENB_CALL_COUNT *
CALL_CAC_THRESH_FOR_NORMAL for the corresponding eNB.

EM_HO_ENB_CALL_COUNT = MAX_ENB_CALL_COUNT *
CALL_CAC_THRESH_FOR_EMER_HO for the corresponding eNB. .
Also, there exist similar thresholds per cell as the figure below. Normal users can
be allowed up to NOR_CELL_CALL_COUNT per cell. Emergency and HO users
can be allowed up to EM_HO_CELL_CALL_COUNT per cell. These thresholds
can be configured for CAC via LSM by using
CALL_CAC_THRESH_FOR_NORMAL and
CALL_CAC_THRESH_FOR_EMER_HO as follows:
NOR_CELL_CALL_COUNT = MAX_CELL_CALL_COUNT *
CALL_CAC_THRESH_FOR_NORMAL for the corresponding cell.
EM_HO_CELL_CALL_COUNT = MAX_CELL_CALL_COUNT *
CALL_CAC_THRESH_FOR_EMER_HO for the corresponding cell.
In case of radio bearer, capacity-based CAC applies similar concept per cell as
illustrated in the figure below. Bearers for normal users can be allowed up to
NOR_DRB_CALL_COUNT per cell. Bearers for emergency and HO users can be
allowed up to EM_HO_DRB_COUNT per cell. Theses thresholds can be
configured for CAC by using DRB_CAC_THRESH_FOR_NORMAL and
DRB_CAC_THRESH_FOR_EMER_HO as follows:
NOR_DRB_COUNT = MAX_DRB_COUNT *
DRB_CAC_THRESH_FOR_NORMAL for the corresponding cell.
EM_HO_DRB_COUNT= MAX_DRB_COUNT *
DRB_CAC_THRESH_FOR_EMER_HO for the corresponding cell.

eNB Capacity Based CAC Parameters

In case of capacity concern, operator should consider the hardware platform and
radio resources, for example, radio bandwidth, the number of channel card, and
QoS level. The following table shows an example in case of 10 MHz bandwidth
and the maximum values can be diverse in different channel card.
The following table shows an example of system parameters configuration for
capacity-based CAC. System parameter configuration can be different according
to channel card and system bandwidth.
System Parameters Criteria (10 MHz BW) Decision
MaxUeCELL 600 Current # of UEs of the cell < MaxUeCELL
(=MAX_CELL_CALL_COUNT)
MaxUeENB 1800 Current # of UEs of the eNB < MaxUeENB
(=MAX_ENB_CALL_COUNT)
MaxRbUE 8 Current # of bearers of the UE < MaxRbUE
MaxRbCELL 1200 Current # of bearers of the cell < MacRbCELL
(=MAX_DRB_COUNT)
In this context, number of active UE is equal to the number of active RRC

Connections. In case of number of bearers, GBR bearers and Non-GBR bearers are
counted all together.
The Maximum number of radio bearers per UE, which counts only data radio
bearers excluding signaling radio bearers, is limited by MAC layer protocol
specification (3GPP TS 36.321) and it is not configurable by operator.
The operator can configure the amount of resources that are reserved for incoming
handover calls. In this case, the call admission algorithms make a decision based
on the capacity that reflects the reserved resources.
Capacity Based CAC Operation

This section describes capacity-based CAC operation in each call procedure:
Capacity Based CAC Operation at RRC Connection Establishment

1 During the RRC connection establishment, eNB capacity-based CAC operates

per call. The procedure starts when the RRC connection request message is
received from UE.
2 The eNB capacity-based CAC procedure is initiated. Initially, the CAC operates
at eNB level. If eNB level CAC is passed, cell level CAC proceeds. Detailed
procedure can be described as follows:
oeNB level CAC
If the attempted RRC Connection is for normal user,
NOR_ENB_CALL_COUNT is applied for the threshold. If the current
number of UEs in the eNB is less than NOR_ENB_CALL_COUNT,
eNB level CAC for the RRC Connection is passed. Otherwise, the call
is rejected.
If the attempted RRC Connection is for an emergency user,
EM_HO_ENB_CALL_COUNT is applied for the threshold. If the
current number of UEs in eNB is less than
EM_HO_ENB_CALL_COUNT, eNB level CAC for the RRC
Connection is passed. Otherwise, the call is rejected.
oCell level CAC
If the attempted RRC Connection is for normal user,
NOR_CELL_CALL_COUNT is applied for the threshold. If the
current number of UEs in the cell is less than
NOR_CELL_CALL_COUNT, eNB level CAC for the RRC
If the attempted RRC Connection is for an emergency user,
EM_HO_CELL_CALL_COUNT is applied for the threshold. If the
current number of UEs in the cell is less than
EM_HO_CELL_CALL_COUNT, eNB level CAC for the RRC
3 If the call is rejected and RRCConnectionReject is sent to UE, depriotisationReq
IE can be populated according to the configuration.
RRCConnectionReject-v1130-IEs ::= SEQUENCE {

deprioritisationReq-r11 SEQUENCE {
deprioritisationType-r11 ENUMERATED {frequency, e-utra},
deprioritisationTimer-r11 ENUMERATED {min5, min10, min15, min30}
} OPTIONAL, -- Need ON
nonCriticalExtension SEQUENCE {} OPTIONAL}
4 If both eNB and cell level CAC is passed, RRC connection establishment is
initiated by transmitting the RRC connection setup message to UE. If the call
is rejected and the call type is an emergency call, the longest call among active
calls in the cell is released. In case of a normal call, the RRC connection
release message is transmitted to UE and the call is released.
5 The UE transmits the RRC Connection Setup Complete message.
6 The eNB sends MME Initial UE message

Capacity Based CAC Operation at E-RAB Setup
After the RRC establishment, eNB capacity-based CAC operates by receiving the
initial context setup request or E-RAB setup/modify request message from MME
for the default radio bearer and dedicated radio bearer (DRB) setup.
1 The eNB capacity-based CAC runs per E-RAB.
oIf the attempted bearer is for normal user, NOR_DRB_COUNT is applied for
the threshold. If current number of bearers in the cell is less than
NOR_DRB_COUNT, call is admitted. Otherwise, the call is rejected.
oIf the attempted bearer is for emergency user, EM_HO_DRB_COUNT is
applied for the threshold. If current number of bearers in the cell is less
than EM_HO_DRB_COUNT, call is admitted. Otherwise, the call is
rejected.
2 If the E-RAB is successfully admitted, the RRC connection reconfiguration
message is transmitted to UE to initiate E-RAB (DRB) establishment.
3 If the call is rejected, whether to admit the E-RAB is determined in
interoperation with pre-emption function per E-RAB (DRB) to control the call
flow (a partial success per E-RAB is ignored).
4 The eNB sends MME E-RAB setup message.

Capacity Based CAC Operation at Intra-eNB Handover
The eNB receives a measurement report from UE.

1 When cell change take places within the same eNB, the eNB capacity-based
CAC operates to control intra-eNB handover call admission.
2 The eNB capacity-based CAC is initiated based on a call. If the current number
of UEs in the cell is less than EM_HO_ENB_CALL_COUNT, the call is
admitted. Otherwise, the call is rejected. If current number of bearers in the
cell is less than EM_HO_DRB_COUNT, call is admitted. Otherwise, the call
is rejected.
3 If the call is admitted, the RRC connection reconfiguration message is
transmitted to UE to initiate the intra-eNB handover. If the call is rejected,
whether to admit the E-RAB is determined in interoperation with the pre-
emption function per E-RAB (DRB) to control the call flow (a partial success
per E-RAB is ignored).
4 The UE transmits RRC connection reconfiguration complete message.
Capacity Based CAC Operation at Inter-eNB Handover
1) The eNB receives a measurement report from UE.

2) The source eNB determines HO and sends the target eNBs a Handover Request
message.
3) To control inter-eNB handover call admission, eNB capacity-based CAC
operates by using the E-RAB Level QoS parameter included in the Handover
Request message received. The eNB capacity-based CAC is initiated based on a
call. If the current number of UEs in the cell is less than
EM_HO_ENB_CALL_COUNT, call is admitted. Otherwise, the call is rejected. If
current number of bearers in the cell is less than EM_HO_DRB_COUNT, call is
admitted. Otherwise, call is rejected.
4) If call is admitted, the Handover Request Acknowledge message is transmitted
to the source eNB to initiate the inter-eNB handover. If call is rejected, whether to
admit the E-RAB is determined in interoperation with the pre-emption function per
E-RAB (DRB) to control the call flow (a partial success per E-RAB is ignored)
5~6) The source eNB transmits the RRC connection reconfiguration message to
UE and performs SN Status Transfer.
8~10) After path switch procedure, the target eNB sends Release Request to
source eNB.
SYSTEM OPERATION
How to Activate
Execute the RTRV-ENB-CAC command to retrieve eNB Call Admission
Control.
Execute the RTRV-CELL-CAC command to retrieve the Cell Call Admission

Control.
Execute the CHG-ENB-CAC command to configure the performance of the
CAC function in the eNB unit.
Execute the CHG-CELL-CAC command to configure the performance in the cell
unit.
Key Parameters
CHG-ENB-CAC/RTRV-ENB-CAC/CHG-CELL-CAC/RTRV-CELL-CAC
CALL_COUNT_CAC_USAGE Whether to execute the Capacity-based Call Admission Control (CAC)
function per cell.
ci_no_use: The capacity-based CAC function per base station is not
performed.
ci_use: The capacity-based CAC function per base station is performed.
CELL_COUNT_CAC_USAGE Whether to execute the call count-based CAC function, which is one of the
capacitybased Call Admission Control (CAC) functions per cell.
ci_no_use: The capacity-based CAC function per cell is not performed.
ci_use: The capacity-based CAC function per cell is performed.
CHG-RRCONNREJECTDEPRIO-INF/RTRV-RRCONNREJECTDEPRIO-INF
REJECT_DEPRIORITY_USE This attribute represents the use of de-prioritisation IE in RRC Connection
Reject message.
DEPRIORITY_TYPE This attribute represents the de-prioritisationType IE (frequency or E-UTRA) in
RRC Connection Reject message.
CHG-TIME-INF/RTRV-TIME-INF
T325 This parameter is the timer value which UE start depriorising either the current
carrier frequency or E-UTRA. The UE start this timer when RRC Connection
Reject message which including deprioritisationReq. The default value is
min5, and it can be changed by the operator during operation as follows:
0: indicates 5 minutes
Refer to TS36.331 T325 for detail.
Counters and KPIs

REFERENCE
LTE-SW4103, Preemption
INTRODUCTION
In case of no resource available, eNB can admit a new bearer by preempting
existing bearers. This feature can be used to provide admission to priority users
even in congestion.
The decision is based on Allocation and Retention Priority (ARP) information of
new bearer(s) and existing bearer(s). The ARP consists of priority level,
preemption capability, and preemption vulnerability, which are delivered from
MME to eNB during E-RAB establishment. When there are multiple preemptive
candidate bearers, eNB selects a longest call.
The MME has responsibility to configure appropriate ARP per each bearer.
BENEFIT
The operator can provide a differentiated service that allows a high-priority UE to
access the network even in congestion.

Dependency
MME to support this feature
Limitation
A connected UE could experience a call drop when eNB is congested.
Related Features
LTE-SV0101 IMS based Emergency
LTE-SV0105 eMPS
LTE-SW4101 Capacity based CAC
LTE-SW4102 QoS based CAC
FEATURE DESCRIPTION
Functional Architecture for CAC

The Capacity based CAC has impact on RRC connection establishment and E-
RAB bearer establishment while QoS based CAC and Pre-emption has impact on
E-RAB bearer establishment only. This section covers preemption. In case of other
two CAC features, refer to LTE-SW4101 and LTE-SW4102.
The functional architecture of Call Admission Control (CAC) is as follows:
The preemption function is applied to GBR and non-GBR bearers in case of no

resources available. Related resources are the number of bearers defined per cell.
If operator provides QoS service and has limited resources that can be allocated to
GBR bearers, the lack of GBR bearers, PRBs and backhaul bandwidth can trigger
preemption function. In this case, an existing GBR bearer will be preempted. The
eNB follows the preemption rules defined in 3GPP TS36.413. If there are multiple
preemption candidates that have the same ARP, eNB will select a candidate bearer
at random.
Parameter Presence Range IE Type and Semantics Description
Reference
Priority Level M - INTEGER (015) The priority of allocation and retention.
Value 15 means 'no priority'. Values between 1
and 14 are ordered in decreasing order of prioirty,
that is 1 is the highest and 14 the lowest. Value 0
shall be treated as a logical error if received.
Pre-emption M - ENUMERATED This indicates pre-emption capability of the
Capability (shall not trigger request on other E-RABs.
pre-emption, may The E-RAB shall not pre-empt other E-RABs or, it
trigger pre- may pre-empt other E-RABs. The Pre-emption
emption) Capability indicator applies to the allocation of
resources for an E-RAB and as such it provides
the trigger to the pre-emption
procedures/processes of the eNB.
Pre-emption M - ENUMERATED This IE indicates the vulnerability of the E-RAB to
Vulnerability (not pre-emptable, preemption of other E-RABs.
pre-emptable) The E-RAB shall not be pre-empted by other E-
RABs or the E-RAB may be pre-empted by other
RABs. Pre-emption Vulnerability indicator applies
Parameter Presence Range IE Type and Semantics Description

Reference
for the entire duration of the E-RAB, unless
modified and as such indicates whether the E-
RAB is a target of the pre-emption
procedures/processes of the eNB.
Handover of Preempted UE
The preempted UE can be handed over to a neighbor cell. The eNB sends MR
Solicitation to preempted UE and it performs handover procedures based on the
measurement result from UE. If multiple carriers are available, they are all
configured for the measurement. The operator can configure handover thresholds
appropriately for the peemption case. Also, they can enable or disable the
handover of preempted UE. According to eNB and UE situation, call procedure
executed can be divided as follows:
Inter-frequency handover: The UE to be pre-empted supports multiple E-UTRA
carriers, and inter-frequency handover is available according to the CAC pre-
emption handover function.
Intra-frequency handover: The UE to be pre-empted does not support multiple E-
UTRA carriers, and intra-frequency handover is available according to the
CAC pre-emption handover function.
Inter-frequency redirection: The UE to be pre-empted supports multiple E-UTRA
carriers, and inter-frequency handover is not available according to the CAC
pre-emption handover function.
RRC connection release: The UE to be pre-empted does not support multiple E-
UTRA carriers, or it supports multiple E-UTRA carriers, but inter-frequency
handover and inter-frequency redirection are not available according to the
CAC pre-emption handover function.
The following flowchart shows operation flow before the CAC pre-emption
handover function executes:
Upon receiving a new call/bearer setup or handover request, eNB performs CAC
function.
1 After CAC function is performed in step1, if the new 'call/bearer setup or
handover' request can be accepted without pre-emption, the request is accepted
and the next procedure is performed.
2 After CAC function is performed in step1, if pre-emption is needed, pre-emption
function is performed to decide whether pre-emption of the existing call is
available.
3 If pre-emption of the existing call is available in step3, the new 'call/bearer setup
or handover' request is accepted, and the next procedure is performed.
4 The CAC pre-emption handover function is performed for the pre-empted call
selected in step3. Also, CAC pre-emption handover is operated only when the
entire call is pre-empted.
When only some bearers of a call are pre-empted, CAC pre-emption handover
is not operated for the call.
5 If pre-emption of the existing call is unavailable in step3, the new 'call/bearer

setup or handover' request is rejected, and the next procedure is performed.
The CAC pre-emption handover function is as follows:
The eNB operates CAC pre-emption handover function according to the result of
the CAC/pre-emption performance. (Continued from the [A] of the operation flow
before the CAC pre-emption handover function executes.)
1 The eNB finds whether there is enough resource available for the CAC pre-
emption handover process.
oIf the CAC pre-emption handover process is available in step1, step 2 is
performed.
oIf the CAC pre-emption handover process is not available in step1, step 7 is
performed.
2 The eNB decides target carrier that will handover the pre-empted call.
oIf UE does support multiple E-UTRA carriers, one of the carriers that are not
a serving carrier is selected.
oIf UE does not support multiple E-UTRA carriers, the serving carrier is
selected.
3 The eNB solicits UE for measurement report for the target carrier selected in
step2. At this moment, it starts a wait timer to determine whether the
measurement solicitation fails.
4 When the measurement report message is received from UE while the wait timer
of step3 is in operation, eNB checks if there exist neighbor cells whose UE
measurement results are above the configured threshold.
5 If there exist neighbor cells whose UE measurement results are above the
configured threshold in step4, the best cell is selected among cells and
handover preparation procedure starts.
6 If the handover preparation succeeds in step5, UE to be pre-empted is directed to
perform handover.
7 If one of the events below occurs during step4 to 6, CAC pre-emption handover
is unavailable. Thus it should be judged whether inter-frequency redirection is
available.
oThe wait timer of step3 expires while the measurement report message is not
received from UE yet.
oIn step 4, there is no neighbor cell whose UE measurement result is above the
configured threshold.
oIn step5, the handover preparation fails.
8 In step7, if UE does support multiple E-UTRA carriers, one of the carriers that
are not a serving carrier is selected and inter-frequency redirection is
performed.
9 In step7, if UE does not support multiple E-UTRA carriers, inter-frequency
redirection is unavailable. Thus, RRC connection release procedure is
performed.
SYSTEM OPERATION
How to Activate
The operator can enable the preemption function by setting
PREEMPTION_FLAG to USE by executing the CHG-CELL-CAC command.
When this function is disabled, eNB ignores the ARP information received from
MME and it does not admit a new bearer when the configured maximum
number of bearers is all used.
The operator can also enable the preemption handover function by setting
ACTIVE_STATE to ACTIVE by executing the CHG-PREEMPT-HO
command.
Key Parameters
CHG-CELL-CAC/RTRV-CELL-CAC
CELL_NUM The cell number. This value must not exceed the maximum number of cells
supported by the system. It is determined by Carrier/Sector. For example, if the
maximum capacity system is 1 Carrier/3 Sector, up to 3 cells are supported.
PREEMPTION_FLAG This parameter decides whether the cell enables or disables the use
preemption functionality.
CHG-PREEMPT-HO/RTRV-PREEMPT-HO
supported by the system. It is determined by Carrier/Sector. For example, if the
maximum capacity system is 1 Carrier/3 Sector, up to 3 cells are supported.
ACTIVE_STATE Whether to use the Preemption Handover Function
PREEMPTION_HO_THRES RSRP threshold used for triggering the EUTRA measurement report for
HOLD_RSRP Preemption Handover.
PREEMPTION_HO_THRES RSRQ threshold used for triggering the EUTRA measurement report for
HOLD_RSRQ Preemption Handover.
Counters and KPIs

Family Display Name Type Name Type Description
Preemption Handover per E- PreemptHoDropBearerI Number of bearers released as a result of inter-eNB
RAB ntra HO failure while performing intra-eNB HO due to
CAC preemption HO operation
PreemptHoBearerIntra Number of bearers handed over as a result of
successful intra-eNB HO among the bearers on
which preemption HO is performed instead of being
released due to CAC preemption HO operation
PreemptHoDropBearerI Number of bearers released as a result of X2HO
nterX2 failure while performingX2HO due to CAC
preemption HO operation
PreemptHoBearerInterX Number of bearers handed over as a result of
2 successful inter-eNB X2HO among the bearers on
PreemptHoDropBearerI Number of bearers released as a result of S1HO
nterS1 failure while performingS1HO due to CAC
preemption HO operation
PreemptHoBearerInterS Number of bearers handed over as a result of
1 successful inter-eNB S1HO among the bearers on
PreemptHoErabCnt Count of Preemption Handover per ERAB collected
PreemptHoErabTargetE TargetEarfcnDl requested for collection
arfcnDL
Preemption Handover PreemtIntraEnbAtt Intra-handover attempt count.
PreemtIntraEnbPrepSu Total intra handover preparation success count
cc
PreemtIntraEnbSucc Total intra handover execution success count
PreemtInterX2OutAtt X2-based preemption handover attempt count in

SeNB
PreemtInterX2OutPrep X2-based preemption handover preparation
Succ success count in SeNB
PreemtInterX2OutSucc X2-based preemption handover execution success
count in SeNB
PreemtInterS1OutAtt S1-based preemption handover attempt count in
SeNB
PreemtInterS1OutPrep S1-based preemption handover preparation
Succ success count in SeNB
PreemtInterS1OutSucc S1-based preemption handover execution success
count in SeNB
NoAvailableTargetCarri Counted when redirection is performed to the
er serving carrier because the target carrier of the UE
does not exist during preemption HO.
MrSolicitFail Counted when redirection is performed because MR
solicit is performed by specifying a target carrier for
preemption HO but no target cell above the MR
threshold for preemption HO is identified within the
specified timer period or report amount.
HoPrepFail Counted when redirection is performed due to
intra/S1/X2 HO preparation failure although a target
carrier for preemption HO is specified and a target
cell is specified as a result of successful MR solicit.
PreemptHoCnt Count of Preemption Handover collected
PreemptHoTargetEarfc TargetEarfcnDl requested for collection
nDL
REFERENCE
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application
Protocol (S1AP), Section 9.2.1.60
LTE-SW5500, CA Call Control

INTRODUCTION
The Carrier Aggregation (CA) is LTE-Advanced key feature that enhances the
peak throughput and quality of UE by allowing UE to use two or more carrier
resources simultaneously. According to 3GPP standard, single UE may aggregate
up to 5 carriers and 100 MHz frequency bandwidth at the same time. Due to this
feature, eNB performs the following functions:
Selection of secondary cells (SCells)
Decision on the allowance of SCell addition
Delivery of the L1 and L2 configuration information for SCells
The basic call processing procedures such as UE Context Setup and Handover are
upgraded to support the aforementioned functions.
BENEFIT
The operator can enhance the utilization of frequency resource and obtain load
balance effects, and more for scheduling.
The UE can improve throughput and reduce file download delay.

Dependency
Rel 10 UE that supports carrier aggregation
Depending on the standard, up to 5 carriers per UE can be aggregated.
FEATURE DESCRIPTION
The eNB supports two following operating modes to effectively support the CA
development scenario of 3GPP Rel10 TS36.300 Annex J:
CA Operation Mode Mode 1 Mode 2
Desirable Deployment Scenario #1 #1, #2
Characteristics Every PCells and SCells are 1:1 Release and re-connection SCell
paired. The pre-designated paired based on PCell-SCell Paired, and
SCell is always configured on MR at initial connection and HO in
initial connection and HO in (Co- (Co-located + MR)
located)
Measurement Configured SCell Configuration SCell Configuration
Configuration Frequency Event A2 Configuration for SCell
State release
CA Operation Mode Mode 1 Mode 2

(per carrier- Non-configured N/A Event A4 Configuration for SCell
frequency) frequency addition
Mode 1: When UE establishes RRC-connection to PCell or is handed over to

PCell, eNB directs UE to add the SCell collocated to the PCell. The UE does
not measure L3 radio quality of SCell.
Mode 2: When UE establishes RRC-connection to PCell or is handed over to
PCell, eNB directs UE to add the SCell collocated to the PCell. The UE may
release and add the SCell again according to L3 measurement report of the
SCell.
Check Blocks for SCell Addition

Samsung eNB considers the following conditions for adding SCell:
Check Description
C1. PCell CA ON/OFF This flag is configurable per PCell. If it is 0, OFF; if it is 1, ON.
Check
C3. CA Band Capability If the supported BandCombinations and BandwidthCombinationsets received from
Check UE radio capacity are supported by the eNB, success.
This check is carried out for every supported BandCombination of UE.
C4. Cell Capacity This step decides the allowed SCell addition based on the number of UEs of PCell
Check and SCell.
If a UE requests SCell addition beyond the maximum number of SCell added calls
which allows the setting of SCell addition per PCell, the request is rejected.
C5. SCell Availability This step is to check the service availability of the SCell requested by SCell addition
Check as follows:
SCell cell release: If the state of the cell requested as SCell is cell released,
impossible to add SCell.
SCell shutting down state: If the state of the cell requested as SCell is shutting
down, impossible to add SCell.
SCell barring or reserving: Decides the possibility of adding SCell considering all
cells barred and reservedforOperatorUse of SCell.
C6. Co-Schedulability This steup is to check whether co-scheduling of PCell and SCell is allowed or not.
Check By using IDs set in expansion to cell configuration, set the SchedulableUnit as a
parameter and if the cell requested as SCell is in the SchedulableUnit same as
PCell, success; otherwise, failure.
C8. UE FGI 112 Check If FGI bit 112 is 1, success; if it is 0, failure.
C4 Checking is moved to SCell activation stage.
Basic Operation for CA

At the Setup of Initial Context Setup (Mode 1, 2)
The eNB performs checks in serial order to determine the CA availability on
obtaining UE capability (at the reception of initial context setup request or of UE
capability information),
C1. PCell CA ON/OFF Check
C3. CA Band Capability Check

C5. SCell Availability Check
If the conditions C1 and C3 are met according to the CA operation modes, eNB
sends the following configurations in the RRC Connection Reconfiguration
message transmitted to UE in the conventional setup procedures.
In case of Mode 1,
If C5 is satisfied for the paired SCell, the eNB configures UE to add the paired
SCell that meets C3 condition.
In case of Mode 2,
If C5 is satisfied for the paired SCell,
oThe eNB configures UE to add paired SCell that meets C3 condition
oConfigures the event A2 measurement for SCell release.
If neither of conditions is failed, eNB performs the conventional initial context
setup procedure, that is, UE does not perform any other CA-related operations.
Once completing UE context setup, even if the states of C1 to C5 are changed
from the 'CA unavailable' to 'CA available' before the release of RRC Connection
or the handout to other cells, the current SCell and SCell measurement
configuration are not changed.
As ever, even if the conditions C1 to C5 during RRC connection are changed 'the
CA available' state to 'CA impossible' state, eNB does not perform SCell release
nor measurement configuration.
On Receiving Event A4 Measurement for SCell Addition Trigger (Modes 2)
Before eNB receives Event A4 Measurement Report (MR) for SCell addition, UE
is supposed to have no added SCell at the SCC. The eNB performs the following
in serial order for the neighbor cell triggering the event on receiving Event A4 MR
for SCell addition trigger:
C6. Co-Schedulability Check
If all conditions C6 and C5 are satisfied, eNB sends UE a separate
RRCConnectionReconfiguration message to set the following:
In case of Mode 2,
Add the reported neighbor cell triggering Event A4 as SCell
Release event A4 measurement on SCC of the added SCell
Configure the event A2 measurement for releasing SCell whose SCC of the
added SCell is Measurement Object (MO).
On Receiving Event A2 MR for SCell Release Trigger (Modes 2)
On receiving event A2 MR for SCell release trigger, eNB sends to UE a separate
RRCConnectionReconfiguration message for UE to set the following:
SCell release in SCC corresponding to MO of the triggered event A2
Release of event A2 measurement for SCell release at SCC of the released SCell
is MO
Configuration of event A4 measurement for SCell addition at SCC of the released
SCell is MO
On Receiving RRC Connection Re-establishment
The eNB performs the following just after receiving the
RRCConnectionReestablishment message from the UE: Release of all SCells
configured.
After completes the RRC connection REestablishment (RRE) procedure, the
configuration related to the CA on the RRCConnectionReconfiguration message is
performed as same as the RRC connection establishment.
Operation at Intra-eNB Handover
If CA supporting eNB receives a HO event MR and the neighbor cell triggering
the event is a cell belongs to eNB includes the PCell, the following check
operations are performed in serial order to determine CA availability in the target
cell:
Based on the conditions according to the CA operating modes, eNB adds the
following configurations in the RRCConnectionReconfiguration message
including MobilityControlInfo.
In case of Mode 1,
If all conditions C1 and C3 are satisfied, and C5 is satisfied for the paired SCell,
UE is configured to add the paired SCell on the SCC.
In case of Mode 2,
If all conditions C1 and C3 are passed, and C5 is satisfied for the paired SCell,
UE is configured to add the paired SCell on the SCC.
The eNB configures event A2 measurement for SCell release at SCC of the added
SCell is MO.
Operation at Inter-eNB Handover (X2, S1 HO)

Operation of Source eNB
In inter-eNB HO procedure, the source eNB sends the target eNB the S1AP or
X2AP:
Handover Request message includes the follows:
Serving SCell list (sCellToAddModList) set by the source eNB
CandidateCellInfoList on the serving frequencies.
UE-RadioAccessCapability.
Operation of Target eNB
When the target eNB supporting CA receives the S1AP or X2AP: Handover
Request message from the source eNB, it performs the following check operations
in serial order to determine the CA availability of UE from the source eNB:
C8. UE FGI bit 112 Check
If all conditions C1 to C3 are satisfied, eNB configures as followings:
In case of Mode 1,
If C5 is satisfied for the paired SCell, eNB configures UE to add paired SCell that
meets C3.
In case of Mode 2,
If C5 is satisfied for the paired SCell, eNB configures UE to add paired SCell that
meets C3.
The eNB configures event A2 measurement for SCell release at SCC on which
the SCells are added.
When UE unsatisfied C8 performs S1 HO, and the handover type described in the
S1AP: Handover Required message is either of the following cases, the target eNB
does not include the configuration of SCell addition nor measurement for
searching SCell in the Handover Request Acknowledge message, but configures
one more separate RRC Connection Reconfiguration message after completion of
the handover of UE.
UTRAN to LTE
GERAN to LTE
Additional Feature: PCell Frequency Switching

Merits
PCell Frequency Switching enables SCell-configured UEs to perform inter-
frequency handover to the SCC earlier than UEs not configuring SCell, thereby
SCell-configured UEs can maintain a higher throughput level compared to non-CA
UEs. In addition, PCell Frequency Switching is free from PCell throughput
degradation caused by measurement gap since CA UEs with a configured SCell
can measure L3 channel quality of neighbor cells on the SCC without
measurement gap.
Setting of Related Parameters

Event A2/A1 thresholds for SCell-configured UEs to trigger inter frequency
searching are defined as configurable system parameters, which shall be set to
higher values than those for non-CA UE. Event A3 offset/A5 threshold2 for SCell-
configured UEs to trigger inter frequency handover are defined as configurable
system parameters, which are recommended to set the same or higher values than
those for non-CA UEs.
Operation
On meeting event-triggering conditions for SCell-configured UEs, SCell-
configured UEs perform inter frequency searching and inter frequency handover to
the SCC. The following figures show state transition diagram of SCell
configuration and measurement configuration in PCell Frequency Switching
CA_InterF_: Threshold or offset for SCell-configured UEs to trigger inter-
frequency carrier searching or handover
InterF_: Threshold or offset for non-CA UEs (including CA UEs which do not
have SCell added) to trigger inter-frequency carrier searching or handover
Mode 1. Operation Details
This section describes how measurements are managed in Mode 1.
As described earlier, the SCell is added in Mode 1 at the time of RRC Connection
Reconfiguration (if not already added). Along with the SCell addition, the
CA_InterF_A2 event is configured for PCell. This event is used to monitor PCell
level and trigger further measurements. It should be defined higher than regular A2
measurements.
When the CA_InterF_A2 trigger is reported, eNB configures CA_InterF_A1 (on
PCell), CA_InterF_A3/A5, and InterF_A2 (on PCell). If UE reports
CA_InterF_A1, other measurement triggers are removed and CA_InterF_A2 is
again added.
If UE reports InterF_A2, eNB configures InterF_A1 and InterF_A3/A5 on UE
and removes other measurements.
If UE reports CA_InterF_A3/A5 (for SCell FA), eNB performs a PCell switch in
which the SCell FA becomes the new PCell and the previous PCell FA is
added as the new SCell.
If UE reports InterF_A1, eNB removes the existing measurements and adds
CA_InterF_A1 (on PCell), CA_InterF_A3/A5, and InterF_A2 (on PCell).
If UE reports InterF_A3/A5, a regular handover is performed.
Mode 2. Operation Details

Mode 2 operates similarly to Mode 1 except that A2 measurements related to
SCell addition and release are also added.
Limitation
PCell Frequency Switching does not apply to UEs having GBR bearer(s).
SYSTEM OPERATION
How to Activate
Execute the CHG-CACELL-INFO command to configure
CA_AVAILABLE_TYPE to DL_Only.
Key Parameters
CHG-CACELL-INFO/RTRV-CACELL-INFO
CA_AVAILABLE_TYPE This parameter indicates whether to support carrier aggregation (CA).
Counters and KPIs

Carrier Aggregation capable CaCapaPCellUE Number of CA capable UEs (PCell)
UEs (PCell)
Carrier Aggregation SCellAddAtt Scell Addition attempt count (SCell)
Messagecount for SCellAddSucc_RrcSig Number of successes in addition to co-located
Addition/Release (SCell)
SCell or successes in SCell addition by HO-in
procedure (SCell)
SCellAddSucc_EventA4 Number of successes in SCell addition by Event
A4 (SCell)
SCellAddSucc_EventA6 Number of successes in SCell addition (change)
by Event A6 (SCell)
SCellAddSucc_RrcReset Number of successes in addition to SCell after
up RRC connection reestablishment procedures
(SCell)
SCellAddFail_RrcSigTO Number of fails in Scell addition by released calls
by RRC Connection Reconfiguration T/O (SCell)
SCellAddFail_CaCapaCa Number of fails in SCell addition under Carrier
c Aggregation Capability CAC Procedure (SCell)
SCellAddFail_CpCcFail Number of fails in Scell Addition under ECCB
(Scell)
SCellAddFail_CpRrmFail Number of fails in Scell Addition due to resource
allocation failure (Scell)
SCellRel_RrcSig Number of times that SCell Release is performed
under the RRC connection reestablishment
procedures (SCell)
SCellRel_HoOut Number of times that SCell Release is performed
under the HO Out procedures (SCell)
SCellRel_EventA2 Number of times that SCell Release is performed
by Event A2 (SCell)
SCellRel_EventA6 Number of times that SCell Release (Change) is
performed by Event A6 (SCell)
SCellRel_RrcResetup Number of times that SCell Release is performed
under the RRC connection reestablishment
procedures (SCell)

SCellRel_CaCac Number of times that SCell Release is performed
under the Carrier Aggregation CAC (SCell)
SCellAddCnt_Avg The average number of SCell Added UEs.
Carrier Aggregation SCellActivation Count of activations (SCell)
Message count for SCellDeactivation_TO Count of SCell deactivation occurrences by
Activation/Deactivation reason: When deactivation timer expires (SCell)
(SCell)
SCellDeactivation_Misma Count of SCell deactivation occurrence by reason:
tch When CA status of eNB and that of the UE are
different (SCell)
CRNTIcollision The cumulated number of Scell Activation fail due
to C-RNTI collision (The C-RNTI of UE, who
requests Scell activation to SCell, is already used
in SCell)
SCellActUEAvg The average number of Scell activated UE
Air MAC Packet (PCell) AirMacULByte The sum of the size of the MAC PDU successfully
received via PUSCH during the statistics period
AirMacULByteCnt AirMacULByte collection count
AirMacULTti The sum of sections that have the MAC PDU
successfully received via PUSCH during the
statistics period
AirMacULThruAvg Average size per second of the MAC PDU
successfully received via PUSCH
AirMacULEfctivThruAvg Average size of the MAC PDU of the section
statistics period
AirMacDLByte The sum of the size of the DCCT/DTCH MAC
PDU that received HARQ ACK among the MAC
PDU transmitted via PDSCH during the statistics
period
AirMacDLByteCnt AirMacDLByte collection count
AirMacDLTti The sum of sections that have the MAC PDU
successfully transmitted via PDSCH during the
statistics period
AirMacDLThruAvg Average size per second of the DCCT/DTCH MAC
period
AirMacDLEfctivThruAvg Average size of the MAC PDU of the section
statistics period
AirMacULByteCurr The most recently collected AirMacByteUl value
AirMacDLByteCurr The most recently collected AirMacDLByte value
AirMacULThruMin Minimum of the average size per second of the
MAC PDU successfully received via PUSCH
AirMacULThruMax Maximum of the average size per second of the
AirMacDLThruMin Minimum value of average size per second of the
DCCT/DTCH MAC PDU that received HARQ ACK
among the MAC PDU transmitted via PDSCH
during the statistics period

AirMacDLThruMax Maximum value of average size per second of the
Air MAC Packet (SCell) AirMacULByte The sum of the size of the MAC PDU successfully
received via PUSCH during the statistics period
AirMacULTti The sum of sections that have the MAC PDU
statistics period.
AirMacULThruAvg Average size per second of the MAC PDU
successfully received via PUSCH.
AirMacULEfctivThruAvg Average size of the MAC PDU of the section
statistics period
AirMacDLByte The sum of the size of the DCCT/DTCH MAC
period
AirMacDLTti The sum of sections that have the MAC PDU
statistics period
AirMacDLThruAvg Average size per second of the DCCT/DTCH MAC
period
AirMacDLEfctivThruAvg Average size of the MAC PDU of the section
statistics period
AirMacULThruMin Minimum of the average size per second of the
AirMacULThruMax Maximum of the average size per second of the
AirMacDLThruMin Minimum value of average size per second of the
AirMacDLThruMax Maximum value of average size per second of the
DL Wideband CQI (PCell) DLReceivedCQI0 Number of receiving CQI 0 for a wideband CQI
per layer/codeword transmitted from CA UE
whose the cell is PCell
DLReceivedCQI1 Number of receiving CQI 1 for a wideband CQI

DLReceivedCQIMin The minimum value of DlReceivedCQI received
from CA UE whose cell is PCell
DLReceivedCQIMax The maximum value of DlReceivedCQI received
DLReceivedCQIAvg The average value of DlReceivedCQI received
CQIErase Number of times that CQI erase per
layer/codeword is received from CA UE whose cell
is PCell
DL Wideband CQI (SCell) DLReceivedCQI0 Number of receiving CQI 0 for a wideband CQI
whose the cell is SCell

DLReceivedCQIMin The minimum value of DlReceivedCQI transmitted
from CA UE whose the cell is SCell
DLReceivedCQIMax The maximum value of DlReceivedCQI
transmitted from CA UE whose the cell is SCell
DLReceivedCQIAvg The average value of DlReceivedCQI transmitted
from CA UE whose the cell is SCell
CQIErase Number of times that CQI erase per

layer/codeword is received from CA UE whose cell
is SCell
CA_UE_PER_CC_NUM DL_1FD_SCC The average number of UEs that has one of FDD
DL carrier to SCell.
DL_1TD_SCC The average number of UEs that has one of TDD
DL carrier to SCell.
DL_2FD_SCC The average number of UEs that has two of FDD
DL carriers to SCell.
DL_2TD_SCC The average number of UEs that has two of TDD
DL carriers to SCell.
DL_1FD_1TD_SCC The average number of UEs that has one of FDD
DL carrier and one of TDD DL carrier to SCell.
CA Addtion and Activation No_DlCaCapabilityUe There is no CA capability corresponding to the
Information (Pcell) supportedBandCombination
2CC_DlCaCapabilityUe CA capability corresponding to the
supportedBandCombination support 2 Component
Carrier
3CC_DlCaCapabilityUe CA capability corresponding to the
supportedBandCombination support 3 Component
Carrier
2CC_ScellAdditionTime Total SCell Addition Time of 2 Component Carrier
3CC_ ScellAdditionTime Total SCell Addition Time of 3 Component Carrier
REFERENCE
[1] 3GPP TS 36.101 Evolved Universal Terrestrial Radio Access (E-UTRA); User
Equipment (UE) radio transmission and reception
Chapter 3 Load Control
LTE-SW2004, Blind Offloading to WCDMA

INTRODUCTION
Depending on the service providers network environment, the intra-LTE load
balancing functions such as load equalization, offloading to intra-group carriers, or
offloading to inter-group carriers are initiated first and the blind offloading to
inter-RAT (WCDMA) function is initiated if cell overload cannot be removed in
LTE network.
The following shows load balancing functions as the serving cell load increases:
BENEFITS
This feature reduces the overload state of LTE cell by using WCDMA network.
The bad QoE due to overload will be reduced.

Dependency
To enable the blind offloading to WCDMA function, operator must set the FA
information of WCDMA.
Limitation
The BlindOffloadtoIRAT_Threshold (iratOffloadThreshold) should be set
higher than intraGroupOffloadThreshold or
interGroupOffloadingThreshold(k).
FEATURE DESCRIPTION
Samsung intra-LTE LB is operating in the following procedure:
1 Cell load monitoring for a serving cell
oIn case of cell load definition, refer to SW2001 Feature Description (FD).
oIf cell load exceeds the iratOffloadThreshold, the blind offloading to
WCDMA operation is triggered.
2 UE selection and redirection execution
oAfter checking UE capability, select UEs that support N_LBMC_TARGET
WCDMAs and perform redirection.
SYSTEM OPERATION
How to Activate
Execute the CHG-TM-CNTR command to set IRAT_3G_OPERATION_MODE to
BLIND_MODE.
To set UTRAN in top priority to select RAT for blind offloading as an additional
option, execute the CHG-IRAT-MLB command to set
IRAT_3G_OFFLOAD_PRIORITY to 3.
Key Parameters
CHG-TM-CNTR/RTRV-TM-CNTR
IRAT_3G_OPERATION_MODE Set the IRAT MLB operating mode for UTRAN.
CHG-IRAT-MLB/RTRV-IRAT-MLB
IRAT_3G_OFFLOAD_PRIORIT Top priority configuration parameter for 3G as a basis to select RAT for a
Y cell load reporting request
Counters and KPIs

LB_REDIRECTION LBRedirectiontoWCDMA Count of trying to UTRAN MLB Redirection
REFERENCE
[1] 3GPP 36.300: E-UTRA and E-UTRAN; overall description Stage 2
[2] 3GPP 36.331: E-UTRAN; Radio Resource Control (RRC); Protocol
specification
[3] 3GPP 36.423: E-UTRAN; X2 application protocol (X2AP)

[4] 3GPP 36.902: E-UTRAN; Self-configuring and self-optimizing network (SON)
use cases and solutions
LTE-SW2020, Load Distribution over Backhaul

Links
INTRODUCTION
When eNB is connected to a backhaul network with multiple Ethernet links, there
are different ways to distribute load over the links depending on IP configuration.
For example, when single IP address is used for two Ethernet links in the same
subnet, link aggregation can be used for load balancing between two links. To
forward a packet, one link is selected by a hashing algorithm based on 5 tuples of
the packet. When one link fails, the other link carries all the packets. In this case,
SCTP multi-homing for S1/X2 interface cannot be used because there is only one
IP address available. The ECMP (Equal Cost Multi Path) is another way to achieve
load balancing between two links that has two different IP addresses belonging to
different subnet. In this case, however, it is not likely to evenly distribute load over
the links because most packets will have the same source, destination IP, and port
number.
In this feature, application layer selects a link during call setup procedures based
on the number of UEs per each link. The traffic from UE is carried over the same
link. The SCTP multi-homing can be enabled at the same time and even load
distribution is achieved by the number of UEs.
BENEFIT
The load balancing is achieved between two links
The operator can monitor all traffic of a specific UE on the same link

Dependency
This feature can be enabled when eNB has two available Ethernet links.
Limitation
This feature is not working with IPsec or Virtual Routing enabled.
FEATURE DESCRIPTION
In case of load balancing between backhaul links that are connected to eNB,
assume that the backhaul network shall be configured to support the separated two
links, and front-end switches (or routers) in different path shall be connected to
each other to secure an emergency path in case of link failure.
Load Balancing Between Backhaul Links

Before eNB sends INITIAL CONTEXT SETUP RESPONSE message during the
UE's call setup procedures, the eNB selects a link that has lower load by the
number of UEs, and include the transport network layer address in the message. As
a result, eNB will use the selected IP address as a source address of uplink GTP
tunnel and as a destination address of downlink GTP tunnel for UE.
Since load is distributed based on the number of UEs and cannot guarantee that
actual amount of traffic is equalized between two links.
The packets coming from and packets heading to the same UE are carried through
the same link. Therefore, operator can monitor all the packets from/to one UE by
tapping the one link. Note that signaling messages (S1, X2) follow SCTP rules.
Link Failure
When eNB detects a failure on one link, it sends GARP message through the other
link so that the switches (or routers) can forward packets by using a live path.
Otherwise, the packets would not be forwarded to eNB in downlink path.
In case of uplink packets, eNB forwards them to the healthy link.
SYSTEM OPERATION
How to Activate
When eNB equips two Ethernet links and both are active means, eNB starts to
distribute calls over two links. When one link becomes not available, eNB will
forward all the packets to the other available link. There is no handler that operator
can enable or disable this feature
Key Parameters
Counters and KPIs

REFERENCE
N/A
LTE-SW2103, UL Congestion Prevention

INTRODUCTION
In a network with a limited backhaul bandwidth, the packets can be discarded at
eNB or at an intermediate node due to small buffer size or rate mismatch.
Specifically, the network congestion may occur when operator constrains UL
backhaul bandwidth of eNB that is connected to a narrow bandwidth backhaul
network. In this case, eNB reduces the overall amount of UL packets generated at
UEs by throttling down UL resource allocation. In such scenario, eNB controls UL
UE-AMBR (Aggregate Maximum Bit Rate) internally depending on the queue
length of the outgoing network scheduler. If the number of packets in buffer
increases over a threshold, eNB will decreases UL UE-AMBR of UEs.
Consequently, the radio scheduler will reduce the amount of radio resources in
proportion.
BENEFITS
The operator can prevent UL packets from being discarded at eNB due to UL
backhaul congestion
The delayed UL packet transmission can be one way to cause flow control at the
application layer

N/A
FEATURE DESCRIPTION
The eNB controls congestion toward UL by recalculating UE-AMBR parameter
using adjustment factor (R) value if packets are discarded due to congestion in UL
backhaul section. The detailed procedure is as follows.
The figure below describes the overall functional architecture for UL congestion
prevention. The eNB internally classifies UL packets into different queues.
Packets from bearers with a specific QCI are sent to a specific queue. Usually,
queues that serve GBR bearers have a higher priority and their packets are
transmitted before the packets in the queues that serve Non-GBR bearers. If the
number of packets in one of the queues for Non-GBR bearers increases over a
threshold, eNB calculates Rate Adjustment Factor (R) and sends it to UL
Scheduler.
Packet Drop
A packet drop occurs when the maximum volume of buffer controlled by eNB is
finally exceeded after a gradual increase in the amount of packet data that eNB has
transmitted in the direction of UL. To prevent packet drops, execute UL flow
control function or UL congestion prevention function.
In other words, periodically monitor the number of packets piled up in UL buffer
of the eNB and, when UL traffic exceeds the threshold (Low_Threshold), reduce
the number of packets that UE transmits to eNB by decreasing UE-AMBR value
applied to UE by a regular amount.
Low_Threshold This parameter indicates the minimum volume of the buffer that can affect the
Rate Adjust Factor.
High_Threshold This parameter indicates volume of the buffer that minimizes the Rate Adjust
Factor.
Buffer_Monitoring_Period The interval at which the Rate Adjust Factor is calculated by measuring the
number of packets in the buffer of eNB.
MIN_UE-AMBR The minimum UE-AMBR that can be allocated to UE when congestion occurs.
Function_Enabler The function that enables or disables (ON/OFF) UL congestion prevention
function.
Response_Mode This parameter determines whether the Response_Mode is linear or non-linear.
The UL flow control periodically monitors the size of packet accumulated in UL

buffer of eNB. When UL traffic exceeds the threshold value (low_threshold), UL
flow control reduces the amount of packet transmitted from UE to eNB by
reducing the value of UE-AMBR, which is applied to UE.
The operator can change the values of low_threshold and high_threshold in the
network management.
The UL congestion prevention function can be turned ON or OFF by using
system parameters.
eNB Control Function

To control UL traffic load, eNB provides the following flow control functions:
The integral type eNB periodically measures the size of packet in the buffer of
transport layer. If queues are classified by QCI types, measure the packet
based on the queue of non-GBR QCI. If there are multiple queues of non-GBR
QCI, measure the each queue respectively and use the largest value among the
results. In this case, operator may use system parameters to configure the
measurement period.
If queue length in the packet exceeds low_threshold value, the integral type eNB
determines the value (R) of UE-AMBR adjustment factor according to the
queue length. The R value is determined between 0 and 1 in decreasing linear
or non-linear values as the queue length increases. If the queue length is less
than the low_threshold value, R value is set to 1. If the queue length exceeds
the high_threshold value, R value is set to 0. The operator may use system
parameters to configure the values of high_threshold and low_threshold. The
operator can use system parameters to configure the change rate of R value
(linear or non-linear.)
The integral type eNB multiplies R value by each of UE-AMBRs to determine
the effective UE-AMBR towards uplink, and allocates UL radio resources to
each of UEs based on this value. In this case, UE-AMBR towards DL
direction is not affected. The UL effective UE-AMBR should always be
maintained above Min_UE-AMBR to ensure the basic service availability for
UE. The operator may use system parameters to configure the Min_UE-
AMBR.
The integral type eNB provides parameters for operator to enable or disable the
UL traffic control between UE and eNB.
Buffer Monitoring
Monitors the queue length (Q_Length) periodically
The intervals are from double digit number msec. 20 ms at the minimum
Measures the Q_Length of queue with the largest buffered amount and relays the
value to the rate feedback block. Based on Q_Length, the rate feedback block
determines and relays the rate adjustment factor R to UL-Scheduler to
calculate the modified UE-AMBR.
Linear Function
The linear function determines the rate adjustment factor R based on the Q_Length
as shown below:
R=1 if Q_Length < Low_Threshold

R=0 if Q_Length > High_Threshold
If R value is different from the previous value, relays the value to UL scheduler to
calculate the modified UE-AMBR. [Modified UE-AMBR = max(R x UE-AMBR,
MIN_UE-AMBR)].
Non- Linear Function

The Non-linear function determines the rate adjustment factor R based on
Q_Length as shown below:
R=1 if Q_Length < Low_Threshold
R=0 if Q_Length > High_Threshold
If R value is different from the previous value, relays the value to UL scheduler to
calculate the modified UE-AMBR. (Modified UE-AMBR = max (R x UE-AMBR).
SYSTEM OPERATION
How to Activate
The eNB provides the scheduling functions to limit the volume of data
transmitted from UE when there is a limitation on bandwidth of the uplink
backhaul line.
If monitoring state is enabled, perform the queue monitoring to determine the
occurrence of backhaul congestion.
The UL Congestion Prevention parameters can be activated by executing the
CHG-BHCGT-PARA command.
Key Parameters
CHG-BHCGT-PARA/RTRV-BHCGT-PARA
DB-INDEX Backhaul Congestion Monitoring Parameter Index
MONITORING-STATE This parameter indicates to enable the queue monitoring, which is used to
determine whether the backhaul is congested.
0: Disabled
1: Enabled
HIGH_THRESHOLD The high threshold of the queue length used to control the uplink traffic. It must
be larger than the low threshold.
LOW_THRESHOLD The low threshold of the queue length used to control the uplink traffic. It must
be less than the high threshold.
MONITORING_PERIOD The interval at which backhaul congestion is monitored in ms. The default is
100 (ms). The target queues are monitored every interval set in this parameter.
MIN_UE_AMBR The UL Effective UE-AMBR must a larger than Minimum UE-AMBR to
guarantee a basic service availability of UEs.
RESPONSE_MODE This parameter indicates a method to calculate UE-AMBR Rate Adjustment
Factor
0: Linear
1: Non-linear
Counters and KPIs

REFERENCE
N/A
LTE-SW2104, eNB Overload Protection

INTRODUCTION
This feature describes how eNB can be protected from being overloaded by
limiting the number of calls during a given time period. Integrated eNB provides a
function that can limit the maximum count of call connection requests (RRC
Connection Request) per unit time.
BENEFIT
This feature helps eNB from being overloaded by configuring the threshold
settings.

Limitation
The UE may experience a long setup time in case of congestion.
FEATURE DESCRIPTION
This feature enables operator to configure the monitoring duration for eNB
overload protection. The maximum number of request messages for each RRC
establishment cause and PS paging is shown below:
The maximum number of highPriorityAccess calls
The maximum number of mo-Signaling calls
The maximum number of mo-Data calls
The maximum number of delayTolerantAccess
The maximum number of PS paging (if include paging priority IE, then eNB will
not discard the paging message)
Refer to RRC establishment causes in RRCConnectionRequest message.
Emergency and mt-Access calls are not limited.
EstablishmentCause ::= ENUMERATED { emergency, highPriorityAccess, mt-Access, mo-

Signaling, mo-Data, delayTolerantAccess-v1020, spare2, spare1}
eNB Operation
The eNB observes number of call request per RRC establishment cause and
number of PS paging for the monitoring time, which is specified in the system
parameter.
If the count exceeds maximum number of call requests for establishment cause or
PS paging message, then eNB will discard the call.
When the monitoring time expires, eNB initializes all counters for RRC
establishment causes and PS paging messages. Then, eNB begins to count up
during the next monitoring time period. When the counter reaches configured
maximum limit, eNB discards any additional request messages.
Operation Procedure
Establishment Cause Based Protection Procedure
The maximum count of call connection requests per unit time can be set as a
system parameter for each RRC establishment cause. However, if RRC
establishment cause is an emergency and mt-Access, this number cannot be set.
The integrated eNB monitors the number of call connection requests for each
RRC establishment cause during the monitoring period set by the system
parameter.
When RRC Connection Request message is received from UE, if the number of
call connection requests has not exceeded the threshold corresponding to the
RRC establishment cause, which is included in the RRC Connection Request
message, the call connection request is accepted. If count exceeds the
threshold, the call connection request is not accepted.
If the monitoring period set by the system parameter has expired, the integrated
eNB initializes the count of call connection requests for each RRC
establishment cause.
The RRC establishment cause can be used by the network to prioritise the
connection establishment request from UE at the high load situation in the
network.
Paging Based Protection Procedure
The maximum count of paging processes per unit time can be set as a system
parameter.
The number of paging requests is monitored during the monitoring period set by
the system parameter.
If the number of paging requests received from MME has not yet exceeded the
threshold, the paging message is processed. If the number exceeds the
threshold, further paging requests are ignored.
If include paging priority IE received from MME, then eNB will not discard the
paging message.
If the monitoring period set by the system parameter has expired, the paging
request count is initialized.
SYSTEM OPERATION
How to Activate
Oveload Protection(CALL): Change the overload protect control mode with
CHG-OVLD-PTC command
oProtectPerNormalCall: Number of Normal Call based Overload Protection
(control 1)
oProtectPerEstablishCause: Establish Cause based Overload Protection
(control 2)
Overload Protection(psPaging): Change the psPaginglProtectUsage to USE with
CHG-OVLD-PTC command
Key Parameters
OVERLAOD_PROTECT_CT Setting value for overload protect.
RL 0: noUse
1:ProtectPerNormalCall
2:ProtectPerEstablishCause
PS_PAGING_PROTECT_U Whether to execute psPaging protect function
SAGE
Counters and KPIs

DENIED_CALL Denied_HighPriorityAc Number of high priority access-type calls denied by the
cess overload protection function
Denied_moSignaling Number of mo signaling-type calls denied by the
overload protection function
Denied_moData Number of mo data-type calls denied by the overload
protection function
Denied_DelayTolerant Number of delay tolerant access calls denied by the
Access overload protection function
Denied_Paging Number of paging messages denied by the overload
protection function
REFERENCE
Resource Control (RRC) protocol specification.
LTE-SW2108, Smart Congestion Mitigation

INTRODUCTION
Up to 3GPP Release 11, MMTel voice access is controlled by both Access Class
Barring and Service Specific Access Control at the same time. As a result, operator
cannot control MMTel voice access separated from data access. From the 3GPP
Release 12, using Smart Congestion Mitigation, eNB can provide three bits in
SIB2 to indicate whether MMTel voice, MMTel video, and SMS UEs shall skip
the Access Class Barring check. In this method, operator can control MMTel voice
access separated from data access and prioritize MMTel voice access over data
access.
BENEFIT
The operators can prioritize MMTel voice, MMTel video, and SMS access
attempts over other data packet services.

Dependency
The UE should support Smart Congestion Mitigation
Limitation
Standardization of this feature is ongoing in 3GPP release 12, hence schedule and
operation is subject to change.
FEATURE DESCRIPTION
To allow UE to skip Access Class Barring for specific application such as mobile
originating MMTELVoice, MMTELVideo, or SMS, eNB can broadcast 3 ACB
skip indicators in SIB2 under system configuration. When UE tries to establish
RRC connection for specific application, UE checks relevant ACB skip indicator
and skips ACB and consider access to the cell as not barred if ACB skip indicator
for relevant application is set.
The following figure shows ACB skip operation for a mobile originating
MMTELVoice:
To use Smart Congestion Mitigation, operator can allow access to specific

applications while keep blocking packet data service at the congestion situation as
shown in the following figure:
SYSTEM OPERATION
How to Activate
The Smart Congestion Mitigation is to configure Access Class Barring Skip
indicator as per Service Specific Access Control.
Key Parameters
RTRV-BAR-PARA/CHG-BAR-PARA
acBarringSkipForMMTELvoice This parameter indicates to enable/disable skipping of Access Class
Barring (Mo-Sig, Mo-Data) procedure when MMTEL Voice is used.
acBarringSkipForMMTELvideo This parameter indicates to enable/disable skipping of Access Class
Barring (Mo-Sig, Mo-Data) procedure when MMTEL Video is used.
acBarringSkipForSMS This parameter indicates to enable/disable skipping of Access Class
Barring (Mo-Sig, Mo-Data) procedure when SMS is used.
Counters and KPIs

There are no a related counters or KPIs.
REFERENCE
[1] TR 36.848 Evolved Universal Terrestrial Radio Access Network (E-UTRAN);
Study on smart congestion mitigation
Chapter 4 Mobility Control
LTE-SW1002, Idle Mobility Support

INTRODUCTION
To support intra-LTE cell reselection, eNB broadcasts the System Information
Block type 3 (SIB3), System Information Block type 4 (SIB4), and System
Information Block type 5(SIB5). The UE shall monitor E-UTRAN BCCH during
idle mode to retrieve these SIBs for the preparation of intra-LTE cell reselection.
Then, UE makes measurements on neighbouring cells based on the criteria and
performs cell reselection to intra-/ inter-frequency neighbouring cells when needed.
The parameters for intra-LTE cell reselection broadcasted in SIB3, SIB4, and SIB5
are as follows:
SIB3 conveys the common information for intra-frequency, inter-frequency and/
or inter-RAT cell reselection.
SIB3 also conveys the specific information for intra-frequency cell reselection.
SIB4 conveys the intra-frequency neighbouring cell related information, that is,
intra-frequency neighbour cell list and blacklisted cells.
SIB5 conveys the specific information for inter-frequency cell reselection.
BENEFIT
The operator can provide idle mobility to its subscribers within E-UTRAN.
The LTE users in idle state can be moving within E-UTRAN.

N/A
FEATURE DESCRIPTION
PLMN Selection
When LTE UE is switched ON, it will start a process to find Public Land Mobile
Network (PLMN). The PLMN may be selected either automatically or manually,
depending on the device's configuration.
Based on the request from NAS layer of UE, if a required PLMN is already
associated with LTE, UE shall scan LTE carriers based on UE stored information.
The UE shall search for the strongest PLMN cell and tune to the Physical
Downlink Shared Channel (PDSCH to read SIB1(s), where PLMN information is
delivered. The PLMN which is reported to NAS shall have its measured RSRP
value. Once PLMN (high quality or otherwise) is selected, UE access stratum will
be instructed to measure reference signal and read the PDSCH for SIB1. This
process occurs again to initiate cell selection using the S-Criteria (based on
Q_RX_LEV_MIN). At this stage if the S-criteria is not met, UE will go into
limited service (for emergency calls) or will find an equivalent PLMN.
The following figure shows the idle mode state procedure:
Selected PLMN available/unavailable: The UE scans all RF channels in

EUTRAN band according to its capabilities to find available PLMNs.
Not camped: No suitable cell found.
Camped normally: The UE obtains normal service and performs the following
tasks:
oSelect and monitor the PCH of the cell.
oPerforms system information monitoring.
oPerform necessary measurements for the cell reselection evaluation
procedure.
oExecute the cell reselection evaluation procedure.
Camped on any cell: The UE obtains limited service and periodically searches for
a suitable cell in the selected PLMN, if UE supports.
Cell selection: The UE selects a suitable cell and the radio access mode based on
idle mode measurements and cell selection criteria.
Cell reselection: If after cell reselection evaluation process a better cell is found,
the cell reselection is performed. If no suitable cell is found, UE enters to the
next state 'Any cell selection'.
Any cell selection: The UE searches an acceptable cell of any PLMN to camp on
The following table shows the parameters for PLMN selection:
Parameter Name Description

Q_RX_LEV_MIN Minimum required RX level in the cell (dBm) (SIB1)
PLMN MCC and MNC (SIB1)
Cell Selection
Initial Cell Selection
The following figure shows initial cell selection procedures:
The UE scans all RF channels in E-UTRAN bands to its capability to find

acceptable cells, which are not barred and measure RSRP value greater than or
equal to -110 dBm. To read PLMN identity and decide the availability of the cell,
UE shall detect Primary/Secondary synchronization signals (PSS/SSS) and decode
cell specific reference signal (CRS) and read at least MIB and SIB1. PCID should
not be overlapped between adjacent cells for successful detecting and decoding of
the signals. The PLMN reading will be reported to NAS layer, and the search for
PLMNs may be stopped on request of NAS.
Once UE has selected the PLMN, the cell selection procedure shall be performed
to select a suitable cell of that PLMN to camp on to access available services, as
described in TS36.304. If UE has stored information of carrier frequencies and
also (optionally) information on cell parameters from previously received
measurement, UE can use this information to speed up the selection procedure.
The suitable cell should satisfy that:
The cell is not barred
The cell is part of the selected PLMN or the registered PLMN or a PLMN of an
equivalent PLMN list
The cell is part of at least one TA that is nor port of the list of 'forbidden tracking
areas for roaming'
The cell selection criterion S satisfies that Srxlev > 0 AND Squal > 0
Priorities between different frequencies or RATs provided to UE by system
information or dedicated signaling are not used in the cell selection procedure.
Cell Barring
The LTE E-UTRAN cells broadcast cell selection information through SIB1 and
SIB2 (AC-Barring).
SIB1 has two fields for cell status indication:
cellBarred
cellReservedForOperatorUse
cellBarred is common for all PLMNs and cellReservedForOperatorUse is specific
per PLMN.
When cell status is indicated as 'not barred' and 'not reserved' for operator use, all
UEs shall treat this cell as candidate during the cell selection and cell reselection
procedures.
When cell status is indicated as 'not barred' and 'reserved' for operator use for any
PLMN,
The UEs assigned to Access Class 11 or 15 operating in their HPLMN/EHPLMN
shall treat this cell as candidate during the cell selection and reselection
procedures if the field cellReservedForOperatorUse for that PLMN set to
'reserved'.
The UEs assigned to an Access Class in the range of 0 to 9, 12 to 14 shall behave
as if the cell status is 'barred' in case the cell is 'reserved for operator use' for
the registered PLMN or the selected PLMN.
When cell status 'barred' is indicated or to be treated as if the cell status is 'barred',
UE is not permitted to select/reselect this cell, not even for emergency calls.
Cell Selection Criteria
The cell selection is performed on the detected cell with RX signal and decoded
MIB and SIBs.
Cell selection criteria:
Srxlev > 0 AND Squal > 0
Where, Srxlev = Qrxlevmeas - (Q_RX_LEV_MIN + Q_RXLEV_MIN_OFFSET) -
Pcompensation, Squal = Qqualmeas - (Q_QUAL_MIN + Q_QUAL_MIN_OFFSET)
The following table shows the parameters of cell selection criteria:
Srxlev Cell selection RX level value (dB)
Squal Cell selection quality value (dB)
Qrxlevmeas Measured cell RX level value (RSRP)
Qqualmeas Measured cell quality value (RSRQ)
Q_RX_LEV_MIN Minimum required RX level in the cell (dBm) (SIB1)
Q_QUAL_MIN Minimum required quality level in the cell (dB) (SIB1)
Q_RXLEV_MIN_OFFSET Offset to the signalled Q_RX_LEV_MIN taken into account in the Srxlev
evaluation as a result of a periodic search for a higher priority PLMN while
camped normally in a VPLMN (SIB1)
Q_QUAL_MIN_OFFSET Offset to the signalled Q_QUAL_MIN taken into account in the Squal

evaluation as a result of a periodic search for a higher priority PLMN while
camped normally in a VPLMN (SIB1)
Pcompensation Max (PEMAX -PPowerClass, 0) (dB)
P_MAX Maximum TX power level an UE may use when transmitting on the uplink in
the cell (dBm) defined as P_MAX in [TS 36.101] (SIB1)
PPowerClass Maximum RF output power of the UE (dBm) according to the UE power class
as defined in [TS 36.101]
Since Q_QUAL_MIN and Q_QUAL_MIN_OFFSET are not provided in network,

devices will test Srxlev only.
If q-QualMinWB (in SIB1/SIB3/SIB5) is present, UE shall, when performing
RSRQ measurement, use a wider bandwidth.
Cell Reselection
The following figure shows initial cell reselection procedures:
When a cell reselection condition is met, UE in idle mode shall attempt to detect,
synchronize, and read system information of candidate frequencies. 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 UE has a priority
provided.
The cell reselection procedures are triggered when one of the following conditions
is met:
1 The serving cell does not fulfill Srxlev > S_INTRA_SEARCH_P and Squal >
S_INTRA_SEARCH_Q. In this case, UE performs intra-frequency cell
reselection procedures.
2 The UE has E-UTRA frequencies or UTRA frequencies with a reselection
priority higher than the reselection priority of the current E-UTRA frequency.
In this case, UE performs inter-RAT cell reselection procedures. The UE shall
search every layer of higher priority at least every Thigher_priority_search = (60 *
Nlayers) seconds, where Nlayers is the total number of configured higher priority
E-UTRA, UTRA carrier frequencies. (3GPP TS36.133 Section 4.2.2)
3 The service cell does not fulfil Srxlev > S_NON_INTRA_SEARCH_P and Squal
> S_NON_INTRA_SEARCH_Q. In this case, UE performs inter-RAT cell
reselection procedures for E-UTRA inter-frequency or UTRA frequency with
an equal or lower reselection priority than the reselection priority of the
current E-UTRA frequency.
Since RSRQ related parameters are not provided in network, devices will test
Srxlev only. The device will use S_INTRA_SEARCH and
S_NON_INTRA_SEARCH instead of S_INTRA_SEARCH_P and
S_NON_INTRA_SEARCH_P respectively.
The following table shows the parameters that trigger cell reselection procedures:
Srxlev Cell selection RX level value (in dB) measured by UE
Squal Cell selection quality value (in dB) measured by UE
S_INTRA_SEARCH This specifies the Srxlev threshold (in dB) for intra-frequency measurements.
This parameter is used by Rel-8 device (SIB3).
S_INTRA_SEARCH_P This specifies the Srxlev threshold (in dB) for intra-frequency measurements.
S_INTRA_SEARCH_Q This specifies the Squal threshold (in dB) for intra-frequency measurements.
S_NON_INTRA_SEARCH This specifies the Srxlev threshold (in dB) for E-UTRAN inter-frequency and
inter-RAT measurements. This parameter is used by Rel-8 device (SIB3).
S_NON_INTRA_SEARCH_P This specifies the Srxlev threshold (in dB) for E-UTRAN inter-frequency and
inter-RAT measurements. This parameter is used by Rel-9 device (SIB3).
S_NON_INTRA_SEARCH_Q This specifies the Squal threshold (in dB) for E-UTRAN inter-frequency and
inter-RAT measurements. This parameter is used by Rel-9 device. (SIB3).
Q_RX_LEV_MIN This specifies the minimum required Rx level in the cell in dBm (SIB3).
Q_QUAL_MIN_REL9 This specifies the minimum required quality level in the cell in dB. This
parameter is used by Rel-9 device (SIB3).
Thresholds and Priority Design

In network, cell reselection triggering thresholds and priority shall be configured.
Dur to that, UEs can select LTE network as a primary network in the presence of
an acceptable LTE signal. In network, RSRP is used as a measurement triggering
criteria because RSRQ can vary even in the center of the serving cell from -3 dB to
-10 dB depending on traffic load from the serving cell. S_INTRA_SEARCH shall
be greater than S_NON_INTRA_SEARCH so that LTE capable UEs can select
LTE frequency as long as it moves under LTE coverage.
The following figure shows the thresholds for cell reselection:
The UE triggers measurement of intra-frequency when the RSRP signal strength

from LTE serving cell decreases below the threshold calculated as follows:
RSRP Strength from Serving Cell =< S_INTRA_SEARCH + Q_RX_LEV_MIN
+ Q_RXLEV_MIN_OFFSET + Pcompensation
Where, Pcompensation is max (PEMAX -PPowerClass, 0) (dB). PEMAX is defined as PMAX in
3GPP TS36.101, and PPowerClass is 23 dBm as per 3GPP TS36.101. (118
dBm).Therefore, Pcompensation is usually assumed to be 0.
The UE triggers measurement of UTRA frequency when the RSRP signal strength
from LTE serving cell decreases below the threshold calculated as follows:
RSRP Strength from Serving Cell =< S_NON_INTRA_SEARCH +
Q_RX_LEV_MIN + Q_RXLEV_MIN_OFFSET + Pcompensation
The UE will start measurements of LTE frequency when the measured RSRP is
less than -64 dBm [Q_RX_LEV_MIN=-63(-126 dBm),
Q_RXLEV_MIN_OFFSET=0, S_INTRA_SEARCH=31(62 dB), Pcompensation=0],
and start the measurements of UTRA frequency when the measured RSRP is less
than -112 dBm [Q_RX_LEV_MIN=-63(-126 dBm),
Q_RXLEV_MIN_OFFSET=0, S_NON_INTRA_SEARCH=7(14 dB),
Pcompensation=0).
In order for UEs to select primarily LTE frequency when UEs end a CSFB call or
when UEs come back into LTE coverage, LTE frequency priority must be greater
than UTRA frequency.
The priority of each frequency is broadcasted in SIB3 (E-UTRA frequency).
Intra-Frequency Cell Reselection
Intra-frequency cell reselection is performed when the signal strength from LTE
serving cell is less than the threshold as described above. The cell reselection is
performed on ranking basis of the current and neighboring cells.
Cell Reselection Criteria:
Rs = Qmeas,s + Q_HYST
Rn = Qmeas,n - Q_OFFSET_FREQ
The following table shows the description of above mentioned parameters:
Rs Rs is for serving cell.
Rn Rn is for neighbour cell.
Qmeas RSRP measurement quantity used in cell reselections.
Q_HYST This parameter (in dB) is to reduce Ping-Pong effects between serving and
neighbor cells.(SIB3)
Q_OFFSET_FREQ In case of intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is valid, otherwise this
equals to zero.
T_RESELECTION This specifies the reselection timer value for EUTRAN (SIB3).
The UE shall perform ranking of all cells that fulfill the cell selection criterion S.
The cells shall be ranked according to the R criteria specified above, deriving
Qmeas,n and Qmeas,s and calculating the R values using averaged RSRP results. If a
cell is ranked as the best cell, UE shall perform cell reselection to that
corresponding cell.
The UE shall 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
T_RESELECTION.
More than 1 second has elapsed since UE camped on the current serving cell.
Initial Attach
When UE camps on a suitable cell, if new cell does not belongs to at least tracking
areas to which UE is registered previously, the UE will register to the network by
sending a Tracking Area Update message.
The following figure shows the initial attach procedures:
1~4) Step 2~4 completes RRC connection establishing of a SRB. The attach
procedure starts with RRC connection establishment procedure. The Attach
Request message included in RRCConnectionSetupComplete is transparently
delivered to MME in INITIAL UE MESSAGE.
5~9) The eNB sends INITIAL UE MESSAGE to MME, then MME responds with
INITIAL CONTEXT SETUP REQUEST after selecting S-GW.
10~12) The eNB acquires UECapabilityInformation and reports it to MME.
13~14) The eNB sends the integrity-protected AS Security Mode Command
message to UE. Then, UE starts control plane signalling integrity.
15~16) The eNB sends RRCConnectionReconfiguration message to data radio

bearer. After eNB receives CONTEXT SETUP REQUEST message from MME, it
creates a default radio bearer by sending RRCConnectionReconfiguration message
to UE. When UE receives RRCConnectionReconfiguration message, it can
transmit packets in uplink and eNB can deliver the packets toward S-GW.
17) The eNB sends Initial Context Setup Response message to MME and
completes the establishment of S1 bearer.
18~19) The UE sends ULInformationTransfer message to eNB, which includes
Attach Complete message. This message is transparently delivered to MME in
UPLINK NAS TRANSPORT message.
20~21) The MME sends Modify Bearer Request message to S-GW, to provide
downlink tunnel information of eNB. After S-GW receives the Modify Bearer
Request message, it can transmit packets in downlink.
If both DRB and SRB carry no packets in downlink and uplink for a certain time
period, eNB releases the RRC connection and S1 bearer. The operator can
configure INTERNAL_SIGNALING_INACTIVITY for a signalling bearer and
INTERNAL_USER_INACTIVITY for a data bearer at eNB level.
When both inactivity timers expire, eNB sends UE CONTEXT RELEASE
message to MME and releases the S1 connection for UE. Also, this message shall
indicate the cause value 'User Inactivity'.
The following figure shows the connection release procedure by the inactivity
timer triggered:
Combined EPS and IMSI Attach

When supporting Combined EPS/IMSI Attach Request, MME selects IWF
(MSC/VLR) based on TA and LA mapping and sends the location update request
with new LAI, IMSI and MME name to IWF. On receiving the request of the
respective VLR will create an association for SGs interworking with MME. In
response, VLR will provide VLR TMSI to MME.
The following figure shows the combined EPS/IMSI attach call flow:
The combined EPS/IMSI Attach procedures are:

1~5) The UE sends an Attach Request to MME with Attach Type as Combined
EPS/IMSI, UE capability as CSFB and data APN name. The APN name is
depending on the subscriber type. The UE may include any of the Internet APN.
6) The MME sends authentication information request message to HSS. After
receiving the Authentication Information Answer from HSS, MME and UE are
authenticated each other with set of authentication messages between UE and
MME. After the successful authentication, MME updates the subscriber location in
HSS and gets the subscriber profile from HSS.
7~8)The MME sends Create Session Request message to S-GW for establishing
the default bearer for UE. The S-GW forwards the session request message to P-
GW. The P-GW replies with the Create Session Response to MME.
9~10) Since UE has requested for combined EPS/IMSI attach, after the default
bearer establishment MME updates UEs location in 3G network by sending the
location update message with new LAI, IMSI and MME name to IWF
(MSC/VLR). After accepting the attach request by the network, default bearer will
be established. IWF updates UEs CS location in HLR.
11~14) The eNB acquires UECapabilityInformation and reports it to MME.
15~16) The eNB sends the integrity-protected AS Security Mode Command
message to UE. Then, UE starts control plane signalling integrity.
17~18) The eNB sends RRCConnectionReconfiguration message to data radio
bearer. After eNB receives CONTEXT SETUP REQUEST message from MME, it
creates a default radio bearer by sending RRCConnectionReconfiguration message
to UE. When UE receives RRCConnectionReconfiguration message, it can
transmit packets in uplink and eNB can deliver the packets toward S-GW.
19) The eNB sends Initial Context Setup Response message to MME and
completes the establishment of S1 bearer.
20~21) The UE sends ULInformationTransfer message to eNB, which includes
Attach Complete message. This message is transparently delivered to MME in
UPLINK NAS TRANSPORT message.
22~23) The MME sends Modify Bearer Request message to S-GW, to provide
downlink tunnel information of eNB. After S-GW receives the Modify Bearer
Request message, it can transmit packets in downlink.
Combined EPS and IMSI Detach
To detach the combined EPS/IMSI attached UE, the UE is required to be detached
from both EPS and CS domain.
The following figure shows the combined EPS/IMSI detach call flow:
The combined EPS/IMSI Detach procedures are:

1~2) The UE sends Detach Request to MME.

3) The MME sends Delete Session Request message to S-GW for deactivating the
default bearer for UE. The S-GW forwards the Delete Session Request message to
P-GW.
4) The IMSI Detach Indication message from MME to IWF (MSC/VLR) so as to
remove the SGs association with regarding to UE IMSI.
5) The P-GW replies with Delete Session Response to MME.
6~8) The MME sends Detach Accept to UE and releases S1-MME signalling
connection.
Related SIB Messages
SIB2 contains radio resource configuration information that is common for all UEs.
The following table shows the SIB2 message:
ac-BarringInfo ac-BarringForEmergency
ac-BarringForMO-Signalling (TAU, Attach/Detach message)
ac-BarringforMO-Data (Service Request, Extended Service Request
messages)
freqInfo ul-CarrierFreq
ul-Bandwidth
additionalSpectrumEmission
radioResourceConfigCommonSIB rach-config, bcch-config, pcch-config, prach-config, pdsch-config,
pusch-config, and pucch-config
UL-CyclicPrefixLength
uplinkPowerControlCommon
ue-TimersAndConstants
timeAlignmentTimerCommon (to control how long UE is considered uplink time aligned)
mbsfn-SubframeConfigLit
SIB3 contains cell re-selection information common for intra-frequency, inter-

frequency and/ or inter-RAT cell re-selection.
cellReselectionInfoCommon q-Hyst
speedStateReselectionPars (Q-hysteresis scaling factor depending
on UE speed)
cellReselectionServingFreqInfo s-NonIntraSearch
threshServingLow
cellReselectionPriority
intraFreqCellReselectionInfo q-RxLevMin
P-max (maximum uplink tx power of UE for the intra-frequency
neighbouring E-UTRA cells)
s-IntraSearch
allowedMeasBandwidth
neighCellConfig (MBSFN and TDD related information)
t-ReselectionEUTRA (cell reselection timer, it can be set per E-
UTRAN frequency)
t-ReselectionEUTRA-SF (speed dependent scale factor)
SIB4 contains neighbouring cell related information relevant only for intra-
frequency cell re-selection. Also, it includes cells with specific re-selection
parameters as well as blacklisted cells.
intraFreqNeighbCellList (List of intra- physCellId
frequency neighbouring cells with q-OffsetCell (Qoffsets,n, the offset between the two cells)
specific cell re-selection parameters, up
to 16)
intraFreqBlackCellList (List of blacklisted intra-frequency neighbouring cells, up to 16)
SIB5 contains information for inter-frequency cell re-selection.

InterFreqCarrierFreqInfo (list of dl-CarrierFreq
frequency information up to 8) q-RxLevMin
p-Max
t-ReselectionEUTRA
t-ReselectionEUTRA-SF
threshX-High (cell reselection to a cell on a higher priority E-
UTRAN frequency or inter-RAT frequency than the serving
frequency if a cell of a higher priority RAT/ frequency fulfils Srxlev
> ThreshX, HighP during a time interval TreselectionRAT)
threshX-Low (cell reselection to a cell on a lower priority E-UTRAN
frequency or inter-RAT frequency than the serving frequency if
the serving cell fulfils Srxlev < ThreshServing, LowP and a cell of
a lower priority RAT/ frequency fulfils Srxlev > ThreshX, LowP
during a time interval TreselectionRAT)
allowedMeasBandwidth
presenceAntennaPort1 (to indicate whether all the neighbouring
cells use Antenna Port 1)
cellReselectionPriority
neighCellConfig (MBSFN and TDD related information)
q-OffsetFreq (Qoffsetfrequency, Frequency specific offset for equal
priority E-UTRAN frequencies)
interFreqNeighCellList (up to 16)
physCellId
q-OffsetCell (Qoffsets,n , the offset between the two cells)
interFreqBlackCellList (up to 16)
SYSTEM OPERATION
How to Activate
The Idle Mobility Support is a collective feature with which UE in Idle State
(Mode) selects a network or a carrier. But, the following key parameters control
the selection criteria of the cell which UE selects. Also, the settings of Command
and Parameter can control the system information message of E-UTRAN.
Key Parameters
RTRV-EUTRA-FA/CHG-EUTRA-FA
PRIORITY This is a parameter specifying the priority of EUTRA-FA during idle reselection
or mobility control information. '7' is the highest priority. Ensure that not to set
the same priority when configuring multiple EUTRA-FAs.
Q_RX_LEV_MIN This parameter is minimum RX level required in a cell that is operating as
EUTRA-FA and its unit is dBm.
T_RESELECTION This parameter is the interval (timer) of reselection execution.
T_RESELECTION_SF_MED This parameter is the medium timer value of the reselection scaling factor.
IUM
T_RESELECTION_SF_HIG This parameter is the high timer value of the reselection scaling factor.
H
S_INTRA_SEARCH This parameter is the threshold value for intra-frequency measurement.
S_NON_INTRA_SEARCH This parameter is the threshold value for the inter-RAT and inter-frequency
measurement.
THRESH_SERVING_LOW This parameter is the low threshold for serving frequency upon reselection
evaluation.
THRESH_X_HIGH This parameter is the threshold value used by UE when reselecting the
frequency with priority higher than the currently camped frequency.
THRESH_X_LOW This parameter is the threshold value used when reselecting the low-priority
frequency from the high-priority frequency.
Q-OFFSER-FREQ This parameter is the frequency offset applied to the q-OffsetFreq of a SIB5
message.
S_INTRA_SEARCH_P This parameter is the threshold-P value for the intra-frequency measurement of
Rel-9.
S_INTRA_SEARCH_Q This parameter is the threshold-Q value for the intra-frequency measurement
of Rel-9.
S_NON_INTRA_SEARCH_ This parameter is the threshold-P value for the inter-frequency measurement
P and Inter-RAT.
S_NON_INTRA_SEARCH_ This parameter is the threshold-Q value for the inter-frequency measurement
Q and Inter-RAT.
Q_QUAL_MIN_REL9 This parameter is the qQualMin value for Rel-9.
THRESH_SERVING_LOW_ This parameter is the threshServingLowQ value for Rel-9.
Q_REL9
THRESH_XHIGH_Q_REL9 This parameter is the threshold value used by UE when reselecting the
frequency with priority higher than the currently camped frequency in the Rel-9.
THRESH_XLOW_QREL9 This parameter is the threshold value used when reselecting the low-priority
frequency from the high-priority frequency in the Rel-9.
RTRV-CELL-RSEL/CHG-CELL-RSEL
Q_HYST The cell number. This value must not exceed the maximum number of cells
supported by the system.
Q_HYST_SFMEDIUM This parameter is the value added when UE speed is medium among Qhyst
values that are added to the current serving
cell in the cell reselection criteria. To apply the change of this parameter, the
SPEED_STATE_RESEL_PARAMS_USAG E should be changed to use in the
CHGMOBIL-STA beforehand.
Q_HYST_SFHIGH This parameter is the value added when UE speed is high among Qhyst values
that are added to the current serving cell in the cell reselection criteria. To
apply the change of this parameter, the
SPEED_STATE_RESEL_PARAMS_USAG E should be changed to use in the
CHGMOBIL-STA beforehand.
Counters and KPIs

REFERENCE
Resource Control (RRC) protocol specification
Equipment (UE) procedures in idle mode
LTE-SW1004, S1 Handover
INTRODUCTION
S1 handover is mobility control functionality between two adjacent eNBs using S1
interface with MME (inter-eNB handover via S1 interface). S1 handover is used
when there is no available direct interface with target eNB, or target eNB belongs
to another MME group.
BENEFIT
The operator can provide connected mobility to its subscribers between cells in
different eNBs.
Users in a connected state can be moving within E-UTRAN, with change of
serving cell.

Limitation
With Full Configuration, Hyper Frame Number (HFN) is reset for all bearers and
lossless HO is not supported.
FEATURE DESCRIPTION
The following figure shows the S1 handover procedure in E-UTRAN (S1
handover with MME and S-GW relocation case):
1) The UE sends MEASUREMENT REPORT including E-UTRAN measurements

to the source eNB.
2) The source eNB determines whether to perform S1-based handover into the
target eNB. This decision can be initiated if there is no X2 connection to target
eNB or inter-eNB handover of target eNB is configured to execute the S1
handover.
Handover decision in case of PCI duplication: On reception of MR message, eNB
checks whether PCI from MR exists in Neighbor NRT or not. If there are several
NRs with same PCI (this case is called PCI duplication), then eNB requests UE for
measurement with the purpose set to report CGI. After obtaining MR message
including ECGI, eNB triggers Handover Preparation using NR of the reported
ECGI.
3) The source eNB sends HANDOVER REQUIRED to source MME. The source
eNB provides information about which bearer is used for data forwarding and
whether direct forwarding is possible from source eNB to target eNB.
4)~6) The MME transmits the HANDOVER REQUEST message to target eNB.
This message creates UE context which has bearer related information and security
context in the target eNB.
7) The target eNB transmits the HANDOVER REQUEST ACKNOWLEDGE
message to MME
8)~10) If indirect forwarding is used, MME transmits the Create Indirect Data
Forwarding Tunnel Request message to S-GW.
The S-GW replies to MME with the Create Indirect Data Forwarding Tunnel
Response message.
11) The source eNB receives the HANDOVER COMMAND from source MME.
12) The source eNB creates the RRCConnectionReconfiguration message using
the Target to Source Transparent Container IE included in the HANDOVER
COMMAND message and transmits it to UE.
To transmit the PDCP status and the HFN status of the E-RABs of which the
PDCP status must be preserved, source eNB transmits eNB/MME STATUS
TRANSFER message to target eNB via MME.
The source eNB must start forwarding downlink data to target eNB through the
bearer, which is planned to be used for data forwarding. This can be either direct
or indirect forwarding.
The UE performs synchronization to target eNB and connects to target cell
through RACH. The target eNB replies with UL allocation and timing advance.
13) After successful synchronization with the target cell, UE notifies the target cell
that the handover procedure is complete using the
RRCConnectionReconfigurationComplete message. The downlink packet
forwarded from source eNB can be transmitted to UE. The uplink packet can be
transmitted to S-GW from UE through target eNB
14)~16) The target eNB sends a HANDOVER NOTIFY message to MME to
inform that UE has changed cell.
17~18) The MME transmits the Modify Bearer Request message to S-GW per
each PDN connection.
The downlink packet from S-GW is immediately transmitted to target eNB.

19) The S-GW transmits the Modify Bearer Response message to MME. To
support packet re-arrangement in target eNB, S-GW transmits at least one end
marker packets to the previous path as soon as the path is changed.
20) If any of the conditions listed in Section 5.3.3.0 of TS 23.401 (6) is met, UE
starts the Tracking Area Update procedure.
21)~24) The source MME releases UEs resources that was used in the source
eNB and the resources for data forwarding.
Full Configuration
The full configuration option is used to support EUTRA handover to eNB of an
earlier release. The target uses a full configuration and previous configuration is
discarded by UE. This can lead to a change in RLC mode for a bearer and the
operation for RLC AM is the same as that for RLC UM. HFN is reset for all
bearers. Since source eNB may not be aware that target eNB is using full
configuration, there is no difference in source eNB behaviour. The target eNB
does not resend data that was attempted delivery to UE to prevent data duplication.
The source eNB includes ue-ConfigRelease IE in HandoverPreparationInformation
message, ue-ConfigRelease IE indicates the RRC protocol release used for UE
specific dedicated configuration. If target eNB does not support the release of RRC
protocol which source eNB used to configure UE, target eNB may be unable to
comprehend UE configuration provided by source eNB. In this case, target eNB
should use the full configuration option to reconfigure UE for Handover and Re-
establishment. Full configuration option includes an initialization of the radio
configuration, which makes the procedure independent of the configuration used in
the source cell with the exception that the security algorithms are continued for the
RRC re-establishment. In case of reconfigurations involving the full configuration
option, the PDCP entities are newly established (SN and HFN do not continue) for
all DRBs irrespective of the RLC mode.
The UE deletes current configuration and applies new configuration based on the
configuration provided by target eNB. Security configuration is retained and
security algorithm is retained for re-establishment. SRBs are reconfigured. DRBs
are released and re-setup using new configuration.
SYSTEM OPERATION
How to Activate
Select 1 event to use to activate S1 Handover.
ACTIVE_STATE of CHG-EUTRA-A3CNF with PURPOSE
A3PurposeIntraLteHandover set to active or ACTIVE_STATE of CHG-
EUTRA-A5CNF with PURPOSE A5PurposeIntraLteHandover set to active
A3 event is preferred.
Set NO_HO of CHG-NBR-ENB to false. It is controlled by NBR eNB base.
Key Parameters
CHG-EUTRA-A3CNF/RTRV-EUTRA-A3CNF
PURPOSE The purpose for using Event A3. It is currently used for intra-LTE handover and
the SON ANR function.
IntraLteHandover
ReportStrongestCells
IntraFrequencyLb
CaInterFreq
ACTIVE_STATE Whether to use Event A3.
Inactive: Event A3 is not used.
Active: Event A3 is used.
A3_OFFSET RSRP threshold used for triggering the EUTRA measurement report for Event
A3.
TIME_TO_TRIGGER timeToTrigger value for Event A3. The time-ToTrigger value is the period of
time that must be met for UE to trigger a measurement report.
TRIGGER_QUANTITY Quantity (RSRP/RSRQ) used to calculate a triggering condition for Event A3.
Either RSRP or RSRQ is assigned.
PURPOSE The purpose for using Event A5. Not in current use. The definition is made for
later use.
ci_A5PurposeIntraLteHandover: Intra-LTE handover.
ci_A5PurposeSpare_1: Reserved.
ci_A5PurposeSpare_2: Reserved.
ACTIVE_STATE Whether to use the Event A5.
A5_THRESHOLD1_RSRP RSRP threshold1 used for triggering the EUTRA measurement report for Event
A5.
A5_THRESHOLD2_RSRP RSRP threshold2 used for triggering the EUTRA measurement report for Event
A5.
time that must be met for the UE to trigger a measurement report.
TRIGGER_QUANTITY This parameter is used to set up the TriggerQuantity of Event A5 during
ReportConfigEutra configuration. The triggerQuantity can be set to
rsrp/rsrq/followA2Event. The UE transmits Event A5 when RSRP or RSRQ
meets a specific threshold according to triggerQuantity. If the triggerQuantity is
RSRP, the A5_THRESHOLD_RSRP is used. If it is RSRQ, the
A5_THRESHOLD_RSRQ is used. If the triggerQuantity is followA2Event, It will
follow the triggerQuantity of the previously received A2 event with handover
purpose. (it is noted that this configuration is only available if the A5 purpose is
handover related case, that is, A5PurposeIntraLteHandover) This change will
be applied to UE from next RRC signaling procedure (for example, Attach or
Idle to Active). To avoid overload, a new setting will not be updated to the
current active UEs.
rsrp: The trigger quantity of this event is set RSRP.
rsrq: The trigger quantity of this event is set RSRQ.
followA2Event: The trigger quantity of this event follows the trigger quantity of
the previously received A2 event.
CHG-NBR-ENB/RTRV-NBR-ENB/CRTE-NBR-ENB/DLT-NBR-ENB
NO_X2 Whether to make X2 connection to neighbor eNB.
False: X2 connection to neighbor eNB is made.
True: X2 connection to neighbor eNB is not made.
NO_HO Whether to perform handover to the neighbor eNB.
False: Handover to neighbor eNB is performed.
True: Handover to neighbor eNB is not performed.
Counters and KPIs

S1 Out Handover InterS1OutAtt The number of attempts for S1 handover in SeNB
InterS1OutPrepSucc The number of successes for S1 handover
preparation in SeNB
InterS1OutSucc The number of successes for S1 handover
execution in SeNB
InterS1OutPrepFail_CpC Preparation fails due to reset notification (eNB
cFail failure or block restart) from ECMB or by ECCB
block during inter S1 handover preparation.
InterS1OutPrepFail_S1a Preparation fails due to S1AP specification cause
pCuFail during inter S1 handover preparation.
InterS1OutPrepFail_S1a Preparation fails due to S1 SCTP link failure
pLinkFail during inter S1 handover preparation.
InterS1OutPrepFail_S1a Preparation fails due to S1AP relocprep timeout
pRpTo (not received) during the inter S1 handover
preparation.
InterS1OutPrepFail_S1a Preparation fails due to receiving S1AP signaling
pSigFail during inter S1 handover preparation.
InterS1OutFail_CpCcTo A call is released due to call control timeout in the
protocol blocks (MAC, RLC, PDCP, GTP) during
the inter S1 handover execution.
InterS1OutFail_CpCcFail A call is released due to reset notification (eNB
failure or block restart) from ECMB or by ECCB
block during the inter S1 handover execution.
InterS1OutFail_UpGtpFai A call is released due to the failure in the GTP
l block during the inter S1 handover execution.
InterS1OutFail_UpMacF A call is released due to the failure in the MAC
ail block during the inter S1 handover execution.
InterS1OutFail_UpPdcpF A call is released due to the failure in the PDCP
ail block during the inter S1 handover execution.
InterS1OutFail_UpRlcFai A call is released due to the failure in the RLC
InterS1OutFail_RrcSigFa A call is released due to receiving RRC signaling
il during the inter S1 handover execution.

InterS1OutFail_S1apCuF A call is released due to the S1AP specification
ail cause during the inter S1 handover execution.
InterS1OutFail_S1apLink A call is released due to the S1 SCTP link failure
Fail during the inter S1 handover execution.
InterS1OutFail_S1apRoT A call is released due to S1AP relocoverall timeout
O (not received) during the inter S1 handover
execution.
InterS1OutFail_S1apSig A call is released due to receiving S1AP signaling
Fail during the inter S1 handover execution.
InterS1OutCnt S1 Handover Out collection count
InterS1OutCid tcID of which collection is requested
S1 In Handover InterS1InAtt S1 handover attempt count in TeNB
InterS1InPrepSucc S1 handover preparation success count in TeNB
InterS1InSucc S1 handover execution success count in TeNB
InterS1InPrep_FailCpCc Preparation fails due to call control timeout in the
To protocol blocks (MAC, RLC, PDCP, and GTP)
during the inter S1 handover preparation.
InterS1InPrep_FailCpCc Preparation fails due to reset notification (eNB
Fail failure or block restart) from ECMB or by ECCB
block during inter S1 handover preparation.
InterS1InPrep_FailUpGtp Preparation fails due to internal failure in the GTP
Fail block during the inter S1 handover preparation.
InterS1InPrep_FailUpMa Preparation fails due to internal failure in the MAC
cFail block during the inter S1 handover preparation.
InterS1InPrep_FailUpPd Preparation fails due to internal failure in the
cpFail PDCP block during the inter S1 handover
preparation.
InterS1InPrep_FailUpRlc Preparation fails due to internal failure in the RLC
Fail block during the inter S1 handover preparation.
InterS1InPrep_FailCpBh Preparation fails due to insufficient backhaul-
CacFail based eNB resources during inter S1 handover
preparation.
InterS1InPrep_FailCpCa Preparation fails due to insufficient capacity-based
paCacFail eNB resources during inter S1 handover
preparation.
InterS1InPrep_FailCpQo Preparation fails due to insufficient QoS-based
sCacFail eNB resources during inter S1 handover
preparation.
InterS1InPrep_FailS1ap Preparation fails due to S1AP specification cause
CuFail during inter S1 handover preparation.
InterS1InPrep_FailS1apL Preparation fails due to S1 SCTP link failure
inkFail during inter S1 handover preparation.
InterS1InPrep_FailS1ap Preparation fails due to receiving S1AP signaling
SigFail during inter S1 handover preparation.
InterS1InFail_CpCcTo A call is released due to call control timeout in the
protocol blocks (MAC, RLC, PDCP, GTP) during
the inter S1 handover execution.
InterS1InFail_CpCcFail A call is released due to reset notification (eNB
failure or block restart) from ECMB or by ECCB

InterS1InFail_UpGtpFail A call is released due to the failure in the GTP
InterS1InFail_UpMacFail A call is released due to the failure in the MAC
InterS1InFail_UpPdcpFai A call is released due to the failure in the PDCP
InterS1InFail_UpRlcFail A call is released due to the failure in the RLC
InterS1InFail_RrcHcTo A call is released due to HO command timeout
(not received) during the inter S1 handover
execution.
InterS1InFail_RrcSigFail A call is released due to receiving RRC signaling
during the inter S1 handover execution.
InterS1InFail_S1apCuFai A call is released due to the S1AP specification
l cause during the inter S1 handover execution.
InterS1InFail_S1apLinkF A call is released due to the S1 SCTP link failure
ail during the inter S1 handover execution.
InterS1InFail_S1apSigFa A call is released due to receiving S1AP signaling
il during the inter S1 handover execution.
InterS1InFail_S1apSigTo A call is released due to S1AP signaling timeout
(not received) during the inter S1 handover
execution.
Handover Time IntraHOTime Time taken from transmitting the
RRCConnectionReconfiguration message to UE
until after receiving the RRCConnection
ReconfigurationComplete message from UE.
IntraHOTimeMax Average maximum intra HO interrupt time
IntraHOTimeTot Sum of Intra HO Interrupt time
IntraHOTimeCnt Count of IntraHoTimeAvg collected
S1HOTime Average S1 HO interrupt time
S1HOTimeMax Average maximum S1 HO interrupt time
S1HOTimeTot Sum of S1 HO interrupt time
S1HOTimeCnt Count of S1HoTimeAvg collected
X2HOTime Average X2 HO interrupt time
X2HOTimeMax Average maximum X2 HO interrupt time
X2HOTimeTot Sum of X2 HO Interrupt time
X2HOTimeCnt Count of X2HoTimeAvg collected
HoTimeCnt Count of HoTime collected
HoTimeCid scID which collection is requested
MOBILITY (KPI) EutranMobilityHOS1Out HOIS1Out success rate of E-UTRAN mobility
sumHOS1Out_Att Total S1 handover attempt count in SeNB
sumHOS1Out_Succ Total S1 handover execution success count in
SeNB
sumHOS1Out_PrepSucc Total S1 handover preparation success count in
SeNB
EutranMobilityHOS1In HOS1In success rate of E-UTRAN mobility
sumHOS1In_Att Total S1 handover attempt count in TeNB

sumHOS1In_Succ Total S1 handover execution success count in
SeNB
sumHOS1In_PrepSucc Total S1 handover preparation success count in
TeNB
REFERENCE
LTE-SW1005, X2 Handover
INTRODUCTION
X2 handover is a handover between two adjacent eNBs using X2 interface (inter
eNB handover via X2 interface).
X2 based handover is used when:
There is an available direct interface with the target eNB
The target eNB belongs to the same MME group.
BENEFIT
The operator can provide connected mobility to its subscribers between cells in
different eNBs.
Users in a connected state can be moving within E-UTRAN, with change of
serving cell.

Limitation
With Full Configuration, HFN is reset for all bearers and lossless HO is not
supported.
FEATURE DESCRIPTION
When eNB receives a measurement report including Event A3 from UE, eNB
triggers intra-LTE handover to the best cell indicated in the measurement report.
Because handover target cell is decided by UEs measurement results for
neighbouring cells.
The eNB can transit from X2 handover to S1 handover with direct forwarding,
when X2 setup fail (cause: 'Invalid MME Group ID').
The following figure shows the X2 handover procedure in E-UTRAN:
1) The UE sends MEASUREMENT REPORT including E-UTRAN measurements

to the source eNB.
2) The source eNB determines whether to accept UE based on the
MeasurementReport message and radio resource management information.
Handover decision in case of PCI duplication: On reception of MR message, eNB
checks whether PCI from MR exists in Neighbor NRT or not. If there are several
NRs with same PCI (this case is called PCI duplication), then eNB requests UE for
measurement with the purpose set to report CGI. After obtaining MR message
including ECGI, eNB triggers Handover Preparation using NR of the reported
ECGI.
3) The source eNB transmits the HANDOVER REQUEST message and the
information necessary for handover to target eNB.
4) The target eNB performs admission control for the incoming handover request.
If accepted, target eNB prepares the handover and creates the

RRCConnectionReconfiguration message including the mobilityControlInfo IE
that communicates the source eNB to perform the handover.
The target eNB includes the RRCConnectionReconfiguration message in the
HANDOVER REQUEST ACKNOWLEDGE message and transmits it to the
source eNB. Bearer Setup list includes a list of tunnel information for receiving
forwarded data if necessary.
5) The RRC CONNECTION RECONFIGURATION for handover is constructed
by the serving eNB and is sent to UE.
To send the uplink PDCP SN receiver status and the downlink PDCP SN
transmitter status of the E-RABs of which the PDCP status must be preserved, the
source eNB sends the SN STATUS TRANSFER message to target eNB.
After receiving the RRCConnectionReconfiguration message that includes the
mobilityControlInfo IE, UE performs synchronization with target eNB and
connects to target eNB through the Random Access CHannel (RACH). The target
cell replies with UL allocation and timing advance.
6) The UE performs the handover to target cell. After UE has successfully
synchronized to target cell, it sends a RRC CONNECTION
RECONFIGURATION COMPLETE message to the target cell.
7) The target eNB sends a PATH SWITCH REQUEST message to MME to
inform that UE has changed cell.
8)~10) The MME sends the Modify Bearer Request message to S-GW. The S-GW
changes the downlink data path into the target eNB. The S-GW transmits at least
one 'end marker' to source eNB through the previous path and releases the user
plane resource for source eNB.
11) The S-GW transmits the Modify Bearer Response message to MME.
12) The MME returns the PATH SWITCH ACKNOWLEDGE message to target
eNB.
13) The target eNB sends the UE CONTEXT RELEASE message to source eNB
to notify handover has succeeded and to make source eNB release its resources.
If source eNB receives the UE CONTEXT RELEASE message, it releases the
radio resources and the control plane resources related to UE context.
14) If S-GW is relocated, MME releases UEs resource that is used in the source
S-GW.
[Enhancement]
The full configuration option is used to support EUTRA handover to eNB of an
earlier release. The target uses a full configuration and the previous configuration
is discarded by UE. This can lead to a change in RLC mode for a bearer and the
operation for RLC AM is the same as that for RLC UM. HFN is reset for all
bearers. Since source eNB may not be aware that target eNB is using full
configuration, there is no difference in source eNB behaviour. The target eNB
does not resend data that was attempted delivery to UE to prevent data duplication.
The Source eNB includes ue-ConfigRelease IE in

HandoverPreparationInformation message, ue-ConfigRelease IE indicates the
RRC protocol release used for UE specific dedicated configuration. If target eNB
does not support the release of RRC protocol which source eNB used to configure
UE, target eNB may be unable to comprehend UE configuration provided by
source eNB. In this case, target eNB should use the full configuration option to
reconfigure UE for Handover and Re-establishment. Full configuration option
includes an initialization of the radio configuration, which makes the procedure
independent of the configuration used in the source cell with the exception that the
security algorithms are continued for the RRC re-establishment. In case of
reconfigurations involving the full configuration option, the PDCP entities are
newly established (SN and HFN do not continue) for all DRBs irrespective of the
RLC mode.
The UE deletes current configuration and applies new configuration based on the
configuration provided by target eNB. Security configuration is retained and
security algorithm is retained for re-establishment. SRBs are reconfigured. DRBs
are released and re-setup using new configuration.
The general message flow is as follows:
1 The source eNB sends Handover Request message including ue-ConfigRelease

IE.
2 The target eNB sets FullConfig IE to true if ue-ConfigRelease IE is higher than
RRC Protocol release of target eNB.
3 The target eNB sends Handover Request Acknowledge message including
FullConfig IE.
4 The source eNB forwards RRC Connection Reconfiguration message to UE.
5 The source eNB transmits RRC Connection Reconfiguration Complete message
to Target eNB.
6 The UE deletes current configuration of source eNB and applies new

configuration provided by target eNB except security configuration.
SYSTEM OPERATION
How to Activate
Select 1 event to use to activate X2 Handover.
ACTIVE_STATE of CHG-EUTRA-A3CNF with PURPOSE
A3PurposeIntraLteHandover set to active or ACTIVE_STATE of CHG-
EUTRA-A5CNF with PURPOSE A5PurposeIntraLteHandover set to active
A3 event is preferred.
Set NO_X2 of CHG-NBR-ENB to false. It is controlled by NBR eNB base.
Key Parameters
PURPOSE The purpose for using Event A3. It is currently used for intra-LTE handover and
the SON ANR function.
ci_A3PurposeReportStrongestCells
ci_A3PurposeIntraFrequencyLb.
ci_A3PurposeCaInterFreq
ci_A3PurposeIntraFrequencyCre
ci_A3PurposePeriodicMr
ACTIVE_STATE Whether to use Event A3.
A3_OFFSET RSRP threshold used for triggering EUTRA measurement report for Event A3.
PURPOSE The purpose for using Event A5. Not in current use. The definition is made for
later use.
ci_A5PurposeCaInterFreq: CaInterFreq.
ci_A5PurposeMbms: InterFrequencyMbms.
ci_A5PurposeArpHandover: ArpHandover.
ci_A5PurposeOnDemandHO: OnDemandHandover.
ci_A5PurposeInterFrequencySPID: InterFrequencySPID.
ci_A5PurposeSpare_2: reserved.
ACTIVE_STATE Whether to use the Event A5.
A5_THRESHOLD1_RSRP RSRP threshold1 used for triggering EUTRA measurement report for Event
A5.
A5_THRESHOLD2_RSRP RSRP threshold2 used for triggering EUTRA measurement report for Event
A5.
CHG-NBR-ENB/RTRV-NBR-ENB/CRTE-NBR-ENB/DLT-NBR-ENB
NO_X2 Whether to make X2 connection to neighbor eNB.
False: X2 connection to neighbor eNB is made.
True: X2 connection to neighbor eNB is not made.
NO_HO Whether to perform handover to neighbor eNB.
False: Handover to neighbor eNB is performed.
True: Handover to neighbor eNB is not performed.
Counters and KPIs

Name
X2 Handover Out InterX2OutAtt Attempt count for X2 handover from SeNB.
InterX2OutPrepSucc Success count for X2 handover preparation
from SeNB.
InterX2OutSucc Success count for X2 handover execution
from SeNB.
InterX2OutPrepFail_CP_CC_FAIL Preparation fails due to reset notification
(eNB failure or block restart) from ECMB or
by ECCB block during the inter X2
handover preparation.
InterX2OutPrepFail_S1AP_LINK_FAIL Preparation fails due to S1 SCTP link
failure during the inter X2 handover
preparation.
InterX2OutPrepFail_S1AP_SIG_FAIL Preparation fails due to receiving S1AP
signaling during the inter X2 handover
preparation.
InterX2OutPrepFail_X2AP_CU_FAIL Preparation fails due to X2AP specification
cause during the inter X2 handover
preparation.
InterX2OutPrepFail_X2AP_LINK_FAIL Preparation fails due to X2 SCTP link
preparation.
InterX2OutPrepFail_X2AP_RP_TO Preparation fails due to X2AP relocprep

Name
timeout (not received) during the inter X2
InterX2OutPrepFail_X2AP_SIG_FAIL Preparation fails due to receiving X2AP
preparation.
InterX2OutFail_CP_CC_TO A call is released due to call control timeout
in the protocol blocks (MAC, RLC, PDCP,
and GTP) during the inter X2 handover
execution.
InterX2OutFail_CP_CC_FAIL A call is released due to reset notification
by the ECCB block during the inter X2
handover execution.
InterX2OutFail_UP_GTP_FAIL A call is released due to the failure in the
GTP block during the inter X2 handover
execution.
InterX2OutFail_UP_MAC_FAIL A call is released due to the internal failure
in the MAC block during the inter X2
handover execution.
InterX2OutFail_UP_PDCP_FAIL A call is released due to the internal failure
in the PDCP block during the inter X2
handover execution.
InterX2OutFail_UP_RLC_FAIL A call is released due to the internal failure
in the RLC block during the inter X2
handover execution.
InterX2OutFail_RRC_SIG_FAIL A call is released due to receiving RRC
execution.
InterX2OutFail_S1AP_CU_FAIL A call is released due to the S1AP
specification cause during the inter X2
handover execution.
InterX2OutFail_S1AP_LINK_FAIL A call is released due to the S1 SCTP link
execution.
InterX2OutFail_S1AP_SIG_FAIL A call is released due to receiving S1AP
execution.
InterX2OutFail_X2AP_CU_FAIL A call is released due to the X2AP
handover execution.
InterX2OutFail_X2AP_LINK_FAIL A call is released due to the X2 SCTP link
execution.
InterX2OutFail_X2AP_RO_TO A call is released due to X2AP RelocOverall
handover execution.
InterX2OutFail_X2AP_SIG_FAIL A call is released due to receiving the X2AP
execution.
InterX2OutCnt X2 Handover Out collection count
InterX2OutCid tcID of which collection is requested

Name
X2 Handover In InterX2InAtt The number of attempts for X2 handover in
TeNB
InterX2InPrepSucc The number of successes for X2 handover
preparation in TeNB
InterX2InSucc The number of successes for X2 handover
execution in TeNB
InterX2InPrepFail_CP_CC_TO Preparation fails due to call control timeout
GTP) during the inter X2 handover
preparation.
InterX2InPrepFail_CP_CC_FAIL Preparation fails due to reset notification
by ECCB block during the inter X2
InterX2InPrepFail_UP_GTP_FAIL Preparation fails due to internal failure in
the GTP block during the inter X2 handover
preparation.
InterX2InPrepFail_UP_MAC_FAIL Preparation fails due to internal failure in
the MAC block during the inter X2 handover
preparation.
InterX2InPrepFail_UP_PDCP_FAIL Preparation fails due to internal failure in
the PDCP block during the inter X2
InterX2InPrepFail_UP_RLC_FAIL Preparation fails due to internal failure in
the RLC block during the inter X2 handover
preparation.
InterX2InPrepFail_CP_BH_CAC_FAIL Preparation fails due to insufficient
backhaul-based eNB resources during the
inter X2 handover preparation.
InterX2InPrepFail_CP_CAPA_CAC_FAIL Preparation fails due to insufficient
capacity-based eNB resources during the
inter X2 handover preparation.
InterX2InPrepFail_CP_QOS_CAC_FAIL Preparation fails due to insufficient QoS-
based eNB resources during the inter X2
InterX2InPrepFail_S1AP_LINK_FAIL Preparation fails due to S1 SCTP link
preparation.
InterX2InPrepFail_S1AP_SIG_FAIL Preparation fails due to receiving S1AP
preparation.
InterX2InPrepFail_X2AP_CU_FAIL Preparation fails due to X2AP specification
cause during the inter X2 handover
preparation.
InterX2InPrepFail_X2AP_LINK_FAIL Preparation fails due to X2 SCTP link
preparation.
InterX2InPrepFail_X2AP_SIG_FAIL Preparation fails due to receiving X2AP
preparation.
InterX2InFail_CP_CC_TO A call is released due to call control timeout

Name
GTP) during the inter X2 handover
execution.
InterX2InFail_CP_CC_FAIL A call is released due to reset notification
by the ECCB block during the inter X2
handover execution.
InterX2InFail_UP_GTP_FAIL A call is released due to the failure in the
GTP block during the inter X2 handover
execution.
InterX2InFail_UP_MAC_FAIL A call is released due to the internal failure
in the MAC block during the inter X2
handover execution.
InterX2InFail_UP_PDCP_FAIL A call is released due to the internal failure
in the PDCP block during the inter X2
handover execution.
InterX2InFail_UP_RLC_FAIL A call is released due to the internal failure
in the RLC block during the inter X2
handover execution.
InterX2InFail_RRC_HC_TO A call is released due to HO command
handover execution.
InterX2InFail_RRC_SIG_FAIL A call is released due to receiving RRC
execution.
InterX2InFail_S1AP_CU_FAIL A call is released due to the S1AP
handover execution.
InterX2InFail_S1AP_LINK_FAIL A call is released due to the S1 SCTP link
execution.
InterX2InFail_S1AP_PATH_TO A call is released due to S1AP path switch
handover execution.
InterX2InFail_S1AP_SIG_FAIL A call is released due to receiving S1AP
execution.
InterX2InFail_X2AP_CU_FAIL A call is released due to the X2AP
handover execution.
InterX2InFail_X2AP_LINK_FAIL A call is released due to the X2 SCTP link
execution.
InterX2InFail_X2AP_SIG_FAIL A call is released due to receiving the X2AP
execution.
InterX2InFail_X2AP_SIG_TO A call is released due to X2AP signaling
handover execution.
MOBILITY (KPI) EutranMobilityHOX2Out HOX2Out success rate of E-UTRAN
mobility

Name
sumHOX2Out_Att Total X2 handover attempt count in SeNB
sumHOX2Out_Succ Total X2 handover execution success count
in SeNB
sumHOX2Out_PrepSucc Total X2 handover preparation success
count in SeNB
EutranMobilityHOX2In HOX2In success rate of E-UTRAN mobility
sumHOX2In_Att Total X2 handover attempt count in TeNB
sumHOX2In_Succ Total X2 handover execution success count
in TeNB
sumHOX2In_PrepSucc Total X2 handover preparation success
count in TeNB
REFERENCE
LTE-SW1202, PS Handover between LTE and

UTRAN
INTRODUCTION
PS Handover between LTE and UTRAN provides the seamless data service over
LTE and UTRAN coverage. In case of supporting outgoing inter-RAT handover to
UTRAN, the serving eNB configures LTE and UTRAN measurements to UEs and
determines PS handover to UTRAN based on the measurement report from UE.
Two procedures, that is, PS handover from LTE to UTRAN and PS handover from
UTRAN to LTE, are supported.
BENEFIT
The operator can provide connected mobility to its subscribers over LTE and
UTRAN coverage.
Users in connected state can move across E-UTRAN and UTRAN coverage,
remaining in the connected state.

Dependency
UTRAN Device, EPC, and UTRAN shall support PS handover between E-
UTRAN and UTRAN
FEATURE DESCRIPTION
When a user under LTE data services area and moves to UTRAN, eNB needs to
transit the service to UTRAN using the PS handover procedure to provide
seamless data services. To support seamless data service when UE moves from E-
UTRAN to UTRAN coverage, Samsung eNB supports PS handover to UTRAN
under the following conditions:
Target UTRAN shall support PS handover
UE shall support measurement reporting for UTRAN frequencies in E-UTRA
connected mode
UE shall support handover to UTRAN
UTRAN frequency shall be configured for PS handover purpose (Each UTRAN
frequency group can be configured to support CS service, PS service or both).
The eNB determines PS handover to UTRAN based on UTRAN measurement

report in UE. When eNB receives the relevant UE measurement results and PS
handover towards UTRAN is possible, the source eNB initiates the inter-RAT PS
handover procedures by sending a handover request to serving MME. According
to the handover request from eNB, MME performs inter-RAT packet handover
preparation procedures with UTRAN. In case the handover succeeded, the
handover command provided by UTRAN will be sent to UE by source eNB.
After this message is received by UE, UE moves on the UTRAN target cell.
The following figure shows the overview of PS handover to UTRAN procedures:
In case of data user in connected mode, Samsung LTE system provides two types
of methods for inter-RAT mobility to UTRAN, that is, PS redirection and PS
handover. The operator can choose which method is preferred for the inter-RAT
mobility based on their requirements. If forced redirection mode is chosen, inter-
RAT PS redirection is always used for inter-RAT connected mode mobility to 3G
(forced redirection option). On the other hand, if forced redirection mode is not
chosen, inter-RAT PS handover is preferred to PS redirection. Though PS
handover is preferred in the system setting, the serving eNB may perform PS
redirection because some reasons, for example, UE not support UTRAN
measurement/handover or no neighbor UTRAN cell is defined.
If the inter-RAT PS handover is used, serving eNB configures Event A2 (Serving
is worse than a threshold) measurement reporting to trigger UTRAN measurement.
On reception of measurement report triggered by Event A2, Samsung eNB
configures UTRAN measurement based on Event B2 (Serving becomes worse
than threshold_1 and inter RAT neighbor becomes better than threshold_2) or
Event B1 (Inter RAT neighbour becomes better than threshold) for UE. PS
handover to UTRAN is triggered on reception of Event B2/B1 as coverage based
trigger. In case of coverage based handover, UTRAN measurement based method
is only used, that is, if there is no UE measurement for UTRAN target carrier/cell,
PS handover is not triggered. In case of UEs which do not support UTRAN
measurement or UTRAN handover, the serving eNB always performs PS
redirection to move UE to UTRAN.
The following figure shows the call flow for PS handover from E-UTRAN to
UTRAN procedure:
Before performing handover procedures, uplink and downlink data traffic of an

LTE UE goes through eNB, S-GW, and P-GW.
1) The UE transmits a measurement report that includes UTRAN measurement.
(Event B2 is triggered)
2) The source eNB determines the PS handover to the UTRAN.
3) The source eNB requests PS handover to UTRAN by transmitting Handover

Required to the source MME.
4)~5) The source MME sends Forward Relocation Request to the new SGSN, and
SGSN sends Relocation Request to Target RNC. Then, radio access bearer is
established between RNC and SGSN.
6) The RNC responds to new SGSN with Relocation Request Acknowledge
containing target RAN TEID (DL) for RAB setup for DL traffic, and the target
RNC is ready to receive forwarded downlink PDUs.
7) Forward Relocation Response with SGSN TEID (UL) is sent from new SGSN
to old MME to receive the forwarded PDUs from source LTE network.
8) The MME sends Create Indirect Data Forwarding Tunnel Request to S-GW
with target SGSN TEID (UL), S-GW becomes capable of forwarding downlink
PDUs to target SGSN.
9) The S-GW sends the Create Indirect Data Forwarding Tunnel Response to
MME with serving S-GW TEID (UL).
10) The source MME sends Handover Command to source eNB with S-GW TEID
(UL). S1 bearer for uplink indirect forwarding between eNB and S-GW is
established.
11) From this phase, downlink indirect forwarding from source eNB to target RNC
is feasible. (Forwarding path: Source eNB Source S-GW Target SGSN
Target RNC)
12) After the indirect forwarding tunnels establishment, source eNB transmits the
Mobility from EUTRA command to UE including the message sent by target
UTRAN.
13)~14) The UE is switched to UTRAN target cell specified by eNB and transmits
HO to UTRAN Complete message to UTRAN. Then, Target RNC notifies
handover is completed by transmitting Relocation Complete to target SGSN.
15)~18) The Target SGSN processes the handover completion procedure with
source MME. Then, Update PDP Context Request/Response procedures are
performed, and Iu bearer tunnel is established.
19) The UE performs Routing Area Update procedure. Thereafter, UE continues
data service in UTRAN.
20)~22) Upon the expiration of resource release timers, retained resources in eNB,
MME, S-GW are released according the appropriate signaling procedures.
After PS handover to UTRAN is completed, uplink and downlink data traffic of
UE goes through RNC and P-GW.
In case PS handover from UTRAN, handover decision is made by the source
UTRAN. The target LTE eNB acquires the handover request in S1AP Handover
Request message sent from MME. When PS handover from UTRAN is requested,
target eNB performs admission control based on the received E-RAB QoS
information. In case the handover request is allowed, target eNB allocates the
required resources according to received E-RAB QoS information and reserves a
C-RNTI and optionally a RACH preamble.
The following figure shows PS handover procedure from UTRAN:
1) The source RNC determines the PS handover to E-UTRAN.

2) The source RNC requests the PS handover by transmitting Relocation Required
to source SGSN.
3)~9) The handover preparation procedure is processed between source UTRAN

and target E-UTRAN. Through this procedure, resources are allocated to support
UE maintain data service in target E-UTRAN after PS handover. If data
forwarding is possible, a tunnel for data forwarding is set up.
10) The source RNC receives Relocation Command from source SGSN.
11) The source RNC transmits the HO from UTRAN Command to UE as well as
the HO command received from target E-UTRAN.
12) The UE is switched to E-UTRAN target cell specified by source RNC and
transmits the RRC Connection Reconfiguration Complete to E-UTRAN.
13) The target eNB notifies that handover is completed by transmitting Handover
Notify to target MME.
14)~18) The target MME processes the handover completion procedure with
source SGSN.
19) The UE performs the Tracking Area Update procedure. Thereafter, UE
continues data service in E-UTRAN.
20)~23) The source SGSN releases the resources used in UTRAN after completing
PS handover with the E-UTRAN. If a tunnel for data forwarding was set up,
source SGSN and target MME release the data forwarding tunnel.
SYSTEM OPERATION
How to Activate
To enable this feature, operator should configure the UTRAN Frequency
Information by executing the CHG-UTRA-FA command and A2 report
configuration for ci_A2PurposeIRatHo and B2 report configuration for the each
UTRAN carrier.
The handover target UTRAN cell need to be registered in the serving cell
neighboring cell list.
Key Parameters
CHG-UTRA-FA/RTRV-UTRA-FA
STATUS This parameter indicates whether to use UTRAN carrier information.
N_EQUIP: Does not use UTRAN carrier information.
EQUIP: Uses UTRAN carrier information.
DUPLEX_TYPE This parameter is the duplex mode information of UTRAN carrier.
FDD: Frequency Division Duplex.
TDD: Time Division Duplex.
UARFCN_UL This parameter sets the Uplink Absolute Radio Frequency Channel Number
(ARFCN) value for the UTRA Frequency.
It executes Data Rule Check (DRC) to ensure that the same Uplink ARFCN
value based on the EQUIP state is not entered.
UARFCN_DL This parameter sets the Downlink Absolute Radio Frequency Channel Number
(ARFCN) value for the UTRA Frequency. It executes Data Rule Check (DRC)
to ensure that the same Downlink ARFCN value based on the EQUIP state is
not entered.
PURPOSE This parameter is the purpose of using the Event A2 per cell. It is used to
activate the measurement gap as default.
LteHo: Used for Gap Activate.
LteBlind: Used for Blind HO.
IRatHo: Used for IRAT HO.
IRatBlind: Used for IRAT Blind HO.
Ca: Used for Carrer Aggregation.
CaPeriodicMr: Used for Add Smart Carrier Aggregation Periodic Measure
Config.
Srvcc: Used for Single Radio Voice Call Continuity.
Mdt: Used for Minimization of Drive Tests.
CaInterFreq: Used for Inter Frequency Carrier Aggregation.
InterFreqAnrTrigger: Used for Inter Frequency Anr.
InterRatAnrTrigger: Used for Inter Rat Anr.
ACTIVE_STATE This parameter indicates whether event A2 is enabled/disabled per target
frequency. This change will be applied to UE from next RRC signaling
procedure (for example, Attach or Idle to Active). To avoid overload, a new
setting will not be updated to the current active UEs.
Active: Event A2 is used. If HO of the target frequency is not needed in the
site, this is inactive.
CHG-UTRA-B2CNF/RTRV-UTRA-B2CNF
PURPOSE This parameter is the purpose to retrieve the B2 report configuration
information used for interoperating with UTRAN.
InterRatHandover: Used for handover to UTRAN.
Srvcc: Used for SRVCC.
InterRatSPID: inter-RAT handover is executed for specific SPID with
handover mobility option.
OnDemandHandover: Enable the forced handover triggering by operator
Spare_1: Reserved field.
Spare_2: Reserved field.
ACTIVE_STATE This parameter indicates whether UTRA Event B2, which is triggered when
Inter RAT neighbor becomes better than threshold, is enabled/disabled.
This change will be applied to UE from next RRC signaling procedure (for
example, Attach or Idle to Active). To avoid overload, a new setting will not be
updated to the current active UEs.
Inactive: UTRA Event B2 is not used.
Active: UTRA Event B2 is used.
CHG-NBR-UTRAN/RTRV-NBR-UTRAN/CRTE-NBR-UTRAN/DLT-NBR-
UTRAN
STATUS This parameter indicates the validity of the Neighbor UTRAN.
This parameter must be set accurately since it determines the RIM operation
and Handover execution.
N_EQUIP: The information is determined as invalid.
EQUIP: The information is determined as valid.
RNC_ID This parameter is RNC ID of UTRAN neighbor cell located near eNB.
C_ID This parameter indicates the cell ID value of UTRAN neighboring cell. This
data must be accurately entered to execute RIM process. The SI of UTRAN
neighboring cell, obtained through the RIM process, is used during CSFB with
3G SIB operation.
LAC This parameter indicates the Location Area Code (LAC) of UTRAN neighboring
Cell. This information is used during RIM operation and Handover. Make sure
that set the parameter accurately to ensure successful RIM operation and
Handover.
RAC This parameter indicates the routing area code of the neighboring UTRAN cell.
This information is used during RIM procedures and Handover. The parameter
must be set accurately because the information is used during RIM procedures
and Handover.
MCC0 ~ MCC5[4] This parameter is the PLMN list information (MCC) of a UTRAN neighbor cell
located around the eNB, Enter 3-digit number whose each digit ranges from 0
to 9. This information is used during RIM operation and Handover. Make sure
that set accurately to ensure successful RIM operation and Handover.
MNC0 ~ MNC5[4] This parameter is the PLMN list information (MNC) of a UTRAN neighbor cell
located around the eNB, Enter 3-digit or 2-digit number whose each digit
ranges from 0 to 9. This information is used during RIM operation and
Handover. Make sure that set accurately to ensure successful RIM operation
and Handover.
DUPLEX_TYPE This parameter is the duplex type information of a UTRAN neighbor cell
located near eNB. The duplex Type of UTRAN Neighboring Cell must be
entered accurately.
P_SCM_CODE This parameter indicates the scramble code information of the neighboring
UTRAN FDD cell. It is used during handover with the UTRAN. The parameter
must be set accurately since it is used during the handover.
ARFCN_UL This parameter indicates the Absolute Radio Frequency Channel Number
(ARFCN) UL value of UTRAN neighboring cell. Values from 0 to 16,383 can be
entered. This should be matched with exact value used by the actual UTRAN
network.
ARFCN_DL This parameter indicates the Absolute Radio Frequency Channel Number
(ARFCN) DL value of UTRAN neighboring cell. Values from 0 to 16,383 can be
entered. This should be matched with exact value used by the actual UTRAN
network.
Make sure that use the unique value compared to previously used value. If the
physCellID and ARFCN DL are same, the system determines the entry is
identical.
Counters and KPIs


HO_INTER_RAT_UTRAN_O RatUtranOutAtt LTE to inter-RAT UTRAN handover attempt
UT count.
RatUtranOutPrepSucc LTE to inter-RAT UTRAN handover
preparation success count
RatUtranOutSucc LTE to inter-RAT UTRAN handover
execution success count
RatUtranOutPrepFail_CpCcFail Preparation fails due to reset notification
by the ECCB block during the UTRAN
RatUtranOutPrepFail_S1apCuF Preparation fails due to S1AP specification
ail cause during UTRAN handover
preparation.
RatUtranOutPrepFail_S1apLink Preparation fails due to S1 SCTP link
Fail failure during the UTRAN handover
preparation.
RatUtranOutPrepFail_S1apRpT Preparation fails due to S1AP relocprep
o timeout (not received) during the UTRAN
RatUtranOutPrepFail_S1apSigF Preparation fails due to receiving S1AP
ail signaling during the UTRAN handover
preparation.
RatUtranOutFail_CpCcTo A call is released due to call control timeout
and GTP) during the UTRAN handover
execution.
RatUtranOutFail_CpCcFail A call is released due to reset notification
(eNB failure or block restart) from the
ECMB or by the ECCB block during the
UTRAN Handover execution.
RatUtranOutFail_UpGtpFail A call is released due to internal failure in
the GTP block during the UTRAN handover
execution.
RatUtranOutFail_UpMacFail A call is released due to internal failure in
the MAC block during the UTRAN
handover execution.
RatUtranOutFail_UpPdcpFail A call is released due to internal failure in
the PDCP block during the UTRAN
handover execution.
RatUtranOutFail_UpRlcFail A call is released due to internal failure in
the RLC block during the UTRAN handover
execution.
RatUtranOutFail_RrcSigFail A call is released due to receiving RRC
signaling during the UTRAN handover
execution.
RatUtranOutFail_S1apCuFail A call is released due to the S1AP
specification cause during the UTRAN
handover execution.
RatUtranOutFail_S1apLinkFail A call is released due to the S1 SCTP link
failure during the UTRAN handover
execution.
RatUtranOutFail_S1apRoTo A call is released due to an S1AP

relocoverall timeout (not received) during
the UTRAN Handover execution.
RatUtranOutFail_S1apSigFail A call is released due to receiving S1AP
execution.

HO_INTER_RAT_UTRAN_I RatUtranInAtt LTE to inter-RAT UTRAN handover attempt
N count
RatUtranInPrepSucc LTE to inter-RAT UTRAN handover
RatUtranInSucc LTE to inter-RAT UTRAN handover
RatUtranInPrepFail_CpCcTo Preparation fails due to call control timeout
and GTP) during the UTRAN handover
preparation.
RatUtranInPrepFail_CpCcFail Preparation fails due to reset notification
by ECCB block during UTRAN Handover
preparation.
RatUtranInPrepFail_UpGtpFail Preparation fails due to internal failure in
the GTP block during the UTRAN
Handover preparation.
RatUtranInPrepFail_UpMacFail Preparation fails due to internal failure in
RatUtranInPrepFail_UpPdcpFail Preparation fails due to internal failure in
RatUtranInPrepFail_UpRlcFail Preparation fails due to internal failure in
preparation.
RatUtranInPrepFail_CpBhCacF Preparation fails due to insufficient
ail backhaul-based eNB resources during the
UTRAN handover preparation.
RatUtranInPrepFail_CpCapaCa Preparation fails due to insufficient
cFail capacity-based eNB resources during the
UTRAN handover preparation.
RatUtranInPrepFail_CpQosCac Preparation fails due to insufficient QoS-
Fail based eNB resources during the UTRAN
RatUtranInPrepFail_S1apCuFail Preparation fails due to S1AP specification
cause during the UTRAN handover
preparation.
RatUtranInPrepFail_S1apLinkFa Preparation fails due to S1 SCTP link
il failure during the UTRAN handover
preparation.
RatUtranInPrepFail_S1apSigFail Preparation fails due to receiving S1AP
signaling during UTRAN Handover
preparation.

RatUtranInFail_CpCcTo A call is released due to call control timeout
and GTP) during the UTRAN Handover
execution.
RatUtranInFail_CpCcFail A call is released due to reset notification
(eNB failure or block restart) from the
ECMB or by the ECCB block during
UTRAN Handover execution.
RatUtranInFail_UpGtpFail A call is released due to internal failure in
the GTP block during the UTRAN handover
execution.
RatUtranInFail_UpMacFail A call is released due to internal failure in
handover execution.
RatUtranInFail_UpPdcpFail A call is released due to internal failure in
handover execution.
RatUtranInFail_UpRlcFail A call is released due to internal failure in
execution.
RatUtranInFail_RrcHcTo A call is released due to HO command
timeout (not received) during the UTRAN
Handover execution.
RatUtranInFail_RrcSigFail A call is released due to receiving RRC
execution.
RatUtranInFail_S1apCuFail A call is released due to the S1AP
specification cause during the UTRAN
handover execution.
RatUtranInFail_S1apLinkFail A call is released due to the S1 SCTP link
failure during the UTRAN handover
execution.
RatUtranInFail_S1apSigFail A call is released due to receiving S1AP
execution.
RatUtranInFail_S1apSigTo A call is released due to S1AP signaling
timeout (not received) during the UTRAN
handover execution.
REFERENCE
[4] 3GPP TS23.401 Technical Specification Group Services and System Aspects;
GPRS enhancements for E-UTRAN access
LTE-SW1204, Redirection to UTRAN without SI

INTRODUCTION
This is outbound mobility control functionality to UTRAN. When mobility event
to UTRAN is occurred, eNB redirects UE towards UTRAN.
BENEFIT
The operator can provide connected mobility to its subscribers from E-UTRAN
to UTRAN.
Users in connected state can move from E-UTRAN to UTRAN.

Dependency
UTRAN Device, EPC, and UTRAN should support this feature.
FEATURE DESCRIPTION
The operator needs to provide PS data service continuously even when LTE/3G
dual mode UE enters 3G-only coverage area. As one of the methods to send the
data UE to UTRAN, eNB initiates the redirection (release with redirect)
procedures. This is indicated by the redirect carrier information in the RRC
CONNECTION RELEASE message. In case of redirection, triggering due to UEs
mobility is supported even if no prior UE measurements have been performed on
the target UTRAN cell and/or frequency.
The following figure shows the Redirection to UTRAN without SI procedure:
In case of UE which is candidate of PS redirection, the serving eNB configures
Event A2 (Serving is worse than a threshold_0) measurement to trigger PS
redirection. When the Event A2 measurement report from UE is received, PS
redirection to a target UTRA carrier is performed. On triggering of PS redirection,
the serving eNB redirects UE to the selected carrier by sending
RRCConnectionRelease message, which includes redirectedCarrierInfoIE.
The following figure shows the call flow for Redirection to UTRAN without SI
procedure:
Before redirection, uplink and downlink data traffic of LTE UE goes through eNB,
S-GW, and P-GW.
1 As UE moves away from source eNB, then eNB determines the redirection to
UTRAN (Event A2 is triggered).
2 The eNB transmits RRCConnectionRelease to UE. The message includes the
target UTRA carrier frequency to which UE will be redirected. At this step,
eNB releases both SRB and DRB.
3 The eNB transmits UE Context Release Request to MME to release UE specific
S1 connection between eNB and S-GW.
4 The MME sends the Release Access Bearer Request to S-GW to release the S1-
U bearer.
5 The S-GW responses by sending the Release Access Bearer Response to MME
after releasing eNB related information. Other elements of UEs S-GW
contexts are not affected in S-GW, and S-GW starts buffering the downlink
packets received for UE.
6 The MME sends UE Context Release Command to eNB to release the S1
signaling connection.
7 The eNB confirms the S1 Release by returning S1 UE Context Release
Complete message to MME. With this, the signalling connection between
MME and eNB for that UE is released.
8 The UE is switched to UTRA carrier that is specified by eNB in the RRC

Connection Release, and connects to UTRAN. The UE performs the Routing
Area Update procedure. In this procedure, SGSN makes a bearer connection to
the old P-GW (GGSN) for seamless IP mobility, and PS session can be
continuously served in UTRAN with the same IP address of LTE. In case of
detailed procedures for Routing Area Update, refer to the design document of
Core Network. The source MME releases any retained RAN and S-GW
resources when a certain timer expires.
After the redirection is completed, data traffic of UE goes through RNC and P-GW
if the direct tunnel is available.
According to the characteristics of deployed site, the number of UTRA frequencies
is configurable. Up to 6 different UTRA frequencies can be assigned per cell. Also,
the purpose of each UTRA frequency can be configurable based on supported
service as follows:
CS_ONLY(1): for CSFB (Redirection w/o SI, Redirection w/ SI, HO), SRVCC
PS_ONLY(2): for PS mobility (Redirection w/o SI, Redirection w/ SI, HO)
BOTH(0): for all cases
If UE has been instructed to complete Redirection process with a target UARFCN
and cannot find the target UARFCN, UE shall try to camp on any suitable cell
based on Stored Information. If UE fails to camp on any suitable cell based on the
Stored Information or UE has no Stored Information or it , then UE should execute
a complete 3G band search before trying again to complete other RAT/band
searches (that is, back to 4G). In more detail, if UE has not been able to find the
target UARFCN and has to start the complete 3G band search then, during that 3G
search, UE should execute a cell selection process & not a cell re-selection process.
If cell selection is not achieved on 3G layer, UE could move from 3G to LTE
during the subsequent cell selection phase on the basis of inter-RAT weighting
(the preference for LTE UEs move to LTE layer).
SYSTEM OPERATION
How to Activate
Information by executing the CHG-UTRA-FA command and configure A2 report
configuration for ci_A2PurposeIRatHo and/or ci_A2PurposeIRatBlind.
If interRatDataOption in CHG-INTWO-OPT is set to 'Data_BlindOnly', Blind
Redirection is executed regardless UEs capabilities on Measurement for UTRAN
and PS handover to UTRAN.
Key Parameters
not entered.
Config.
CHG-INTWO-OPT/RTRV-INTWO-OPT
INTER_RAT_DATA_OPTION This parameter indicates whether to force redirection during the inter RAT PS
handover for Data Call.
Data_UeCapability: Redirection or handover according to UE Capability.
Data_BlindOnly: Redirection is executed regardless of condition.
Counters and KPIs

PS_REDIR_UTRAN_OUT PsRedirAttUtran PS Redirection to Inter RAT UTRAN attempt count
PsRedirPrepSuccUtran PS Redirection to Inter RAT UTRAN preparation
success count
PsRedirSuccUtran PS Redirection to Inter RAT UTRAN execution success
count
REFERENCE
LTE-SW1205, Redirection to UTRAN with SI

INTRODUCTION
This is outbound mobility control functionality to UTRAN. When mobility event
to UTRAN is occurred, eNB redirects UE towards UTRAN. If System Information
(SI) of the neighboring cells in the selected carrier is available, SI of neighboring
UTRAN cells is included in the message as well as the redirected UTRA carrier
information.
BENEFIT
to UTRAN.
Users in connected state can move from E-UTRAN to UTRAN.

Dependency
FEATURE DESCRIPTION
By using this feature, serving eNB can include system information of the target
cell in the redirection message. So, the call setup delay in UTRAN can be reduced.
The operator needs to provide PS data service continuously even when LTE/3G
dual mode UE enters the 3G-only coverage area. As one of the methods to send
the data UE to UTRAN, eNB initiates the redirection (release with redirect)
procedures.
This is indicated by the redirect carrier information in the RRC CONNECTION
RELEASE message. If UE supports the enhanced redirection to UTRAN and
System Information (SI) of neighboring UTRAN cell is available, carry out
Redirection with SI to reduce the call setup time is UTRAN.
The following figure shows the PS redirection to UTRAN with SI procedures:
In case of UE which is candidate of PS redirection, the serving eNB configures
Event A2 (Serving is worse than a threshold_0) measurement to trigger PS
redirection. When the Event A2 measurement report from UE is received, PS
redirection to a target UTRA carrier is performed. On triggering of PS redirection,
the serving eNB redirects UE to the selected carrier by sending
RRCConnectionRelease message, which includes redirectedCarrierInfoIE. It
system information of the neighboring cells in the selected carrier is available, the
system information is included in RRCConnectionRelease message. Otherwise,
redirected UTRA carrier information is only included in the message (Redirection
to UTRAN without SI feature). To acquire system information from neighboring
UTRAN cells, the serving eNB and neighboring UTRAN cells should support
RIM procedures.
The following figure shows the call flow for redirection to UTRAN procedure:
Before redirection, uplink and downlink data traffic of LTE UE goes through eNB,
S-GW, and P-GW.
1 As UE moves away from the source eNB, then eNB determines the redirection
to UTRAN (Event A2 is triggered).
2 The eNB transmits RRCConnectionRelease to UE. The message includes the

target UTRA carrier frequency which UE will be redirected. If SI (System
Information) of the neighboring cells in the selected carrier is available, SI of
neighboring UTRAN cells are included. At this step, eNB releases both SRB
and DRB.
3 The eNB transmits UE Context Release Request to MME to release UE specific
S1 connection between eNB and S-GW.
4 The MME sends the Release Access Bearer Request to S-GW to release the S1-
U bearer.
5 The S-GW responses by sending the Release Access Bearer Response to MME
after releasing eNB related information. Other elements of UEs S-GW
contexts are not affected in S-GW, and S-GW starts buffering the downlink
packets received for UE.
6 The MME sends UE Context Release Command to eNB to release the S1
signaling connection.
7 The eNB confirms the S1 Release by returning S1 UE Context Release
Complete message to MME. With this, the signalling connection between
MME and eNB for that UE is released.
8 The UE is switched to UTRA carrier that is specified by eNB in the RRC
Connection Release, and connects to UTRAN. The UE performs the Routing
Area Update procedure. In this procedure, SGSN generally makes a bearer
connection to the old P-GW (GGSN) for seamless IP mobility, and PS session
can be continuously served in UTRAN with the same IP address of LTE. In
case of detailed procedures for Routing Area Update, refer to the design
document of Core Network. The source MME releases any retained RAN and
S-GW resources when a certain timer expires.
After the redirection is completed, data traffic of UE goes through RNC and P-GW
if the direct tunnel is available.
According to the characteristics of deployed site, the number of UTRA frequencies
is configurable. Up to 6 different UTRA frequencies can be assigned per cell. Also,
the purpose of each UTRA frequency can be configurable based on supported
service as follows:
CS_ONLY(1): for CSFB (Redirection without SI, Redirection with SI, HO),
SRVCC
PS_ONLY(2): for PS mobility (Redirection without SI, Redirection with SI, HO)
When reviewing UE behavior under a failure to reach the target RAT/frequency,
the version of the document Samsung refers to the 3GPP specification 3GPP TS
36.304 is Rel-9 (9.11.0).

searches (that is, back to 4G).In more detail, if UE has not been able to find the
SYSTEM OPERATION
How to Activate
To enable this feature, operator should configure the GERAN Frequency
Information by executing the CHG-UTRA-FA command and configure A2
report configuration for ci_A2PurposeIRatHo and/or ci_A2PurposeIRatBlind.
If interRatDataOption in CHG-INTWO-OPT is set to Data_BlindOnly, Blind
Redirection is executed regardless UEs capabilities on Measurement for
UTRAN and PS handover to UTRAN.
isAllowedRim parameter should be set as True by executing the CHG-HO-
OPT. This parameter configures the RIM procedure and rimSupport
parameter should be set as True by executing the CHG-NBR-UTRAN
command.
Key Parameters
(ARFCN) value for UTRA Frequency.
not entered.
Config.
CHG-HO-OPT/RTRV-HO-OPT
RIM_ENABLE This parameter indicates whether to support the RAN Information Management
(RIM) function for Inter RAT (WCDMA, GEARN).
False: Does not perform the RIM function.
True: Performs the RIM function.
UTRAN
RIM_SUPPORT This parameter is whether the UTRAN neighbor cell supports the RIM. This
parameter indicates whether or not the RIM procedure of a neighbor UTRAN
cell is supported. If it is set to False, then the RIM procedure is not executed. If
it is set to True, then the RIM procedure is executed. It must be set accurately
since the RIM procedure execution is determined by the setting.
False: RIM is not supported.
True: RIM is supported.
Counters and KPIs

PS_REDIR_UTRAN_O PsRedirAttUtran PS Redirection to Inter RAT UTRAN attempt count
UT
PsRedirPrepSuccUtr PS Redirection to Inter RAT UTRAN preparation success
an count
PsRedirSuccUtran PS Redirection to Inter RAT UTRAN execution success
count
REFERENCE
LTE-SW1208, CSFB to UTRAN with Redirection

with SI
INTRODUCTION
CS fallback, a function to provide voice services to LTE users before Voice over
LTE (VoLTE) is introduced, makes transition to CS domain upon LTE users
outgoing/incoming call so that the user can get voice services.
The function of CSFB to UTRAN is the transition of UE to UTRAN according to
the CSFB procedure, in the event of CSFB outgoing/incoming.
When eNB receives a S1 message where CSFB indicator is included from MME,
it selects a target frequency and performs a procedure of redirection with system
information.
Then, UE starts voice call outgoing/incoming procedure in UTRAN.
BENEFIT
The operator can provide CS service to its subscribers by using legacy CS
network (UTRAN).
Users can make a CS call while staying in E-UTRAN, by transition to legacy CS
network (UTRAN).

Dependency
UTRAN Device, EPC and UTRAN should support this feature.
RIM for SI tunneling shall be support by EPC and UTRAN.
FEATURE DESCRIPTION
With the default LTE data network connection in operation, a mobile terminating
(incoming) CS voice call triggers paging via LTE network to UE. This paging
message initiates CSFB, as the device sends a NAS EXTENDED SERVICE
REQUEST to the network to transition to 3G network. Once transitioned, the
legacy call setup procedures are followed to setup the CS call.
Mobile originating (outgoing) calls follow the same transition from LTE (PS) to
3G (CS), except for the paging step. In 3G networks, PS data sessions can also be
established simultaneously for data services. After the voice call ends and UE
returns to idle state or Cell_PCH state, the device should perform cell reselection
procedures to reselect LTE cell. If UE has still PS session after the voice call ends,
then UE remains in 3G cell.
3G network coexists with LTE network residing between UE and core network.
The MME serves users while in LTE access network, while for 3G SGSN serves
users when utilizing data services and MSC (Mobile Switching Center) when
utilizing voice services. To support CS Fallback signaling, MME connects to MSC
with SGs interface. The SGs interface is used for the mobility management and
paging procedures between EPS and CS domain. Also, it is used for the delivery of
both mobile originating and mobile terminating SMS.
The following figure shows the architecture and interfaces for CSFB:
In general, UE notifies to MME about the type of attach required during the attach
procedure. In case Attach Type in the Attach request message is Combined
EPS/IMSI Attach, combined CS and PS updates are executed. In case of
Combined EPS/IMSI Attach there is a requirement to use SGs interface, between
MME and MSC.
To enable CSFB to UTRAN based on Redirection with SI feature, the parameter
INTER_RAT_CS_REDIRECTION should be set as True by executing CHG-
INTWO-OPT command. This parameter is used for the selection of the
interworking option per cell.
Also, RIM_ENABLE parameter should be set as TRUE by executing the
CHG-HO-OPT. This parameter performs to enable the RIM procedure per eNB.
The following figure shows redirection based CSFB to UTRAN procedures when
UE is in idle mode:
1) The UE, in idle state, originates a voice call or receives a mobile terminated
voice call.
2~5) Since UE is in idle state, it starts RRC connection establishment procedures
with eNB to make a SRB connection. The UE sends NAS Extended Service
Request message to MME, which is included in RRC Connection Setup Complete
message.
6) The MME sends eNB S1-AP Initial Context Setup Request message that
includes CSFB indicator.
7) The eNB processes the AS security activation.
8) The eNB transmits S1-AP Initial Context Setup Response message to MME. At
this step, eNB does not setup a DRB connection because UE is going to redirect to
UTRAN.
9) The eNB sends RRC Connection Release message to UE. The message includes
UTRA carrier frequency to which UE will be redirected, the cell reselection
priority of the UTRA frequency, and system information of one or more cells on
the redirected UTRA frequency.
10~14) The eNB transmits UE Context Release Request message to MME to
release S1 bearer connection between eNB and S-GW. S5 bearer between S-GW
and P-GW is retained. If UE sends Routing Area Update message to SGSN, then
SGSN will trigger RAU procedure with old MME. In this case, SGSN will make a
bearer connection between itself and PGW and MME will remove the S5 bearer
connection. Usually, CSFB UE sends Routing Area Update message because it
changes the Routing Area, but, depending on UE implementation it may not
trigger RAU procedure because it will go back to LTE network as soon as it ends
the CSFB call.
15~17) The UE connects to UTRAN and sets up a CS session. Also, it performs
UTRAN location update procedures. At this step, UE is not expected to set up a PS
session because UE is in idle state.
The following figure shows redirection based CSFB to UTRAN procedures when
UE is in connected mode:
1) The UE, in connected state, originates a voice call or receives a mobile

terminated voice call.
2~3) The UE sends NAS Extended Service Request message to MME. The eNB
and UE already have both SRB and DRB because UE is in connected mode.
4) The MME sends eNB S1-AP UE Context Modification Request message that
5) The eNB transmits S1-AP UE Context Modification Response message to
MME.
6) The eNB sends RRC Connection Release message to UE. The message includes
UTRA carrier frequency to which UE will be redirected, the cell reselection
priority of UTRA frequency, and system information of one or more cells on the
redirected UTRA frequency. At this step, eNB releases both SRB and DRB.
7~11) The eNB transmits UE Context Release Request message to MME to
release S1 bearer connection between eNB and S-GW. S5 bearer between S-GW
and P-GW is retained but the state is changed to idle mode. If UE sets up a PS
bearer in UTRAN, SGSN will make a bearer connection between SGSN and P-
GW (GGSN) for seamless IP mobility and MME will remove the S5 bearer
connection.
12~14) The UE connects to UTRAN and sets up a CS session. Also, it performs
UTRAN location update procedures. At this step, UE is expected to set up a PS
session as well because there is an ongoing active bearer. The PS session can be
continued in UTRAN with the same IP address.
According to the characteristics of the deployed site, the number of UTRA
frequencies is configurable. Up to 6 different UTRA frequencies can be assigned
per cell. Also, the purpose of each UTRA frequency can be configurable based on
supported service as follows:
CS_ONLY(1): for CSFB (Redirection w/o SI, Redirection w/ SI, HO), SRVCC
PS_ONLY(2): for PS mobility (Redirection w/o SI, Redirection w/ SI, HO)
When reviewing UE behavior under a failure to reach the target RAT/frequency,
the version of the document Samsung refers to the 3gpp specification 3GPP TS
36.304 is Rel-9 (9.11.0).
searches (that is, back to 4G). In more detail, if UE has not been able to find the
SYSTEM OPERATION
How to Activate
Information by executing the CHG-UTRA-FA command.

OPT command. This parameter configures the RIM procedure and
rimSupport parameter should be set as True by executing the CHG-NBR-
UTRAN command.
Key Parameters
not entered.
UTRAN
RIM_SUPPORT This parameter is whether the UTRAN neighbor cell supports the RIM. This
parameter indicates whether or not the RIM procedure of a neighbor UTRAN
cell is supported. If it is set to False, then the RIM procedure is not executed. If
it is set to True, then the RIM procedure is executed. It must be set accurately
since the RIM procedure execution is determined by the setting.
Counters and KPIs

CSFB_REDIR_UTRAN_OUT CSFBRedirUtranAtt CSFB with Redirection to inter-RAT UTRAN
attempt count

CSFBRedirUtranPrepSucc CSFB with Redirection to inter-RAT UTRAN
preparation success count.
CSFBRedirUtranSucc CSFB with Redirection to inter-RAT UTRAN
execution success count.
REFERENCE
description; Stage 2.
Resource Control (RRC); Protocol specification.
[3] 3GPP TS36.413 Evolved Universal Terrestrial Access Network (E-UTRAN);
S1 Application Protocol (S1AP).
[4] 3GPP TS23.272 Circuit Switched Fallback in Evolved Packet System; Stage 2.
LTE-SW1209, CSFB to UTRAN with PS Handover

INTRODUCTION
CS fallback, a function to provide voice services to LTE users before Voice over
LTE (VoLTE) is introduced, makes transition to CS domain upon LTE users
outgoing/incoming call so that the user can get voice services.
The function of CSFB to UTRAN is the transition of UE to UTRAN according to
the CSFB procedure, in the event of CSFB outgoing/incoming.
When eNB receives a S1 message where CSFB indicator is included from MME,
it selects a target frequency and performs a procedure of PS handover.
Then, UE starts voice call outgoing/incoming procedure in UTRAN.
BENEFIT
network (UTRAN).
network (UTRAN).

Dependency
FEATURE DESCRIPTION
With the default LTE data network connection in operation, a mobile terminating
(incoming) CS voice call triggers paging via LTE network to UE. This paging
message initiates CSFB, as the device sends a NAS EXTENDED SERVICE
REQUEST to the network to transition to 3G network. Once transitioned, the
legacy call setup procedures are followed to setup the CS call. If UE does not
support PS handover to UTRAN, CSFB to UTRAN with redirection procedure is
used.
Mobile originating (outgoing) calls follow the same transition from LTE (PS) to
3G (CS), except for the paging step. In 3G networks, PS data sessions can also be
established simultaneously for data services. After the voice call ends and UE
returns to idle state or Cell_PCH state, the device should perform cell reselection
procedures to reselect LTE cell. If UE has still PS session after the voice call ends,
then UE remains in 3G cell.
3G network coexists with LTE network residing between the UE and the core
network. The MME serves users while in LTE access network, while for 3G
SGSN serves users when utilizing data services and MSC (Mobile Switching
Center) when utilizing voice services. To support CS Fallback signaling, MME
connects to MSC with SGs interface. The SGs interface is used for the mobility
management and paging procedures between EPS and CS domain. Also, it is used
for the delivery of both mobile originating and mobile terminating SMS.
Combined EPS/IMSI Attach there is a requirement to use SGs interface, between
MME and MSC.
To enable CSFB to UTRAN with PS Handover feature, the parameter
INTER_RAT_CS_REDIRECTION should be set as True by executing the
CHG-INTWO-OPT command. This parameter is used for the selection of the
interworking option per cell.
And RIM_ENABLE parameter should be set as FALSE by executing the
CHG-HO-OPT command. This parameter performs to disable the RIM
procedure per eNB.
The following figure shows PS handover based CSFB to UTRAN procedures
when UE is in idle mode:
1) The UE, in idle state, originates a voice call or receives a mobile terminated
voice call.
2~5) Since UE is in idle state, it starts RRC connection establishment procedures
with eNB to make a SRB connection. The UE sends NAS Extended Service
Request message to MME, which is included in RRC Connection Setup Complete
message.
6) The MME sends eNB S1-AP Initial Context Setup Request message that
7) The eNB processes the AS security activation.
8) The eNB transmits S1-AP Initial Context Setup Response message to MME.
9) The eNB provides the UTRAN measurement order to UE. (if available)
10) The handover preparation procedure between Source E-UTRAN and target
UTRAN is processed.
11) The eNB, including the HO command received from CSFB indicator and
target UTRAN, transmits the Mobility from EUTRA Command to UE.
12) The UE switches over to UTRAN target cell designated by eNB and performs
the rest of handover procedure.
The following figure shows PS handover based CSFB to UTRAN procedures
when UE is in connected mode:
1) The UE, in connected state, originates a voice call or receives a mobile

terminated voice call.
2~3) The UE sends NAS Extended Service Request message to MME. The eNB
and UE already have both SRB and DRB because UE is in connected mode.
4) The MME sends eNB S1-AP UE Context Modification Request message that
5) The eNB transmits S1-AP UE Context Modification Response message to
MME.
6) The eNB provides the UTRAN measurement order to UE (if available).
UTRAN is processed.
8) The eNB, including the HO command received from CSFB indicator and target
UTRAN, transmits the Mobility from EUTRA Command to UE.
9) The UE switches over to UTRAN target cell designated by eNB and performs
the rest of handover procedure.
SYSTEM OPERATION
How to Activate
Information by executing the CHG-UTRA-FA command and the UTRAN Periodic
Measurement information for StrongestCell report purpose by executing the CHG-
UTRA-PRD command.
Key Parameters
not entered.
CHG-GERAN-PRD/RTRV-GERAN-PRD
PURPOSE This parameter represents the usage of the periodic report used for
interoperating with the UTRAN.
RatPeriodicalPurposeReportStrongestCells: CS Fallback (CSFB): Used for
the solicit measurement report while performing.
StrongestCellsForSON: Used for the operation of SON.
ReportCGI: Used for the acquisition of the CGI information.
Mlb: Used for measurement report of MLB.
ACTIVE_STATE This parameter indicates whether to use UTRA periodic report. This change
will be applied to UE from next RRC signaling procedure (for example, Attach
or Idle to Active). To avoid overload, a new setting will not be updated to the
current active UEs.
Inactive: UTRA periodic report is not used.
Active: UTRA periodic report is used.
MAX_REPORT_CELL This parameter is the maximum number of cells included in the measurement
report for UTRA periodic report. This information is the maximum number of
Cells that can be included in a single message (that is, Measurement Report)
when a device is reporting the measurement results. When applying the new
value to the active UEs during the parameter change, it may cause system
overload so the application of the changed parameter is done when a new
connection request (Attach or Idle to Active) is received from a device.
REPORT_INTERVAL This parameter is the interval of measurement reports for UTRA periodic
report. This information is for setting the Measurement Report transmission
interval when a device is reporting measurement results. This change will be
applied to UE from next RRC signaling procedure (for example, Attach or Idle
to Active). To avoide overload, a new setting will not be updated to the current
active UEs.
REPORT_AMOUNT This parameter is the periodic measurement report count when interoperating
with the UTRAN. The reports are transmitted as many times as the specified
count.
Counters and KPIs

CSFB_PSHO_UTRAN_OUT CSFBPsHoUtranAtt Attempt count for CSFB with inter-RAT
UTRAN PS handover
CSFBPsHoUtranPrepSucc Success count for CSFB with inter-RAT
UTRAN PS handover preparation.
CSFBPsHoUtranSucc Success count for CSFB with inter-RAT
UTRAN PS handover execution.
CSFBPsHoUtranPrepFail_Cp Preparation fails due to reset notification
CcFail (eNB failure or block restart) from ECMB or
by the ECCB block during the CSFB PS
CSFBPsHoUtranPrepFail_S1a Preparation fails due to S1AP specification
pCuFail cause during the CSFB PS handover
preparation.
CSFBPsHoUtranPrepFail_S1a Preparation fails due to S1 SCTP link failure
pLinkFail during the CSFB PS handover preparation.
CSFBPsHoUtranPrepFail_S1a Preparation fails due to S1AP relocprep
pRpTo timeout (not received) during the CSFB PS
CSFBPsHoUtranPrepFail_S1a Preparation fails due to receiving S1AP
pSigFail signaling during the CSFB PS handover
preparation.
CSFBPsHoUtranFail_CpCcTo A call is released due to call control timeout
and GTP) during the CSFB PS handover
execution.
CSFBPsHoUtranFail_CpCcFai A call is released due to reset notification
l (eNB failure or block restart) from the ECMB
or by the ECCB block during the CSFB PS
handover execution.
CSFBPsHoUtranFail_UpGtpF A call is released due to a failure in the GTP
ail block during the CSFB PS handover

execution.
CSFBPsHoUtranFail_UpMacF A call is released due to a failure in the MAC
ail block during the CSFB PS handover
execution.
CSFBPsHoUtranFail_UpPdcp A call is released due to a failure in the PDCP
Fail block during the CSFB PS handover
execution.
CSFBPsHoUtranFail_UpRlcFa A call is released due to a failure in the RLC
il block during the CSFB PS handover
execution.
CSFBPsHoUtranFail_RrcSigF A call is released due to receiving an RRC
ail signaling during the CSFB PS handover
execution.
CSFBPsHoUtranFail_S1apCu A call is released due to S1AP specification
Fail cause during the CSFB PS handover
execution.
CSFBPsHoUtranFail_S1apLin A call is released due to the S1 SCTP link
kFail failure during the CSFB PS handover
execution.
CSFBPsHoUtranFail_S1apRo A call is released due to an S1AP relocoverall
To timeout (not received) during the CSFB PS
handover execution.
CSFBPsHoUtranFail_S1apSig A call is released due to receiving S1AP
Fail signaling during the CSFB PS handover
execution.
REFERENCE
[4] 3GPP TS23.272 Circuit Switched Fallback in Evolved Packet System; Stage 2
LTE-SW1301, Idle Mobility to GERAN

INTRODUCTION
To support from E-UTRAN to GERAN cell reselection, eNB broadcasts the
System Information Block type 7 (SIB7).
The UE shall monitor E-UTRAN BCCH during idle mode to retrieve the SIB7 for
the preparation of cell reselection to GERAN. Then, UE makes measurements on
the neighboring GERAN cells based on the criteria and performs cell reselection to
GERAN when needed.
The parameters for cell reselection to GERAN broadcasted in SIB7 are as follows:
GERAN carrier frequency group list
Cell reselection priority per carrier frequency group
GERAN neighboring cell information
Threshold values for cell reselection criteria
Cell reselection timer
Parameters for speed dependent cell reselection
BENEFIT
The operator can provide idle mobility to its subscribers to GERAN.
Users in idle state can move to GERAN.

Dependency
GERAN supported Device, EPC, and GERAN should support this feature.
FEATURE DESCRIPTION
The eNB supports UE's idle mobility through its SIB broadcasting. In the idle
mode, UE receives the SIB broadcast by the cell it has camped onto, and performs
inter-RAT cell reselection to GERAN based on the cell reselection parameter
contained in the SIBs.
The SIBs are used to perform the following functionality:
The SIB1 provides information that is required in evaluating if UE is allowed to
access a cell. The UE uses this for PLMN selection and cell selection. Also,
SIB1 defines the scheduling of other system information. The UE acquires
other SIBs of the cell using this information.
The SIB3 provides the common information required for intra-frequency, inter-
frequency and/or inter-RAT cell reselection. Also, it conveys the specific
information for intra-frequency cell reselection.
The SIB7 provides information about GERAN frequencies and parameters for
cell re-selection.
The GERAN cell reselection parameters broadcasted via SIB7 are as follows:
GERAN carrier frequencies per GERAN carrier frequency group
oA set of GERAN carrier frequencies can be provided in three ways
(explicitListOfARFCNs, equallySpacedARFCNs, and
variableBitMapOfARFCNs) as per 3GPP.
Cell reselection priority per GERAN carrier frequency group
Cell reselection thresholds per GERAN carrier frequency group
Cell reselection timer for GERAN cell reselection
Cell reselection timer for speed dependant GERAN cell reselection
oFor fast moving UE speed dependent GERAN cell reselection scaling factors
are applied. If the number of reselections during the period TCRmax is
greater than NCR_H high mobility is detected. If the number exceeds
NCR_M and not NCR_H then medium mobility is detected. In the
high/medium mobility states Qhyst and TreselectionRAT are multiplied by
the Speed dependent scaling factor Qhyst and Treselection. The reselection
to GERAN is performed if (Srxlev_GSM - Qrxlevmin in SIB7) > (Srxlev
of LTE cell - Qrxlevmin in SIB3 + Qhyst in SIB3)
Cell Reselection Triggering and Measurement

The inter-RAT cell reselection procedures are triggered when one of the following
conditions is met:
The UE has E-UTRA frequencies or GERAN frequencies with a reselection
priority higher than the reselection priority of the current E-UTRA frequency.
In this case, UE performs inter-RAT cell reselection procedures. The UE
searches every layer of higher priority at least every
T_higher_priority_search=(60 * N_layers) seconds, where N_layers is the
total number of configured higher priority E-UTRA carrier frequencies and is
additionally increased by one if one more group of GERAN frequencies is
configured as a higher priority (3GPP TS 36.133 Section 4.2.2).
The service cell does not fulfil S_rxlev > S_NON_INTRA_SEARCH_P and
S_qual > S_NON_INTRA_SEARCH_Q. In this case, UE performs inter-RAT
cell reselection procedures for E-UTRA inter-frequency or GERAN frequency
with an equal or lower reselection priority than the reselection priority of the
current E-UTRA frequency.
The priority of each frequency is broadcast in SIB3 (E-UTRA frequency) and
SIB7 (GERAN frequency).
Since RSRQ can vary even in the center of the serving cell from -3 dB to -10 dB
depending on traffic load from the serving cell, devices will test S_rxlev only.
The UE triggers the measurement of GERAN frequency when RSRP signal

strength from LTE serving cell decreases below the calculated threshold.
Cell Reselection Criteria from LTE to 2G

Assuming that the priority of GERAN frequency is lower than E-UTRAN, cell
reselection to a cell on a lower priority GERAN frequency than the serving
frequency is performed according to GERAN cell reselection criteria shown in the
following figure.
The UE reselects the GERAN cell when RSRP signal strength from LTE serving
cell decreases to less than the threshold calculated and the signal strength of
GERAN target cell increases to more than the calculated threshold (3GPP TS
36.304 Section 5.2.4.5).
Cell reselection from 2G to LTE

The UE in idle mode may be connected to either LTE or GERAN network
depending on the radio condition.
The UE selects primary LTE frequency when UE ends a CSFB call or when UE
comes back into LTE coverage in the presence of acceptable LTE signal.
Cell reselection from GERAN to LTE is performed by UE, based on the system
information provided by GERAN. The UE in GERAN monitors the broadcast
channel from the GERAN serving cell during idle mode to retrieve System
Information 2Quarter message for preparation of cell reselection to E-UTRAN.
After cell reselection to E-UTRAN is completed, UE performs a Tracking Area
update in E-UTRAN.
SYSTEM OPERATION
How to Activate
To enable this feature, operator should configure the SIB7_PERIOD in CHG-
SIB-INF and the GERAN Frequency Information by executing the CHG-
GERAN-FA command.
Key Parameters
CHG-SIB-INF/RTRV-SIB-INF
SIB7_PERIOD This parameter is the transmission period for the system information block type
7 of the cell in eNB. The SIB7 contains information for IRAT cell reselection to
GERAN.
ms80: 80 ms.
ms160: 160 ms.
ms5120: 5120 ms.
not_used: SIB7 is not transmitted.
CHG-GERAN-FA/RTRV-GERAN-FA
STATUS This parameter indicates whether GERAN FA object is valid.
N_EQUIP: Invalid.
EQUIP: Valid.
FOLLOWING_ARFCNS The following ARFCNs are the choice option to select the remaining ARFCN
values except starting ARFCN.
explicitList: used for explicitListOfARFCNs. Set geranArfcn0 ~ geranArfcn31.
equallySpaced: used for equallySpacedARFCNs. Set geranArfcn0,
arfcnSpacing and numberOfFollowingARFCNs.
variableBitMap: used for variableBitMapOfARFCNs. Set geranArfcn0 and
variableBitMapOfARFCNs.
GERAN_ARFCN0 This parameter is the Absolute Radio Frequency Channel Number (ARFCN) of
GERAN FA object (Start ARFCN).
GERAN_ARFCN1 ~ This parameter is the Absolute Radio Frequency Channel Number (ARFCN) of
GERAN_ARFCN31 GERAN FA object.
ARFCN_SPACING If followingARFCNs is set to equallySpaced, arfcnSpacing becomes Space, d,
between a set of equally spaced ARFCN values.
NUMBER_OF_FOLLOWING If followingARFCNs is set to equallySpaced, numberOfFollowingARFCNs
_ARFCNS becomes The number, n, of the remaining equally spaced ARFCN values in
the set. The complete set of (n+1) ARFCN values is defined as: {s, ((s + d)
mod 1024), ((s + 2*d) mod 1024) ... ((s + n*d) mod 1024)}, where s is
startingARFCN (geranArfcn0).
VARIABLE_BIT_MAP_OF_ If followingARFCNs is set to variableBitMap, variableBitMapOfARFCNs
ARFCNS [16] becomes Bitmap field representing the remaining ARFCN values in the set.
The leading bit of the first octet in the bitmap corresponds to the ARFCN = ((s
+ 1) mod 1024), the next bit to the ARFCN = ((s + 2) mod 1024), and so on. If
the bitmap consist of N octets, the trailing bit of octet N corresponds to ARFCN
= ((s + 8*N) mod 1024). The complete set of ARFCN values consists of
ARFCN = s and the ARFCN values, where the corresponding bit in the bitmap
is set to 1 and s is startingARFCN (geranArfcn0).
Counters and KPIs

REFERENCE
LTE-SW1302, PS Handover between LTE and

GERAN
INTRODUCTION
When a user under LTE data services area and moves to GERAN, eNB transits the
service to GERAN using the PS handover procedure to provide seamless data
services.
The eNB determines PS handover to GERAN based on the GERAN measurement
report in UE. When eNB receives the GERAN measurement results in UE, it
selects the handover target cells from the results and processes the handover
preparation procedure.
Once the handover procedure is successful with GERAN, eNB requests UE
handover to GERAN (PS handover). The UE makes handover to the target cell of
GERAN specified by eNB, and receives data services from GERAN.
When a user under data services moves from GERAN, eNB provides seamless
data services using the PS handover procedure with GERAN.
When eNB received a handover request from the MME, it determines whether to
accept HO based on the Call Admission Control (CAC) of the HO. When HO
acceptance is determined, eNB transmits an acknowledge message for the
handover request to the MME, after assigned resources for that HO. After that, UE
moves to LTE as per the direction from source GERAN, and after the PS handover
from GERAN procedure succeeded, it continues data services in the LTE.
BENEFIT
The operator can provide connected mobility to its subscribers between E-
UTRAN and GERAN.
Users in a connected state can move between E-UTRAN and GERAN, remaining
in the connected state.

Dependency
GERAN supported Device, EPC, and GERAN shall support this feature based on
3GPP Rel-8. It needs inter operability test (IOT) with commercial UE which
support PS Handover between LTE and GERAN.
FEATURE DESCRIPTION
To support seamless data service when UE moves from E-UTRAN to GERAN
coverage, Samsung eNB supports PS handover to GERAN under the following
conditions:
Target GERAN shall support PS handover
UE shall support measurement reporting for GERAN frequencies in E-UTRA
connected mode (FGI#15 for B1, FGI#23 for B2).
UE shall support handover to GERAN (FGI#9).
GERAN frequencs shall be configured for PS handover
oEach GERAN frequency group can be configured to support CS service, PS
service, or both.
oA set of GERAN frequencies can be provided in three ways
(explicitListOfARFCNs, equallySpacedARFCNs,
variableBitMapOfARFCNs) as per 3GPP.
Once the above conditions are met, serving eNB sends measurement configuration
including event A2 (Serving is worse than a threshold value) to trigger GERAN
measurement. On reception of measurement report triggered by event A2,
Samsung eNB configures GERAN measurement using event B1 or B2. The
serving eNB also configures measurement gap for inter-RAT measurement, and
UE performs GERAN measurement during the configured gap period. If
measurement report for event B1 or B2 is received, the serving eNB starts
handover preparation to the target cell.
The following figure shows PS handover procedure to the GERAN:
1) The UE transmits measurement report including the GERAN measurement for

GERAN frequencies.
2) The source eNB determines PS handover to the GERAN.
3) The source eNB requests PS handover to the GERAN by transmitting the
Handover required to the source MME.
4)~10) The handover preparation procedure between source E-UTRAN and target
GERAN is processed. The resource allocation is made so that the UE can maintain
data services at the target GERAN after PS handover through this procedure.
When data forwarding is available, the tunnel setup for data forwarding is made.
11) The source eNB receives a handover command from the source MME.
12) The source eNB transmits mobility from E-UTRA command to UE, including
the HO command received from the GERAN.
13) The UE makes transition to the GERAN target cell as per the direction from
the eNB, and transmits XID response to the GERAN.
14) The target BSC informs handover completion by transmitting PS handover
complete to target SGSN. It also transmits XID response to the target SGSN.
15)~21) The target SGSN processes handover completion procedure with the
source MME.
22) The UE performs the Routing Area update. After that, it keeps data services in
the GERAN.
23)~27) The source MME releases the resources used in E-UTRAN after complete
PS handover with GERAN. When a tunnel for data forwarding is setup, the source
MME and target SGSN release the data forwarding tunnel.
In case PS handover from GERAN, handover decision is made by GERAN and
eNB starts handover preparation, if it receives S1AP Handover Request message
from MME.
The following figure shows PS handover procedure from the GERAN:
1) The source BSC determines PS handover to the E-UTRAN.

2) The source BSC requests PS handover to the E-UTRAN, transmitting PS
Handover required to source SGSN.
3)~ 9) The handover preparation procedure between source GERAN and target E-
UTRAN is processed. The resource allocation is made so that UE can maintain
data services at the target E-UTRAN after PS handover through this procedure.
When data forwarding is available, the tunnel setup for data forwarding is made.
10) The source BSC receives PS Handover required acknowledge from source
SGSN.
11) The source BSC transmits PS HO command to UE including HO command

received from the target E-UTRAN.
12) The UE transits to the E-UTRAN target cell as per the direction from source
BSC, and transmits the RRC connection reconfiguration complete to the E-
UTRAN.
13) The target eNB transmits the Handover notify to the target MME to notify that
handover is completed.
14)~18) The target MME processes the handover completion procedure with
source SGSN.
19) The source SGSN processes BSS packet flow release procedure with source
BSC.
20) The UE performs the tracking area update procedure. After that, it keeps data
services in the E-UTRAN.
21)~23) The source SGSN releases resources used in the GERAN after completing
the PS handover with E-UTRAN. When a tunnel for data forwarding is setup,
source SGSN and target MME release the data forwarding tunnel.
SYSTEM OPERATION
How to Activate
Information by executing the CHG-GERAN-FA command and A2 report
configuration for ci_A2PurposeIRatHo and B2 report configuration for the each
GERAN carrier.
The handover target GERAN cell needs to be registered in the serving cell
neighboring cell list.
Key Parameters
N_EQUIP: Invalid.
EQUIP: Valid.
FOLLOWING_ARFCNS The followingARFCNs is the choice option to select the remaining ARFCN
values except startingARFCN.
the GERAN FA object. (Start ARFCN)
Config.
CHG-GERAN-B2CNF/RTRV-GERAN-B2CNF
PURPOSE This parameter is the usage of GERAN Event B2 report. It is used for inter-
RAT Handover.
InterRatHandover: In case of Inter-RAT handover.
Srvcc: In case of SRVCC.
handover mobility option.
Spare_1: Reserved.
Spare_2: Reserved.
ACTIVE_STATE This parameter indicates whether the GERAN Event B2, which is triggered
when Inter RAT neighbor becomes better than threshold, is enabled/disabled.
This change will be applied to the UE from next RRC signaling procedure (for
updated to the current active UEs.
Inactive: GERAN Event B2 is not used.
Active: GERAN Event B2 is used.
CHG-NBR-GERAN/RTRV-NBR-GERAN/CRTE-NBR-GERAN/DLT-NBR-
GERAN
STATUS The validity of GERAN neighboring cell information.
N_EQUIP: Invalid
EQUIP: Valid
TARGET_CELL_ID The ID of GERAN neighboring cell to eNB.
LAC This parameter is the Location Area Code of GERAN neighbor cell located
around eNB. The location area code of GERAN neighboring cell to eNB.
RAC This parameter is the routing area code of GERAN neighbor cell located
around eNB.
NETWORK_COLOUR_COD The network color code of GERAN neighboring cell to eNB. Codes are from 0
E to 7. Ensure that not to enter previously entered information. If all three of the
networkColourCode, baseStationColourCode, and ARFCN information match
previously entered information, the system determines it to be a duplicated
entry.
BASE_STATION_COLOUR This parameter is the base station color code of GERAN neighbor cell located
_CODE around eNB.
MCC [4] The PLMN information (MCC) of GERAN neighboring cell to eNB. It is a three-
digit number with each digit being from 0 to 9.
MNC [4] The PLMN information (MNC) of GERAN neighboring cell to eNB. It is a three-
digit or two-digit number with each digit being from 0 to 9.
ARFCN This parameter is the ARFCN of the GERAN neighbor cell located around the
eNB.
BAND_INDICATOR The band indicator of GERAN neighboring cell to eNB.
dcs1800: Indicates DCS 1800 band.
pcs1900: Indicates PCS 1900 band.
Counters and KPIs

HO_INTER_RAT_GERAN_ RatGeranOutAtt LTE to inter-RAT GERAN handover
OUT attempt count
RatGeranOutPrepSucc LTE to inter-RAT GERAN handover
RatGeranOutSucc LTE to inter-RAT GERAN handover
RatGeranOutPrepFail_CpCcFail Preparation fails due to reset

notification (eNB failure or block restart)
from ECMB or by ECCB block during
inter GERAN Handover preparation.
RatGeranOutPrepFail_S1apCuFail Preparation fails due to S1AP
specification cause during the GERAN
RatGeranOutPrepFail_S1apLinkFail Preparation fails due to S1 SCTP link
failure during the GERAN handover
preparation.
RatGeranOutPrepFail_S1apRpTo Preparation fails due to S1AP relocprep
timeout (not received) during the
GERAN Handover preparation.
RatGeranOutPrepFail_S1apSigFail Preparation fails due to receiving S1AP
signaling during the GERAN handover
preparation.
RatGeranOutFail_CpCcTo A call is released due to call control
timeout in the protocol blocks (MAC,
RLC, PDCP, and GTP) during the
GERAN handover execution.
RatGeranOutFail_CpCcFail A call is released due to reset
from the ECMB or by the ECCB block
during the GERAN Handover execution.
RatGeranOutFail_UpGtpFail A call is released due to internal failure
in the GTP block during the GERAN
handover execution.
RatGeranOutFail_UpMacFail A call is released due to internal failure
in the MAC block during the GERAN
handover execution.
RatGeranOutFail_UpPdcpFail A call is released due to internal failure
in the PDCP block during the GERAN
handover execution.
RatGeranOutFail_UpRlcFail A call is released due to internal failure
in the RLC block during the GERAN
handover execution.
RatGeranOutFail_RrcSigFail A call is released due to receiving RRC
execution.
RatGeranOutFail_S1apCuFail A call is released due to the S1AP
handover execution.
RatGeranOutFail_S1apLinkFail A call is released due to the S1 SCTP
link failure during the GERAN handover
execution.
RatGeranOutFail_S1apRoTo A call is released due to an S1AP
relocoverall timeout (not received)
during the GERAN Handover execution.
RatGeranOutFail_S1apSigFail A call is released due to receiving S1AP
execution.
HO_INTER_RAT_GERAN_I RatGeranInAtt LTE to inter-RAT GERAN handover

N attempt count
RatGeranInPrepSucc LTE to inter-RAT GERAN handover
RatGeranInSucc LTE to inter-RAT GERAN handover
RatGeranInPrepFail_CpCcTo Preparation fails due to call control
GERAN handover preparation.
RatGeranInPrepFail_CpCcFail Preparation fails due to reset
from ECMB or by ECCB block during
GERAN Handover preparation.
RatGeranInPrepFail_UpGtpFail Preparation fails due to internal failure
Handover preparation.
RatGeranInPrepFail_UpMacFail Preparation fails due to internal failure
RatGeranInPrepFail_UpPdcpFail Preparation fails due to internal failure
RatGeranInPrepFail_UpRlcFail Preparation fails due to internal failure
RatGeranInPrepFail_CpBhCacFail Preparation fails due to insufficient
backhaul-based eNB resources during
the GERAN handover preparation.
RatGeranInPrepFail_CpCapaCacFa Preparation fails due to insufficient
il capacity-based eNB resources during
the GERAN handover preparation.
RatGeranInPrepFail_CpQosCacFail Preparation fails due to insufficient
QoS-based eNB resources during the
GERAN handover preparation.
RatGeranInPrepFail_S1apCuFail Preparation fails due to S1AP
RatGeranInPrepFail_S1apLinkFail Preparation fails due to S1 SCTP link
failure during the GERAN handover
preparation.
RatGeranInPrepFail_S1apSigFail Preparation fails due to receiving S1AP
signaling during GERAN Handover
preparation.
RatGeranInFail_CpCcTo A call is released due to call control
GERAN Handover execution.
RatGeranInFail_CpCcFail A call is released due to reset
from the ECMB or by the ECCB block
during GERAN Handover execution.
RatGeranInFail_UpGtpFail A call is released due to internal failure

handover execution.
RatGeranInFail_UpMacFail A call is released due to internal failure
handover execution.
RatGeranInFail_UpPdcpFail A call is released due to internal failure
handover execution.
RatGeranInFail_UpRlcFail A call is released due to internal failure
handover execution.
RatGeranInFail_RrcHcTo A call is released due to HO command
GERAN Handover execution.
RatGeranInFail_RrcSigFail A call is released due to receiving RRC
execution.
RatGeranInFail_S1apCuFail A call is released due to the S1AP
handover execution.
RatGeranInFail_S1apLinkFail A call is released due to the S1 SCTP
link failure during the GERAN handover
execution.
RatGeranInFail_S1apSigFail A call is released due to receiving S1AP
execution.
RatGeranInFail_S1apSigTo A call is released due to S1AP signaling
GERAN handover execution.
REFERENCE
LTE-SW1304, Cell Change Order to GERAN

without NACC
INTRODUCTION
Cell Change Order to GERAN is another outbound mobility feature in addition to
PS handover and redirection. Compared to PS handover, Cell Change Order does
not prepare user session in the target GERAN.
The eNB determines whether to perform the Cell Change Order to GERAN based
on UEs measurement report. In addition, eNB specifies the carrier frequency and
target cell for GERAN to which UE needs to move (without including system
information of the target cell).
Then, UE releases the connection to E-UTRAN and switches over to the target
carrier frequency of GERAN specified by eNB to receive data service from
GERAN.
BENEFIT
to GERAN.
Users in connected state can move from E-UTRAN to GERAN.

Dependency
FEATURE DESCRIPTION
Cell Change Order without NACC could be performed under the following
conditions:
UE or target GERAN does not support PS handover
oOptionally, measurement could be omitted via configuration
UE shall support cell change order procedure (FGI#10).
System Information of the target cell is not provided (without NACC).
Once the above conditions are met, serving eNB sends measurement configuration
including event A2 (Serving is worse than a threshold value) to trigger GERAN
measurement. On reception of measurement report triggered by event A2,
Samsung eNB configures GERAN measurement using event B1 or B2. The
serving eNB also configures measurement gap for inter-RAT measurement, and
UE performs GERAN measurement during the configured gap period. If
measurement report for event B1 or B2 is received, the serving eNB starts Cell
Change Order without NACC procedure
The following figure shows the procedure to perform Cell Change Order without
NACC to GERAN:
1 The eNB determines whether to switch the cell change order without NACC to
GERAN.
2 The eNB specifies GERAN carrier frequency and target GERAN cell to which
UE is to switch over and transmits the Mobility from EUTRA Command to
UE.
3 The eNB transmits UE Context Release Request to MME.
4 The MME transmits UE Context Release Command to eNB.
5 The eNB transmits UE Context Release Complete to MME.
6 The UE switches over to the target GERAN cell of GERAN carrier, which is
designated by eNB to the Mobility from EUTRA Command and connects to
GERAN. The procedures of GERAN location registration and GERAN call
setup are performed. Then, UE keeps providing its service in the GERAN.
SYSTEM OPERATION
How to Activate
Information by executing the CHG-GERAN-FA command and configure A2
GERAN and PS handover to GERAN.
The operator can put the high priority on CCO to GERAN without NACC by
executing the CHG-GERAN-INTWO command for Normal type based on UE
measurement and Blind type without UE measurement. The lower number
priority has the higher priority.
If blindCCOsupport in CHG-GERAN-INTWO is set to True, Blind CCO is
supported during interworking with GERRAN and Target GERAN cell for
Blind CCO should be configured by executing the CHG-GERAN-BLCCO
command.
Key Parameters
N_EQUIP: Invalid.
EQUIP: Valid.
GERAN FA object. (Start ARFCN)
Config.
INTER_RAT_DATA_OPTIO This parameter indicates whether to force redirection during the inter RAT PS
N handover for Data Call.
CHG-GERAN-INTWO/RTRV-GERAN-INTWO
NORMAL_PRIORITY0 This parameter indicates the first priority in the normal type GERAN
interworking procedure.
ccoWithNACC: CCO with NACC.
ccoWithoutNACC: CCO without NACC.
enhancedRedirection: Enhanced Redirection with SI.
geranRedirecdtion: Redirection without SI.
NORMAL_PRIORITY1 This parameter indicates the second priority in the normal type GERAN
NORMAL_PRIORITY2 This parameter indicates the third priority in the normal type GERAN
NORMAL_PRIORITY3 This parameter indicates the fourth priority in the normal type GERAN
BLIND_PRIORITY0 This parameter indicates the first priority of blind type GERAN interworking
procedure.
BLIND_PRIORITY1 This parameter indicates the second priority in the normal type GERAN
BLIND_PRIORITY2 This parameter indicates the third priority in the normal type GERAN
BLIND_PRIORITY3 This parameter indicates the fourth priority in the normal type GERAN
BLIND_CCOSUPPORT This parameter indicates whether to support blind Cell Change Order (CCO)
during GERAN interworking.
False: Blind CCO not supported.
True: Blind CCO supported.
CHG-GERAN-BLCCO/RTRV-GERAN-BLCCO
TARGET_GERAN_NBR_IDX This parameter is the target GERAN neighbor cell index where the blind CCO
will be performed for the relevant cell.- geranRedirecdtion: Redirection without
SI.
Counters and KPIs

CCO_GERAN_OUT CcoGeranAtt LTE to Inter RAT GERAN CCO attempt count
CcoGeranPrepSucc LTE to Inter RAT GERAN CCO preparation success
count
CcoGeranSucc LTE to Inter RAT GERAN CCO execution success
count
REFERENCE
LTE-SW1305, Cell Change Order to GERAN with

NACC
INTRODUCTION
Cell Change Order to GERAN is another outbound mobility feature in addition to
PS handover and redirection. Compared to PS handover, Cell Change Order does
not prepare user session in the target GERAN.
The eNB determines whether to perform the Cell Change Order to GERAN based
on UEs measurement report. In addition, eNB specifies the carrier frequency and
target cell for GERAN to which UE needs to move (including system information
of the target cell). System information is exchanged using RIM procedure.
Then, UE releases the connection to E-UTRAN and switches over to the target
carrier frequency of GERAN specified by eNB to receive data service from
GERAN.
BENEFIT
to GERAN.

Dependency
RIM for SI tunneling shall be support EPC and GERAN.
Limitation
RIM based SI tunneling is only possible for eNB to acquire GERAN NACC
information.
FEATURE DESCRIPTION
Cell Change Order with NACC could be performed under the following conditions.
oOptionally, measurement could be omited via configuration
System Information of the target cell is provided (with NACC).

The following figure shows the procedure to switch cell change order with NACC
to GERAN:
1 The eNB determines whether to switch the cell change order with NACC to
GERAN.
2 The eNB specifies GERAN carrier frequency and target GERAN cell to which
UE is to switch over and, including the SI list of the target GERAN cell,
transmits the Mobility from EUTRA Command to UE.
6 The UE switches over to the target GERAN cell of the GERAN carrier, which is
designated by eNB to the Mobility from EUTRA Command and connects to
GERAN. The procedures of GERAN location registration and GERAN call
setup are performed. Then, UE keeps providing its service in the GERAN.
SYSTEM OPERATION
How to Activate

The operator can put the high priority on CCO to GERAN with NACC by
Blind CCO should be configured by executing the CHG-GERAN-BLCCO.
isAllowedRim parameter should be set as True using CHG-HO-OPT. This
parameter configures the RIM procedure and rimSupport parameter should
be set as True by executing the CHG-NBR-GERAN.
Key Parameters
N_EQUIP: Invalid.
EQUIP: Valid.
the GERAN FA object. (Start ARFCN)
GERAN_ARFCN31 the GERAN FA object.
_ARFCNS becomes the number, n, of the remaining equally spaced ARFCN values in the
set. The complete set of (n+1) ARFCN values is defined as: {s, ((s + d) mod
1024), ((s + 2*d) mod 1024) ... ((s + n*d) mod 1024)}, where s is
Ca: Used for Carrier Aggregation.
Config.
frequency. This change will be applied to the UE from next RRC signaling
procedure.
BLIND_CCOSUPPORT This parameter indicates whether to support blind Cell Change Order (CCO)
TARGET_GERAN_NBR_ID This parameter is the target GERAN neighbor cell index where the blind CCO
X will be performed for the relevant cell.- geranRedirecdtion: Redirection without
SI.
GERAN
RIM_SUPPORT This parameter indicates whether or not the RIM procedure of a Neighbor
GERAN Cell is supported. It must be set accurately since the RIM procedure
execution is determined by the setting.
Counters and KPIs

CCO_GERAN_OUT CcoGeranAtt LTE to Inter RAT GERAN CCO attempt count
CcoGeranPrepSu LTE to Inter RAT GERAN CCO preparation success count
cc
CcoGeranSucc LTE to Inter RAT GERAN CCO execution success count
REFERENCE
LTE-SW1306, Redirection to GERAN without SI

INTRODUCTION
The eNB ensures its seamless data service by switching to GERAN using the
procedure of redirection without SI when a user providing LTE data service gets
out of LTE area.
The eNB determines whether to switch the redirection to GERAN based on UEs
measurement report.
When the redirection of GERAN is determined, eNB clears UEs RRC connection
and specifies the carrier frequency of GERAN to which UE is to switch over
(redirection without SI).
The UE switches over to the target carrier frequency of GERAN, which is
specified by eNB to receive data service from the GERAN.
BENEFIT
to GERAN.

Dependency
FEATURE DESCRIPTION
The following figure shows the procedure to switch the redirection without SI to
GERAN:
1 The eNB determines whether to switch the redirection to GERAN.

2 The eNB includes GERAN carrier frequency to which UE is to switch over and
transmits the RRC Connection Release to UE.
6 The UE switch over to GERAN that eNB specifies to the RRC Connection
Release, and connects to GERAN. Also, UE initiates GERAN location
registration procedure. Then, UE is on standby in GERAN and continues to
provide the service.
SYSTEM OPERATION
How to Activate
The operator can put the high priority on Redirection to GREAN without SI by
Key Parameters
N_EQUIP: Invalid.
EQUIP: Valid.
Config.
frequency. This change will be applied to the UE from next RRC signaling
procedure.
Counters and KPIs

REDIR_GERAN_OUT RedirGeranAtt LTE to Inter RAT GERAN Redirection attempt count
RedirGeranPrepS LTE to Inter RAT GERAN Redirection preparation success
ucc count
RedirGeranSucc LTE to Inter RAT GERAN Redirection execution success
count
REFERENCE
LTE-SW1307, Redirection to GERAN with SI

INTRODUCTION
The eNB ensures its seamless data service by switching to GERAN using the
procedure of redirection with SI when a user providing LTE data service gets out
of LTE area.
The eNB determines whether to perform the redirection to GERAN based on UEs
measurement report. When the redirection of GERAN is determined, eNB clears
UEs RRC connection, specifies the carrier frequency of GERAN to which UE is
to switch over, and delivers GERAN cell list and the system information (SI) lists
of each cell (redirection with SI). Finally, UE switches over to the target carrier
frequency of GERAN specified by eNB to receive data service from GERAN.
To expedite GERAN access, the RAN Information Management (RIM)
interworking between eNB and GERAN is required to process the redirection with
SI. The eNB obtains and stores SI lists of each cell from an adjacent GERAN
through the RIM procedure. In addition, eNB use the SI lists of each cell when
processing the redirection with SI.
BENEFIT
to GERAN.

Dependency
GERAN supported Device, EPC and GERAN should support this feature.
Limitation
RIM based SI tunneling is only possible for eNB to acquire GERAN SI.
FEATURE DESCRIPTION
The following figure shows the procedure to switch the redirection with SI to
GERAN:
RRC Connection Release message includes cellInfoList-r9 IE which contains SI of

the target cells.
1 The eNB determines whether to switch the redirection to GERAN.

2 The eNB transmits the RRC Connection Release, including GERAN carrier
frequency, GERAN list, and SI lists of each cell.
6 The UE switch over to GERAN that eNB specifies to the RRC Connection
Release, and connects to the GERAN. Also, UE initiates GERAN location
registration procedure. Then, UE is on standby in GERAN and continues to
provide the service.
SYSTEM OPERATION
How to Activate
The operator can put the high priority on Redirection to GERAN with SI
(Enhanced Redirection) by executing the CHG-GERAN-INTWO command for
Normal type based on UE measurement and Blind type without UE
measurement. The lower number priority has the higher priority.
rimSupport parameter should be set as True by executing the CHG-NBR-
GERAN command.
Key Parameters
N_EQUIP: Invalid.
EQUIP: Valid.
Config.
procedure.
GERAN
Counters and KPIs

REDIR_GERAN_OUT RedirGeranAtt LTE to Inter RAT GERAN Redirection attempt count
RedirGeranPrepSucc LTE to Inter RAT GERAN Redirection preparation success
count
RedirGeranSucc LTE to Inter RAT GERAN Redirection execution success
count
REFERENCE
LTE-SW1310, CSFB to GERAN with Redirection

with SI
INTRODUCTION
CS fallback is the function to provide voice service to LTE users before the
introduction of Voice over LTE (VoLTE), it switches UE over to CS domain to
provide mobile originated/mobile terminated call. The CSFB to GERAN with
Redirection with System Information (SI) function switches UE to GERAN by the
redirection with SI procedure when sending or receiving the CSFB.
When the S1 message including the CSFB indicator is received from MME, eNB
clears UEs RRC connection, specifies the carrier frequency of GERAN to which
UE is to switch over, and delivers GERAN cell list and the system information
(SI) lists of each cell (redirection with SI). The UE switches over to the target
carrier frequency of GERAN specified by eNB and initiates the voice call
sending/receiving procedure. This function delivers GERAN carrier frequency
together with the SI lists of each GERAN cell, which reduces the processing time
taken after UE switches over to GERAN, resulting in contributing to the
improvement of CSFB call quality.
To provide system information, RAN Information Management (RIM)
interworking between eNB and GERAN is necessary to process the CSFB to
GERAN with Redirection with SI. The eNB obtains and stores SI lists of each cell
from an adjacent GERAN through the RIM procedure. In addition, eNB use the SI
lists of each cell when processing the CSFB to GERAN with Redirection with SI.
BENEFIT
network (GERAN)
network (GERAN)

Dependency
Limitation
RIM based SI tunneling is only possible for eNB to acquire GERAN SI (Manual
configuration in LSM is not available).
FEATURE DESCRIPTION
Regardless of UE movement, CSFB is triggered when there is mobile originating
or mobile terminating call.
To support CSFB service, 2G network coexists with LTE network where in MME
serves users while in LTE access network, and SGSN serves users while in 2G
access network. In 2G network, SGSN serves users when utilizing data services
and MSC (Mobile Switching Center) when utilizing voice services. To support CS
Fallback signaling, MME connects to MSC with SGs interface. The SGs interface
is used for the mobility management and paging procedures between EPS and CS
domain. Also, it is also used for the delivery of both mobile originating and
terminating SMS.
Combined EPS/IMSI Attach, there is a requirement to use SGs interface between
MME and MSC.
The following figure shows the procedure for performing CSFB with Redirection
to GERAN with SI:
RRC Connection Release includes cellInfoList-r9 IE to provide system information

of target cells.
1) The UE initiates the CSFB procedure. If UE is in idle state, UE via RRC

connection establishment procedure switches over to the connected state. The
figure below shows the case when UE is in Active state.
2) The UE transmits the NAS EXTENDED SERVICE REQEUST, which is
embedded in RRC UL Information Transfer message.
3) The eNB relays NAS message to MME using S1AP Uplink NAS Transport
message
4) The MME transmits the S1AP initial Context setup Request message in which
the CSFB indicator is included to eNB. In case UE is in idle state, eNB processes
the AS security activation and the default bearer setup procedure.
5) The eNB transmits the S1AP Context setup Response message to MME.
6) The eNB includes the GERAN carrier frequency to which UE is to switch over
and transmits the RRC Connection Release to UE with system information of
candidate cells. (Optionally, eNB may request measurement of GERAN before
step 6)
7~11) The eNB transmits UE Context Release Request to MME. The MME
processes the S1 release procedure with eNB.
13) The UE switches over to GERAN carrier frequency provided in the RRC
Connection Release by eNB and connects to GERAN carrier frequency. It initiates
the GERAN location registration procedure.
14) If GERAN cannot provide simultaneous CS and PS service, UE requests
GERAN to suspend the PS service.
15~16) The SGSN processes MME and bearers suspension procedure by UEs
request. The MME suspends S-GW and PS bearers by the request from SGSN.
17) Then, UE performs CS call setup and continues providing the CS service.
The following figure shows the call procedure for CSFB when UE is in Idle state:
SYSTEM OPERATION
How to Activate
Information by executing the CHG-GERAN-FA command.
The operator can put the high priority on CSFB to GERAN with Redirection with
SI (Enhanced Redirection) by executing the CHG-GERAN-INTWO command
for Normal type based on UE measurement and Blind type without UE
measurement. The lower number priority has the higher priority.
rimSupport parameter should be set as True by executing CHG-NBR-
GERAN command.
Key Parameters
N_EQUIP: Invalid.
EQUIP: Valid.
procedure.
GERAN
Counters and KPIs

CSFB_REDIR_GERAN_OUT CSFBGeranRedirAtt Count of CSFB with Inter RAT GERAN
Redirection attempts
CSFBGeranRedirPrepSucc Count of CSFB with Inter RAT GERAN
Redirection preparation successes
CSFBGeranRedirSucc Count of CSFB with Inter RAT GERAN
Redirection execution successes
REFERENCE
LTE-SW1311, CSFB to GERAN with CCO without

NACC
INTRODUCTION
introduction of Voice over LTE (VoLTE), it switches UE over to CS domain to
provide mobile originated/mobile terminated call (Refer to SW1309).
The CSFB to GERAN with Cell Change Order (CCO) without Network Assisted
Cell Change (NACC) function switches UE to GERAN by CCO without NACC
procedure.
When the S1 message including the CS FB indicator is received from MME, eNB
provides the cell change order to UE and specifies carrier frequency and target cell
of GERAN to which the CSFB indicator and UE are to switch over (CCO without
NACC). The UE switches over to the target cell of GERAN specified by eNB and
initiates the voice call sending/receiving procedure.
Whether to use CCO or release with redirection could be configured by LSM.
BENEFIT
network (GERAN)
network (GERAN)

Dependency
GERAN supported Device, EPC, and GERAN shall support this feature.
FEATURE DESCRIPTION
The CSFB to GERAN with Cell Change Order (CCO) without Network Assisted
Cell Change (NACC) function switches UE to GERAN by CCO without NACC
procedure.
When S1 message including the CS FB indicator is received from MME, eNB
provides the cell change order to UE and specifies carrier frequency and target cell
in the GERAN to which the CSFB indicator and UE are to switch over (CCO
without NACC). The UE switches over to the target cell of GERAN specified by
eNB and initiates the voice call sending/receiving procedure.
CCO without NACC could be performed under the following conditions:

connected mode (FGI#15 for B1, FGI#23 for B2)
UE shall support cell change order procedure (FGI#10)
System Information of the target cell is not provided (without NACC)
The following figure shows the call flow for CSFB to GERAN with CCO without
NACC:
1) The UE initiates CSFB procedure. If UE is in idle state, UE using the RRC

connection establishment procedure switches over to the connected state.
2) The UE transmits NAS EXTENDED SERVICE REQEUSTembedded in RRC
UL Information Transfer message.
message
4) The MME transmits the S1AP Initial Context setup Request message in which
the CSFB indicator is included to eNB. In case of UE is in idle state, eNB
processes the AS security activation and default bearer setup procedure.
5) The eNB transmits the S1AP Initial Context Setup Response message to MME.
6) The eNB specifies GERAN carrier frequency and target GERAN cell to which
UE is to switch over and transmits the Mobility from EUTRA command to UE.
(The eNB may request measurement of GERAN before step 6. This measurement
will increase total CSFB latency)
13) The UE switches over to GERAN carrier frequency given by eNB and
connects to GERAN. It initiates the GERAN location registration procedure.
14) If GERAN cannot provide simultaneous CS and PS service, UE requests
15~16) The SGSN processes the bearers suspension procedure by UEs request.
The MME suspends S-GW and PS bearers by the request from SGSN.
17) Then, UE performs CS call setup and continues to provide the CS service.
The following figure shows the procedure for UE in idle state:
SYSTEM OPERATION
How to Activate
The operator can put the high priority on CSFB to GERAN with CCO without
NACC by executing the CHG-GERAN-INTWO command for Normal type
based on UE measurement and Blind type without UE measurement. The
lower number priority has the higher priority.
Blind CCO should be configured by executing the CHG-GERAN-BLCCO
command.
Key Parameters
N_EQUIP: Invalid.
EQUIP: Valid.
GERAN_ARFCN1~GERAN_ This parameter is the Absolute Radio Frequency Channel Number (ARFCN) of
ARFCN31 GERAN FA object.
procedure.
BLIND_CCOSUPPORT This parameter indicates whether to support blind Cell Change Order(CCO)
TARGET_GERAN_NBR_IDX This parameter is the target GERAN neighbor cell index where the blind CCO
will be performed for the relevant cell.
Counters and KPIs

CSFB_CCO_GERAN_OUT CSFBGeranCcoAtt CSFB with inter-RAT GERAN CCO attempt count
CSFBGeranCcoPr CSFB with inter-RAT GERAN CCO preparation success
epSucc count
CSFBGeranCcoSu CSFB with inter-RAT GERAN CCO execution success
cc count
REFERENCE
[4] 3GPP TS23.272 Circuit Switched Fallback in Evolved Packet System; Stage
LTE-SW1312, CSFB to GERAN with CCO with

NACC
INTRODUCTION
introduction of Voice over LTE (VoLTE), it switches UE over to CS domain when
LTE user sends or receives a voice call to let the user receives a voice service from
the CS domain.
The CSFB to GERAN with Cell Change Order (CCO) with Network Assisted Cell
Change (NACC) function switches UE to GERAN with CCO with NACC
procedure.
provides the cell change order to UE, specifies the carrier frequency and target cell
of the GERAN to which UE is to switch over, and delivers the system information
(SI) list of the target cell (CCO with NACC). The UE switches over to the target
cell of GERAN specified by eNB and initiates the voice call sending/receiving
procedure.
The RAN information management (RIM) interworking between eNB and
GERAN is required to process the CSFB to GERAN with CCO with NACC. The
eNB obtains and stores SI lists of each cell from an adjacent GERAN through the
RIM procedure. In addition, eNB use the SI lists of each cell when processing the
CSFB to GERAN with CCO with NACC.
BENEFIT
network (GERAN).
network (GERAN).

Dependency
GERAN supported Device, EPC, and GERAN shall support this feature.
RIM for SI tunneling shall be supported by EPC and GERAN.
Limitation
RIM based SI tunneling is only possible for ENB to acquire GERAN system
information (Manual configuration in LSM is not available).
FEATURE DESCRIPTION
domain. Also, it is used for the delivery of both mobile originating and terminating
SMS.
Cell Change Order with NACC could be performed under the following
conditions:
System Information of the target cell is provided (with NACC).
The following figure shows the call flow for CSFB to GERAN with CCO with
NACC:
System information of the target cell shall be obtained by RIM procedure.
1) The UE initiates CSFB procedure. If UE is in idle state, UE using the RRC

connection establishment procedure switches over to the connected state.
2) The UE transmits the NAS EXTENDED SERVICE REQEUSTembedded in
RRC UL Information Transfer message.
message
4) The MME transmits the S1AP Initial Context setup Request message in which
the CSFB indicator is included to eNB. In case of UE is in idle state, eNB
processes the AS security activation and default bearer setup procedure.
5) The eNB transmits the S1AP Initial Context Setup Response message to MME.
6) The eNB specifies GERAN carrier frequency and the target GERAN cell to
which UE is to switch over and transmits the Mobility from EUTRA command to
UE including the SI lists of the target GERAN cell.
(The eNB may request measurement of GERAN before step 6. This measurement
will increase total CSFB latency)
13) The UE switches over to GERAN carrier frequency given by eNB and
connects to GERAN. It initiates the GERAN location registration procedure.
14) If the GERAN cannot provide simultaneous CS and PS service, UE requests
15~16) The SGSN processes the bearers suspension procedure by UEs request.
The MME suspends S-GW and PS by the request from SGSN.
17) Then, UE performs CS call setup and continues to provide the CS service
The following figure shows the procedure for UE in idle state:
SYSTEM OPERATION
How to Activate
The operator can put the high priority on CSFB to GERAN with CCO with NACC
by using CHG-GERAN-INTWO command for Normal type based on UE
measurement and Blind type without UE measurement. The lower number priority
has the higher priority.
supported during interworking with GERRAN and Target GERAN cell for Blind
CCO should be configured by executing the CHG-GERAN-BLCCO command.
isAllowedRim parameter should be set as True using CHG-HO-OPT. This
parameter configures the RIM procedure and rimSupport parameter should be set
as True by executing the CHG-NBR-GERAN command.
Key Parameters
N_EQUIP: Invalid.
EQUIP: Valid.
BAND_INDICATOR The band indicator of GERAN FA object.
procedure.
BLIND_CCOSUPPORT This parameter indicates whether to support blind Cell Change Order(CCO)
TARGET_GERAN_NBR_ID This parameter is the target GERAN neighbor cell index where the blind CCO
X will be performed for the relevant cell.- geranRedirecdtion: Redirection without
SI.
GERAN
Counters and KPIs

CSFB_CCO_GERAN_OUT CSFBGeranCcoAtt CSFB with inter-RAT GERAN CCO attempt count
CSFBGeranCcoPre CSFB with inter-RAT GERAN CCO preparation
pSucc success count
CSFBGeranCcoSuc CSFB with inter-RAT GERAN CCO execution success
c count
REFERENCE

LTE-SW1313, CSFB to GERAN with PS

Handover
INTRODUCTION
introduction of Voice over LTE (VoLTE), it switches over UE to CS domain when
there is a voice call (mobile originated or mobile terminated) so that the user
receive a voice service from CS domain. The CSFB to GERAN with PS handover
function switches UE to GERAN by PS handover procedure.
provides GERAN measurement order to UE. When GERAN measurement results
are received from UE, eNB selects the handover target cell and processes the
handover preparation procedure. If GERAN and handover preparation procedures
are successfully completed, eNB instructs UE about handover to GERAN and
delivers the CSFB indicator (PS handover).
The UE performs handover to the target cell of GERAN specified by eNB and
initiates the voice call setup procedure.
BENEFIT
network (GERAN).
Users can do a CS call while staying in E-UTRAN, by transition to legacy CS
network (GERAN).

Dependency
GERAN supported Device, EPC, and GERAN shall support this feature based on
3GPP Rel.8. It needs IOT with commercial UE which support PS Handover
between LTE and GERAN.
FEATURE DESCRIPTION
domain. Also, it is also used for the delivery of both mobile originating and
terminating SMS.
Samsung eNB can use PS handover for CSFB to GERAN under the following
conditions:
Target GERAN shall support PS handover
UE shall support handover to GERAN (FGI#9).
Depending on the configuration and UE capability, Redirection or Cell Change

Order could be used for CSFB
The following figure shows the procedure for CSFB with PS handover to GERAN
for UE in active:
1) The UE initiates CSFB procedure. If UE is in idle state, UE processes the

connection establishment between eNB and RRC procedure to switch over to the
connected state.
2~3) The UE transmits the NAS EXTENDED SERVICE REQEUST and eNB
relays it.
4) The MME transmits the S1 request message in which the CSFB indicator is
included to eNB. In case CSFB of UE is in idle state, eNB processes the AS
security activation and default bearer setup procedure.
5) The eNB transmits the S1 response message to MME.
6) The eNB provides the GERAN measurement order to UE. (if available)
GERAN is processed.
8) The eNB, including the HO command received from the CSFB indicator and
target GERAN frequency, transmits the Mobility from EUTRA Command to UE.
9) The UE switches over to GERAN target cell designated by eNB and performs
the rest of handover procedure
The following figure shows the procedure for CSFB with PS handover to GERAN
in case UE is in idle state:
SYSTEM OPERATION
How to Activate
Information by executing the CHG-GERAN-FA command and the GERAN
Periodic Measurement information for StrongestCell report purpose by using
CHG-GERAN-PRD command.
psHoSupport parameter should be set as True by executing the CHG-NBR-
GERAN command.
Key Parameters
N_EQUIP: Invalid.
EQUIP: Valid.
BAND_INDICATOR The band indicator of the GERAN FA object.
CHG-GERAN-PRD/RTRV-GERAN-PRD
PURPOSE The purpose for using information on the GERAN periodic event report.
StrongestCells: This purpose is used for ICIC.
StrongestCellsForSON: This purpose is used for SON.
ReportCGI: This purpose is used for CGI.
Mlb: This purpose is used for MLB.
ACTIVE_STATE This parameter indicates whether to use the GERAN periodic event report.
Inactive: The GERAN periodic event report is not used.
Active: The GERAN periodic event report is used.
MAX_REPORT_CELL The maximum number of cells to be included in a measurement report due to
the GERAN periodic event report.
REPORT_INTERVAL The interval of a measurement report of UE due to the GERAN periodic event
report.
REPORT_AMOUNT The maximum number of measurement reports of UE due to the GERAN
periodic event report.
GERAN
PS_HO_SUPPORT This parameter indicates whether to support the PS-HO of the given GERAN
neighbor cell.
False: PS-HO is not supported.
True: PS-HO is supported.
Counters and KPIs

CSFB_PSHO_GERAN_OUT CSFBPsHoGeranAtt Attempt count for CSFB with inter-
RAT GRAN PS handover
CSFBPsHoGeranPrepSucc Preparation success count for
CSFB with inter-RAT GRAN PS
handover
CSFBPsHoGeranSucc Count of CSFB with Inter RAT
GERAN PS handover execution
successes
CSFBPsHoGeranPrepFail_CpCcFail Preparation fails due to reset
notification (eNB failure or block
restart) from ECMB or by the ECCB
block during the CSFB PS
CSFBPsHoGeranPrepFail_S1apCuFail Preparation fails due to S1AP
specification cause during the
CSFB PS handover preparation.
CSFBPsHoGeranPrepFail_S1apLinkFail Preparation fails due to S1 SCTP
link failure during the CSFB PS
CSFBPsHoGeranPrepFail_S1apRpTo Preparation fails due to S1AP
relocprep timeout (not received)
during the CSFB PS handover
preparation.
CSFBPsHoGeranPrepFail_S1apSigFail Preparation fails due to receiving
S1AP signaling during the CSFB
PS handover preparation.
CSFBPsHoGeranFail_CpCcTo A call is released due to call control
timeout in the protocol blocks
(MAC, RLC, PDCP, and GTP)
execution.
CSFBPsHoGeranFail_CpCcFail A call is released due to reset
notification (eNB failure or block
restart) from the ECMB or by the
ECCB block during the CSFB PS

handover execution.
CSFBPsHoGeranFail_UpGtpFail A call is released due to a failure in
the GTP block during the CSFB PS
handover execution.
CSFBPsHoGeranFail_UpMacFail A call is released due to a failure in
the MAC block during the CSFB PS
handover execution.
CSFBPsHoGeranFail_UpPdcpFail A call is released due to a failure in
the PDCP block during the CSFB
PS handover execution.
CSFBPsHoGeranFail_UpRlcFail A call is released due to a failure in
the RLC block during the CSFB PS
handover execution.
CSFBPsHoGeranFail_RrcSigFail A call is released due to receiving
an RRC signaling during the CSFB
CSFBPsHoGeranFail_S1apCuFail A call is released due to S1AP
specification cause during the
CSFB PS handover execution.
CSFBPsHoGeranFail_S1apLinkFail A call is released due to the S1
SCTP link failure during the CSFB
CSFBPsHoGeranFail_S1apRoTo A call is released due to an S1AP
relocoverall timeout (not received)
execution.
CSFBPsHoGeranFail_S1aSigFail A call is released due to receiving
S1AP signaling during the CSFB
REFERENCE
LTE-SW2011, Service based Intra-LTE Handover

INTRODUCTION
The UE can use a variety of services such as Voice over LTE, Web or FTP in LTE
network. Because each service has different characteristics, it is necessary to use a
different handover policy for each service. For example, in case of VoLTE in a
multi-carrier environment, it is necessary to enable UE to handover to the carrier
with good coverage. Services with a different QoS use a different QCI. In case of
handover control for each service, eNB applies the handover policy set for each
QCI.
The service based intra-LTE handover function can be used in the multi-carrier
environment. The eNB uses this function only to UE that supports multi-carrier.
BENEFIT
To use a handover policy set for each QCI, a different handover policy can be
applied for a different service.
The mobility quality of VoLTE can be improved.

Dependency
This function can be enabled in the multi-carrier environment.
Limitation
Up to 5 mobility profiles are allowed.
QCI 5 is determined according to the default mobility profile (Mobility Profile 0).
The UE should support multi-carrier.
FEATURE DESCRIPTION
Operation Scenario
The operator sets the parameters as per their requirement for service based intra-
LTE handover.
Provisioning/Parameter Settings for service based Intra-LTE
Appropriate mobility profile is allocated to each QCI. Mobility Profile 0 is the
default configuration, which is allocated to the QCI that does not belong to
Mobility Profiles 1-4. In case of QCI 5, Mobility Profile 0 is allocated instead of
Mobility Profiles 1-4.
The following table shows an example of mobility profile allocation for each QCI:
Mobility Profile # Mobility Profile 0 Mobility Mobility Mobility Mobility
Profile 1 Profile 2 Profile 3 Profile 4
QCIs allocated to Default configuration QCI 1 QCI 2, 3, 4 QCI 7, 8, 9 No allocated
each mobility group (Default value per QCI) QCI
Mobility control related items are set for each mobility profile as follows:
Preferred target carrier frequencies for E-UTRAN (FDD or TDD)
Handover triggering event
Measurement configuration
Blind redirection option
The UE may have multiple QCIs belonging to different mobility profiles. In such
cases, Mobility Profile of UE is determined by the mobility profile associated with
highest priority QCI of that UE. If highest priority QCI is associated with default
mobility profile, then service based handover scheme is disabled for that UE and
existing handover scheme will be applied.
The following table shows an example of Priority Allocation per QCI:
QCI # 0 1 2 3 4 5 6 7 8 9
Priority 9 2 4 3 5 1 6 7 8 9
The mobility profile for UE is determined based on the QCI of a bearer that is used
by UE. Therefore, a different handover policy can be used per QCI.
The operational scenario is as follows:
The following figure is an example of service based intra-LTE handover:
For example, UE A and UE B have QCI 1 and QCI 9 respectively and mobility
profile per QCI is set as shown in below table. That is, Mobility Profile 1 is
allocated to UE A and Mobility Profile 2 is allocated to UE B. In this case, if a
preferred carrier is set to Carrier A for Mobility Profile 1 and Carrier B for
Mobility Profile 2, UE A handovers to Carrier A and UE B handovers to Carrier B
as shown in above figure.
The following table shows an example of Mobility Profile Allocation per QCI that
is Set in UE.
UE A B
QCI 1 9
Mobility Profile Mobility Profile 1 Mobility Profile 2
SYSTEM OPERATION
How to Activate
Configure QCI Mobility Group ID to each QCI value by executing the CHG-QCI-
VAL command. If multiple bearers with different QCIs are configured for the same
UE, then the QCI Mobility Group ID with highest priority QCI will be chosen.
QCI Mobility Group specific handover parameters can be configured by
RTRV/CHG EUTRA-FAQCI, RTRV/CHG-EUTRA-A1CNFQ, RTRV/CHG-
EUTRA-A2CNFQ, RTRV/CHG-EUTRA-A3CNFQ, RTRV/CHG-EUTRA-
A4CNFQ, RTRV/CHG-EUTRA-A5CNFQ. If specific QCI Mobility Group is going
to use event A3 to handover to the specific FA, then use 1) CHG-EUTRA-FAQCI
to set handover type to be A3 and 2) CHG-EUTRA-A3CNFQ to set the active
status of the corresponding cell, handover purpose, qci group index, and FA index.
Key Parameters
RTRV-QCI-VAL/CHG-QCI-VAL (QCI Mobility Group configuration)
QCI This parameter is the QoS Class Identifier (QCI). The range is 0 - 255.The
standard QCI defined in the standard document is 1 - 9. 0 and 10 - 255 can be
used by the operator optionally.
[Related Specifications] 3GPP TS 23.203 [Table 6.1.7] Standardized QoS
characteristics.
STATUS This parameter indicates the whether to use the QoS Class Identifier (QCI).
EQUIP: eNB uses the relevant QCI.
N_EQUIP: eNB does not use the relevant QCI.
PRIORITY This parameter is the priority of the QoS Class Identifier (QCI). The range is 1
to 16, and 1 means the highest priority.
QCI_MOBILITY_GROUP_ID This attribute defines the QCI Mobility Group ID of the QCI.
RTRV-EUTRA-FAQCI/CHG-EUTRA-FAQCI
CELL_NUM The cell number to be changed.
FA_INDEX EUTRA frequency index. Up to 8 FAs can be assigned per cell.
QCI_GROUP_INDEX QCI Group index.
STATUS Whether the EUTRA FA is valid.
N_EQUIP: Invalid.
EQUIP: Valid.
OFFSET_FREQ Frequency offset value applied to offsetFreq in RRC Connection
Reconfiguration.
HANDOVER_TYPE Handover Type per Carrier
ci_HoEventA3
ci_HoEventA4
ci_HoEventA5
RTRV-EUTRA-A1CNFQ/CHG-EUTRA-A1CNFQ
frequency.
LteHo: Used for Gap Activate
LteBlind: Used for Blind HO
IRatHo: Used for IRAT HO
IRatBlind: Used for IRAT Blind HO
Ca: Used for Carrer Aggregation
CaPeriodicMr
Srvcc
Mdt
Spare_2: Reserved.
frequency.
This change will be applied to UE from next RRC signaling procedure (for
updated to the current Active UEs.
PURPOSE This parameter is the purpose of using Event A3 event.
IntraLteHandover: Performs handover.
ReportStrongestCells: Performs the ANR operation.
IntraFrequencyLb
Spare_2: Reserved. Not used at this moment.
FA_INDEX The FA_INDEX is a parameter corresponding to the FA_INDEX of EUTRA-FA.
The configuration conditions of A3 event (A3_OFFSET, TRIGGER_QUANTIY,
and so on.) can be set differently per FA. To configure A3 event for a specific
FA, the status of EUTRA-FA (FA_INDEX#n) must be EQUIP and the
ACTIVE_STATE of EUTRA-A3CNF (FA_INDEX#n) must be Active.
ACTIVE_STATE This parameter is the purpose of using Event A3 event. If this is set to Inactive,
the A3 event is not configured.
A4PurposeUntraLteHandover: handover is executed
A4PurposeANR_Specific:the ANR operation is executed
A4PurposeCA: SCELL is configured
A4PurposeUnloading: the unloading operation is executed
A4PurposeSpare_2: it is not used at this moment because it is reserved for
future use.
The configuration conditions of A4 event (A4_THRESHOLD_RSRP,
TRIGGER_QUANTIY, and so on.) can be set differently per FA. To configure
A4 event for a specific FA, the status of EUTRA-FA (FA_INDEX#n) must be
EQUIP and the ACTIVE_STATE of EUTRA-A4CNF (FA_INDEX#n) must be
Active. The ANR_Specific/CA/Unloading is only used to configure FA_INDEX
#0 and other values are ignored.
IntraLteHandover: Intra-LTE handover.
Spare_1: Reserved.
Spare_2: Reserved.
The configuration conditions of A5 event (A5_THRESHOLD_RSRP1,
TRIGGER_QUANTIY, and so on.) can be set differently per FA. To configure
A5 event for a specific FA, the status of EUTRA-FA (FA_INDEX#n) must be
EQUIP and the ACTIVE_STATE of EUTRA-A5CNF (FA_INDEX#n) must be
Active.
Counters and KPIs

- IntraEnbAtt Intra eNB handover attempt count
IntraEnbPrepSucc Intra eNB handover preparation success count
IntraEnbSucc Intra eNB handover execution success count
IntraEnbPrepFail_CP_C Intra eNB handover preparation fails due to due to
C_TO call control timeout in the protocol blocks (MAC,
RLC, PDCP, GTP)
IntraEnbPrepFail_CP_C Intra eNB handover preparation fails due to reset
C_FAIL notification (eNB failure or block restart) from
ECMB or by the ECCB block
IntraEnbPrepFail_UP_M Intra eNB handover preparation fails due to the
AC_FAIL failure in the MAC block
IntraEnbPrepFail_UP_R Intra eNB handover preparation fails due to the
LC_FAIL failure in the RLC block
IntraEnbPrepFail_RRC_ Intra eNB handover preparation fails due to
SIG_FAIL receiving RRC signaling
IntraEnbPrepFail_CP_B Intra eNB handover preparation fails due to
H_CAC_FAIL Backhaul QoS based CAC
IntraEnbPrepFail_CP_C Intra eNB handover preparation fails due to
APA_CAC_FAIL Capacity based CAC
IntraEnbPrepFail_CP_Q Intra eNB handover preparation fails due to Air QoS
OS_CAC_FAIL based CAC
IntraEnbPrepFail_S1AP Intra eNB handover preparation fails due to the
_CU_FAIL S1AP specification cause
IntraEnbPrepFail_S1AP Intra eNB handover preparation fails due to the S1
_LINK_FAIL SCTP link failure
IntraEnbPrepFail_S1AP Intra eNB handover preparation fails due to
_SIG_FAIL receiving S1AP signaling
IntraEnbFail_CP_CC_T Intra eNB handover fails due to call control timeout
O in the protocol blocks (MAC, RLC, PDCP, GTP)
IntraEnbFail_CP_CC_F Intra eNB handover fails due to reset notification
AIL (eNB failure or block restart) from ECMB or by the
ECCB block

IntraEnbFail_UP_GTP_ Intra eNB handover fails due to the failure in the
FAIL GTP block
IntraEnbFail_UP_MAC_ Intra eNB handover fails due to the failure in the
FAIL MAC block
IntraEnbFail_UP_RLC_ Intra eNB handover fails due to the failure in the
FAIL RLC block
IntraEnbFail_RRC_HC_ Intra eNB handover fails due to HO preparation
TO timeout (not received HO command)
IntraEnbFail_RRC_SIG_ Intra eNB handover fails due to receiving RRC
FAIL signaling
IntraEnbFail_S1AP_CU Intra eNB handover fails due to the S1AP
_FAIL specification cause
IntraEnbFail_S1AP_LIN Intra eNB handover fails due to the S1 SCTP link
K_FAIL failure
IntraEnbFail_S1AP_SIG Intra eNB handover fails due to receiving S1AP
_FAIL signaling
IntraHOTime Time taken from transmitting the
RRCConnectionReconfiguration message to UE
until after receiving the
RRCConnectionReconfiguration Complete
message from the UE.
IntraHOTimeMax Average maximum intra HO interrupt time
IntraHOTimeTot Sum of intra HO interrupt time
IntraHOTimeCnt Count of IntraHOTime collected
REFERENCE
N/A
LTE-SW2014, SPID based Dedicated Priority

INTRODUCTION
The eNB supports dedicated signaling with Inter-Frequency/RAT cell reselection
or handover priorities based on SPID (Subscriber Profile ID).
Specification based SPID support
Operator specific SPID support
BENEFIT
The operator can control idle mode camping RAT and carriers of UE based on
absolute priorities determined by subscription information.
The operator can control service frequency of UE based on absolute priorities
determined by subscription information.

Dependency
The operator specific values are required.
Limitation
The reference values, SPID=1~128, 254, 255 and 256 can be supported.
FEATURE DESCRIPTION
The SPID information is received from MME (Initial Context Setup Request/UE
Context Modification/Downlink NAS Transport) or other eNB (Handover Setup
Request).
The eNB support to Inter-frequency handover or reselection priority based on
dedicated priority each SPID.
SPID based Inter-frequency Handover

When eNB receives UE's SPID, it checks whether SPID is set by the operator. If
SPID is set, then eNB performs Inter-frequency handover for the highest
prioritized frequency in the dedicated priority list.
Related Operation
When eNB receives UE's SPID, it selects frequencies should be UseFlag is set to
use.
The eNB performs measurement (A4, A5) using RRCConnectionReconfiguration

procedure for the highest prioritized frequencies among selected frequencies.
The eNB sets Measurement Gap, which leads to search for Inter-frequency cell.
When eNB receives MR by A4 (Neighbour cell signal strength only) or A5, it
performs inter-frequency handover toward the searched frequency.
SPID based Inter-RAT Handover

When eNB receives UE's SPID, it checks whether SPID is set by the operator. If
the SPID is set and the highest prioritized frequency is Inter-RAT frequency, then
eNB performs Inter-RAT handover to the chosen frequency.
Related Operation
When eNB receives UE's SPID, it selects frequencies should be UseFlag is set to
use.
If the highest prioritized frequency is Inter-RAT frequency, eNB performs
measurement (B1, B2) using RRCConnectionReconfiguration procedure on
the highest prioritized inter-RAT frequency.
The eNB sets Measurement Gap, which leads to search for Inter-frequency cell.
When eNB receives MR by B1 or B2, it performs inter-frequency handover
toward the searched frequency.
If the frequencies of multiple RATs have the same highest priority, one target
RAT is chosen according to the fixed order of LTE > UTRAN > GERAN.
SPID based Reselection Priority

During RRC Connection Release occurrence, SPID setup of corresponding UE is
verified by eNB. If the setup is complete, the corresponding dedicated priority list
is transferred to UE by eNB.
Related Operation
When configuring RRC Connection Release to MS, verify if SPID (1~128, 254,
255, and 256) of MS is set.
Allow configuration of IdleModeMobilityControlInfo only for SPID set to MS
with UseFlag on. At this point, only include RAT supported according to UE
Radio Capability of MS in order to exclude non-supported RAT information.
If UseFlag is off for the SPID set for UE, configure
IdleModeMobilityControlInfo according to Idle mode Load Balancing feature.
Transmit the configured RRC Connection Release message to MS.
Specification
SPID Range
Values 1~128: Operator specific SPID values.
Values 129~256: Reference values
Reference SPID Values

The following table shows eNB local configuration in idle and connected mode for
SPID = 256:
Configuration Parameter Value Description
E-UTRAN Carriers Priority High The selection priorities for idle and connected mode of all
E-UTRAN carriers are higher than the priorities for all
UTRAN and GERAN carriers
UTRAN Carriers Priority Medium The selection priorities for idle and connected mode of all
UTRAN carriers are lower than the priorities for all E-
UTRAN carriers and higher than the priorities for all
GERAN carriers
GERAN Carriers Priority Low The selection priorities for idle and connected mode of all
GERAN carriers are lower than the priorities for all E-
UTRAN and UTRAN carriers
SPID = 255:
UTRAN Carriers Priority High The selection priorities for idle and connected mode of all
UTRAN carriers are higher than the priorities for all
GERAN and E-UTRAN carriers
GERAN Carriers Priority Medium The selection priorities for idle and connected mode of all
GERAN carriers are lower than the priorities for all UTRAN
carriers and higher than the priorities for all E-UTRAN
carriers
E-UTRAN Carriers Priority Low The selection priorities for idle and connected mode of all
E-UTRAN carriers are lower than the priorities for all
UTRAN and GERAN carriers
SPID = 254:
GERAN Carriers Priority High The selection priorities for idle and connected mode of all
GERAN carriers are higher than the priorities for all
UTRAN and E-UTRAN carriers
UTRAN Carriers Priority Medium The selection priorities for idle and connected mode of all
UTRAN carriers are lower than the priorities for all GERAN
carriers and higher than the priorities for all E-UTRAN
carriers
E-UTRAN Carriers Priority Low The selection priorities for idle and connected mode of all
E-UTRAN carriers are lower than the priorities for all
GERAN and UTRAN carriers
SYSTEM OPERATION
How to Activate
Set dedicated priority of the FA to the specific SPID by using the RTRV/CHG-
EUTRA-PRIOR command for EUTRAN FA,the RTRV/CHG-UTRA-PRIOR
command for UTRAN FA, and the RTRV/CHG-GERAN-PRIOR command
for GERAN FA.
If operator needs to create a UE with specific SPID to intra-LTE handover to FA
with the highest dedicate priority using A4 or A5 measurement event,
aSet spidMobilityOption of the specific Cell/PLMN/FA/SPID with the highest
dedicatedPriority value to 'handoverOnly' or 'both' by executing the CHG-
EUTRA-PRIOR command.
bSet spidMeasureOption of the corresponding Cell/PLMN/FA/SPID to
'hoEventA4' or 'hoEventA5' by executing the CHG-EUTRA-PRIOR
command.
cSet activeState of the A4 or A5 event for the corresponding Cell/FA to be
active using CHG-EUTRA-A4CNF command or CHG-EUTRA-A5CNF
command with index A4purposeInterFrequencySPID or
A5purposeInterFrequencySPID (if service based handover feature is
applied, EUTRA-A4CNFQ or EUTRA-A5CNFQ with the relevant QCI
Mobility Group ID has to be considered also.).
If operator needs to create a UE with specific SPID to inter-RAT handover to FA
with the highest dedicate priority using B1 or B2 measurement event,
aSet spidMobilityOption of the specific Cell/PLMN/FA/SPID with the highest
dedicatedPriority value to 'handoverOnly' or by executing the using CHG-
UTRA-PRIOR or CHG-GERAN-PRIOR command.
bSet spidMeasureOption of the corresponding Cell/PLMN/FA/SPID to
'hoEventB1' or 'hoEventB2' by executing the CHG-UTRA-PRIOR or
CHG-GERAN-PRIOR command.
cSet activeState of the B1 or B2 event for the corresponding Cell/FA to be
active using CHG-UTRA-B1CNF/CHG-UTRA-B2CNF or CHG-
GERAN-B1CNF/CHG-GERAN-B2CNF (if the service specific handover
feature is applied, UTRA-B1CNFQ/UTRA-B2CNFQ or GERAN-
B1CNFQ/GERAN-B2CNFQ with the relevant QCI Mobility Group ID has
to be considered also.).
Key Parameters
RTRV-EUTRA-PRIOR/CHG-EUTRA-PRIOR
PLMN_ID PLMN index. It is mapping to MCC/MNC configured in plmnIdx of
PLDEnbPlmnInfo.
FA_ID This parameter is the Evolved Universal Terrestrial Radio Access (EUTRA)
frequency index. This parameter enters the FA value that each cell supports
and it is mapped to the FA_INDEX parameter value in the RTRV-EUTRA-FA
command.
SPID_INDEX This parameter is the Subscriber Profile ID (SPID). This parameter is the index
used to refer to the registration information of a subscriber.
SPID This parameter is the Subscriber Profile ID (SPID) for Radio Access Terminal
(RAT)/frequency priority value. The range of an entered value is 1 - 128 and a
value between 129 and 253 cannot be entered.
USED_FLAG This parameter shows whether the dedicated priority is used.
no_use: Dedicated priority is not used.
use: Dedicated priority is used.
DEDICATED_PRIORITY This parameter is the dedicated priority value. Enter a dedicated priority value
according to the FA_INDEX and SPID.
SPID_MOBILITY_OPTION Define addtional operations based on the mobility setting of the parameter for
SPID of the UE.
reselectionOnly(0): When UE is released, send the dedicated priority per FA
for SPID that the UE currently possesses among the FAs supported in UE
Radio Capability through IdleModeMobilityControlInfo. However, A4 or A5
based inter-frequency handover based on SPID shall not be performed.
handoverOnly(1): When the UE first receives SPID, if the FA configured to be
the highest DEDICATED_PRIORITY for the SPID is different from the
serving frequency of the UE but can be supported in UE Radio Capabiilty,
attach A4 or A5 event to induce inter-frequency handover.
In this case, idleModeMobilityControlInfo to be transmitted when UE is

released shall be based on Idle Mode Load Balancing.
both(2): When UE first receives SPID, if the FA configured to be the highest
DEDICATED_PRIORITY for the SPID is different from the serving frequency
of the UE but can be supported in UE Radio Capability, attach A4 or A5
event to induce inter-frequency handover. In addition, when UE is released,
the dedicated priority per FA configured in SPID that UE currently possesses
among the FAs that can be supported in UE Radio Capability shall be
transitted through IdleModeMobilityControlInfo.
SPID_MEASURE_OPTION If spidMobilityOption is handoverOnly or both, designate measurement event
type to trigger inter-frequency handover.
spidHoEventA4(0): measurement event type for inter-frequency handover
triggering is EventA4.
spidHoEventA5(1): measurement event type for inter-frequency handover
triggering is EventA5.
RTRV-UTRA-PRIOR/CHG-UTRA-PRIOR
CELL_NUM This parameter specifies the cell number to retrieve the periodic report config
information used for interoperating with the UTRAN.
PLMN_INDEX PLMN index. It is mapping to MCC/MNC configured in plmnIdx of
PLDEnbPlmnInfo.
FA_ID This parameter is the Universal Terrestrial Radio Access (UTRA) frequency
index. The operator can enter a FA value each cell supports and maximum 6
FAs can be entered. This parameter is mapped to the FA_INDEX parameter
value included in the RTRV-UTRA-FA command.
SPID_INDEX This parameter is the Subscriber Profile ID (SPID) index. This parameter is the
index used to refer to the registration information of a subscriber.
SPID Subscriber Profile ID for RAT/Frequency priority. SPID could not be setting
129~253.
USED_FLAG Whether to use dedicatedPriority.
CI_no_use: dedicatedPriority is not used.
CI_use: dedicatedPriority is used.
DEDICATED_PRIORITY Dedicated Priority Value for Frequency according SPID.
According to 3GPP TS36.300, if spid is 255, dedicated priority is set to 7.
SPID_MOBILITY_OPTION Define additional operations based on the mobility setting of the parameter for
SPID of the UE.
Radio Capability through IdleModeMobilityControlInfo. However, B1 or B2
based inter-RAT handover to UTRAN based on SPID shall not be performed.
handoverOnly(1): When UE first receives SPID, if the FA configured to be the
highest DEDICATED_PRIORITY for the SPID is different from the serving
frequency of UE but can be supported in UE Radio Capability, attach B1 or
B2 event to induce inter-RAT handover to UTRAN.
In this case, idleModeMobilityControlInfo to be transmitted when UE is

of the UE but can be supported in UE Radio Capability, attach B1 or B2
event to induce inter-RAT handover to UTRAN. In addition, when UE is
released, the dedicated priority per FA configured in SPID that UE currently
possesses among the FAs that can be supported in UE Radio Capability
shall be transmitted through IdleModeMobilityControlInfo.
SPID_MEASURE_OPTION_ If spidMobilityOption is handoverOnly or both, designate measurement event
INTER_RAT type to trigger inter-RAT handover to UTRAN.
spidHoEventB1(0):measurement event type for inter-RAT handover to
UTRAN triggering is EventB1.
spidHoEventB2(1):measurement event type for inter-RAT handover to
UTRAN triggering is EventB2.
RTRV-GERAN-PRIOR/CHG-GERAN-PRIOR
CELL_NUM The cell number to be changed.
PLMN_INDEX PLMN index. It is mapping to MCC/MNC configured in plmnIdx of
PLDEnbPlmnInfo.
FA_INDEX GERAN frequency index. Up to 6 FAs can be assigned per cell. It is mapping
to PLDGeranFaPriorInfo.
SPID_INDEX SPID index.
SPID Subscriber Profile ID for RAT/Frequency priority. SPID could not be setting
129~253.
USED_FLAG Whether to use dedicatedPriority.
CI_no_use: dedicatedPriority is not used.
CI_use: dedicatedPriority is used.
DEDICATED_PRIORITY Dedicated Priority Value for Frequency according SPID.
According to 3GPP TS36.300, if spid is 254, dedicated priority is set to 7.
SPID_MOBILITY_OPTION Define additional operations based on the mobility setting of the parameter for
SPID of the UE.
Radio Capability through IdleModeMobilityControlInfo. However, B1 or B2
based inter-RAT handover to GERAN based on SPID shall not be
performed.
handoverOnly(1): When the UE first receives SPID, if the FA configured to be
the highest DEDICATED_PRIORITY for the SPID is different from the
serving frequency of the UE but can be supported in UE Radio Capability,
attach B1 or B2 event to induce inter-RAT handover to GERAN.
In this case, idleModeMobilityControlInfo to be transmitted when the UE is

of the UE but can be supported in UE Radio Capability, attach B1 or B2
event to induce inter-RAT handover to GERAN. In addition, when UE is
released, the dedicated priority per FA configured in SPID that UE currently
possesses among the FAs that can be supported in UE Radio Capability
shall be transitted through IdleModeMobilityControlInfo.
SPID_MEASURE_OPTION_ If spidMobilityOption is handoverOnly or both, designate measurement event
INTER_RAT type to trigger inter-RAT handover to GERAN.
spidHoEventB1(0): measurement event type for inter-RAT handover to
GERAN triggering is EventB1.
spidHoEventB2(1): measurement event type for inter-RAT handover to
GERAN triggering is EventB2.
RTRV-EUTRA-A4CNF/CHG-EUTRA-A4CNF OR RTRV-EUTRA-
A4CNFQ/CHG-EUTRA-A4CNFQ
PURPOSE This parameter is the purpose of using Event A4.
IntraLteHandover: handover is executed
ANR_Specific: the ANR operation is executed
CA: SCELL is configured
Sendback: the Sendback operation is executed
InterFrequencyLb: the Active Load Balancing operation is executed
ArpHandover: Enable inter frequency handover function for UEs that have a
specific ARP
InterFrequencySPID: inter-frequency handover is executed for specific SPID
with handover mobility option.
ACTIVE_STATE This parameter is the purpose of using Event A4. If this is set to Inactive, the
Event A4 is not configured.
RTRV-EUTRA-A5CNF/CHG-EUTRA-A5CNF OR RTRV-EUTRA-
A5CNFQ/CHG-EUTRA-A5CNFQ
PURPOSE This parameter is the purpose of using Event A5.
IntraLteHandover: Used for Intra LTE Handover.
CaInterFreq: Performs Inter frequency handover for Carrier Aggregation(CA)
UE
InterFrequencyMbms: Inter frequency handover to get MBMS service
ArpHandover: Enable Inter frequency handover function for UEs that have a
specific ARP
InterFrequencySPID: Inter frequency handover for the specific SPID with
handover mobility option
ACTIVE_STATE This parameter is the purpose of using Event A5. If this is set to Inactive, the
Event A5 is not configured.
RTRV-UTRA-B1CNF/CHG-UTRA-B1CNF or RTRV-UTRA-B1CNFQ/CHG-
UTRA-B1CNFQ
PURPOSE This parameter specifies the use of the UTRAN Event B1 used for
interoperating with the UTRAN.
InterRatHandover: Used for handover to the UTRAN. (0)
ANR_Specific: Used for the ANR operation with the UTRAN. (1)
Srvcc: Used for the Srvcc with the UTRAN. (2)
Mlb: Used for MLB. (3)
handover mobility option. (4)
ACTIVE_STATE This parameter is the purpose of using Event B1. If this is set to Inactive, the
Event B1 is not configured.
RTRV-UTRA-B2CNF/CHG-EUTRA-B2CNF or RTRV-EUTRA-B2CNFQ/CHG-
EUTRA-B2CNFQ
PURPOSE This parameter is the purpose to retrieve the B2 report configuration
information used for interoperating with the UTRAN.
InterRatHandover: Used for handover to the UTRAN. (0)
Srvcc: Used for SRVCC. (1)
RTRV-GERAN-B1CNF/CHG-GERAN-B1CNF or RTRV-GERAN-
B1CNFQ/CHG-GERAN-B1CNFQ
PURPOSE This parameter is the usage of information on the GERAN Event B1 report. It is
used for inter-RAT Handover and SON ANR function.
InterRatHandover: Used for InterRAT Handover (0)
ANR_Specific: Used for SON ANR (1)
Srvcc: Used for SRVCC (2)
Mlb: For MLB. (3)
RTRV-GERAN-B2CNF/CHG-GERAN-B2CNF or RTRV-GERAN-
B2CNFQ/CHG-GERAN-B2CNFQ
PURPOSE This parameter is the usage of the GERAN Event B2 report. It is used for inter-
RAT Handover.(0)
InterRatHandover: For Inter-RAT handover.(0)
Srvcc: For SRVCC. (1)
Counters and KPIs

REFERENCE
Chapter 5 Radio Scheduler
LTE-ME1101, PDSCH Resource Allocation

INTRODUCTION
In SC-FDMA or OFDM system, the frequency-domain resource allocation
information needs to be signaled to UE. Because the large number of resource
blocks within the frequency band, the resource allocation is one of the largest
fields in the downlink control information. In the case of SC-FDMA uplink, the
allocated resource blocks need to be contiguous to guarantee single-carrier
property. While the contiguous resource allocation can be signaled with the
minimum of signaling bits, it also results in limiting the scheduling flexibility. In
the case of OFDM, non-contiguous resource blocks can be allocated thus
providing maximum scheduling flexibility. However, the signaling overhead also
increases for non-contiguous resource block allocation. To provide various choices
of scheduling performance and signaling overhead, multiple resource allocation
types are defined. A contiguous resource allocation scheme is defined for both and
the uplink and the downlink. As pointed out earlier, a contiguous resource
allocation is necessary in the uplink due to single-carrier access. In downlink,
contiguous resource allocation provides a low overhead alternative while limiting
scheduling flexibility, In addition to contiguous resource allocation, two types of
non-contiguous resource allocation using a bitmap-based signaling are defined for
the downlink.
BENEFIT
This feature enables to enhance flexibility in spreading the resources across the
frequency domain to exploit frequency diversity.

Limitation
Type 1 resource block allocations are not applicable to the 1.4 MHz channel
bandwidth.
DCI formats 1, 2, and 2A always signal a type 0 resource block allocation when
the channel bandwidth is 1.4 MHz.
FEATURE DESCRIPTION
3GPP LTE defines three downlink resource allocation types as follows:
Downlink Resource Allocation Type 0

A type 0 downlink resource block allocation can be signaled from eNB to UE
using Downlink Control Information (DCI) format 1, 2, and 2A.
An allocation received during downlink subframe n defined the allocated
Resource Blocks within the same downlink subframe.
A type 0 Resource Block allocation uses a bitmap to indicate which Resource
Block Groups (RBGs) are allocated to UE. A single RBG is a set of
consecutive Resource Blocks. The allocated RBG do not need to be
contiguous.
The number of Resource Blocks within an RBG is predetermined and is a
function of the channel bandwidth.
The following table shows the RBG size as a function of the channel bandwidth:
Parameters Channel Bandwidth
1.4 MHz 3 MHz 5 MHz 10 MHz 15 MHz 20 MHz
Total Number of Resource Blocks 6 15 25 50 75 100
RBG Size (RB) 1 2 2 3 4 4
Number of complete RBG 6 7 12 16 18 25
Size of remaining RBG - 1 1 2 3 -
Total Number of RBG 6 8 13 17 19 25
Size of bitmap (bits) 6 8 13 17 19 25
Each channel bandwidth includes a number of complete RBG. A partial RBG is

also included if the total number of Resource Block is not a multiple of the
RBG size.
The bitmap signaled using the Type 0 Resource Block allocation includes a
single bit for each RBG. A value of 1 indicates that the RBG has been
allocated to the UE.
The following figure shows the RBG for channel bandwidth of 5MHz:

A type 1 downlink Resource Block allocation can be signaled from eNB to UE
using DCI format 1, 2, and 2A. An allocation received during downlink
subframe n defined the allocated Resource Blocks within the same downlink
subframe.
Type 1 resource block allocations are not applicable to the 1.4 MHz channel
bandwidth.
Type 1 resource block allocations are divided into 3 sections: RBG subset
number, Resource Block offset flag, and Resource Block bitmap.
The RBG sizes are the same as those specified for a Type 0 Resource Block
allocation. The number of RBG subsets is equal to the RBG size.
The following table shows the RBG size and number of RBG subsets for each
channel bandwidth:
Parameters Channel Bandwidth
Total Number of Resource Blocks N/A 15 25 50 75 100
RBG Size (RB) N/A 2 2 3 4 4
Number of RBG subsets N/A 2 2 3 4 4
RBG subset (bits) N/A 1 1 2 2 2
Offset flag (bits) N/A 1 1 1 1 1
bitmap (bits) N/A 6 11 14 16 22
Total Bits N/A 8 13 17 19 25
The number of bits used to signal the RBG subset is either 1 or 2 depending on
the number of subsets. The resource blocks allocated to UE always belong to a
single RBG subset.
The resource block offset flag indicates whether the subsequent Resource Block
bitmap should be aligned with the bottom of the lowest Resource Block within
the subset, or aligned with the top of the highest Resource Block within the
subset. This offset is necessary because the bit map is not sufficiently large to
include all Resource Blocks within the subset.

A type 2 downlink resource block allocation can be signaled from eNB to UE
using DCI format 1A.
An allocation received during downlink subframe n defined the allocated
resource blocks within the same downlink subframe.
The set of allocated virtual resource blocks are mapped onto the set of allocated
physical resource blocks.
Contiguous virtual resource blocks are contiguous both before and after mapping
onto their physical resource blocks. In this case, the set of allocated physical
resource blocks is the same as the set of allocated virtual resource blocks. In
addition, the resource block allocation is the same in both time slots belonging
to the subframe.
Contiguous allocations can range from a single virtual resource block to the
complete set of virtual resource blocks spanning the entire channel bandwidth.
Contiguous virtual resource block allocation is signaled using Resource
Indication Values (RIV). The calculation of the RIV is same as when
calculating the RIV for type 0 uplink resource allocations.
SYSTEM OPERATION
How to Activate
The PDSCH resource allocation type is automatically determined by Samsung
scheduler based on the DCI format and the traffic type and cannot be directly
controlled by the operator.
Key Parameters
Counters and KPIs

REFERENCE
[1] Telefonica, Req20, The Vendors LTE solution shall support functionality to
enquire UE capability and record number of UEs per eNodeB and per cell for each
UE category, Telefonica RFP (12.04)
LTE-ME3203, Aperiodic CQI Reporting

INTRODUCTION
For the downlink data transmissions in an LTE network, the eNodeB typically
selects the modulation scheme and code rate depending on a prediction of the
downlink channel conditions. An important input to this selection process is the
Channel Quality Indicator (CQI) feedback transmitted by the UE in the uplink.
CQI feedback is an indication of the data rate, which can be supported by the
channel, considering the Signal to Interference plus Noise Ratio (SINR) and the
characteristics of the UE receiver.
The eNB supports two types of CQI reporting:
Periodic CQI is semi-statically configured by the eNB to be periodically
transmitted on PUCCH.
Aperiodic CQI can be triggered on the PUSCH by a CSI request within DCI
format 0 on PDCCH. It can also be triggered within random access response
grant belonging to a random access response message on the PDSCH.
BENEFIT
DL frequency selective scheduling to use sub-band CQI of all subbands.
DL radio resource scheduling to serve the best resource allocation.

N/A
FEATURE DESCRIPTION
The aperiodic CQI is sent by PUSCH and be triggered by the CQI request field
within UL grant. The eNB configures the following types of CQI reporting
through the RRC signaling:
Wideband reporting
UE-selected sub-band reporting
Higher layer configured sub-band reporting
In UE-selected sub-band reporting, the UE reports average CQI of M number of
preferred sub-band in addition to wideband CQI. While it reports wideband CQI
and sub-band CQI of all subbands in higher layer configured sub-band reporting.
Because higher layer configured CQI reporting provides more information than
UE-selected sub-band reporting, the Samsung eNB only operates higher layer
configured CQI reporting.
The eNB uses aperiodic CQI for frequency selective scheduling because sub-band
information of periodic sub-band CQI is limited, as follows:
The UE reports only the selected sub-band CQI in bandwidth part.
The UE does not transmit sub-band CQIs for the entire bandwidth simultaneously,
which leads to longer reporting time.
The eNB also uses aperiodic CQI in DL Carrier Aggregation. When the Carrier
Aggregation feature is enabled, the use of two bits for CSI request is applicable.
According to CSI request field, aperiodic CQI reporting is triggered for Pcell or
Scell.
SYSTEM OPERATION
How to Activate
Execute CHG-CQI-REP to set CQI_REPORT_APERIODIC_SETUP to
ci_Config_Setup for enabling aperiodic CQI report when DL Frequency
Selective Scheduling (FSS) is enabled.
Execute CHG-CQI-REP to set CQI_REPORT_APERIODIC_SETUP_R10 to
ci_Config_PcellScellSetup for enabling aperiodic CQI report when Carrier
Aggregation feature is enabled.
Key Parameters
RTRV-CQI-REP/CHG-CQI-REP
CQI_REPORT_APERIODIC_SETUP This parameter is set to enable or disable the use of aperiodic
report mode.
Release: Aperiodic report mode is disabled.
Setup: Aperiodic report mode is enabled.
CQI_REPORT_APERIODIC_SETUP_R10 Config aperiodic report mode for Rel 10.
0: ci_Config_ReleaseAll
1: ci_Config_PcellSetup
2: ci_Config_ScellSetup
3: ci_Config_PcellScellSetup
Counters and KPIs

REFERENCE
LTE-ME3206, Periodic Channel Status

Reporting
INTRODUCTION
The principle of link adaptation is fundamental to the design of a radio interface,
which is efficient for packet-switched data traffic. Unlike the early versions of
Universal Mobile Telecommunication System (UMTS), which is used fast closed-
loop power control to support circuit-switched services with a roughly constant
data rate, link adaptation in High Speed Packet Access (HSPA) and LTE adjusts
the transmitted information data rate (modulation scheme and channel coding rate)
dynamically to match the prevailing radio channel capacity for each user.
In case of downlink data transmissions in LTE, eNB typically selects the
modulation scheme and code rate depending on a prediction of downlink channel
conditions. An important input to this selection process is the Channel Quality
Indicator (CQI) feedback transmitted by UE in uplink. The CQI feedback is an
indication of the data rate, which can be supported by the channel, taking into
account the Signal to Interference plus Noise Ratio (SINR) and the characteristics
of UEs receiver.
In case of LTE uplink transmissions, the link adaptation process is similar to that
for the downlink, with the selection of modulation and coding schemes also being
under the control of eNB. An identical channel coding structure is used for uplink,
while the modulation scheme may be selected between QPSK and 16QAM, and,
for the highest category of UE, also 64QAM. The main difference from the
downlink is that instead of basing the link adaptation on CQI feedback, eNB can
directly make its own estimate of the supportable uplink data rate by channel
sounding, for example using the Sounding Reference Signals (SRSs). A final
important aspect of link adaptation is its use in conjunction with multi-user
scheduling in time and frequency, which enables the radio transmission resources
to be shared efficiently between users as the channel capacity to individual users
varies. The CQI can therefore be used not only to adapt the modulation and coding
rate to the channel conditions, but also for the optimization of the time/frequency
selective scheduling and for inter-cell interference management.
BENEFIT
Enable link adaptation from facilitating this feature
Enable downlink radio resource scheduling to serve the best resource allocation

Dependency
This feature can be enabled in case of uplink 64.
FEATURE DESCRIPTION
In cellular communication systems, the quality of signal received by UE depends
on channel quality from serving cell, level of interference from other cells, and
noise level. To optimize system capacity and coverage for a given transmission
power, the transmitter should try to match the information data rate for each user
to the variations in received signal quality. This is commonly referred to as link
adaptation and is typically based on Adaptive Modulation and Coding (AMC).
The degrees of freedom for the AMC consist of the modulation and coding
schemes:
Modulation Scheme
Low-order modulation (that is, few data bits per modulated symbol, for
example, QPSK) is more robust and can tolerate higher levels of interference
but provides a lower transmission bit rate. High-order modulation (that is,
more bits per modulated symbol, for example, 64QAM) offers a higher bit rate
but is more prone to errors due to its higher sensitivity to interference, noise
and channel estimation errors; it is therefore useful only when the SINR is
sufficiently high.
Code rate
In case of given modulation, the code rate can be chosen depending on the
radio link conditions: a lower code rate can be used in poor channel conditions
and a higher code rate in the case of high SINR. The adaptation of the code
rate is achieved by applying puncturing or repetition to the output of a mother
code.
A key issue in the design of AMC scheme for LTE was whether all Resource
Blocks (RBs) allocated to one user in a subframe should use the same Modulation
and Coding Scheme (MCS) or whether the MCS should be frequency dependent
within each subframe. It was shown that in general only a small throughput
improvement arises from a frequency-dependent MCS compared to RB-common
MCS in the absence of transmission power control, and therefore the additional
control signalling overhead associated with frequency-dependent MCS is not
justified. Therefore in LTE the modulation and channel coding rates are constant
over the allocated frequency resources for a given user, and time-domain channel-
dependent scheduling and AMC is supported instead. In addition, when multiple
transport blocks are transmitted to one user in a given subframe using multistream
Multiple-Input Multiple-Output (MIMO), each transport block can use an
independent MCS.
In LTE, UE can be configured to report CQIs to support eNB in selecting an

appropriate MCS to use for downlink transmissions. The CQI reports are derived
from downlink received signal quality, typically based on measurements of the
downlink reference signals. It is important to note that, like HSDPA, the reported
CQI is not a direct indication of SINR in LTE. Instead, UE reports the highest
MCS that it can decode with a transport block error rate probability not exceeding
10%. Thus, the information received by eNB takes into account the characteristics
of UEs receiver, and not just the prevailing radio channel quality. Hence, UE that
is designed with advanced signal processing algorithms (for example, using
interference cancellation techniques) can report a higher channel quality and,
depending on the characteristics of the eNBs scheduler, can receive a higher data
rate.
The following table shows the list of modulation schemes and code rates which
can be signalled by means of a CQI value:
The AMC can exploit UE feedback by assuming that the channel fading is
sufficiently slow. This requires the channel coherence time to be at least as long as
the time between UEs measurement of the downlink reference signals and
subframe containing correspondingly-adapted downlink transmission on the
Physical Downlink Shared CHannel (PDSCH). However, a trade-off exists
between the amount of CQI information reported by UEs and accuracy with which
the AMC can match the prevailing conditions. Frequent reporting of CQI in the
time domain allows better matching to channel and interference variations, while
fine resolution in the frequency domain allows better exploitation of frequency-
domain scheduling. However, both lead to increased feedback overhead in the
uplink. Therefore, eNB can configure both time-domain update rate and
frequency-domain resolution of the CQI.
CQI Feedback
In case of CQI feedback, eNB employs periodic reporting of the CQI and UE will
transmit the reports using the PUCCH. Only wideband and UE-selected sub-band
feedback is possible for periodic CQI reporting, for all downlink (PDSCH)
transmission modes. The type of periodic reporting is configured by eNB by RRC
signalling. In case of wideband periodic CQI reporting, the period can be
configured to {2, 5, 10, 16, 20, 32, 40, 64, 80, 160} ms or OFF, and UE reports
one wideband CQI value for the whole system bandwidth. In case of UE selected
sub-band, the total number of sub-bands N is divided into J fractions called
bandwidth parts. One CQI value is computed and reported for a single selected
sub-band from each bandwidth part, along with the corresponding sub-band index.
The value of J depends on the system bandwidth as summarized in below table.
The following table shows the periodic CQI reporting with UE-selected sub-bands:
sub-band size (k) and bandwidth parts (J) versus downlink system bandwidth.
System Bandwidth (RBs) Sub-band Size (k RBs) Number of Bandwidth parts (J)
6-7 (Wideband CQI only) 1
8-10 4 1
11-26 4 2
27-63 6 3
64- 110 8 4
Multiple Antenna Transmission Case

Channel Quality Indicator (CQI)
A CQI index is defined by a channel coding rate value and modulation scheme
(QPSK, 16QAM, and 64QAM) as given in first table of description. In addition to
4-bit absolute CQI indices, three differential CQI values are defined to reduce the
CQI signaling overhead. Note that UE always reports the wideband CQI even
when UE-selected sub-band feedback is used for periodic reporting. This is
because wideband CQI is required for setting the power levels for downlink
control channels that are transmitted in a frequency diverse transmission format
over the wideband to exploit frequency diversity.
Precoding Matrix and Rank Indicator (PMI and RI)
The MIMO transmission rank can be either one or two for the case of two-antenna
ports requiring single-bit Rank Indicator (RI). The numbers of precoders for two
antenna ports are four and two for rank-1 and rank-2 respectively. Therefore,
Precoding Matrix Indicator (PMI) requires two bits for rank-1 and a single bit for
rank-2. In case of four antenna ports, MIMO transmission rank can be one, two,
three, or four requiring two bit rank indication. The number of precoders for each
rank is 16 and therefore requires four bit PMI indication.
SYSTEM OPERATION
How to Activate
Key Parameters
RTRV-CQI-REP/CHG-CQI-REP
TRANSMISSION_MODE Transmission mode.
ci_tm1: Single-antenna port (port 0), DCI format 1 or 1A is used.
ci_tm2: Transmit diversity, DCI format 1 or 1A is used.
ci_tm3: Open-loop spatial multiplexing, DCI format 2A or 1A is used.
ci_tm4: Closed-loop spatial multiplexing, DCI format 2 or 1A is used.
ci_tm5: MU-MIMO, DCI format 1D or 1A is used.
ci_tm6: Closed-loop rank-1 precoding, DCI format 1B or 1A is used.
ci_tm7: Single-antenna port (port 5), DCI format 1 or 1A is used.
ci_tm8: Single-antenna port (port 7/port 8), DCI format 2B or 1A is used
ci_tm9: UE specific RS based Transmission (Rel 10)
ci_tm10: UE specific RS based Transmission (Rel 11)
Counters and KPIs

REFERENCE
LTE-ME3307, UL Sub-frame Bundling

INTRODUCTION
When User Equipment (UE) is at the cell edge, it may undergo power shortage due
to the transmission power limitation. To overcome the power shortage at cell edge,
3GPP LTE provides TTI bundling operation. When TTI bundling is configured by
RRC, HARQ transmissions for a transport block are performed in consecutive
TTIs without waiting for HARQ feedback. Each HARQ transmission depends on
incremental redundancy.
The eNB accumulates the received energy of all transmissions and sends HARQ
feedback only one time after the last redundancy version of transport block is
received.
Therefore, TTI bundling operation reduces the number of required HARQ
feedback messages and overhead resulting from uplink grant
BENEFIT
Extending uplink cell coverage and helpful for applications such as VoIP

Dependency
TTI bundling supportable UE
Limitation
In case of TDD, TTI bundling is only applicable to U/D config 0, 1, and 6. Others
are not available because there is not enough UL subframes in 10ms radio frame
(it should be equal to or greater than 4).
FEATURE DESCRIPTION
The TTI bundling (or subframe bundling) is intended to improve the uplink
coverage performance of VoLTE service, that improves air-interface performance
in scenarios where coverage is limited by UE transmit power capability.
To provide good quality of VoLTE service, both VoLTE packet error rate and
latency are important factors. In case of UE in cell edge, however, bit error rate
can be increased due to high path loss and limited UE transmission power. High
bit error rate can increase both residual VoLTE packet error rate and latency due to
HARQ retransmissions.
The following figure shows the UL subframe bundling operation which can
improve VoLTE service quality in the cell edge and extend the cell coverage.
Concept of generating UL TTI bundles is illustrated in below figure. UL subframe

bundling groups 4 consecutive uplink TTI to generate an effective TTI duration of
4 ms. To use a different Redundancy Version (RV), each duplicate is processed.
The eNB receives with an Incremental Redundancy soft combining gain. The set
of code words are modulated and mapped onto 4 consecutive uplink subframes.
Transmissions belonging to each bundle size are sent without waiting for any
HARQ acknowledgements. The same Modulation and Coding Scheme (MCS) and
frequency bandwidth are used for all 4 TTI belonging to the bundle.
When UL subframe bundling is used, the number of HARQ process is halved from
8 to 4. The timing of HARQ acknowledgement is based on the timing of last TTI
within the bundle, that is, acknowledgement is sent 4 subframes after last TTI in
the bundle. The retransmission delay is 16 subframes (16ms) when using UL
subframe bundling, compared to the retransmisson delay of 8 subframes (8ms)
when UL subframe bundling is not used.
The UL subframe bundling lowers effective transmisson rate and improves the
packet error rate. Latency is also reduced because waiting time for HARQ
ACK/NACK is not required for the first four re-transmissions. Furthermore,
signaling overhead is reduced for ACK/NACK transmissions. On the other hand,
spectral efficiency can be degraded by applying UL subframe bundling feature.
Whether or not to use UL subframe bundling is instructed by RRC message to
each UE. In case of efficient operation of UL subframe bundling, the target UE
selection is important because unnecessary UL subframe bundling assignment can
degrade the spectral efficiency. If UL subframe bundling feature is enabled in eNB,
the eNB checks channel conditions of UEs with on-going QCI 1 VoLTE bearer
and choose some UEs in bad channel condition for UL subframe bundling.
Samsung eNB selects UEs for UL subframe bundling by optimized criterion
considering various channel condition related information, but no configurable
parameter is provided.
SYSTEM OPERATION
How to Activate
The operator can activate or deactivate UL sub-frame bundling by setting the
parameter TTI_BUNDLING in PLD to True (= 1) or False (= 0) respectively. This
parameter means whether to use sub-frame bundling in the cell or not.
Turn ON TrchInfoFunc::TTI_BUNDLING = 1
Turn Off TrchInfoFunc::TTI_BUNDLING = 0
Key Parameters
RTRV-TRCH-INF/CHG-TRCH-INF
CELL_NUM Indexing parameter
TTI_BUNDLING This parameter is used to enable to use TTI bundling.
False: TTI bundling is not used.
True: TTI bundling is used.
MAX_HARQTX_BUNDLING The maximum HARQ transmission count is subframe bundling mode.
Counters and KPIs

REFERENCE
Medium Access Control (MAC) protocol specification
LTE-ME3309, Resource allocation

enhancement for SIB
INTRODUCTION
The system information is broadcasted using Master Information Block (MIB) and
series of System Information Blocks (SIB). The resource elements used by MIB on
the PBCH are fixed as central 72 subcarriers by 3GPP specification, but resource
elements for SIB can be controlled by MAC scheduler. This feature provides the
method for control the resource used for SIB. New resource allocation methods for
SIB not only ensure reliable reception of SIBs but also reduce the overhead, which
is caused by SIBs.
BENEFIT
Resource overhead caused by SIBs can be adjusted in consideration of reliable
reception of system information.

N/A
FEATURE DESCRIPTION
The system information consists of Master Information Block (MIB) and System
Information Block (SIB). MIB is the only system information transferred using the
BCH and PBCH. SIBs are transferred using the DL-SCH and PDSCH. SIB1 has
its own RRC message whereas other SIBs except SIB1 are encapsulated within the
more general System Information RRC message. UE start by reading the MIB and
provides sufficient information to read SIB1. SIB1 provides scheduling
information for the remaining SIB. A summary of the information included within
the MIB and each of the SIB is provided in below table.
System Information Content
Master Information Block Downlink channel bandwidth, PHICH configuration, and SFN
System Information Block 1 PLMN Id, tracking area code, cell selection parameters, frequency band, cell
barring, and scheduling information for other SIB
System Information Block 2 Access class barring, RACH, BCCH, PCCH, PRACH, PDSCH, PUSCH,
PUCCH parameters, UE timers and constants, and uplink carrier frequency
System Information Block 3 Cell reselection parameters
System Information Block 4 Intra-frequency neighbouring cell information for cell reselection
System Information Block 5 Inter-frequency neighbouring cell information for cell reselection
System Information Block 6 UMTS neighbouring cell information for cell reselection
System Information Content

System Information Block 7 GERAN neighbouring cell information for cell reselection
System Information Block 8 CDMA2000 neighbouring cell information for cell reselection
System Information Block 9 Home eNB name
System Information Block 10 Earthquake and Tsunami Warning System primary notification
System Information Block 11 Earthquake and Tsunami Warning System secondary notification
System Information Block 12 Commercial Mobile Alert Service (CMAS) notification
System Information Block 13 MBMS Single Frequency Network(MBSFN) configuration information
The set of Resource Elements used by MIB on PBCH is standardized by 3GPP, so

does not require any additional signaling, that is, PBCH occupies the central 72
subcarriers within the first 4 OFDMA symbols of the second slot of a radio frame.
The same allocation is made for both FDD and TDD. On the other hand, the set of
Resource Elements used by SIB on PDSCH is not standardized by 3GPP, so
requires additional signaling to inform UE of where to look. The PDCCH is used
to provide this additional signaling. The PDCCH includes a CRC, which is
scrambled by System Information RNTI (SI-RNTI) if it includes resource
allocation information relevant to SIB. The SI-RNTI has been standardized to have
a single fixed value of FFFF.
The eNB is responsible for scheduling Resource Blocks (RBs) used to transfer the
SIB. The MIB and SIB1 are broadcast at a rate which is specified by 3GPP. The
rate at which other SIBs are broadcast is implementation dependent. Downlink
Control Information (DCI) format 1A and 1C can be used to signal PDSCH
resource allocation for the SIB. DCI format 1A supports localized/distributed
resource allocation and DCI format 1C supports distributed resource allocation.
Samsung eNB allocates the SIB in localized manner, so DCI format 1A is used.
When DCI format 1A is used to schedule resources for SIB, the modulation
scheme is always QPSK (the modulation scheme specified within the MCS table is
ignored). In addition, TBS index is set equal to the value of MCS bits rather than
reading its value from MCS table. TPC Command is not used for power control
but is used to identify the Transport Block Size (TBS). The most significant bit is
ignored while the least significant bit indicates whether column 2 or column 3
should be selected from within the TBS table that is the number of allocated RBs
should be assumed to be either 2 or 3 for the purposes of identifying the TBS. A
value of 0 corresponds to 2 assumed RBs, while a value of 1 corresponds to 3
assumed RBs. In summary, MCS index in DCI format 1A represents TBS of SIB,
and link adaptation is done by number of allocated RBs only.
Samsung eNB supports to control number of allocated RBs for SIBs. To adjust the
number of RBs for SIBs, two different cases are categorized according to the
urgency of SIB reception: Normal and Exceptional case.
Normal Case
Normally UE reads system information in RRC Idle mode to acquire the
parameters necessary to access the network. While UE read SIBs to access the
network, UE does not need to acquire SIBs in urgent since SIBs are repeated
periodically. SIB1 is repeated at a rate of 20ms by 3GPP specification, and other
SIBs are repeated according to the periodicity indicated by SIB1 in the range of
{80ms, 160ms, 320ms, 640ms, 1280ms, 2560ms, 5120ms}. In normal case, the
less number of RBs can be used to allocate SIBs to reduce resource overhead and
increase capacity.
Exceptional Case
In certain cases, UE need to acquire SIBs immediately, that is, modification of
System Information, ETWS, and CMAS. The UE in RRC connected should
receive SIBs as fast as possible in case of SI modification since UE needs to
communicate with eNB using new system information. If UE communicates with
eNB using old system information, the communication will fail, and moreover
transmission of UE causes interference to other UEs. In case of ETWS and CMAS,
UE needs to receive quickly to response against disasters.
Samsung eNBs control number of RBs for SIBs using two weight factors,
BCCH_SCALING_FACTOR and BCCH_REDUCE_FACTOR as follows:
Exceptional case: Number of SIB RBs = Default RBs x
BCCH_SCALING_FACTOR/16
Normal case: Number of SIB RBs = Number of SIB RBs for Exceptional
case/BCCH_REDUCE_FACTOR
In the above cases, defaults RBs are fixed number of RBs for SIB determined by
its TBS. If BCCH_REDUCE_FACTOR = 1, number of SIB RBs in Normal case
becomes same as that in Exceptional case.
SYSTEM OPERATION
How to Activate
The operator can control number of RBs for SIB by related parameters.
Key Parameter
RTRV-MACCTRLCH-FUNC/CHG-MACCTRLCH-FUNC
BCCH_SCALING_FACTOR This parameter determines the number of RBs for BCCH in exceptional case,
which is given by :
The number of default RB x BCCH_SCALING_FACTOR/16.
BCCH_REDUCE_FACTOR This parameter determines the number of BCCH RBs in normal case in
conjunction with BCCH_SCALING_FACTOR, which is given by :
The number of default RB x
BCCH_SCALING_FACTOR/BCCH_REDUCE_FACTOR/16.
Counters and KPIs

REFERENCE
[1] 3GPP TS 36.211 E-UTRA Physical Channels and Modulations
[2] 3GPP TS 36.213 E-UTRA Physical Layer Procedures
[3] 3GPP TS 36.331 E-UTRA Radio Resource Control (RRC) Protocol
Specification
LTE-ME3503, CFI-based PUSCH adaptation

INTRODUCTION
The PUCCH resources are allocated in edge of the system bandwidth, and the
number of PUCCH resources becomes overhead to reduce UL throughput. Among
PUCCH resources, format 1a/1b resources for HARQ-ACK are mapped to CCEs
in DL subframe. Because number of CCEs depends on CFI, the number of
PDCCH symbols, the number of PUCCH resources for HARQ-ACK also depends
on CFI. This feature enables UL scheduler allocates the number of PUSCH RBs
according to the change of PUCCH HARQ-ACK resources by CFI change.
BENEFIT
The UL peak throughput can be achieved while PDCCH symbols are flexibly
changed.

Dependency
This feature is supported in TDD 20 MHz bandwidth only.
This feature is operated in PUCCH state 0 only.
FEATURE DESCRIPTION
The PUCCH is used to transfer Uplink Control Information (UCI). Number of
PUCCH resources is sum of number of resources for format 1/1a/1b and that for
format 2.
The PUCCH format 1/1a/1b includes Scheduling Request (SR) and HARQ-ACK.
HARQ-ACK can be seperated as Semi-Persistent Scheduling (SPS) and PDCCH
based scheduling. The locations of each PUCCH resources are shown in below
figure, where CQI is located in edge of system bandwidth. SPS HARQ-ACK and
SR is located inside of CQI, where the number of SPS HARQ-ACK and SR is
determined by higher-layer RRC parameter N(1)PUCCH. The position of HARQ-
ACK by PDCCH based scheduling is nearest to PUSCH region.
The SR resources and SPS HARQ-ACK resources are allocated per UE

dedicatedly, but HARQ-ACK resources according to PDCCH based scheduling
are mapped to PDCCH CCE indices of the corresponding DL transmission.
The PUCCH HARQ-ACK resource index is calculated as follows:
FDD: N(1)PUCCH + n_CCE
TDD: N(1)PUCCH + (M-m-1) x N(p) + m x N(p+1) + n_CCE
oN(1)PUCCH: number of resources reserved for SPS HARQ-ACK and SR.
on_CCE: PDCCH CCE index of the corresponding DL transmission.
In TDD, HARQ-ACKs for multiple DL subframes are bundled in one UL
subframe, so PUCCH HARQ-ACK resources are multipled by number of bundled
DL subframes. M is the number of DL bundled subframes and m is the subframe
index where the PDCCH CCE index is mapped to HARQ-ACK. M is 2 for UL/DL
Configuration 1 and 4 for UL/DL Configuration 2.
The following figure shows HARQ-ACK resource allocation for TDD UL/DL
Configuration #2:
In the above figure, the position of HARQ-ACK resource depends on CCE index
and PDSCH subframe index, and can be separated by CFI. This means some
HARQ-ACK resources are not used when the corresponding DL subframe uses
small number of PDCCH symbols. Because positions of PUCCH HARQ-ACK
resources are close to PUSCH region, unused RBs for PUCCH HARQ-ACK can
be used for PUSCH transmission. Hence, UL throughput can be increased by
restricting CFI and reduce HARQ-ACK resources, especially in TDD.
Another way is to change maximum number of PUSCH RBs dynamically based
on CFI as below figure. By flexibly changing number of PUSCH RBs, UL
throughput can be maintained while adapting number of PDCCH symbol.
When this function is enabled, Samsung eNB reduces frequency of changing

PDCCH symbol because CFI increase makes PUSCH RBs be smaller, where
PUSCH retransmission may be not transmitted. So, CFI increase needs to wait
until all UL retransmission is transmitted.
This function is only applied in PUCCH state 0 in TDD 20MHz by following
reason:
The number of HARQ-ACK resources in TDD is much more than FDD. Hence,
this function is more effective in TDD than in FDD.
The side effect of this function, the reduction of frequency of changing PDCCH
symbol, may influence the number of PDCCH allocation failure in large
number of UEs. This side effect can be reduced if there are a lot of CCEs per
CFI as 20MHz BW.
SYSTEM OPERATION
How to Activate
The operator can activate of deactivate this feature by setting the parameter
CFI_PUSCH_ALLOC_ENABLE in PLD.
Turn ON PuschConfIdle::CFI_PUSCH_ALLOC_ENABLE = 1
Turn OFF PuschConfIdle::CFI_PUSCH_ALLOC_ENABLE = 0
Key Parameter
RTRV-PUSCH-IDLE/CHG-PUSCH-IDLE
CFI_PUSCH_ALLOC_ENAB This parameter is used to enable this feature.
LE 0: This feature is not used.
1: This feature is used.
Counters and KPIs

REFERENCE
[1] 3GPP TS 36.211 E-UTRA Physical Channels and Modulations
[2] 3GPP TS 36.213 E-UTRA Physical Layer Procedures
[3] 3GPP TS 36.331 E-UTRA Radio Resource Control (RRC) Protocol
Specification
Chapter 6 Radio
Transmission
LTE-ME0102, FDD 3MHz Bandwidth

INTRODUCTION
In the LTE system, total six channel bandwidths are standardized in 3GPP
specification: 1.4, 3, 5, 10, 15, and 20 MHz channel bandwidth. In this feature, it is
described of 3 MHz channel bandwidth configuration, which is composed of total
15 resource block (RB). 1 RB is 180 kHz frequency spacing, and actually the
bandwidth of 2.7 MHz is used for transmission except for guard bandwidth.
Therefore, the spectral efficiency is 90% for 3 MHz channel bandwidth
configuration.
BENEFIT
The operator can support LTE service with channel bandwidth of 3 MHz.

N/A
FEATURE DESCRIPTION
3GPP has specified a set of six channel bandwidths, ranging from 1.4 MHz to 20
MHz. These are presented in the following table:
Parameter Channel Bandwidth
Number of Resource Blocks 6 15 25 50 75 100
Number of Subcarriers 72 180 300 600 900 1200
The following figure shows the definition of Channel Bandwidth and

Transmission Bandwidth Configuration for one E UTRA carrier:
Chapter 6 Radio Transmission
A Resource Block (RB) represents the basic unit of resource for LTE air-
interface. The eNB scheduler allocates RBs to UE when allowing data transfer.
The subcarriers belong to Orthogonal Frequency Division Multiple Access
(OFDMA) technology in downlink, and Single Carrier Frequency Division
Multiple Access (SC-FDMA) technology in uplink.
There are 12 subcarriers per RB so the number of subcarriers equals 12 x number
of RBs.
Each subcarrier occupies 15 kHz so the total subcarrier bandwidth equals 15 kHz
x number of subcarriers.
The downlink subcarrier bandwidth includes an additional 15 kHz to
accommodate a null subcarrier at the center of all other subcarriers. The null
subcarrier provides 15 kHz of empty spectrum within which noting is
transmitted.
The total subcarrier bandwidth is less than the channel bandwidth to allow for the
roll-off of emissions and to provide some guard band.
The larger channel bandwidths provide support for the higher throughputs.
Smaller channel bandwidths provide support for lower throughputs but are
easier to accommodate within existing spectrum allocations.
3GPP also specifies a subcarrier spacing of 7.5 kHz (in addition to the subcarrier
spacing of 15 kHz). The subcarrier spacing of 7.5 kHz is only used in cells
which are dedicated to Multimedia Broadcast Multicast Services (MBMS).
There are 24 rather than 12 carriers per RB when using 7.5 kHz subcarrier
spacing so the total bandwidth of a RB remains the same.
The following figure shows a time-frequency resource structure in 3 MHz channel
bandwidth LTE system:
The time-frequency resources are subdivided according to the following structure:

The largest unit of time is the 10 ms radio frame, which is further subdivided into
ten 1 ms subframes, each of which is split into two 0.5 ms slots.
Each slot comprises seven OFDM symbols in the case of the normal cyclic prefix
length, or six if the extended cyclic prefix is configured in the cell.
In frequency domain, resources are grouped in units of 12 subcarriers (thus
occupying a total of 180 kHz), such that one unit of 12 subcarriers for duration of
one slot is termed a Resource Block (RB). The smallest unit of resource is
Resource Element (RE), which consists of one subcarrier for duration of one
OFDM symbol. Thus, a RB is comprised of 84 resource elements in the case of
normal cyclic prefix length.
SYSTEM OPERATION
How to Activate
Execute the RTRV-CELL-IDLE command to retrieve both DL_BANDWIDTH
and UL_BANDWIDTH used by an operating cell.
Key Parameters
RTRV-CELL-IDLE
PHY_CELL_ID This parameter is the Physical cell ID. It is used to allow the UE to identify
the cell in a radio section, and to recover the cell specific reference signal.
It should be allocated to avoid conflict between neighbor cells.
CELL_TYPE This parameter is the type that is operating the cell:
macroCell: Operates many normal cells.
openCell: Operates a single normal cell.
hybridCell: Operates CSG cells as well as normal cells.
csgCell: Operates only Closed Subscriber Group (CSG) cells.
DUPLEX_TYPE This parameter is the communication method that is used while operating
the cell:
UL_ANT_COUNT This parameter is the number of Rx antennas used by an operating cell.
EARFCN_DL This parameter is the downlink absolute radio frequency channel number
(ARFCN) used in the evolved universal terrestrial radio access network (E-
UTRAN) system of an operating cell. The center frequency must be
changed to E-UTRA absolute radio frequency channel number (EARFCN).
[Related Specifications] Refer to 3GPP TS 36.101, 5.7.3.
EARFCN_UL This parameter is the Uplink ARFCN used in the E-UTRAN system of an
operating cell. The center frequency must be changed to EARFCN.
[Related Specifications] Refer to 3GPP TS 36.101, 5.7.3.
DL_BANDWIDTH This parameter is the downlink bandwidth used by an operating cell:
1.4MHz: 1.4 MHz bandwidth that uses 6 Physical RBs.
3MHz: 3 MHz bandwidth that uses 15 physical RBs.
20MHz: 20 MHz Bandwidth that uses 100 physical RBs.
UL_BANDWIDTH This parameter is the uplink bandwidth used by an operating cell.
1.4MHz: 1.4 MHz bandwidth that uses 6 Physical RBs.
20MHz: 20 MHz Bandwidth that uses 100 physical RBs.
FREQUENCY_BAND_INDICAT This parameter is the frequency band indicator information, which is about
OR where the frequency of an operating cell is located. This information is
broadcasted to the UE through SIB 1.
GROUP_ID This parameter is the Group ID of the carrier where the cell belongs.
FORCED_MODE This parameter indicates whether to change the configuration regardless of
the cell status.
False: Set the value considering the cell status.
True: Set the value without considering the cell status.
DL_CRS_PORT_COUNT This parameter is the number of downlink CRS ports that are supported by
the system.
Counters and KPIs

There is no related counter and KPI.
REFERENCE
[1] 3GPP TS 36.101: Evolved Universal Terrestrial Radio Access (E-UTRA); User
Equipment (UE) radio transmission and reception
[2] 3GPP TS 36.104: Evolved Universal Terrestrial Radio Access (E-UTRA);
Base Station (BS) radio transmission and reception
[3] 3GPP TS 36.211: Evolved Universal Terrestrial Radio Access (E-UTRA);
Physical channels and modulation
LTE-ME0201, Frame Structure Type 1 (FDD)

INTRODUCTION
The frame structure considers only the time domain. 3GPP TS 36.211 specifies
frame structure 'Type 1' and 'Type2'. Frame structure type 1 is applicable to FDD
(both full and half duplex), whereas frame structure type 2 is applicable to TDD.
In both cases, radio frames are numbered using their System Frame Number (SFN).
The transmission resource consists of a consecutive radio frame. Each radio frame
is composed of 10 subframes with 1ms length and each subframe is composed of
two slots, that is, totally radio frame is a composition of 20 slots indexed 0 to 19.
Each slot has duration of 0.5 ms. Downlink and uplink transmission of a radio
frame is divided in frequency domain.
BENEFIT
The operator can support FDD-LTE service.

Dependency
FDD Only
FEATURE DESCRIPTION
The Frame structure type 1 is applicable to half duplex FDD.
The following figure shows the frame structure type 1:
The smallest one is called a slot, which is of length Tslot = 0.5 ms.
Two consecutive slots are defined as a subframe of length one ms, and 20 slots,
numbered from 0 to 19, constitute a radio frame of 10ms. Channel-dependent
scheduling and link adaptation operate on a subframe level. Therefore, the suframe
duration corresponds to the minimum downlink TTI, which is of one ms duration,
compared to a 2 ms TTI for the HSPA and a minimum 10 ms TTI for the UMTS.
A shorter TTI for fast link adaptation and is able to reduce delay and better exploit
the time varying channel through channel dependent scheduling.
Each slot consists of a number of OFDM symbols including CPs. CP is a kind of
guard interval to combat inter-OFDM-symbol interference, which should be larger
than the channel delay spread. Therefore, the length of CP depends on the
environment where the network operates, and it should not be too large as it brings
a bandwidth and power penalty. With a subcarrier spacing f = 15 kHz, the
OFDM symbol time is 1/f 66.7 us.
The LTE defines two different CP lengths:
Normal CP
Extended CP
A normal CP and an extended CP correspond to seven and six OFDM symbols per
slot, respectively. The extended CP is for multicell multicast/broadcast and very
large cell scenarios with large delay spread at a price of bandwidth efficiency, with
length 16.7 us. The normal CP is suitable for urban environment and high data rate
applications. Note that the normal CP lengths are different for the first and
subsequent OFDM symbols, which is to fill the entire slot of 0.5 ms. For example,
with 10 MHz bandwidth, the sampling time is 1/(15000x1024) s and the number of
CP samples for the extended CP is 256, which provides the required CP length of
256/(15000x1024)1.67 us. In case of 7.5 kHz subcarrier spacing, there is only a
single CP length, corresponding to three OFDM symbols per slot.
The typical parameters for frame structure are as follows:
Parameter Transmission bandwidth [MHz]
1.4 3 5 10 15 20
Occupied bandwidth [MHz] 1.08 2.7 4.5 9.0 13.5 18.0
Guard band [MHz] 0.32 0.3 0.5 1.0 1.5 2.0
Sampling frequency [MHz] 1.92 3.84 7.68 15.36 23.04 30.72
FFT size 128 256 512 1024 1536 2048
Number of occupied subcarriers 72 180 300 600 900 1200
Number of resource blocks 6 15 25 50 75 100
SYSTEM OPERATION
How to Activate
The separate activate procedure is not necessary for this feature.
Key Parameters
There is no related parameter.
Counters and KPIs

There is no counter or KPI.
REFERENCE
Chapter 7 Services
LTE-SV0303, OTDOA
INTRODUCTION
In the Observed Time Difference of Arrival (OTDOA) positioning method, UE
makes an observation of the arrival time difference of Reference Signal (RS) from
two or more eNBs. Then, the position of UE can be calculated based on the known
position of eNBs and the time differences.
The time difference between the RS from the serving cell and the neighbor cells
are called Reference Signal Time Difference (RSTD). To measure the RS from
(probably far away) neighbor cells, a special positioning signal is defined in
Release 9 and called Positioning Reference Signal (PRS). PRS was introduced to
improve the hearability of neighboring cells within completing measurements for
the downlink OTDOA positioning method. 3GPP recognized that the hearability of
the existing cell-specific reference signals was not sufficient to support the
OTDOA positioning method. Therefore, hearability can be challenging as a result
of neighboring cells being co-channel with the serving cell, especially at locations
where the serving cell signal strength is high.
In case of E-SMLC, UE provide RSTD information through the LPP protocol
layer and eNB provides PRS and base station information through the LPPa
protocol layer. Then, E-SMLC makes a final decision on the position of UE. The
MME transparently relays LPP and LPPa layer information to E-SMLC.
BENEFIT
The operator can provide an OTDOA-based location service.
End users can get more accurate location-based services such as maps and
navigations.

Dependency
UE that support OTDOA based on 3GPP Release 9 or later version.
MME to support LPPa protocol
E-SMLC to support OTDOA
eNB that support PRS
Precise synchronization between eNBs is required for better accuracy (GPS
synchronization is recommended)
Chapter 7 Services
Limitation
Air interface throughput is impacted due to PRS broadcasting as there is no
PDSCH data in the subframe where PRS located.
In rural areas, there are fewer measureable cells which may impact accuracy.
PRS subframe configuration needs to be manually planned to ensure no
overlapping with PBCH, SIBs, Paging, and Measurement Gap scheduling.
No SON Functionality is available to support automatic PRS configuration, PRS
configurations will have to be manually planned and configured.
FEATURE DESCRIPTION
The OTDOA positioning method makes use of Reference Signal Time Difference
(RSTD) measurements from UE. The RSTD quantifies the subframe timing
difference between a reference cell and a neighboring cell. The accuracy of the
positioning calculation is improved if UE can provide RSTD measurements from
an increased number of cells. RSTD is measured in units of Ts (1/30720 ms) and is
reported to the Enhanced Serving Mobile Location Center (E-SMLC) where the
location calculation is completed. E-SMLC is a network element within the
operator's infra network.
The UE receives an LTE Positioning Protocol (LPP) Provide Assistance Data
message from E-SMLC. This message is packaged by MME as a NAS message
before being packaged by eNB as an RRC message. The Provide Assistance Data
message includes both the reference and neighboring cells information. The
reference cell does not have to be the current serving cell for UE.
The PRS are able to coexist with both the cell specific reference signals and the
physical layer control information at the start of each subframe (PCFICH, PHICH,
and PDCCH). Also, PRS occupies an increased number of resource elements
within a subframe relative to the cell specific reference signals to help improve
RSTD measurement accuracy. The sequence used to generate the positioning
reference signal is a function of the physical cell identity (PCI) and the cyclic
prefix duration (normal or extended). The PRS are broadcasted using antenna port
6. They are not mapped onto resource elements allocated to the PBCH, Primary
synchronization signal nor secondary synchronization signal. The PRS are only
defined for 15 kHz subcarrier spacing. They are not supported for 7.5 kHz
subcarrier spacing used by Multimedia Broadcast Multicast Services (MBMS).
Below figure shows examples of PRS for normal cyclic prefix. There is a
dependency upon the number of antenna ports used for the cell specific reference
signal. Additional symbols are used by the cell specific reference signal when
broadcast from four antenna ports.
The following figure is Mapping of positioning reference signals (normal cyclic
prefix):
Chapter 7 Services
The PRS configuration parameters include PRS Bandwidth, PRS Configuration

Index, Number of Consecutive Downlink Subframes, and PRS Muting
Configuration.
PRS Bandwidth: The bandwidth that PRS occupied. The PRS bandwidth is
signalled to UE with a value of 6, 15, 25, 50, 75, or 100 resource blocks. The
positioning reference signal bandwidth is always centered on middle of the
channel bandwidth. The PRS configuration index is used to define both a
periodicity and subframe offset for the timing of the positioning reference
signal. The look-up table presented below is used to link the configuration
index to the periodicity and subframe offset. Below table is Positioning
Reference Signal subframe configuration.
PRS Configuration Index: The PRS Configuration Index (IPRS) defines the
periodicity (TPRS) and subframe offset (PRS) for timing of the PRS.
The following table shows the relation among these parameters:
Number of Consecutive Downlink Subframes: The number of consecutive

downlink subframes defines the number of subframes during which the
positioning reference signal is broadcast within each positioning reference
signal period. The number of consecutive downlink subframes can be
configured with values of 1, 2, 4, or 6 subframes.
Chapter 7 Services
PRS Muting Configuration: PRS muting Configuration consist of 2, 4, 8, or 16

bits map sequence. The periodicity of the muting pattern is defined by the
length of the bits map. The PRS positioning occasion will not exist in the
subframe if the corresponding bit is set to 0.
Based on 3GPP 36.211, PRS is not transmitted in RE allocated to PBCH, PSS, and
SSS and UE only uses PRS except resources allocated to PBCH, PSS, and PSS,
SSS. PBCH and synchronization signal are transmitted in subframe #0 and
bandwidth (6RB), where the corresponding resources are allocated due to this, can
transmit PRS to only 38% (FDD) or 50% (TDD) among total REs available for
PRS allocation. Therefore, when configuring PRS configuration index in PLD in
Samsungs systems, it is suggested to operate without transmitting PRS in
subframe #0.
To allocate PDSCH and PRS to the same RB, it needs to puncture PDSCH in RE
to where PRS is transmitted, and this can cause performance decrease of PDSCH
reception and PRS reception of neighbor cell. Therefore, Samsung does not
transmit PDSCH in RBs where PRS is allocated. In case of Paging and SIB1
transmitted to a fixed subframe, it is assumed that there is no PRS when UE
decodes the corresponding traffic and if this is not the case, PRS is received.
Therefore, if one of either Paging/SIB1 or PRS needs to puncture the other, the
reception performance of Paging/SIB1 or PRS decreases. Thus, it is suggested to
service providers to operate without transmitting PRS in subframe (= 5, 9) to
where Paging/SIB1 is transmitted, when setting up PRS configuration index.
The eNB interworks with E-SMLC with LPPa interface. OTDOA Information
Exchange procedure is used to allow the E-SMLC request eNB to transferOTDOA
information to the E-SMLC. The procedure consists of the following messages:
OTDOA Information Request/Response/Failure
After eNB receives the OTDOA information request message from E-SMLC,
the OTDOA information transfer function performs according to reception of
the requested information and it performs as follows.
oIf it received OTDOA cell information: It transmits the OTDOA
INFORMATION RESPONSE message including the ODTOA cell
information.
oIf it fails to receive OTDOA cell information: It transmits OTDOA
INFORMATION FAILURE message including the cause (value) of the
failure.
Followings are OTDOA Cell Information:
PCI
Cell ID
TAC
EARFCN
PRS Bandwidth
PRS Configuration Index
CP Length
Chapter 7 Services
Number of DL Frames
Number of Antenna Ports
SFN Initialization Time
E-UTRAN Access Point Position
PRS Muting Configuration
To implement RSTD measurement, UE need some assistance date send from E-
SMLC via LTE Positioning Protocol (LPP) interface. The UE receives an LPP
Provide Assistance Data message from the E-SMLC. This message is packaged by
MME as a NAS message before being packaged by eNB as an RRC message. The
Provide Assistance Data message includes information regarding both the
reference and neighboring cells.
The content of the reference cell information is presented in below table. Similar
information is also provided for each of the neighboring cells.
Information Element
physCellId
cellGlobalId
earfcnRef
antennaPortConfig
cpLength
prsInfo prs-Bandwidth
prs-ConfigurationIndex
numDL-Frames
prs-MutingInfo
After receive the OTDOA assistance data, UE shall start RSTD measurement and
report the measurement results to E-SMLC through LPP interface where the
location calculation is completed.
Measurement Gap Exclusion

To ensure UE can perform RSTD measurement, measurement gap shall not be
schedule in the subframes where PRS located, otherwise RSTD measurement can
fail when UE are doing inter-FA/RAT measurement.
The eNB support excluding specified measurement gap offsets and the exact
excluded gap offset is configurable (gap pattern 0: 0~39; gap pattern 1: 0~79) to
ensure all UE to receive PRS. The excluded offset can be one offset or
combination of several offsets. The measurement gap offset exclusion can be
enable/disabled (ON/OFF).
The operator can configure the starting offset and rang of consecutive gap offset.
Starting gap offset range is 0~39 or 0~79 considering of gap pattern, while rang of
consecutive gap offset number can be 1~15. For example, if starting offset set to 0
and offset range set to 15, then gap offset 0~14 are excluded.
Chapter 7 Services
Inter-frequency RSTD Measurement Support

In OTDOA positioning method, especially in inter frequency cell deployment, E-
SMLC may request UE to perform inter frequency RSTD measurement to improve
the accuracy by obtaining more RSTD measurement results. This feature enables
eNB to configure to start or stop the requested measurement gap sent from UE by
a new introduced Release 10 RRC procedure 'Inter-frequency RSTD measurement
indication', 'Inter-frequency RSTD measurement indication'. After eNB receive the
requested measurement gap from UE, eNB may start to configure the gap as UE
requested or ignore the gap configuration if the requested gap is not acceptable in
the system based on operator's configuration. Currently, three options are provided
for operator to control eNB's action when receive UE's 'inter-frequency RSTD
measurement indication' message:
Ignore: The eNB ignore UE's request, the measurement gap will not be assigned
to UE. The purpose of this option is to limit the impact to current UE's
performance as measurement gap may have bad impact to the performance.
Accept: The eNB always accept UE's request. The purpose of this option is to
ensure UE to receive inter-frequency RSTD measurement for better accuracy
of LCS.
Measurement Gap Algorithms based: In this option, if UE's requested
measurement gap offset can be accepted by the current measurement gap
allocation algorithms then the gap will be allocated to UE, if UE's requested
measurement gap offset cannot be accepted by the current measurement gap
allocation algorithms then the requested gap will be ignored.
Operator Configurable PRS Power Boosting

This feature supports PRS power boosting with respect average max power. To
ensure good RSTD measurement performance, PRS power is configured a little bit
bigger power. The configurable range is from 0dB to 7.75dB by 0.5 dB step.
SYSTEM OPERATION
How to Activate
In case of activate OTDOA function, the OTDOA_ENABLE parameter value
must be set to '1(True)' (executing the CHG-POS-CONF command).
In case of activate measurement gap exclusion function, the
MEAS_GAP_OFFSET_EXCLUDED parameter value must be set to 'True'
(executing the CHG-POS-CONF command).
In case of activate PRS power boost function, the
PRS_POWER_BOOST_OFFSET parameter value must be set greater than '0'
(executing the CHG-POS-CONF command).
Chapter 7 Services
In case of activate Inter-Frequency RSTD measurement gap assignment function,

the RSTD_MEAS_GAP_OPTION parameter value must be set to
'AlwaysAccept' or 'ByAlgorithm' (executing the CHG-MSGAP-INF
command).
Key Parameters
RTRV-POS-CONF/CHG-POS-CONF
OTDOA_ENABLE If the otdoaEnable value is set to 1 (ON) to execute OTDOA included in the UE
Positioning function, eNB transmits a PRS signal and UE transmits related
configuration, and so on to eNB. If the otdoaEnable value is set to 0 (OFF),
eNB does not transmit PRS but transmits the information of the cell.
PRS_BANDWIDTH The positioning reference signal (PRS) bandwidth value. If operator enters this
value, eNB forwards the value to the MAC layer.
Transmission bandwidth of PRS. Values from 0 to 5 are mapped with
prsBw6_1.4 MH, prsBw6_1.4 MHz, prsBw15_3 MHz, prsBw25_5 MHz,
prsBw50_10 MHz,
MEAS_GAP_OFFSET_EXC This attribute represents that measurement gap offset exclusion function is
LUDED activated or deactivated.
For Inter-Frequency RSTD measurement gap assignment function,

RTRV-MSGAP-INF/CHG-MSGAP-INF
RSTD_MEAS_GAP_OPTIO This parameter indicates the methods how to allocate MeasurementGap when
N eNB receives an InterFreqRSTDMeasurementIndication from UE.
For PRS power boost function.

RTRV-POS-CONF/CHG-POS-CONF
PRS_POWER_BOOST_OF This parameter is the PRS power boosting offset value. When operator enters
FSET the value, eNB transmits the value to the MAC layer.
Counters and KPIs

REFERENCE
[2] 3GPP TS36.455 Evolved Universal Terrestrial Radio Access (E-UTRA); LTE
Positioning Protocol A (LPPa)
Chapter 7 Services

[4] 3GPP TS 36.305 Evolved Universal Terrestrial Radio Access Network (E-
UTRAN); Stage 2 functional specification of User Equipment (UE) positioning in
E-UTRAN
[5] 3GPP TS 36.355 Evolved Universal Terrestrial Radio Access (E-UTRA); LTE
Positioning Protocol (LPP)
Requirements for support of radio resource management
Chapter 7 Services
LTE-SV0404, VoLTE Quality Enhancement

INTRODUCTION
The VoLTE traffic is characterised by periodic, small sized packets. Generally
QCI=1, RLC UM mode guaranteed bit rate (GBR) bearers are used for carrying
VoLTE traffic. The VoLTE quality enhancement functions are enabled based on
QCI of the bearer UE is having.
The user perceived quality of VoLTE service is determined by several parameters
like packet delay/jitter and packet loss.
Samsung implements the below mentioned functions to enhance the user observed
quality of VoLTE service:
VoLTE-aware UL grant
Configuration of Target BLER for VoLTE
Conservative RB Allocation for VoLTE
Reduction of UL packet loss at source eNB during handover
Reduction of DL packet loss at source eNB during handover
VoLTE related counters
BENEFIT
The voice quality reduction related to RTP loss and delay, which are used as
VoLTE service quality indicators by operator, is enhanced.
The operator can recognize VoLTE related counters.
User experienced VoLTE service is enhanced by reducing packet loss or
preventing silence period during VoLTE session calls.

DL cell throughput will be impacted due to conservative RB allocation for
VoLTE user HARQ re-transmissions.
UL cell throughput will be impacted due to VoLTE-aware UL grant in case of
SID period of a VoLTE session.
Downlink packet mirroring might cause duplicate packets to be delivered to
application layer (RTP).
Chapter 7 Services
FEATURE DESCRIPTION
VoLTE-aware UL Grant
The VoLTE service is characterised by small sized periodic packets, for example,
about 60byte packets every 20ms. The UE needs to send buffer status report (BSR)
MAC control element to eNB to obtain uplink grant for sending these small sized
data packets. Since VoLTE traffic is periodic in nature, UE periodically sends
BSR to eNB. There could be scenarios where UE has data available for
transmission but the networks view of UE state is otherwise. Below are two such
cases:
1 The UE transmits BSR along with VoLTE packet and this MAC PDU fails to
receive at eNB even after maximum HARQ re-transmission attempts.
2 The UE transmits a non-zero BSR after transmission of a zero BSR. The BSR
can be received at eNB in reverse order if the zero BSR transmitted encounters
more HARQ re-transmissions.
Both of these scenarios would result in no UL grant allocation for UE and hence
no data transmission for hundreds of milliseconds. This causes silence periods
during VoLTE call.
The VoLTE-aware UL grant function allocates dummy UL grants to UE even if
the uplink buffer status of UE is calculated as zero. UL scheduler allocates uplink
grant based on the recent non-zero BSR of UE, when
32 milliseconds after the point when the internal buffer occupancy of UE is
calculated as zero.
32 milliseconds after receiving zero BSR from UE
This may reduce the overall UL resource, but enhances VoLTE service quality in
poor uplink radio coverage scenarios.
Configuration of Target BLER for VoLTE

Unlike the non-GBR bearer services which demands high spectral efficiency due
to throughput oriented characteristics, VoLTE bearer requires low spectral
efficiency. Due to this, VoLTE demands very less throughput, but VoLTE bearer
is delay sensitive. So, VoLTE Quality Enhancement function sets the target BLER
lower than the conventional services to reduce downlink and uplink packets
transmission error rate. Since the throughput requirements are low for VoLTE
service, MCS is allocated conservatively to improve HARQ error rate and to meet
the target BLER.
UE Type UL Target BLER DL Target BLER
VoLTE 2.7 % 2.5 %
Non VoLTE 10 % 10 %
Chapter 7 Services
Conservative RB Allocation for VoLTE

To prevent VoLTE service quality deterioration in a poor radio condition, VoLTE
Quality Enhancement function allocates downlink resources conservatively to
reduce HARQ error rate and BLER.
If the initial transmission and first re-transmission of a VoLTE MAC PDU fails,
then DL scheduler allocates 8 times more resource blocks than the initial
transmission for second re-transmission onwards. If the increased resource block
count is greater than maximum PDSCH RB allocation limit, then maximum
possible RBs are allocated. In case of increased RB allocation, MCS is still
maintained same as previous transmission and hence code-rate of this re-
transmission reduces considerably. Reduced code rate helps to improve HARQ
error rate.
[Reduction of UL Packet Loss at Source eNB during Handover]

During Handover procedure, eNB RLC performs RLC Re-establishment as soon
as RRC layer creates and sends 'Handover Command' message to lower layer.
Hence, RLC buffer is flushed, stops timers and resets RLC state variables. Any UL
packets that arrive at eNB after the moment will be lost.
Practically, Handover command may take a while to reach to UE via HARQ/ARQ
retransmissions. In this case, UE will keep sending UL packets over the air until it
receives Handover command and these packets will be lost at eNB.
To prevent this packet loss during handover, eNB does not perform RLC Re-
establishment when 'Handover command' is sent to UE.
In case of UL, the packet remaining in the RLC re-ordering buffer is not
discarded after transmitting HO command, but the packet from MAC is
assembled and transmitted to S-GW.
In case of DL, the packet remaining in the RLC buffer is not discarded but
transmitted to UE.
This function helps to reduce the chance of packet loss of VoLTE service during
Handover.
Chapter 7 Services
Reduction of DL Packet Loss at Source eNB during Handover

During Handover, the loss of VoLTE packets degrades VoLTE quality. As QCI1
bearers are serviced by RLC UM mode in general, DL VoLTE packets that are yet
not transmitted over the air and waiting to be scheduled in RLC buffer will be
flushed when 'Handover command' is sent to UE.
So, to further reduce DL packet loss during handover, eNB mirrors one DL
VoLTE packet (QCI 1) in PDCP layer. During handover, source eNB forwards the
mirrored VoLTE packets to target eNB. Once received the packets, target eNB
send this packet to UE to minimize packet loss.
The detailed feature operation can be described as:
When eNB receives VoLTE packet from S-GW, the packet is copied and saved
in mirroring buffer in the PDCP layer before processing RoHC and ciphering
functions.
Original VoLTE packet is transmitted to RLC after processing RoHC and
ciphering functions.
Mirroring buffer saves one VoLTE packet. If mirroring buffer already contains a
packet, the older packet is deleted and new packet is received.
If Handover command (RRC connection reconfiguration) is transmitted from the
source eNB, the packet saved to that point is transmitted to the target eNB.
Chapter 7 Services
VoLTE Related Counters

VoLTE Related Counter Description
VoLTE call drop rate Statistics on the rate of dropped VoLTE calls among all VoLTE calls
VoLTE intra/S1/X2 handover Statistics on the rate of VoLTE calls with intra/S1/X2 handover success among
success rate VoLTE calls with intra/S1/X2 handover attempt respectively
VoLTE handover latency time Statistics on the Min/Max/Avg latency time collected from target eNodeB
during handover
VoLTE quality defect rate for Statistics on the rate of DL/UL VoLTE bearers respectively with at least one
DL/UL VoLTE bearer occurrence of packet interval greater than threshold (for example, 1 s) among
all VoLTE bearers
HARQ failure rate for DL/UL Statistics on the rate of VoLTE packets with HARQ failure among all VoLTE
VoLTE bearer packets for DL/UL VoLTE bearers respectively
CQI for DL VoLTE bearer Statistics on the CQI report information for DL VoLTE bearers
Distribution of SINR for UL Statistics on the SINR distribution regarding to the before and after Outer-loop
VoLTE bearer compensation for UL VoLTE bearers
SYSTEM OPERATION
How to Activate
This feature is basically activated and cannot be deactivated by operator.
Chapter 7 Services
Key Parameters
Counters and KPIs

Name
VoLTE Quality VoLTE_UlQualityDefect The number of QCI #1 bearers which has NO RTP
Defect Interval during specific amount of time for UL VoLTE
Packet.
VoLTE_DlQualityDefect The number of QCI #1 bearers which has NO RTP
Interval during specific amount of time for DL VoLTE
Packet.
VoLTE VoLTE_IntraEnbAtt Intra handover attempt count
Handover VoLTE_IntraEnbPrepSucc Successful intra handover preparation count
VoLTE_IntraEnbSucc Successful intra handover execution count
VoLTE_InterX2OutAtt X2 handover attempt count
VoLTE_InterX2OutPrepSucc Successful X2 handover preparation count
VoLTE_InterX2OutSucc Successful X2 handover execution count
VoLTE_InterS1OutAtt S1 handover attempt count
VoLTE_InterS1OutPrepSucc Successful S1 handover preparation count
VoLTE_InterS1OutSucc Successful S1 handover execution count
VoLTE Ho Time VoLTE_IntraHoTime_Avg When Intra eNB Handover is completed, this statistic is
collected.
VoLTE_IntraHoTime_Min This counter is updated when
VoLTE_IntraHoTime_Avg is collected and it is low than
previous maximum value.
VoLTE_IntraHoTime_Max This counter is updated when
VoLTE_IntraHoTime_Avg is collected and it is greater
than previous maximum value.
VoLTE_IntraHoTime_Cnt This counter is cumulated when
VoLTE_IntraHoTime_Avg is collected
VoLTE_IntraHoTime_Tot This counter is cumulated when
VoLTE_IntraHoTime_Avg is collected
VoLTE_X2HoTime_Avg When X2 Handover is completed, this statistic is
collected.
VoLTE_X2HoTime_Min This counter is updated when VoLTE_X2HoTime_Avg
is collected and it is greater than previous maximum
value.
VoLTE_X2HoTime_Max This counter is cumulated when
VoLTE_X2HoTime_Avg is collected
VoLTE_X2HoTime_Cnt This counter is cumulated when
VoLTE_X2HoTime_Tot This counter is cumulated when
VoLTE_S1HoTime_Avg When S1 Handover is completed, this statistic is
collected.
VoLTE_S1HoTime_Min This counter is updated when VoLTE_S1HoTime_Avg
is collected and it is greater than previous maximum
Chapter 7 Services

Name
value.
VoLTE_S1HoTime_Max This counter is cumulated when
VoLTE_S1HoTime_Avg is collected
VoLTE_S1HoTime_Cnt This counter is cumulated when
VoLTE_S1HoTime_Tot This counter is cumulated when
VoLTE Quality VoLTE_DropRate The number of VoLTE Drop rate
VoLTE_UlQualityDefectRate The number of UL Quality Defect rate
VoLTE_DlQualityDefectRate The number of DL Quality Defect rate
VoLTE_IntraHoSuccessRate The number of VoLTE HO Intra Success rate
VoLTE_X2HoSuccessRate The number of VoLTE HO X2 Success rate
VoLTE_S1HoSuccessRate The number of VoLTE HO S1 Success rate
REFERENCE
N/A
Chapter 7 Services
LTE-SV0503, Multicell and Multicast

Coordination (MCE)
INTRODUCTION
Multicell and Multicast Coordination Entity (MCE) is an eMBMS entity that
controls eMBMS sessions requested by MME. Also, it allocates radio resources in
time domain and schedules eMBMS sessions. In addition, it aligns the opening of
eMBMS radio channel among cells that belong to the same MBSFN Area.
Samsung MCE is provided as an external server.
The advantages of centralized MCE architecture are as follows:
SCTP offloading from MME
eMBMS service restoration when eNB restarts or fails
Large MBSFN areas
MCE is an essential entity for eMBMS service. This feature covers following basic
and advanced MCE functions:
M2 and M3 interface
eMBMS session start and stop based on MBMS Service Area
1:1 Active and Standby redundancy
eMBMS session restoration when eNB restarts or fails
Inter-MCE scheduling coordination
Multiple PLMN supported for RAN sharing
In case of resource allocation and MBMS bearer scheduling, refer to LTE-SV0504
eMBMS Resource Allocation. In addition to MCE, eMBMS related network
entities include eNB, MME, MBMS GW, and BMSC in the mobile network.
BENEFIT
The operator can provide eMBMS service and increase radio resource utilization.
Wide MBSFN area is provided that minimizes eMBMS interference between
cells.
Continuous eMBMS service is provided even in case when eNB fails and restarts.
Resilient MCE system is provided by 1:1 active and standby redundancy
Chapter 7 Services

Dependency
MME that supports 3GPP Release 11 M3 interfaces
Samsung eNB that supports 3GPP Release 11 M2 interface
Release 9 and later UE that supports eMBMS
MBMS-GW and BMSC are required for eMBMS service
Limitation
256 MBSFN Areas
3000 eNBs and 9000 cells per MCE blade
Simultaneous session processing of 10 per 1 second
256 Sessions per MCE (One Blade)
Related Features
LTE-SV0501 eMBMS Basic Function
LTE-SV0504 eMBMS Resource Allocation
LTE-SV0511 eMBMS QoS
LTE-SV0513 eMBMS Service Continuity
LTE-SV0515 eMBMS Session Monitoring
FEATURE DESCRIPTION
M2 Interface Management
According to 3GPP TS36.443 V11.3.0, MCE and eNB setup M2 connection and
support following procedures.
M2 SETUP procedures to make M2 connection
M2 RESET procedures
ENB CONFIGURATION UPDATE procedures to update application level eNB
configuration data
MCE CONFIGURATION UPDATE procedures to update application level MCE
configuration data
ERROR INDICATION procedures
M3 Interface Management
According to 3GPP TS36.444 V11.6.0, MCE and MME setup M3 connection and
support following procedures.
M3 SETUP procedures to make M3 connection
Chapter 7 Services
M3 RESET procedures
MCE CONFIUGRATION UPDATE procedures to update application level MCE
configuration data
MCE can make multiple M3 connections with different MMEs.
MBMS Session Management

According to 3GPP TS36.443 V11.3.0 and 3GPP TS36.444 V11.6.0, MCE
supports MBMS session control functions.
MBMS SESSION START and STOP procedures initiated by MME
MBMS SESSION UPDATE procedure initiated by MME
On receiving M3 MBMS SESSION START message from MME, MCE sends M2
MBMS SESSION START message to eNBs that belong to MBSFN Areas that
support the MBMS Service Area ID, which is specified in the M3 MBMS
SESSION START message. MCE does not use PLMN ID of TMGI in the
message when it decides target eNBs or MBSFN Areas. This means that MBMS
SESSION START message can be sent to eNBs even though eNBs does not
support PLMN ID of TMGI in the message. If eNB does not support PLMN ID, it
should reject the session request. This is to support eMBMS service in RAN
sharing network.
The session duration parameter in MBMS SESSION START REQUEST message
decides the session duration. When it expires, MCE releases the MBMS Session
unless it is updated by MBMS SESSION UPDATE REQUEST message.
MCE Redundancy
Samsung MCE provides active and standby redundancy. When an active server
fails, the standby server takes over the role without any service impact. Following
figure shows an example configuration of MCE. Maximum 5 active and standby
pairs are equipped in a single chassis (HS23). Active and standby servers share the
same IP interface so that the active and standby architecture is transparent to eNB
or MME. Active server periodically backups data to standby server. When active
server fails (SW or HW fails or board reset), the standby server will take over the
role in a few seconds. After switchover, MCE makes SCTP setup with all of the
eNBs, and MCE also makes SCTP setup with MME. However, these switchover
procedures have no impact on ongoing eMBMS data sessions.
Chapter 7 Services
Inter-MCE Scheduling Coordination

When a big city or nation-wide area is covered by multiple MCEs, they need to
broadcast synchronized eMBMS data over the entire area. For example, there are
two MCEs that cover two disjoint areas respectively. Even though eNBs in two
disjoint areas broadcast the same eMBMS service, there could be severe
interference in the border area if they are not synchronized. The interference can
be removed if eNBs broadcast the same eMBMS data in the same physical
location of the frequency at the same time.
In case of inter-MCE scheduling coordination, the MCEs must be configured so
that they have the same MBMS Service Area ID with the same physical resource
configuration such as RFAP and RFAP offset. In addition, for the MBMS Service
Area, they shall receive eMBMS data from the same BMSC. In the figure below,
the first two MBSFN areas have the same MBMS Service Area and the same
physical resource allocation. The coordinated MBMS Service Area must span over
the same frequency and over eNBs that are SFN synchronized. MBSFN Area ID
and MBSFN Synchronization Area ID can be different between two MCEs while
MBMS Service Area and RFAP and RFAP Offset must be the same. The eNBs in
the MBMS Service Areas will be able to transmit synchronized eMBMS data for
the same eMBMS session. Each MCE may have its own MBMS Service Area
independently of the other MCEs (MBSFN Areas 2 to 256 in the example).
In case of MBMS Service Area that needs to be synchronized over multiple MCEs,
operator shall configure following system parameters the same over the MCEs.
MBMS Service Area ID
Chapter 7 Services
RFAP
RFAP Offset
MSP
MCS Level(Signalling and Data)
The number eMBMS sufbrames per radio frame
Configuration of MBSFN Areas that corresponds to the MBMS Service Area.
Refer to Information included in MBMS Scheduling Information(3GPP
TS36.443 V10.1.0 9.1.7)
Information included in MCCH related BCCH Configuration Item (3GPP
TS36.443 V10.1.0 9.2.1.13), excluding MBSFN Area ID and Cell Information
List.
In addition, following requirements must be met.
The MCEs shall be connected to the same BMSC.
The same MBMS Service Area must be configured over the same frequency, the
same PLMN
All eNBs in the same MBMS Service must be SFN synchronized.
The MBSFN Areas that serve the MBMS Service Area must not support other
MBMS Service Areas that cover local regions.
Following is overall procedures to apply the coordinated scheduling information to
MCEs and eNBs.
1 LSM shall provide coordinated scheduling information to the concerned MCEs
2 Upon receiving the M2 setup request from eNB, the MCE shall provide MCCH
configuration information for the cluster MBSFN area
3 Upon receiving the M2 setup response from MCE, eNB shall schedule MCCH
by given configurations
4 Upon receiving the M3 session start message for the specific MBMS service
area from MME, MCE shall schedule PMCH/MCH by the coordinated
scheduling information
5 Upon receiving the M2 MBMS SCHEDULING INFORMATION message for
the specific MBSFN area, eNB MAC shall schedule PMCH/MCH by the
given information
SYSTEM OPERATION
How to Activate
The relevant MCE PLD is set as follows:
CHG-MBMSENB-CONF: eNB-MCC/MNC, eNB IP address, and so on, eMBMS
status The indexes increases to 3000
Chapter 7 Services
CHG-MBSFN-MAPPINGINFO: Set the MBSFN area. (To set the MBSFN area,
set the MBMS Service Area Id and the MBMS Synchronisation Area Id.)
Key Parameters
CHG-MBMSENB-CONF/RTRV- MBMSENB-CONF
ENB_INDEX Index of eNB. The value entered when registering the MBMS eNB is used.
STATUS The validity of the MBMS eNB information.
ENB_MNC[4] The PLMN information (MCC) that represents the MBMS eNB. It is a three-digit
number with each digit being from 0 to 9.
ENB_MNC[4] The PLMN information (MNC) that represents the MBMS eNB. It is a three-digit
or two-digit number with each digit being from 0 to 9.
ENB_IP_V4 Enter the IP address of the MBMS eNB in the IP version 4 format.
ENB_IP_V6[16] Enter the IP address of the MBMS eNB in the IP version 6 format.
SECONDARY_ENB_IP_V4 Enter the secondary IP address of the MBMS eNB in the IP version 4 format.
SECONDARY_ENB_IP_V6[ Enter the secondary IP address of the MBMS eNB in the IP version 6 format.
16]
CHG-MBSFN-MAPPINGINFO/RTRV-MBSFN-MAPPINGINFO
MBSFN_AREA_ID Index for change and retrieve MBSFN area id.
STATUS Status of MBSFN Mapping Info
MBSFN_SYNC_AREA_ID MBSFN SYNC AREA ID
MBMS_SERVICE_AREA_ID MBSFN Service AREA ID
..[ ]
Counters and KPIs

MBMS_M2_SETUP: M2 SessionStart, SessionStop
MBMS_SESSION_SETUP: M3 SessionStart, SessionStop
Family Name Counter Name Description
MBMS_M2_SETUP M2ConnEstabAtt Count of M2 setup attempts transmitted by the
eNB
M2ConnEstabSucc Count of M2 setup successes transmitted by
the MCE
M2ConnEstabFail_M2AP_C M2 setup failure count. A failure is due to the
U_FAIL specified cause in specification.
M2ConnEstabFail_M2AP_LI M2 setup failure count. A failure is due to
NK_FAIL SCTP link failure.
SessionStartAtt Count of M2 MBMS session start request
attempts transmitted by MCE.
SessionStartSucc Count of M2 MBMS session start response
successes received by the MCE.
SessionStartFail_CP_CC_FA Count of Failure of 'M2 MBMS Session Start'.
The failure is caused by the MCE restart or
Chapter 7 Services

IL MCE disability.
SessionStartFail_CP_CAPA_ Count of Failure of 'M2 MBMS Session Start'
CAC_FAIL because of resource based CAC by MCE.
SessionStartFail_M2AP_CU_ Count of Failure of 'M2 MBMS Session Start'
FAIL because of the cause specified in TS36.443.
SessionStartFail_M2AP_LIN Count of Failure of 'M2 MBMS Session Start'
K_FAIL because of M2 SCTP Link failure.
SessionStopAtt Count of M2 MBMS session stop request
attempts transmitted by MCE.
SessionStopSucc Count of M2 MBMS session stop response
successes received by the MCE.
SessionStopFail_CP_CC_FA Count of Failure of 'M2 MBMS Session Stop'.
IL The failure is caused by the MCE restart or
MCE disability.
SessionStopFail_M2AP_LIN Count of Failure of 'M2 MBMS Session Stop'
SessionStartFail_M2_OTHE Count of Failure of 'M2 MBMS Session Stop'.
R_REASONS The failure is caused by an exceptional case
not specified above reason.
MBMS_SESSION_SETUP SessionStartAtt Count of 'M3 MBMS Session Start' received
by MCE
SessionStartSucc Count of 'M3 MBMS Session Start Response'
transmitted by MCE
SessionStartFail_CP_CAPA_ Count of Failure of 'M3 MBMS Session Start'
CAC_FAIL because of resource based CAC by MCE.
SessionStartFail_M3AP_CU_ Count of Failure of 'M3 MBMS Session Start'
FAIL because of the cause specified in TS36.444.
SessionStartFail_M3AP_LIN Count of Failure of 'M3 MBMS Session Start'
SessionStopAtt Count of 'M3 MBMS Session Stop' received by
MCE
SessionStopSucc Count of 'M3 MBMS Session Stop Response'
transmitted by MCE
SessionStopFail_CP_CC_FA Count of Failure of 'M3 MBMS Session Stop'.
IL The failure is caused by the MCE restart or
MCE disability.
SessionStopFail_M3AP_LIN Count of Failure of 'M3 MBMS Session Stop'
REFERENCE
N/A
Chapter 7 Services
LTE-SV0504, eMBMS Resource Allocation

INTRODUCTION
MCE performs an eMBMS scheduler role allocating eMBMS radio resource to
each MBMS session. The eMBMS scheduling is performed for each MBSFN area.
The eNB transmits eMBMS data according to the scheduling information provided
by MCE. In addition, MCE performs MBMS session admission control
functionality, where MCE checks the capacity of MBSFN area, MCE, eNB, and
cell to decide whether it accepts the call or not. In addition, MCE maintains
allocated resources and makes an admission decision based on GBR requested in
MBMS Session Start Request from BMSC.
BENEFIT
This feature facilitates efficient radio resource allocation with the statistical
multiplexing of the logical channels into a given physical subframe.

Dependency
UE should support eMBMS service.
eNB and MCE are required to support eMBMS service.
Limitation
Up to 15 PMCHs can be supported in one MBSFN Area
Up to 256 MBSFN Areas
FEATURE DESCRIPTION
eMBMS Channels
The channels used in LTE eMBMS are largely classified into a logical channel, a
transport channel, and a physical channel and they are mapped with each channel
as shown below:
Logical channel: MCCH, MTCH
Transport channel: MCH
Physical channel: PMCH
Chapter 7 Services
eMBMS Radio Resource Allocation

The allocation of the resource of MBMS consists of largely common subframe
allocation, session admission control, and MCH scheduling part including MTCH
multiplexing part.
Below is the procedure flow explaining the resource allocation in the MCE. In the
following flow, Step 1 corresponds to the common subframe allocation while
Steps 2 and 3 the session administration control for PMCH and MTCH,
respectively:
The common subframe allocation and the session admission are the unique
functions of the MCE and MTCH multiplexing and MCH scheduling are the
functions of the eNB MAC scheduler, which are not included in the procedure
flow. (The step 1 in below figure assumed MTCH multiplexing feature not
currently supported)
Chapter 7 Services
The MCE performs resource allocation based on the existing MBSFN area, PMCH,
MTCH, and more after receiving the MBMS session start request message from
the BMSC. If the resource allocated for eMBMS is not sufficient, MCE transmits
MBMS session start failure message to MME.
In Step 0, MCE selects on which MBSFN area a new channel will be added based
on the service ID included to MBMS session start request message. Depending on
the service, channels may be added to multiple MBSFN areas.
Step 1 is calculating the number of all physical radio frames available in CSAP in
the MBSFN areas decided in Step 0
Calculates the data rate encoded to the signaling MCS required for PMCH
Calculates the number of all subframes to be encoded only with the data MCS
excluding the data volume encoded to MCS
Calculates the estimated radio resource volume required by a new channel by
referring to RLC header and MCS level applied to QCI in addition to GBR
required by the new channel.
Chapter 7 Services
Step 2 is deciding a PMCH. By considering the QCI information, the PMCH

supporting the QCI as same as the requested session is decided and if there is no
PMCH in the same QCI, a new PMCH is created.
Check whether the GBR required by a new channel may be satisfied in
consideration of the resource volume used by the PMCH. (If the remaining
capacity in the existing PMCH is enough, MTCH may be simply added.)
If there is a conventional PMCH supporting the same QCI but the capacity is not
sufficient, allocate a new MTCH by adding eMBMS subframe to the existing
PMCH after increasing capacity of PMCH in a method for changing the interval. If
PMCH configuration is changed, no influence over the conventional session must
exist and if there is any overlapped MBSFN area, the conflict with their PMCHs
must not occur.
In Step 3, to add a new channel (MTCH) to the selected MBSFN area, if the
session required by a new channel exceeds the maximum number of MTCHs, the
session is rejected.
By referring to the radio resource allocated to use for eMBMS, do not use more
than the number. If the resource is insufficient, reject the request. The resource
available by eMBMS is set by the administrator.
In case of precise resource allocation computation, beginning of this release the
resource allocation computation take into account of the MAC/RLC overhead.
SYSTEM OPERATION
How to Activate
This feature is enabled when eNB and MCE support eMBMS service.
Resource is allocated according to the PLD of REL_MBMS_SCHEDULING_INFO.
Some parameters can be changed by executing the CHG-MBMSSCH-INF
command.
However, it is desirable to change such PLD values after fully being aware of the
role of each parameter.
For example, CSAP, RFAP, and offset are connected with one another and if the
overlapped MBSFN area is allowed, it will follow the eMBMS Radio Resource
Algorithm.
Therefore, PLD provides only the function of reading set values - according to the
algorithm - instead of settable values.
Only for the session whose QCI has the same value, multiplexing MTCH to
PMCH is possible.
Also, refer to the feature eMBMS QoS for data MCS mapping depending on QCI.
Multiple MBSFN functions as functions of supporting up to 8 MBSFN areas in a
cell may configure PLDEnbMbsfnAreaInfo per MBSFN area of a cell.
Chapter 7 Services
In addition, MCE may be configurable to allow the cell to operate as MBSFN

reserved cell for a specific MBSFN area, and this may be configurable through
CHG-MBMS-CELLINFO.
Key Parameters
The following parameters are related to eMBMS resource allocation:
Parameters Description
MBSFN_AREA_ID mbsfnAreaId for change and retrieve
STATUS Status of MBMS Scheduling Info
SUBFRAME_ALLOC_TYPE Subframe Allocation Type
MAX_SUBFRAME_NUM Max Subframe Number
MCH_SCHEDULING_PERIOD MCH Scheduling Period
CSAP Common Subframe Allocation Period
RFAP Radio Frame Allocation Period
OFFSET Radio Frame Allocation Offset
Counters and KPI

REFERENCE
N/A
Chapter 7 Services
LTE-SV0514, Adaptive Delay Reduction for

eMBMS
INTRODUCTION
Due to MCCH modification period, for example 512 ms or 1024 ms, defined in the
3GPP standard, data transmission of an MBMS session can be delayed at random
longer than 5.12 second. This delay occurs in eMBMS sessions only because
eMBMS data transmission needs to be synchronized among eNBs unlike unicast
traffic. This delay results in poor Quality of Experience of eMBMS UEs because
there is a large time gap between video on device and live scene in the stadium. In
case of PTT over eMBMS, unbearable delay from mouth to ear may occur.
This feature reduces the delay by discarding data packets buffered at eNBs, which
results in pulling up the time from the perspective of UE. This feature can be
enabled for live broadcasting or PTT over eMBMS.
BENEFIT
In live broadcasting service, the time gap between the video played in device and
the live scene in the stadium is eliminated and the UE can watch the
synchronized video in the stadium.
In voice service such as Push-To-Talk, the voice messages can be delivered
without unnecessary delay at eNB.

Dependency
This feature can be enabled in Samsung MCE and eNB.
Limitation
Note that If MCE does not get DELAY INFORMATION from an eNB that is
located farthest away from BMSC then the eNB might not transmit MBMS
data for the delay reduction session due to the excessive time shifting.
Note that eNB might not transmit MBMS data that arrives at eNB too late.
Time shift can occur only when the synchronization sequence length of session is
less than 1.5 seconds. Otherwise, eNB discards MBMS packets during the first
5 seconds but MCE and eNB cannot reduce the delay due to the insufficient
synchronization sequence learning time.
Adaptive Delay Reduction (ADR) feature must be enabled when all the eNBs
connected to the MCE supports ADR feature.
Chapter 7 Services
There can be eMBMS interference in border area when two or more MCEs setup
ADR session for the same eMBMS session, even though they coordinate
resource allocation through LSM, such as RFAP.
FEATURE DESCRIPTION
Basic Concept
When MBMS session is started, BMSC transmits MBMS data unit periodically
according to specified synchronization sequence. If the data to be transmitted does
not exist, since void packet, without user data, along with timestamp are
transmitted, eNB could receive timestamp increasing packet successively. eNB
transmits packet at the calculated time according to timestamp + offset base. If the
packet is empty, data will not be transmitted for the corresponding time period.
Therefore, from the moment of first timestamp binding to corresponding SFN, all
the packets in the session will have same delay until the end of the session.
During packet transmission in the session, to prevent delay, eNB will discard
buffered packets and will transmit recently arrived packet. This is similar to
eliminating front of movie film, to make earlier showing time. All eNB must be
synchronized between transmitting data, so MCE makes decision of the moment of
packet discard, the moment of packet transmission starting and send notice to all
broadcasting target eNBs.
Adaptive Delay Reduction function is performed through gap control between
SFN (eNB transmits according to SFN) and timestamp, which is specified in the
MBMS data packet. For example, as seen in the figure below, if the offset value is
512, then arrived packet (with timestamp value = 6) near SFN=512 will be
transmitted on SFN=518. Then 60 ms packet delay happens. If the offset value is
changed to 508, the packet (with timestamp=6) will be transmitted on SFN=514.
As a result, delays can be reduced by 40 ms.
Call procedure between eNB, MCE, BMSC are as follows: Steps 4)~5) is executed
for the MBMS session configured as
Minimum_Time_To_MBMS_Data_Tansfer=0.
Chapter 7 Services
BMSC Functionality
BMSC transmits MBMS data after SESSION START message transmission to
MCE after the time specified on Minimum_Time_to_MBMS_Data_Transfer.
During Minimum_Time_to_MBMS_Data_Transfer time, all eNBs belonging to
MBMS Service Area perform session configuration, radio resource configuration,
multicast joining to prepare MBMS data transmission.
For Adaptive Delay Reduction feature, BMSC needs to provide following
functions.
When transmitting SESSION START message, BMSC sets up
Time_to_MBMS_Data_Transfer = 0 for the live streaming session in order
to minimize the delay. Then, after sending SESSION START, BMSC
transmits MBMS data packet or empty packet (Type 0).
Synchronization Sequence Length of session, subject to delay reduction, must be
less than 1.5 second. If Synchronization Sequence Length is greater than 1.5
second, the value of Minimum_Time_to_MBMS_Data_Transfer must not
set as zero. If this session is assigned as the session subject to delay
reduction, even though initially transmitted MBMS packet will be lost, time is
not shifted.
MBMS data sent during initial session will be lost when time is shifted. This loss
will occur for approximately 5 seconds, until MCE completes the delay reduction
procedure following the start message transmission. The packets received by eNB
after that will not be lost due to time shift function. However, packets arriving late
by backhaul network delay will be discarded according to normal eMBMS
operation.
Chapter 7 Services
MCE Functionality
MCE performs Adaptive Delay Reduction function for the session configured as
Time_to_MBMS_Data_Transfer = 0. After receiving SESSION START
REQUEST message from MME, the procedures of SESSION START REQUEST
and SCHEDULING INFORMATION message transmission to the target eNB will
be performed the same way as for normal eMBMS session.
For the Adaptive Delay Reduction enabled session, the eNB will be notified that
the corresponding session is delay reduction session through SESSION START
message. Afterwards, based on received DELAY TIME INFORMATION
(SessionID, Offset, and Synchronization Sequence Length) from each eNB, MCE
detects eNB which was most delayed receiving MBMS data, and time shift value
is determined according to the late eNB. MCE transmits the final offset value to all
eNBs to make time shift.
Time shift is applied the same way even when eNB is restarted.
eNB Functionality
For the delay reduction function enabled session, the eNB will discard MBMS data
upon receiving SESSION START REQUEST message until receiving TIME
SHIFT REQUEST. The synchronization sequence length can be acquired through
synchronization sequence learning for the corresponding session. eNB transmits
the value of synchronization sequence length, the value of SFN (Offset) when
zero timestamp received and Session ID (MCE-MBMS-M2AP-ID) to MCE
through the DELAY TIME INFORMATION message.
When eNB receives TIME SHIFT REQUEST message, eNB modifies timestamp
of each packets to make radio transmission time shift.
SYSTEM OPERATION
How to Activate
Execute the command CHG-MBMSDELAY-INF to configure
'ADAPTIVE_DELAY_REDUCTION_USE' as to 'On' or 'Off'.
Execute the command RTRV-MBMSDELAY-INF to retrieve the existing
configuration settings.
Key Parameters
There are no prerequisite parameters except activating/deactivating parameters for
this feature.
CHG-ENBPDCP-INF/RTRV-ENBPDCP-INF
DB_INDEX index of this tuple
ADAPTIVE_DELAY_REDUC This parameter represents On/Off of the Adaptive Delay Reduction functionality.
Chapter 7 Services
TION_USE
Counters and KPIs

Family Name 'MBMS_ENB_SYNC' has two counters related to this feature (LTE-
SV0514).
Family Display name Type Description
DroppedSyncPduCount_ADR Integer The cumulated number of SYNC PDU discarded by
Range:0~2147483647 the Adaptive Delay Reduction functionality.
DroppedSyncPduByte_ADR Integer The cumulated bytes of SYNC PDU discarded by the
Range:0~2147483647 Adaptive Delay Reduction functionality.
REFERENCE
N/A
Chapter 7 Services
LTE-SV0515, eMBMS Session Monitoring

INTRODUCTION
Unlike unicast sessions, a MBMS session must be kept very long time period, and
there is no feedback from UEs whether they receives MBMS data successfully or
not. Therefore, a service monitoring tool is required for operator to monitor
whether MBMS data is normally broadcast or not.
In this feature, operator can monitor each session based on TMGI. Provided
information includes the total number of transmitted and received packets,
discarded packets, delayed packets, radio usage rate, and a plurality of
configuration information. The operator can check each cell and eNB whether they
normally provide eMBMS service or not.
Due to hardware resource limitation, LSM provides a limited number of sessions
that operator can monitor at the same time.
BENEFIT
The operator can monitor eMBMS session and check the status and quality of
eMBMS service.

Dependency
This feature can be enabled with Samsung eNB, MCE, and LSM.
Limitation
The operator can monitor up to 20 sessions at the same time. However, a cell
provides the session monitoring information of up to 16 sessions.
The information is updated every 2.56 seconds
Even in case of the same session, the displayed information may be different at a
monitoring moment between different cells or between eNB and MBMS-
GW/BMSC because of different delays between them. In addition, statistics
from RLC and GTP layers cannot be exactly matched at a specific moment
because of packets in traversal or different time sources used.
Chapter 7 Services
FEATURE DESCRIPTION
A. eMBMS Session Monitoring

This feature checks service quality and normality of the service operation status
for each session from BMSC that transmits eMBMS data to eNB that broadcasts
eMBMS data via MBMS GW.
The operator can check the information listed on the table below by selecting a
specific cell and session (TMGI) through LSM. Also, they can check the
information for up to 20 cells or 20 sessions at the same time. The corresponding
information is automatically updated in every 2.56 seconds. When a session that
meets the condition is created, the information is automatically displayed on the
window.
Input: List of ECGI, List of TMGI
Output: Listed below the information table
The following information is provided per Cell: TMGI.
Number Items Level Description Collection Entity
1 Start Time Per TMGI The time that eNB has opened MTCH Call Controller
channel of the session (TMGI) (eNB)
2 MBSFN Per TMGI MBSFN synchronization area ID of the Call Controller
Synchronization Area ID specified cell (eNB)
3 MBMS Service Area ID Per TMGI MBMS service area ID of the specified Call Controller
TMGI (eNB)
4 MBSFN Area ID Per TMGI MBSFN area ID of the specified cell Call Controller
(eNB)
5 PMCH Per TMGI PMCH ID that corresponds to the Call Controller
specified TMGI (eNB)
6 MTCH Per TMGI MTCH ID that corresponds to the Call Controller
specified TMGI (eNB)
7 Data MCS Level Per TMGI Data MCS level of the PMCH where Call Controller
the specified TMGI belongs to (eNB)
8 Singnalling MCS Level Per TMGI Signaling MCS level of the PMCH Call Controller
where the specified TMGI belongs to (eNB)
9 RX Packets (Type 0) Per TMGI The total number of Type 0 packets SYNC Handler
that eNB has received from MBMS (eNB)
after a session started of the specified
TMGI
TMGI
TMGI
12 TX Packets Per TMGI The total number of packets that SYNC SYNC Handler
Handler has transmitted to each cell of (eNB)
the corresponding eNB after a session
started of the specified TMGI
Chapter 7 Services

13 Discarded Packets Per TMGI The total number of packets including SYNC Handler
(Empty) summary packet that have been (eNB)
discarded by SYNC Handler, after a
session started of the specified TMGI
14 Discarded Packets Per TMGI The total number of the discarded SYNC Handler
(Lost) packets due to some packets that has (eNB)
not been received among the packets
that SYNC Handler has received within
the synchronization sequence after a
15 Discarded Packets Per TMGI The total number of packets that have SYNC Handler
(Others) been discarded by SYNC Handler for (eNB)
reasons other than empty and lost after
a session started of the specified
TMGI. For instance, when Multicast
packets are received while the RLC is
not ready.
16 RX SSEQ Per TMGI The total number of synchronization SYNC Handler
sequences that SYNC Handler has (eNB)
received after a session started of the
specified TMGI
17 TX SSEQ Per TMGI The total number of synchronization SYNC Handler
sequences that SYNC Handler has (eNB)
transmitted to each cell after a session
18 Discarded SSEQ Per TMGI The total number of synchronization SYNC Handler
sequences that have been discarded (eNB)
by SYNC Handler after a session
19 Delayed RX SSEQ Per TMGI After a session started of the specified SYNC Handler
TMGI, the packets that belong to the (eNB)
next synchronization sequence will be
received. The total numbers of
synchronization sequences that have
been transmitted to each cell after all
delayed packets of the previous
synchronization sequence are
received.
20 RX Packets (RLC) Per TMGI The total number of packets that RLC RLC(eNB)
has received after a session started of
the specified TMGI
21 TX Packets (RLC) Per TMGI The total number of packets that have RLC(eNB)
been transmitted by RLC after a
22 Control Packets Per TMGI The total number of packets that have RLC(eNB)
been discarded in RLC due to no
payload, after a session started of the
specified TMGI. For example, Type0 or
Type3 packets.
23 Discarded Packets Per TMGI The total number of packets that have RLC(eNB)
(Late Arrival) been discarded in RLC due to late
arrival after a session started of the
specified TMGI (Control packets
excluded)
23-1 Discarded Packets Per TMGI The number of packets that have been RLC(eNB)
Chapter 7 Services

(Insufficient Radio discarded without being transmitted
Resource) due to the lack of radio resources for a
session of the specified TMGI.
24 Discarded Packets Per TMGI The total number of packets that have RLC(eNB)
(Others) been discarded in RLC for the reasons
other than empty, late arrival, lack of
radio resources after a session started
of the specified TMGI. (Control packets
excluded)
25 Throughput Per TMGI Calculates the throughput by counting RLC(eNB)
(Total Bytes x 8/Period) the total bytes that have been
transmitted from RLC for the Period
(collecting period: 2.56 seconds). The
unit is Kbps.
26 Buffer Usage Per Cell The entire buffer usage for eMBMS in a RLC(eNB)
specified cell at the moment of
collecting statistic information
Number of Occupied Buffers/Total
Buffers x 100
27 PRB Usage Per The amount of PRB usage used in MAC(eNB)
PMCH PMCH among the total radio resources
assigned to PMCH, where TMGI
belongs to the statistics information
during collecting period
Number of PRBs used for the
PMCH/Number of PRBs Configured for
the PMCH
B. eMBMS Session Summary Log

If an eMBMS session is terminated normally or abnormally, eNB collects
information for the session from each cell and transmits it to LSM. The LSM saves
this information for a certain period of time and discard it automatically. If traffic
volume is too large between eNB and LSM, the operator can remove the normal
termination cases.
eMBMS Session Summary Log information includes all the counting information
for eMBMS Session Monitoring on the above tables and the following information
is collected additionally.
eMBMS session can last up to 19 days according to its standard. However, eNB
closes the Session Summary Log periodically and reports it to LSM.
1~27 Refer to 1~27 in A. eMBMS Session -
Monitoring
28 End Time Per TMGI Session Stop Time of the Specified TMGI Call Controller
(eNB)
C. eMBMS Service Status Report

The operator can identify the current eMBMS service area through LSM.
Chapter 7 Services
The operator can check MBSFN area list that supports each MBMS service area
and they can retrieve the following information of each MBSFN area.
Input: MCE, MBSFN Area ID
Output: Refer to the following table
The following information is provided per MBSFN area.
Number Items Level Description Collection
Entity
1 Total Number of Per MBSFN The total number of eNBs registered to MCE
eMBMS eNBs Area MCE through M2 Setup among the eNBs
included in MBSFN area of the specified
MCE.
2 Total Number of Per MBSFN The total number of cells that were set to MCE
eMBMS Cells Aera provide eMBMS service to eNB through
M2 Setup Response among the eNBs
MCE.
3 Total Number of Per MBSFN The total number of cells that were MCE
Reserved Cells Area notified as reserved cells to eNB through
M2 Setup Response among the eNBs
MCE.
4 Subframe Per MBSFN Subframes that were set for eMBMS in MCE
Allocation Area MBSFN area of the specified MCE (SIB2
information).
5 RFAP Per MBSFN Radio Frame Allocation Pattern that was MCE
Area set for eMBMS in MBSFN area of the
specified MCE.
6 Number of PMCHs Per MBSFN The total number of the PMCHs that is MCE
Area providing service in MBSFN area (Up to
15).
7 PMCH Resources Per PMCH, Resources assigned to the PMCH among MCE
Per MBSFN the eMBMS Subframe resources
Area assigned to MBSFN area
8 Number of MTCHs Per PMCH, The total number of MTCHs provided in MCE
Per MBSFN MBSFN area per PMCH.
Area
SYSTEM OPERATION
How to Activate
Execute the RTRV-SSL-CTRL command to retrieve the existing configuration
settings for Session Summary Log (SSL).
Execute the CHG-SSL-CTRL command to configure the settings for Session
Summary Log (SSL).
Execute the RTRV-MCERSC-STS command to retrieve the resource status of
Multi-cell/multicast Coordination Entity (MCE).
Chapter 7 Services
Key Parameters
CHG-SSL-CTRL/RTRV-SSL-CTRL
DB_INDEX Index of this relation
MBMS_SSL_CREATE_CONDITION Deciding value how to apply Session Summary Log(SSL)
RTRV-MCERSC-STS
MBSFN_AREA_ID Index of Multimedia Broadcast Single Frequency Network or Multicast
Broadcast Single Frequency Network (MBSFN) area.
TOT_ENBS Total number of eNBs that have connected with MCE through M2 interface.
TOT_CELLS Total number of eMBMS service cells that have connected with MCE through
M2 interface except reserved cell.
TOT_REV_CELLS Total number of reserved cells that have still connected with MCE through M2
interface in MBSFN area.
RFAP Radio frame allocation period for MBSFN area.
SUBFRAME_ALLOC[12] MBSFN subframe configuration (subframe allocation: one frame item) in SIB2.
NUM_PMCH Total number of Physical Multicast Channels (PMCHs) allocated for eMBMS.
SF_ALLOC_END Ratio of the subframe resources allocated by MBSFN area and used actually in
PMCH.
N_MTCH_P0 Total number of MTCHs per 0-th PMCH provided by MBSFN area.
N_MTCH_P14 Total number of MTCHs per 14-th PMCH provided by MBSFN area.
Counters and KPIs

REFERENCE
N/A
Chapter 7 Services
LTE-SV0517, eMBMS Service Restoration

INTRODUCTION
eMBMS service restoration is to recover eMBMS sessions when eNB or MCE or
MME fails. When MME fails, eMBMS session context will move to another
MME. The MCE shall be able to re-associate the existing eMBMS sessions with
the new MME that requests MBMS Session Start Request message with 'Re-
establishment Indication' flag. When MCE restarts, it will perform M3 Setup and
send M3 Reset message to MME. The MME will send original eMBMS Session
Start message to recover the sessions.
In case of M3 link failure, MCE deletes all the related eMBMS sessions and tries
to make M3 Setup repeatedly. Once the M3 setup is completed, MCE will send
M3 Reset message to MME.
MCE can be connected to multiple MMEs (up to 16). However, MCE expects that
the same MME controls the same MBMS sessions, which means that the MCE
rejects any duplicate MBMS Session Start Request message from other MME
without 'Re-establishment Indication' flag.
BENEFIT
This feature enables MBMS service to continue even in case of MME failure, or
MCE failure, or M3 path failure.

Dependency
MME that support 3GPP Rel-12
Limitation
Max 16 MMEs supported
FEATURE DESCRIPTION
eMBMS Service Restoration When eNB Fails

The MCE shall not delete MBMS session information in the event of STCP keep
alive message failure. When eNB reboots, MCE transmits all the MBMS session
information as soon as eNB and MCE setup M2 connection. Sine eNBs in the
same MBSFN area including the rebooted eNB use the synchronized SFN and the
same timestamp offset value for each MBMS session, the rebooted eNB can keep
the restored MBMS sessions synchronized with neighbor eNBs.
The following figure shows eNB failure case of the centralized MCE:
Chapter 7 Services
From eNB's respect, it shall be treated as normal M2 setup, since it cannot

differentiate from normal start to recovered session. MCE shall not flag any non-
standard information to eNB.
MME Restoration Support

The MME requests eMBMS Session Start Request message, and eMBMS session
is associated with MME. In case of MME failure, another MME can send eMBMS
Session Start Request message with 'Session Re-establishment Indication' flag
when the primary MME fails. Then, MCE will re-associate eMBMS Session to the
secondary MME that requests session re-establishment.
Chapter 7 Services
The MBMS Session Start Request message with 'Re-establishment indication' flag
may differ from the existing one. In this case, MCE shall send MBMS Session
Update message to all eNBs of the corresponding MBMS Service Area.
MCE Restoration
When MCE restarts or it detects a failure in M3 link, it will make M3 setup and
sends M3 Reset message to MME. Then, MME will send MBMS Session Start
message to MCE.
In case of M3 link failure, MCE will release all eMBMS sessions that it has
managed.
SYSTEM OPERATION
How to Activate
Dependency with other feature, limitation and prerequisite: RTRV-MCECONN-
PARA/CHG-MCECONN-PARA :: MME_FAILOVER_TIMER.
Key Parameters
Counters and KPIs

eMBMS MCE session-related statistics have the following items (The operator can
retrieve them by MME index.).
Chapter 7 Services
Node restoration-related parts cannot be checked but operator can observe that the
MBMS_SESSION_SETUP statistics of the other MME index are increasing.
MBMS_SESSION_SETUP: SessionStartAtt, SessionStartSucc, and so on.
MBMS_SESSION_SETUP SessionStartAtt Count of M3 Session Start attempts
transmitted by MME
SessionStartSucc Count of M3 Session Start successes
transmitted by MCE
SessionStartFail_CP_CAPA_CAC_F M3 Session Start failure count. A
AIL failure is due to the CAC by MCE.
SessionStartFail_M3AP_CU_FAIL M3 Session Start failure count. A
failure is due to the specified cause in
specification TS36.444.
SessionStartFail_M3AP_LINK_FAIL M3 Session Start failure count. A
failure is due to SCTP link failure.
SessionStopAtt Count of M3 MBMS Session Stop
received by the MCE.
SessionStopSucc Count of M3 MBMS Session Stop
successes transmitted by MCE.
SessionStopFail_CP_CC_FAIL Count of Failure of 'M3 MBMS Session
Stop' This failure is due to reception of
RESET during 'Session Strop'
procedure or block restart and so on.
SessionStopFail_M3AP_LINK_FAIL Count of Failure of 'M3 MBMS Session
Stop' This failure is due to SCTP link
failure.
REFERENCE
[1] 3GPP TS23.007
Chapter 7 Services
LTE-SV1100, TCP Optimization

INTRODUCTION
TCP optimization feature is introduced to reduce the congestion occurring at eNB.
The TCP optimization feature provides PDCP PDU discard functionality at eNB in
Downlink as per QCI level. By discarding downlink packets at eNB, based on the
discard timer timeout, the TCP optimization feature provides an active queue
management function which may accelerate the congestion detection and control
mechanism at TCP senders during the time of congestion at eNB.
The backhaul data rate is high whereas the air interface throughput is very low
(that is, air interface throughput is low due to bad RF conditions and high BLER
rate) of the users. In such a scenario, packets are not getting scheduled at the rate
they are arriving. As a consequence of delayed scheduling, the effects are seen as
high TCP RTT latencies and higher than normal Packet Delay statistics. This
would cause high congestion at eNBs and result in in situations like the TCP
sender doing a retransmission (due to timeout) of a packet which was not even
transmitted on air.
Chapter 7 Services
By discarding downlink packets at eNB whose discard timer has expired there are
two advantages.
1 By dropping all the packets which are, in a sense, expired downlink packets for
that QCI. Also by discarding older data packets at eNB, operator can control
what to drop rather than blindly dropping all incoming packets in case of a full
buffer.
2 By dropping aged downlink packets at eNB for non GBR bearers, there is a
possibility of detecting congestion earlier than dropping incoming new packets.
By detecting congestion the TCP senders adapt their sending rate, thereby
controlling congestion.
BENEFIT
The operator can prevent long queuing delay at eNB.
Users can experience improved end-user performance in terms of reduced TCP
round-trip time in congestion situation.

N/A
FEATURE DESCRIPTION
The TCP optimization is implemented for Acknowledged Mode Data (AMD) PDU
in PDCP/RLC layer of eNB. The eNB monitors age of the queued up packets.
When age of a packet exceeds the discard timer value, then such a packet is
discarded.
If the value of discard timer value is Infinity for QCI, packet discard operation
does not occur for that QCI.
If the discard timer value is set to a non-Infinity value, packets that are older than
discard timer will be discarded. The unit of the discard timer is in milliseconds.
Effect on TCP Congestion Control due to DISCARD TIMER timeout:
After the downlink packets are discarded at eNB, at the affected TCP sender (s),
the congestion window will be reduced.
Chapter 7 Services
The TCP application can detect packet loss and adapt its data rate to the available
rate.
If a packet is discarded at eNB, it becomes a signal of light congestion for the
TCP sender
If there are many packet discarded at the eNB, it is a signal of serious congestion.
The congestion window is reduced when a missing packet(s) is detected, thereby
adapting the available rate by reducing the congestion window size.
In case of more information on Congestion Control at TCP, refer to TCP
Congestion Control RFC 2581 and RFC 5681
SYSTEM OPERATION
How to Activate
Execute the CHG-PDCP-INF command to configure discard timer.
Execute the RTRV-PDCP-INF command to retrieve the existing configuration
settings.
Key Parameters
The existing CHG-PDCP-INF command will be used
DISCARD_TIMER The parameter is a queue management parameter which indicates the maximum age
a packet can be held in the RLC queues at per QCI level.
Packets older than DISCARD_TIMER will be discarded at the RLC
Counters and KPIs

DL PDCP PDU PdcpPduDiscardRateDL Discard rate of PDCP PDUs
discard rate This counter displays the ratio of packets that are
Chapter 7 Services

discarded due to DISCARD_TIMER_DL expiry and the
total packets in the buffer over a period of 10seconds. The
units are in ppm (x 10^6).
REFERENCE
[1] 3GPP TS 36.323 'Packet Data Convergence Protocol (PDCP) specification'
Chapter 8 RAN Sharing
LTE-SW5001, Multi-PLMN Support

INTRODUCTION
Multiple-PLMN support allows provide LTE service to subscribers of multiple
operators in a cell concurrently.
For Multiple-PLMN support, eNB broadcasts multiple PLMN IDs which are
sharing a cell in system information and supports UE associated signaling with a
UE and an appropriated core network based on the PLMN which UE has selected.
In RAN sharing, operators have their own dedicated carrier. The Multi-PLMN
Support feature allows serving only one available PLMN ID to the subscribers of
the dedicated carrier. The PLMN ID served in the cell is either primary or
secondary PLMN, which depends on operator's ownership of the dedicated carrier.
The primary PLMN ID is included in the broadcasted PLMN list to support
successful ANR operation. It is marked as reserved for operator use to avoid
access from primary PLMN subscribers when the carrier is only available for
secondary PLMN.
The Multiple Operator Core Network (MOCN) has the RAN structure where
multiple partner operators share one spectrum. Whereas, in MORAN structure,
each partner operator uses dedicated frequency, however, shares same eNB. In
general, one host operator manages the RAN in the MOCN or MORAN structure,
and other partner operators provide services for users through the RAN. The host
operator can check the data usage through the statistical information. However,
partner operators cannot access this data without host operator's help.
This feature provides a function to collect data usage by PLMN ID in the eNB for
each partner operator. The collected data is transmitted to the LSM. The provider
can check the data used by the partner operators.
BENEFIT
Multiple operators can share eNB in MORAN architecture.
Operator can reduce CAPEX and OPEX by sharing site, eNB and backhaul
network with partners.
Host operator can figure out how much data is consumed by each partner
operator.
The data usage can be utilized for the purpose of settlement among partner
operators.

Dependency
Required Network Elements: For usage reporting function, in addition to eNB,
the LSM should support this feature.
Related Radio Technology: E-UTRAN (LTE)
Others: Each partner operator must have their own dedicated carrier for Multiple
Operator Radio Access Network (MORAN).
Limitation
The feature supports a maximum of six dedicated carriers per eNB.
FEATURE DESCRIPTION
The eNB provides the following functions for this feature:
Broadcast multiple PLMN IDs, up to six, in SIB.
Routing of signaling for call control based on the selected PLMN ID by UE.
Inter-PLMN handover support in shared network.
Radio resource sharing in shared cell.
In a shared cell, the eNB broadcasts the supporting PLMN ID list, up to six,
through SIB1. The first PLMN ID broadcasted to SIB 1 must be set to the same as
the PLMN ID of the global eNB ID. The first listed PLMN must be the same as
the primary PLMN of eNB. The supporting PLMN ID list per cell is configured by
the system parameter. The UE reads the PLMN IDs, and selects one based on its
selection process.
When the UE is expected to make RRC connection with eNB, the selected PLMN
ID is included in the RRC Connection Setup Complete message. The eNB uses
this PLMN ID to select the core network, and to transfer the Initial UE message.
Figure below depicts the signaling procedures of eNB.
Multiple Operator Support with Dedicated Carriers

In MORAN architecture, operators do not have to share spectrum. One possible
scenario is that operators have its own dedicated carrier and do not share with
others. The Multi-PLMN Support feature enable operator to share eNB with its
own dedicated carrier.
Figure below shows an eNB sharing scenario with dedicated carrier between
operator A and B. While the operator A is the owner or manager of the shared eNB
and the operator B shares the eNB with a dedicated carrier. In the dedicated carrier
cells of each operator, only one PLMN ID is available, which provide services to
the subscribers of the carrier owner.
Definitions used to describe the relation between PLMN ID and the dedicated
carrier owner.
Owner PLMN: The operators PLMN ID that is the eNB owner or manager of the
eNB.
Sharing PLNM: The operators PLMN ID that shares eNB with a dedicated
carrier with eNB owner operator.
The rules for PLMN broadcasting in the dedicated carrier cells are as follows:
In the dedicated carrier cells of eNB owner or manager:
oOnly PLMN ID of owner PLMN is broadcasted in SIB1 as the primary
PLMN.
In the dedicated carrier cells that shares eNB with owner operator:
oTwo PLMN IDs shall be broadcasted in SIB1 (owner PLMN + sharing
PLMN). Owner PLMN ID shall be the primary PLMN and sharing PLMN
ID shall be the secondary PLMN.
oOwner PLMN, that is primary PLMN in SIB1, shall set to 'reserved for
operator' to prevent provide services to owner PLMNs subscribers in
sharing PLMN operators dedicated carrier.
The reason for including PLMN ID of owner PLMN in sharing PLMN carrier is to
enable SON related operation, for example ANR, and packets forwarding issue in
the shared eNB.
This feature supports up to 6 operators dedicated carriers MOCN sharing operation.
Network Management for RAN Sharing

In the RAN sharing structure, such as MOCN or MORAN, the host operator is
responsible for RAN management. The host operator manages the fault,
configuration, administration, performance, and statistics of the RAN shared with
partner operators through the LSM. The partner operators control the RAN
through the host operator rather than changing the system parameter by directly
accessing to the RAN.
The statistical information is stored periodically in the LSM and managed by the
PLMN ID. Through the north bound interface, the LSM can forward the operator
specific and common statistics to each operator's OSS respectively, as shown in
figure below.
EMS Clients for Partners

RAN is controlled and maintained by one operator. Other partners monitor or
query the network or usage information. Access level from an EMS client to the
main EMS can be changed according to the agreement between the host operator
and partners.
Figure below depicts the relationship of main and client EMSs.
Statistics Collected per PLMN

The information collected in the eNB by the PLMN ID is outlined in table below.
This statistics can be changed for a specific operator SW PKG, or for a Single
RAN SW PKG. For example, in SSR3.0, Bearers and Data usage categories were
excluded.
Category Items Classification Level Comments
PRB Usage DL PRB Usage Per PLMN/Cell Average number of PRBs
UL PRB Usage allocated to each PLMN during a
certain time period.
Active UEs Average number of active Per PLMN/Cell Average and peak number of
UEs RRC_Connected users during a
certain time period.
Maximum number of active
UEs
Bearers Average number of Bearers Per PLMN/Cell/QCI Average and peak number of
Maximum number of bearers during a certain timer
period.
Bearers
Data Usage Total number of Bytes (DL) Per PLMN/Cell/QCI Total number of bytes delivered
Total number of Bytes (UL) to or from UE. Uncompressed
packets are measured at
Total number of Bytes (DL) Per PLMN/Cell PDCP/RLC/MAC layer.
Total number of Bytes (UL)
Signaling Messages Total number of signaling Per PLMN/Cell DL/UL RRC/S1/X2 messages.
messages (DL)
Total number of signaling
messages (DL) (UL)
SYSTEM OPERATION
How to Activate
To add additional PLMN ID broadcasted to the specific cell, do the following:
1 Execute RTRV/CHG-ENBPLMN-INFO to configure additional PLMN ID
(=MCC + MNC) to the unused PLMN_IDX.
2 Execute RTRV/CHG-CELLPLMN-INFO to set PLMN_USAGE of the newly
specified PLMN ID with the specific cell and the corresponding PLMN_IDX.
Key Parameters
RTRV-ENBPLMN-INFO/CHG-ENBPLMN-INFO
PLMN_IDX The plmn index to be changed or retrieved. PLMN ID coreresponding to the
selected plmnIdx is mapped to the PLMN ID which is retrieved or changed by
command RTRV/CHG-ENBPLMN-INFO with the same plmnIdx number.
MCC[4] Mobile Country Code (MCC) that comprises Public Land Mobile Network
(PLMN).
MNC[4] Mobile Network Code (MNC) that comprises Public Land Mobile Network
(PLMN).
MCC/MNC of the PLMN_IDX = 0 is representative PLMN ID of the system

operator, and cannot be changed by CHG-ENBPLMN-INFO.
RTRV-CELLPLMN-INFO/CHG-CELLPLMN-INFO
CELL_NUM This parameter is the number of cells.This value must not exceed the maximum
PLMN_IDX The plmn index to be changed or retrieved. PLMN ID coreresponding to the
selected plmnIdx is mapped to the PLMN ID, which is retrieved or changed by
command RTRV/CHG-ENBPLMN-INFO with the same plmnIdx number.
PLMN_USAGE When cell is operated, determine whether to use the value of PLMN
corresponding plmnIdx.
use: The value of PLMN corresponding plmnIdx can be serviced.
no_use: The value of PLMN corresponding plmnIdx not be serviced.
Counters and KPIs

Name
RRC Connection ConnNo_PLMN The average value of the number of RRC connections
number (PLMN) periodically collected.
ConnMax_PLMN The maximum value of ConnNo_PLMN.
E-RAB UsageNbr_PLMN Average E-RAB count per unit time.
Simultaneous UsageNbrMax_PLMN Maximum E-RAB count per unit time.
Number (PLMN)
UsageNbr_QCI_x Average E-RAB count per unit time (QCIx).
UsageNbrMax_QCI_x Maximum E-RAB count per unit time (QCIx).
S-GW UL/DL ByteUleNBQCI_QCIx Bytes of user of QCI (x) data sent from the eNB to the S-GW.
packets (PLMN)
ByteDleNBQCI_QCIx Bytes of user of QCI (x) data sent from the S-GW to the eNB.
DL/UL Total PRB TotPrbDl_PLMN Total PRB Usage for PDSCH/PDCCH transmission per
Usage (PLMN) PLMN.
TotPrbDlMin_PLMN TotPrbDl_PLMN minimum.
TotPrbDlMax_PLMN TotPrbDl_PLMN maximum.
TotGbrPrbDl_PLMN Total PRB usage for downlink GBR traffic transmission per
PLMN.
TotGbrPrbDlMin_PLMN TotGbrPrbDl_PLMN minimum.
TotGbrPrbDlMax_PLMN TotGbrPrbDl_PLMN maximum.
TotNGbrPrbDl_PLMN Total PRB usage for downlink non-GBR traffic transmission
per PLMN.
TotNGbrPrbDlMin_PLMN TotNGbrPrbDl_PLMN minimum.
TotNGbrPrbDlMax_PLMN TotNGbrPrbDl_PLMN maximum.

Name
TotPrbUl_PLMN Total PRB usage for PUSCH transmission per PLMN.
TotPrbUlMin_PLMN TotPrbUl_PLMN minimum.
TotPrbUlMax_PLMN TotPrbUl_PLMN maximum.
TotGbrPrbUl_PLMN Total PRB usage for uplink GBR traffic transmission per
PLMN.
DL/UL Total PRB TotGbrPrbUlMin_PLMN TotGbrPrbUl_PLMN minimum.
Usage (PLMN)
TotGbrPrbUlMax_PLMN TotGbrPrbUl_PLMN maximum.
TotNGbrPrbUl_PLMN Total PRB usage for uplink non-GBR traffic transmission per
PLMN.
TotNGbrPrbUlMin_PLMN TotNGbrPrbUl_PLMN minimum.
TotNGbrPrbUlMax_PLMN TotNGbrPrbUl_PLMN maximum.
PROTOCOL_MSG RrcMsgSnd Sent the number of times in the RRC protocol Msg eNB.
RrcMsgRcv The number received in the RRC protocol Msg eNB.
S1MsgSnd Sent the number of times in the S1AP protocol Msg eNB.
S1MsgRcv The number received in the S1AP protocol Msg eNB.
X2MsgSnd Sent the number of times in the X2AP protocol Msg eNB.
X2MsgRcv The number received in the X2AP protocol Msg eNB.
If the operator does not use RAN sharing feature, some family of the statistics listed
above can be removed.
REFERENCE
[3] 3GPP TS23.251 Network Sharing; Architecture and functional description
Chapter 9 SON
Chapter 9 SON
LTE-SO0201, Intra-LTE ANR

INTRODUCTION
Samsung automatic neighbor relation (ANR) automatically configures and
manages the intra-LTE neighbor relation table (NRT), and it aims to maintain the
optimal NRT reflecting changes in the communication environment during the
system operation. Stable UE mobility of Samsung LTE cells is guaranteed by
optimized NRT management. UE mobility is guaranteed as follows according to
UE connection status.
1 RRC_CONNECTED: Guarantees stable intra-LTE HO of UE while connected
to the cell.
2 RRC_IDLE: Guarantees stable execution of cell selection/reselection of UE
while the cell is disconnected.
Samsung ANR provides the following functions depending on the SON phase:
1 Self-configuration phase
oInitial NRT auto-configuration through O&M: Create an initial NRT by using
the location information of active cells during eNB or cell growing
procedure.
2 Self-optimization phase
oFinds and adds new neighbor cells during HO execution due to UE mobility.
iAdds new neighbor cells to the NRT based on UE or LSM.
iiEstablishes bi-directional NR relations by adding the serving cell to the
NRT of a new neighbor cell with the help of the LSM.
iiiSets the automatic X2 interface between the serving cell and the new
neighbor cell.
oFinds and adds neighbor cells based on ANR specific event
iPerforms ANR measurement by configuring ANR specific event with the
UE selected among the ones which initially attach or perform
handover to this cell.
iiIf the best neighbor cell included in the measurement report (MR)
message triggered by ANR specific event is unknown, adds this cell to
NRT based on the UE or LSM.
iiiEstablishes bi-directional NR relations by adding the serving cell to the
NRT of a new neighbor cell with the help of the LSM.
ivConfigures the X2 interface automatically between a serving cell and
new neighbor cell.
Chapter 9 SON
oANR control function per carrier/operator

iPrevents adding a new neighbor cell of a specific carrier to NRT by
controlling the ANR measurement by carrier.
iiPrevents the X2 interface from being configured with the neighbor eNB,
which belongs to a specific operator by controlling X2 configuration
by operator.
iiiPrevents adding a new neighbor cell, which belongs to a specific
operator by controlling neighbor cell addition function per operator.
oAutomatic NRT management function
iNR ranking calculation: The NR ranking is calculated using the number
of MR messages received for HO.
iiNRT size management: The number of NRs in NRT should be managed
so that it does not exceed the pre-defined maximum size.
Guarantees the minimal number of effective neighbor cells per carrier
if attempting to add a new NR, when the NRT is full.
iiiUnnecessary NR removal: When the number of MR messages received
for NR is reduced due to UE not reporting them any longer, this
function removes the NR based on the specific threshold, which
enables for the NRT to include only valid NRs.
ivManagement of NR causing HO performance degradation: If the number
of HO success for NR is extremely low in spite of considerable
number of HO attempts, this function removes the NR or manages it as
HO blacklist based on the two respective thresholds for HO success
and attempts.
vInvalid NR management: If the number of successive HO failure for an
NR is larger than a threshold, this function removes the NR or
manages it as HO blacklist.
viHO blacklist management: This function manages the NRs causing HO
performance degradation or invalid NRs as HO blacklist.
oAutomatic X2-NRT management function
iX2 NR ranking calculation: X2 NR ranking is calculated using the
number of HO attempts.
iiX2-NRT size management: The number of X2 NRs in X2-NRT should be
managed so that it does not exceed the pre-defined maximum size.
eNB considers the number X2 NRs to be guaranteed per band
indicator
iiiUnnecessary X2 NR blacklisting: If ratio of handover attempt to an X2
NR is lower than predefined threshold, this function disconnects X2
link with the unnecessary X2 NR.
ivX2 link restoring: If ratio of S1 handover attempt to an X2 NR is larger
than predefined threshold, this function restores the X2 link with the
X2 NR.
oConfigures the neighbor cell lists used in measurement configurations
Chapter 9 SON
Configures the best neighbor cell list, which includes a maximum of 32

cells for each carriers measurement configuration in the order of
descending ranking, for the purpose of joint optimization with Samsung
MRO function.
BENEFIT
The operator can reduce CAPEX and OPEX costs for configuring and managing
the NRT of LTE cells.
The system performance indicators such as HO success rate and call drop rate are
optimized by configuring NRT optimized for coverage and air status of each
LTE cell. This guarantees reliable mobility of UEs in the RRC_IDLE mode
and the RRC_CONNECTED mode.

Dependency
UE ECGI acquiring function support: For UE-based NR addition, UE should
support the E-UTRAN cell global identifier (ECGI) acquiring function.
LSM-based NR addition function support: The operator should set LSM-based
NR addition flag to True.
In order to use the X2 setup on/off per PLMN function, operator should purchase
license key of LTE-SW5012 Operator Specific Feature Activation feature.
Limitation:
Bi-directional NR addition is possible only when the new neighbor cell belongs
to the same LSM as the serving cell. Bi-directional NR relations cannot be
established with the neighbor cells that are located in a different LSM or that
belong to a different vendor.
FEATURE DESCRIPTION
Architecture
Samsung ANR function operates in eNB and LSM. The overall architecture is
shown in the following figure:
Chapter 9 SON
As shown in figure above, Samsung ANR function is executed at eNB SON Agent
and at the LSM SON Manager. The operation of each entity in this architecture is
described below.
1 LSM
SON Manager: NRT Management Function
aCreates initial NRT
bPerforms LSM-based NR addition
cEstablishes bi-directional NR relationship based on LSM
2 eNB
SON Agent: NR Detection Function
aReceives the measurement report message for HO from the call processor
bReceives the measurement report message for periodic ANR from the call
processor
cAcquires ECGI and X2 TNL address from the Call Processor
SON Agent: NR Add Function
aAdds a neighbor cell by using the ECGI information
bAdds a neighbor eNB by using the X2 TNL address information.
Chapter 9 SON
If the configuration of X2 interface with a specific operator is not

allowed, configure as NoX2 = True.
SON Agent: NR Removal Function
aDeletes the NR by receiving the information on deletion of the NR from the
Call Processor (Served Cells to Delete IE in the X2 ENB
CONFIGURATION message).
bRemoves unnecessary NR.
cManagement of the NR that causes HO performance degradation.
dManagement of the invalid NR.
SON Agent: NR Ranking Function
aCalculates the ranking of NR by using the number of received MR messages.
bSends the NR ranking information to the Call Processor in order to create the
neighbor cell list for measurement configuration.
SON Agent: NRT Management Function
aDecides whether to perform NR addition/retrieval/attribute value
update/deletion.
bLSM SON Manager: Synchronizes NRT management function with the NRT.
cManages the NRT size so that it does not exceed the specified threshold
(maxNRTSize).
Guarantees the minimal number of effective neighbor cells per carrier if
attempting to add a new NR when the NRT is full.
Intra-LTE ANR Function

Self-Configuration Phase-Initial NRT Auto-configuration
Samsung LSM provides eNB or cell grow window with a SON option box. If the
Initial NRT Generation option in the box is checked, an initial NRT is generated
using the cells location information. This information is entered in LSM after the
software download to the cell has completed. Samsung LSM SON property
window includes the following parameters, which are used to generate the initial
NRT.
1 NRT.type: Decides the initial NRT creation method
2 NRT.multiple: A multiple for multiplying R counts (used in initial NRT
creation) and an average distance to the cells
3 NRT.limitDistance: The maximum distance to the neighbor cell that can be
included in the initial NRT
Samsung LSM provides the following Initial NRT generation methods.
1 NRT.type = average
aCreation method: Includes neighbor cells up to NRT.size per carrier in the
NRT within the radius of max{NRT Multiple Ravg, NRT.limitDistance}
Chapter 9 SON
iRavg: The average distance of R Count of cells within the

NRT.limitDistance.
R Count: The number of cells to be used for the Ravg calculation
iiNRT.size: The number of the initial NRT configurations
2 NRT.type = distance
aCreation method: Includes NRT.size neighbor cells within the radius of
NRT.limitDistance in the NRT.
3 NRT Type = minimum
aCreation method: Creates an initial NRT in the same way as NRT.type =
average, but the distance to the closest cell among the cells remaining
within NRT.limitDistance is used instead of Ravg.
Self-Optimization Phase-Automatic NRT Management
In the Self-optimization phase, Samsung ANR function provides the following
features:
Finds and Adds New Neighbor Cells during HO Execution due to UE
Mobility
Samsung NR addition function is triggered by an event where new neighbor cells
are found during the HO execution due to the UE mobility. In order to add the cell
to the NRT, if an ECGI can be acquired from UE, the UE-based NR addition is
executed; if an ECGI cannot be acquired, the LSM-based NR addition is
performed. The ECGI can be acquired from UE when the UE does not currently
use a GBR service, supports ECGI acquiring function as UE feature, and the
serving cell uses discontinuous reception (DRX).
1 The UE-based NR addition procedure uses the following steps:
aThe UE performs measurements according to the measurement configuration
transmitted by the serving cell.
bThe UE transmits the measurement report message to the serving cell.
cThe serving cell detects the PCI (Unknown PCI) of the new cell that does not
exist in its own NRT, and then it transmits the reportCGI configuration
requesting UE to acquire the ECGI.
iIf the ANR measurement for the carrier of a new cell is not allowed, the
neighbor cell is not added (that is, the procedure is terminated).
Setting parameter: ANR_ALLOW (Command: CHG-EUTRA-FA)
ANR_ALLOW: If the parameter is set to no use, the ANR
measurement is not allowed.
iiCommands for DRX operation setting: CHG-DRX-INFO
QCI: QCI index (1~9) used in UE-based NR adding function
DRX_CONFIG_SETUP: ci_Config_reportCGI
ON_DURATION_TIMER_REPORT_CGI:
ci_onDurationTimer_psf10
Chapter 9 SON
DRX_INACTIVITY_TIMER_ REPORT_CGI:
ci_drx_InactivityTimer_psf10
DRX_RETRANSMISSION_TIMER_ REPORT_CGI:
ci_drx_RetransmissionTimer_sf16
LONG_DRXCYCLE_START_OFFSET_TYPE_REPORT_CGI:
ci_sf2560_chosen
iiiTo handle the exception case of DRX operation, SON Agent runs the
EUTRA_REPORT_CGI_MR_TO_WAIT timer. If UE cannot acquire
the ECGI/CGI within the time, SON Agent terminates the DRX
operation to return the normal state of service.
dThe UE reads ECGI of new cell corresponding to the Unknown PCI in the
DRX period.
eThe UE transmits measurement report message including the acquired ECGI
to the serving cell.
fThe serving eNB checks whether PLMN ID in MR message is registered in
SonAnrPlmnBlackListInfo PLD.
iIn case that the PLMN ID is registered in SonAnrPlmnBlackListInfo PLD
and its usedFlag = use,
If EUTRA_BLOCK_FLAG = True, serving eNB terminates ANR
operation.
If EUTRA_BLOCK_FLAG = False, serving eNB performs step g.
iiIn case that the PLMN ID is not registered in SonAnrPlmnBlackListInfo
PLD or the PLMN ID is registered and its usedFlag = no_use,
Serving eNB performs step g
gThe serving eNB acquires IP address (X2 TNL address) of the new eNB from
MME.
hThe serving cell adds the new cell to its NRT.
iThe serving eNB reports to LSM that the new cell added to its NRT.
jThe LSM adds the serving cell to the new cell's NRT (Bi-directional NR
adding).
kThe serving eNB and new eNB determine whether to establish X2 connection
as follows (This function can be used if operator purchases the license key
of LTE-SW5012).
iIf the configuration of the X2 interface for the PLMN of the new eNB is
allowed, serving eNB sends X2 Setup Request to the new eNB.
iiIf the configuration of the X2 interface for the PLMN of the new eNB is
not allowed, set NoX2 = True for the neighbor eNB
X2 interface configuring command by PLMN: CHG-PLMNANR-ENB
ANR_TARGET_MCC: MCC of Neighbor eNB
ANR_TARGET_MNC: MNC of Neighbor eNB
Chapter 9 SON
USE_NBR_NO_X2: In case of use, set NoX2 = True for the neighbor

eNB with PLMN.
The following figure illustrates the UE-based NR addition procedure:
2 The LSM-based NR addition procedure uses the following steps:

aThe UE performs measurements based on the measurement configuration
sent by the serving cell.
bThe UE transmits measurement report message to the serving cell.
cAfter serving cell detects a PCI of a new cell which does not exist in its NRT
(Unknown PCI), it reports to LSM that unknown PCI is detected, since
acquiring ECGI from UE is not available.
iIf ANR measurement for the carrier of a new cell is not allowed, the
neighbor cell is not added (the unknown PCI detection is not reported
to LSM).
Chapter 9 SON
dThe LSM finds the nearest cell which corresponds to the serving eNB and
unknown PCI, and adds new cell to the serving cells NRT without
consideration of the new cell's PLMN.
eThe LSM adds the serving cell to the new cells NRT (bi-directional NR
adding).
fThe serving eNB and new eNB set the X2 connection.
iIf configuration of the X2 interface for PLMN of the new eNB is not
allowed, set NoX2 = True for the neighbor eNB.
The following figure illustrates the LSM-based NR addition procedure:
Finds and Adds New Neighbor Cells Based on the ANR specific-event and
Renewal of NR Info.
Chapter 9 SON
If a large volume of new cells are deployed to the network rapidly, neighbor cells
should be included in the NRT. As a result, reliable UE mobility can be supported.
In this scenario, Samsung ANR performs the additional NR adding function that
periodically finds and adds new neighbor cells. With this function, the optimum
NRT achievement rate is improved and reliable network operation is available.
The cycle of the function is set by date/hour/minute/performing duration and
through this cyclical operation and activation/deactivation flag, the operator can
control overheads which occur at eNB and UE.
The LTE cell decides which UEs will perform the function among the ones who
initially attach or enter the cell due to a handover according to the UE search rate
set by each cell (ANR_UE_SEARCH_RATE_TOTAL). Then, LTE cell decides
which selected UE measures among the LTE intra-frequency
(ANR_UE_SEARCH_RATE_INTRA_FREQ), the LTE inter-frequency
(ANR_UE_SEARCH_RATE_INTER_FREQ), and the UTRAN carriers
(ANR_UE_SEARCH_RATE_UTRAN). For example, if LTE network has two
carriers and UTRAN network has a few carriers, assume that UE search rates are
configured as ANR_UE_SEARCH_RATE_TOTAL = 5%,
ANR_UE_SEARCH_RATE_INTRA_FREQ = 40%,
ANR_UE_SEARCH_RATE_INTER_FREQ = 40%, and
ANR_UE_SEARCH_RATE_UTRAN = 20%. Then, 2% of UEs for the LTE intra-
frequency, 2% of UEs for the LTE inter-frequency, and 1% of UEs for the
UTRAN carriers will perform measurement for this function.
Samsung periodic ANR operation procedure uses the following steps:
1 To start the function, LTE cell selects the target UE among the ones which
initially attach or perform handover and the target carrier, and then sends the
RRC Connection Reconfiguration message to the target UE including the
ANR measurement configuration with target carrier to the target UE.
aThe function checks whether UE supports intra/inter-frequency ANR
operation based on the FeatureGroupIndicators IE included in the UE-
EUTRA-Capability IE
iIntra-frequency ANR support: 17th bit = 1
iiInter-frequency ANR support: 18th bit = 1 & 25th bit = 1
bTarget UE selection
iGenerates three random number (N1,N2,N3) ranging from 0 to 1
iiIf N1 < ANR_UE_SEARCH_RATE_TOTAL, LTE cell selects UE
cTarget carrier selection
iAccording to UE Capability, the method to select the target carrier for
ANR is as follows:
If UE supports LTE intra/inter-frequency ANR and the UTRAN ANR
operation, sets the intervals for LTE intra-frequency
(ANR_UE_SEARCH_RATE_INTRA_FREQ: y1), the LTE inter-
frequency (ANR_UE_SEARCH_RATE_INTER_FREQ:y2), and
the UTRAN carriers (ANR_UE_SEARCH_RATE_UTRAN:y3).
In this case, the intervals are separated into 3 parts:
Chapter 9 SON
If UE supports only LTE intra/inter-frequency ANR operation, sets

the intervals for LTE intra-frequency
(ANR_UE_SEARCH_RATE_INTRA_FREQ: y1), the LTE inter-
frequency (ANR_UE_SEARCH_RATE_INTER_FREQ:y2). In
this case, the intervals are separated into 2 parts:
Selects one among intra-frequency ANR, inter-frequency ANR, and

UTRAN ANR according to the random value N2.
iiWhen LTE intra-frequency ANR is selected, the UE performs periodical
measurement for intra-frequency.
iiiWhen LTE inter-frequency ANR is selected and there are more than 1
inter-carrier, sets the interval for each UE-supportable inter-carrier
with the ANR_UE_SEARCH_RATE in the ascending order of the
carrier index
x_{k}: ANR_UE_SEARCH_RATE set to k^{th} inter-carrier index
the interval for k^{th} carrier
a) Minimum value in the interval: (if k = 0, the value

is 0)
b) Maximum value in the interval:

After selecting one among UE-supportable LTE inter-carriers
according to the random value N3, UE performs periodical
measurement for the target inter-frequency.
dANR measurement configuration setting
iIf the selected carrier is intra-frequency
- ReportConfigEUTRA: configures ANR specific A3 event
iiIf the selected carrier is inter-frequency
- If A2 event is used for inter-frequency ANR
a) ReportConfigEUTRA: configures ANR specific A2 event
- If A2 event is not used for inter-frequency ANR or the eNB receives
MR message due to ANR specific A2 event
a) MeasObjectEUTRA: Sets the target carrier
b) ReportConfigEUTRA: configures ANR specific A4 event
c) Configures measurementGap
2 The UE transmits measurement report message to serving cell corresponding to
the ANR measurement configuration.
3 The serving cell perceives that PCI of the best neighbor cell in the message is a
new cell which is not in its NRT, and performs UE-based or LSM-based NR
addition.
Chapter 9 SON
aIf the ANR measurement for the carrier of a new cell is not allowed, the
neighbor cell is not added (The detail on the unknown PCI detection is not
reported to LSM)
bPlease refer to the c~j of Section Finds and Adds New Neighbor Cells during
HO Execution due to UE Mobility for the detail operation of the next
procedure.
4 The serving cell runs NR information update procedure based on Validity Check
Flag, if PCI of best neighbor cell existed in NRT is reported.
aIf the value of Validity Check Flag is True, nothing occurs.
bIf the value of Validity Check Flag is False, serving cell sends
RRCConnectionReconfiguration to UE for ECGI/CGI acquisition. Then,
the serving cell updates NRT, if it is necessary.
The UE-based NR addition following the periodic NR adding function is shown
below:
Chapter 9 SON
Automatic NRT management function

Samsung periodic NRT management procedure uses the following steps:
1 The serving cell collects statistics number of MR messages received for the HO
to neighbor cells included in the NRT.
2 When calculate the NR ranking arrives, the serving cell calculates ranking of the
NRs included in NRT based on the collected statistics.
3 The serving cell considers the NR with a low number of MR messages for HO as
unnecessary and removes it from the NRT.
4 The serving cell considers the NR with an extremely low HO success rate as a
HO performance degradation causing NR and then, the serving cell removes it
from the NRT or manages it as HO blacklist. In addition, if a NR satisfies the
predefined condition by analyzing HO preparation failure cause, Samsung
ANR removes the invalid NR from the NRT or manages it as HO blacklist.
1) NR Ranking Calculation
The NR ranking reflects the validity or importance of NR included in the NRT.
Samsung eNB defines the NR rankings attribute as having the higher ranking
when more MR messages are received as the HO for the NR is triggered.
The NR ranking is performed as follows:
1 The NR ranking calculation is performed at a specified interval.
2 The NR related to ranking calculation must be included in NRT at least beyond
the ranking calculation interval.
3 The ranking value used between the ranking calculation intervals uses the
ranking value calculated in the previous interval.
Chapter 9 SON
The following figure illustrates the NR ranking operation with an example:
The NR ranking is calculated based on statistics. To compare the rankings of NRs,

the period for collecting the statistics should be same among the NRs. In the
previous figure, New NR (NR j) is added at 16:00, the statistics for NR is collected
only for 11 hours. On the other hand, the statistics for NR previously added (NR i)
is collected for 24 hours. Since the comparison of the ranking between NR i and
NR j is imbalanced, we distinguish the ranking calculation method for these two
NRs.
The NR Ranking is calculated as follows:
1 The currentRank value for the NR i which is in the NRT for more than one NR
ranking calculation period as follows:
currentRank_{i}(k) = (1-)previousRank_{i}(k) + NMR_{i}(k)
ok: current ranking calculation time
o: IIR filter coefficient that gives some weights to the previous rank value
and the current statistics
opreviousRank_{i}(k): The rank value calculated in the last period
oNMR_{i}(k): The number of MR message received for the Cell i, which is
collected from the previous ranking calculation point k-1 to point k
2 The currentRank value for the NR j which is in the NRT for less than a NR
ranking calculation period as follows:
oFrom the NR ranking calculation point k,
currentRank_{j}(k) = -1
Maintain the value at-1 until the NR Ranking calculation period.
oAt the next ranking calculation point k+1,
currentRank_{j}(k+1) = NMR_{j}(k+1)
If the number of MR messages received for NR j is 0, NMR_{j}(k+1) is
set to 0.
Chapter 9 SON
At k+2 (next ranking calculation time after k+1), the rank value of NR j
is calculated as the same way as NR i which is explained above.
2) NRT Size Management
The maxNRTSize presents maximum number of NRs that can be included in the
Intra-LTE NRT. NRT size management is performed as follows:
1 maxNRTSize: Unless a service provider requests for a separate value, default
value is set as 256.
2 Intra-LTE NRT is managed so that no more NRs than the maxNRTSize could be
included.
When the attempt of adding a new NR occurs, in the situation where the existing
number of NRs is as many as maxNRTSize in Intra-LTE NRT, the following
operations are performed depending on the ANR setting mode.
1 ANR setting mode = sonAutoApply or sonManualApply
oReason for new NR addition attempt
aNR addition by UE-based ANR function
bNR addition by LSM-based ANR function
cNR addition by LSM-based bi-directional addition function
dManual addition by the operator
oOperation procedure
aIn case of carriers which NRs as HO attribute (T) are larger than
minNRTSizeCarrier (i)
iParameter for setting the minimal number of effective neighbors by
carrier: minNRTSizeCarrier (Command: CHG-EUTRA-FA)
If the maxNRTSize change attempting value is larger than the value
adding the sum of minNRTSizeCarrier (i) for all carriers and the
number of NR belonging to the HO blacklist, it changes.
maxNRTSize: Maximum size for a NRT (Command: CHG-SON-
ANR)
bAmong NRs as CurrentRank -1 & HO attribute (T) set as carriers for Intra-
LTE NRT,
The NR whose CurrentRank = -1 is excluded from the list of removal since
it existed less than the NR ranking interval in NRT.
cThe lowest ranking NR with the remove attribute (T) is deleted and a new NR
is added.
2 ANR setting mode = sonFuncOff
oReason for new NR addition attempt
aNR addition by LSM-based bi-directional addition function
bManual addition by the operator
oOperation procedure
Chapter 9 SON
aIn case of NR addition by LSM-based bi-directional addition function:

Same as the operating procedure (1)
bIn case of Manual addition by the operator: the New NR is not added
The following figure shows the ranking based NR removal function used to
manage the NRT size:
3) Unnecessary NR Removal
When the network is stabilized through the network optimization, this function
removes NRs which cannot receive MR messages among the NRs included when
the network was initially created, so that only valid NRs could be included in the
NRT. The operator can control this functions ON/OFF state, and at the NR
ranking calculation point k, the serving cell removes the NR i which meets the
following conditions.
aANR operation mode = sonAutoApply or sonManualApply &
bnrDelFlag = True &
nrDelFlag: ON/OFF control flag that determines the operational status.
cCumulatedMRi (k) thNumMrNrDel &
CumulatedMRi(k): The number of MR messages received for NR i
during thTimeNrDel period at the NR ranking calculation point k.
thNumMrNrDel: The threshold value to decide unnecessary NR.
disRemoveAllowed = True for NR i
The following figure shows the statistics based NR removal function used to delete
unnecessary NRs:
Chapter 9 SON
4) Management of NR causing HO performance degradation

If a new cell located nearby has the same PCI as the PCI of a distant NR, which is
included in the NRT at the initial network formation and UE transmits a
measurement report message for HO while moving to the new cell. Due to this, the
serving cell wrongly recognizes the PCI in the message as belonging to the distant
NR. Therefore, UE fails the HO execution.
The following figure illustrates the management scenario of the NR causing HO
performance degradation:
In the previous figure, UE moves toward the neighbor cell (ECGI = 1002) and
transmits the measurement report message including PCI = 20 by HO triggering to
the serving cell (ECGI = 1000). The serving cell completes HO preparation using
the NR (ECGI = 1001) included in the NRT, and then transmits the HO command
message received from the NR. However, UE is moved to the new cell (ECGI =
1002), thus HO execution fails. As shown the figure above, Samsung ANR
removes the HO performance degradation causing NR from the NRT or manages
it as HO blacklist.
The operator can control this functions ON/OFF state, and at the NR ranking
calculation point k, the serving cell removes the NR i from the NRT or manages it
as HO blacklist which meets the following conditions.
Chapter 9 SON
aANR operation mode = sonAutoApply or sonManualApply &

bwrongNrDelFlag = True &
wrongNrDelFlag: ON/OFF control flag that determines the operational
status.
cCumulatedNHOAtti (k) thHoAttNrDel &
CumulatedNHOAtti (k): The number of HO preparation successes
collected for NR i during thTimeNrDel at the NR ranking calculation
point k.
thHoAttNrDel: The threshold value of HO attempts to decide HO
performance degradation causing NR.
dCumulatedNHOSuci (k) thHoSucNrDel &
CumulatedNHOSuci (k): The number of HO success collected for NR i
during thTimeNrDel period at the NR ranking calculation point k.
thHoSucNrDel: The threshold value of the number of HO success to
decide HO performance degradation causing NR.
eisRemoveAllowed = True for NR i
5) Management of invalid NR
1 Determination of invalid NR which causes HO preparation failure
aServing cell removes the invalid NR from the NRT or manages it as HO
blacklist if the number of successive HO preparation failures is larger than
the predefined threshold. The threshold can be configured by operator for
each HO preparation failure cause.
bIn order to use this function, following parameter configuration is required.
ianrEnable = Auto or Manual
iinbrDelCauseFlag = True
iiiThreshold > 0 per Cause
The following table shows S1 HO preparation failure causes.
Causes Meaning
Handover Failure In Target The handover failed due to a failure in target EPC/eNB or target system.
EPC/eNB Or Target System
TS1RELOCprep Expiry Handover Preparation procedure is cancelled when timer TS1RELOCprep
expires.
Cell not available The concerned cell is not available.
Unknown Target ID Handover rejected because the target ID is not known to the EPC.
Unknown PLMN The MME does not identify any PLMN provided by the eNB.
The following table shows X2 HO preparation failure causes

Causes Meaning
TRELOCprep Expiry Handover Preparation procedure is cancelled when timer TRELOCprep
expires.
Chapter 9 SON
Causes Meaning
Cell not available The concerned cell is not available.
6) HO blacklist management
1 NR can be managed as HO blacklist if the NR is determined as the invalid NR or
the NR causing HO performance degradation.
2 Serving cell performs validation check for the NR managed as HO blacklist by
acquiring ECGI of the NR through reportCGI once during ranking period.
3 NRs can be changed from HO blacklist to the HO whitelist for the following
cases
aA. ECGI information of the NR is changed by reportCGI operation.
bB. The value of hand-in statistics for the HO blacklist NR is larger than
thHandIn4Black2White.
cC. Operator changes the HO attribute of the NR from HO blacklist to HO
whitelist.
Automatic X2-NRT Management Function
1) X2 NR Priority (ranking) Calculation
The X2 NR ranking (priority) means the validity or significance of the X2 NR
included in X2 NRT. Samsung Intra-LTE ANR function defines that the X2 NR
ranking attribution has higher ranking as the more number of S1/X2 HO triggering
for X2 NR increases. X2 NR ranking is operated in the method shown below:
1 The X2 NR ranking calculation is performed after cell NR ranking.
2 The X2 ranking value used between the ranking calculation intervals uses the
ranking value calculated in the previous interval.
X2 NR ranking uses S1/X2 HO statistics and is calculated as shown below:
1 Collecting HOIn (i) statistics for X2 NR i in X2 NRT
oReceive HANDOVER REQUEST (S1/X2).
oIndex eNB i corresponding to the top ECGI in Last Visited Cell Information
IE included in UE History Information IE.
oIncrease HOInS1 (i) or HOInX2 (i) by HO triggering type.
oHOIn(i) = HOInS1 (i) + HOInX2 (i)
2 Collecting HOOut(i) statistics for X2 NR i in X2 NRT
oTransmit HANDOVER REQUIRED (S1) or HANDOVER REQUEST (X2).
oIncrease HOOutS1 (i) or HOOutX2(i) for eNB i as target of HO.
oHOOut(i) = HOOutS1 (i) + HOOutX2 (i)
3 Calculating the currentX2Rank value by X2 NR as follows:
currentX 2Ranki (k ) (1 ) previousX 2Ranki (k ) tempCurrentX 2Ranki (k )
k: X2 NR ranking calculation time
Chapter 9 SON
: IIR filtering coefficient

previousX2Ranki(k): X2 rank value calculated in the previous interval
tempCurrentX2Ranti(k) = HOOutRatei(k)+ HOInRatei(k)
HOOut(i)
HOOutRate(i) I
max(1, HOOut(i))
i 1
HOinS1(i ) HOinX 2(i )
HOInRate(i ) I
max( 1, HOinS1(i ) HOinX 2(i ))
i 1
I: Total number of X2 NRs in X2 NRT

HOOut(i): S1/X2 HO-Out attempt count to neighbor eNB i at this
interval
HOInS1(i)/HOInX2(i): S1/X2 HO-Out attempt count collected to
neighbor eNB i at this interval
4 Setting the currentX2Rank value for the new X2 NR j which existed within the
NR ranking calculation period in X2 NRT
currentX 2Rank j (k ) defaultVal ueX 2
defaultValueX2: configurable system parameter
2) X2-NRT Size Management
The maxX2NRTSize means the maximum number of X2 NRs, which can be
included in the Intra-LTE X2 NRT, and is operated as the following:
1 maxX2NRTSize: Different initial value can be set per service provider.
2 The eNB does not include X2 NRs more than X2 NRT hard limit in Intra-LTE
X2-NRT. Also, it manages the number of X2 NRs included in the Intra-LTE
X2-NRT not to exceed the maxX2NRTSize every ranking period.
3 If the operator configures the X2GuaranteedBandInfo to maintain minimum
number of X2 Links for a specific band indicator, the eNB performs X2 NR
deletion function for X2-NRT size management by considering the value of
the parameters in X2GuaranteedBandInfo.
When an attempt occurs to add a new X2 NR, in the situation where there exist X2
NRs as many as maxX2NRTSize in Intra-LTE X2 NRT, eNB allows X2 NR
addition until X2-NRT hard limit size and does not add the new X2 NR when there
exist X2 NRs as many as X2-NRT hard limit.
The eNB manages the number of X2 NRs included in the Intra-LTE X2-NRT not
to exceed the maxX2NRTSize every ranking period through following operation.
1 Include in X2-NRT in order of X2 ranking among X2 NRs as noRemove = True.
2 In the order of index of band indicator in X2GuaranteedBandInfo, includes the
X2 NRs which supports the band indicator in the X2-NRT from the order of
higher X2 ranking until the number of X2 NR reaches minX2NrtSize.
Chapter 9 SON
oIf the number of X2 NRs in X2-NRT is larger or equal to maxX2NRTSize at

step (2), omit step (3).
oThrough the steps (1) and (2), the number of X2 NRs can be larger than
maxX2NrtSize.
3 Includes X2 NR in the X2-NRT from the order of higher X2 ranking until the
number of X2 NR reaches maxX2NrtSize.
X2-NRT Size Management operation is shown in the following figure:
3) Unnecessary X2 NR blacklisting
In order to reduce X2 signaling load caused by invalid X2 NR, if ratio of handover
attempt to an X2 NR is lower than predefined threshold, this function disconnects
the X2 link with the unnecessary X2 NR. The operator can control this functions
ON/OFF state. At the X2 NR ranking calculation point k, the serving eNB
disconnects X2 Link by changing the attribute of noX2 of X2 NR i which meets
the following conditions from False to True.
1 sonX2MgmtEnable = Auto &
2 nrX2BlackEnable = Auto &
3 &
oavg.tempCurrentX2Rank_{i}(k): The average occurrence ratio of handover
to X2 NR i during thTimeNrDel at the X2 NR ranking calculation point k
oweightThX2Black: weight factor for determining the threshold for judging the
X2 NR as an invalid X2 NR
oN_{NBR-eNB}: the number of X2 NRs which exist in X2-NRT more than
thTimeNrDel
4 noRemove = False for X2 NR i
Chapter 9 SON
The following figure shows the statistics based X2 NR removal function.
4) X2 Link restoring
eNB restores the X2 Link of the X2 NR by changing the attribute of noX2 from
True to False if the currentX2Rank is larger than the predefined threshold at X2
NR ranking calculation point. The operator can control this functions ON/OFF
state. At the X2 NR ranking calculation point k, the serving eNB restores X2 Link
by changing the attribute of noX2 of X2 NR i which meets the following
conditions from True to False.
1 sonX2MgmtEnable = Auto &
2 nrX2ReEnable = Auto &
3 &
oweightThX2Black: weight factor for determining the threshold for judging
the X2 NR as an X2 NR to be restored
oN_{NBR-eNB}: the number of X2 NRs which exist in X2-NRT more than
ranking calculation period (rankPeriod)
4 noRemove = False for X2 NR i
Creates Neighbor Cell Lists for Measurement Configuration
The LTE cell can transmit to UE the measurement configurations of a maximum
of 32 frequencies and information of a maximum of 32 neighbor cells for each
configuration (cell individual offset). Cell individual offset is a parameter which
optimizes and improves each NRs HO performance in Samsung MRO function.
For the purpose of joint optimization with Samsung MRO function, Samsung
ANR function configures a maximum of 32 neighbor cell lists for each
frequencys measurement configuration in the order of ranking. HO performance
can be improved, when the cell individual offset value optimized for each neighbor
cell is transmitted to UE in the order of the nearest coverage with the serving cell.
The procedure for this operation is as follows.
1 NRs with isHOAllowed = True & isRemoveAllowed = False are configured in
the neighbor cell list in the order of ranking.
2 (If it is not filled) NRs with isHOAllowed = True & isRemoveAllowed = True
are configured in the neighbor cell list in the order of ranking.
Chapter 9 SON
SYSTEM OPERATION
How to Activate
Pre-condition
The UE must support Intra-LTE ANR capability (that is, the UE capability &
related feature group indicator bits are set to 1).
The UE has no GBR bearer (for example, QCI=1).
Feature Activation & Action
The related system parameters are configured as follows:
oThe ANR_ENABLE value must be set to Manual or Auto.
oTo enable periodic Scheduled ANR functionality, the NR_ADD_EVENT
value must be set to anrMrBased or bothMrBased.
oThe ANR_UE_SEARCH_RATE_TOTAL value must greater than 0.
oFor Intra-Frequency periodic ANR functionality, the
ANR_UE_SEARCH_RATE_INTRA_FREQ value must greater than 0.
oFor Inter-Frequency periodic ANR functionality, the
ANR_UE_SEARCH_RATE_INTER_FREQ value must greater than 0.
oThe concerned E-UTRA FAs ANR_UE_SEARCH_RATE value must
greater than 0.
oThe DRX_CONFIG_SETUP value must be set to Drx_Config_Setup or
Drx_Config_reportCGI.
1 The eNB chooses UE for Scheduled ANR by ANR UE selection rules.
2 In case Intra-LTE ANR UE is selected, eNB configures ANR specific
measurement configuration for UE (at this time, measurement duration timer is
started in the eNB).
3 The UE transmits the measurement report to the eNB based on ANR specific
measurement configuration.
4 When eNB receives non-neighbor E-UTRA cell from UE, it requests cell global
identity to the UE (using reportCGI configuration).
5 If eNB successfully obtains the non-neighbor E-UTRA cells CGI from UE, it
registers the new E-UTRA cell into the own neighbor DB.
6 The eNB removes ANR specific measurement configuration for Scheduled ANR
from the UE when the measurement duration timer is expired.
(For mobility based Intra-LTE ANR) In case of the UE receives handover related
measurement report from the UE, the eNB perform from 4) to 5) steps.
Deactivation
The ANR_ENABLE value must be set to OFF.
To disable Scheduled ANR functionality, the NR_ADD_EVENT value must be
set to hoMrBased.
Chapter 9 SON
Key Parameters
This table describes SON property for NRT auto-configuration in LSM.
Parameters for Initial NRT auto-configuration
R Count The number of neighbor cells used to calculate the inter-site distance for
Initial NRT, PCI, and RSI auto-configuration.
NRT Type Criteria for determining the effective distance used to generate the initial
NRT. It can be set to minimum, average, or distance.
Distance: Use of NRT Limit Distance as effective radius
Average: Use of R multiplied by NRT Multiple as effective radius where R
is the distance obtained by averaging the inter-site distance with the
neighbor cells in the nearest order (The number of neighbor cells is R
Count).
Minimum: Use of R multiplied by NRT Multiple as the effective radius
where R is the distance with nearest neighbor cell.
NRT Size The number of neighbor cells that can be included in the initial NRT.
NRT Multiple The coefficient which is multiplied to either the average distance of the cells
as many as R Count or the distance of the nearest neighbor cell.
NRT Limit The maximum distance to the neighbor cell that can be included in the Initial
Distance NRT.
The operator can set the operation mode of Samsung ANR function to
automatic/manual/deactivate or retrieve the mode through the following
commands and parameter.
Parameters for the operation mode control
CHG-SONFN-CELL/RTRV-SONFN-CELL
ANR_ENABLE The Intra-LTE Automatic Neighbor Relation (ANR) operation is controlled in
3 modes.
Off (0): The Intra-LTE ANR function is not performed (X2-based NR
deletion and NR ranking calculation is performed).
Manual (1): Operator approval is required for NR deletion. Other ANR
functions are performed automatically.
Auto (2): All ANR functions are performed automatically.
The operator can configure or view method to manage X2 interface by using the
following commands and parameters.
Parameters for X2 interface management
CHG-SONFN-ENB/RTRV-SONFN-ENB
SON_X2_MGMT_ENABLE The flag controlling whether the automatic X2 interface management
function is performed or not.
Off (0): The automatic X2 interface management function is not performed.
Auto (1): The automatic X2 interface management function is performed
(X2 ranking calculation and the size management of X2 Neighbor
Chapter 9 SON
Relation Table (NRT)).
NR_X2_BLACK_ENABLE The flag controlling whether the automatic X2 interface blacklisting function
is performed or not. (Prerequisite: SON_X2_MGMT_ENABLE = Auto)
Off (0): The automatic X2 interface blacklisting function is not performed.
Auto (1): The automatic X2 interface blacklisting function is performed.
NR_X2_RE_ENABLE The flag controlling whether the automatic X2 interface restore function is
performed or not. (Prerequisite: SON_X2_MGMT_ENABLE = Auto)
Off (0): The automatic X2 interface restoring function is not performed.
Auto (1): The automatic X2 interface restoring function is performed.
Counters and KPIs

Counters related to the Samsung ANR function are as follows:
Name
HO IntraEnbPrepSucc The number of Intra-eNB handover preparation success to
intra-eNB neighbor cell
IntraEnbSucc The number of Intra-eNB handover execution success to
intra-eNB neighbor cell
InterX2OutPrepSucc The number of X2 HO preparation success to inter-eNB
neighbor cell
InterX2OutSucc The number of X2 HO execution success to inter-eNB
neighbor cell
InterS1OutPrepSucc The number of S1 HO preparation success to inter-eNB
neighbor cell
InterS1OutSucc The number of S1 HO execution success to inter-eNB
neighbor cell
KPIs related to Samsung ANR function are as follows:

KPI Name Description
EutranMobilityHOIntra Intra-eNB handover success rate of E-UTRAN mobility
EutranMobilityHOX2Out X2 handover success rate of E-UTRAN mobility
EutranMobilityHOS1Out S1 handover success rate of E-UTRAN mobility
CallDropRatio Call drop rate
REFERENCE
[1] 3GPP TS 36.300: E-UTRA and E-UTRAN; overall description Stage 2
(Release 10).
[2] 3GPP TS 36.331: E-UTRAN; Radio Resource Control (RRC); Protocol
specification (Release 10).
[3] 3GPP TS 36.902: E-UTRAN; Self-configuring and self-optimizing network
(SON) use cases and solutions.
[4] 3GPP TS 32.500: E-UTRAN; Concepts & Requirements.
Chapter 9 SON
[5] 3GPP TS 32.501: E-UTRAN; Self-configuration of network elements; OAM

Requirements for Self Configuration Use Cases.
[6] 3GPP TS 36.413: E-UTRAN; S1 Application Protocol (Release 10).
[7] 3GPP TS 36.423: E-UTRAN; X2 Application Protocol (Release 10).
Chapter 9 SON
LTE-SO0301, PCI AutoConfiguration

INTRODUCTION
Samsung PCI optimization provides functions such as auto PCI configuration for
initial PCI allocation during network installation, PCI collision, confusion
detection, and auto PCI optimization for PCI reallocation.
There are 504 PCIs in the LTE system. PCIs consist of the formula (1) using 168
unique physical layer cell identity groups, N_{ID}^{(1)} and 3 physical layer
identities within the physical layer cell identity group, N_{ID}^{(2)}
N_{ID}^{Cell}=3*N_{ID}^{(1)}+ N_{ID}^{(2)}(1)
N_{ID}^{(2)} is related to cell-specific reference signal location pattern.
N_{ID}^{(1)} is a sequence number which is used N_{ID}^{Cell} with
N_{ID}^{(2)}
PCIs are used in synchronization and reference signal generation, which are
involved in cell selection, handover and channel estimation procedures.
According to 3GPP specification there are 504 unique physical-layer cell identities.
The physical-layer cell identities are grouped into 168 unique physical-layer cell-
identity groups, each group containing three unique identities.
Samsung PCI optimization policy is as follows:
PCI allocated should satisfy the collision-free and confusion-free condition.
PCI allocated should reduce inter-RS (cell-specific reference signal) interference.
PCI reallocation can be performed based on either location or Neighbor Relation
Table method.
PCI of the newest cell to be enabled in the network should be changed, when its
collision occurs. (Newly grow cell should have the higher ECGI number).
BENEFIT
With Samsung PCI optimization, the operator can reduce CAPEX/OPEX
required for network installation and expansion.
Samsung PCI optimization guarantees the end users have improved mobility
between cells.

Dependency
Application of the PCI optimization requires location information of the cell where
the PCI allocation is required.
Chapter 9 SON
Limitation
The location based PCI reallocation method of the PCI optimization might cause a
PCI collision and confusion with a cell that does not use the same EMS.
FEATURE DESCRIPTION
Samsung PCI optimization operates in eNB's SON agent and EMS's SON manager.
The overall structure is as follows:
The operation of each entity in this architecture is as follows:

LSM
SON Manager: PCI Management Function
Create initial PCI
Performs a PCI reallocation upon receiving the PCI collision/confusion notify
information message.
PCI reallocation cell selection
Transmits a new PCI to the eNB of the cell whose PCI is changed.
Chapter 9 SON
Transmit timer triggering notify information to eNB which has smaller ECGI.
eNB: SON Agent
SON Agent: PCI Management Function
oTransmits a notify information message to the LSM and stores it in the DB
when PCI collision/confusion is determined.
oTimer running for waiting PCI reconfiguration when LSM trigger timer
oWhen timer expires, transmit a new PCI allocation message to the LSM.
SON Agent: PCI collision/confusion Detection Function
oDetects PCI collision/confusion using the X2_SETUP_REQUEST and
eNB_CONFIGURATION_UPDATE messages received from the call
processor.
oDetects a PCI collision/confusion using the ECGI information received from
the neighbor detection function.
PCI Auto-configuration
The PCI auto-configuration function is performed in LSM. It aims to allocate PCIs
based on the distance between cells to avoid PCI collision/confusion. Selects the
reference distance from the cells that allocates PCI, and then allocates PCIs,
assuring that all cells belonging to the same LSM within the reference distance
avoid PCI collision/confusion. The following picture shows a brief overview of the
PCI configuration.
There are two kinds of considering situation to avoid when PCI auto configuration
is performed.
PCI collision
oDefinition: where two cells with adjacent coverage use the same FA and PCI.
Chapter 9 SON
oProblem: handover ambiguity occurs because UE existing on the border

between the two cells cannot distinguish the serving cell from the neighbor
cell.
oThe following figure shows PCI collision:
PCI confusion
oDefinition: where two cells adjacent to the coverage of the serving cell (cell
B) use the same FA and PCI.
oProblem: handover ambiguity occurs because the cell B is cannot distinguish
which is the target cell.
oThe following figure shows PCI confusion:
The PCI auto-configuration involves the following operations:

1 The LSM receives latitude/longitude coordinates of the installed cell from the
operator or the GPS during eNB installation.
2 The LSM calculates the reference distance (D) (Refer to 2.2.1).
3 N_{ID}^{(2)} is allocated first for the PCI allocation cell. For the cell existing
at the same location, ensure N_{ID}^{(2)} is not in neighborhoods with it by
using its cell number.
4 Select PCIs other than the ones used by all cells that use the same LSM within
the reference distance from the PCI allocation cell. If the cells within the
reference distance (D) use all allocable PCIs, select PCIs by using the
maximum reuse distance. Maximum reuse distance means the maximum
distance between cells which the same PCI can be reused within D.
Chapter 9 SON
Distance Calculation for PCI Auto-configuration

PCIs are collected within the reference distance (D) to avoid PCI conflicts and D is
calculated as follows:
D = MAX(R*R_Multi, LimiDist).
R = Inter-site distance.
R_multi = [0, 4].
LimitDist = [0, 100] km.
The cells within reference distance (D) will be considered for new installed cells
PCI auto configuration. LSM calculate reference distance (D) with above 3
parameters R, R_multi, and LimitDist.
The following is explanation of parameters for PCI auto-configuration:
R means basically Inter-site distance, but Inter-site distance from a cell to another
cell can have all different value. So, Samsung support 3 different kinds of
Inter-site distance R calculation mode. Inter-site distance R is calculated based
on the selection below.
ominimum: using R as distance of the nearest neighbour cell
odistance: criteria of fixed distance
oaverage: using R as average distance with cell inside LimitDist
Operator can change the inter-site distance mode value in LSM SON Property
GUI PCI Type menu.
R_multi is a scaling parameter for expansion Inter-site distance R. Operator can
adjust the number of cells inside the distance D with R_multi.
Operator can change R_multi value in LSM SON Property GUI PCI multiple
menu.
LimitDist means minimum of the effective Distance D when allocating PCI.
Even through dense deployment area, each cell should consider minimum
distance LimitDist for PCI auto-configuration.
Operator can change LimitDist value in LSM SON Property GUI PCI
LimitDist menu.
PCI Optimization
PCI Collision/Confusion Detection
The PCI collision/confusion detection function is performed in SON agent of eNB.
There is a list of PCI collision/confusion detection occurrence situation & pre-
requisite as below. When PCI collision/confusion is detected, SON agent reports to
SON manager of LSM on the occurrence of PCI conflict and the 2TierNRT
creation.
PCI conflicts detection occurrence
oPCI change by operator
oNew neighbor cell enrolled by ANR operation and Manually added neighbor
Chapter 9 SON
oX2 message information (FA, PCI, and ECGI) from neighbor eNB
Pre-requisite
oNeighbor relation Table
o2Tier Neighbor relation Table
A pre-requisite for PCI confusion is that each cell creates and maintains its NRT
for handover. A serving cell is only aware of its immediate neighbor cell (that is,
NRT) and not its neighbor to neighbor PCI number (that is, 2TierNRT). PCI
confusion occurs as a result of 2TierNRT PCI clash hence, a cell also needs to
create a list of neighbor to neighbor cell PCI value, to detect PCI confusion. When
a cell receive a X2 message from its immediate neighbor cell, it updates 2TierNRT
PCI values, which is used for PCI confusion detection and deny PCI list, for new
PCI allocation. The figure below shows more details about PCI
Collision/Confusion Detection:
PCI Reallocation Cell Selection

The PCI conflict always occurs in pair, PCI reallocation should change only one
PCI. When LSM receives PCI conflict report from eNB, it determines one cell to
change PCI based on ECGI. LSM selects the cell having higher ECGI between
two cells contained in PCI conflict report. Also, it tries to change the PCI of the
selected cell. In addition, instructs the cell with lower ECGI to start the timer for
triggering the request for a new PCI. If the cell with a higher ECGI successfully
changes its PCI, then eNB managing the cell sends its neighbor eNBs X2 message
which informs the change of the PCI. If eNB managing the cell with a lower ECGI
receives this X2 message, the cell recognizes the resolution of PCI conflict and
then cancels the timer operation. Otherwise, the timer will be expired and the cell
with a lower ECGI will recognize that PCI conflict is not resolved. Then, the cell
with a lower ECGI requests LSM to reallocate a new PCI.
Chapter 9 SON
PCI Reallocation
Upon receiving the report of PCI conflict, SON manager of LSM selects the target
cell for PCI reallocation. PCI reallocation procedures are performed once its cell is
selected.
NRT based PCI reallocation (default)
The NRT based PCI reallocation method is as follows:
o2TierNRT PCI number is reported from eNB.
oStep1) Delete the PCIs in the 2TierNRT from the PCI pool.
oStep2) Reconfigure new PCI by PCI auto-configuration procedure in the
same way self-configuration phase.
PCI Collision Detection Based on UE Mobility
The PCI collision detection function based on UE mobility focuses on the
resolution of PCI conflict between neighboring eNBs when UE moves from one
cell coverage to other one. By using this function, PCI collision can be detected
even though there is no neighbor relation between two adjacent cells. UE cannot
successfully perform HO: RLF occurs due to RF degradation and UE tries to
synchronize with the target cell again. UE requests RRC Connection Re-
establishment to the target cell but the request is rejected, because the target cell
does not have UE Context.
PCI collision detection occurrence
oThe UE moves from the serving cell to the target cell
oThe UE experiences RLF event
oThe UE tries RRC Re-establishment (RRE) procedure in the target cell
oThe eNB of the target cell can detect PCI that can be potentially involved in
the PCI collision
Condition for PCI collision detection
There are three defined conditions that control PCI collision detection:
oCondition 1: PCI in UE-Identity and PCI of the cell that receives Re-
establishment request from UE are the same.
oCondition 2: C-RNTI in UE-Identity has already existed in the cell that
receives Re-establishment request from UE
oCondition 3: Short MAC-I in UE-Identity is not identical to Short MAC-I
that is calculated by the target cell
oPCI collision is detected if condition 1 is satisfied and condition 2 is not
satisfied, or all three conditions are satisfied at the same time.
Pre-requisite
SON Manager at EMS differentiates PCI conflict message and PCI collision
notification
The following figure shows Samsung femto PCI collision detection based on
UE mobility:
Chapter 9 SON
Once SON Manager at LSM receives the notification of the PCI collision from
eNB, it selects the cell for PCI reallocation based on obtained ECGI
information. PCI reallocation procedure is the same as described previously.
To exclude the redundancy of notification of PCI collision, LSM saves PCI
collision event and waits until PCI reconfiguration time period starts. In this
case, LSM begins to resolve PCI collision one by one during PCI
reconfiguration period. If another timer that relates to PCI confusion event is
running, LSM turns off the timer.
SYSTEM OPERATION
How to Activate
Pre-condition
The PCI optimization function is activated in the LSM.
To activate this feature, PCID_ENABLE (system parameter) value must be set to
Auto or Manual.
1 The eNB monitors X2 Setup Request, X2 Setup Response, and X2 eNB
Configuration messages.
2 The eNB delivers PCI conflict information to the LSM when the PCI collision or
confusion is detected.
3 If the new PCI is reassigned from the LSM, the eNB applies the new PCI to the
system.
(SLR4.5.0) To activate PCI collision detection based on UE mobility information
feature, PCI_COLLISION_DETECT_FLAG (system parameter) value must
be set to True.
Chapter 9 SON
Feature Deactivation
To deactivate this feature, PCID_ENABLE (system parameter) value must be set
to OFF.
(SLR4.5.0) To deactivate PCI collision detection based on UE mobility
information feature, PCI_COLLISION_DETECT_FLAG (system parameter)
value must be set to False.
Key Parameters
The following tables show SON property for NRT auto-configuration in LSM:
SON property setting for PCI Auto-configuration
R Count Number of neighbor cells used to calculate the inter-site distance for initial
NRT, PCI, RSI auto-configuration
PCI Type Criteria for determining the effective distance used to generate the initial PCI.
It can be set to minimum, average, or distance.
Distance: Use of PCI Limit Distance as effective radius
Average: Use of R multiplied by PCI Multiple as effective radius where R is
the distance obtained by averaging the inter-site distance with the neighbor
cells in the nearest order (The number of neighbor cells is R Count).
Minimum: Use of R multiplied by PCI Multiple as the effective radius where R
is the distance with nearest neighbor cell.
PCI Multiple The coefficient which is multiplied to either the average distance of the cells as
many as R Count or the distance of the nearest neighbor cell.
PCI Limit Distance The minimum distance to the neighbor cell that can be included in the Initial
PCI.
Pico PCI White List Set Pico PCI White List
Can set up to 10 ranges.
In case of entering none or space: allocated Pico PCI of that range
Can set as number or number-number. (ex:0-100,150-200,300)
Macro PCI White List Set Macro PCI White List
Can set up to 10 ranges.
In case of entering none or space: allocated Macro PCI of that range
Can set as number or number-number. (ex:0-100,150-200,300)
The operator can set the operation mode of the Samsung PCI Auto-configuration
function to automatic/manual/deactivate or retrieve the mode through the
following commands and parameter.
PCID_ENABLE Controls SON PCID operation at 3 stages.
Off (0): Performs X2 monitoring.
Manual (1): After initial PCI auto configuration, X2 monitoring and PCI
collision/confusion detection are performed, the PCID in which
collision/confusion was detected can be reallocated manually.
Auto (2): After initial PCI auto configuration, X2 monitoring and PCI
collision/confusion detection are performed, the PCID in which
Chapter 9 SON
collision/confusion was detected is reallocated automatically by the LSM
SON manager.
PCI_COLLISION_DETECT_F This parameter controls the UE based PCI collision detection function.
LAG False (0): The PCI collision detection function and related notification
message is not performed.
True (1): The PCI collision detection function and related notification is
performed.
Counters and KPIs

There are no related counters and KPIs
REFERENCE
[1] 3GPP 36.300: E-UTRA and E-UTRAN; overall description Stage 2 (Release 9)
specification (Release 9)
[4] 3GPP 32.500: E-UTRAN; Concepts & Requirements
[5] 3GPP 32.501: E-UTRAN; Self-configuration of network elements; OAM
Requirements for Self Configuration Use Cases
[6] 3GPP 32.521: E-UTRAN; Self-Organizing Networks (SON) Policy Network
Resource Model (NRM) Integration Reference Point (IRP); Requirements
Resource Model (NRM) Integration Reference Point (IRP); Information Service
(IS)
[8] 3GPP 32.541: E-UTRAN; OAM Requirements for Self Healing Use Cases
Chapter 9 SON
LTE-SO0401, RACH Optimization

INTRODUCTION
Random Access Channel (RACH) of LTE system is the uplink channel defined in
the 3GPP specifications. Depending on the purpose, RACH is classified into two
types, the contention based method and the non-contention based method. The
contention based method is used for the initial network connection of User
Equipment (UE) and the non-contention-based method is used for the connection
to the target cell during UE's handover. The actual information transmitted to
RACH includes the Zadoff Chu (ZC) sequence whose total length is 839. The LTE
System has total 838 ZC sequences (root sequences) for RACH and one ZC
sequence can be reused by cyclic shifting. The UE transmits one sequence that is
Random Access Preamble (RAP) through Physical Random Access Channel
(PRACH) that is the physical channel of RACH to connect initially to the network
or attempt a connection to the target cell. Each cell of LTE System configures a
RAP set with total 64 consecutive RAPs. As UE selects and uses any RAPs in this
RAP set, the number of root sequences used in a cell is determined by the reuse
number of one root sequence. A cell can use RAPs by dividing the 64 RAPs into
preambles for random access and the dedicated preambles for handover.
PRACH resource allocation in LTE System is determined by the PRACH
configuration index and freq-offset. The PRACH configuration index indicates its
allocation interval and the location of the subframe where it is transmitted. The
PRACH freq-offset indicates the location of the physical resource block where it is
allocated. The PRACH configuration index is used to determine the reuse number
of root sequence. Each RACH resource parameter value can be determined with
various combinations by HighSpeedFlag, Zero Correlation Zone Configuration
(ZCZC), and Random Access Preamble format.
Samsung RACH optimization method aims to minimize UE access delay and
maximize UL capacity using various RACH resources. Also, its optimization
function is placed in the eNB and EMS respectively. It collects RACH-related
statistics, changes parameters using accumulated statistics, and detects RSI
collision in eNB. It initially allocates RSI, reallocates RSI during operation, and
changing some of RACH parameters in EMS.
The configuration function of Samsung RACH optimization automatically
determines RSI of the newly installed or grown cell. It sets the reference distance
based on location of the installed cell to minimize RSI reuse within the reference
distance.
The optimization performs below functions: RSI collision detection and
reallocation during the operation of the network, optimization of the number of
dedicated preambles through the collection of RACH-related statistics, and
optimization of the RACH time resources and optimization of the RACH
transmission power of UE.
Chapter 9 SON
BENEFIT
The operator can reduce previously spent CAPEX and OPEX cost for configuring
and managing the RSI and PRACH parameters of LTE cells.
Minimize UE access delay and maximize UL capacity

Dependency
Self Configuration
oApplication of the RSI configuration requires location information of the cell
where the RSI allocation is required.
Self Optimization
oApplication of the RACH optimization needs 3GPP Rel.9 UE support
including RACH- report in UE information message.
Limitation
Self Configuration
oThe location based RSI allocation method might cause a RSI collision with a
cell that does not use the same EMS.
Self Optimization
oRSI allocation method might cause RSI reallocation failure when X2
connection is unable between eNBs.
FEATURE DESCRIPTION
Samsung RACH optimization operates in eNB's SON agent and EMS's SON
manager. The overall structure is as follows:
Chapter 9 SON
The architecture above shows, Samsung RO functions is executed at eNBs SON

agent and EMSs SON Manager. The operation of each entity in this architecture
is as follows:
EMS
SON Manager: RSI Management Function
Create initial RSI
Performs a RSI reallocation upon receiving the RSI collision/confusion notify
information message.
RSI reallocation cell selection
Transmits a new RSI to the eNB of the cell whose RSI has been changed.
eNB: SON Agent
RO Statistic Management
oIt periodically collects and accumulates the RO-related statistics information
from UE and eNB.
oIt receives changed RO-related parameters and transmits to the Radio
Resource Control (RRC) block.
Chapter 9 SON
RO Parameter Control Function

oIt changes RO parameters at every RACH parameter decision interval based
on accumulated RACH statistics.
RSI Collision Detection Function
oIt detects RSI collision through the ENB_CONFIGURATION_UPDATE
message received from the call processor.
Self-Configuration Procedure
RSI Auto-configuration
Samsung RSI auto-configuration is performed in EMS. Subsequently, it aims to
allocate RSI that minimizes RS range overlap based on the input distances
between cells. The RSI Auto-configuration function operates based on the
distances from the cell that requires RSI allocation to other currently operating
cells that use the same EMS. The closest cell among those is selected to configure
the virtual neighbor. After that, the used root sequence set is calculated using the
union of the virtual neighbor and the root sequence that the virtual neighbor is
using. RSI is allocated by selecting an available RS range among RS in the whole
root sequence pool excluding the used root Sequence set.
RSI auto configuration involves the following operation:

1 When installing a cell, EMS receives the latitude and longitude coordinates of
the installed cell through the operator or GPS.
2 The operator inputs the parameters related to RO of SON Property window of
EMS.
3 The distances to the currently operating cells that use the same FA among the
cells within the already input NRT distance threshold are calculated, and in
order of proximity, the NMax_virtual_NRT numbers of cells are selected to
configure the virtual NRT.
Chapter 9 SON
4 Used Root Sequence set is configured by collecting root sequences that are used
by cells in Virtual NRT.
5 An available RS set is configured in the whole RS pool by excluding the used
root sequence set.
6 RSI is allocated by selecting an allocable RS range among the available RS set.
At this point, if there is no RS range among the available RS set that satisfies
the consecutive RS, eNB includes RS range which is used in the farthest cell
into the available RS set, and allocates RSI by selecting an allocable RS range
among the available RS set. The eNB repeats step 6) until an RSI can be
allocated to the growing cell.
As mentioned in document, each cell should use continuous 64 PRACH
preambles.
PRACH preamble can be reuse based cyclic shift value which defined in 3GPP
36.211 table 5.7.2-2 as below:
oN_{CS} for preamble generation (preamble formats 0-3)
ZeroCorrelationZoneConfig N_{CS} value
Unrestricted Set Restricted Set
0 0 15
1 13 18
2 15 22
3 18 26
4 22 32
5 26 38
6 32 46
7 38 55
8 46 68
9 59 82
10 76 100
11 93 128
12 119 158
13 167 202
14 279 237
15 419 -
oN_{CS} represents the number of cyclic shift

oHigh speed flag(Boolean) :
0 then use Unrestricted set, 1 then use Restricted set
oRoot sequence index : initial root sequence index
oExample) if, ZCZC=9, high speed flag=0
Then, the number of reusable preamble with one root sequence is
calculated as
Chapter 9 SON
Floor (838/59) = 14, Floor (total number of root sequence/cyclic shift

value)
So, one root sequence is reusable 14times
oAs mentioned above one cell needs to have 64 continuous preamble.
So, the number of required root sequence for one cell is calculated as
Ceil (64/14) = 5, ceil (number of preamble for one cell/number of reusable
preamble)
oTherefore, 5 root sequence is required.
oEMS figures out with above procedures.
7 Generate occupied root sequence index subset based on the all cells that use the
same EMS within the reference distance.
8 Select RSI which has minimum number of root sequence index range out of
unoccupied root sequence index set.
PRACH Position Allocation
The location of PRACH in an LTE system is determined by the PRACH
configuration index along the time axis of the UL frame and by the PRACH
frequency offset value along the frequency axis of the UL frame. When PRACHs
that use 6RBs are at the same location in a heterogeneous network environment,
interference between the PRACHs of macrocell and femtocell, and RSI collision
may occur. Samsung RO function prevents interference of PRACH and RSI
collision in heterogeneous networks by separating the frequency location of
PRACH according to eNB type.
The following figure shows PRACH separation on heterogeneous LTE network:
Chapter 9 SON
Self Optimization
The self-optimization function of Samsung RACH Optimization is divided into the
event triggering operation and the periodic operation that is based on the statistics
information collected during operation. The event triggering RO operation
performs required operations when one of the following events is occurred during
network operation: i) neighbor relation change, ii) change in root sequence of
neighbor cell, iii) activation of RS collision detection and RSI reallocation
function (from OFF to ON). The statistics based periodic RO operation controls
PRACH InitialReceivedTargetPower, the number of dedicated preambles, and so
on. according to periodically obtained RACH-related statistics.
RSI Conflict Detection and Reallocation
RS Collision Detection
RS collision refers to a situation where two cells in neighbor relation use the
same FA and RS. In this case, as UE of the two cells selects one preamble in
an overlapping RS range and then transmits the PRACH preamble to attempt
the initial connection to the network, the probability of contention increases.
Therefore, it can degrade the performance of the initial network connection.
The RS collision detection function is performed by SON Agent of eNB if RS
collision detection and corresponding RSI reallocation function is activated.
The RS collision detection function is performed for the following cases:
oFor the case of two cells with Inter-eNB neighbor relation: The function
operates when cell configuration change message is received through X2
interface.
oFor the case of Intra-eNB neighbor cell: The function operates when eNB
Configuration update of itself is performed.
The SON Agent reports the occurrence of RS collision to SON manager of
EMS when RS collision is detected.
RSI reallocation
The SON manager of EMS receives RS collision reports and selects target
cells for RS reallocation. The selection procedure is as follows:
o(Case 1) In case that the function is already activated, a cell that has a bigger
ECGI is selected as RSI reallocation cell based on the ECGIs of RS
collision target cells.
o(Case 2) In case that the status of RS collision detection and RSI reallocation
function for a cell is changed from inactive (OFF) to active (ON), the cell
is selected as RSI reallocation cell.
Chapter 9 SON
Then, SON manager in EMS requests the selected cell to report the neighbor
relation list. Meanwhile, for (Case 1), EMS transmits a timer triggering
message to a cell with a smaller ECGI, and the cell receiving the message
operates timer. If timer of the cell with a smaller ECGI has expired, the cell
considers that RSI reallocation to the cell with a bigger ECGI has failed and
requests the RSI reallocation again. At this point, if a RSI change message is
received from the cell with a bigger ECGI after the timer has started running,
timer of the cell with a smaller ECGI will be stopped. For (Case 2) where the
status of RS collision detection and RSI reallocation function for a cell is
changed from inactive (OFF) to active (ON), the operation of timer is not
performed.
The cell that received the NR list request transmits the NR list to EMS. Then,
EMS configures used root sequence set by collecting root sequence used by
neighbor cells in the NR list. When using the used root sequence set, EMS
allocates RSI in the same way for the self-configuration procedure. If no RSI
for reallocation is available, EMS does not reallocate RSI.
Periodic RACH Optimization

There are two aspects of RACH optimization that is number of dedicated preamble
and Initial ReceivedTargetPower. The following figure shows a procedural of
RACH optimization:
Chapter 9 SON
Dedi_Pre_Fail_Radio = Failure ratio of dedicated preamble allocation

Avg_Pre_Sent_Num_Ratio = Average Number of Num of Preamble Sent
Det_Cont_Ratio = Ratio of contention detected
Thx_up/dn: threshold which is configurable in EMS
Dedicated Preamble vs. Contention Preamble Adjustment
An optimal number of dedicated preambles dictate new subscriber accessibility
and HO latency. Using HO statistics, RO control function controls the number of
dedicated preamble dynamically. For example - in a lightly loaded cell with low
mobility activity, RO control function will split the available preambles to allow
for more contention preambles. In a cell with lot of mobility activity and near-
capacity user count, RO control function will split the available preambles to have
more dedicated preambles. The following figure shows the general flow of
contention vs. dedicated preamble split:
Chapter 9 SON
RO statistics management keeps statistics of dedicated preamble usage and

computes a probability of dedicated preamble assignment failure based on
DedicatedPreambles-AssignFail OM. If the configured probability,
PROB_DEDICATED_INCREASE, exceeds configured threshold,
DEDICATED_INCREASE, dedicated preambles are increased. In a similar
fashion-if configured probability-PROB_DEDICATED_DECREASE falls below a
configured threshold of DEDICATED_DECREASE, dedicated preambles are
decreased. The following figure shows the general flow of dedicated vs. contention
preamble split:
PRACH Channel Configuration for RACH Optimization

3GPP spec allows for several configurations that signal the configuration of
PRACH channel-via SystemInformationBlockType2. Since PRACH is a common
uplink control channel, it is wasteful to allocate RACH region in all sub-frames.
eNB can choose to declare the location of subframe and the periodicity of PRACH
based on prachConfigIndex. The following figure shows the mapping of
prachConfigIndex to physical location of PRACH region:
Parameter Allowed Values
powerRampingStep (dB) 0, 2, 4, 6,
preambleInitialReceivedTargePower (dBm) -120, -118, -116, -114, -112, -110, -108, -106, -104, -102, -100, -
98, -96, -94, -92, -90
prachConfigIndex Refer to the table below
The following table shows the PrachConfigindex to RACH region mapping:
Chapter 9 SON
As an example, PRACH configuration Index of 0 means UE should use Preamble

format 0 and transmit the preamble in even system frame numbers on subframe
number 1. This translates to PRACH location in 1st subframe in every 20
milliseconds.
PRACH configuration also includes power related parameters. eNB performs
statistical analysis of RACH related OMs and optimizes RACH configuration
based on performance. The following figure provides an overview of optimization
algorithm:
Chapter 9 SON
RO statistics management receives RACH statistics related number of preambles

sent and contention detected. eNB sends ULInformationTransferRequest message
with rach-ReportReq set to TRUE.
If numberOfPreamblesSent is greater than a configured threshold, eNB checks for
contentionDetected flag and computes contention detection probability if available.
Based on the RACH statistics, PRACH related parameters are adjusted as follows:
> if contention detection probability-PROB_CONTENTION_INCREASE is
greater than a configured threshold value, CONTENTION_INCREASE, then
eNB configures opportunity (or PRACH density) related parameters,
prachConfigIndex, to allow more PRACH opportunities.
[This is a scenario where UEs are not able to capture PRACH channel due to
less opportunities, which is causing a lot of preamble collision.]
> if contention detection probability-PROB_CONTENTION_INCREASE is less
than the configured threshold value, CONTENTION_INCREASE, then eNB
increases preambleInitialReceivedTargetPower which allows for higher initial
power while sending first RACH preamble.
[This is a scenario where UEs are not able to capture PRACH channel due to
inadequate preamble power. Thus, it takes more retries-while slowly
increasing power, to get RACH response]
If numberOfPreamblesSent AND contention detection probability fall below
their respective configured thresholds, PRACH density and power parameters
are lowered.
SYSTEM OPERATION
How to Activate
Pre-condition
The RACH optimization function is activated in the EMS.
The UE supports RACH report functionality (that is, UE Information procedure).
Chapter 9 SON
The X2 messages include PRACH Configuration information.

To activate RACH optimization feature, RACH_OPT_ENABLE value must be
set to Auto.
To activate RS conflict detection and RSI reallocation feature,
RSI_CONFLICT_ENABLE value must be set to Auto.
1 For RACH optimization, eNB requests RACH report information to UE that is
connected to the serving (that is, Attach or Idle-to-Active cases) or target cell
(for example, Handover case).
2 The eNB successfully performs UE Information procedure with UE and then
controls related counters using received RACH report information.
3 For RS collision detection and RSI reallocation, eNB monitors the X2 Setup
Request, X2 Setup Response, and X2 eNB Configuration Update messages.
4 The eNB checks if RS collision occurs using the received RACH configuration
information.
5 If RS collision is detected, eNB reports RS conflict message to the EMS.
6 If new RSI is reallocated from the EMS, eNB adapts new RSI value to the
system.
Deactivation
To deactivate RACH optimization feature, RACH_OPT_ENABLE value must be
set to OFF.
To deactivate RS collision detection and RSI reallocation feature,
RSI_CONFLICT_ENABLE value must be set to OFF.
Key Parameters
The following table describes SON property for RSI auto-configuration in LSM.
SON property window for RSI auto-configuration
R Count Number of Cell to use for calculating average of NRT, PCI, RSI.
RSI Type Criteria of the effective radius when allocating RSI. Can set to minimum, average
or distance.
minimum: using R as distance with nearest neighbor cell.
distance: criteria of fixed distance.
average: use of R multiplied by RSI Multiple as effective radius where R is the
distance obtained by averaging the inter-site distance with the neighbor cells in
the nearest order (The number of neighbor cells is R Count).
RSI Multiple Expansion range of calculating the effective distance when allocating RSI.
RSI Limit Distance Minimum of the effective radius when allocating RSI.
The operator can set the operation mode of Samsung RACH Optimization function
to activate/deactivate the mode through the following commands and parameter.
Chapter 9 SON
RACH_OPT_ENABLE The parameter is used to control the RACH Optimization operation in three
modes.
Off (0): RO function is disabled, except X2 interface monitoring
Manual (1): RO related parameters are change by operators confirmation.
Auto (2): All RO related parameters are change automatically
RSI_CONFLICT_ENABLE RSI reallocation function Enable/Disable
Counters and KPIs

Random Access HighSpeedMonitoring The number of UEs which are monitored for moving
Preambles speed
NoOfHighSpeed The number of high speed UEs which are monitored
DedicatedPreambles The number of detected dedicated preambles.
DedicatedPreamblesA The number of failures to get dedicated preamble
ssignFail allocation after requesting the dedicated preamble from
RRC to MAC
RandomlySelectedPre The number of the preambles belonging to Group A
amblesLow among the detected contention based preambles
RandomlySelectedPre The number of the preambles belonging to Group B
amblesHigh among the detected contention based preambles
RACHUsage Average number of detected preambles
Calculate when reporting the statistics information:
Sum (RACHUsageTot)/sum (RACHUsageCnt)
RACH Usage Preamblesent1 The cumulative number of times when the
numberOfPreamblesSent value in the rachReport
information of the RRC UE information response
message received from the UE is 1
Preamblesent2 The cumulative number of times when the
message received from the UE is 2.
Chapter 9 SON

message received from the UE is 9 or more.
RachContention This counter collects the contentionDetected value in
the rachReport information of the RRC UE information
response message received from the UE.
RachReportsRcvNum The cumulative number of times when the rachReport
information is received in the RRC UE information
response message received from the UE.
REFERENCE
[4] 3GPP 32.500: E-UTRAN; Self-Organizing Networks (SON); Concepts and
requirements
[5] 3GPP 32.501: E-UTRAN; Self-configuration of network elements; Concepts
and requirements
Resource Model (NRM) Integration Reference Point (IRP); Requirements
Resource Model (NRM) Integration Reference Point (IRP); Information Service
(IS)
[8] 3GPP 32.541: E-UTRAN; Self-Organizing Networks (SON); Self-healing
concepts and requirements
Chapter 9 SON
LTE-SO0602, Cell Outage Compensation

INTRODUCTION
Samsung Cell Outage Compensation (COC) adjusts the transmission power of
RRH automatically, if the outage occurs for a specific cell during the operation of
LTE system to compensate a cell outage area. Also, this consists of cell outage
detection, cell outage compensation, and cell outage clear functions.
1 Cell outage detection
oThe eNB detects the occurrence of cell outage and if the cell outage occurred,
it reports cell outage to the EMS.
2 Cell outage compensation
oIf the EMS receives report on the cell outage from eNB, it selects a cell to
participate in the COC to compensate the cell outage and determines the
transmission power of RRH of the cell. The cell to participate in COC is
excluded from the Coverage and Capacity Optimization (CCO).
oThe EMS transmits to eNB the transmission power of RRH of the cell to
participate in COC as determined above.
oThe eNB applies the received transmission power of RRH.
3 Cell outage clear
oIf the cell outage is released, eNB reports it to the EMS.
oIf the EMS receives report on the release of the cell outage, it sets the
transmission power of RRH of the outage cell. As a result, the cell to
participate in the COC before cell outage as the transmission power value
and transmits it to eNB. At the time, the outage cell and the cell to
participate in COC are included against as targets for CCO.
oThe eNB applies the received transmission power of RRH.
The transmission power of RRH of each cell may be controlled by CCO function
and COC function. To prevent conflicts between the two functions, COC function
has the higher priority than CCO function. Accordingly, if both CCO function and
COC function are operated, the transmission power of RRH is adjusted as follows:
If a specific cell is participating in COC, in other words, if the cell uses the
maximum transmission power to compensate the outage area, the transmission
power of RRH of the cell is not adjusted by CCO function.
If the specific cell does not participate in COC, the transmission power of RRH
of the cell may be adjusted by CCO function.
Chapter 9 SON
BENEFIT
Operator can reduce operational cost by automatic cell outage detection and
compensation functions.
After cell outage occurs, users in cell outage area can be in service in a short time.

Dependency:
This feature supports only Macro and Outdoor Pico systems.
Limitations:
In case that Tx power of the COC candidate cell is set to maximum value, its Tx
power value is not changed anymore when outage of its neighbor cell is
detected.
FEATURE DESCRIPTION
Network Structure
The network architecture for COC in LTE system is as shown below. The main
network entities (NEs) in the network architecture include eNBs and EMS. The
connection between EMS and eNB represents a management interface. Also, eNBs
and EMS exchange information for the performance of COC through the
management interfaces.
The following figure is Network architecture for COC in LTE system:
Chapter 9 SON
The main NEs for the operation of COC are as follows:

1 eNB
oDetects a cell outage
oReports occurrence of the cell outage to the EMS.
oReceives transmission power by RRH of the cell to participate in the COC to
compensate the cell outage from the EMS.
Applies transmission power of RRH of the cell.
Delivers information on the changed transmission power of the RRH
through SIB2.
oIf the cell outage becomes clear, reports it to the EMS.
oReceives transmission power by RRH before the occurrence of COC of the
outage cell and the cell participating in COC from the EMS.
Applies transmission power of RRH of the cell.
Delivers information on the changed transmission power of the RRH
through SIB2.
2 EMS
oReceives the occurrence of a cell outage from eNB.
oDetermines a cell to participate in COC.
Saves the information on the outage cell and the cell to participate in
COC.
oExcludes the cell to participate in COC from the operation of CCO.
Determines transmission power of the cell to participate in COC.
Delivers transmission power of the cell to participate in COC to eNB.
Receives the cell outage clear from eNB. (Check the status of eNB cell
regularly.)
If the cell outage becomes clear, includes the cell to participate in COC
in the targets for COC.
Delivers the transmission power by RRH before the occurrence of COC
of the outage cell and the cell participating in COC.
COC Operation Procedure

The operation procedure of Samsung COC is as follows:
Chapter 9 SON
1 The eNB detects occurrence of the cell outage.

2 The eNB delivers the CELL_OUTAGE_DETECTION message including the
information on the outage cell to the EMS.
3 The EMS selects a cell to participate in COC among the neighbor cells of the
outage cell.
4 The EMS stores the information on the outage cell and the cell to participate in
COC (for example, eNB ID, cell ID, and transmission power of RRH before
the occurrence of the cell outage).
5 The EMS excludes the cell to participate in COC from the operation of CCO.
6 The EMS determines transmission power of RRH of the cell to participate in
COC.
Chapter 9 SON
7 The EMS delivers the COC_COMP_RRH_TX_POWER_RECONFIG message

including the transmission power by RRH for the cell to participate in COC
managed by eNB to the eNB including the cell to participate in COC.
8 The eNB sets the transmission power of the RRH depending on the transmission
power of the cell to participate in COC included in the
COC_COMP_RRH_TX_POWER_RECONFIG message.
9 The eNB delivers the information on the changed transmission power of the
RRH through SIB2.
10 The EMS checks status of the cell regularly until it receives the
CELL_OUTAGE_CLEAR message from eNB or status of the outage cell is
enabled.
11 The eNB performs cell outage recovery.
12 The eNB delivers the CELL_OUTAGE_CLEAR message including the
information on the cell to the EMS, if the cell outage is relieved.
13 The EMS checks whether it receives the CELL_OUTAGE_CLEAR message
or status of the outage cell is enabled.
14 The EMS includes a cell whose outage is released to participate in COC in the
target for CCO.
15 The EMS delivers the COC_COMP_RRH_TX_POWER_RECONFIG message
including the transmission power by RRH before outage occurrence of the cell
relating to COC managed by the eNB to the eNB including the COC-related
cell (the cell whose outage is relieved and the cell to participate in COC).
16 The eNB sets the transmission power of the RRH depending on the
transmission power of the COC-related cell by RRH to the
COC_COMP_RRH_TX_POWER_RECONFIG message.
17 The eNB delivers the information on the changed transmission power of the
RRH through SIB2.
COC Algorithm
(Sub1) Cell Outage Detection
The eNB detects the occurrence of the cell outage for the cell outage detection
function and reports it to the EMS.
1 Detecting the occurrence of a cell outage
Samsung COC function defines an outage cell as follows:
oIf status of the cell is maintained as being disabled during a specific period of
time (DisableDuration)
If status of the cell is disabled due to the lock by operator, the cell is not
considered as an outage cell.
2 Reporting the occurrence of the cell outage to the EMS
If the cell managing by eNB is decided as an outage cell, the eNB reports the
CELL_OUTAGE_ DETECTION message to the EMS. The
CELL_OUTAGE_DETECTION message includes followings:
Chapter 9 SON
oOutageeNBID: The ID of eNB transmitting the

CELL_OUTAGE_DETECTION message
oOutageCellID: The ID of the cell where the outage occurs
oTxPdBm: The transmission power of RRH of the cell where the outage
occurs
(Sub2) Cell Outage Compensation
When the EMS receives the CELL_OUTAGE_DETECTION message from eNB,
it performs the following procedure:
1 Selecting the cell to participate in COC and saving the relevant information
2 Excluding the cell to participate in COC from the operation of CCO
3 Determining the transmission power of the RRH of the cell to participate in
COC
4 Delivering and applying the transmission power of the RRH of the cell to
participate in COC
5 Checking status of the outage cell regularly
The detail for the aforementioned procedure is as follows:
(Sub2) Selecting a cell to participate in COC and determining the transmission
power of the RRH (Procedures from 1 to 3)
The EMS checks the outage cell from the CELL_OUTAGE_DETECTION
message transmitted by eNB, and checks the value of FrequencyRange
(=Intra-Frequency or Inter-Frequency) of SON Property.
In case that FrequencyRange=Intra-Frequency, cells satisfying all the
following conditions are selected to participate in COC for the outage cell:
oAmong neighbor cells in outage cells NRT, neighbor cell using the same
frequency with the outage cell
oCells set to participate in COC
oIf the handover attempt count to the cell during a day exceeds zero
In case that FrequencyRange=Inter-Frequency, cells satisfying all the
following conditions are selected to participate in COC for the outage cell:
oAll the neighbor cells in outage cells NRT
oCells set to participate in COC
oIf the handover attempt count to the cell during a day exceeds zero
The EMS saves eNB ID, cell ID, and the current transmission power of the
RRH for the outage cell and the selected cells to participate in COC through
the aforementioned conditions. After excluding the cells to participate in COC
from the CCO operation, the EMS sets the transmission power of the RRH of
the cell to the transmission power to the maximum.
(Sub2) Delivering and applying the transmission power of the RRH of the cell to
participate in COC (Procedure 4)
Chapter 9 SON
The EMS delivers to eNB that manages the cells to participate in COC
transmission power of the RRH of the pre-determined cells to participate in
COC through the COC_COMP_RRH_RX_POWER_RECONFIG message.
The COC_COMP_RRH_RX_POWER_RECONFIG message includes the
eNB ID, ID of the cell to participate in COC, the RRH index of the cell, and
the transmission power value of the RRH.
The eNB that receives the COC_COMP_RRH_TX_POWER_RECONFIG
message sets the transmission power of the RRH of the cell managed by the
eNB to the transmission power value in
COC_COMP_RRH_TX_POWER_RECONFIG. After changing the power
transmission of the RRH, eNB delivers to UE the information on the changed
power transmission of the RRH through SIB2.
(Sub2) Checking status of the outage cell (Procedure 5)
After sending the COC_COMP_RRH_TX_POWER_RECONFIG message,
the EMS checks status of the outage cell regularly until the following
conditions are satisfied:
oReceiving the CELL_OUTAGE_CLEAR message from eNB which manages
the outage cell
oChecking that status of the outage cell is enabled by checking the status of
the cell regularly
(Sub1) Cell Outage Clear
When the EMS receives the CELL_OUTAGE_CLEAR message from eNB or
checks whether status of the outage cell is enabled, the following operation is
performed:
1 Detecting and reporting cell outage clear
2 Including the cells to participate in COC in the cells for CCO
3 Determining the transmission power of the RRH of the COC-related cells (the
outage cell and cells to participate in COC) before occurrence of the cell
outage
4 Delivering and setting the transmission power of the RRH of the COC-related
cells
The detail for the aforementioned procedure is as follows:
(Sub2) Detecting and reporting cell outage clear (Procedure 1)
aIn case of detecting cell outage clear by reporting to eNB
If status of the outage cell is changed from disabled to enabled, the eNB
decides the outage of the cell is cleared and reports the
CELL_OUTAGE_CLEAR message to the EMS. The
CELL_OUTAGE_CLEAR message includes the cell ID information of the
cell whose outrage is released.
bIn case of detecting the release of cell outage through checking the status of
the cell of EMS periodically
The EMS checks status of outage cell regularly and if status of outage cell
is changed to enabled, the EMS decides the status as cell outage clear.
Chapter 9 SON
(Sub2) Recovering the transmission power of the COC-related cell (Procedure

from 2 to 3)
When the EMS checks the release of the cell outage (whether the status of the
cell is enabled by receiving the CELL_OUTAGE_CLEAR message from the
eNB or through the regular checkup of the EMS), the EMS includes the cell to
participate in COC again in the cell for CCO. After that, the EMS determines
the transmission power of the RRH of the COC-related cells (an outage cell
which is released and a cell to participate in COC) as the saved value when the
cell outage compensation operation is performed.
(Sub2) Delivering and setting the transmission power of the RRH of the COC-
related cell (Procedure 4)
The EMS transmits transmission power value of the RRH pre-determined to
eNB through the COC_COMP_RRH_TX_POWER_RECONFIG message.
The COC_COMP_RRH_TX_POWER_RECONFIG message includes the
eNB ID, IDs of the cells to participate in COC, the RRH index of the cell, and
the transmission power value of the RRH.
The eNB that receives the COC_COMP_RRH_TX_POWER_RECONFIG
message sets the transmission power of the RRH of the COC-related cell as
the transmission power before the occurrence of the cell outage included in the
message. After that, eNB delivers the information on the changed transmission
power of the RRH through SIB2.
SYSTEM OPERATION
How to Activate
The operator sets the COC operation to auto or manual of the
SON_COC_FUNC_ENABLE value of eNB to operate the COC to activate the
COC operation. In addition, the operator sets the
SON_CCO_PWR_CTRL_ENABLE value of the cell to change the transmission
power to auto through the COC operation.
Provided, however, that the SON_COC_PWR_CTRL_ENABLE value cannot be
applied as auto for the cell in the eNB whose SON_COC_FUNC_ENABLE is Off.
The CCO operation-related parameter settings are as follows:
FrequencyRange: Frequency range considered when selecting cells to participate
in COC
DISABLE_DURATION: Waiting time to decide as cell outage
Key Parameters
The operator may set frequency range considered when selecting cells to
participate in COC by using FrequencyRange of SON Property.
FrequencyRange Frequency range which will be considered when selecting cells to participate
in COC
Chapter 9 SON
The operator may change and retrieve the operating mode, either automatic or
release, in Samsung COC by using the following commands and parameters:
SON_COC_FUNC_ENABLE In SON, determines the enable of the cell outage compensation (COC) SON.
Off: Turn off the function.
Manual: Turn on the function. The operator applies the COC result after
checking it.
Auto: Turn on the function. Apply the COC result automatically.
The operator may change and retrieve the Tx power changing mode of each cell by
COC, either automatic or release, by using the following commands and
parameters:
SON_COC_PWR_CTRL_ENA In SON, determines the enable of the transmission power changing function
BLE by the cell outage compensation (COC) algorithm.
Off: Turn off the function.
Auto: Parameters may be changed by an algorithm.
Counters and KPIs

Samsung COC function uses the following statistical information.
Name
HO_INTRA IntraEnbSucc The number of Intra-eNB handover execution success to intra-eNB
neighbor cell
HO_X2_OUT InterX2OutAtt The number of X2 HO execution attempt to inter-eNB neighbor cell
HO_S1_OUT InterS1OutAttempt The number of S1 HO execution attempt to inter-eNB neighbor cell
REFERENCE
Chapter 9 SON
LTE-SO0702, Coverage and Capacity

Optimization
INTRODUCTION
Samsung CCO has the purpose of optimizing the coverage. Also, it is used as a
function of adjusting the transmission power of the RRH automatically to optimize
the coverage during the operation of LTE system.
Samsung CCO consists of three detailed functions as follows:
1 Detecting the occurrence of a coverage hole
oDetermines a coverage hole based on the information on the RLF report from
UE.
2 Collecting information
oCollects and reports the coverage holes, UE in and out and hand-out-related
statistics
3 Coverage optimization
oDetermines and sets the transmission power of the RRH based on the
information on the collected network status.
BENEFIT
To reduce the optimization costs during the operation by adjusting the
transmission power of the RRH depending on the network status
To guarantee less call drop and seamless service by adjusting the transmission
power of the RRH depending on the network status

Dependency:
RLF report from UE supported: To collect the RF environment information upon
the occurrence of the RLF of the UE, the UE must support the RLF report
function.
This feature supports only Macro and Outdoor Pico systems.
Limitations:
The transmission power of the RRH for the cells to participate in COC
determined by COC is impossible to be adjusted.
Chapter 9 SON
FEATURE DESCRIPTION
Architecture
The figure below shows Samsung CCO-related network architecture and the main
network entities include eNBs and the EMS:
The main functions of eNBs and EMS are as follows:

1 eNB
oDetects a coverage hole.
oCollects information to adjust the transmission power of the RRH (coverage
hole, UE in and out and hand-out-related statistics).
oReports collected information to the EMS.
oReceives transmission power of RRHs from the EMS.
oApplies transmission power of the RRH.
oDelivers information on changed transmission power of the RRH through
SIB2.
2 EMS
oCollects information to adjust the transmission power of the RRH from the
eNB (coverage hole, UE in and out, and hand-out-related statistics).
oDecides transmission power of the RRH based on the received information.
oDelivers transmission power by RRH to eNB.
Chapter 9 SON
CCO Function
CCO Operation Flow
The whole operating flow of Samsung CCO is as follows:
1 The EMS delivers the CCO-related PLD to eNB.

2 The eNB detects a coverage hole based on the RLF report from the terminal.
3 The eNB collects information on the coverage hole-related statistics to detect the
coverage hole during the Report period.
4 The eNB collects statistics related to UE in to and UE out from the cell managed
by itself during the Report period.
5 The eNB collects statistics related to the hand-out count to the neighbor cell
among the cells managed by it during the Report period.
6 The eNB delivers to EMS statistics relating to the collected coverage holes, UE
in and out and hand-out during the Report period.
7 The EMS decides transmission power of the RRH considering the network status
based on the information collected from eNB (coverage hole-related statistics)
at every CCO period.
8 The EMS delivers decided transmission power of the RRH to eNB.
Chapter 9 SON
9 The eNB changes cell configuration information based on the received

transmission power of the RRH and delivers the information on the changed
transmission power of the RRH to UE through SIB2.
CCO Algorithm
Samsung CCO has the purpose of optimizing the coverage. Also, it is used as a
function of adjusting the transmission power of the RRH automatically to optimize
the coverage during the operation of LTE system.
Samsung CCO operates as follows:
1 Detecting a coverage hole
oDetermining a coverage hole based on the information on the RLF report
from UE
2 Collecting and reporting information
oCollecting and reporting the coverage holes, UE In/Out and hand-out-related
statistics
3 Deciding the transmission power of the RRH
oDeciding transmission power of the RRH based on the information on the
collected network status
4 Configuring the transmission power of the RRH
oApplying transmission power of the RRH decided to the RRH
oChanging and delivering to UE the system parameters depending on the
decided transmission power of the RRH
Detailed explanation on the detailed operations of each algorithm is as follows:
(Sub2) Detecting a coverage hole
When the RLF is generated by using the RLF report information (serving
RSRP, serving RSRQ or neighbor RSRP) from UE, the eNB determines the
occurrence of the coverage hole if the predicted SINR is less than the SINR
threshold.
(Sub2) Collecting and reporting coverage hole statistics
When a coverage hole is detected during the CCO period, eNB calculates the
difference of the transmission power of the serving cell or neighbor cell. Also,
the both cells are having the same frequency with serving cell to remove the
coverage hole and collect the coverage hole-related statistics (count of
calculating difference of transmission power, and sum of the difference of the
transmission power). Besides, eNB collects the statistics relating to UE in to,
or UE out from, the cell managed by it during the Report period. The eNB
reports to the EMS the statistics relating to the collected coverage holes, UE
in-and-out and hand-out during the Report period.
Deciding the transmission power of the RRH
Chapter 9 SON
The EMS calculates the transmission power of the cell in every CCO period to
remove the coverage hole by using the statistical information relating to the
coverage hole, UE in-and-out and hand-out received from eNBs (count of
calculating difference of transmission power, and sum of the difference of the
transmission power) which are collected during CCO period as follows:
aEMS calculates each cells count of calculating difference of transmission
power and the count of UE in-and-out based on the statistical information
from eNB. For the count of calculating difference of transmission power
and the count of UE in-and-out, only the information that are collected by
neighbor cell with the same cell type (macro cell or pico cell).
bEMS calculates the ratio of the coverage hole for the current transmission
power of the cell by using the count of calculating difference of
transmission power and the count of UE in-and-out as shown below, and
calculates average coverage hole ratio based on IIR filtering.
Coverage hole ratio = count of calculating difference of transmission
power/UE in and out count
The above average coverage hole ratio for the transmission power of the
cell represents the degree of the occurrence of the coverage hole based on
the transmission power of the cell.
cEMS calculates sum of the difference of transmission power and the count of
calculating difference of transmission power by using the information on
the statistics from eNB. For the calculation of each cells sum of the
difference of transmission power and the count of calculating difference of
transmission power, only the information collected by neighbor cell with
the same cell type (macro cell or pico cell) is considered.
dEMS calculates the candidate transmission power for each cell to remove the
coverage hole by using the sum of the difference of transmission power
and the count of calculating difference of transmission power as follows:
Candidate transmission power = current transmission power + (the sum
of the difference of the transmission power/count of calculating
difference of transmission power)
eEMS decides the transmission power of each cell by using the average
coverage hole ratio within the scope of [candidate transmission power and
current transmission power] of the cell in a direction to removing the
coverage hole.
However, the collected statistical information for the cell whose UE in-and-out
count is less than UE in-and-out count threshold is saved and the transmission
power is maintained as it is.
Additionally, to prevent the coverage hole area from being increased by
reducing the transmission power of the cell and the neighbor cell, if there is a
neighbor cell whose hand-out account exceeds the hand-out threshold and
whose state of transmission power is reduced for the cell whose transmission
power is determined to be reduced through the aforementioned course, the
transmission power is prohibited from being reduced and the current
transmission power is maintained.
Chapter 9 SON
(Sub2) Configuring the transmission power of the RRH

EMS delivers the decided transmission power of the RRH of the cell to eNB.
The eNB configures the RRH transmission power of the cell with that of the
cell received from the EMS. Also, it transmits information on the changed
RRH transmission power of the cell to UE through SIB2.
SYSTEM OPERATION
How to Activate
The operator sets the CCO operation to auto or manual' of the
SON_CCO_FUNC_ENABLE value of eNB to operate the CCO to activate the
CCO operation. In addition, the operator sets the
SON_CCO_PWR_CTRL_ENABLE value of the cell to change the transmission
power to auto through the CCO operation.
However, the SON_CCO_PWR_CTRL_ENABLE value cannot be applied as
auto for the cell in the eNB whose SON_CCO_FUNC_ENABLE is OFF.
The CCO operation-related parameter settings are as follows:
POWER_RANGE: Scope of adjusting the transmission power
POWER_STEP_SIZE: Step size used to calculate the difference of the
transmission power
COVERAGE_HOLE_SINR: SINR threshold corresponding to the coverage hole
UE_IN_OUT_THRESHOLD: UE in-and-out count threshold
COVERAGE_HOLE_RATIO_EXPIRE_TIME: Average coverage hole ratio
maintaining time
Key Parameters
The operator may change and retrieve the operating mode, either automatic or
release, in Samsung CCO by using the following commands and parameters:
SON_CCO_FUNC_ENABLE In SON, determines the enable of the CCO (coverage & capacity
optimization) SON.
Off: Turn off the function
Auto: The changed parameter is automatically applied to operation when
the parameter is changed by the algorithm.
The operator may change and retrieve the Tx power changing mode of each cell by
CCO, either automatic or release, by using the following commands and
parameters:
Chapter 9 SON
SON_CCO_PWR_CTRL_ENA In SON, decide enable of the transmission power changing function by CCO.
BLE Off: Turn off the function
Auto: Parameters may be changed by an algorithm.
Counters and KPIs

Samsung CCO function uses the following statistical information.
Name
HO_INTRA IntraEnbSucc The number of Intra-eNB handover execution success to intra-
eNB neighbor cell
HO_X2_OUT InterX2OutAtt The number of X2 HO execution attempt to inter-eNB neighbor
cell
HO_S1_OUT InterS1OutAttempt The number of S1 HO execution attempt to inter-eNB neighbor
cell
HO_X2_IN InterX2InSucc The number of X2 HO execution success from inter-eNB
neighbor cell to own eNB cell
HO_S1_IN InterS1InSucc The number of S1 HO execution success from inter-eNB
neighbor cell to own eNB cell
RRC_REESTAB ConnReEstabSucc The number of success of RRC_REESTAB
MRO_RLF TooLateHoRlfBeforeT RLF occurrence count by too late HO before HO triggering
riggering
REFERENCE
Chapter 9 SON
LTE-SO0802, Cell On/Off in Multi-carrier Sites

INTRODUCTION
This feature supports macro cell on/off function in multi-carrier environment. By
switching off unnecessary cells, the power consumption can be reduced. Moreover,
RU transmission power can be saved when all cells in the RU are switched off.
To minimize service impact to UEs, this feature should be operated in the
environment that multi-carriers are overlapped in a co-located site.
Two types of cell on/off mechanisms can be supported: Predefined Time schedule
based (SSR4.0/SLR5.0) and Traffic load based (next PKG).
BENEFIT
Power consumption can be reduced by switching off unnecessary cells.

Limitation
Multi cells need to be overlapped in a co-located site
The energy saving effect can be different according to HW configuration
FEATURE DESCRIPTION
Architecture
The architecture of Cell on/off function is as follow.
Chapter 9 SON
Operators can configure policies for Cell on/off function using EMS. The function
operates according to the configured policies.
The role of each blocks participating in this function is as follow.
1 EMS
EMS provides GUI for configuring policies for operator and transfers the
configured policies to eNB.
2 Call block
Call block executes Cell on/off function according to operator configured
policies. It will release calls in the cell at cell switch off condition and transfer
the result of cell switch off to neighbor cells. Moreover, cell activation can be
executed when traffic load is over threshold.
3 OAM
OAM block transfers Tx on/off message to RU according to the result of this
function and HW configuration.
4 RU
RU executes Tx on/off according to message from OAM block.
Operation
The concept of cell off operation is as follow.
Chapter 9 SON
Cell switch off operation can be executed only for the cells that are co-located in a
same site. The target cell to switch off will release existing call by forced handover.
When all calls are released in the cell, the cell will be switched off and the cell is
managed as dormant cell.
Pre-defined Time Schedule based ES
Time schedule based function operates cell switch on/off according to the time
schedule configured by operator. The policies that need to be configured by
operator are as follow.
Function on/off per cell
Co-located cell list per cell
Time schedule for on/off per cell
Traffic load threshold for cell switch off or cell activation
Whether to execute forced handover and timer configuration
Operation Flow for Cell on/off
Overall operation flow for pre-defined time schedule based Cell on/off is as follow.
Chapter 9 SON
Steps Description
1 Policies configured by operator are transferred to eNB.
2 Cells monitor periodically for the scheduled time.
3 At the scheduled time, the cell checks whether the traffic load threshold is configured by operator.
4 If traffic load threshold is configured by operator, the cell compares traffic load with the threshold.
If traffic load is less than threshold, the next process will be executed. Else, execute the
comparison at the next period.
Chapter 9 SON
Steps Description
5 The cell should block new calls.
6 Check whether all calls in the cell are released. If some calls are remained and the forced
handover option is configured by operator, the forced handover function is executed. If any call
remains after the Timer expires, the all calls are released.
7 If all calls are released in the cell, the cell will be switched off. When the cell becomes dormant
cell, it transfers eNB Configuration Update message to neighbor cells to inform cell switch off.
8 RU Tx off will be executed if all cells in the RU are switched off.
9 Execute cell switch on when the scheduled time ends. When the cell switches on, it transfers eNB
Configuration Update message to some of neighbor cells to inform cell switch on.
10 RU Tx on will be executed if RU Tx off is executed by this function.
Operation Flow for Cell activation

Cell can activate dormant cells when traffic load is high by Cell Activation
message. Operation flow for cell activation is as follow.
Steps Description
1 If traffic load threshold is configured by operator, the cell compares traffic load with the threshold.
2 If traffic load is higher than threshold, the cell transfers Cell Activation message to some of
neighbor dormant cells. Else, execute the comparison at the next period.
3 Dormant cells executes cell switch on when they receive Cell Activation message.
Chapter 9 SON
SYSTEM OPERATION
How to Activate
Use the command CHG-GRCREL-CONF to set esCellOffMode to
ScheduleBased. Operator can disable this feature by setting the parameter to
Off.
If you want to use forced handover for faster graceful cell off, use the command
CHG-GRCREL-CONF to set esCellOffMode to withForcedHo.
If you want to use timer based release for active calls, use the command CHG-
GRCREL-CONF to set esCellOffTimerEnable to On.
Use the command CHG-GRCREL-CONF to set esCellOffTimer, when you want
to reconfigure timer for timer based release.
If FA priority of the cell is set to 7, the cell is not off although esCellOffMode of
a cell is set to ScheduleBased.
Key Parameters
RTRV-EUTRA-FA/CHG-EUTRA-FA
PRIORITY_FOR_ES_CELL_ON_OFF This is priority for FA of cell on target. The cells of FA allocated
priority 7 is excluded in candidate cell off.
RTRV-SONFN-ENB/CHG-SONFN-ENB
CELL_OFF_LOAD_THRESHOLD This is a threshold parameter for triggering cell off.
A cell load is lower than this threshold for triggering cell off.
CELL_ACT_LOAD_THRESHOLD This is a threshold parameter for activating cell on.
It is lower than this threshold for triggering cell off.
When a cell load is bigger than this threshold, the cell activates NBR
dormant cells.
RTRV-SONFN-CELL/CHG-SONFN-CELL
ES_CELL_ON_OFF_ENABLE This parameter indicates whether to enable the ES Cell On/Off.
There are three modes (Off, ScheduleBased, TrafficBased). If the
parameter is Off, this cell is excluded Cell On/Off.
RTRV-GRCREL-CONF/CHG-GRCREL-CONF
ES_CELL_OFF_MODE This parameter is used to set cell-off for energy saving operation mode when
estate, and esModeType (of CellEnergySavingStatus) is transited to enable
and cell off. There are normal and withForcedHo that triggers On-Demand
Chapter 9 SON
Forced HO at transition to cell-off.
ES_CELL_OFF_TIMER_ENAB This parameter is used to enable or disable timer operation. If you set this
LE parameter to ON, the timer is triggered at transition to set cell-off for energy
saving. And then, it make eNB forcibly release remained active calls in the
cell under cell-off for energy saving, when timer is expired.
ES_CELL_OFF_TIMER This parameter is used to set timer duration in esCellOffTimer.
Counters and KPIs

ODHO_X2_OUT OnDemandHoOutAtt The count of handover attempt by On-
demand HO triggering
OnDemandHoOutSucc The count of handover success by On-
ODHO_X2_IN OnDemandHoInAtt The count of hand-in attempt by On-
OnDemandHoInSucc The count of hand-in success by On-
ODHO_REDIRECTION RedirectionToLTEByOnDemand The count of redirection to LTE by On-
Ho demand HO triggering
RedirectionToWCDMAByOnDe The count of redirection to WCDMA by
mandHo On-demand HO triggering.
RedirectionToGERANByOnDem The count of redirection to GERAN by
andHo On-demand HO triggering
RedirectionToHRPDByOnDema The count of redirection to HRPD by On-
ndHo demand HO triggering
CcoToGERANByOnDemandHo The count of CCO to GERAN by On-
TIMER_RELEASE ReleaseCntByTimer The count of release by timer expiration
REFERENCE
[1] 3GPP TS 36.423 (Rel.11)
[2] 3GPP TS 32.551 (Rel.11)
[3] 3GPP TS 36.300 (Rel.12)
Chapter 9 SON
LTE-SO0804, DL MIMO TX Branch On/Off

INTRODUCTION
The Energy Saving (ES) function controls the Downlink (DL) Transmitter (Tx)
Branch to lower the power consumption of the eNB. The purpose of Samsung ES
is to reduce the operators OPEX and carbon dioxide emission by saving power
consumption of the eNB without any coverage or QoS loss during the eNB
operation.
The technology for DL Tx Branch On/Off ES disables some transmission branches
of the RU with two or more downlink transmitting branches and lower power
consumption by transmitting the downlink data only through the other enabled
branches. At the time, the branch means the combination of PA modules
connected with transmission and reception antennas.
The technology can be applied to the LTE system to which two or more
transmission antennas are employed and Samsung eNB with the ES function
controls the power amplifier (PA) and Tx antenna of the radio unit (RU) and the
modem of the digital unit (DU) during the operation of the system to lower power
consumption.
The Samsung eNB always operates in the Normal Mode if the Samsung ES
function is not active; The Samsung eNB operates in either of the Saving Mode or
Normal Mode otherwise. When the Samsung eNB works in the Saving Mode, the
serving DL traffic is limited to a level lower than a certain level.
The following is an example of the operation of the Saving Mode and the Normal
Mode in case of the RU with two Tx branches:
Normal Mode
oTx branch 0 (Tx antenna-0 and the related PA module): enabled
oAvailable RB allocation: 100% of system BW
Saving Mode
oTx branch 1 (Tx antenna-1 and the related PA module): disabled
oAvailable RB allocation: about half of system BW
The Samsung eNB that supports the ES function provides the following three ES
executing options:
ES Function OFF
Manual Apply (Pre-defined time schedule based ES)
Auto Apply (Traffic analysis based ES)
Chapter 9 SON
The system operator may not operate the ES function OFF or run the ES function
ON in the following two ways:
The system operator may configure the time of the eNB working in the Saving
Mode by day and the eNB works in the Saving Mode according to the
schedule.
The eNB decides the operation mode by itself. The eNB predicts DL traffic usage
at an interval and decides whether it works in the Saving Mode or the Normal
Mode by using it.
BENEFIT
Reduction of OPEX without coverage/QoS loss.

Dependency
Channel card with Samsung Baseband Modem 8200 or later.
Limitation
RU with 2 or more independently controllable Tx branches (antennas and power
amplifiers).
For SLR3.1, exactly 2 Tx branches and 2 CRS system.
Disabling Energy saving function is needed for under 5MHz systems.
oSamsung systems use at least 18RBs for SIB
oRB should be restricted to 50% when operating in Energy saving mode
oFor under 5MHz bandwidth, available RB will be under 18 RBs at Energy
saving mode
oIn this case, Energy saving mode cannot be operated or SIB cannot be
transferred to UE.
FEATURE DESCRIPTION
Architecture
The following figure shows the structure of the Samsung ES function. The EMS
and eNB have blocks related to the ES function.
Chapter 9 SON
The role of the ES-related function of the EMS SON-manager is to support the
system operator to set ES function-related settings using the PLD and to transmit
the settings to the eNB OAM. The setup information transmitted to the eNB OAM
by the SON-manager is largely divided into the following three.
Enable/disable settings of the ES function
Automatic apply (traffic analysis/prediction)-related parameter settings
Manual apply (pre-defined schedule based ES)-related parameter settings
The EMS SON-manager also receives reports on the operation status of the eNBs
ES function.
Function blocks for the implementation of the ES in the eNB are the SON-agent,
OAM, MODEM, scheduler and RU.
1 The eNB SON-agent determines the eNBs operating mode based on the time-
varying traffic information collected during the system operation and allows
the MODEM, scheduler and the RU to perform operations set by each
operating mode. To do this, the SON-agent consists of the following function
blocks.
2 The eNB OAM collects PM statistics information and provides it to the SON-
Agent. Also, the OAM performs as a bridge of information transfer between
the EMS SON-manager and the eNB SON-agent.
3 When the eNB SON-agent decides the eNB operating mode, the eNB scheduler
block limits the number of scheduled RBs or releases the limitation of the
number according to the decided eNB operating mode. In addition, the
scheduler delivers the operating mode decided in the modem.
4 The modem creates an appropriate signal by Tx branch depending on the
received operating mode from the scheduler.
5 The eNB RU control module is a module in the transceiver of the RU and
performs the role of actually implementing the Saving mode-related
commands by communicating with the Saving mode management module of
the SON-agent. In other words, it enables or disables some Tx branches.
(Disable or Enable).
Chapter 9 SON
Operation
The following figure describes overall procedure of Samsung ES function
described in this document.
The SON-agent ES block of the eNB performs the following operations every one
hour.
Chapter 9 SON
1 Analyzes the traffic load for D days from the past to the present. (Analyze traffic
load)
2 Predicts the traffic load required for the upcoming 1 hour based on this
information. (Predict traffic load)
3 Determines the mode to perform for the upcoming 1 hour based on the traffic
analysis and prediction. (Determine whether to enter the Saving Mode or not)
4 Enables the eNB to perform the determined operations.
If the eNB was decided to operate the Saving Mode during the interval (i) as a
time segment at the unit of every one coming hour, the SON-agent of the eNB
checks whether the failure of the eNB occurred every refresh period of the PM
statistical data (5 or 15 minutes) or the observed DL traffic was rapidly increased.
Based on the result, the eNB temporarily suspends the operation of the Saving
Mode during the shorter length of the time segment Interval (i, p) and returns to
the Normal Mode.
Traffic Prediction
The traffic load for the upcoming 1 hour is predicted as the larger value of the
following two metrics.
Time series average of the traffic load at the same hour for past D days
Weighted moving average of the traffic load for the recent M hours
Determination of Execution Mode
The Samsung ES function determines the operation mode for the upcoming 1 hour
every hour on the hour. The eNB operates in the Saving Mode for 1 hour if the
traffic load predicted should be below the threshold defined by Samsung ES
functionality. The threshold is defined in below table. Provided, however, that the
value may be changed depending on SLR version and the provided providers.
Mode Threshold Restriction for RB Allocation DL Tx Branch
(Predicted Traffic)
Normal Above 24 % No restriction All branches are enabled
ES Below 24 % Up to 48 % Some branches are disabled
Test for Stopping of Saving Mode Operation

The Samsung ES function checks whether to continue the Saving Mode operation
every time it acquires the statistics related to the retransmission of DL data. If any
of the following three conditions is satisfied, the eNB operates temporarily in the
Normal Mode regardless of the current execution mode.
The ratio of the number of the 4th retransmission to the sum of the number of
initial, 2nd, 3rd, and 4th transmission is higher than 1% (Possible to be
changed).
The block error rate of the 4th retransmission is larger than 10% (Possible to be
changed).
The RLF ratio is larger than 1% (Possible to be changed).
Chapter 9 SON
SYSTEM OPERATION
How to Activate
Execute the command RTRV/CHG-SONFN-CELL to retrieve/change the
operation mode and information of the Self-Organizing Network (SON)
function for each Cell.
Execute the command RTRV/CHG-ES-SCHED to retrieve/change the schedule
information of the Self-Organizing Network (SON) Energy Saving (ES)
function.
Execute the command RTRV/CHG-ES-COM to retrieve/change the ES Mode
Common information of the Self-Organizing Network (SON) Energy Saving
(ES) function.
Key Parameters
ENERGY_SAVINGS_ENABLE Controls SON Energy Saving in 3 modes.
Off: The Energy Saving functions except for traffic analysis is disabled.
Manual: The Energy Saving function in accordance with the schedule set by
the operator is enabled.
Auto: The Energy Saving functions based on the information obtained from
traffic analysis is enabled.
CHG-ES-SCHED/RTRV-ES-SCHED
WEEK_DAY The day for which the Energy Saving function is operated according to the
schedule.
HOUR This parameter is the activation time (h) of the energy saving feature
according to the schedule.
ES_STATE This setting is required for enabling the energy saving feature using the
schedule.
Inactive: The energy saving feature does not run.
Active: The energy saving feature runs based on the schedule.
SCHEDULED_ES_MODE ES Mode type in which the Energy Saving function is operated during one
hour according to the schedule.
CHG-ES-COM/RTRV-ES-COM
DATA_VALIDITY This parameter is the number of days of traffic analysis to be used in
calculating the estimates for determining Energy Saving (ES) mode. For
traffic estimation, the average traffic load statistics are calculated for the
specified time over the last 15 days or the last 30 days as determined by this
Chapter 9 SON
parameter.
MOVING_AVERAGE_VALIDIT This parameter determines how many hours of data are used for calculating
Y the traffic estimates. When this parameter value is determined, it is weighted
with the MOVING_AVERAGE_WEIGHT parameter for calculating the traffic
estimates.
MOVING_AVERAGE_WEIGH This parameter is the weight of the recent hours to apply moving average for
T calculating the traffic estimates. When the number of hours (h) of data to use
is determined by the MOVING_AVERAGE_VALIDITY parameter, this
parameter value is used as weights for data of each hour for calculation.
Also, the first weight of this parameter indicates the most recent hour. If
MOVING_AVERAGE_VALIDITY is 2 hours and this parameter is
50,50,0,0,0,0,0,0,0,0, it means that a weighting of 50% is applied to the last
2 hours.
RE_TX_THRESHOLD This parameter is the 4th Re Tx (third retransmission count of PDSCH
HARQ) threshold value for determining system abnormality. The unit used
is %. This refers to the ratio of the 4th value over the sum of the 1st through
4th values of the no. of DL transmission values in the statistics item DL-
HARQ status. If the no. of DL transmission value exceeds the major alarm
threshold value, it is deemed as a system abnormality. Before starting the
Self-Organizing Network (SON) Energy Saving (ES) feature, it must be
determined whether the current system status is normal. Therefore, if the
system is in abnormal status, the energy saving mode is disabled and the
normal mode is enabled. The energy saving feature remains disabled until
the system abnormality is resolved.
BLER_THRESHOLD This parameter is the 4th Re Tx BLER (PDSCH BLER for the third HARQ
retransmission) threshold value for determining system abnormality. The unit
used is %. This means the BLER for the 4th transmission among the DL
residual BLER values of the statistics item DL-HARQ status. If the DL
residual BLER value exceeds the major alarm threshold value, it is deemed
as a system abnormality. Before starting the Self-Organizing Network (SON)
Energy Saving (ES) feature, it must be determined whether the current
system status is normal. Therefore, if the system is in abnormal status, the
energy saving mode is disabled and the normal mode is enabled. The
energy saving feature remains disabled until the system abnormality is
resolved.
RLF_THRESHOLD RLF Threshold for system abnormality.
ALLOCATION_REDUCTION_ Allocation Reduction Factor for Traffic Abnormality
FACTOR
AUTO_ES_MODE ES Mode when Energy Saving is operated by Auto Apply.
RTRV-ES-TYPE
ES_MODE_INDEX This parameter is the index used for saving the information of each Energy
Saving (ES) mode.
ES_MODE_TYPE This parameter is the Energy Saving (ES) mode to be activated when the
traffic load estimate is lower than ES_MODE_ENTERING_THRESHOLD
and ES_MODE_LEAVING_THRESHOLD.
Normal: Runs on Normal Mode Voltage and RB count.
Mode(#): Runs with variable voltage and RB count according to the mode.
The higher the mode, the less voltage and RB count are used to save
energy.
ES_MODE_PREDICTION_TH ES Mode Prediction Threshold
RESHOLD
Chapter 9 SON
ES_MODE_RB_ALLOCATION ES Mode RB Allocation Threshold
_THRESHOLD
Counters and KPIs

The eNB SON agent predicts the traffic for each cell during the specified time
interval by using the following PM statistic data items.
Counter Description
DL PRB Usage PRB usage of Downlink DTCH traffic
REFERENCE
[4] 3GPP 32.541: E-UTRAN; OAM Requirements for Self Healing Use Cases
Chapter 9 SON
LTE-SO0901, Minimization Drive Test

Optimization
INTRODUCTION
Minimization of Drive Test (MDT) is a standardized mechanism to collect the
network performance measurements from the commercial UEs with possibly the
location information. The collected UE measurement results can be utilized for
various purposes, for example, network parameter optimization, coverage hole
detection, and so on. Operator can save the cost for network optimization by using
MDT feature.
Samsung MDT supports two modes of operations, that is, Immediate MDT and
Logged MDT. Immediate MDT is targeted on the UEs in Active mode while
Logged MDT is performed by the UEs in Idle mode.
BENEFIT
Operator can save the cost for collecting the network performance measurement
data.
End-used service quality can be enhanced thanks to efficient network
optimization conducted by using MDT data

Dependency
For Signaling-based MDT, the core network entities shall support the
corresponding functions.
For Management-based MDT, RAN EMS shall support the corresponding
functions.
For Logged MDT, UE shall support the corresponding functions (Rel.10 or later).
Limitation
Rel.11 MDT functions are not supported.
FEATURE DESCRIPTION
Optimization of radio network performance is very important task for mobile
operators. Conventionally, operators conduct drive test to collect the radio
measurement, and parameter optimization is performed based on the gathered
information. Mobile operators have spent a lot of time and money for conventional
drive test and network optimization.
Chapter 9 SON
Minimization of Drive Test (MDT) feature is introduced in 3GPP Rel.10 to

provide more cost-efficient method to measure and optimize the network
performance. Since the mobile devices exist over whole network areas, MDT
procedure utilizes UE's measurement capability to acquire the information of
network. Through the standardized MDT procedures, operators order some UEs to
measure the network performance, and collect the measured data in the server
which is called Trace Collection Entity (TCE) in 3GPP specification. Then, the
collected information can used for many purposes including coverage hole
detection, capacity optimization, and so on.
By using this feature, the operator can reduce the cost for gathering the
measurement data and optimizing the network parameters. Furthermore, MDT can
be more efficient method than the conventional drive test for some areas where the
conventional drive test is not very efficient, for example, in-building environment.
MDT Configuration parameters may be delivered to the target UE and
measurement data can be collected by the UE itself during idle state (Logged
MDT), or MDT data collection can be done at the serving eNB by reusing the
existing RRM procedures while the target UE stays in connected state (Immediate
MDT).
There are two types of methods to configure and manage MDT, which are
Signaling-based MDT and Management-based MDT.
Signaling based MDT: Used to collect the measurement data of a specific UE
based on IMSI or IMEI SV. The MDT configuration message is sent from
MME to eNB.
Management based MDT: Used to collect the measurement data in a specific area.
The MDT configuration message is sent directly from RAN OAM server to
(set of) cells without specifying target UEs. Some UEs in the area are chosen
by eNB for MDT operations.
Because MDT management reuses the existing Trace architecture, the two
methods have almost same architecture as Signaling-based and Management-based
Trace methods, respectively.
The following table summarizes the differences of Signaling and Management-
based MDTs.
Signaling-based MDT Management-based MDT
Configuration path (Core) OAM HSS MME eNB (RAN) OAM eNB
Reusing trace Signaling based trace, for example, Call Management based trace, for example,
procedures Trace Cell Traffic Trace
Target of Specific subscriber (IMSI) or equipment Specific area, for example, cells, TAs
configuration (IMEI, IMEI SV)
Target UE selection Target UE selection by OAM Target UE selection by eNB

User consent User consent checking of the specific UE User consent checking is done by eNB at
checking can be done by HSS before delivering the UE selection based on the saved UE
configuration message. context
Session continuity MDT parameter transfer during handover No MDT session continuity on cell change
on cell change (Only user consent information can be
transferred)
Chapter 9 SON
Supported MDTs Both Logged and Immediate MDT Both Logged and Immediate MDT
In Signaling-based MDT, a specific UE is chosen by OAM based on IMSI or IMEI

SV. The configuration message including the corresponding MDT parameters is
sent to HSS for checking the user consent. If subscription data of the user allows
MDT, the HSS sends MDT activation message to serving MME of the UE, and the
MME sends it to the serving eNB.
In Management-based MDT, a specific area is chosen for measurement data
collection with MDT parameters. The eNBs in the area choose some UEs and data
collection is done based on the received configuration. The user consent for MDT
is saved in UE context generally during UE attach, and hence the serving eNB can
choose only the UEs which allow Management based MDT data collection.
The following figure shows concepts for Signaling and Management-based MDT
configuration.
For UE selection in Management-based MDT, Samsung MDT provides the

following options to restrict the scope of chosen users.
UE capability option: 1) All UEs, 2) Rel. 10 or later UEs only, 3) Rel. 10 or later
+ standalone GNSS capable UEs only. Operator may want to collect only the
measurement data with high accuracy.
Chapter 9 SON
UE pickup rate: The probability that a UE is chosen for MDT operation when the
UE satisfies all the requirements for UE selection. Operator may not want to
get measurement data from all the UEs who satisfy the requirements due to
large overhead.
In the RANs configuration and operation aspects, there are two types of MDT,
which are Immediate and Logged MDT. Data collection for Immediate MDT is
performed for the connected UEs by eNB, while Logged MDT data collection is
performed by each UE itself during idle mode. Immediate and Logged MDT can
be configured by both Signaling-based and Management-based MDT
configuration procedures.
In Immediate MDT, the following types of measurement data can be collected
while the UE is in connected mode.
M1: RSRP and RSRQ measurement by UE
M2: Power Headroom (PH) measurement by UE
M3: Uplink Received Interference Power of the connected cell (Rel.11)
M4: DL/UL Data Volume of the UE per QCI (Rel.11)
M6: Collecting all the event-triggered measurement reports configured for RRM
purpose (Rel.11)
For collecting data for M1, the eNBs RRC configures measurement reporting
trigger to the chosen UE. Reporting trigger for M1 can be 1) Periodic or 2) Serving
cell becomes worse than threshold; Event A2. The UE sends the measurement
report (RSRP and/or RSRQ of serving and neighboring cells) to the serving eNB if
the reporting condition is met, and the serving eNB collects the data and sends it to
the TCE.
On the other hand, no RRC reporting trigger is required for M2 because PHR is
carried by MAC signaling. If MDT data collection for M2 is configured, the
serving eNB collects the PHR information triggered by normal MAC mechanisms.
Similarly, M3 Received Interference Power and M4 Data Volume measurements
are also performed by the eNB itself so that no additional RRC signaling is
required. If M6 is set, all the existing event-triggered measurement reports
configured for RRM purposes are collected, for example, Event A1, A2, A3, A4,
A5, A6, B1, and B2 events. Differently from M1, RRC measurement configuration
is not additionally configured solely for MDT purpose. However the measured
metric is similar to M1, which are RSRP or RSRQ.
Chapter 9 SON
Location information can be included in the measured data. Two positioning

methods are supported, that is, Standalone GNSS/GPS and Enhanced Cell ID (E-
CID). If GNSS/GPS positioning method is chosen, the serving eNB request UEs to
include standalone GNSS/GPS location result as the best effort manner. Then the
standalone GNSS/GPS supporting UE can include the detailed location
information if data available. If E-CID method is chosen, the serving eNB collects
eNB Rx-Tx Time Difference and UE Rx-Tx Time Difference which are the raw
data for E-CID. The serving eNB sends the data to TCE, but calculation of detailed
location based on collected data is out of scope of the eNB. Among E-CID raw
data metrics defined in 3GPP, Angle of Arrival (AoA) trace is not supported. If
either GNSS/GPS or E-CID related data is not available, location may be
estimated based on signal measurement results for M1, that is, RF fingerprint,
according to the TCE implementation.
Configuration message of Immediate MDT mainly contains the following
information:
List of measurements: M1 (RSRP/RSRQ) and/or M2 (PHR) and/or M3
(Received Interference Power) and/or M4 (Data Volume) and/or M6
(Measurement report collection triggered by RRM events)
Reporting trigger: Periodic or Event A2 (Only for M1)
Report amount: Number of measurement reports sent (Only for M1 + Periodic)
Event threshold: Reporting threshold for measurement report (Only for M1 +
Event A2)
Area scope: Area scope where the MDT data collection should be conducted
Positioning method: GNSS/GPS and/or E-CID
The eNB immediately starts the MDT operation when it receives the configuration
message and the target user is selected. Because Immediate MDT reuses the
existing 3GPP standard procedures, the operation is mostly transparent to the UEs.
In Logged MDT, only periodic downlink pilot strength measurement can be
performed during idle mode operations. Configuration parameters for Logged
MDT are sent to the UE through RRC signaling procedure after the UE transits to
the connected state. However, the actual data collection is done while the UE is in
idle state. On reception the Logged MDT configuration message over RRC,
Logged MDT-capable UE saves the parameters. Then, the UE starts to collect data
after the UEs state is changed to idle state by considering the saved MDT
configuration parameters. After the measurement data is collected during idle
mode, UE notifies existence of logged MDT data during RRC connection
establishment procedures. Then, the eNB may request the UE to send the logged
data, and the received data is sent to the proper TCE based on TCE ID in the
logged data.
Configuration message of Logged MDT mainly contains the following
information:
Logging duration: Logging duration: The timer value for completely stopping the
logging job. If the UEs state changes from idle to connected state, logging
stops for a moment. However, the timer continues independent of state
changes. Logging will continue if the UE goes to idle before this timer expires.
Chapter 9 SON
Logging interval: Periodicity of measurement during idle mode

Trace Reference and Trace Recording Session Reference: Uniquely identifying
the MDT session in the whole PLMN
Area scope: Area scope where the MDT data collection should be conducted
TCE ID: The ID which uniquely identifying the TCE where the data should be
delivered. All the eNBs maintain the unique mapping table for TCE ID to TCE
IP address.
The following figure describes the concepts for Immediate and Logged MDT
operation.
Additionally, UE RLF reporting (by Rel.9 or later UE) trace and RRC Connection
Establishment Failure (RCEF) reporting (by Rel.11 or later UE) trace are also
supported as management based MDT trace. RAN EMS orders some cells to trace
the RLF or RCEF reports sent by UEs. The, the eNB does not perform any specific
triggering action for the trace but just collects the RLF or RCEF information when
the reporting is received in the specified area. The collected information is sent to
the TCE server.
Chapter 9 SON
SYSTEM OPERATION
How to Activate
1 Signalling Based Immediate MDT
oThe SIG_BASED_IMMEDIATE_MDT_ALLOWED (system parameter)
must be set to True in the eNB.
oProper information for TCE must be set.
2 Signalling Based Logged MDT
oThe SIG_BASED_LOGGED_MDT_ALLOWED (system parameter) must
be set to True in the eNB.
3 Management Based Immediate MDT
oThe MGMT_BASED_IMMEDIATE_MDT_ALLOWED (system parameter)
oConfigures the MDT parameters and activates immediate MDT trace from
the LSM.
4 Management Based Logged MDT
oThe MGMT_BASED_LOGGED_MDT_ALLOWED (system parameter)
oConfigures the MDT parameters and activates logged MDT trace from the
LSM.
Key Parameters
CHG-MDTCTRL-PARA/RTRV-MDTCTRL-PARA
SIG_BASED_IMMEDIATE_MD This parameter shows the whether to permit to the Signaling Based
T_ALLOWED Immediate MDT on demand.
False: Signaling Based Immediate MDT request is not allowed.
True: Signaling Based Immediate MDT request is allowed.
SIG_BASED_LOGGED_MDT_ This parameter shows the whether to permit to the Signaling Based Logged
ALLOWED MDT on demand.
False: Signaling Based Logged MDT request is not allowed.
True: Signaling Based Logged MDT request is allowed.
MGMT_BASED_IMMEDIATE_ This parameter shows the whether to permit to the Management Based
MDT_ALLOWED Immediate MDT on demand.
False: Management Based Immediate MDT request is not allowed.
True: Management Based Immediate MDT request is allowed.
MGMT_BASED_LOGGED_MD This parameter specifies the whether to permit to the Management Based
T_ALLOWED Logged MDT (Minimization Drive Test) on demand.
False: Management Based Logged MDT request is not allowed.
Chapter 9 SON
True: Management Based Logged MDT request is allowed.
MDT_UE_PICKUP_RATE This parameter represents the selection rate which it uses when selecting
the Management Based MDT object UE. If the random number generated
between 0 is this value or less, select as MDT object UE.
Counters and KPIs

REFERENCE
[1] 3GPP 37.320: UTRA and E-UTRA; Radio measurement collection for
Minimization of Drive Tests (MDT); Overall description; Stage 2 (Release 10)
[2] 3GPP 36.300: E-UTRA and E-UTRAN; overall description Stage 2 (Release
10)
[4] 3GPP 36.413: E-UTRAN; S1 Application Protocol (S1AP) (Release 10)
[5] 3GPP 36.423: E-UTRAN; X2 Application Protocol (X2AP) (Release 10)
[6] 3GPP 32.421: Telecommunication management; Subscriber and equipment
trace; Trace concepts and requirements (Release 10)
trace; Trace control and configuration management (Release 10)
trace; Trace data definition and management (Release 10)
Chapter 9 SON
LTE-SO2011, Drive Test Optimization (Coverage

and Capacity Optimization)
INTRODUCTION
Samsung Drive Test Optimization (DTO) is a solution for automatically
optimizing the network at initial stage of LTE system. This function can reduce the
OPEX used to optimize the network at initial stage through automated initial
network optimization.
Samsung DTO provides the following functions at the steps of initial network
optimization:
Step Function
1 Drive test Collecting, reporting and making automated the RF information.
1-1) Install the DM software that has the real time reporting function (at the interval of one
second) to the terminal for testing to make report to a remote control node (SSOM).
1-2) If test UE supports 3GPP MDT with location measurement/report capability, the
feature can be operated based on MDT without DM software through configuration in
SSOM.
2) SSOM displays RF information reported by the DM software/MDT in real time.
2 Analyze Finding a problem section: Find and display a RF performance degradation area.
Analyzing RF environment: Display the information on the RF environment (RSRP and
SINR) on the optimized clusters through the heat map and the CDF.
3 Optimize Recommending the new values of antenna E-tilt/Azimuth and RRH power to improve RF
performance through the algorithm.
The operator decides a parameter to be recommended to improve RF performance.
4 Apply Changes the antenna parameter remotely in the optimization cluster.
Displays the recommended value proposed by the algorithm through SSOM GUI. The
change is decided by the operator.
BENEFIT
Operator can reduce the OPEX through the amount of manual processes involved
in initial network optimization through drive test.
The result of optimizing the network at the initial stage improves the effective
quality of users.

Dependency
In case of the DTO function, Smart SON Manager and Smart Scheduler are
required. (DTO function can operate even when Smart Scheduling functions
(DL Smart, UL Smart) are turned off.)
Chapter 9 SON
In case of some UEs, the compatibility of real time reporting DM apps is

impossible. Only UEs with modem chipsets from Qualcomm can support and
interlocking may not be allowed depending on a maker, a model, a firmware
version and so on.
UE should support 3GPP MDT capability (with location information) for DTO
operation based on MDT.
Remote control of E-tilt/Azimuth requires antenna products supporting the
remote control of E-tilt/Azimuth. For the antenna product supporting remote
control of E-Tilt/Azimuth, Smart SON Manager (SSOM) can perform remote
antenna parameter control.
Remote azimuth control function is vendor-specific function. eNB S/W may not
support the function for some antenna manufactures (vendors). In this case,
remote control of E-Tilt/Azimuth in SSOM is not supported.
Acquisition of accurate information on antenna position, height, Mechanical Tilt
(M-Tilt), antenna direction, and 3D antenna pattern based on site survey is
required.
Limitation
The DTO function cannot work in indoor, because it is difficult to acquire the
GPS information in the indoor environment.
Since the change in shadowing depending on each location may be considerable
in the dense urban environment where there are many skyscrapers,
optimization performance and efficiency may be reduced.
Recommendation of E-Tilt/Azimuth values based on auto-optimization is limited
to the antenna supporting remote E-Tilt/Azimuth function.
Activation/deactivation of Trace/MDT by Smart SON Manager (SSOM) are
available only when Samsung EPC is adopted in the network. If other vendor's
EPC is adopted in the network, operator may manually perform activation and
deactivation of Trace/MDT.
FEATURE DESCRIPTION
Architecture
Samsung DTO provides Smart SON Manager (SSOM) and Smart SON Server and
the overall architecture is as shown in the figure below:
Chapter 9 SON
The main NEs of the DTO are as follows: In addition to the following NEs, CSM
(MME EMS), MME, and so on. are all NEs included in the DTO architecture for
the call trace function.
SSOM
Central node controlling the operation of DTO
Displaying real time RF information
Displaying moving routes
Displaying the result of the analyzed RF environment of the Smart SON Server
Displaying the recommended value of the antenna parameters of the Smart SON
Server
Changing remote e-tilt, azimuth, and power
(For DTO operation based on MDT information) Collects the UL RF information
by receiving the call trace report from eNB (the SRS received power)
(corresponding to the TCE under the 3GPP standards).
Smart SON Server
Analyzing RF environment
oReceives the collected DL RF information and site information during the
drive test from the SSOM.
o(For DTO operation based on DM application) Collects the UL RF
information by receiving the call trace report from eNB (the SRS received
power) (corresponding to the TCE under the 3GPP standards).
oReceives the analysis policy from the SSOM.
Chapter 9 SON
oAnalyzes the RF environment of the optimized clusters based on the

collected DL/UL RF information.
oReports the analysis result to the SSOM.
Optimizing antenna parameters
oReceives the optimization policy from the SSOM.
oDraws the antenna parameter value to improve the RF performance by the
optimize policy and reports to the SSOM.
DM Web Server (Required for DTO operation based on DM application)
Terminal DM information collecting server
Keeps the received real time RF information from the DM application of the
tested UE.
The SSOM monitors the collected RF information and brings the data whenever
new RF information is created.
LSM (EMS)
The SSOM acquires the site information from the LSM.
The SSOM orders the call trace activation/deactivation to the LSM.
The SSOM orders the change in the antenna parameters to the LSM.
Smart Scheduler
The Smart scheduler is located in the equipment same to the Smart SON Server.
Also, it collects the information on the UL SRS of the neighbor cell delivered to
the call trace.
eNB
The eNB delivers information such as SRS and statistics, which are acquired
from UEs, to Smart SON Server
The eNB applies optimized RRH power and Antenna e-tilt of RRH.
Samsung DTO Call flow

The overall operating procedure of Samsung DTO is as shown in the figure below:
Chapter 9 SON
The whole procedure can be classified into 7 steps as follows:

1 Step of preparing a drive test
o(For DTO operation based on DM application) Enter the DM web server IP
(public) to UE for testing.
oThe Smart SON Manager transmits the drive test starting message. This
message informs to Smart SON Server of the drive test start.
oAfter transmitting the drive test starting message, the SSOM enters IMSI of
the tested UE and trace activation command is delivered to the EMS (only
available for Samsung EPC.).
2 Step of conducting the drive test
For DTO operation based on DM application:
Chapter 9 SON
oWhen start of the drive test (test route drive start) is ordered to the tested UE,
the DM application of the tested UE starts uploading the DM information
collected in real time to the DM web server.
oThe eNB delivers SRS received power information received from the Smart
Scheduler to the Smart SON server.
oThe RF information collected during the drive test is as follows:
Common IMSI of UE
GPS information Location
Height
Time
Lock/Unlock Status
Serving Cell PCID
Serving Cell ECGI
SFN (Serving Cell)
DL Serving RSRP
RSRQ
RSSI
SINR
Number(#) of Neighbor
# (Neighbor) PCID
RSRP
RSRQ
UL Serving SRS Rx. Power
Neighbor SRS Rx. Power
For DTO operation based on MDT information:

oThe eNB uploads MDT reports from MDT activated test UE to SSOM.
oThe eNB delivers the SRS received power information received from the
Smart Scheduler to the SSOM.
oThe RF information collected during the drive test is given in Table 2-2:
M1+UE Location
Trace Reference (MCC+MNC+Trace ID)
Time Stamp
MDT Info. Flag(0: M1+UE location, 1: M4, 2: M5)
M1 RSRP/RSRQ/PCI Pcell DL earfcn (Not included in MeasResults IE)
(=measResultPCell)
ECGI (Not included in MeasResults IE)
PCI (Not included in MeasResults IE)
measResultPCell rsrpResult
rsrqResult
Scell1 DL earfcn (Not included in MeasResults IE)
(=MeasResultServFreq)
ECGI (Not included in MeasResults IE)
Chapter 9 SON
servFreqId-r10
measResultSCell-r10 rsrpResultSCell-
r10
rsrqResultSCell-
r10
measResultBestNeighCell- physCellId-r10
r10
rsrpResultNCell-
r10
rsrpResultNCell-
r10
~
Scell5 DL earfcn (Not included in MeasResults IE)
(MeasResultServFreq) ECGI (Not included in MeasResults IE)
servFreqId-r10
measResultSCell-r10 rsrpResultSCell-
r10
rsrqResultSCell-
r10
measResultBestNeighCell- physCellId-r10
r10
rsrpResultNCell-
r10
rsrpResultNCell-
r10
Neighbor Top 1 physCellId
(=MeasResultEUTRA)
measResult rsrpResult
rsrqResult
~
Neighbor Top 8 physCellId
(=MeasResultEUTRA)
measResult rsrpResult
rsrqResult
triggering event Triggering event
UE GNSS pos ellipsoid-Point-r10,
Location ellipsoidPointWithAltitude-r10,
ellipsoidPointWithUncertaintyCircle-r11,
ellipsoidPointWithUncertaintyEllipse-r11,
ellipsoidPointWithAltitudeAndUncertaintyEllipsoid-r11,
ellipsoidArc-r11,
polygon-r11
(This is choice IE which is selected by UE, Included in LocationInfo-r10 IE of
MeasResults IE)
3 Step of ending the drive test

o(For DTO operation based on DM application) Provide the test routing drive
end command to the tested UE and stop reporting the DM information.
oThe Smart SON Manager sends the drive test ending message to the Smart
SON Server and inform end of the test.
Chapter 9 SON
oOnce end of the drive test, the SSOM delivers the trace deactivation
command to the EMS and the trace ends. (Only available for Samsung
EPC.)
o(For DTO operation based on MDT information) SSOM delivers the MDT
deactivation command to the EMS and then the MDT for the test UE is
deactivated. (only available for Samsung EPC)
oDeliver the list of all PCIs included in the DM/MDT information through the
initial antenna parameter requesting message to the EMS and receive
initial parameters of all antennas belonging to the PCI from the EMS.
oDeliver the DM/MDT information to the Smart SON Server through the
drive test analysis starting message of the SSOM.
4 Selecting DTO area (optimized cluster)
oSelect the area to perform analysis and optimization based on the RF
information collected from the Smart SON Server.
5 Analyzing RF environment
oThe Smart SON Server performs analysis of RF environment to the DTO
area selected in 4) based on the RF information collected through the steps
1) to 3) (DM/MDT information and trace information).
oThe Smart SON Server reports the result of the analysis to the SSOM.
6 Antenna Optimizing parameters
oThe Smart SON Server optimizes the antenna parameters in the test
route/DTO area.
oThe Smart SON Server reports the result of the optimization to the SSOM.
7 Applying the optimized antenna parameters
oThe SSOM delivers the optimized antenna parameters to the EMS.
oThe EMS delivers the optimized antenna parameter values to eNB and the
parameters are optimally changed. (E-tilt values of Multi RET in eNB are
applied in parallel.)
SYSTEM OPERATION
How to Activate
Smart SON DTO function has precedence over TPC and ATO functions. If DTO
function is activated, TPC and ATO stop their operation and transit to suspend
state.
Pre-condition
eNB should interwork with Smart SON Server, and operational state should be
enabled.
In SSOM, LSM should be registered.
In LSM, Smart SON Server and MME should be registered.
Chapter 9 SON
For call trace at Smart SON Server, Smart SON Server should be included in
TCE table.
1 Before DTO activation, confirmation and information input for the following
DTO related PLD parameters through EMS are required:
aSet SON_DTO_FUNC_ENABLE value of optimization target eNBs
SON_FUNC_ENB_CONTROL PLD to Auto.
bSet SON_AZIMUTH_CTRL_ENABLE, SON_TILT_CTRL_ENABLE,
SON_POWER_CTRL_ENABLE values of optimization target cells
SON_FUNC_CELL_CONTROL PLD to Auto. (Set those values can be
set to Off if azimuth/tilt/power cannot be changed due to HW constraint or
operator does not want the change of steer/tilt/power..)
cOperator enters attributes of optimization target eNBs SON_DTO_FUNC
PLD.
dOperator enters attributes of optimization target cells ANTENNA_CONF
PLD.
2 Activation of DTO function in SSOM
aOn Drive Test registration screen, enter Test Name, IMSI, Smart Son Server,
TCE Address, MME Name, Reference Test, and Map View Type. Then,
click the confirmation button.
bIf new Drive Test is successfully registered, Start button appears bottom of
Drive Test Tab screen. If Start button is clicked, moving path and graph
data are displayed on the screen in real-time.
3 Activation of real-time report function in DM app. (This step is skipped when
DTO operates based on MDT)
aEnter DM Web Server IP address and port (6001) for real-time RF
information reporting in DM app.
bReal-time RF information reporting starts upon clicking Apply and connect
button.
4 Perform DTO Analyze/Optimize in SSOM.
aIf Stop button clicked, Drive Test ends and Analyze screen appears.
bClick Start Analyze button (wait 3 min - retry)
cIf Analyze is finished, Compare button and Optimize tab are activated. By
clicking Compare button, problem path can be identified.
dClick optimize tab and click Start Optimize button (wait 3 min - retry)
eIf Optimize is finished, Compare button and Apply tab are activated. By
clicking Compare button, problem path can be identified.
fOptimized results can be identified by clicking Apply button. Operator can
apply the optimized results by selecting antenna information.
Chapter 9 SON
After using DTO function, DTO can be deactivated by clicking finish button on
SSOM.
SON_DTO_FUNC_ENABLE value must be set to Off.
Key Parameters
Entering Drive Test Information
When clicking the drive test button at the SSOM, the pop-up window for entering
the drive test-related information appears and the operator enters the information
required to perform the drive test.
Parameters for drive test
Test name Drive test name
IMSI The International Mobile Subscriber Identity
Smart SON Server Select the Smart SON Server IP to perform the RF environment analysis and
optimization.
TCE Address Private IP of the Smart SON Server
MME Name Select the MME to perform the call trace function.
Reference test Drive test which is the subject of comparison
Click the checkbox to compare the result of the reference test and the new drive
test drive test after completion of the drive test.
Parameters for Analyze Policy

The operator may set the analyzing options of Samsung DTO by using the
Parameters for analyze policy
Drive test step Information on the flag classifying the primary drive test and secondary or higher
drive tests
Performance metric Threshold to be used to select a problem section
Performance threshold Threshold to be used to select a problem section
Duration of problem section Minimal length of the problem section
Distance between grid Binning distance of optimized cluster
points
Parameters for Optimize Policy

The operator may set the optimization options of Samsung DTO by using the
Parameters for optimization policy
Optimize command Performance metric to be used for optimization
Optimize item Select an antenna parameter to control by checking the checkbox.
Chapter 9 SON
Setting DTO Operation Mode

The operator may set and view the operating mode, either automatic or release, in
Samsung DTO functions by using the following commands and parameters:
SON_DTO_FUNC_ENABL Whether to enable the DTO (drive test optimization) SON function, (one of the
E SON functions).
Off (0): The function is turned off.
Auto (1): When the parameter value is changed by an algorithm, this change is
applied automatically.
Counters and KPIs

REFERENCE
Chapter 9 SON
LTE-SO2021, Tx Power Control (Coverage and

Capacity optimization)
INTRODUCTION
Samsung Tx Power Control (TPC) is a function of automatically controlling the
transmission power of the RRU. Also, this function performs to improve UE
throughput during the operation of Smart LTE System. Samsung TPC fully
satisfies the requirements of the 3GPP LTE standards.
It consists of three detailed functions as follows:
Collecting information
oCollecting the network status (UE distribution and channel status) and
statistical information of the network
Deciding the transmission power of the RRU
oDeciding the transmission power of the RRU based on the information on the
Setting the transmission power of the RRU
oApplying the transmission power of the RRU decided to the RRU
decided transmission power of the RRU
BENEFIT
By controlling the transmission power of the RRU depending on the network
status, possible to increase the whole network throughput.
By controlling the transmission power of the RRU depending on the network
status, possible to increase the edge UE throughput.

Dependency
In case of TPC function, Smart SON Manager and Smart Scheduler are required.
(TPC function can operate even when Smart Scheduling functions (DL Smart,
UL Smart) are OFF)
To collect the information on the received signal of UE, the eNB/Smart scheduler
must support the SRS acquiring function.
Chapter 9 SON
FEATURE DESCRIPTION
Architecture
The blocks related to Smart SON TPC include Smart SON Server (with Smart
Scheduler), Smart SON Manager (SSOM), eNB, and EMS and the whole
architecture is as follows:
The main NEs for the TPC operation are as follows:

eNB
Collects information to control the transmission power of the RRU (loading
information, SRS received power, and statistics of the network quality).
Reports the collected information to Smart Scheduler.
Receives the transmission power by RRU from Smart Scheduler.
Applies the transmission power of the RRU.
Delivers the information on the transmission power of the RRU through SIB2.
Smart Scheduler
Receives information to control the transmission power of the RRU (loading
information, SRS received power, and statistics of the network quality) from
eNB.
Decides transmission power of the RRU based on the received information.
oTLM TPC: Algorithm of controlling the transmission power of RRU to
maximize throughput and load metric.
oRoll-back: Roll-back algorithm to prevent degradation of the network quality
due to the control of transmission power of the RRU by TLM TPC.
Chapter 9 SON
Delivers the transmission power by RRU to eNB.

EMS
Saves TPC-related PLD information and delivers to Smart SON Manager and eNB.
Smart SON Manager (SSOM)
Delivers TPC-related PLD information to Smart Scheduler.
TPC Operation Flow

The whole operating flow of Samsung TPC is as follows:
1 The EMS delivers the TPC-related PLD to eNB and SSOM.

2 The SSOM delivers the received TPC-related PLD to Smart Scheduler.
3 The eNB delivers the SRS received power by UE to Smart Scheduler by
collecting the power.
4 The Smart Scheduler processes and stores the received information on the SRS
received power by UE.
5 The eNB collects and delivers to Smart Scheduler the statistics of the network
quality (HO and call drop-related statistics).
Chapter 9 SON
6 The eNB collects and delivers to Smart Scheduler the scheduling-related

information (loading information, and so on.).
7 The Smart Scheduler decides transmission power of the RRU by considering
status of the network based on the collected information (scheduling
information, statistics of network quality, and SRS received power).
8 The Smart scheduler delivers the decided transmission power of the RRU to
eNB.
9 The eNB changes cell configuration information based on the received
transmission power of the RRU and delivers the information on the changed
transmission power of the RRU to UE through SIB2.
TPC Operation Algorithm

The transmission power of the RRU of Samsung TPC is decided by two
algorithms as follows:
1 Algorithm of controlling the transmission power of the RRU to maximize
throughput and load metric.
2 Roll-back algorithm to prevent the degradation of the network quality due to the
control of the transmission power of the RRU by TLM TPC.
The detailed information on each algorithm is explained below.
TLM TPC
In Samsung TPC, TLM TPC improves throughput of the edge UE without
performance degradation of the average UE throughput by controlling the RRU
transmission power of all cells managed by Smart Scheduler. TLM TPC works as
follows:
oCollecting information on the network status (loading by UE, SRS received
power, and loading by cell)
Deciding the transmission power of the RRU
oDeciding the transmission power of the RRU based on the information on the
Configuring the transmission power of the RRU
oApplying the transmission power of the RRU decided to the RRU
decided transmission power of the RRU
Detailed explanation on the detailed functions of each algorithm is as follows:
Collecting Information
The eNB collects PRB utilization of the cell and the PRB utilization by UE during
the TLM TPC interval. Once collected, it reports the PRB utilization of the
collected cell at the TLM TPC interval to Smart Scheduler.
In addition, eNB reports SRS received power of the cell from UE to Smart
Scheduler by measuring the power.
Chapter 9 SON
Deciding the Transmission Power of the RRU

Smart Scheduler decides the RRU transmission power by cell maximizing the cost
function through power search based on the collected information from eNBs.
Herein the cost function is the sum of the log (UE throughput) for UEs in all cells
managed by Smart Scheduler. In addition, UE throughput is modelled using UE
information (PRB utilization, SRS received power) from eNBs.
In addition, power search is performed only within the designated power range.
Configuring the Transmission Power of the RRU
Smart Scheduler delivers decided transmission power of the RRU of the cell to
eNB. The eNB configures the RRU transmission power of the cell with that of the
cell received from the Scheduler. Also, it transmits information on the changed
RRU transmission power of the cell to UE through SIB2.
Roll-Back
In Samsung TPC, roll-back keeps the network quality through recovery of the
RRU transmission power when the network quality is degraded by the change in
the RRU transmission power by TLM TPC algorithm. Roll-back works as follows:
oCollecting statistical information on network quality (HO and call drop-
related statistics)
Monitoring network quality
oChecking the occurrence of the network quality degradation based on
statistical information on the network quality
Adjusting RRH Tx power change range of TLM TPC
oPreventing network quality degradation by adjusting RRH Tx power change
range of TLM TPC.
Detailed explanation on the detailed functions of each algorithm is as follows:
Collecting Information
The eNB collects information on the call drop rate and HO success rate of the cells
during the roll-back interval. Once collected, it reports the information to Smart
Scheduler at the roll-back interval.
Monitoring Network Quality
Smart Scheduler stores the history of network quality based on the information on
the call drop rate and HO success rate of the received cells from eNBs.
Smart Scheduler calculates the average call drop rate and HO success rate of each
cell for the previous specific hours. This average calculation is based on the
current time by using the information on the call drop rate and HO success rate
with the history of network quality.
Smart Scheduler confirms the following conditions for each cell. A cell is
determined as a network quality degradation cell if the cell satisfies any of the
following conditions:
[Condition 1] Average call drop rate > KPI_{CallDropRate}
Chapter 9 SON
[Condition 2] Average HO success rate < KPI_{HOSuccessRate}

Adjusting RRH Tx Power Change Range of TLM TPC
Smart Scheduler reduces the range of RRH Tx power change for the network
quality degradation cell. TLM TPC prevents network performance degradation due
to TLM TPC by deciding Tx power of the network quality degradation cell within
the adjusted RRH Tx power change range.
SYSTEM OPERATION
How to Activate
Pre-condition
Interworking between eNB and Smart SON Server is required, and operational
state should be enabled.
Feature Activation
1 For TPC activation, confirmation and information input for the following TPC-
related PLD parameters through EMS are required.
aSet SON_TPC_FUNC_ENABLE value for TPC target eNB to Auto.
bSet SON_PWR_CTRL_ENABLE value for TPC target cell to Auto.
cFor the cell of eNB where SON_TPC_FUNC_ENABLE value is OFF,
SON_PWR_CTRL_ENALBE value cannot be set to Auto.
2 Configure PLD parameters related with RRH Tx Power determination algorithm.
aTLM TPC
Apply of Algorithm (TLM_PC_ENABLE = Auto)
Configuration of TLM TPC operation period
(TPUT_LOAD_PC_ENABLE)
Configuration of range of TLM TPC power change (POWER_RANGE)
bRoll-back function
Apply of Algorithm (STATS_CHECK_ENABLE = Auto)
Configuration of Roll-back operation period
(STATS_CHECK_PERIOD)
3 If DTO function is activated during TPC operation, operation of TPC function is
stopped and its state transits to suspend state.
SON_TPC_FUNC_ENABLE value must be set to OFF.
Key Parameters
The operator may set and view the operating mode, either automatic or release, in
Samsung TPC by using the following commands and parameters:
Chapter 9 SON
SON_TPC_FUNC_ENABLE Whether to enable the TPC (Tx. Power Control) SON function.
Off (0): TPC function is turned off.
Auto (1): TPC function is turned on.
The operator may set and view the Tx power changing mode, either automatic or
release, by using the following commands and parameters:
SON_PWR_CTRL_ENABLE Whether to enable the power control.
Off (0): Power change according to TPC function is turned off.
Auto (1): Power change according to TPC function is turned on.
Counters and KPIs

Name
Intra eNB IntraEnbAtt The number of Intra-eNB handover execution attempt to intra-eNB
Handover neighbor cell
IntraEnbSucc The number of Intra-eNB handover execution success to intra-
eNB neighbor cell
X2 Handover Out InterX2OutAtt The number of X2 HO execution attempt to inter-eNB neighbor
cell
InterX2OutSucc The number of X2 HO execution success to inter-eNB neighbor
cell
S1 Handover Out InterS1OutAtt The number of S1 HO execution attempt to inter-eNB neighbor
cell
InterS1OutSucc The number of S1 HO execution success to inter-eNB neighbor
cell
X2 Handover In InterX2InAtt The number of X2 HO execution attempt from inter-eNB neighbor
cell to own eNB cell
InterX2InSucc The number of X2 HO execution success from inter-eNB neighbor
S1 Handover In InterS1InAtt The number of X2 HO execution success from inter-eNB neighbor
InterS1InSucc The number of S1 HO execution success from inter-eNB neighbor
RRC connection ConnEstabSucc The number of RRC connection setup success
establishments
RRC Connection ConnReEstabSucc The number of RRC reestablishment success
Re-establishment
Call Drop CallDrop_ECCB_R The number of call released due to radio link failure
ADIO_LINK_FAILU
RE
CallDrop_ECCB_A The number of call released due to maximum retransmission in
RQ_MAX_RE_TRA RLC
NSMISSION
Chapter 9 SON
REFERENCE
[1] 3GPP 36.300: E-UTRA and E-UTRAN; overall description Stage 2 (Release 9).
specification (Release 9).
use cases and solutions.
[4] 3GPP 32.500: E-UTRAN; Concepts & Requirements.
Requirements for Self Configuration Use Cases.
Chapter 9 SON
LTE-SO2031, Antenna Tilt Optimization

(Coverage and Capacity Optimization)
INTRODUCTION
The Antenna Tilt Optimization (ATO) Coverage and Capacity Optimization
(CCO) as LTE network optimization during the operation consists of a function of
monitoring the network change and calculating the optimized tilt value after
detecting the change in the network. These functions work at the configurable
interval.
The ATO CCO controls service coverage and received signal level of UE by
changing the electrical tilt (e-tilt) through using the RET antenna. Such function
may provide the optimized air interface (RF environment).
To perform ATO CCO, Smart SON Server collects the following information from
UE and eNB:
UE information
oSounding Reference Signal (SRS) power by using Smart Scheduler, NI
information
oPeriodic Measurement Report (MR) information
oMDT information including RSRP, UE location information
eNB information
oStatistical information on the internal collection of eNBs (PM)
oScheduling information (PRB usage per UE)
The detailed functions of the ATO CCO without MDT information are as follows:
Monitoring change in air interface
oCalculating the change index parameter based on collected information
UE count
Outage ratio :radio link failure probability
Signal to Noise Ratio (SNR)
NbrINR : Interference to noise ratio working to the neighbor cell as
interference component
oDetermining the occurrence of the air interface change to the specific index
conditions
E-tilt optimization
oMonitoring the change of the air interface, deciding e-tilt difference fit for
following conditions to the target cell:
Chapter 9 SON
SNR difference to target SNR

NbrINR difference to target NbrINR
oDeciding effectiveness and consistency of e-tilt difference as follows:
Confirming the improvement of average serving/neighbor cell SINR
Confirming the collection in specific e-tilt
The detailed functions of the ATO CCO with MDT information are as follows:
1 E-Tilt Optimization
Calculating optimal e-tilt based on information collected through MDT
2 Apply of optimal e-tilt
Applying optimal e-tilt to corresponding cells
Rolling back if network quality is degraded after new e-tilt apply
BENEFIT
The operator can reduce CAPEX and OPEX cost consumed in the past to manage
the network status.
Because e-tilt is decided to optimize the coverage and capacity of each LTE cell,
the quality of the received signal is improved and the outage ratio is reduced.

Dependency
Smart SON Manager and Smart Scheduler are required for the ATO. (ATO CCO
can operate even when Smart Scheduling functions (DL Smart, UL Smart) are
OFF.)
Supporting the UL SRS report/periodic MR of UE: To collect the information on
the received signal of UE, the eNB and the Smart Scheduler must support the
function of acquiring the periodic MR/SRS.
To support the automatic optimization of e-tilt during the operation, the RET-
antenna that may control e-tilt through the RET module must be supported.
UE should support 3GPP MDT with location information in order to collect
location information and RF status required for MDT based ATO CCO
operation.
Limitation
On assumption that optimization of the initial network is performed, ATO
calculates the optimization value by detecting any occurrence of the change in
the wireless network status. Also, this calculation occurs due to the
construction of a new building during operation of the service.
(For ATO CCO operation without MDT information) Because it works in a way
of reducing a trial error at an interval, a certain period of time is required to
optimize.
Chapter 9 SON
(For ATO CCO operation with MDT information) If UE fail to report MDT
report message including location information, accuracy of ATO CCO
optimization results for the corresponding cell can be degraded.
FEATURE DESCRIPTION
Architecture
The blocks related to the Smart SON ATO CCO include Smart SON Server (with
Smart Scheduler), Smart SON Manager (SSOM), eNB, and EMS and the whole
architecture is as follows:
The main NEs for ATO CCO operation are as follows:

Smart SON Manager (SSOM): SON GUI (ATO Function Control)
Configuring ATO CCO working environment
oATO CCO operating period
oATO CCO working interval to monitor change in air interface (ATOperiod)
oATO CCO working time to monitor change in air interface
oTilt optimization working interval (TOperiod)
o(For ATO CCO operation without MDT information) Ratio of selecting the
target to configure periodic MR
o(For ATO CCO operation with MDT information) UE selection ratio for
MDT reporting (MDT report UE ratio)
Confirming application of the change in tilt (Operation of manual application)
Confirming description on the tilt application (history management)
Chapter 9 SON
For ATO CCO operation with MDT information:

oSSOM transmits MDT and statistic information collection request to LSM
oSSOM transmits MDT information, UE based measurement information
collection request to Smart SON Server
oSSOM calculates average load per cell based on the collected load per cell
information, and transmits the average load per cell to Smart SON Server
oAfter antenna tilt adjustment, SSOM calculates RLF occurrence ratio
whenever it receives RLF information, and it determines whether network
performance is degraded or not.
oIf SSOM determines that network performance is degraded, SSOM transmits
tilt adjustment request to LSM for roll back operation.
oAfter transmitting roll back request to LSM, SSOM transmits roll back
notification to SSOM.
oSSOM displays SINR heat map for before and after apply of optimal e-tilt to
operator (TBD).
oSSOM transmits e-tilt adjustment request to LSM.
oSSOM transmits acknowledgment for e-tilt adjustment complete to Smart
SON Server.
oSSOM transmits MDT deactivation request to LSM.
oSSOM transmits algorithm end request to Smart SON Server.
eNB
(For ATO CCO operation without MDT information) RQA Function
oConfiguring or terminating a periodic measurement report (pMR) with a
specific UE
oDelivering SRS information by UE to Smart Scheduler
oDelivering serving/neighbor RSRP information to Smart SON server
PM (ATO CCO related statistics)
oCollecting RRC connection (Re) establishment/RLF item by using the call
information
oDelivering statistical information to Smart SON Server at the configured
interval to the SON GUI
RET antenna management
oChanging/managing e-tilt parameters depending on result of the ATO
operation
o(For ATO CCO operation with MDT information) Transmitting
acknowledgment message to LSM after completing e-tilt adjustment.
(For ATO CCO operation with MDT information) MDT and scheduling
information collection
oCollecting MDT information from UE and transmitting the collected
information to Smart SON Server
Chapter 9 SON
oTransmitting scheduling information (PRB usage) for connected UE to Smart

SON Server
Smart Scheduler
SRS management Function
Managing serving/neighbor cell SRS/NI information
Sharing SRS information with Smart SON server
Smart SON Server (with Smart Scheduler)
Detection of change in air interface
oCalculating a detection parameter with the collected information from
eNBs/Smart Scheduler
oDetermining change in air interface by using the detection parameter
oSelecting a cell whose air interface is changed
Tilt optimization Function
oCalculating a tilt optimization parameter with the collected information from
eNBs/Smart Scheduler
o(For ATO CCO operation without MDT information) Deciding change in e-
tilt for the cell selected in the detection function
oFor ATO CCO operation with MDT information) Deciding the change in e-
tilt and priority for apply of the change.
oDetermining effectiveness of e-tilt values whose previous interval is changed
oDetermining optimization of e-tilt
oTransmitting the decided value of e-tilt and information required to display to
SSOM
EMS
PLD sync function: Managing PLD change/maintenance
oTransmitting MDT activation and request for statistic information collection
to eNB of cells participating in ATO CCO.
oTransmitting network statistic information (load/RLF information per cell)
received from eNB to SSOM.
oTransmitting e-tilt adjustment request to eNB of corresponding cells.
oTransmitting e-tilt adjustment complete acknowledgment to SSOM.
oTransmitting MDT deactivation request to eNB of cells participating in ATO
CCO.
Smart SON ATO CCO Function

Operation of ATO CCO without MDT Information
Smart SON ATO CCO without MDT information starts depending on the
scheduling information entered in the SSOM, and the whole flow is as follows:
Chapter 9 SON
1 Starting operation of ATO CCO by the SSOM.

oConfigure ATO CCO operation in the SSOM.
oThe SSOM updates ATO CCO related PLD value from EMS every TOperiod.
oThe SSOM delivers updated PLD to the Smart SON Server.
2 Updating PLD information
The Smart SON Server updates PLD value from the SSOM.
3 Operating ATO
The SSOM triggers operation of ATO CCO to the Smart SON Server every
ATOperiod.
4 Configuring Radio Quality Analysis (RQA)
oConfigure periodic MR to be collected by eNB at the SSOM.
oThe SSOM request eNB to operate RQA.
Chapter 9 SON
oThe Smart SON Server collects serving/neighbor cell SRS information from
the Smart Scheduler during TOperiod.
oThe Smart SON Server collects the information on periodic MR (optional)
and PM statistics from eNBs during TOperiod.
Interface for statistic information collecting: FTP
6 Operating the function of monitoring change in air interface
oCalculate the detection parameter by using (5) information.
oDetermine change in the network by using the detection parameter.
oIf change in the network does not occur, the SSOM alarms the end of the
ATO CCO operation/Operate from (10).
oSelect the cell in the network change to the target to change tilt.
7 Determining the change in e-tilt
oCalculate the tilt optimization parameter by using (5) information.
oDetermine e-tilt change by using the tilt optimization parameter for the
selected cell.
oDetermine effectiveness and rollback of the changed e-tilt at the past interval.
oIf change in the e-tilt does not occur, the SSOM alarms the end of the ATO
CCO operation/Operate from (10).
8 Alarming change in e-tilt
oThe Smart SON server delivers the changed e-tilt to SSOM.
oThe SSOM transmits the change e-tilt to EMS.
oThe EMS transmits the changed e-tilt to eNB for apply the changed e-tilt
value to the RET. (E-tilt values of multi RET in eNB are applied in
parallel.)
9 Performing operation of the e-tilt optimization (repeatedly).
Perform (5) and (7)~ (9) every TOperiod.
10 Stopping operation of RQA
The SSOM request eNB to stop operation of the RQA.
11 Holding the operation until the next ATOperiod
Operation of ATO CCO with MDT Information
The following figure shows call flow of ATO CCO function (with MDT
information)
Chapter 9 SON
1 If one or more than one Smart SON function (ATO CCO, ATO COC, NCSR,
TPC) is in operation during network in service, following operations are
always performed:
eNB transmits PRB usage of each connected UE to Smart SON Server
Smart Scheduler transmits SRS Rx power and estimated value of NI per
connected UE to Smart SON Server
Chapter 9 SON
2 If operator selects Activation after configuring parameters for ATO CCO

operation through GUI of SSOM, SSOM generates MDT activation and
request on statistics collection, and it transmits those messages to LSM. In
addition, SSOM generates MDT data, UE based measurement collection
request, and it transmits those messages to Smart SON Server.
3 Upon receiving MDT activation and request for statistics from SSOM, LSM
generates and transmits MDT activation request and request for PM statistics
to eNB including target cells of ATO CCO.
4 eNB that has received MDT activation request starts to collect MDT information
from MDT UEs.
5 eNB that has received request for PM statistics starts to collect PM information
(load/RLF information per cell).
6 Smart SON Server which has received MDT data, UE based measurement
collection request starts to collect SRS Rx power and NI from Smart Scheduler.
7 eNB periodically reports collected MDT data to Smart SON Server.
8 eNB periodically reports collected load/RLF information per cell to LSM.
9 LSM transmits received load/RLF information per cell to SSOM.
10 SSOM determines whether network quality is degraded or not in every PM
statistic period.
11 If SSOM determines that the network quality is degraded due to apply of new
e-tilt, SSOM immediately transmits tilt control request for the purpose of roll
back to LSM.
12 At the end of data collection period, SSOM calculates average load per cell and
transmit the average load per cell to Smart SON Server.
13 Smart SON Server starts analysis at the end of data collection period.
14 Smart SON Server calculates new e-tilt values for target cells of ATO CCO.
15 Smart SON Server transmits determined e-tilt values and data for display heat
map to SSOM.
16 Upon reception of new e-tilt values, SSOM generates tilt adjustment request
and transmits it to LSM.
17 SSOM displays SINR heat maps for before/after new e-tilt apply (TBD).
18 LSM receiving e-tilt adjustment request orders corresponding eNBs to adjust e-
tilt.
19 eNB receiving e-tilt adjustment request adjusts e-tilt. If e-tilt adjustment is
completed, eNB generates acknowledgment and transmits it to LSM.
20 LSM receiving acknowledgment for e-tilt adjustment relays the
acknowledgment to SSM.
21 If SSOM receives acknowledgment of e-tilt adjustment from all cells that have
requested to adjust e-tilt, SSOM transmits tilt control completion message to
Smart SON Server.
Chapter 9 SON
22 If SSOM that has determined network quality degradation and requested roll
back of e-til receives acknowledgment for the e-tilt roll back, SSOM transmits
roll back notification message to Smart SON Server.
23 If operator selects Deactivation through SSOM or the configured time expires,
SSOM generates MDT deactivation and request for statistics collection stop,
and it transmit those messages to LSM. In addition, SSOM generates MDT
data and UE based measurement collection stop request, and it transmit the
message to Smart SON Server.
24 LSM receiving MDT deactivation and request for statistics collection stop
transmits MDT deactivation request and statistic data collection stop messages
to eNBs for target cells of ATO CCO.
SYSTEM OPERATION
How to Activate
Pre-condition
The eNB should interwork with Smart SON Server, and operational state should
be enabled.
If Radio Quality Analysis (RQA) is activated by other function, current RQA
should be deactivated and RQA should be reactivated for the purpose of ATO.
(For ATO CCO operation without MDT information) If Radio Quality Analysis
(RQA) is currently running for other purpose, the current RQA operation
should be disabled and RQA should be rescheduled for the purpose of ATO
CCO.
(For ATO CCO operation with MDT information) Smart SON Server should be
registered in TCE table in order to enable MDT information collection in
Smart SON Server.
(For ATO CCO operation with MDT information) LTE-SO0901 Minimization
Drive Test Optimization (MDT) feature must be supported. (For detail
information on the MDT function, refer to the LTE-SO0901 feature
description and system operation.)
Feature Activation
1 In SSOM, MDT usage for ATO CCO should be configured by selecting Usage
of MDT.
oUsage of MDT is configured as On, MDT based ATO CCO is activated.
oUsage of MDT is configured as Of, MDT based ATO CCO is deactivated
and MR based ATO CCO operation will be performed.
2 For ATO CCO operation without MDT information (MR based ATO CCO
operation)
Chapter 9 SON
aBefore activation of ATO CCO, confirmation and information input for the
following ATO CCO-related PLD parameters are required.
SON_ATO_FUNC_ENABLE value must be set to Auto or Manual.
Setting of RQA related parameters
iRQA_ENALBE value must be set to On (1).
iiSMART_SON_ATO_FLAG value must be set to True.
iiiSTART_TIME_HOUR and START_TIME_MIN are configured with
start time of RQA is enabling.
bActivating ATO CCO function in SSOM.
Configure Usage of MDT to Off and click Register button on ATO
Schedule Job screen.
Configure Smart SON Server, Period, Schedule Term (ATOperiod), Start
At, Algorithm Term (TOperiod), and Call rate in SSOM GUI
Configuration.
3 For ATO CCO operation with MDT information
aBefore activation of ATO CCO, confirmation and information input for the
following ATO CCO-related/Tilt-related/MDT-related PLD parameters
are required.
SON_CCO_MDT_FUNC_ENABLE of SON_FUNC_ENB_CONTROL
PLD for ATO CCO target eNB must be set to Auto.
SON_TILT_CTRL_ENABLE of SON_FUNC_CELL_CONTROL PLD
for ATO CCO target cell must be set to Auto.
Attribute of SON_CCO_MDT_FUNC PLD for ATO CCO target eNB
should be configured by operator.
Attribute of ANTENNA_CONF PLD for ATO CCO target cell should be
configured by operator.
MGMT_BASED_IMMEDIATE_MDT_ALLOWED of
MDT_CTRL_PARA PLD for the ATO CCO target cell should be set
to True.
bActivate ATO CCO function through SSOM
Click registration button after selecting Usage of MDT to On and
configuring Period for MDT based ATO.
Click confirm button after configuring Smart SON Server, Period, Start
Time, MDT report UE ratio, Algorithm Type, Usage of Load Statistics
DB on ATO(CC) registration screen.
4 Apart from the configuration registered in SSOM, ATO CCO can be activated
by clicking ATO Start button.
5 ATO CCO is performed during network operation, and ATO CCO cannot
simultaneously operate with DTO.
Chapter 9 SON
Delete configuration contents registered in SSOM.
Apart from the configuration registered in SSOM, operator can deactivate ATO
CCO function by clicking ATO Stop button.
For ATO CCO operation without MDT information (MR based ATO CCO
operation):
oSON_ATO_FUNC_ENABLE value must be set to Off and disabling RQA
function.
oRQA_ENALBE value must be set to Off (0).
oSMART_SON_ATO_FLAG value must be set to False.
oSON_CCO_MDT_FUNC_ENABLE value must be set to Off.
Key Parameters
The operator may set and view the operating mode, among automatic, manual or
release, in Smart SON ATO by using the following commands and parameters:
SON_ATO_FUNC_ENABLE Whether to enable the ATO (antenna tilt optimization) Coverage and
Capacity Optimization SON function without MDT information.
Manual (1): When the parameter value is changed by an algorithm, this
change is reported to the LSM and then the operator determines manually
whether to apply the changed parameter value.
Auto (2): When the parameter value is changed by an algorithm, this change
is applied automatically.
SON_CCO_MDT_FUNC_ENA Whether to enable the MDT-based ATO (CCO) SON function, (one of the
BLE SON functions).
Manual (1): When the parameter value is changed by an algorithm, this
change is reported to the LSM and then the operator determines manually
whether to apply the changed parameter value.
Auto (2): When the parameter value is changed by an algorithm, this change
is applied automatically.
The operator may set and view the e-tilt changing mode, either automatic or
release, in use of the RET by using the following commands and parameters:
SON_TILT_CTRL_ENABLE Whether to enable the Tilt control
Auto (1): The parameter value is changed by an algorithm
Chapter 9 SON
Counters and KPIs

ATO CCO without MDT Information
Counters related with Smart SON ATO CCO function without MDT information
RRC connection ConnEstabSucc The number of RRC connection setup success
establishments
RRC Connection Re- ConnReEstabSucc The number of RRC reestablishment success
establishment
Call Drop CallDrop_ECCB_RADIO_LINK_ The number of call released due to radio link
FAILURE failure
ATO CCO with MDT Information

Counters related with ATO CCO function with MDT information
PRB_TOTAL TotPrbDLAvg Resources used for PDSCH/PDCCH transmission
among all downlink resources.
MRO_RLF CoverageHole The number of RLF/HO failure occurrence
according to coverage hole in this cell region.
CoverageHoleN The number of RLF/HO failure occurrence
according to coverage hole for this cell region
toward
neighbor cell N.
RRC_ESTAB ConnEstabSucc The number of RRC establishment success
RRC_REESTAB ConnReEstabSucc The number of RRC re-establishment success.
REFERENCE
Chapter 9 SON
LTE-SO2032, Antenna Tilt Optimization (Cell

outage compensation)
INTRODUCTION
The Samsung Antenna Tilt Optimization (ATO) for Cell Outage Compensation
(COC) feature improves RF environment (SINR) of the cell outage area by
automatically adjusting antenna tilt of neighboring cells of the outage cell, if the
outage occurs for a specific cell during the operation of LTE system. ATO COC is
based on Minimization of Drive Test (MDT) function. ATO COC consists of RF
map generation/update, cell outage detection, cell outage compensation, and cell
outage clear functions.
1 RF information map creation and update function
oCreating and updating RF information map by collecting MDT Data and real-
time RF information.
2 Cell outage detection function
oCell outage detection by monitoring change of cell status information.
oCell outage detection based on statistic information.
3 Cell outage compensation function
oCalculation of e-tilt values for neighboring cells of the outage cell for
compensating cell outage area.
oCells participating in ATO COC operation maximize average SINR of cell
outage area by adjusting their antenna tilts.
4 Cell outage clear function
oIf the cell outage is cleared, antenna tilts of ATO COC participating cells are
returned to the value of antenna tilt before the cell outage occurs.
The following figure shows Concept of Antenna Tilt Optimization (COC).
Chapter 9 SON
BENEFIT
By supporting operator to quickly detect cell outage, time required to recover
network operation can be reduced.
Cell outage compensation enables operator to continuously provide services to
the users located in cell outage area.
User can be provided service with short interruption time in case of cell outage
occurrence.

Dependency
ATO COC requires Smart SON Manager and Smart Scheduler.
Support of UE UL SRS report/Periodic MR function is required. To collect
information on received signal of the UE, eNB and Smart scheduler should
support periodic MR/SRS acquisition functions.
Support of Remote Electrical Tilting (RET) is required. For enabling e-tilt
automatic adjustment during network operation, RET antenna which can
adjust e-tilt through RET module is required.
UE should support 3GPP MDT function (immediate MDT (M1/location)).
Limitation
Certain time is required for determining cell outage detection for cell outage
compensation in order to accurately determine cell outage situation.
Chapter 9 SON
FEATURE DESCRIPTION
Architecture
The blocks related to the Smart SON ATO COC include Smart SON Server (with
Smart Scheduler), Smart SON Manager (SSOM), eNB, and EMS. Overall
architecture for Smart SON ATO COC is shown in the following figure.
In the above architecture, operation of each entity for Smart SON ATO COC is as
follows:
1 Smart SON Manager (SSOM)
oParameter configuration for ATO COC operation
iActivation/deactivation of ATO COC feature
iiMDT based ATO period (determination period of statistic based cell
outage detection)
iiiMDT Report Target UE selection ratio
oDetermination of Cell Outage Detection (COD)
ivPeriodic COD : Determination of COD based on statistics data from
EMS
Chapter 9 SON
vEvent driven COD : Determination of COD based on cell status

abnormality information from EMS
oCOD identification functionality (Auto/Manual apply operations)
oFunction for confirm ATO COC apply (Manual apply operation)
oFunction for check ATO COC apply history (history management)
oRequest of MDT activation and statistic data collection to EMS
oRequest of MDT data/RF information collection to Smart SON Server
oCOC with MDT operation request/Apply of new e-tilt values
2 eNB
oMDT configuration
iManaging MDT operation for specific UE
iiReporting SRS information per UE to Smart Scheduler
iiiReporting MDT measurement data to Smart SON Server
oPM (ATO COC related Statistics)
iCollecting RRC connection (Re)Establishment/MRO RLF based on Call
information
iiReporting statistics to EMS in every statistics reporting period.
oRET Antenna Management
iApplying/managing e-tilt parameter which is determined by ATO COC
3 Smart Scheduler
oSRS Management Function
iManaging Serving/Neighbor Cell SRS/NI information
iiSharing SRS information with Smart SON Server
4 Smart SON server (in Smart Scheduler)
oRF Information Map Management Function
iGenerating/managing RF information map based on information
collected in eNB/Smart Scheduler (MDT/SRS Rx power/Network
quality)
oTilt optimization Function
iCalculating optimal e-tilt values based on the RF information map.
5 EMS
oSystem parameter management (change/maintenance)
oCollecting MDT and statistic information from the target cells and
transmitting them to SSOM in a certain period.
oInforming SSOM the cell status abnormality if time that certain cells status
is kept disabled is longer than certain time duration.
Chapter 9 SON
Smart SON ATO COC Function

ATO COC Operational Procedure
Smart SON ATO COC operation starts when operator activates the function
through SSOM GUI. Operational procedure of ATO COC is as follows:
1 Collection of MDT and real-time RF information

aSmart SON Server collects MDT information, SRS Rx power, CQI, RI, MPR
from eNB.
2 RF information map creation and update
aSmart SON Server creates service area based on location information of
MDT collection target cells, and divides the collection area as a form of
grid.
bSmart SON Server updates RF information collected during COD
determination period in each grid.
3 Cell Outage Detection (COD)
aSSOM performs COD based on cell status change.
bSSOM performs COD based on periodic statistics collection.
4 Cell Outage Compensation (COC)
Chapter 9 SON
aSmart SON Server selects COC target cells which will participate in COC
operation, by using RF map.
bSmart SON Server determines antenna tilts of COC target cells, which
maximizes average SINR of Cell Outage area.
5 Cell Outage Clear (COC)
aIf the cell outage is cleared, the values of antenna tilt of COC target cells
return to the values used before the cell outage occurs.
ATO COC call flow
Call flow of Smart SON ATO COC feature is as follows:
1 SSOM registers/activates ATO COC function.
2 If ATO COC function is activated by operator or schedule, SSOM requests
required operations for ATO COC to EMS and Smart SON server.
3 EMS requests eNB to perform MDT activation/statistic report if ATO COC
related operation is requested from SSOM.
4 Smart SON Server collects MDT data from eNB and SRS Rx power from Smart
Scheduler if activation of ATO COC function is requested from SSOM.
5 eNB transmits collected MDT and scheduling data to Smart SON Server at
every operational period.
6 EMS accumulates statistic information from eNB during the operational period,
and transmits the accumulated information to SSOM.
7 Smart SON Server receives SRS Rx power from Smart Scheduler at every 1.28
sec.
8 Smart SON server generates and updates RF information map at every
operational period based on the collected information.
9 SSOM determines cell outage by using statistic data collected after the end of
operational period.
10 If cell outage is detected, SSOM transmits request of COC operation along
with cell outage occurrence information to Smart SON Server (if operational
mode is set to manual, operators confirmation is required before performing
COC.) If cell outage is not detected, SSOM does not perform COC.
11 If COC operation request is delivered from SSOM, Smart SON server
calculates new e-tilt values of COC target cells for cell outage compensation
based on RF information map updated until current operational period.
12 Smart SON Server informs SSOM the newly calculated e-tilt values. Then,
SSOM requests EMS to apply the new e-tilt values.
13 EMS requests e-tilt adjustments to eNBs corresponding to the COC target cells.
14 If acknowledgment for e-tilt adjustment request is received by SSOM, SSOM
informs operator about the operation results.
Chapter 9 SON
Apart from the periodic COD operation, if EMS identifies that specific condition
(cell status disable) is maintained for certain time duration, EMS reports the
abnormal cell status to SSOM. Then, SSOM can detect cell outage based on the
report from EMS. In this case, procedures from 10) to 14) are performed for COC.
Chapter 9 SON
SYSTEM OPERATION
How to Activate
Pre-condition
The eNB should interwork with Smart SON Server, and operational state should
be enabled.
If MDT is activated by other function, current MDT should be deactivated and
MDT should be reactivated for COC with MDT function
In SSOM, EMS should be registered.
In EMS, Smart SON Server and MME should be registered.
In TCE table, Smart SON Server should be registered.
(For ATO COC operation with MDT information) LTE-SO0901 (Minimization
Drive Test Optimization, MDT) feature must be supported.
(For detail information on the MDT function, refer to the LTE-SO0901 feature
description and system operation.)
Feature Activation
1 Before activation of COC with MDT (ATO (COC)), confirmation and
information input for the following COC with MDT-related system parameters
are required.
aIn SON_FUNC_ENB_CONTROL relation, CocMdtFuncEn value must be
set to Autoapply or Manualapply.
bIn SON_FUNC_CELL_CONTROL relation, TiltCtrlEn value must be set to
Auto (enable).
cRequired setting for MDT activation must be activated.
2 Activating COC with MDT function in SSOM.
aSelect Usage of MDT
bInput the Period for MDT based ATO
cClick Register button on ATO Schedule Job screen.
dConfigure Smart Son Server, Overall duration of COC with MDT function
and Call rate for MDT in SSOM GUI Configuration.
3 COC with MDT is performed during network operation, and it can
simultaneously operate with CCO with MDT. But, it cannot simultaneously
operate with DTO and NCSR
Delete configuration contents registered in SSOM.
COC with MDT-related system parameters are set as follows
In SON_FUNC_ENB_CONTROL relation, CocMdtFuncEn value must be set to
Off.
Chapter 9 SON
In SON_FUNC_CELL_CONTROL relation, TiltCtrlEn value must be set to

Off(disable)
Key Parameters
The operator may configure or change the operation of the Smart SON ATO
(COC) by using the following configuration:
Parameters for GUI configuration
Parameters Description Unit
Smart Son Server Select a server to perform ATO operation. -
Period Select a period where ATO (COC) operation is performed. -
Start At ATO operation starting time -
MDT report UE ratio Ratio of calls for MDT %
Usage of MDT Usage of MDT -
Period for MDT based Periodic for COD -
ATO
The operator may set and view the operating mode, among automatic, manual or
release, in Smart SON COC with MDT by using the following commands and
parameters:
SON_COC_MDT_FU Whether to enable the Antenna Tilt Optimization (COC with MDT) SON function, (one
NC_ENABLE of the smart SON functions).
Manual (1): When the parameter value is changed by an algorithm, this change is
reported to the SSOM and then the operator determines manually whether to apply
the changed parameter value.
Auto (2): When the parameter value is changed by an algorithm, this change is
applied automatically.
The operator may set and view the e-tilt changing mode, either automatic or
release, in use of the RET by using the following commands and parameters:
SON_TILT_CTRL_E Whether to enable the Tilt control
NABLE Off (0): The function is turned off.
Auto (1): The parameter value is changed by an algorithm
Counters and KPIs

Chapter 9 SON
REFERENCE
[1] 3GPP 36.300: E-UTRA and E-UTRAN; overall description Stage 2
specification
[6] 3GPP 32.422: Trace control and configuration management
[7] 3GPP 32.423: Trace data definition and management
Chapter 9 SON
LTE-SO2041, New Cell Site Recommendation

INTRODUCTION
Samsungs new cell site recommendation solution automatically recommends the
number and locations of new small cells to install when operating a Smart LTE
system. The purpose of this function is to enhance network performance.
Samsungs new cell site recommendation solution consists of the following
processes:
oCollects information on the network status (load and RF status) and network
statistics in real-time.
2 Determining the need for additional small cells
oDetermines whether additional small cells are required to enhance network
performance based on the information collected during a certain timeframe.
3 Collecting trace information
oCollects the location information and real time information using MDT.
4 Determining the number and locations of additional small cells to install
oDetermines the optimal number and locations of additional small cells to
install.
oReports the optimal number and locations of the small cells to the network
operator.
BENEFIT
Improves the network throughput by selecting the optimal locations for small
cells based on the network status.
Releases macro overloads caused by expanded macro coverage and increased
subscribers.
Reduces operating expenses (OPEX) by automatically recommending the optimal
number and locations of small cells.
Improves the service quality of UEs in problematic areas by selecting the optimal
locations for small cells based on the network status.

Dependency
The Smart SON Manager and Smart SON Server are required for the new cell
site recommendation function.
Chapter 9 SON
The UE must have MDT capabilities to acquire the location information and the
RF status.
Limitation
If UE fails to report its location information with MDT message, then the
accuracy decreases for that cell.
FEATURE DESCRIPTION
Architecture
The following figure shows the network architecture for Samsungs new cell site
recommendation solution. The main network entities (NEs) in this architecture
include the eNB, Smart Scheduler, LSM, and Smart SON Manager (SSOM).
The functions of the main NEs used in Samsungs new cell site recommendation
solution are as follows:
1 eNB
oCreates the network statistics (loading information, call drop rates).
oReceives call trace reports from UE.
oReports the collected information to the Smart Scheduler.
Chapter 9 SON
2 Smart SON Server

oDetermines the number of additionally required small cells and the
installation locations.
iSelects problematic areas (coverage holes, UE-dense areas) based on the
MDT information.
iiDetermines the number and locations of the new small cells required for
network optimization.
iiiReports the determined result to the SSOM.
3 SSOM (Smart SON Manager)
oDetermines whether additional small cells are required.
iDetects cell having coverage holes or cell in heavy load situation based
on information collected by LSM, and determines whether detail
information collection is required or not.
iiActivates MDT for the detected cell if SSOM determines that detail
information collection is required.
oDisplays the problematic locations (coverage holes, UE-dense areas).
oDisplays the optimal number and locations of the small cells to install.
4 LSM (LTE System Manager)
oCollects information for determining whether new cell site is required or not.
oCollects network statistic information from eNB, and forwards the collected
information to SSOM.
New Cell Site Recommendation Function

New Cell Site Recommendation Operation Flow
The operating flow of Samsungs new cell site recommendation solution is as
follows:
Chapter 9 SON
1 eNB collects network service information (cell load and RLF information) of its
managing cells, and delivers the information to LSM.
2 SSOM determines whether detailed information collection due to coverage hole
or too heavy load is required or not (operation of new cell site
recommendation is required or not) based on the network service information
collected from LSM.
3 If SSOM determines that the operation of new cell site recommendation is
required, it transmits MDT activation to the cell with problem, and SSOM
transmits new cell site recommendation triggering to Smart SON Server.
4 Smart SON Server collects MDT and scheduling information.
5 Smart SON Server transmits MDT deactivation commend to SSOM, if all
information required for algorithm operation is collected.
6 SSOM transmits MDT deactivation to eNB for stopping MDT collection.
7 Smart SON Server determines the number of additional small cells to install and
the installation locations of the additional small cells to install.
Chapter 9 SON
8 Smart SON Server reports the number of additional small cells to install and the
cells installation locations to the SSOM.
9 SSOM reports the number of additional small cells to install and the cells
installation locations to operator.
New Cell Site Recommendation Detailed Operation
1 Collecting Information
eNB collects its managing cells PRB usage and PRB usage per UE during
New Cell Site Recommendation period. Also, it reports the collected
information related with cell loading to SSOM in every New Cell Site
Recommendation period.
In addition, eNB acquires UEs RLF information during the same period, and
reports information of RLF occurred due to coverage hole to SSOM.
2 Determining Necessity of Additional Small Cell Installation
Necessity of additional installation of new small cell is triggered by following
two cases.
oTriggering by coverage hole
SSOM determines that cell in which RLF due to coverage hole does not
satisfy condition requires installation of new small cell.
oTriggering by too heavy loading
SSOM determines that cell having cell loading higher than pre-defined
level requires installation of new small cell.
If SSOM determines that the installation of new small cell is required, SSOM
transmits MDT activation to the cell with problem, and SSOM transmits new
cell site recommendation triggering to Smart SON Server.
3 Determining New Cell Site
In case that Samsung New Cell Site Recommendation function is performed,
LSM transmits trace activation message to MME and eNB. During MDT
information collecting duration, Smart SON Server collects RF information
and location information from MDT UE through eNB. In addition, if RLF
occurs, corresponding information is collected. Upon finishing MDT
information collecting duration, trace deactivate message is delivered to MME
and eNB.
Smart SON Server performs following operations to estimate problem location
based on collected information such as UE location, RSRP, and RSRQ.
oFor case of triggering due to coverage hole
iBinning the whole MDT area by specific size.
iiFor each bin, calculating the values of received RSRP and SINR for all
cells by averaging RF information in location corresponding to the bin.
iiiDetermining bins where network quality (RSRP or SINR) is lower than
specific threshold as problem area.
ivDetermining coverage radius of new small cell according to the Tx
power of the small cell.
Chapter 9 SON
vLocating small cell at the bin having the worst network quality, and
determining whether the small cell can cover all adjacent problem
areas.
viIf the small cell cannot cover all of the problem areas, moving the
location of small cell to adjacent bin and determining whether the
small cell can cover all problem areas.
viiBin where the small cell can cover all adjacent problem areas is selected
as new cell site location.
viiiIf other problem area exists, increasing the number of additional small
cells by 1, and repeating procedures iii~vi.
oIn case of triggering due to too heavy loading

iBinning the whole MDT area by specific size, and calculating the PRB
usage corresponding to each bin.
iiDetermining coverage radius of new small cell according to the Tx power
of the small cell.
iiiLocating the small cell at each of all bins, and selecting a bin with the
highest PRB usage in the coverage of the small cell.
ivIf the cell is still too high loading status even though excluding the load
expected to be accommodated by the new small cell, increasing the
number of new small cell by 1 and repeating procedures ii and iii.
Chapter 9 SON
Smart SON Server reports determined number of new small cells and their
locations to SSOM.
SYSTEM OPERATION
How to Activate
Smart SON New Cell Site Recommendation function has precedence over TPC
and ATO functions. If DTO function is activated, TPC and ATO stop their
operation and transit to suspend state.
Since DTO function has precedence over New Cell Site Recommendation function,
New Cell Site Recommendation function waits until operation of DTO function is
finished, if DTO function is currently running.
Pre-condition
eNB should interwork with Smart SON Server, and operational state should be
enabled.
For call trace at Smart SON Server, Smart SON Server should be included in
TCE table.
1 Before New Cell Site Recommendation activation, confirmation and information
input for the following related PLD parameters through EMS are required.
aSet SON_NCSR_FUNC_ENABLE value of optimization target eNBs
SON_FUNC_ENB_CONTROL PLD to Manual.
2 Activate New Cell Site Recommendation function in SSOM. If the function is
activated, RLF information and cell load information are collected to
determine whether new cell installation is required or not. If SSOM determines
that new cell installation is required, it is reported to operator.
3 If operator activates operation for new cell installation, Smart SON Server
collects MDT information and scheduling information.
Chapter 9 SON
4 After finishing the information collecting, Smart SON Server reports the number
of newly required cells and their locations to operator, and finishes operations
for MDT and scheduling information collecting.
After reporting New Cell Site Recommendation operation to operator, operation
for additional cell installation is deactivated.
Key Parameters
SON_NCSR_FUNC_ENABLE Whether to enable the New Cell Site Recommendation SON function, (one of
the SON functions).
Off: The function is turned off.
Manual: When the parameter value is changed by an algorithm, the
operator determines manually whether to apply the changed parameter
value.
CHG-MDTCTRL-PARA/RTRV-MDTCTRL-PARA
MGMT_BASED_IMMEDIATE This parameter shows the whether to permit to the Management Based
_MDT_ALLOWED Immediate MDT on demand.
False: Management Based Immediate MDT request is not allowed.
True: Management Based Immediate MDT request is allowed.
MDT_UE_PICKUP_RATE This parameter represents the selection rate which it uses when selecting the
Management Based MDT object UE. If the random number generated
between 0 is this value or less, select as MDT object UE.
Counters and KPIs

REFERENCE
[6] 3GPP 32.422: Trace control and configuration management
Chapter 10 System Test and
Analysis
LTE-OM9001, Cell Traffic Trace

INTRODUCTION
This feature provides detailed information at call level on all UEs in a specific cell.
The traceable interfaces are UE-Associated S1, X2 and RRC. This trace result is
transmitted to LSM or Trace Collection Entity (TCE) server.
BENEFITS
This feature allows operator to analyze all the signaling messages transmitting and
receiving in a specific cell, which can be used for troubleshooting.

Dependency
The LSM and MME are required.
The TCE server is required.
Limitation
The LSM can act as TCE server, but stores simultaneously trace results from up
to six cells in E-UTRAN system.
In case of CPU overload status, tracing can be suspended to prevent the negative
impact on the service users.
FEATURE DESCRIPTION
Samsung eNB provides 3GPP standard (TS 32.422 & 32.423) based Subscriber
and Equipment Trace. This feature performs tracing signalling interface messages
on all calls in the specific cell. The operator can control the cell traffic trace using
cell ID through LSM. If trace results are generated, eNB reports the results to TCE.
Chapter 10 System Test and Analysis
When several PLMNs are supported in the RAN, for starting Trace eNB shall only
select UEs where the pLMNTarget = selectedPLMN-Identity that UE includes in
RRCConnectionSetup message 3GPP TS 36.331.
Management based trace procedure is as follows:
Management Based Trace Activation (New Call)
Management Based Trace Activation (Undergoing call setup)
Management Based Trace Activation (Existing Call)
Management Based Trace Deactivation
If a call ends normally by sending a RRC Connection Release message to UE, the
trace recording session for that call is ended. To stop tracing for the cell, the
deactivate trace message is send to eNB through LSM.
SYSTEM OPERATION
How to Activate
The procedure for enabling cell traffic trace is as follows:
1 Log into LSM and select Performance Management | Call Trace.

2 Perform the management-based trace for a trace type.
3 The operator can select the following input parameters
oTarget eNB
oList of interface: S1, X2, and Uu
oDepth: Minimum, Medium, and Maximum
oTarget cell ID
4 Press REGISTER button, then [Register Call Trace] window is displayed.
5 Press Start button, then [Display Real Time Data] window is displayed.
6 Click DELETE button, then trace is deleted.
7 Click REFRESH button, then list in the trace list table is re-displayed.
Key Parameters
RTRV-TCE-LIST/CHG-TCE-LIST/CRTE-TCE-LIST/DLT-TCE-LIST
tceType This parameter represents the TCE server type and has to one of three below
values.
standAlone: TCE Server is standAlone Type.
lsmEmbedded: TCE Server is embedded in LSM
smartSon: TCE Server is for Smart SON server
Counters and KPIs

Collected Data on Uu Interface according to the trace depth are as follows:
Data Name Message Name Description
CS Fallback indicator MOBILITY FROM EUTRA Whether a fallback to CS network is
COMMAND possible
CN Domain PAGING Identifies whether the domain is CS
or PS network.
S-TMSI PAGING S-TMSI information of UE (MME
code, M-TMSI)
ReestablishmentCause RRC CONNECTION Cause of UEs re-establishment
REESTABLISHMENT REQUEST
Wait time RRC CONNECTION REJECT The period of time for which the
system waits until UE attempts a call
again
Release Cause RRC CONNECTION RELEASE The reason for which UEs
connection has been released
Redirection Information RRC CONNECTION RELEASE The carrier frequency of the RAT
used by UE during cell reselection
Establishment Cause RRC CONNECTION REQUEST The reason for which UEs
connection has been established
Selected PLMN-Identity RRC CONNECTION SETUP The UE selected PLMN ID
COMPLETE

RegisteredMME RRC CONNECTION SETUP Information of MME with which UE is
COMPLETE registered
Rat-Type UE CAPABILITY INFORMATION The RAT information of the
capabilities given by UE
Measured Results MEASUREMENT REPORT The results measured by the terminal
CDMA2000-Type HANDOVER FROM EUTRA CDMA2000Type information (1xRTT,
PREPARATION REQUEST HRPD)
UL HANDOVER PREPARATION
TRANSFER
UL INFORMATION TRANSFER
Target RAT Type MOBILITY FROM EUTRA The RAT information for the target
COMMAND
Collected Data on S1 Interface according to the trace depth are as follows:

E-RAB ID All messages containing the ID E-RAB ID
E-RAB Level QoS E-RAB SETUP REQUEST QoS for E-RAB
Parameters E-RAB MODIFY REQUEST
INITIAL CONTEXT SETUP
REQUEST
Cause INITIAL CONTEXT SETUP Cause for failure of the message
FAILURE
UE CONTEXT RELEASE
REQUEST
UE CONTEXT RELEASE
COMMAND
UE CONTEXT MODIFICATION
FAILURE
HANDOVER REQUIRED
HANDOVER PREPARATION
FAILURE
HANDOVER REQUEST
HANDOVER FAILURE
HANDOVER CANCEL
PATH SWITCH REQUEST
FAILURE
NAS NON DELIVERY INDICATION
Handover Type HANDOVER REQUIRED Handover type (IntraLTE,
HANDOVER COMMAND LTEtoUTRAN...)
HANDOVER REQUEST
E-UTRAN CGI HANDOVER NOTIFY Cell global ID of eNB (PLMN ID + cell
PATH SWITCH REQUEST ID)
INITIAL UE MESSAGE
UPLINK NAS TRANSPORT
TAI HANDOVER NOTIFY Tracking area ID of eNB (PLMN ID +
PATH SWITCH REQUEST TAC)

Target ID HANDOVER REQUIRED ID of the target RAT which is the
handover target
CDMA2000 HO Status DOWNLINK S1 CDMA2000 Whether HO to the CDMA2000 is
TUNNELING successful
CDMA2000 RAT Type DOWNLINK S1 CDMA2000 RAT information of the CDMA2000
TUNNELING (1xRTT, HRPD)
UPLINK S1 CDMA2000
TUNNELING
CDMA2000 Sector ID UPLINK S1 CDMA2000 TUNNELING Sector ID of the CDMA2000
CDMA2000 HO Required UPLINK S1 CDMA2000 TUNNELING Whether UE has to prepare handover
Indication to the CDMA2000
Collected Data on X2 Interface according to the trace depth are as follows:

E-RAB id All messages where it is present ID of E-RAB
E-RAB Level QoS HANDOVER REQUEST QoS for E-RAB
Cause HANDOVER REQUEST Cause information of each message
HANDOVER PREPARATION
FAILURE
HANDOVER CANCEL
Target Cell ID HANDOVER REQUEST Handover targets cell ID
GUMMEI HANDOVER REQUEST Handover targets GUMMEID
UE History Information HANDOVER REQUEST History of UE
REFERENCE
[3] 3GPP TS32.422 Telecommunication management; Subscriber and equipment
trace; Trace control and configuration management
trace; Trace data definition and management
LTE-OM9002, Subscriber and Equipment Trace

INTRODUCTION
The Subscriber and Equipment Trace provide detailed information at call level on
one or more specific mobile(s). This data is transmitted to the TCE server.
BENEFITS
This feature allows operator to analyze the signaling messages transmitting and
receiving through S1-MME, X2 and Uu interfaces for a designated user, which can
be used for troubleshooting.

Dependency
The TCE and MME are required.
The LSM can act as TCE server if LSM connect with Samsung Core system.
Limitation
If CPU critical alarm is occurred, all traces stop for system protection.
In case of using TCE server, operator should register TCE IP Address on eNB
through ASM.
FEATURE DESCRIPTION
Samsung eNB provides 3GPP standard (TS 32.422 & 32.423) based Subscriber
and Equipment Trace.
This feature performs tracing signaling interface messages on a specific UE.
Also, this feature supports mobility. If Trace Activation IE is contained in the
Initial Context Setup Request message, or Trace Start message is received from
MME, the eNB starts a trace for the call. If Trace Activation IE is contained in the
Handover Request message received from the source eNB or MME in case of X2
or S1 Handover, eNB starts a trace for the call.
If trace results are generated, eNB reports the results to TCE.
Signaling based trace procedure is as follows:

Signaling Based Trace Activation
Signaling based trace deactivation
If a call ends normally by sending a RRC Connection Release message to UE, the
trace for that call is ended. To stop the tracing, the deactivate trace message is send
to eNB through MME.
SYSTEM OPERATION
How to Activate
If Trace Activation IE is included in the Initial Context Setup Request message,
the Trace Start message or the Handover Request (S1/X2) message from MME,
the eNB starts trace for the call.
The operator can control the trace disable/resume threshold.
oIf CPU state is higher than disable threshold, trace will be paused.
oAfter trace disabled, CPU state is lower than resume threshold, trace will
restart.
Key Parameters
RTRV-TCE-LIST/CHG-TCE-LIST/CRTE-TCE-LIST/DLT-TCE-LIST
tceType This parameter represents the TCE server type and has to one of three below
values:
standAlone: TCE Server is standAlone Type.
lsmEmbedded: TCE Server is embedded in LSM
smartSon: TCE Server is for Smart SON server
Counters and KPIs

Collected Data on Uu Interface according to the trace depth are as follows:
CS Fallback indicator MOBILITY FROM EUTRA Whether a fallback to CS network is
COMMAND possible

CN Domain PAGING Identifies whether the domain is CS or
PS network.
S-TMSI PAGING S-TMSI information of the UE (MME
code, M-TMSI)
ReestablishmentCause RRC CONNECTION Cause of UEs re-establishment
REESTABLISHMENT REQUEST
Wait Time RRC CONNECTION REJECT The period of time for which the system
waits until UE attempts a call again
Release Cause RRC CONNECTION RELEASE The reason for which UEs connection
has been released
Redirection Information RRC CONNECTION RELEASE The carrier frequency of RAT used by
UE during cell reselection
Establishment Cause RRC CONNECTION REQUEST The reason for which UEs connection
has been established
Selected PLMN-Identity RRC CONNECTION SETUP The UE selected PLMN ID
COMPLETE
RegisteredMME RRC CONNECTION SETUP Information of MME with which UE is
COMPLETE registered
Rat-Type UE CAPABILITY INFORMATION The RAT information of the capabilities
given by UE
Measured Results MEASUREMENT REPORT The results measured by the terminal
CDMA2000-Type HANDOVER FROM EUTRA CDMA2000Type information (1xRTT,
PREPARATION REQUEST HRPD)
UL HANDOVER PREPARATION
TRANSFER
UL INFORMATION TRANSFER
Target RAT Type MOBILITY FROM EUTRA The RAT information for the target
COMMAND
Collected Data on S1 Interface according to the trace depth are as follows:

E-RAB ID All messages containing the ID E-RAB ID
E-RAB Level QoS E-RAB SETUP REQUEST QoS for E-RAB
Parameters E-RAB MODIFY REQUEST
INITIAL CONTEXT SETUP REQUEST
Cause INITIAL CONTEXT SETUP FAILURE Cause for failure of the message
UE CONTEXT RELEASE REQUEST
UE CONTEXT RELEASE COMMAND
UE CONTEXT MODIFICATION
FAILURE
HANDOVER REQUIRED
HANDOVER PREPARATION FAILURE
HANDOVER REQUEST
HANDOVER FAILURE
HANDOVER CANCEL
PATH SWITCH REQUEST FAILURE
NAS NON DELIVERY INDICATION

Handover Type HANDOVER REQUIRED Handover type (IntraLTE,
HANDOVER COMMAND LTEtoUTRAN...)
HANDOVER REQUEST
E-UTRAN CGI HANDOVER NOTIFY Cell global ID of eNB (PLMN ID +
PATH SWITCH REQUEST cell ID)
INITIAL UE MESSAGE
TAI HANDOVER NOTIFY Tracking area ID of eNB (PLMN
PATH SWITCH REQUEST ID + TAC)
Target ID HANDOVER REQUIRED ID of the target RAT which is the
handover target
CDMA2000 HO Status DOWNLINK S1 CDMA2000 TUNNELING Whether HO to CDMA2000 is
successful
CDMA2000 RAT Type DOWNLINK S1 CDMA2000 RAT information of CDMA2000
TUNNELING (1xRTT, HRPD)
UPLINK S1 CDMA2000 TUNNELING
CDMA2000 Sector ID UPLINK S1 CDMA2000 TUNNELING Sector ID of the CDMA2000
CDMA2000 HO Required UPLINK S1 CDMA2000 TUNNELING Whether UE has to prepare
Indication handover to the CDMA2000
Collected data on X2 Interface according to the trace depth is as follows:

E-RAB id All messages where it is present ID of E-RAB
E-RAB Level QoS HANDOVER REQUEST QoS for E-RAB
Cause HANDOVER REQUEST Cause information of each
HANDOVER PREPARATION FAILURE message
HANDOVER CANCEL
Target Cell ID HANDOVER REQUEST Handover targets cell ID
GUMMEI HANDOVER REQUEST Handover targets GUMMEID
UE History Information HANDOVER REQUEST History of UE
REFERENCE
UTRAN); S1 application Protocol (S1AP)
trace; Trace control and configuration management
trace; Trace data definition and management
LTE-OM9004, CSL (Call Summary Log) Report

INTRODUCTION
This feature collects the detail information for a call. The call release type, call
duration, and handover information and so on are automatically collected and
transmitted to EMS or external server.
BENEFITS
The operator can analyze the detail information of a call.

Dependency
External server for CSL data is required.
Limitation
To support for all calls including normal calls, it is required to explain in advance
about expending LSM capacity or external server. (Basically, LSM can store only
the CSL data of abnormal calls.)
FEATURE DESCRIPTION
The CSL data is collected by eNB. When a call is setup, eNB starts to collect
information for the call. If the call is released, eNB reports CSL data to the
external server.
By the configuration, eNB can support following cases:

Case1: LSM- CSL data of abnormal calls
Case2: LSM- CSL data of all calls
Case3: LSM- CSL data of abnormal calls, External server - CSL data of all calls
Case4: LSM- CSL data of all calls, External server - CSL data of all calls
The CSL data includes detail information for a call. It includes a total of 10
information items: call information, common item information, connection
information, release information, handover information, throughput information,
RF information, adjacency information, UE history information, and call
debugging information.
SYSTEM OPERATION
How to Activate
The operator can control to report the collected CSL information to external server
by executing the CHG-CSL-INFO COMMAND.
Key Parameters
RTRV-CSL-INF/CHG-CSL-INF
DB_INDEX Index
CSL_SERVER The type of CSL Server.
Counters and KPIs

There are no a related counters or KPIs.
REFERENCE
LTE-OM9010, VoLTE Monitoring

INTRODUCTION
The operator commands into Element Management System (EMS) to trigger the
trace of VoLTE calls (UEs or cells) at eNBs. The eNB, after receiving the
commands from EMS, collects the information of VoLTE traffic and sends them
to EMS (or the external server). The operator can analyze the quality of VoLTE
service and identify the cause and the location of problems traffic by post-
processing the collected information.
BENEFIT
The operator can get benefits in analyzing the quality of VoLTE service and
identifying the cause and location of problems.
VoLTE quality monitoring: Loss, jitter, and delay
Identification of problem causes: Decompression failure due to RoHC error, loss,
duplicated packet, out-of-order, and delay
Isolation of the section that problems occur: UL air, backhaul + core network,
inter eNB, and DL air section

Dependency
The LTE device
The EMS is required.
The Mobility Management Entity (MME) is required to get TraceReference for
UE trace scenario.
The Global Positioning System (GPS) is required to analyze the delay of VoLTE
packets.
Limitation
The number of simultaneous UEs to be monitored per cell/eNB (TBD)
FEATURE DESCRIPTION
Basic concept
The operator commands into EMS (Element Management System) to trigger the
collection of the information of VoLTE traffic (for some UEs or cells) at eNBs.
The eNB, received the commands from EMS, collects the information of VoLTE
traffic as indicated and sends them to the EMS or external server.
The operator can monitor and analyze the quality of VoLTE traffic by post-
processing the collected data.
The following figure shows VoLTE monitoring:
S1-C S6a
MME HSS
Uu
S11 S7 PCRF
LTE UE S1-U Operators

Serving S5/S8 PDN- SGi
Gateway Gateway IP services
E NodeB e.g. IMS
eNodeB sends the
information of VoLTE
traffic periodically
EMS commands to eNodeB and
saves the information of VoLTE
traffic
Operation Scenario
UE Trace
The operator can select several VoLTE UEs to be monitored by using
TraceReference. Therefore, end-to-end VoLTE quality from originating UE to
terminating UE can be monitored.
Before enable VoLTE monitoring tool, operator should know TraceReference of a
specific VoLTE UE to be monitored. (for example, from signal trace)
Cell trace
The operator can select cells, which are to be monitored by using specific cell ID.
Then random VoLTE UEs in a certain cell are monitored. Therefore, VoLTE
quality of a certain cell can be monitored.
The following figure shows flow chart and collected information:
eNodeB EMS
g ON
Monitorin
Log data includes:

- RTP header and Time stamp
- RoHC error event
Send Log da
ta periodically - SIP packet and Time stamp
- Transmission completion time to UE
Analyzing Results (Example)

By post-processing the collected information, operator can analyze the quality of
VoLTE service (such as loss, jitter, and delay) and identifying the cause (such as
decompression failure due to RoHC error, loss, duplicated packet, out-of-order,
and delay) and the location of problems for each section (such as UL air,
backhaul+Core network, inter eNB, and DL air section).
SYSTEM OPERATION
How to Activate
To activate this feature, for UE based VoLTE monitoring, operator uses the
CHG-VOMA-UE command to register Trace Reference of the specific UE for
VoLTE Monitoring. It is noted that operator has to register signaling based
trace for this UE in advance, to retrieve Trace Reference. In case of each
VOMA_INDEX, different trace reference (=TRACE_REFERENCE_MCC +
TRACE_REFERENCE_MNC + TRACE_ID) will be assigned, if operator use
this trace reference, VOMA_USAGE will be set to EQUIP.
To activate this feature, for Cell level VoLTE monitoring, operator uses the
CHG-VOMA-CELL command to change VOMA_USAGE to EQUIP for a
specific Cell.
Key Parameters
CHG-VOMA-UE/RTRV-VOMA-UE
VOMA_INDEX This attribute indicates Trace-Reference index which is on the VoMA
Trace.
VOMA_USAGE This attribute indicates the UE is used or not for VoMA Trace.
TRACE_REFERENCE_MCC It is MCC (Mobile Country Code) of the Trace Reference for which VoMA
trace is triggered.
For example, if the Trace Reference received by S1AP or X2AP message
is 43 58 07 00 34 D7, its BCD format PLMN ID is 43 58 07, and MCC is
348. (Reference : TS 32.423)
TRACE_REFERENCE_MNC It is MNC (Mobile Network Code) of the Trace Reference for which VoMA
trace is triggered.
For example, if the Trace Reference received by S1AP or X2AP message
is 43 58 07 00 34 D7, its BCD format PLMN ID is 43 58 07, and MNC is
570. (Reference : TS 32.423)
TRACE_ID This attribute indicates decimal format of Trace ID in the Trace Reference
for which VoMA trace is triggered. For example, if the trace reference
received by S1AP or X2AP message is 43 58 07 00 34 D7, its BCD
format PLMN ID is 43 58 07, and its Trace ID is 00 34 D7 in hexadecimal
format and stored in this attribute as decimal number13527. (Reference:
TS 32.423)
VOMA_QCI0 This attribute indicates the first VoMA Trace QCI.
VOMA_QCI0_MAX_LENGTH This attribute indicates maximum length, which includes PDCP header
and logging payload for QCI0.
CHG-VOMA-CELL/RTRV-VOMA-CELL
CELL_NUM Cell number
VOMA_USAGE This attribute indicates the cell is used or not for VoMA Trace.
Counters and KPIs

REFERENCE
N/A
LTE-OM9100, Key Performance Indexes

INTRODUCTION
The Key Performance Indicators (KPIs) are used to monitor the quality of service
provided to the end-user. They are calculated using counters collected by eNB.
Some KPIs are defined in TS32.450 while others are proprietary to Samsung. This
feature provides a brief introduction to KPIs. In case of detailed information, refer
to Samsung LTE system counter description manual.
BENEFIT
The operator can monitor the following characteristics of service provided to the
end user.
Accessibility
Retainability
Integrity
Availability
Mobility

N/A
FEATURE DESCRIPTION
ACCESSIBILITY
ACCESSIBILITY
These KPIs show probability for the end-user to be provided with E-RAB at
request. The probability success rate for E-RAB establishment is calculated by
multiplying the probability success rates for different parts of E-RAB
establishment. The probability success rate for each part of E-RAB establishment
is calculated as successful attempts divided by total number of attempts.
The following table shows the formula:
Name Description
ErabAccessibilityInit = (SumRrcConnEstabSucc/SumRrcConnEstabAtt) Initial E-RAB establishment success
* (SumS1sigS1ConnEstabSucc/SumS1sigS1ConnEstabAtt) * rate
(SumErabEstabInitSuccNbr/SumErabEstabInitAttNbr) * 100%.
ErabAccessibilityAdd = Added E-RAB establishment
(SumErabEstabAddSuccNbr/SumErabEstabAddAttNbr) * 100%. success rate
Name Description
E-RAB Connection Failure Rate = 0 if SumRrcConnEstabAtt = 0 OR Probability that the end-user is not
SumS1sigS1ConnEstabAtt = 0 OR SumErabEstabInitAttNbr = 0. provided with E-RAB at the initial
Otherwise, E-RAB Connection Failure Rate = 100 - request
(SumRrcConnEstabSucc/SumRrcConnEstabAtt) *
(SumS1sigS1ConnEstabSucc/SumS1sigS1ConnEstabAtt) *
(SumErabEstabInitSuccNbr/SumErabEstabInitAttNbr) * 100%
RACH_SUCCESS_RATE
These KPIs measure RACH success rate.
Name Description
NonHoRachSuccessRate = ((RachSumConnEstabSucc+ Non-Handover RACH success Rate
RachSumConnReEstabSucc)/(RachSumRandomlySelectedPreambles
Low + RachSumRandomlySelectedPreamblesHigh)) * 100 %
HoRachSuccessRate = ((RachSumIntraEnbInSucc + Handover RACH Success Rate
RachSumInterX2InSucc +
RachSumInterS1InSucc)/RachSumDedicatedPreambles) * 100 %
CONN_DROP_RATE
This KPI measures the ratio of number of abnormally terminated E-RABs to
number of successfully established E-RABs.
Name Description
ConnDropRate = Probability that the end-user
CdrRelActive/(CdrSumEstabInitSuccNbr+CdrEstabAddSuccNbr)*100 % abnormally loses E-RAB
SUCCESS_RATE
This KPI measures RRC success rate, ERAB success rate, and call drop rate based
on the RRC, ERAB, CALL_DROP, and HO statistics collected.
Name Description
RrcEstabSuccessRatio = The average success rate of
(SumRrcEstabSuccess/SumRrcEstabAttempt) * 100%. RRC_ESTAB.
ErabEstabSuccessRatio = (SumErabEstabSuccess/ The average success rate of
SumErabEstabAttempt) * 100%. ERAB_ESTAB.
CallDropRatio = (SumCallDrop_EccbDspAuditRlcMacCallRelease + The average call drop rate.
SumCallDrop_EccbRcvResetRequestFromEcmb +
SumCallDrop_EccbRcvCellReleaseIndFromEcmb +
SumCallDrop_EccbRadioLinkFailure +
SumCallDrop_EccbDspAuditMacCallRelease +
SumCallDrop_EccbArqMaxRetransmission +
SumCallDrop_EccbDspAuditRlcCallRelease +
SumCallDrop_EccbTmoutRrcConnectionReconfig +
SumCallDrop_EccbTmoutRrcConnectionReestablish +
SumCallDrop_EccbS1SctpOutOfService/SumEstabInitSuccNbr +
SumInterX2InSucc + SumInterS1InSucc + SumRatInSuccUTRAN) *
100 %.
CONN_TIME
This KPI measures the connection setup time from RRC CONNECTION
REQUEST message to INITIAL CONTEXT SETUP RESPONSE message.
Name Description
ConnSetupTime = (ConnTimeConnEstabTimeTot + Elapsed time from transmitting RRC Connection
ConnTimeEstabTimeTot + Request to receiving Initial Context Setup Response
ConnTimeS1SigTimeTot)/(ConnTimeConnEstabTime
Cnt + ConnTimeEstabTimeCnt +
ConnTimeS1SigTimeCnt)
RETAINABILITY
RETAINABILITY
This KPI shows how often the end-user abnormally loses E-RAB during the time
of E-RAB is used.
Name Description
ErabRetainability = Number of E-RABs with data in a buffer that was
(SumRelActive/RetainSessionTimeUE) * 100. abnormally released, normalized with number of data
session time units.
RETAINABILITY_QCI
This KPI shows how often the end-user abnormally loses an E-RAB (per QCI)
during the time of E-RAB is used.
Name Description
ErabRetainability = The number by dividing the E-RAB Release count by
(RetainRelActive/RetainSessionTimeQci) * 100 %. E-RAB holding time.
INTEGRITY
INTEGRITY
These KPIs show how E-UTRAN impacts the service quality provided to the end-
user.
Name Description
EutranIpThroughput = E-UTRAN IP throughput per QCI
IntegrityEutranIpThroughputTot/IntegrityEutranIpThrou
ghputCnt
EutranIpLatency = E-UTRAN IP latency per QCI
IntegrityEutranIpLatencyTot/IntegrityEutranIpLatencyC
nt
CELL_THRU
These KPIs measure DL/UL cell throughput and DL/UL UE throughput.

Name Description
CellThruDLAvg = CellThruDLTot/CellThruDLCnt Average Downlink sector Throughput Counter
CellThruULAvg = CellThruULTot/CellThruULCnt Average Uplink sector Throughput Counter
UEThruDLAvg = UEThruDLTot/UEThruDLCnt Average Downlink UE Throughput Counter
UEThruULAvg = UEThruULTot/UEThruULCnt Average Uplink UE Throughput Counter
CellThruDLPeak Peak Downlink sector Throughput Counter
CellThruDLTime Number of seconds for Downlink Throughput within a
Recording Period Counter
CellThruULPeak Number of seconds for Uplink Throughput within a
Recording Period Counter
CellThruULTime Peak Uplink sector Throughput Counter
UEThruDLPeak Peak Downlink UE Throughput Counter
UEThruULPeak Peak Uplink UE Throughput Counter
WEIGHTED_CQI
This KPI measures average channel quality indicator (CQI) reported by UEs.
Name Description
WeightedDLReceivedCQI = Average of channel quality indicator reported by UEs
SumWeightedDLReceivedCQI/SumDLReceivedCQI
AVAILABILITY
AVAILABILITY
This KPI measures the availability of E-UTRAN cell.
Name Description
EutranCellAvailability = ((CellAvailPmPeriodTime - Percentage of time the cell is considered available
ReadCellUnavailableTime)/CellAvailPmPeriodTime) *
100 %.
CELL_CAPACITY
This KPI measures the average simultaneous RRC-connected UE load per cell.
The Following table shows the formula:
Name Description
ConnNoUEAvg = The average RRC Connection Capacity rate (%) per
(ConnNoRrcAvg/ConnMaxCallCount) * 100 %. unit time.
ConnNoUEMax The maximum RRC Connection Capacity rate (%)
per unit time.
UsageNbrRbAvg = The average E-RAB Capacity rate (%) per unit time.
(UsageNbrErab/UsageMaxDrbCount) * 100 %.
UsageNbrRbMax The maximum E-RAB Capacity rate (%) per unit
time.
ConnNoRrcAvg The average RRC Connection per unit time.
Name Description
ConnMaxCallCount The average available call count in the cell.
UsageNbrErab The average number of E-RAB per unit time.
UsageMaxDrbCount The maximum available number of E-RAB in the cell.
ENB_CAPACITY
This KPI measures the average simultaneous RRC-connected UE load per eNB.
Name Description
EnbConnNoUEAvg = The average RRC Connection Capacity rate (%) per
(EnbConnNoRrcAvg/EnbMaxCallCount) * 100 %. unit time.
EnbConnNoRrcAvg The average RRC Connection per unit time.
EnbMaxCallCount The average available call count in eNB.
MOBILITY
MOBILITY
These KPIs measure E-UTRAN handover success rates.
Name Description
EutranMobilityHOIntra = Intra-eNB handover success rate
(sumHOIntra_Succ/sumHOIntra_Att) * 100 %.
EutranMobilityHOX2Out = Outgoing X2 handover success rate
(sumHOX2Out_Succ/sumHOX2Out_Att) * 100 %.
EutranMobilityHOX2In = Incoming X2 handover success rate
(sumHOX2In_Succ/sumHOX2In_Att) * 100 %.
EutranMobilityHOS1Out = Outgoing S1 handover success rate
(sumHOS1Out_Succ/sumHOS1Out_Att) * 100 %.
EutranMobilityHOS1In = Incoming S1 handover success rate
(sumHOS1In_Succ/sumHOS1In_Att) * 100 %.
EutranMobilityHOInterRatHrpd = Inter-RAT optimized HRPD handover success rate
(sumHOInterRatHrpd_Succ/sumHOInterRatHrpd_A
tt) * 100 %.
EutranMobilityHOInterRatUtranOut = Outgoing inter-RAT handover success rate
(sumHOInterRatUtranOut_Succ/sumHOInterRatUtr
anOut_Att) * 100 %.
EutranMobilityHOInterRatUtranIn = Incoming inter-RAT handover success rate
(sumHOInterRatUtranIn_Succ/sumHOInterRatUtran
In_Att) * 100 %.
EutranMobilityHOInter = ((sumHOS1Out_Succ + Outgoing handover success rate to an eNB of the same
sumHOX2Out_Succ)/(sumHOS1Out_Att + frequency
sumHOX2Out_Att)) * 100 %.
VOLTE_HO_SUCCESS_RATE
These KPIs measure VoLTE handover success rate.
Name Description
VoLTE_IntraHoSuccessRate = VoLTE HO Intra Success rate
(SumVoLTE_IntraEnbSucc/SumVoLTE_IntraEnbAtt) *
100 %
VoLTE_X2HoSuccessRate = VoLTE HO X2 Success rate
(SumVoLTE_InterX2OutSucc/SumVoLTE_InterX2OutAtt)
* 100 %
VoLTE_S1HoSuccessRate = VoLTE HO S1 Success rate
(SumVoLTE_InterS1OutSucc/SumVoLTE_InterS1OutAtt)
* 100 %
LBHO_KPI
These KPIs measure load-balancing handover success rate.
Name Description
InterEnbHoSuccRatio = Inter-eNB load balancing handover success rate
(SumInterEnbMlbHoSucc/SumInterEnbMlbHoAtt) *
100 %
IntraEnbIntraCarrierGroupHoSuccRatio = Intra-eNB load balancing handover success rate to a
(SumIntraEnbIntraCarrierGroupMlbHoSucc/SumIntr separate carrier within the same eNB of the same
aEnbIntraCarrierGroupMlbHoAtt) * 100 % frequency due to load balancing
IntraEnbInterCarrierGroupHoSucRatio = Intra-eNB load balancing handover success rate to a
(SumIntraEnbInterCarrierGroupMlbHoSucc/SumIntr separate carrier within the same eNB of the different
aEnbInterCarrierGroupMlbHoAtt) * 100 % carrier group due to load balancing
SendbackHOSuccRatio = Handover success ratio by sendback in eNB
(SumSendbackHOSucc/SumSendbackHOAtt) *
100 %
SYSTEM OPERATION
N/A
REFERENCE
[1] LTE eNB Counter Description for SLR 5.0.
[2] 3GPP TS 32.450: Key performance indicators: Definitions.
[3] 3GPP TS 32.425: Performance measurements.
[4] 3GPP TS 32.404: Performance measurements: Definitions and templates.
LTE-OM9101, L1 and L2 Counters

INTRODUCTION
The Layer 1 (L1) and Layer 2 (L2) counters provide the data for statistical analysis
at PHY/MAC layers. This data is used to monitor E-UTRAN performance. Some
of these counters are defined in TS32.425 while others are specific to Samsung.
This feature provides a brief introduction to counters. Only the counters which are
visible to operators and are collected at PHY/MAC layers are included in this
feature. In case of detailed information about all available counters, refer to
Samsung LTE system counter description manual.
BENEFIT
The operator can get data to perform statistical analysis related to the following:
Air MAC performance
PRB utilization
Radio resource utilization
Random access performance
Hybrid ARQ performance
Adaptive modulation and coding performance
Carrier aggregation performance
eICIC performance
E-RAB session time
Received signal power statistics
Transmitted signal power statistics

Dependency
The LSM server should be available for receiving statistics data from eNB.
FEATURE DESCRIPTION
AIR MAC PERFORMANCE
AIR_MAC_BYTES
Name Description
Name Description
AirMacByteUl The sum of the size of MAC PDU successfully received via PUSCH during the
statistics period.
AirMacTtiUl The sum of sections that have MAC PDU successfully received via PUSCH
during the statistics period.
AirMacUlThru Average size per second of MAC PDU successfully received via PUSCH.
AirMacUlEfctivThru Average size of MAC PDU of the section successfully received via PUSCH
AirMacByteDl The sum of the size of DCCT/DTCH MAC PDU that received HARQ ACK
among MAC PDU transmitted via PDSCH during the statistics period.
AirMacTtiDl The sum of sections that have MAC PDU successfully transmitted via PDSCH
AirMacDlThru Average size per second of DCCT/DTCH MAC PDU that received HARQ ACK
AirMacDlEfctivThru Average size of MAC PDU of the section successfully transmitted via PDSCH
AirMacUlThruMin Minimum of the average size per second of MAC PDU successfully received via
PUSCH
AirMacUlThruMax Maximum of the average size per second of MAC PDU successfully received
via PUSCH
AirMacDlThruMin Minimum of the average size per second of DCCT/DTCH MAC PDU that
received HARQ ACK among MAC PDU transmitted via PDSCH during the
statistics period.
AirMacDlThruMax Maximum of the average size per second of DCCT/DTCH MAC PDU that
statistics period.
ULIpThruVol The cumulated number that indicates the sum of the sizes of MAC SDUs that
were successfully received through the PUSCH during the sample intervals of
all UEs in the collection interval.
ULIpThruTime The cumulated number of TTIs during the sample intervals of all UEs in the
collection interval.
ULIpThruAvg The calculated number that indicates the average per-second size which is
derived from that MAC SDUs that were successfully received through the
PUSCH during the sample intervals of all UEs is divided by TTIs during the
sample intervals in the collection interval.
AIR_MAC_BYTES_PLMN
Name Description
PLMNAirMacULByte The sum of the size of MAC PDU successfully received via PUSCH during the
statistics period.
PLMNAirMacULTti The sum of sections that have MAC PDU successfully received via PUSCH
PLMNAirMacULThruAvg Average size per second of MAC PDU successfully received via PUSCH.
PLMNAirMacULEfctivThruA Average size of MAC PDU of the section successfully received via PUSCH
vg during the statistics period.
PLMNAirMacDLByte The sum of the size of DCCT/DTCH MAC PDU that received HARQ ACK
PLMNAirMacDLTti The sum of sections that have MAC PDU successfully transmitted via PDSCH
Name Description
PLMNAirMacDLThruAvg Average size per second of DCCT/DTCH MAC PDU that received HARQ ACK
PLMNAirMacDLEfctivThruA Average size of MAC PDU of the section successfully transmitted via PDSCH
vg during the statistics period
PLMNAirMacULThruMin Minimum of the average size per second of MAC PDU successfully received via
PUSCH
PLMNAirMacULThruMax Maximum of the average size per second of MAC PDU successfully received via
PUSCH
PLMNAirMacDLThruMin Minimum of the average size per second of DCCT/DTCH MAC PDU that
statistics period
PLMNAirMacDLThruMax Maximum of the average size per second of DCCT/DTCH MAC PDU that
statistics period
AIR_MAC_BYTES_PCELL
Name Description
AirMacULByte The sum of the size of MAC PDU successfully received via PUSCH during the
statistics period
AirMacULTti The sum of sections that have MAC PDU successfully received via PUSCH
AirMacULThruAvg Average size per second of MAC PDU successfully received via PUSCH
AirMacULEfctivThruAvg Average size of MAC PDU of the section successfully received via PUSCH
AirMacDLByte The sum of the size of DCCT/DTCH MAC PDU that received HARQ ACK
among MAC PDU transmitted via PDSCH during the statistics period
AirMacDLTti The sum of sections that have MAC PDU successfully transmitted via PDSCH
AirMacDLThruAvg Average size per second of DCCT/DTCH MAC PDU that received HARQ ACK
AirMacDLEfctivThruAvg Average size of MAC PDU of the section successfully transmitted via PDSCH
AirMacULThruMin Minimum of the average size per second of MAC PDU successfully received via
PUSCH
AirMacULThruMax Maximum of the average size per second of MAC PDU successfully received
via PUSCH
AirMacDLThruMin Minimum value of average size per second of DCCT/DTCH MAC PDU that
statistics period
AirMacDLThruMax Maximum value of average size per second of DCCT/DTCH MAC PDU that
statistics period
AIR_MAC_BYTES_SCELL
Name Description
AirMacULByte The sum of the size of MAC PDU successfully received via PUSCH during the
statistics period
AirMacULTti The sum of sections that have MAC PDU successfully received via PUSCH
AirMacULThruAvg Average size per second of MAC PDU successfully received via PUSCH.
AirMacULEfctivThruAvg Average size of MAC PDU of the section successfully received via PUSCH
AirMacDLByte The sum of the size of DCCT/DTCH MAC PDU that received HARQ ACK
AirMacDLTti The sum of sections that have MAC PDU successfully transmitted via PDSCH
AirMacDLThruAvg Average size per second of DCCT/DTCH MAC PDU that received HARQ ACK
AirMacDLEfctivThruAvg Average size of MAC PDU of the section successfully transmitted via PDSCH
AirMacULThruMin Minimum of the average size per second of MAC PDU successfully received via
PUSCH
AirMacULThruMax Maximum of the average size per second of MAC PDU successfully received
via PUSCH
AirMacDLThruMin Minimum value of average size per second of DCCT/DTCH MAC PDU that
statistics period
AirMacDLThruMax Maximum value of average size per second of DCCT/DTCH MAC PDU that
statistics period
PRB UTILIZATION
PRB_QCI
Name Description
PrbDl The PRB usage used as downlink DTCH traffic
PrbUl The PRB usage used as uplink DTCH traffic
PRB_TOTAL
Name Description
TotPrbDLAvg The resource used for PDSCH/PDCCH transmission among the total downlink
resource
TotGbrPrbDLAvg Ratio of the resource used to transmit GBR traffic against the total downlink
resources.
TotNGbrPrbDLAvg Ratio of the resource used to transmit non-GBR traffic against the total downlink
resources.
Name Description
TotPrbULAvg The resource used for PUSCH transmission among the total uplink resource
TotGbrPrbULAvg Ratio of the resource used to transmit GBR traffic against the total uplink
resources.
TotNGbrPrbULAvg Ratio of the resource used to transmit non-GBR traffic against the total uplink
resources.
TotPucchPrbULAvg The resource used for PUCCH transmission among the total uplink resource
TotPucchPuschPrbULAvg The resource used for PUCCH/PUSCH transmission among the total uplink
resource
TotNgbrSCellPrbDLAvg Ratio of the resource used to transmit non-GBR traffic of SCell against the total
downlink resources.
PRB_TOTAL_PLMN
Name Description
TotPrbDl_PLMN Ratio of resource used for PDSCH/PDCCH transmission against the total PLMN
downlink resource available.
TotPrbDlMin_PLMN Minimum value of PLMNTotPrbDLAvg
TotPrbDlMax_PLMN Maximum value of PLMNTotPrbDLAvg
TotPrbUl_PLMN Ratio of resource used for PUSCH reception against the total PLMN uplink
resource available.
TotPrbUlMin_PLMN Minimum value of PLMNTotPrbULAvg
TotPrbUlMax_PLMN Maximum value of PLMNTotPrbULAvg
PRB_SMART
Name Description
TotPrbCsRatio The ratio of PRB to which coordinated scheduling is applied
TotPrbJtRatio The ratio of PRB to which joint transmission is applied
TotPrbDLAllocRatio The total ratio of allocated PRB
TotPrbCs Total count of PRB to which coordinated scheduling is applied
TotPrbJt Total count of PRB to which joint transmission is applied
TotPrbDLAvail Total count of available PRB
TotPrbDLAlloc Total count of allocated PRB
TotPrbNormRatio The ratio of PRB to which normal (excluding CS/JT) scheduling is applied based
on the total available PRB
TotPrbCsAllocRatio The ratio of PRB to which coordinated scheduling is applied based on the
allocated PRB
TotPrbJtAllocRatio The ratio of PRB to which Joint transmission is applied based on the allocated
PRB
TotPrbNormAllocRatio The ratio of PRB to which normal (excluding CS/JT) scheduling is applied based
on the allocated PRB
TotPrbNorm Total count of PRB to which normal (excluding CS/JT) scheduling is applied
PRB_FULL_UTILIZATION
Name Description
Name Description
DLPrbFullUtilRatio The percentage of time during which all available PRBs for the downlink have
been assigned
ULPrbFullUtilRatio The percentage of time during which all available PRBs for the uplink have been
assigned
RADIO RESOURCE UTILIZATION

RRU_MEAS
Name Description
RruCceUsageDistDL1 Aggregation Level 1 of PDCCH DL grant
RruCceUsageDistUL1 Aggregation Level 1 of PDCCH UL grant
RruCceAllocationFailDLAvg Average CCE allocation failure rate of PDCCH DL grant
RruCceAllocationFailULAvg Average CCE allocation failure rate of PDCCH UL grant
RruPrbDLPcchAvg Average usage rate of PCCH PRB
RruPrbULSrbAvg Average PRB usage rate of Uplink SRB
RruPrbDLSrbAvg Average PRB usage rate of Downlink SRB
RRU_MEAS_NEW
Name Description
RruCceUsageDistDL1 Aggregation level1 of PDCCH DL grant
RruCceUsageDistUL1 Aggregation level1 of PDCCH UL grant
RruCceAllocationFailDLAvg The CCE allocation fail ratio of PDCCH DL grant
RruCceAllocationFailULAvg The CCE allocation fail ratio of PDCCH UL grant
RruPrbDLPcchAvg PCCH PRB Usage
RruPrbDLSrbAvg Downlink SRB (CCCH/DCCH) PRB Usage
RruPrbULSrbAvg Uplink SRB (CCCH/DCCH) PRB Usage
PDCCH
Name Description
Cfi1 The number of used CFI1
Name Description
PDCCHCceUsedAgg1 The number of used aggregation level 1 for allocating PDCCH CCE
PDCCHCcePerUser The average number of allocated CCE per UE
ACTIVE_UE
Name Description
UEActiveDl The number of UEs satisfying one or more of the following conditions in a
continuous 20 ms interval (sampling occasion) is summed every 80 ms for each
QCI.
If there is a DRB which receives a buffer occupancy request from the RLC
If there is a DRB which receives an HARQ retransmission request when a
collection interval ends, the average is calculated by dividing the summed
number of UEs by the number of sampling occasions that occurred.
UEActiveDlTot Sum of UEActiveDLAvg collected
UEActiveUl The number of UEs satisfying one or more of the following conditions in a
continuous 20 ms interval is summed every 80 ms for each QCI.
If there is a DRB where the uplink data requested to be allocated using the
Buffer Status Report message is waiting
If there is a DRB which receives an HARQ retransmission request when a
collection interval ends, the average is calculated by dividing the summed
number of UEs by the number of sampling occasions that occurred.
UEActiveUlTot Sum of UEActiveULAvg collected
SumActiveUEDL This counter is the cumulated number per every TTI of DL DRB for each QCI
which receives a buffer occupancy request from the RLC or which has received
a HARQ retransmission request during the sampling period.
SumActiveUEUL This counter is the cumulated number per every TTI of UL DRB for each QCI
where the uplink data requested to be allocated using the Buffer Status Report
message is waiting or which received an HARQ retransmission request.
RANDOM ACCESS PERFORMANCE

RA
Name Description
HighSpeedMonitoring The number of UEs which are monitored for moving speed
NoofHighSpeed The number of high speed UEs which are monitored
DedicatedPreambles The number of detected dedicated preambles.
DedicatedPreambleAssign The number of failures to get dedicated preamble allocation after requesting the
Fail dedicated preamble from the RRC to the MAC
Randomlyselectedpreambl The number of the preambles belonging to Group A among the detected
esLow contention based preambles
Randomlyselectedpreambl The number of the preambles belonging to Group B among the detected
esHigh contention based preambles
RACHUsageAvg Average number of detected preambles
UE_LIMIT_TA_INITIAL_ATTACH
Name Description
RARFailByTaLimitation The number of not-transmitted RARs due to TA Threshold in UE Initial Attach. If
taBasedUeLimitFlag is set as 1 and if the TA value assumed by BTS after
receiving preamble is larger than taThresholdForAttach, RAR is not transmitted
for the preamble.
Timing alignment statistics families (TA, TA_RRE, TA_NORMAL_RELEASE,

TA_ABNORMAL_RELEASE, TA_HO)
Timing Advance (TA) is a MAC Control Element (CE) that is used to control
uplink signal transmission timing. Timing advance is a negative offset, at UE,
between the start of a received downlink subframe and a transmitted uplink
subframe. Timing Advance offset compensates the propagation delay between
eNB and UE.
The following figure shows how propagation delay is compensated with TA
command. The UE adjusts the uplink transmission by 2 * so that eNB receives
the uplink data on the exact uplink subframe boundary. The eNB can either send
an absolute timing advance value or a relative timing adjustment value. Absolute
TA value is 11-bit in size and is sent only during random access procedure (in
random access response message). The relative timing adjustment is 6-bit in size
and can be sent any time when UE is connected, using Timing Advance MAC
control element. In case of random access response, the 11-bit timing advance
command NTA*16 is used. In other cases, a 6-bit timing advance command
indicates adjustment of the current NTAvalue, NTA,old to the new NTA value,
NTA,new where NTA,new = NTA,old + (A -31)16. Here, adjustment of NTA
value by a positive or a negative amount indicates advancing or delaying the
uplink transmission.
DL transmission subframe i at eNB

DL Reception subframe i at UE
UL transmission subframe i at UE
UL reception subframe i at eNB
TA
TA = (N TA +N TA offset).Ts seconds
Categorizing the TA distribution according to specific events provides information

about the distribution of distance from cell site where the events are occurring.
This statistical information can be used for network optimization and planning.
Samsung eNB provides a TA Distribution OM Family with 5 TA Distribution OM
Groups:
Call Attempt TA
Re-establishment TA
Normal Call Release TA
Abnormal Call Release TA
Handover TA
Though the OM group name indicates timing advance (TA), the distribution
counters are provided in terms of distance from cell site in meters. Each of these
OM groups provides PDF of UE distance with smaller granularity near cell center
and with progressively reduced granularity towards cell edge. Call Attempt TA,
Re-establishment TA, and Handover TA are calculated based on the absolute
timing advance value (11-bit) sent to UE as part of random access procedure. This
TA value is converted to distance in meters to provide the respective TA OM
groups. Abnormal Call Release TA and Normal Call Release TA OM groups are
calculated based on the final TA value. The eNB sends multiple relative timing
adjustment values (6-bit) to UE until the call is released normally or abnormally.
Also, it calculates the final TA value of UE by accumulating these relative TA
values onto the last absolute TA value sent to UE. This final TA value is then
converted to distance in meters to provide the respective TA OM groups.
Call Attempt TA (TA Family)

Call Attempt TA is pegged when eNB receives MSG3 successfully as part of RRC
connection establishment procedure. This TA OM Group pegs the timing advance
sent to UE in RAR MAC PDU in those cases where MSG3 is RRC Connection
Request message. The TA value sent to UE in this case is 11-bit absolute timing
advance value. Call attempt TA OM group is pegged irrespective of accessibility
success or failure after MSG3 reception at eNB. Call Attempt TA OM group is not
pegged in the following cases that involve RACH procedure:
Initial RACH procedure fails (for example, MSG3 time-out).
The UE performs RRC Connection Re-establishment to serving cell when a call is
ongoing, the Call Attempt TA OM does not get affected as it is already pegged
when MSG3 is received.
The UE performs RACH procedure after maximum re-transmission of Scheduling
Request (dsr-TransMax). In this case, Call Attempt TA is not affected as the
MSG3 received is not RRC Connection Request message (MSG3 in this scenario
will be CRNTI control element along with/without BSR).
The UE performs RACH procedure due to the reception of PDCCH order from
eNB. In this case also, call attempt TA is not affected, as the MSG3 received is not
RRC Connection Request message (MSG3 in this case will be CRNTI MAC
Control element).
Name Description
TimeAdvanceSection0 Distance (meter): 0~200, 16TS: from 0 to 2.
TimeAdvanceSection1 Distance (meter): 201~400, 16TS: from 3 to 5.

TimeAdvanceSection20 Distance (meter): 10001~, 16TS: from 127 to 1282.
Re-establishment TA (TA_RRE family)

Connection Re-establishment TA is pegged when eNB receives MSG3
successfully as part of RRC connection Re-establishment procedure. This TA OM
group pegs the timing advance sent to UE in RAR MAC PDU in those cases where
MSG3 is RRC Connection Re-establishment Request message. The TA value sent
to UE in this case is 11-bit absolute timing advance value. Connection Re-
establishment TA OM group is pegged when eNB receives RRC Connection Re-
establishment Request message, irrespective of whether the re-establishment
attempt is rejected (RRC Connection Re-establishment Reject) or accepted (RRC
Connection Re-establishment). During handover procedure, target eNB may
receive RRC Connection Re-establishment Request as MSG3 (UE performs re-
establishment procedure in case of HO failure). In this case, Connection Re-
establishment TA is pegged at the target eNB.
Name Description
RRE_TimeAdvanceSection0 Distance (meter): 0~200, 16TS: from 0 to 2.
RRE_TimeAdvanceSection1 Distance (meter): 201~400, 16TS: from 3 to 5.

RRE_TimeAdvanceSection20 Distance (meter): 10001~, 16TS: from 127 to 1282.
Normal Call Release TA (TA_NORMAL_RELEASE Family)

Normal Call Release TA is pegged when a call is released normally, that is, with
any cause that is not related to accessibility failures and call drops. The cases
include normal releases such as user inactivity-triggered release, MME-triggered
releases, call release due to CSFB, call release due to inter-RAT re-direction, call
release in source eNB after successful handover, and so on. Normal call release
TA is pegged after accumulating all relative TA values sent to UE after the last
absolute TA value transmission. This accumulated TA value is converted to
distance from cell site and is used to update the OM counter. This calculated
distance will indicate the distance at which the call is released.
Name Description
NormalRelease_TimeAdvanceSection0 Distance (meter): 0~200, 16TS: from 0 to 2.
NormalRelease_TimeAdvanceSection1 Distance (meter): 201~400, 16TS: from 3 to 5.

NormalRelease_TimeAdvanceSection20 Distance (meter): 10001~, 16TS: from 127 to 1282.
Abnormal Call Release TA (TA_ABNORMAL_RELEASE Family)

Abnormal Call Release TA is pegged when call is released with one of the cause
that is not pegged under Normal Call Release TA, that is, all abnormal call release
cases. The cases include call drops, accessibility failures, and other abnormal cases.
This OM group provides information about the cell site distance where abnormal
call releases are happening. Higher abnormal call releases at a specific cell site
distance might call for network optimizations, drive tests and so on. Abnormal
Call Release TA is pegged after accumulating all relative TA values sent to UE
after the last absolute TA value transmission. This accumulated TA value is
converted to distance from cell site and is used to update the OM counter. Below is
the list of cause values for which Abnormal Call Release TA is pegged:
Call Drop cases

CallDrop_* counters in CALL_DROP (24) counter family where * denotes a
drop cause.
Failure Causes in RRC Connection Establishment OM group: ConnEstabFail_*
counters in RRC_ESTAB counter family where * denotes a failure cause.
Failure Causes in E-RAB Setup OM group: ErabInitFailNbr_* counters in
ERAB_ESTAB counter family where * denotes a failure cause.
Failure Causes in UE-associated logical S1 Connection Establishment OM group:
S1ConnEstabFail_* counters in S1SIG counter family where * denotes a
failure cause.
In case of more information about CALL_DROP, RRC_ESTAB, ERAB_ESTAB,
and S1SIG counter families, refer to LTE system counter description manual.
Name Description
AbnormalRelease_TimeAdvanceSection0 Distance (meter): 0~200, 16TS: from 0 to 2.
AbnormalRelease_TimeAdvanceSection1 Distance (meter): 201~400, 16TS: from 3 to 5.

AbnormalRelease_TimeAdvanceSection20 Distance (meter): 10001~, 16TS: from 127 to 1282.
Handover TA (TA_HO family)

Handover TA is pegged when MSG3 is received successfully as part of handover
procedure in target cell. In handover scenarios, the MSG3 received at target eNB
can either be RRC Connection Reconfiguration Complete message or RRC
Connection Re-establishment message. In both of these cases, handover is
considered as success if UE gets connected to the target cell successfully. But
Handover TA is pegged only when eNB receives RRC Connection
Reconfiguration Complete message as the MSG3. In case, RRC Connection Re-
establishment Request is received as MSG3 during handover, the TA value is
pegged as Connection Re-establishment TA and not Handover TA. Random access
procedure in case of handover can either be contention based or contention free
and in both cases, the TA will be pegged in Handover TA OM group, if the MSG3
received is RRC Connection Reconfiguration Complete message.
Name Description
Name Description
HOTimeAdvanceSection0 The cumulated count of the case that TA of RACH success UE in handover
is between 0 and 2.
is between 3 and 5.

is between 127 and 1282.
Carrier Aggregation
In case of carrier aggregation, as uplink CA is not supported, timing advance value
for the PCell is pegged for all of the TA OM groups defined above.
HYBRID ARQ PERFORMANCE
TRANSMISSION
Name Description
DlResidualBLER_Retrans0 PDSCH BLER for the initial HARQ transmission.
DlResidualBLER_Retrans1 PDSCH BLER for the first HARQ retransmission.
DlResidualBLER_Retrans2 PDSCH BLER for the second HARQ retransmission.
DlResidualBLER_Retrans3 PDSCH BLER for the third HARQ retransmission.
DlTransmission_Retrans0 Number of initial PDSCH HARQ transmissions
DlTransmission_Retrans1 Number of first PDSCH HARQ retransmissions
DlTransmission_Retrans2 Number of second PDSCH HARQ retransmissions
DlTransmission_Retrans3 Number of third PDSCH HARQ retransmissions
DlTransmission_Nacked_Retran Number of third PDSCH HARQ retransmission failures
s3
UlResidualBLER_Retrans0 PUSCH BLER for the initial HARQ retransmission.
UlResidualBLER_Retrans1 PUSCH BLER for the first HARQ retransmission.

UlResidualBLER_Retrans26 PUSCH BLER for the twenty sixth HARQ retransmission.
UlResidualBLER_Retrans27 PUSCH BLER for the twenty seventh HARQ retransmission.
UlTransmission_Retrans0 Number of initial PUSCH HARQ transmissions
UlTransmission_Retrans1 Number of first PUSCH HARQ retransmissions
UlTransmission_Retrans2 Number of second PUSCH HARQ retransmissions

UlTransmission_Retrans26 Number of twenty sixth PUSCH HARQ retransmissions
UlTransmission_Retrans27 Number of twenty seventh PUSCH HARQ retransmissions
UlTransmission_Nacked_Retran Number of twenty seventh PUSCH HARQ retransmissions
s27
DlResidualBLER_RetransAvg Average of distribution for DLResidualBLERRetrans.
UlResidualBLER_RetransAvg Average of distribution for ULResidualBLERRetrans.
DlResidualBLER_RetransNak PDSCH BLER for HARQ NACK.
UlResidualBLER_RetransNak PUSCH BLER for HARQ NACK.
DlResidualBLER_RetransMin Minimum value of DLResidualBlerRetrans
Name Description
DlResidualBLER_RetransMax Maximum value of DLResidualBlerRetrans
UlResidualBLER_RetransMin Minimum value of ULResidualBlerRetrans
UlResidualBLER_RetransMax Maximum value of ULResidualBlerRetrans
MIMO
Name Description
PdschBLERperLayer PDSCH BLER for each layer
PuschBLERperLayer PUSCH BLER for each layer
MIMO_NEW
Name Description
PdschTransmissionPerLayer Transmission count per layer for PDSCH
PdschErrorPerLayer PDSCH error count for each layer
PuschTransmissionPerLayer Transmission count per layer for PUSCH
PuschErrorPerLayer PUSCH error count for each layer
MCS
Name Description
PdschBLERperMCS0 PDSCH BLER transmitted to MCS 0

PuschBLERperMCS0 PUSCH BLER received from MCS 0

UlReceivedMCS0 The number of times PUSCH of MCS 0 is received

DlSchedulerMCS0 The number of PRBs assigned to PDSCH MCS 0

UlSchedulerMCS0 The number of PRBs assigned to PUSCH MCS 0
Name Description

DL_ACK_NACK_DTX_RATIO
Name Description
DlreceivedAckNackDtxRatio ACK, NACK, DTX ratio
ADAPTIVE MODULATION AND CODING PERFORMANCE

DL_MCS
Name Description
DlTransmittedMCS0 The number of times that MCS 0 PDSCH is transmitted per layer/ codeword
DlTransmittedMCS1 The number of times that MCS 1 PDSCH is transmitted per layer/ codeword

DlTransmittedMCS30 The number of times that MCS 30 PDSCH is transmitted per layer/
codeword
DlTransmittedMCS31 The number of times that MCS 31 PDSCH is transmitted per layer/
codeword
DL_LAYER
Name Description
DlTransmittedLayer Transmission counts per layer for PDSCH
DL_CQI
Name Description
DLReceivedCQI0 The number of times that CQI 0 is received per layer/codeword
Name Description
DLReceivedCQIMin Minimum value of DLReceivedCQI
DLReceivedCQIMax Maximum value of DLReceivedCQI
DLReceivedCQIAvg Average value of DLReceivedCQI
DL_CQI_NEW
Name Description
DlReceivedCQIAvg Average value of DL received CQI
DlReceivedCQI0 The number of times that CQI 0 is received per layer/codeword

DlReceivedCQIMin Minimum value of DLReceivedCQI
DlReceivedCQIMax Maximum value of DLReceivedCQI
CQIErase Number of times layer/codeword CQI is erased
DL_CQI_NEW_PCELL
Name Description
DLReceivedCQI0 Number of receiving CQI 0 for a wideband CQI per layer/codeword
transmitted from CA UE whose the cell is PCell

DLReceivedCQIMin The minimum value of DlReceivedCQI received from CA UE whose cell is
PCell
DLReceivedCQIMax The maximum value of DlReceivedCQI received from CA UE whose cell is
PCell
DLReceivedCQIAvg The average value of DlReceivedCQI received from CA UE whose cell is
PCell
CQIErase Number of times that CQI erase per layer/codeword is received from CA UE
whose cell is PCell
DL_CQI_NEW_SCELL
Name Description
Name Description

DLReceivedCQIMin The minimum value of DlReceivedCQI transmitted from CA UE whose the cell
is SCell
DLReceivedCQIMax The maximum value of DlReceivedCQI transmitted from CA UE whose the
cell is SCell
DLReceivedCQIAvg The average value of DlReceivedCQI transmitted from CA UE whose the cell
is SCell
CQIErase Number of times that CQI erase per layer/codeword is received from CA UE
whose cell is SCell
DL_SUBBAND_CQI
Name Description
DLReceivedSubband0CQI0 The number of times that CQI 0 of subband0 is received

DLReceivedSubband0CQIMi The minimum value of DLReceivedCQI in the subband0
n
DLReceivedSubband0CQIMa The maximum value of DLReceivedCQI in the subband0
x
DLReceivedSubband0CQIAv The average value of DLReceivedCQI in the subband0
g
Subband0CQIErase The number of times that CQI erase of subband0 is received

DLReceivedSubband1CQIMi The minimum value of DLReceivedCQI in the subband1
n
DLReceivedSubband1CQIMa The maximum value of DLReceivedCQI in the subband1
x
DLReceivedSubband1CQIAv The average value of DLReceivedCQI in the subband1
g


Name Description
4
5
DLReceivedSubband11CQIM The minimum value of DLReceivedCQI in the subband11
in
DLReceivedSubband11CQIM The maximum value of DLReceivedCQI in the subband11
ax
DLReceivedSubband11CQIA The average value of DLReceivedCQI in the subband11
vg

4
5
DLReceivedSubband12CQIM The minimum value of DLReceivedCQI in the subband12
in
DLReceivedSubband12CQIM The maximum value of DLReceivedCQI in the subband12
ax
DLReceivedSubband12CQIA The average value of DLReceivedCQI in the subband12
vg
DL_PMI
Name Description
DlReceivedPMI0 The number of times that PMI 0 is received

DL_RI
Name Description
DlReceivedRIAvg Average value of DL received RI
DlReceivedRI0 Reserved
DlReceivedRI1 The number of times that RI 1 is received
CARRIER AGGREGATION PERFORMANCE

CA_ACT_DEACT
Name Description
SCellActivation Count of activations (SCell)
SCellDeactivation_TO Count of SCell deactivation occurrences by reason: When deactivation timer
expires (SCell)
SCellDeactivation_Mismatch Count of SCell deactivation occurrence by reason: When CA status of eNB and
that of the UE are different (SCell)
CRNTIcollision The number of Scell Activation fail due to C-RNTI collision (The C-RNTI of UE,
who requests Scell activation to SCell, is already used in SCell)
SCellActUEAvg The average number of Scell activated Ues
CA_ACT_INFO
Name Description
SCellActUEAvg The average number of Scell activated UEs
SCellActivatedTime The total time of Scell activated time
EICIC PERFORMANCE
EICIC_ABS
Name Description
AvgABSNum Average ABS number
ABSBin0 The ratio of not using ABS pattern
ABSBin5 The using ratio of ABS pattern used 5/40 as ABS ratio

E-RAB SESSION TIME

ERAB_SESSION_UE
Name Description
SessionTimeUEAvg Average in-session time per UE
SessionTimeUETot Sum of SessionTimeUEAvg collected
ERAB_SESSION_QCI
Name Description
SessionTimeQciAvg Average in-session time per QCI
SessionTimeQciTot Sum of SessionTime SessionTimeQciAvg collected
RECEIVED SIGNAL POWER STATISTICS

POWER
Name Description
InterferencePower Average interference over thermal noise for each PRB
ThermalNoisePower Average Thermal Noise
RssiOverPath Average RSSI for each antenna
RssiPath0 Average RSSI of Antenna #0
RssiPath1 Collected RssiPath0Avg count
RNTP
Name Description
RntpOwnCell_PRB0 RNTP of downlink PRB #0

RU_RSSI
Name Description
RuRssiAvg The average values of RSSI
RuRssiMax The maximum values of RSSI
RuRssiCurr The most recently collected RSSI values
RuRssiTot The total sum of the RSSI values
RuRssiCnt Number of times that the RSSI values were collected
IIU_RSSI
Name Description
IiuRssiAvg The average values of RSSI
IiuRssiMax The maximum values of RSSI
IiuRssiCurr The most recently collected RSSI values
IiuRssiTot The total sum of the RSSI values
IiuRssiCnt Number of times that the RSSI values were collected
RRH_RSSI
Name Description
RrhRssiAvg The average values of RSSI for each RRH path
RrhRssiMax The maximum values of RSSI for each RRH path
RrhRssiCurr The most recently collected RSSI values for each RRH path
RrhRssiTot The total sum of the RSSI linear values for each RRH path
RrhRssiCnt Number of times that the RSSI values were collected for each RRH path
Name Description
RrhRssidBmAvg The average values of RSSI dBm for each RRH path
RrhRssidBmTot The total sum of the RSSI dBm values for each RRH path
RrhRssidBmCnt Number of times that the RSSI dBm values were collected for each RRH path
RSSI_PATH
Name Description
RssiPathAvg The average value of RSSI for each path
RssiPathMax The maximum value of RSSI for each path
RssiPathCurr The most recently collected RSSI values for each path
RssiPathTot Sum of RSSI values for each path
RssiPathCnt RSSI values collection count for each path
IOT
Name Description
IotAvg IoT Average
IotMin IoT Min
IotMax IoT Max
UL_SINR_DISTRIBUTION
Name Description
SinrDistULWbPreComp_Bin0 Uplink SINR Bin0 (-10~-8 dB) count before Outer-loop compensation
SinrDistULWbPreComp_Bin1 Uplink SINR Bin1 (-8~-6 dB) count before Outer-loop compensation

SinrDistULWbPreComp_Bin18 Uplink SINR Bin18 (26~28) count before Outer-loop compensation
SinrDistULWbPreComp_Bin19 Uplink SINR Bin19 (28~30) count before Outer-loop compensation
SinrDistULWbPostComp_Bin0 Uplink SINR Bin0 (-10~-8 dB) count after Outer-loop compensation
SinrDistULWbPostComp_Bin1 Uplink SINR Bin1 (-8~-6 dB) count after Outer-loop compensation

SinrDistULWbPostComp_Bin1 Uplink SINR Bin18 (26~28 dB) count after Outer-loop compensation
8
SinrDistULWbPostComp_Bin1 Uplink SINR Bin19 (28~30 dB) count after Outer-loop compensation
9
PUCCH_SINR_DISTRIBUTION
Name Description
PUCCHSinrDistBin0 The cumulated number of PUCCH SINR Bin0 (-10~-8 dB).
PUCCHSinrDistBin1 The cumulated number of PUCCH SINR Bin1 (-8~-6 dB).

PUCCHSinrDistBin19 The cumulated number of PUCCH SINR Bin19 (28~30 dB).
PUSCH_TX_POWER
Name Description
PhrRxCount This counter is cumulated by 1 when PHR is received.
TxPowerSum This counter is cumulated by the PUSCH Tx Power when PHR is received.
PowerLimitCount This counter is cumulated by 1 if (PHR index - 23) is less than 0 when PHR is
received.
AveragePuschTxPower Average PUSCH transmission power
PowerShortageRatio Percentage of received PHRs with PHR index - 23 < 0.
TRANSMITTED SIGNAL POWER STATISTICS

RRH_TX_POWER
Name Description
RrhTxPowerAvg The average value of RRH TX Power
RrhTxPowerMax The Maximum value of RRH TX Power
RrhTxPowerCurr The most recently collected RRH TX Power
RrhTxPowerTot The total sum of the RRH TX Power values
RrhTxPowerCnt Number of times that the RSSI values were collected for each RRH TX Power
UE_TX_POWER
Name Description
PuschRbCountAvg Number of average uplink RBs except PUCCH RB
PuschRbCountTot Number of accumulated uplink RBs except PUCCH RB
PuschRbCountCnt Count of PuschRbCountAvg called
UETxPowerPrbAvg Average UE TX Power on RB
UETxPowerPrbTot Accumulated UE TX Power on RB
UETxPowerPrbCnt Count of UETxPowerPrbAvg called
AllocCount Number of RBs allocated for PUSCH
RRH_UE
Name Description
RrhUE The number of UEs per RRH
Count when UE operates PRACH process. Count when RRH receives MSG3
In the same RRH, when UE operates PRACH process, duplicate count may
occur.
During measurement period, when UE does not operate PRACH process, the
corresponding UE is not counted for this counter. (Specifically, when UE
moves between main cell and copy cell and, it does not operate PRACH
process, the corresponding UE is not counted for this counter)
RF
Name Description
RuGain RU Gain
RuGainCnt a number of collection of RuGain
Name Description
TxRfPower Tx RF Power
TxRfPowerCnt a number of collection of TxRfPower
OverpowerAlarmThr Overpower alarm threshold
OverpowerAlarmThrCnt a number of collection of OverpowerAlarmThr
LowpowerAlarmThr Lowpower alarm threshold
LowpowerAlarmThrCnt a number of collection of LowpowerAlarmThr
RfTemp RF Temperature
RfTempCnt a number of collection of RfTemp
TX_DIGITAL_IQ
Name Description
TxDigitalIq Tx Digital I/Q
TxDigitalIqCnt a number of collection of TxDigitalIq
SMART_SON_TX_POWER
Name Description
SmartSon_TxPowerAvg The Average value of Tx Power
SmartSon_TxPowerMax The Maximum value of Tx Power
SmartSon_TxPowerMin The Minimum value of Tx Power
SmartSon_TxPowerTot The total sum of Tx Power
SmartSon_TxPowerCnt Number of times that the TxPower values were collected
SYSTEM OPERATION
How to Activate
This feature is basically enabled. The statistical data are collected during eNB
operation and transmitted to LSM.
Key Parameters
There are no related parameters
Counters and KPIs

For detailed information about all available counters, refer to Samsung LTE
system counter description manual.
REFERENCE
[1] LTE eNB System Counter Description_SLR4.5.0.
[2] 3GPP TS 32.450: Key performance indicators: Definitions.
[3] 3GPP TS 32.425: Performance measurements.

[4] 3GPP TS 32.404: Performance measurements: Definitions and templates.
Samsung eNB (LTE)
Feature Description for PKG 5.0.0
Document Version 2.0
2015 Samsung Electronics Co., Ltd.

All rights reserved.

eNodeB Feature-Description PACKAGE 4.0 PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

eNodeB Feature-Description PACKAGE 4.0 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Samsung eNB (LTE)

Document Version 2.0

Document Number: 2600-00I10TGAP

LTE-SW1301, Idle Mobility to GERAN .......................................................................................... 217

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 iv

LTE-OM9002, Subscriber and Equipment Trace........................................................................... 536

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 v

This document provides detailed descriptions of new/enhanced features in the

Some features, commands, parameters, or counters are not supported by all

Conventions in this Document

Provides information or instructions that you should follow to avoid service

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 vi

File Names and Paths

User Input and Console Screen Output Text

New and Changed Information

Development Type Feature ID, Name

Development Type Feature ID, Name

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 ix

Organization of This Document

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 x

LTE-ME2019, DL SU 2x2 MIMO (TM3 and TM4)

DEPENDENCY AND LIMITATION

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 2

Number of Number CW, Layer mapping

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 3

Counters and KPIs

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 4

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 5

DEPENDENCY AND LIMITATION

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 6

oEstimate the covariance matrix of interference and noise

3 Interference rejection is achieved by MMSE combining at the eNB receiver.

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 7

Default IRC_ENABLE is 'FALSE (IRC OFF) (IRC_ENABLE= 0)'.

Counters and KPIs

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 8

LTE-ME2022, DL SU 4x4 MIMO (TM3 and TM4)

DEPENDENCY AND LIMITATION

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 9

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 10

Number of Number CW, Layer mapping

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 11

Number of Number CW, Layer mapping

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 12

Counters and KPIs

[5] 3GPP TS 36.214 Evolved Universal Terrestrial Radio Access (E-UTRA);

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 14

LTE-ME2023, DL SU 4x2 MIMO (TM3 and TM4)

DEPENDENCY AND LIMITATION

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 15

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 16

Number of Number CW, Layer mapping

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 17

Counters and KPIs

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 18

[5] 3GPP TS 36.214 Evolved Universal Terrestrial Radio Access (E-UTRA);

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 19

LTE-ME5110, FDD Carrier Aggregation (5+5)

DEPENDENCY AND LIMITATION

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 20

Samsung eNB (LTE) Feature Description for PKG 5.0.0 v2.0 21

LTE-ME5111, FDD Carrier Aggregation (3+5)

DEPENDENCY AND LIMITATION