LTE Optimization Guideline

819 LTE Optimization
Engineering Guideline
COPYRIGHT
This manual is proprietary to SAMSUNG Electronics Co., Ltd. and is protected by

copyright.
No information contained herein may be copied, translated, transcribed or duplicated for

any commercial purposes or disclosed to the third party in any form without the prior
written consent of SAMSUNG Electronics Co., Ltd.
TRADEMARKS
Product names mentioned i this manual may be trademarks and/or registered trademarks of
their respective companies.
This manual should be read and used as a guideline for properly installing and operating the product.
This manual may be changed for the system improvement, standardization and other technical reasons
without prior notice.
Updated manuals are available at:
https://systems.samsungwireless.com/
For questions on the manuals or their content, contact

NetSysTechWriter@sta.samsung.com
©2012 SAMSUNG Electronics Co., Ltd. All rights reserved

819 LTE Optimization Engineering Guideline
INTRODUCTION
Purpose
This manual describes LTE Optimization process flow, practices and call release cause.
Document Content and Organization
This manual contains the following:
CHAPTER 1. LTE Optimization Process Flow
This chapter describes the site, cluster and market level optimizations.
CHAPTER 2. LTE Optimization Practices
This chapter describes the coverage improvement, interference control, LTE handover
optimization, EUTRAN/CDMA2000 Handover, RAN parameters, eNodeB control
parameters and parameter reference guide.
CHAPTER 3. Call Release Cause
This chapter describes the call release cause.
CHAPTER 4. References
This chapter includes reference documents.
2012 © SAMSUNG Electronics Co., Ltd. i

Revision History
Version DATE OF ISSUE REMARKS Author
1.0 11. 2012. First Edition Abhishek Warhadkar

1.1 12.2012 Added section 2.8, Updated Abhishek Warhadkar
Chapter 4 References
© SAMSUNG Electronics Co., Ltd. ii

TABLE OF CONTENTS
Revision History .......................................................................................................................................ii
CHAPTER 1. LTE Optimization Process Flow 2-1
1.1 Site Level Optimization ......................................................................................................... 2-1
1.2 Cluster Level Optimization+.................................................................................................. 2-2
1.3 Market level Optimization...................................................................................................... 2-5
CHAPTER 2. LTE Optimization Practices 2-1
2.1 Coverage Improvement ......................................................................................................... 2-1
2.1.1 Techniques to improve coverage ............................................................................................ 2-1
2.2 Interference Control............................................................................................................... 2-4
2.3 LTE Handover Optimization .................................................................................................. 2-9
2.3.1 Active mode handover ............................................................................................................. 2-9

2.3.2 Idle Mode Handover ..............................................................................................................2-14
2.4 EUTRAN and CDMA2000 Handover ................................................................................... 2-16
2.5 RAN Parameters .................................................................................................................. 2-21
2.5.1 Physical Cell Identity ..............................................................................................................2-21

2.5.2 Root Sequence Index (RSI) ..................................................................................................2-22
2.6 e-NodeB - Control Parameters ............................................................................................ 2-23
2.7 Parameter Reference Guide ................................................................................................ 2-23
2.8 Relevant Documents and Processes ................................................................................. 2-23
CHAPTER 3. Call Release Cause 3-24
CHAPTER 4. References 4-1
© SAMSUNG Electronics Co., Ltd. iii

LIST OF FIGURES
Figure 1: Site level testing process flow .................................................................................... 2-2

Figure 2: Cluster Drive testing scenario ..................................................................................... 2-3
Figure 3: LTE Cluster Optimization Process Flow ..................................................................... 2-3
Figure 4: LTE Optimization Practices......................................................................................... 2-4
Figure 5: Indicators of DL Interference ...................................................................................... 2-5
Figure 6: Example of an overshooting sector ............................................................................ 2-6
Figure 7: Improvement in SINR as a result of down-tilt ............................................................. 2-7
Figure 8: X2 based Active handover call flow .......................................................................... 2-10
Figure 9: A3 Event description ................................................................................................. 2-11
Figure 10: Example of Handover optimization ......................................................................... 2-15
Figure 11: Operational procedure for Neighbor Relation Optimization .................................... 2-15
Figure 12: Example of optimum PSS planning ........................................................................ 2-21
© SAMSUNG Electronics Co., Ltd. iv

CHAPTER 1. LTE Optimization

Process Flow
LTE performance optimization activities can be divided into three different levels:
1. Site level
2. Cluster level
3. Market level
1.1 Site Level Optimization

Single sites are the basic building blocks of wireless networks. Contiguous sites form clusters and
clusters constitute markets. Therefore optimization of a network begins with individual sites. Site
level testing is a critical step in the process to ensure each site is meeting all the key performance
indicator (KPI) targets. This type of testing can also be referred to as site level drive testing, site
level shakedown or site level acceptance testing. It can begin as soon as a site is on-air and
functional. Scope for site level testing can vary from basic to a detailed. Most operators and OEMs
perform the following basic tests as a part of site level testing:
A. Peak uplink and downlink throughput test
B. Intra-eNB handovers
C. Inter-eNB handover to immediate first tier neighbors
D. Radio latency test
E. Call success test
Additionally, sector level parameters and data fill are also verified during the course of this activity.
Examples are listed below:
1. Commissioning tests: These tests certify there are no discrepancies in configured
parameters such as Transmit power, Diversity paths etc.
2. Sweep tests: VSWR and uplink noise tests guarantee that sites do not have any anomalies
in coax, fiber and antenna installation. Uplink noise test also eliminate possibility of
external interference.
3. RF parameters: Site and sector level parameters such as PCID, RACH, sector orientation
or azimuth are also verified.
© SAMSUNG Electronics Co., Ltd. 2-1

4. Alarm testing
Figure 1: Site level testing process flow
1.2 Cluster Level Optimization+

Cluster level performance testing or optimization activity is the next key factor in network
optimization. A cluster is a group of several on-air contiguous sites. Contiguous coverage between
sites of a cluster is a critical factor in ensuring seamless mobility. Site level testing as described in
the previous section is usually considered a prerequisite for cluster level testing. Once a cluster is
formed, a baseline drive test is conducted to capture the pre-optimization performance of the cluster.
A cluster drive route must be carefully designed to cover each sector of all sites so that major roads,
thruways, points of interest and demographics important to operators are covered. The drive data is
then analyzed and studied for potential optimization changes to improve user experience.
Suggested changes are implemented and a re-drive is conducted to recapture the performance
improvement. All changes made during the optimization phase must be documented for future
reference. Cluster optimization becomes challenging when there are common elements such as a
shared antenna between two technologies. A balance or trade-off must be considered while
optimizing such networks as improving one network may negatively impact the other underlay or
overlay network.

Iperf/FTP
servers
EPC
eNB monitoring
tool
Test
UEs Iperf/ftp
`
clients
eNB Inter eNB eNB

Pre-determined route ` `
HO point
Intra eNB `
HO point Intra eNB

HO point Intra eNB
HO point Test equipment
in vehicle
Figure 2: Cluster Drive testing scenario
Figure 3: LTE Cluster Optimization Process Flow

Examples of major KPIs included in cluster level optimization testing are as follows:
1. Connection/call success rate
2. Connection/call drop rate
3. Average uplink throughput
4. Average downlink throughput
5. Average Radio latency
6. Handover success rate and Handover latency
The objective of cluster level testing is to meet or exceed all KPI targets. In situations where one or
more KPIs are not met, possible recommendations should be evaluated: addition of new sites or
sector, antenna replacement, addition of capacity carriers etc. are put forth to achieve required
performance. Figure 1D explains basic LTE optimization practices.
Figure 4: LTE Optimization Practices
LTE standard has a large number of configurable parameters which can affect the performance
aspect of the network. To maintain consistency, several of these parameters must be set to a global
default value. Global default value also referred to as „Golden Parameters‟ must be discussed and
consulted between the OEM and Operator so that an optimized value can be determined based on
laboratory testing, simulating techniques and real world subscriber scenarios.
RF design simulations can also assist in finalizing the physical changes intended coverage
improvement or interference control. Cell planning or design tools can predict the effect of physical

changes which can be useful in evaluating the impact before implementation. Costly measures such
as physical changes, antenna azimuth or radiation center changes must be carefully assessed to
minimize customer impact and service degradation below set target. Overlapping coverage between
sites is crucial to accomplish optimal handover performance.
Neighbor list implementation ensures successful handover between contiguous sites and sectors.
An initial neighbor list plan can be generated using RF design tools or any other similar tool
capable of designing neighbor plans. Maintaining updated neighbor lists for every site is
recommended to facilitate successful handovers in an evolving network. Neighbor lists from
underlying technology, if available, can be useful first-hand information.
LTE parameters like Physical cell identity (PCI), Root sequence index, Traffic area codes, Traffic
area lists etc. must be planned prior to the commencement of optimization activity. These
parameters can be tweaked during the optimization phase.
The addition of new sites or sectors to the network is considered when existing sites cannot provide
sufficient coverage in terms of reliability and sustainability. Optimization engineers should propose
such ideas to the RF design group to consider during cell planning exercise and network expansion.
1.3 Market level Optimization

For an evolving network, optimization can be a routine activity. Deployment of new macro sites,
small cells, in-building solutions are always considered to meet the high demand of capacity and
bandwidth. Regular network tweaks and optimization efforts are always needed when new network
elements are integrated to serve increased demands and improvement of user experience.
Market level optimization can be considered a final step in accomplishing a high performing LTE
network. This activity is similar to cluster level activity where multiple optimized clusters are
evaluated and analyzed to ensure proper networking and mobility between them.

CHAPTER 2. LTE Optimization

Practices
2.1 Coverage Improvement

Cell site planning is an important factor in network design process. Antenna selection, antenna
radiation center, antenna tilt (mechanical or electrical) and antenna azimuth governs the coverage
of any given cell site. Lack of coverage also referred to as lack of dominant server or coverage hole
happens when any given geographic region does not have enough RF coverage to serve both fixed
and mobile subscribers. Strength of Reference signal is used in determining the coverage holes.
In LTE terms (as defined in TS 36.214), Reference signal received power is defined as:
Reference signal received power (RSRP), is defined as the linear average over the power
contributions (in [W]) of the resource elements that carry cell-specific reference signals within the
considered measurement frequency bandwidth.
For RSRP determination the cell-specific reference signals R0 according TS 36.211 [3] shall be
used. If the UE can reliably detect that R1 is available it may use R1 in addition to R0 to determine
RSRP.
The reference point for the RSRP shall be the antenna connector of the UE.
If receiver diversity is in use by the UE, the reported value shall not be lower than the
corresponding RSRP of any of the individual diversity branches
2.1.1 Techniques to improve coverage

1. Antenna orientation and tilt – Pointing the antenna in direction of interest and adjusting the
tilt (mechanical or electrical) is the most common practice to control coverage. Availability
of the remote electrical tilt (RET) feature has made this task more convenient by not
requiring tower climb or visits to the cell site location. Electrical tilt change should also be
evaluated using proper design tools to estimate the effect before implementation. Minimum

to no harm should be maintained while implementing change in tilt or azimuth. In other

words, while adjusting tilt and azimuth, one must make sure that the suggested change will
not adversely affect existing coverage and served subscribers.
2. Antenna diversity – Adding diversity in uplink is another practice to improve uplink cell
coverage. Uplink diversity improves the „receive sensitivity‟ of eNB resulting in better
uplink coverage.
3. Cell selection threshold QRxLevMin – This parameter specifies the minimum required Rx
level in the cell in dBm. Cell selection process and cell selection criteria as per 3GPP
standard 36.304 are:
Cell Selection process

Description
The UE shall use one of the following two cell selection procedures:
a) Initial Cell Selection
This procedure requires no prior knowledge of which RF channels are E-UTRA carriers. The UE
shall scan all RF channels in the E-UTRA bands according to its capabilities to find a suitable cell.
On each carrier frequency, the UE need only search for the strongest cell. Once a suitable cell is
found this cell shall be selected.
b) Stored Information Cell Selection
This procedure requires stored information of carrier frequencies and optionally also information
on cell parameters, from previously received measurement control information elements or from
previously detected cells. Once the UE has found a suitable cell the UE shall select it. If no suitable
cell is found the Initial Cell Selection procedure shall be started.
NOTE: Priorities between different RAT or frequencies provided to the UE by system information
or dedicated signaling are not used in the cell selection process.
Cell Selection Criteria

The cell selection criterion S is fulfilled when:
Srxlev > 0
Where:
Srxlev = Qrxlevmeas – (Qrxlevmin – Qrxlevminoffset) - Pcompensation
Where:
The signaled value QrxlevminOffset is only applied when a cell is evaluated for cell selection as a
result of a periodic search for a higher priority PLMN while camped normally in a VPLMN [5].
During this periodic search for higher priority PLMN the UE may check the S criteria of a cell

using parameter values stored from a different cell of this higher priority PLMN.
Srxlev Cell Selection RX level value (dB)
Qrxlevmeas Measured cell RX level value (RSRP).
Qrxlevmin Minimum required RX level in the cell (dBm)
Qrxlevminoffset Offset to the signalled Qrxlevmin 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 [5]
Pcompensation [FFS]
Cell reselection parameters in system information broadcasts

Cell reselection parameters are broadcast in system information and are read from the serving cell
as follows:
Qoffsets,n This specifies the offset between the two cells.

Qoffsetfrequency Frequency specific offset for equal priority E-UTRAN frequencies.
Qhyst This specifies the hysteresis value for ranking criteria.
Qrxlevmin This specifies the minimum required Rx level in the cell in dBm.
TreselectionRAT This specifies the cell reselection timer value. For each target RAT a
specific value for the cell reselection timer isdefined, which is
applicable when evaluating reselection within E-UTRAN or towards
other RAT (i.e. TreselectionRATfor E-UTRAN is
TreselectionEUTRAN, for UTRAN TreselectionUTRAN for GERAN
TreselectionGERAN, forTreselectionCDMA_HRPD, and for
TreselectionCDMA_1xRTT).Note: TreselectionRAT is not sent on
system information, but used in reselection rules by the UE for each
RAT.
TreselectionEUTRAN This specifies the cell reselection timer value TreselectionRAT for E-
UTRAN
TreselectionUTRAN This specifies the cell reselection timer value TreselectionRAT for
UTRAN
TreselectionGERAN This specifies the cell reselection timer value TreselectionRAT for
GERAN
TreselectionCDMA_HRPD This specifies the cell reselection timer value TreselectionRAT for
CDMA HRPD
TreselectionCDMA_1xRTT This specifies the cell reselection timer value TreselectionRAT for
CDMA 1xRTT
Threshx, high This specifies the threshold used by the UE when reselecting towards
the higher priority frequency X than currentlyserving frequency. Each
frequency of E-UTRAN and UTRAN, each band of GERAN, each
band class of CDMA2000HRPD and CDMA2000 1xRTT will have a
specific threshold.
Threshx, low This specifies the threshold used in reselection towards frequency X
priority from a higher priority frequency. Eachfrequency of E-UTRAN
and UTRAN, each band of GERAN, each band class of CDMA2000
HRPD and CDMA20001xRTT will have a specific threshold.

Threshserving, low This specifies the threshold for serving frequency used in reselection
evaluation towards lower priority E-UTRANfrequency or RAT.
Sintrasearch This specifies the threshold (in dB) for intra frequency measurements.
Snonintrasearch This specifies the threshold (in dB) for EUTRAN inter-frequency and
inter-RAT measurements.
TCRmax This specifies the duration for evaluating allowed amount of cell
reselection(s).
NCR_M This specifies the maximum number of cell reselections to enter
medium mobility state.
NCR_H This specifies the maximum number of cell reselections to enter high
mobility state.
TCRmaxHyst This specifies the additional time period before the UE can enter
normal-mobility.
4. Cell selection threshold Qqualmin - Minimum required quality level in the cell (dB). This
is applicable only for FDD cells.
5. Uplink Power control – Uplink power control determines the average power over a SC-
FDMA symbol in which the physical channel is transmitted. PUCCH supports transmission
of ACK/NACK, CQI report and scheduling requests. Coverage can be controlled by UEs
Physical Uplink Control Channel (PUCCH) and Physical Uplink Shared Channel (PUSCH).
Parameters p0_nominal_pusch and p0_nominal_pucch are two critical parameters which
define PUSCH and PUCCH transmit power.
2.2 Interference Control

Downlink (DL) inter cell interference which reduces the signal quality is a major factor
contributing to degraded service. It usually impacts cell-edge users which lack good quality RF
signal due to the presence of multiple serving sectors of similar signal strength. DL inter-cell
interference scenario can also be observed in dense urban areas where multipath factor can results
in strong signals from various sectors in one geographic region. DL interference if not corrected
can lead to poor throughput performance on both downlink and uplink. Therefore an improved DL
coverage in terms of both signal strength and quality provides better user experience.
Indicators such as low Signal to noise ratio (SINR), low scale Channel quality indicator (CQI),
Transmission mode (transmit diversity), low Reference Signal Received Quality (RSRQ) and high
Block error rate (BLER) are common indicators of DL interference. Low SINR and low CQI
reports result in lower and more robust modulation scheme for data transmission. The first step in
optimization efforts is to improve the coverage and quality of existing serving cells resulting in

good quality of service (QoS).

RSRQ is defined in TS 36.214 as:
Reference Signal Received Quality (RSRQ) is defined as the ratio N×RSRP/(E-UTRA carrier
RSSI), where N is the number of RB’s of the E-UTRA carrier RSSI measurement bandwidth. The
measurements in the numerator and denominator shall be made over the same set of resource
blocks.
E-UTRA Carrier Received Signal Strength Indicator (RSSI), comprises the linear average of the
total received power (in [W]) observed only in OFDM symbols containing reference symbols for
antenna port 0, in the measurement bandwidth, over N number of resource blocks by the UE from
all sources, including co-channel serving and non-serving cells, adjacent channel interference,
thermal noise etc.
The reference point for the RSRQ shall be the antenna connector of the UE.
If receiver diversity is in use by the UE, the reported value shall not be lower than the
corresponding RSRQ of any of the individual diversity branches.
Figure 5: Indicators of DL Interference

DL interference is usually controlled by maintaining equal power boundaries for cells within a
contiguous cluster. Containing the coverage of a cell only to its intended service region ensures that
the cell is not overshooting and adding to DL interference elsewhere. For boomer sites, use of
mechanical tilt is common practice to contain the coverage and direct the energy in intended
service areas. In reference to mechanical tilt, the gain reduction occurs in the direction or azimuth
of antenna whereas with electrical tilt, there is identical gain reduction in all directions. Antenna
selection during design process is also crucial in planning a good quality network. Knowledge of
antenna characteristics such as horizontal and vertical beam width and side lobes should be utilized
in selecting optimized tilts and azimuth. Transmit attenuation can be used to control excessive DL
interference.
A proper drive test must be conducted to identify the root cause of DL interference. The use of
scanners is recommended; scanner log analysis is useful in pin-pointing overshooting sectors.
Introduction of a new channel or carrier is another approach to tackle interference. However, many
operators do not have this option due to limited licensed spectrum. The idea of new macro or small
cell additions and capacity carriers are considered in cases where DL interference cannot be
controlled due to several network constraints.
Figure 6: Example of an overshooting sector

Figure 7: Improvement in SINR as a result of down-tilt
Other than general optimization practices to control interference, LTE also offers features such as
„Inter cell Interference Coordination (ICIC)‟ technique which dynamically controls interference
based on UE‟s CQI reports.
Downlink ICIC (DL-ICIC) enhances cell-edge UE performance by adjusting the power for UE
based on reported channel condition. Cell center users get different power allocation based on UE‟s
feedback.
Average CQI Threshold metric is used to differentiate cell edge and cell center users. DL power
control mechanism uses the channel estimation to adjust the Pa parameter which leads to:
 If the user is estimated to be in cell center condition, UE specific DL power related

parameter Pa is lowered, which results in power reduction of data subcarriers for that UE
and further decreases interference to neighboring cells
 If UE is estimated to be in cell center condition, Pa is increased and hence data subcarriers
power is increased to maintain edge UE‟s quality
The ratio of PDSCH EPRE to cell-specific RS EPRE among PDSCH REs (not applicable to
PDSCH REs with zero EPRE) for each OFDM symbol is denoted by either  A or  B according
to the OFDM symbol index

Uplink ICIC (UL-ICIC) feature is used to control uplink interference. Below flow explains how
uplink power control is implemented using indicators such as Interference over thermal (IOT),
Interference overload indicator (IOI).
 eNBs exchange IOI over X2 Interface

o IOI Information is set as (High/Medium/Low) on per PRB basis
 eNB estimates the IOT (Interference Over Thermal) on per PRB basis
 IOT is an estimation of interference from neighboring cells
 IOT is estimated as:
o RSSI - Serving_signal_power - Thermal Noise
o Serving Signal Power = Based on UE Channel Estimation (using SRS/DMRS)
o Thermal Noise = Based on minimum RSSI over a collection period
 Following parameters are then used to determine the IOI indication based on IOT
Parameter Range Default Description
1 to 128
32 The desired IOT (interference over thermal) from neighboring
UL TARGET IOT (step size :
(8dB) cells used for the ICIC Procedure as explained below
0.25dB)
Interference overload indicator(IOI) is a signaling to the

neighboring cells to indicate the interference status
(high/medium/low) for ICIC operation
UL IOI 1 to 128
2 IOI is set as:
THRESHOLD (step size:
(0.5dB) If current IOT < (ulTargetIot – ulIoiThresholdStep ), IOI =
STEP 0.25dB)
low status
If current IOT > (ulTargetIot + ulIoiThresholdStep ), IOI =
high status
Else, IOI = medium status.
eNB calculates ICIC metric of each UE at every ICIC period
ICIC metric= (IOI_factor) + (delta_interference) + (Fairness Factor)
o IOI_factor is cell-specific
 Reflects the estimated neighboring eNBs‟ interference level experienced.
 IOI_factor is calculated from IOI information from all neighboring eNBs
by averaging the IOI information of all PRBs and all eNBs.
o Delta_interference is UE-specific
 Contributed IOT – Target IOT

 Contributed IOT is estimated interference to neighboring eNBs created by

UE
 Amount of contributed IOT can be determined by path loss between UE
and neighboring eNBs and by using the UE Transmit Power information
from PHR (Power Headroom Report)
 Path loss can be obtained using the measurement report from UE
or
 Estimation based on UE‟s channel condition (CQI, RSRP etc.)
o Fairness Factor is UE-specific
 Results in fairness among UEs, without which, cell center UEs could have
very low ICIC metric causing them to use high power
 Power control
o For UEs with high ICIC metric, TPC (Transmit Power Command) of -1dB is used.
o For UEs with low ICIC metric, TPC of +1dB is used.
2.3 LTE Handover Optimization

Handover success rate is another important KPI focused on in optimization process. Having a good
success rate indicates that sites in network connect to each and user can enjoy uninterrupted access
to network in mobility scenarios. The impact of LTE handover performance depends on what a
type of applications users are running at their end. For example, poor handover performance or
high handover latency have low impact on applications such as file transfer where a small
interruption can be tolerable whereas bad handover performance may have severe impact on VOIP
applications where a handover drop results in voice call drop.
2.3.1 Active mode handover

Active mode handover can be of three different types:
1. Intra/Inter Frequency – Handover between cells using sane or different center frequencies
2. Intra/Inter eNB – Handover between cells of the same or different site
3. S1/X2 based – Handover involving MME interaction or directly between two eNBs using
X2 links
UE can be configured in connected state to report several different types of measurements based on
event types as explained below.

o Event A1
 Serving becomes better than a threshold
 Used to deactivate Gap Measurements
o Event A2
 Serving becomes worse than a threshold
 Used to activate Gap Measurements
o Event A3
 Neighbor becomes offset better than the Serving
 Used to trigger Intra-FA Handoff
o Event A4
 Neighbor becomes better than a threshold
 Used for ANR
Figure 8: X2 based Active handover call flow
Next section discusses the configuration related to Event A3 which is used to facilitate Intra-FA
LTE handover.

Figure 9: A3 Event description
• In active mode measurements are performed only when Serving Cell RSRP falls below a
configurable threshold (Smeasure)
• The A3 event parameters for Active mode measurement are transmitted via RRC
Connection Reconfiguration Message
• The parameter a3offset defines the (neighbor + offset > serving) criteria.
• Additionally, there is a cell individual offset that can be configured per neighbor
(Ind_offset).
• This criterion must be satisfied over a configurable period of time for the measurement
report to be done (TimeToTrigger).
• The measurement criteria can be based on RSRP or RSRQ and is configurable
(TriggerQuantity).
• The measurement report can be configured to report RSRP/RSRQ or both
(ReportQuantity).
• Periodic reports can be generated after the Event criteria are met based on a configurable
parameter (reportInterval).
• Number of reports generated based on the event is controlled using a configurable
parameter (reportAmount)

LSM Command LSM Parameter Unit Range Default
A3_Offset 0.5db -30db to +30db 4
0,40,64,80,100,128,
Time_To_Trigger ms 160,256,320,480,512,640,1024,1280,2560 480ms
,5120
Trigger_Quantity RSRP or RSRQ RSRQ
RTRV-EUTRA-
A3-CNF Same as Trigger Quantity
Both (RSRQ &
Report_Quantity Or
RSRP)
Both
120ms, 240ms, 480ms, 640ms, 1024ms,

Report_Interval ms 2048ms, 5120ms, 10240ms, 1min, 240ms
6min, 12min, 30min, 60min
Report_Amount 1,2,4,8,16,32,64, infinity 8
CHG-MEAS- *RSRP
S_Measure 0 ~ 97 60
FUNC Range

LSM Details
LSM Parameter Range/Size Default
Command
The RSRP measurement is
filtered by the UE before
sending the measurement report
using the following formula. M
fc0, fc1, fc2, fc3,
is the latest measured result, F
fc4, fc5, is the filtered result and the
factor “a” is based on the filter
Rsrp_Filter_Coefficient fc6, fc7, fc8, fc9, 4
coefficient. More the co-
fc11, fc13, efficient the new filtered result
is influenced more by the
fc15, fc17, fc19
previous filtered value than the
current measured value.
a = 1/2(k/4)
CHG-QUANT-
EUTRA
The RSRQ measurement is
filtered by the UE before
sending the measurement report
fc0, fc1, fc2, fc3, using the following formula. M
fc4, fc5, is the latest measured result, F
is the filtered result and a is
rsrqFilterCoefficient fc6, fc7, fc8, fc9, 4 based on the filter coefficient.
fc11, fc13, More the co-efficient the new
filtered result is influenced
fc15, fc17, fc19 more by the previous filtered
value than the current measured
value.
A3 offset and Smeasure are two critical parameters which can be tweaked to improve handover
performance. Additionally, „cell individual offset‟ and „Hysteresis‟ parameters can be applied to
improve handover performance.
A3 event description as per 3GPP TS 36.331:

The UE shall:
1> consider the entering condition for this event to be satisfied when condition A3-1, as
specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified
below, is fulfilled;
Inequality A3-1 (Entering condition)

Mn  Ofn  Ocn  Hys  Ms  Ofs  Ocs  Off
Inequality A3-2 (Leaving condition)

Mn  Ofn  Ocn  Hys  Ms  Ofs  Ocs  Off

The variables in the formula are defined as follows:
Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as
defined within measObjectEUTRA corresponding to the frequency of the neighbour cell).
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within
measObjectEUTRA corresponding to the frequency of the neighbour cell), and set to zero if
not configured for the neighbour cell.
Ms is the measurement result of the serving cell, not taking into account any offsets.
Ofs is the frequency specific offset of the serving frequency (i.e. offsetFreq as defined within
measObjectEUTRA corresponding to the serving frequency).
Ocs is the cell specific offset of the serving cell (i.e. cellIndividualOffset as defined within
measObjectEUTRA corresponding to the serving frequency), and is set to zero if not
configured for the serving cell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within
reportConfigEUTRA for this event).
Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigEUTRA
for this event).
Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Ofn, Ocn, Ofs, Ocs, Hys, Off are expressed in dB.
2.3.2 Idle Mode Handover

Idle mode handover or cell reselection is the process used by UE and network to monitor UE‟s
location without it requiring radio resources. In Idle mode, UE remains attached at MME level but
remains RRC idle unless it requires RRC resources (for eg. To perform TAU or Paging procedures)
Maintaining most current and updated neighbor list on the eNBs is critical to facilitate successful
handover. Neighbor list must be updated frequently to accommodate addition of new sites and
sectors in the network.
Condition where multiple handovers are recorded within a very short period between same two
cells in stationary or mobile scenario is known as Ping-Pong. Ping-Pong condition affects the end
user as more processing time results in poor user experience. This situation arises when both source
and target sectors meet the handover thresholds and are equivalent in signal strength. Ping-Pong
can occur in both strong and weak conditions. A3 offset, S-measure, Hysteresis and Cell individual
offset are some parameters which can be tweaked to reduce Ping-Pong rate. Fig 1I shows an
example of Ping-Pong condition

Figure 10: Example of Handover optimization
Samsung eNB's neighbor optimization function calculates the neighbor priority and optimally
manages the neighbor information based on calculated priority. In addition, it prevents handover
execution for a specific cell using handover blacklist feature. The priority is calculated using
handover statistics. It maintains the optimum and most current neighbor information by
periodically calculating the priorities.
UE Serving Cell Target Cell LSM
Measurement Report
HO preparation
HO Command
HO execution
(1) HO Statistics
(2) Ranking Calculation Period
 NR Ranking Calculation  Change from NRT to

 Lower HO Quality HO Black List
Calculation  Restore from HO Black
 HO-to-Black-Cell Ratio List to NRT
Calculation
(3) CLI command

(NO HO = ON or OFF)
Figure 11: Operational procedure for Neighbor Relation Optimization

The automatic neighbor relation function through UE measurement is used for adding
neighbors via the LSM or the UE measurement in the following cases:
 During UE handover
 When source cell lacks the target cell neighbor information
This function can be turned on/off using the CHG-SONFN-CELL command.

The CHG-SONFN-CELL command has the following ANR_ENABLE field parameter values:
 sonFuncOff: The ANR function is not performed.
 sonManualApply: NR deletion (X2 based), handover blacklist addition according to

NR priority level and NRT recovery are performed automatically. Note that NR
deletion or blacklist addition requires user confirmation.
 sonAutoApply: NR deletion (X2 based), handover blacklist addition according to NR

priority level and NRT recovery are performed automatically.
2.4 EUTRAN and CDMA2000 Handover

EUTRAN and CDMA2000 handover can be useful when both networks are overlaid on same
geographical region. A user traveling out of LTE coverage area can hand down to HRPD while
maintaining the same data session and uninterrupted data transfer. This feature is helpful in cases
where a new LTE network is deployed on a matured CDMA2000 network and UE can rely on
underlying network whenever it goes out of coverage on LTE
Implementation of Neighbor list for underlying CDMA network is needed to facilitate EUTRAN to
CDMA2000 handover. On LTE side, appropriate neighboring sectors with PN and channel
information are populated. Right HRPD neighbors can be selected based statistics such as
Handover matrix (HOM) data of CDMA network. Optimization drive test can also give useful
information in defining missing or appropriate neighbors for EUTRAN to CDMA2000
interworking.
Below table explains Parameters and Events used on EUTRAN to CDMA2000 interworking:
Message IE Parameter Description

RRC B2 Event b2Threshold1Rsrp RSRP threshold1 used for
Connection triggering the EUTRA
Reconfiguration measurement report for
CDMA2000 HRPD Event B2.

b2Threshold1Rsrq RSRQ threshold1 used for

triggering the EUTRA
measurement report for
CDMA2000 HRPD Event
B2.
b2Threshold2Cdma2000 CDMA2000 threshold 2 used
for triggering the inter-RAT
CDMA2000 measurement
report for CDMA2000
HRPD Event B2.
qOffsetFreq
hysteresisB2 Hysteresis applied to entry
and leave condition of
timeToTriggerB2 timeToTrigger value for
CDMA2000 HRPD Event
B2. The timeToTrigger value
is the period of time that must
be met for the UE to trigger a
measurement report.
reportIntervalB2 The reporting interval of a
CDMA2000 HRPD Event
B2.
reportAmountB2 The number of measurement
reports for CDMA2000
HRPD Event B2.
maxReportCellsB2 The maximum number of
cells included in a
triggerQuantityB2 Quantity that triggers the
Event B2 measurement The
trigger can be set for either
RSRP or RSRQ and is only
applicable on threshold 1.
RRC A2 Event a2ThresholdRsrp A2 event is triggered when
Connection source becomes worse than
Reconfiguration the configured RSRP
threshold (Refer to standard
36.133 for RSRP Report
mapping)
a2ThresholdRsrq Primary RSRQ threshold
value for eventA2. Used only
when triggerQuantityA2Prim
is set to RSRQ.
reportIntervalA2 Determines the reporting
interval of a measurement
report for Event A2
triggerQuantityA2 A1 event is triggered when
source becomes worse than
the configured RSRQ
threshold ((Refer to

standard 36.133 for RSRQ

Report mapping)
hysteresisA2 Hysteresis applied to entry
and leave conditions of Event
A2
timeToTriggerA2 The timeToTrigger value is
the period of time that must
measurement report for Event
A2
reportAmountA2 The number of reports for
periodical reporting for the
primary eventA2
measurement .
Value 0 means that reports are

sent as long as the event is
fulfilled.
Primary and secondary

measurement parameters refer
to the option to use different
settings for two simultaneous
measurements for eventA2.
maxReportCellsA2 The maximum number of

cells included in a
A2.
reportQuantityA2 Determines whether the
Measurement report for A2
event includes both RSRP and
RSRQ information or the only
RSRP or RSRQ as configured
by the Trigger event above.
filterCoefficientEUtraRsrp Filtering coefficient used by
the UE to filter RSRP
measurements before event
evaluation The measurement
filter averages a number of
measurement report values to
filter out the impact of large
scale fast fading.
filterCoefficientEUtraRsrq Filtering coefficient used by
the UE to filter RSRQ
measurements before event
evaluation The measurement
filter averages a number of
measurement report values to
filter out the impact of large
scale fast fading.
RRC A1 Event a1ThresholdRsrp A1 event is triggered when
Connection source becomes better than
Reconfiguration the configured RSRP

threshold ( Actual Threshold

= Parameter - 140, 36.133
standards) dbm
a1ThresholdRsrq A1 event is triggered when
source becomes better than
the configured RSRQ
threshold (Refer to 36.133
standard for RSRP Report
mapping)
triggerQuantityA1 Determines whether Event A1
is triggered based on RSRP or
RSRQ criteria.
reportQuantityA1 Determines whether the
Measurement report for A1
event includes both RSRP and
RSRQ information or the only
RSRP or RSRQ as configured
by the Trigger event above.
maxReportCellsA1 The maximum number of
cells included in a
A1.
hysteresisA1 Hysteresis applied to entry
and leave conditions of Event
A1.
timeToTriggerA1 The timeToTrigger value is
the period of time that must
A1
reportIntervalA1 Determines the reporting
interval of a measurement
report for Event A1
reportAmountA1 Determines the number of
measurement reports UE
needs to send when Event A1
criteria is met
SIB8 systemTimeInfo timeAndPhaseSynchCritical
CellReselection bandClass Identifies the CDMA-eHRPD
Parameters frequency band class in which
CDMA 2000 the carrier frequency can be
found
cellReselectionPriority Reselection priority of the cell
in the eNB. The range is 0-7,
where 0 indicates low, and 7
high in priority.
threshXHigh ThreshXHigh of CDMA2000

HRPD band class DB.
threshXLow ThreshXLow of CDMA2000
HRPD band class DB.

tReselectionSfUsageHRPD Whether to use

tReselectionSfUsageHRPD of
HRPD reselection information
that is sent down to SIB8.
tReselectionSfUsageHRPD
determines whether to apply a
scaling factor for HRPD cell
reselection.
tReselectionHRPD TReselctionHRPD included in
the HRPD Reselection
information sent to SIB8. The
default is 0, and can be
changed by the operator.
tReselectionSfHighHRPD Value by which parameter
tReselectionCdmaHrpd is
multiplied if the UE is in a
high mobility state as defined
in 3GPP TS 36.304
tReselectionSfMediumHRPD TReselectionSfMediumHRPD
included in the HRPD
Reselection information sent
to SIB8.
searchWindowSize The size of the search window
in the eNB.

2.5 RAN Parameters

This section talks about two eNB sector level parameters called, Physical Cell Identity (PCI) and
Root Sequence Index (RSI).
2.5.1 Physical Cell Identity

PCI is derived from two physical layer signals – Primary Synchronization Signal (PSS) and
Secondary synchronization signal (SSS). There are 504 unique PCIs. The physical-layer cell
identities are grouped into 168 unique physical-layer cell-identity groups, each group containing
three unique identities. The grouping is such that each physical-layer cell identity is part of one and
cell
only one physical-layer cell-identity group. A physical-layer cell identity N ID  3N ID
(1)
 N ID
(2)
is thus
(1)
uniquely defined by a number N ID in the range of 0 to 167, representing the physical-layer cell-
(2)
identity group, and a number N ID in the range of 0 to 2, representing the physical-layer identity
within the physical-layer cell-identity group.
Each cells Reference signal transmits a pseudo random sequence corresponding to assigned PCI.
And channel quality measurements are also made on reference signals. Thus, an optimized
allocation of PCIs is needed to avoid problems in cell recognition or cell search. During PCI
planning, one needs to avoid same PCI and PSS on neighboring cell. This eliminates confusion in
cell search and also reduces interference which can occur due to PSS or reference signal collision.
Figure 12: Example of optimum PSS planning

2.5.2 Root Sequence Index (RSI)

The Preambles used in RACH procedure are derived from Root Sequence. Preambles are obtained
by cyclic shifts of root sequence which are based on Zadoff-Chu sequence. There are 838 Root
Sequences available. There are 64 preambles available per cell and UE randomly selects one
preamble to perform random access procedure. If number of preambles per root sequence is less
than 64 Preambles, continue deriving Preambles with next Root Sequence unit 64 preambles are
obtained.
Thus, unique assignment of Root sequence is recommended between neighboring cells. Below two
tables describes Ncs to Zero Correlation zone config mapping and LSM parameter for configuring
RSI and Zero correlation zone config parameter.
N CS value
N CS configuration
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 -
LSM Parameter
Parameter Range Default
type
Root_sequence_Index 0 ~ 837 Planned
Zero_correl_zone_config 0 ~ 15 12
3 (Alpha)
CHG-PRACH-
CONF 4 (Beta)
Prach_Config_Index 0 ~ 63
5 (Gamma)

2.6 e-NodeB - Control Parameters

This section describes some parameters which can help improve call sustainability and reliability
resulting in better network performance.
HARQ Control
CQI Control
AMC Control
2.7 Parameter Reference Guide

Following mapping table provides a quick reference guide for optimization and troubleshooting
each of the LTE KPIs:
KPI Parameters/Drive test log analyses Soft Parameters eNB/LSMR

QRxlevMin, QqualMin, Backoff
Connection
RSRP, SINR Parameter, MSG4HARQ, eHRPD
success rate
redirection parmeters
Connection
RSRP, SINR, UL BLER, DL BLER
drop rate Check call release cause
X2 link status, Neighbor list, A3 offset,
Handover
RSRP, SINR Smeasure, Cell Individual offset, ANR,
Success Rate
PCI collision
Handover
HO Interruption time
Latency Backhaul delay, X2 interface
RSRP, SINR, DL MCS, DL RB,
DL Throughput
PDSCH TP, RI, CQI, DL BLER DL ICIC
RSRP, SINR, UL MCS, UL RB,
UL Throughput PUSCH TP, CQI, UL BLER, PDCCH
BLER UL ICIC
2.8 Relevant Documents and Processes

Please contact Sprint or STA National RF team for latest releases of following documents:
1. Site Modification Process Flow
2. Golden Parameters for LTE and eHRPD
3. Released feature request documentation (FRD)
4. 510 LTE eNB Maintenance Manual
5. 410 MMBS Operational manual

CHAPTER 3. Call Release Cause
The Call Release Cause is explained below:

Value Call Release
Description Collection Time
DEC HEX Cause
A failure occurs in GW
S1AP_CauseRadio during the handover, or When the target eNB receives the
256 0X0100 Network_ the handover preparation Handover Cancel message from
unspecified fails if the MME cannot the source eNB.
process the handover.
- When gbrType of QCI received
within
E_RABLevelQoSParameters IE of
the Initial Context Setup Request
message is GBR but
gbrQosInformation received is not
present.
within
S1AP_invalid_qos_ The action fails due to
283 0x011B the E_RAB Setup Request
combination invalid QoS combination.
message is GBR but
present.
within
the E_RAB Modify Request
message is GBR but
present.
Used in the UE context release
S1AP_authenticatio The action occurs due to
307 0x0133 when the call fails due to the
n_failure the authentication failure.
authentication failure.
When the target eNB receives the
X2AP_CauseMisc_ Default X2 cause in the
566 0X0236 Handover Cancel message from
unspecified eNB.
the source eNB.
The RRC Connection When timRrcConnectionSetup

Setup Complete message is received because the
RRC_TMOUT_ message is not received timer is ended that waits until the
768 0X0300 rrcConnectionSetu after the RRC RRC Connection Setup Complete
p Connection Setup message is received after sending
message is sent to the the RRC Connection Setup
UE. message to the UE

Value Call Release

DEC HEX Cause
The RRC Connection When timRrcConnectionReconfig

Reconfiguration message is received due to the
Complete message is not timer termination while waiting to
received after the RRC receive the RRC Connection
Connection Reconfiguration Complete
Reconfiguration message after the RRC
message is sent to the Connection Reconfiguration
UE. message is sent to the UE
- SB2DB State: sending
RRC_TMOUT_ - SB2DB state: Initial Context
Initial Context Setup
769 0X0301 rrcConnectionReco Setup Failure
Failure
nfig
- Other State: sending
- INCELLue state: UE Context
UE Context Release
Release Request
Request
- REESTue2 state: UE Context
Release Request
- GAPprepare state: UE Context
Release Request
- ANRprepare state: UE Context
Release Request
When
The RRC Connection
timRrcConnectionReEstablish
Reestablishment
message is received due to the
Complete message is not
RRC_TMOUT_ timer termination while waiting to
received after the RRC
770 0X0302 rrcConnectionReEs receive the RRC Connection
Connection
tablish Reestablishment Complete
Reestablishment
message after the RRC
message is sent to the
Connection Reestablishment
UE.
message is sent to the UE
When the
The Security Mode timRrcSecurityModeCommand
Complete message is not message is received due to the
RRC_TMOUT_
received after the timer termination while waiting to
771 0X0303 rrcSecurityModeCo
Security Mode Command receive Security Mode Complete
mmand
message is sent to the message after the Security Mode
UE. Command message is sent to the
UE
When the
The UE Capability timRrcUeCapabilityEnquiry
Information message is message is received due to the
RRC_TMOUT_
not received after the UE timer termination while waiting to
772 0X0304 rrcUeCapabilityEnq
Capability Enquiry receive the UE Capability
uiry
message is sent to the Information message after the UE
UE. Capability Enquiry message is
sent to the UE
The RRC Connection

Reconfiguration When the timer ends while waiting
Complete message is not to receive the RRC Connection
RRC_TMOUT_intra
received after the RRC Reconfiguration Complete
_
775 0X0307 Connection message after the RRC
HandoverCmdCom
Reconfiguration Connection Reconfiguration
plete
message is sent to the message is sent to the UE during
UE during the Intra the intra eNB handover
handover.

Value Call Release

DEC HEX Cause
The RRC Connection
RRC_TMOUT_inter
_
X2HandoverCmdC
omplete
UE during the X2 the intra X2 handover
handover.
The RRC Connection
RRC_TMOUT_inter
_
S1HandoverCmdC
omplete
UE during the S1 the intra S1 handover
handover.
When the
The Initial Context Setup timS1InitialContextSetup message
S1AP_TMOUT_ Request message is not is received due to the timer
787 0X0313 s1InitialContextSet received after the Initial termination while waiting to
up UE message is sent to receive the Initial Context Setup
the MME. Request message after the Initial
UE message is sent to the MME
S1AP_TMOUT_ When the timS1PathSwitch
The Path Switch Request
Acknowledge message is
timer termination while waiting to
not received after the
790 0X0316 receive the Path Switch Request
s1PathSwitch Path Switch Request
Acknowledge message after the
Path Switch Request message is
MME.
sent to the MME
S1AP_TMOUT_ The UE Context Release When the timS1RelocOverall
Command message from message is received due to the
the MME is not received timer termination while waiting to
because the handover is receive the UE Context Release
792 0X0318
s1RelocOverall complete after the Command message from the
Handover Command MME after the Handover
message is received Command message is received
from the MME. from the MME
The MME Status When the timer ends while waiting
S1AP_TMOUT_ Transfer message is not for the MME Status Transfer
794 0x031A s1MMEStatusTrans received after the eNB message after the eNB Status
fer Status Transfer message Transfer message is sent to the
is sent to the MME. MME
X2AP_TMOUT_ The UE Context Release

When the timX2RelocOverall
message is not received
from the Target eNB
because the handover is
804 0x0324 receive the UE Context Release
x2RelocOverall complete after the
message after the Handover
Handover Acknowledge
Acknowledge message is
message is received
received from the target eNB
from the Target eNB.
The MME Status When the timer ends while waiting
X2AP_TMOUT_ Transfer message is not for the MME Status Transfer
805 0x0325 x2SNStatusTransfe received after the eNB message after the eNB Status
r Status Transfer message Transfer message is sent to the
is sent to the MME. MME

Value Call Release

DEC HEX Cause
When the
timInternalResourceSetup
receive the response after the
SetupReq message is sent to
assign resources to the protocol
blocks within the eNB
The response message - SB2DB state: Initial Context

is not received after the Setup Failure
RRC_TMOUT_ SetupReqe message is
- DB2DBScomplete state: UE
816 0X0330 internalResourceSe sent for setting the
Context Release Request, E_RAB
tup resource for the internal
Setup Response
protocol blocks of the
eNB. - DB2DBMcomplete state: UE
Context Release Request, E_RAB
Modify Response
- DB2DBRfail state: E_RAB
Release Response
- PHYREcomplete state: UE
Context Release Request
- INTERprepare_T state:
Handover Failure
When receiving the
timInternalSecurityControl
After sending the message because the timer is
msgCpdcpSecurityContr ended that waits until the
RRC_TMOUT_ msgCpdcpSecurityControlSucces
ol message to the PDCB,
818 0X0332 internalSecurityCon s message is received after
cannot receive the
trol sending the
msgCpdcpSecurityContr
olSuccess message msgCpdcpSecurityControl
message to the PDCB
- SB2DBint state-SB2DBciph state
During Handover, after During Handover, when the

sending the timInternalForwardingPathSetup
msgCgtpSetupReq message is received because the
RRC_TMOUT_ message to the GTPB for timer is ended that waits until the
820 0X0334 internalForwarding setting uplink and msgCgtpSetupCnf message is
PathSetup downlink path, cannot received after sending the
receive the msgCgtpSetupReq message to
msgCgtpSetupCnf GTPB for setting the uplink,
message downlink path
When the
The timInternalReestablishControl
msgCrlcControlSuccess message is received due to the
or timer termination while waiting to
msgCpdcpControlSucces receive the
RRC_TMOUT_
s is not received after the msgCrlcControlSuccess or
821 0X0335 internalReestablish
msgCrlcControl, msgCpdcpControlSuccess
Control
msgCpdcpControl message after the msgCrlcControl
message is sent for RLC, or msgCpdcpControl message is
PDCP reestablishment sent for RLC, PDCP
during inter eNB HO. reestablishment during inter eNB
HO

Value Call Release

DEC HEX Cause
When the timInternalBufferFlush

The
msgCpdcpBufferFlushCn
f message is not
RRC_TMOUT_ receive the
822 0X0336 received after the
internalBufferFlush msgCpdcpBufferFlushCnf
msgCpdcpBufferFlush
message after the
msgCpdcpBufferFlush message is
PDCB during handover.
sent to the PDCB during handover
When the
timInternalDataTransferStart
receive the
msgCpdcpControlSuccess
The message after the
msgCpdcpControlSucces msgCpdcpControl message is
RRC_TMOUT_ sent
s message is not
823 0X0337 internalDataTransfe
received after the
rStart - INCELLresume state: key
msgCpdcpControl
message is sent. refreshing
- INTRAresume state: Intra Cell
handover
- INTERstart_T state: Inter eNB
handover
- REESTresume1 state:
Reestablish
When the
RRC_USER_INAC msgCmacPhyUserInactivityInd
833 0X0341 UE is in inactive status.
TIVITY message is received from the
MACB.
After sending only as When the timer ends while

much as the RLC Max running the
RRC_ARQ_MAX_
retransmission count, the timInternaReestablshTimeToWait
834 0X0342 RE_
UE status does not timer after the
TRANSMISSION
become active for a msgCrlcMaxRetransInd message
certain period of time. is received from the RLCB
RRC_RADIO_LINK The radio link with the The MAC notifies the ECCB of the
835 0X0343
_ FAILURE UE failed. possible release of the uplink

Value Call Release

DEC HEX Cause
The MAC notifies the radio link with the UE if it fails to
ECCB of the possible receive the HARQ-ACK/NACK
release of the uplink 200 times or more consecutively
radio link with the UE if it for the downlink data
fails to receive the (msgCmacPhyOutOfSynchInd). If
HARQ-ACK/NACK 200 the ECCB is notified by the MAC
times or more of being InSync again (HARQ-
consecutively for the ACK/NACK received 20 times), or
downlink data. If the if it fails to receive the RRC
ECCB is notified by the Connection Re-establishment
MAC of being InSync Request from the UE, the call is
again (HARQ- released after a time-out (default:
ACK/NACK received 20 5 seconds,
times), or if it fails to timInternaReestablshTimeToWait)
receive the RRC .
Connection Re-
establishment Request
from the UE, the call is
released after a time-out
(default: 5 seconds).
When the RRC Connection
The RRC Connection Reestablishment Request
Reestablishment message is received by the
RRC_REEST_FAIL
838 0X0346 Request message is incorrect state (SB2DB state),
_ INVALID_ STATE
received in the invalid then the RRC Connection
state. Reestablishment Reject message
is sent
The UE Context Release
Command is received in
the unexpected abnormal
state (the cause in the
message: normal When the cause of the UE
S1AP_RCV_S1_ release, detach, Context Release Command
UECTXTRELEASE successful handover). received from the MME is:
840 0X0348 CMD_ The eNB triggers the normal_release, detach or
ABNORMAL_STAT cause when it receives successful_handover while the
E the UE Context Release procedure with the MME is not
Command message complete
including ‘normal release’
in a state that does not
involve the Initial Context
Setup procedure.
RRC_RCV_RESET The call is released after
When the Reset Request
_ the Reset Request
841 0X0349 message is received from the
REQUEST_FROM message is received
ECMB block.
_ECMB from the ECMB block.
S1AP_RCV_S1_R The call is released by
When the Reset message is
842 0X034A ESET_ receiving the Reset
received from the MME
FROM_MME message from the MME.
The call is released after When the S1 status in the
S1AP_S1_SCTP_
the S1 Association msgCsctpStatusInd message
844 0X034C OUT_OF_SERVIC
changes to ‘out of received from the SCTP is
E
service.’ ‘out_of_service’
RRC_RCV_CELL_ The call is released after - When the Cell Release Ind is
845 0X034D RELEASE_IND_FR the Cell Release Ind received from the ECMB block
OM_ ECMB message is received due to the CPRI failure

Value Call Release

DEC HEX Cause
from the ECMB block. - When the Cell Release Ind is
received from the ECMB block
due to the DSP failure
The call remains in the When the call remains in the

RRC_DSP_AUDIT ECCB and MAC, but not ECCB and MAC, but not in the
846 0x34E _RLC_ in the RLC. This creates RLC when the
CALL_RELEASE a resource mismatch and msgCdspResourceNotification
the call is released. message is received
The call remains in the When the call remains in the

RRC_DSP_AUDIT ECCB and RLC, but not ECCB and RLC, but not in the
847 0x34F _MAC_ in the MAC. This creates MAC when the
CALL_RELEASE a resource mismatch and msgCdspResourceNotification
the call is released. message is received
The call is cancelled due
to the resource When the call remains in the
RRC_DSP_AUDIT
mismatch, because the ECCB, but not in the RLC and
_RLC_
848 0x350 ECCB has remaining MAC when the
MAC_CALL_RELE
calls but the RLC and the msgCdspResourceNotification
ASE
MAC have no call message is received
remaining.
The security algorithm
value is received in the
Initial Context Setup
Request, S1 Handover
Request, X2 Handover
When the ciphering algorithm
Request, and S1 UE
RRC_SEC_ALGO does not have the null algorithm
Context Modification
849 0x351 RITHMS_COMBIN value even if the integrity
message. The ciphering
ATION_INVALID algorithm supports the null
algorithm should have
algorithm
the null algorithm value if
the integrity algorithm
supports the null
algorithm. Otherwise, the
call is released.
ECCB_RELEASE_
The call is released due
DUE_ When the relcallall command is
851 0x353 to the internal cause of
TO_ENB_GENERA executed
the eNB.
TED_ REASON
If calls are generated
more than the number of When DRB ID and LOCH ID are
RRM_MAX_DRB_ DRB that can be assigned after the Initial Context
875 0X036B
COUNT_ OVER accommodated by cell, Setup Request or E-RAB Setup
they are rejected by Request message is received
CAC.
If calls with the QoS that
When the permission is checked
cannot be
RRM_QOSCAC_F to allow new calls after the Rrc
876 0X036C accommodated by cell,
AIL Connection Request or Handover
they are rejected by
Request message is received.
CAC.
If DRB is generated
exceeding the When DRB ID and LOCH ID are
MAX_DRB or assigned after the Initial Context
880 0X0370 RRM_RBID_FULL
MAX_LOGH per call, Setup Request or E-RAB Setup
DRB ID and LOCH ID Request message is received
cannot be assigned.

Value Call Release

DEC HEX Cause
Occurs when the BH link

When the permission is checked
usage by the QoS (GBR
ECCB_ERRM_BH to allow new calls after the Rrc
881 0x0371 Bearer) exceeds the
CAC_FAIL Connection Request or Handover
threshold defined in the
Request message is received.
PLD.
If a new call supports
both SRS and DRX, the
SRS resources need to
assigned in advance to
When assigning the DRX
RRM_SRS_MUST assign the DRX
888 0X0378 resources if a new call supports
_BE_ ASSIGNED resources but cannot
both SRS and DRX
assign the DRX
resources because the
SRS resource is not
assigned.
The database in the
CQI/PMI is abnormal.
RRM_CQIPMI_DB When assigning CQI/PMI
892 0X037C CQI/PMI resources
_ ABNORMAL resources
cannot be assigned to
new calls.
CQI/PMI resources are
RRM_CQIPMI_DB When assigning CQI/PMI
893 0X037D all assigned and not
_FULL resources
available any more.
- When SPS resources are

assigned for the QCI 1 existing in
During SPS resource the DRB after the Initial Context
assignment and Setup Request or E-RAB Setup
cancellation, the SPS Request message is received, or
RRM_SPS_DB_AB the SPS resources are cleared
898 0X0382 resource search is not
NORMAL following the DRB release of the
allowed to exceed the
Max value of the SPS QCI 1
resource DB.
- When
fnELIB_DecisionDrxSpsConfig is
called.

the DRB after the Initial Context
SPS resources are all Setup Request or E-RAB Setup
RRM_SPS_DB_FU
899 0X0383 assigned and not Request message is received
LL
available any more.
- When
called.

Assigning duplicate the DRB after the Initial Context
RRM_SPS_ALREA resources is not allowed Setup Request or E-RAB Setup
900 0X0384 Request message is received
DY_ ASSIGNED since the SPS resources
are already assigned.
- When
called.

Value Call Release

DEC HEX Cause

RNTIs used for the SPS the DRB after the Initial Context
RRM_SPS_RNTI_ purpose are all assigned Setup Request or E-RAB Setup
901 0X0385 Request message is received
FULL and not available any
more.
- When
called.
n1PucchAnRep n1PucchAnRep resources are
RRM_N1PUCCHA
resources are all assigned after the Rrc Connection
903 0X0387 N_REP_
assigned and not Request or Handover Request
DB_ABNORMAL
available any more. message is received.
Since there are already
RRM_N1PUCCHA assigned resources
N_REP_ regarding the When assigning N1PUCCHAN
905 0X0389
ALREADY_ASSIG N1PUCCHAN_REP on REP resources
NED the call, it is not
assigned.
Cannot initialize because
RRM_N1PUCCH_ When the database for
the capacity of
907 0X038B DB_ N1PUCCHAN REP resources is
N1PUCCH internal
INSUFFICIENT initialized
resource DB is too small.
During SR resource
assignment and When SR resources are assigned
cancellation, the SR after the Rrc Connection Request
RRM_SR_DB_ABN
908 0X038C resource search is not or Handover Request message is
ORMAL
allowed to exceed the received, or the SR resources are
Max value of the SPS cleared following the call release
resource DB.
When SR resources are assigned

SR resources are all
RRM_SR_DB_FUL after the Rrc Connection Request
909 0X038D assigned and not
L or Handover Request message is
available any more.
received

RRM_SR_ALREAD assigned resources
910 0X038E When assigning SR resources
Y_ ASSIGNED regarding the SR on the
call, it is not assigned.
During SR resource
When SRS resources are
assignment and
assigned after the Rrc Connection
cancellation, a database
RRM_SRS_DB_ Request or Handover Request
919 0X0397 search for the SRS
ABNORMAL message is received, or the SRS
resource exceeds the
resources are cleared following
range of resources
the call release
secured.
When SRS resources are
RRM_SRS_DB_FU SRS resources are all assigned after the Rrc Connection
920 0X0398
LL assigned. Request or Handover Request
message is received

RRM_SRS_ALREA assigned resources
921 0X0399 When assigning SRS resources
DY_ ASSIGNED regarding the SRS on the
call, it is not assigned.

Value Call Release

DEC HEX Cause
During TPC PUCCH

RNTI resource When TPC PUCCH resources are
RRM_TPC_PUCC assignment and assigned after the Rrc Connection
H_ cancellation, the TPC Request or Handover Request
923 0X039B
RNTI_DB_ABNOR PUCCH resource search message is received, or the TPC
MAL is not allowed to exceed PUCCH resources are cleared
the Max value of TPC due to the call release
PUCCH resource DB.
TPC PUCCH RNTI
RRM_TPC_PUCC resources are all When assigning TPC PUCCH
924 0X039C
H_ RNTI_FULL assigned and cannot be resources
assigned further.
Assigning duplicate
RRM_TPC_PUCC When TPC PUCCH resources are
resources is not allowed
H_ assigned after the Rrc Connection
925 0X039D since the TPC PUCCH
RNTI_ALREADY_ Request or Handover Request
resources are already
ASSIGNED message is received
assigned.
SPS resources which

should be assigned prior
RRM_SPS_MUST_ When assigning TPC PUSCH
927 0X039F to the TPC PUSCH
BE_ ASSIGNED resources
resource assignment are
not assigned.
RNTIs used for the TPC

RRM_TPC_PUSC PUSCH purpose are all When assigning TPC PUSCH
928 0X03A0
H_ RNTI_FULL assigned and not resources
available any more.
Assigning duplicate When TPC PUSCH resources are

RRM_TPC_PUSC
resources is not allowed assigned for the QCI 1 existing in
H_
930 0X03A2 since the TPC PUSCH the DRB after the Initial Context
RNTI_ALREADY_
resources are already Setup Request or E-RAB Setup
ASSIGNED
assigned. Request message is received
RRM_ALL_MME_N When the MME overload is
OT_ controlled after the RRC
The MME in service does
933 0X03A5 Connection Request or RRC
not exist.
SERVICE Connection Setup Complete
message is received
If the MME is in Overload
When the MME overload is
state, it cannot
controlled after the RRC
RRM_MME_OVER accommodate the calls
LOAD because overloadAction
Connection Setup Complete
and establishmetCause
message is received
does not match.
controlled after the RRC
RRM_NOT_EXIST In MME Pool, specific
_MME MME ID does not exist.
Connection Setup Complete
message is received
The MME to controlled after the RRC
RRM_AVAILABLE_
936 0X03A8 accommodate new calls Connection Request or RRC
MME_NOT_EXIST
does not exist. Connection Setup Complete
message is received
The existing call is When a new call connection has
RRM_UE_STMSI_
937 0X03A9 released due to the same the same sTmsi value for
DUPLICATE
STMSI value. accommodating new calls

Value Call Release

DEC HEX Cause
- When receiving the
msgCgtpSetupFailure as a
response to msgCgtpSetupReq
- SB2DB state: Initial Context
Setup failure
Use it if there is response - DB2DBScomplete: E_RAB
for Gtp setup fail after Setup Response, UE Context
GTP_Setup_Failur
1536 0X0600 receiving the SetupReq Release Request
e
message from the - DB2DBRfail: E_RAB Release
ECCB. Response, UE Context Release
Request
- INTERpath_S: UE Context
Release Request
- INTERprepare_T: S1 Handover
Failure
There is a response for
When Gtp Modify fails after the
GTP_Modify_Failur Gtp setup fail after the
1538 0X0602 ModifyReq message is received
e ModifyReq message is
from the ECCB
received from the ECCB.
After the SetupReq message is received from the ECCB, a
series of the GTP setup starts: create a GTP tunnel, set a
1540 0X0604 GTP_Path_Failure timer to the echo request message to be sent to the dstip of
the message, and respond to the ECCB if a response is not
received three times within the time limit.
A response is sent when the

When the message received
message received from the dst
GTP_Not_Support_ from the dst peer has an
1541 0X0605 peer during the tunnel setup
EH extension header not
has an extension header not
supportable by the system
supportable by the system.
Send a response to cancel the

call by responding to the When receiving Error
GTP_GTP_Error_I
1542 0X0606 ECCB when receiving the Indication message from dst
nd
Error Indication message from peer
dst peer.
An invalid message response

When the callid of the
is sent when when the callid of
PDCP_Invalid_Calli downloaded message from
1792 0x0700 the downloaded message from
d the ECCB is the value of
the ECCB is the value of the
MAX_USER_ENB or higher
MAX_USER_ENB or higher.
The messages are normal if

the Rbid is below MAXS_RB
When Rbid is above
when the message
MAX_RB if the message
downloaded from the ECCB is
PDCP_Invalid_RBi downloaded from the ECCB
1793 0x0701 PDCP_DRB, or below
d is PDCP_DRB, and when
MAX_SRB when it is
Rbid is above MAX_SRB if it
PDCP_SRB and an invalid
is PDCP_SRB
message response is sent for
all other cases.
When the NumRb of the

message downloaded from
PDCP_Invalid_Nu is sent when the NumRb of the
1794 0x0702 the ECCB is sent in the
mRb message downloaded from the
value of CI_MAX_RB or
ECCB is above CI_MAX_RB.
higher

Value Call Release

DEC HEX Cause

When the RLC mode of the
PDCP_Invalid_Rlc is sent when the RLC mode of
1795 0x0703 message downloaded form
Mode the message downloaded from
the ECCB is invalid
the ECCB is invalid.
An invalid message response When the setup Type of the

PDCP_Invalid_Set is sent when the setupType of message downloaded form
1796 0x0704
upType the message downloaded from the ECCB is inappropriate
the ECCB is invalid. value
An invalid message response When the CntlType of the

PDCP_Invalid_Cntl is sent when the CntlType of message downloaded from
1797 0x0705
Type the message downloaded from the ECCB is the Unknown
the ECCB is invalid. type

is sent when the SNType of When the SNType of the
PDCP_Invalid_Pdc the message downloaded from message downloaded from
1798 0x0706
pSnType the ECCB is UM, but not the ECCB is UM, but not 7-
bit or 12-bit
7-bit or 12-bit.

is sent when the SNType of When the SNType of the
PDCP_Invalid_Pdc the message downloaded from message downloaded from
1798 0x0706
pSnType the ECCB is UM, but not the ECCB is UM, but not 7-
bit or 12-bit
7-bit or 12-bit.
An invalid message response When the logical type of the

is sent when the logical type of message downloaded from
PDCP_Invalid_Loc the message downloaded from the ECCB is other than
1804 0x0707
hType the ECCB is other than either either LOCH_DCCH (for the
LOCH_DCCH (for the SRB) or SRB) or LOCH_DTCH (for
LOCH_DTCH (for the DRB). the DRB)
Used when responding for the When the ROHC context

ROHC context setup setup procedure fails due to
PDCP_Rohc_Setu
1805 0x0708 procedure failure due to lack of lack of memory while
p_Failure
memory while receiving receiving ConfigReq from
ConfigReq from the ECCB. the ECCB
An invalid message response When the cell number of the

is sent when the cell number of message received from the
RLCB_ECCB_INV
2080 0x0820 the message received from the ECCB is greater than the
ALID_ CELLNUM
ECCB is greater than the maximum cell number
maximum cell number defined. defined

is sent when the cell When the cell corresponding
RLC_ECMB_CELL
2081 0x0821 corresponding to the message to the message received
_IS_ IDLE
received from the ECCB is from the ECCB is idle
idle.

Value Call Release

DEC HEX Cause
The call ID of the message

When the call ID of the
received from the ECCB is not
RLCB_ECCB_INV message received from the
2082 0x0822 the value within the defined
ALID_ CALL_ID ECCB is outside the defined
range, respond that the
range
message is not correct.

When the number of RBs in
RLCB_ECCB_NU is sent when the number of
2083 0x0823 the message received from
MRB_ ZERO RBs in the message received
the ECCB is zero
from the ECCB is zero.

When the number of RBs in
RLCB_ECCB_NU is sent when the number of RB
the message received from
2084 0x0824 MRB_ of the message received from
the ECCB is greater than the
OVER_MAXRB the ECCB is greater than the
maximum value defined
maximum value defined.

When the poll retransmit
is sent when the poll retransmit
timer in the message
ECCB_RLC_INVAL timer value of the message
2085 0x0825 received from the ECCB is
ID_T_ POLL received from the ECCB is
greater than the maximum
greater than the maximum
value defined
value defined.

When the poll pdu in the
is sent when the poll pdu value
ECCB_RLC_INVAL message received from the
2086 0x0826 of the message received from
ID_ POLL_PDU ECCB is greater than the
the ECCB is greater than the
maximum value defined.

When the poll byte in the
is sent when the poll byte
2087 0x0827 value of the message received
ALID_ POLL_BYTE ECCB is greater than the
from the ECCB is greater than
the maximum value defined.

When ‘max Retx’ in the
is sent when the max Retx
2088 0x0828 value of the message received
ALID_ MAX_RETX ECCB is greater than the
from the ECCB is greater than

When the ‘sn length’ in the
RLCB_ECCB_INV is sent when the sn Length
message received from the
2089 0x0829 ALID_ value of the message received
ECCB is greater than the
SN_LENGTH from the ECCB is greater than

RLCB_ECCB_IVAL When the RB in the
is sent when there is no
ID_ message received from the
2090 0x082A mapping value for the RB
NUM_RB_UNMAT ECCB has no mapping
value of the message received
CH value
from the ECCB.

Value Call Release

DEC HEX Cause

RLCB_ECCB_CAL When the call ID in the
is sent when the call ID status
2091 0x082B L_IS_ message received from the
of the message received from
NOT_ACTIVE ECCB is not active
the ECCB is not ACTIVE.
When the cell call ID of the

When the cell call ID in the
2092 0x082C ALID_ ECCB is not within the defined
ECCB is outside the defined
CELLCALL_ID range, respond that the
range
message is not correct.

When the ‘delete flag’ in the
RLCB_ECCB_INV is sent when the ‘delete flag’ in
2093 0x082D ALID_ the message received from the
DELETE_FLAG ECCB is outside the defined
range
range.

RLCB_ECCB_INV When the ‘delete numcall’ in
is sent when the ‘delete
ALID_ the message received from
2094 0x082E numcall’ in the message
DELETE_NUMCAL the ECCB is outside the
received from the ECCB is
L defined range
outside the defined range.

RLCB_ECCB_INV When the ‘T reorder’ in the
is sent when the ‘T reorder’ in
ALID_ message received from the
0x082F the message received from the
MAX_T_REORDE ECCB is outside the defined
R range
range.
2095
RLCB_ECCB_INV When the ‘T status prohibit’
is sent when the ‘T status
ALID_ in the message received
0x0830 prohibit’ in the message
MAX_T_STATUS_ from the ECCB is outside
received from the ECCB is
PROHIBIT the defined range
outside the defined range.

When the ‘pcch cfg T’ in the
RLCB_ECCB_INV is sent when the ‘pcch cfg T’ in
2096 0x0831 ALID_ the message received from the
PCCH_CFG_T ECCB is outside the defined
range
range.

When the ‘pcch cfg mode
RLCB_ECCB_INV is sent when the ‘pcch cfg
period coefficient’ in the
ALID_ mode period coefficient’ in the
2097 0x0832 message received from the
PCCH_CFG_MOD message received from the
_ PERIOD_COEFF ECCB is outside the defined
range
range.

When the ‘pcch cfg nB’ in
RLCB_ECCB_INV is sent when the ‘pcch cfg nB’
2098 0x0833 ALID_ in the message received from
the ECCB is outside the
PCCH_CFG_NB the ECCB is outside the
defined range
defined range.

Value Call Release

DEC HEX Cause

When new connections are
is sent if new connections are
C_RLCB_ECCB_L not allowed due to
not allowed due to insufficient
2099 0x0834 ACK_ insufficient RBs that can be
RBs that can be allocated to
OF_NUMOFRB allocated to the message
the message received from the
received from the ECCB
ECCB.
An invalid message response When new connections are

RLCB_ECCB_DL_ is sent if new connections are not allowed due to
LACK_ not allowed due to insufficient insufficient AMD window
2100 0x0835
OF_AMDWINDOW AMD window pools that can be pools that can be allocated
_POOL allocated to the message to the message received
received from the ECCB. from the ECCB

When the ‘qci’ in the
is sent when the ‘qci’ in the
ALID_ QCI_VALUE ECCB is outside the defined
range
range.

When the ‘rlc mode’ in the
is sent when the ‘rlc mode’ in
2102 0x0837 the message received from the
ALID_ RLC_MODE ECCB is outside the defined
range
range.

RLCB_ECCB_UL_ When there are not enough
is sent if there are not enough
NO_ window tag pools that can
2103 0x0838 window tag pools that can be
MORE_WIN_TAG_ be allocated to the message
allocated to the message
POOL received from the ECCB
received from the ECCB.

When the ‘loch type’ in the
RLCB_ECCB_INV is sent when the ‘loch type’ in
2104 0x0839 ALID_ the message received from the
LOCH_TYPE ECCB is outside the defined
range
range.

When the ‘control type’ in
RLCB_ECCB_INV is sent when the ‘control type’
2106 0x083A ALID_ in the message received from
the ECCB is outside the
CONTROL_TYPE the ECCB is outside the
defined range
defined range.

When the ‘num Call’ in the
is sent when the ‘num Call’ in
2107 0x083B the message received from the
ALID_ NUM_CALL ECCB is outside the defined
range
range.

RLCB_ECCB_INV When the ‘cell Call Id’ and
is sent when the ‘cell Call Id’
ALID_ ‘CallID’ in the message
2108 0x083C and ‘CallID’ in the message
CALLID_UNMATC received from the ECCB do
received from the ECCB do
H not match
not match.

Value Call Release

DEC HEX Cause
An error code is sent when the

When the config request
tPollRetransmit timer value
RLCB_ECCB_INV sent to the RLC from the
within the Config Request
2109 0x083D ALID_ ECCB, i.e., the call setup
received from the ECCB (i.e.,
POLL_RETX message has an invalid
the call setup message) is
‘tPollRetransmit’ timer
incorrect.

When the ‘qci’ in the
RLCB_ECCB_NOT is sent when the ‘qci’ in the
2110 0x083E message received from the
_ EQUIPPED_QCI message received from the
ECCB is not in ‘equip’ status
ECCB is not in ‘equip’ status.

RLCB_ECCB_UL_ When there are not enough
is sent if there are not enough
NO_ call pools that can be
2111 0x083F call pools that can be allocated
MORE_CALL_POL allocated to the message
to the message received from
L received from the ECCB
the ECCB.

RLC_EMPTY_MS When the message received
G from the RLC is NULL
RLC is NULL.
When the message received
RLC_UNKNOWN_ message received from the
2177 0x0881 contains an ID that the RLC
MSG_ID RLC contains an unknown
is not allowed to receive
message ID.
When the RLC received a

RLC_INVALID_DA message that is either
2178 0x0882 size of the message received
TA_LEN greater than 8 Kbytes or less
from the RLC is incorrect.
than zero
When the RLC downlink

An error code is sent when no
RLC_NO_RSP_FR does not respond to the
2179 0x0883 response message is received
OM_DL message received from the
from the RLC downlink.
ECMB and ECCB
When the RLC uplink does

RLC_NO_RSP_FR not respond to the message
2180 0x0884 response message is not
OM_UL received from the ECMB
received from the RLC uplink.
and ECCB
When the RLC downlink and

An error code is sent when no
RLC_NO_RSP_FR uplink do not respond to the
2181 0x0885 response message is received
OM_ DLUL message received from the
from the RLC downlink/uplink.
ECMB and ECCB

When the RLC uplink
RLC_RX_BEFORE RLC uplink receives a
2182 0x0886 receives a signaling
_RLC_ READY signaling message before it is
message before it is ready
up and running properly.

transaction ID exceeds the When an invalid transaction
RLC_INVALID_RL
specified range while the RLC ID is found during the
2183 0x0887 C_
processes the message signaling process in the RLC
TRANSACTION_ID
received from the ECCB and for internal purposes
ECMB

Value Call Release

DEC HEX Cause
An error code is sent when a

When a response is sent
reply for the signaling
RLC_INVALID_CO again after the RLC
2184 0x0888 message already processed
NTEXT signaling block completes
by the RLC is received from
the process
the RLC downlink.

When the signaling
RLC_RLC_CONTE number of signaling message
2185 0x0889 messages received exceed
XT_FULL received exceeds the RLC
the RLC capacity
capacity.
RLCB_ERROR_RL An error code is sent if the
When the RLC cannot
2186 0x088A C_ RLC cannot process the ‘cell
process the ‘cell num’
CONTEXT_FULL num.’
When processing all
MAC_INVALID_MS A undefined Msg ID is
2304 0x0900 ECCB/ECMB MAC
GID received.
messages
When processing all
MAC_INVALID_SE An undefined SetupType is
2305 0x0901 messages that contain
TUPTYPE received.
‘SetupType’
When processing
MAC_INVALID_CA The Call Cell ID received is
2306 0x0902 msgCmacPhyConfigReq_ty
LL_CELLID outside the allowed range.
pe
MAC_INVALID_PA A parameter received is When processing all config
2307 0x0903
RAMETER outside the allowed range. messages.
The RB cannot be allocated When setting the logical
MAC_INSUFFICIE due to the insufficient MACB channel within
2308 0x0904
NT_ RESOURCE internal resource required to msgCmacPhyConfigReq_ty
manage the RB. pe
When setting the logical
A reconfig/delete request is channel reconfig/delete
MAC_NOT_ASSIG
2309 0x0905 received on the RB that is not within
NED_RB
allocated. msgCmacPhyConfigReq_ty
pe
When processing
A config/delete request is config/delete messages
MAC_NOT_ASSIG
2310 0x0906 received on the UE that is not other than
NED_UE
allocated. msgCmacPhyConfigReq_ty
pe
The call setup message
MACB_NOT_ASSI channel within
2312 0x0908 received does not have the
GN_SRB1 msgCmacPhyConfigReq_ty
SRB1 setup.
pe
The RB number within the channel within
MACB_INVALID_R
2313 0x0909 Logical Channel Config msgCmacPhyConfigReq_ty
B_CONFIG
exceeds the maximum vaule pe/msgCmacPhyReconfigC
ommit_type
When processing all
MACB_INVALID_C The cell corresponding to the
2314 0x090A ECCB/ECMB MAC
ELL_ID message received is idle.
messages
When the call ends without
4095 0x0FFF NO_FAULT The call ends successfully.
any failures

CHAPTER 4. References
 https://Systems.samsungwireless.com/
o Network Vision > Publications > Sprint > 4G RAN > Manuals
 430 LTE eNB Maintenance Troubleshooting Manual
 410 MMBS Operational Manual
 LTE standard documents: 3GPP TS 36 series

Samsung Telecommunications
America (STA)
©2010 Samsung Electronics Co., Ltd.
All rights reserved.
Information in this manual is proprietary to SAMSUNG

Electronics Co., Ltd.
No information contained here may be copied, translated,

transcribed or duplicated by any form without the prior written
consent of SAMSUNG.
Information in this manual is subject to change without notice.
© SAMSUNG Electronics Co., Ltd. 1

LTE Optimization Guideline

Uploaded by

Copyright:

Available Formats

LTE Optimization Guideline

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LTE Optimization Guideline

Uploaded by

Copyright:

Available Formats

819 LTE Optimization

This manual is proprietary to SAMSUNG Electronics Co., Ltd. and is protected by

No information contained herein may be copied, translated, transcribed or duplicated for

For questions on the manuals or their content, contact

©2012 SAMSUNG Electronics Co., Ltd. All rights reserved

Document Content and Organization

This manual contains the following:

CHAPTER 1. LTE Optimization Process Flow

CHAPTER 2. LTE Optimization Practices

CHAPTER 3. Call Release Cause

This chapter describes the call release cause.

This chapter includes reference documents.

2012 © SAMSUNG Electronics Co., Ltd. i

1.0 11. 2012. First Edition Abhishek Warhadkar

© SAMSUNG Electronics Co., Ltd. ii

Revision History .......................................................................................................................................ii

CHAPTER 1. LTE Optimization Process Flow 2-1

1.1 Site Level Optimization ......................................................................................................... 2-1

1.2 Cluster Level Optimization+.................................................................................................. 2-2

1.3 Market level Optimization...................................................................................................... 2-5

CHAPTER 2. LTE Optimization Practices 2-1

2.1 Coverage Improvement ......................................................................................................... 2-1

2.1.1 Techniques to improve coverage ............................................................................................ 2-1

2.2 Interference Control............................................................................................................... 2-4

2.3 LTE Handover Optimization .................................................................................................. 2-9

2.3.1 Active mode handover ............................................................................................................. 2-9

2.4 EUTRAN and CDMA2000 Handover ................................................................................... 2-16

2.5 RAN Parameters .................................................................................................................. 2-21

2.5.1 Physical Cell Identity ..............................................................................................................2-21

2.6 e-NodeB - Control Parameters ............................................................................................ 2-23

2.7 Parameter Reference Guide ................................................................................................ 2-23

2.8 Relevant Documents and Processes ................................................................................. 2-23

CHAPTER 3. Call Release Cause 3-24

CHAPTER 4. References 4-1

© SAMSUNG Electronics Co., Ltd. iii

Figure 1: Site level testing process flow .................................................................................... 2-2

© SAMSUNG Electronics Co., Ltd. iv

CHAPTER 1. LTE Optimization

1.1 Site Level Optimization

© SAMSUNG Electronics Co., Ltd. 2-1

Figure 1: Site level testing process flow

1.2 Cluster Level Optimization+

© SAMSUNG Electronics Co., Ltd. 2-2

eNB Inter eNB eNB

HO point Intra eNB

Figure 2: Cluster Drive testing scenario

Figure 3: LTE Cluster Optimization Process Flow

© SAMSUNG Electronics Co., Ltd. 2-3

Figure 4: LTE Optimization Practices

© SAMSUNG Electronics Co., Ltd. 2-4

1.3 Market level Optimization

© SAMSUNG Electronics Co., Ltd. 2-5

CHAPTER 2. LTE Optimization

2.1 Coverage Improvement

2.1.1 Techniques to improve coverage

© SAMSUNG Electronics Co., Ltd. 2-1

to no harm should be maintained while implementing change in tilt or azimuth. In other

Cell Selection process

Cell Selection Criteria

© SAMSUNG Electronics Co., Ltd. 2-2