819 LTE Optimization
Engineering Guideline
COPYRIGHT This manual is proprietary to SAMSUNG Electronics Co., Ltd. and is protected by copyright. No information contained contained herein herein may be copied, translated, translated, transcribed or or duplicated for for any commercial commercial purposes or disclosed to the third party in any form without the prior written consent of SAMSUNG 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
[email protected]
©2012 SAMSUNG Electronics Electronics Co., Co., Ltd. All rights 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, improvement, interference control, LTE handover optimization, EUTRAN/CDMA2000 EUTRAN/CDMA2000 Handover, RAN parameters, eNodeB control parameters parameters and parameter parameter reference reference guide.
CHAPTER 3. Call Release Cause This chapter describes the call release cause.
CHAPTER 4. References This chapter includes reference documents. documents.
2012 © SAMSUNG Electronics Co., Ltd.
i
819 LTE Optimization Engineering Guideline
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 Warhadkar
Chapter 4 References
© SAMSUNG Electronics Co., Ltd.
ii
819 LTE Optimization Engineering Guideline
TABLE OF CONTENTS Revision History ........................................... ...................... ........................................... ............................................ ........................................... ........................................... ........................... .....ii
CHAPTER 1. LTE Optimization Optimi zation 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 Optimi zation 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 Active mode mode handov handover er ........ ............ ........ ........ ........ ........ ........ ....... ....... ........ ....... ....... ........ ....... ....... ........ ........ ........ ........ ........ ........ ........ ........ ........ ....... ....... ........ ...... 2-9 2.3.2 Idle Mode Handover .............................................................................................................. 2-14
2.4
EUTRAN and CDMA2000 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
CHAPTER 4. References
3-24
4-1
\
© SAMSUNG Electronics Co., Ltd.
iii
819 LTE Optimization Engineering Guideline
LIST OF FIGURES Figure 1: Site level t esting 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
819 LTE Optimization Engineering Guideline
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 t he 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
819 LTE Optimization Engineering Guideline
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 f uture 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.
© SAMSUNG Electronics Co., Ltd.
2-2
819 LTE Optimization Engineering Guideline
Iperf/FTP servers
EPC eNBmonitoring tool
Test UEs `
Pre-determinedroute
`
eNB
IntraeNB HOpoint
`
Iperf/ftp clients
eNB
IntereNB HOpoint `
IntraeNB HOpoint
IntraeNB HOpoint
Testequipment invehicle
Figure 2: Cluster Drive testing scenario
Figure 3: LTE Cluster Optimization Process Flow
© SAMSUNG Electronics Co., Ltd.
2-3
819 LTE Optimization Engineering Guideline
Examples of major KPIs included in cluster level optimization testing are as fol lows: 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 phys ical © SAMSUNG Electronics Co., Ltd.
2-4
819 LTE Optimization Engineering Guideline
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.
© SAMSUNG Electronics Co., Ltd.
2-5
819 LTE Optimization Engineering Guideline
CHAPTER 2. Practices
LTE Optimization
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
© SAMSUNG Electronics Co., Ltd.
2-1
819 LTE Optimization Engineering Guideline
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 © SAMSUNG Electronics Co., Ltd.
2-2
819 LTE Optimization Engineering Guideline
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 EUTRAN 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.
© SAMSUNG Electronics Co., Ltd.
2-3
819 LTE Optimization Engineering Guideline
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. This specifies the duration for evaluating allowed amount of cell reselection(s). This specifies the maximum number of cell reselections to enter medium mobility state. This specifies the maximum number of cell reselections to enter high mobility state. This specifies the additional time period before the UE can enter normal-mobility.
TCRmax NCR_M NCR_H TCRmaxHyst
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 SCFDMA 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 t wo 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 hi gh 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
© SAMSUNG Electronics Co., Ltd.
2-4
819 LTE Optimization Engineering Guideline
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
© SAMSUNG Electronics Co., Ltd.
2-5
819 LTE Optimization Engineering Guideline
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
© SAMSUNG Electronics Co., Ltd.
2-6
819 LTE Optimization Engineering Guideline
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
© SAMSUNG Electronics Co., Ltd.
2-7
819 LTE Optimization Engineering Guideline
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
1 to 128 UL TARGET IOT (step size : 0.25dB)
Default
Description
32 (8dB)
The desired IOT (interference over thermal) from neighboring cells used for the ICIC Procedure as explained below Interference overload indicator(IOI) is a signaling to the neighboring cells to indicate the interference status (high/medium/low) for ICIC operation
UL IOI THRESHOLD STEP
1 to 128 (step size: 0.25dB)
2 IOI is set as: (0.5dB) If current IOT < (ulTargetIot – ulIoiThresholdStep ), IOI = 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
© SAMSUNG Electronics Co., Ltd.
2-8
819 LTE Optimization Engineering Guideline
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
o
Estimation based on UE‟s channel condition (CQI, RSRP etc.)
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
2.3
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.
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. © SAMSUNG Electronics Co., Ltd.
2-9
819 LTE Optimization Engineering Guideline
o
o
o
Event A1
Serving becomes better than a threshold
Used to deactivate Gap Measurements
Event A2
Serving becomes worse than a threshold
Used to activate Gap Measurements
Event A3
o
Neighbor becomes offset better than the Serving Used to trigger Intra-FA Handoff
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. © SAMSUNG Electronics Co., Ltd.
2-10
819 LTE Optimization Engineering Guideline
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 )
© SAMSUNG Electronics Co., Ltd.
2-11
819 LTE Optimization Engineering Guideline
LSM Command
LSM Parameter
A3_Offset
Unit
0.5db
-30db to +30db
Default
4
Time_To_Trigger ms
0,40,64,80,100,128, 160,256,320,480,512,640,1024,1280,2560 480ms ,5120
Trigger_Quantity
RSRP or RSRQ
RSRQ
Report_Quantity
Same as Trigger Quantity Or Both
Both (RSRQ & RSRP)
Report_Interval
120ms, 240ms, 480ms, 640ms, 1024ms, 2048ms, 5120ms, 10240ms, 1min, 6min, 12min, 30min, 60min
240ms
1,2,4,8,16,32,64, infinity
8
RTRV-EUTRAA3-CNF
Report_Amount
CHG-MEASFUNC
Range
S_Measure
© SAMSUNG Electronics Co., Ltd.
ms
*RSRP 0 ~ 97 Range
60
2-12
819 LTE Optimization Engineering Guideline
LSM Command
LSM Parameter
Range/Size
Default
fc0, fc1, fc2, fc3, fc4, fc5, Rsrp_Filter_Coefficient fc6, fc7, fc8, fc9, fc11, fc13,
4
fc15, fc17, fc19
CHG-QUANTEUTRA
fc0, fc1, fc2, fc3, fc4, fc5, rsrqFilterCoefficient
fc6, fc7, fc8, fc9, fc11, fc13, fc15, fc17, fc19
4
Details
The RSRP measurement is filtered by the UE before sending the measurement report using the following formula. M is the latest measured result, F is the filtered result and the factor “a” is based on the filter coefficient. More the coefficient the new filtered result is influenced more by the previous filtered value than the current measured value. a = 1/2(k/4) The RSRQ measurement is filtered by the UE before sending the measurement report using the following formula. M is the latest measured result, F is the filtered result and a is based on the filter coefficient. More the co-efficient the new filtered result is influenced 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 t o 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
© SAMSUNG Electronics Co., Ltd.
2-13
819 LTE Optimization Engineering Guideline
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 t he 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
© SAMSUNG Electronics Co., Ltd.
2-14
819 LTE Optimization Engineering Guideline
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 i s 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 Lower HO Quality Calculation HO-to-Black-Cell Ratio Calculation
Change from NRT to HO Black List Restore from HO Black List to NRT
(3) CLI command (NO HO = ON or OFF)
Figure 11: Operational procedure for Neighbor Relation Optimization
© SAMSUNG Electronics Co., Ltd.
2-15
819 LTE Optimization Engineering Guideline
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
RRC B2 Event Connection Reconfiguration
© SAMSUNG Electronics Co., Ltd.
Parameter
Description
b2Threshold1Rsrp
RSRP threshold1 used for triggering the EUTRA measurement report for CDMA2000 HRPD Event B2.
2-16
819 LTE Optimization Engineering Guideline
b2Threshold1Rsrq
b2Threshold2Cdma2000
RSRQ threshold1 used for triggering the EUTRA measurement report for CDMA2000 HRPD Event B2. CDMA2000 threshold 2 used for triggering the inter-RAT CDMA2000 measurement report for CDMA2000 HRPD Event B2.
qOffsetFreq hysteresisB2
timeToTriggerB2
reportIntervalB2
reportAmountB2
maxReportCellsB2
triggerQuantityB2
RRC A2 Event Connection Reconfiguration
a2ThresholdRsrp
a2ThresholdRsrq
reportIntervalA2
triggerQuantityA2
© SAMSUNG Electronics Co., Ltd.
Hysteresis applied to entry and leave condition of CDMA2000 HRPD Event B2. 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. The reporting interval of a measurement report for CDMA2000 HRPD Event B2. The number of measurement reports for CDMA2000 HRPD Event B2. The maximum number of cells included in a measurement report for CDMA2000 HRPD Event B2. Quantity that triggers the Event B2 measurement The trigger can be set for either RSRP or RSRQ and is only applicable on threshold 1. A2 event is triggered when source becomes worse than the configured RSRP threshold (Refer to standard 36.133 for RSRP Report mapping) Primary RSRQ threshold value for eventA2. Used only when triggerQuantityA2Prim is set to RSRQ. Determines the reporting interval of a measurement report for Event A2 A1 event is triggered when source becomes worse than the configured RSRQ threshold ((Refer to
2-17
819 LTE Optimization Engineering Guideline
hysteresisA2
timeToTriggerA2
reportAmountA2
standard 36.133 for RSRQ Report mapping) Hysteresis applied to entry and leave conditions of Event A2 The timeToTrigger value is the period of time that must be met for the UE to trigger a measurement report for Event A2 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
reportQuantityA2
filterCoefficientEUtraRsrp
filterCoefficientEUtraRsrq
RRC A1 Event Connection Reconfiguration © SAMSUNG Electronics Co., Ltd.
a1ThresholdRsrp
The maximum number of cells included in a measurement report for Event A2. 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. 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. 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. A1 event is triggered when source becomes better than the configured RSRP 2-18
819 LTE Optimization Engineering Guideline
a1ThresholdRsrq
triggerQuantityA1
reportQuantityA1
maxReportCellsA1
hysteresisA1
timeToTriggerA1
reportIntervalA1
reportAmountA1
SIB8
systemTimeInfo
timeAndPhaseSynchCritical
CellReselection bandClass Parameters CDMA 2000 cellReselectionPriority
threshXHigh threshXLow
© SAMSUNG Electronics Co., Ltd.
threshold ( Actual Threshold = Parameter - 140, 36.133 standards) dbm A1 event is triggered when source becomes better than the configured RSRQ threshold (Refer to 36.133 standard for RSRP Report mapping) Determines whether Event A1 is triggered based on RSRP or RSRQ criteria. 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. The maximum number of cells included in a measurement report for Event A1. Hysteresis applied to entry and leave conditions of Event A1. The timeToTrigger value is the period of time that must be met for the UE to trigger a measurement report for Event A1 Determines the reporting interval of a measurement report for Event A1 Determines the number of measurement reports UE needs to send when Event A1 criteria is met Identifies the CDMA-eHRPD frequency band class in which the carrier frequency can be found Reselection priority of the cell in the eNB. The range is 0-7, where 0 indicates low, and 7 high in priority.
ThreshXHigh of CDMA2000 HRPD band class DB. ThreshXLow of CDMA2000 HRPD band class DB.
2-19
819 LTE Optimization Engineering Guideline
tReselectionSfUsageHRPD
tReselectionHRPD
tReselectionSfHighHRPD
tReselectionSfMediumHRPD
searchWindowSize
© SAMSUNG Electronics Co., Ltd.
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. TReselctionHRPD included in the HRPD Reselection information sent to SIB8. The default is 0, and can be changed by the operator. Value by which parameter tReselectionCdmaHrpd is multiplied if the UE is in a high mobility state as defined in 3GPP TS 36.304 TReselectionSfMediumHRPD included in the HRPD Reselection information sent to SIB8. The size of the search window in the eNB.
2-20
819 LTE Optimization Engineering Guideline
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
(1)
3 N ID
(2)
N ID 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
© SAMSUNG Electronics Co., Ltd.
2-21
819 LTE Optimization Engineering Guideline
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 configuration 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
LSM Parameter type
N CS value Unrestricted set 0 13 15 18 22 26 32 38 46 59 76 93 119 167 279 419
Restricted set 15 18 22 26 32 38 46 55 68 82 100 128 158 202 237 -
Parameter
Range
Root_sequence_Index
0 ~ 837 Planned
Zero_correl_zone_config 0 ~ 15 CHG-PRACHCONF Prach_Config_Index
© SAMSUNG Electronics Co., Ltd.
0 ~ 63
Default
12 3
(Alpha)
4
(Beta)
5
(Gamma)
2-22
819 LTE Optimization Engineering Guideline
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 Parameter, MSG4HARQ, eHRPD redirection parmeters
Connection success rate
RSRP, SINR
Connection drop rate
RSRP, SINR, UL BLER, DL BLER
Handover Success Rate
RSRP, SINR
Handover Latency
HO Interruption time
DL Throughput
RSRP, SINR, DL MCS, DL RB, PDSCH TP, RI, CQI, DL BLER
DL ICIC
UL Throughput
RSRP, SINR, UL MCS, UL RB, PUSCH TP, CQI, UL BLER, PDCCH BLER
UL ICIC
Check call release cause X2 link status, Neighbor list, A3 offset, Smeasure, Cell Individual offset, ANR, PCI collision Backhaul delay, X2 interface
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
© SAMSUNG Electronics Co., Ltd.
2-23
819 LTE Optimization Engineering Guideline
CHAPTER 3. Call Release Cause
The Call Release Cause is explained below: Value DEC
256
HEX
0X0100
Call Release Cause
Description
Collection Time
S1AP_CauseRadio Network_ unspecified
A failure occurs in GW during the handover, or the handover preparation fails if the MME cannot process the handover.
When the target eNB receives the Handover Cancel message from the source eNB.
283
0x011B
S1AP_invalid_qos_ The action fails due to combination invalid QoS combination.
- When gbrType of QCI received within E_RABLevelQoSParameters IE of the Initial Context Setup Request message is GBR but gbrQosInformation received is not present. - When gbrType of QCI received within E_RABLevelQoSParameters IE of the E_RAB Setup Request message is GBR but gbrQosInformation received is not present. - When gbrType of QCI received within E_RABLevelQoSParameters IE of the E_RAB Modify Request message is GBR but gbrQosInformation received is not present.
307
0x0133
S1AP_authenticatio n_failure
The action occurs due to the authentication failure.
Used in the UE context release when the call fails due to the authentication failure.
566
0X0236
X2AP_CauseMisc_ unspecified
Default X2 cause in the eNB.
When the target eNB receives the Handover Cancel message from the source eNB.
RRC_TMOUT_ rrcConnectionSetu p
The RRC Connection Setup Complete message is not received after the RRC Connection Setup message is sent to the UE.
When timRrcConnectionSetup message is received because the timer is ended that waits until the RRC Connection Setup Complete message is received after sending the RRC Connection Setup message to the UE
768
0X0300
© SAMSUNG Electronics Co., Ltd.
3-24
819 LTE Optimization Engineering Guideline
Value DEC
769
HEX
0X0301
Call Release Cause
RRC_TMOUT_ rrcConnectionReco nfig
Description
Collection Time
The RRC Connection Reconfiguration Complete message is not received after the RRC Connection Reconfiguration message is sent to the UE.
When timRrcConnectionReconfig message is received due to the timer termination while waiting to receive the RRC Connection Reconfiguration Complete message after the RRC Connection Reconfiguration message is sent to the UE
- SB2DB State: sending Initial Context Setup Failure - Other State: sending UE Context Release Request
- SB2DB state: Initial Context Setup Failure - INCELLue state: UE Context Release Request - REESTue2 state: UE Context Release Request - GAPprepare state: UE Context Release Request - ANRprepare state: UE Context Release Request
770
771
772
775
0X0302
0X0303
0X0304
0X0307
The RRC Connection Reestablishment Complete message is not received after the RRC Connection Reestablishment message is sent to the UE.
When timRrcConnectionReEstablish message is received due to the timer termination while waiting to receive the RRC Connection Reestablishment Complete message after the RRC Connection Reestablishment message is sent to the UE
RRC_TMOUT_ rrcSecurityModeCo mmand
The Security Mode Complete message is not received after the Security Mode Command message is sent to the UE.
When the timRrcSecurityModeCommand message is received due to the timer termination while waiting to receive Security Mode Complete message after the Security Mode Command message is sent to the UE
RRC_TMOUT_ rrcUeCapabilityEnq uiry
The UE Capability Information message is not received after the UE Capability Enquiry message is sent to the UE.
When the timRrcUeCapabilityEnquiry message is received due to the timer termination while waiting to receive the UE Capability Information message after the UE Capability Enquiry message is sent to the UE
RRC_TMOUT_intra _ HandoverCmdCom plete
The RRC Connection Reconfiguration Complete message is not received after the RRC Connection Reconfiguration message is sent to the UE during the Intra handover.
When the timer ends while waiting to receive the RRC Connection Reconfiguration Complete message after the RRC Connection Reconfiguration message is sent to the UE during the intra eNB handover
RRC_TMOUT_ rrcConnectionReEs tablish
© SAMSUNG Electronics Co., Ltd.
3-25
819 LTE Optimization Engineering Guideline
Value DEC
776
777
787
HEX
0X0308
0X0309
0X0313
Call Release Cause
The RRC Connection Reconfiguration Complete message is not RRC_TMOUT_inter received after the RRC _ Connection X2HandoverCmdC Reconfiguration omplete message is sent to the UE during the X2 handover. The RRC Connection Reconfiguration Complete message is not RRC_TMOUT_inter received after the RRC _ Connection S1HandoverCmdC Reconfiguration omplete message is sent to the UE during the S1 handover.
S1AP_TMOUT_ s1InitialContextSet up
S1AP_TMOUT_ 790
0X0316
s1PathSwitch
S1AP_TMOUT_
792
794
0X0318
0x031A
s1RelocOverall
S1AP_TMOUT_ s1MMEStatusTrans fer X2AP_TMOUT_
804
805
0x0324
0x0325
Description
x2RelocOverall
X2AP_TMOUT_ x2SNStatusTransfe r
© SAMSUNG Electronics Co., Ltd.
Collection Time
When the timer ends while waiting to receive the RRC Connection Reconfiguration Complete message after the RRC Connection Reconfiguration message is sent to the UE during the intra X2 handover
When the timer ends while waiting to receive the RRC Connection Reconfiguration Complete message after the RRC Connection Reconfiguration message is sent to the UE during the intra S1 handover
When the The Initial Context Setup timS1InitialContextSetup message Request message is not is received due to the timer received after the Initial termination while waiting to UE message is sent to receive the Initial Context Setup the MME. Request message after the Initial UE message is sent to the MME When the timS1PathSwitch The Path Switch Request message is received due to the Acknowledge message is timer termination while waiting to not received after the receive the Path Switch Request Path Switch Request Acknowledge message after the message is sent to the Path Switch Request message is MME. sent to the MME 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 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 Transfer message is not received after the eNB Status Transfer message is sent to the MME.
When the timer ends while waiting for the MME Status Transfer message after the eNB Status Transfer message is sent to the MME
The UE Context Release message is not received from the Target eNB because the handover is complete after the Handover Acknowledge message is received from the Target eNB.
When the timX2RelocOverall message is received due to the timer termination while waiting to receive the UE Context Release message after the Handover Acknowledge message is received from the target eNB
The MME Status Transfer message is not received after the eNB Status Transfer message is sent to the MME.
When the timer ends while waiting for the MME Status Transfer message after the eNB Status Transfer message is sent to the MME
3-26
819 LTE Optimization Engineering Guideline
Value DEC
HEX
Call Release Cause
Description
Collection Time When the timInternalResourceSetup message is received due to the timer termination while waiting to receive the response after the SetupReq message is sent to assign resources to the protocol blocks within the eNB
816
0X0330
RRC_TMOUT_ internalResourceSe tup
The response message is not received after the SetupReqe message is sent for setting the resource for the internal protocol blocks of the eNB.
- SB2DB state: Initial Context Setup Failure - DB2DBScomplete state: UE Context Release Request, E_RAB Setup Response - 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
818
0X0332
After sending the msgCpdcpSecurityContr RRC_TMOUT_ ol message to the PDCB, internalSecurityCon cannot receive the trol msgCpdcpSecurityContr olSuccess message
When receiving the timInternalSecurityControl message because the timer is ended that waits until the msgCpdcpSecurityControlSucces s message is received after sending the msgCpdcpSecurityControl message to the PDCB - SB2DBint state-SB2DBciph state
820
821
0X0334
0X0335
RRC_TMOUT_ internalForwarding PathSetup
During Handover, after sending the msgCgtpSetupReq message to the GTPB for setting uplink and downlink path, cannot receive the msgCgtpSetupCnf message
During Handover, when the timInternalForwardingPathSetup message is received because the timer is ended that waits until the msgCgtpSetupCnf message is received after sending the msgCgtpSetupReq message to GTPB for setting the uplink, downlink path
RRC_TMOUT_ internalReestablish Control
The msgCrlcControlSuccess or msgCpdcpControlSucces s is not received after the msgCrlcControl, msgCpdcpControl message is sent for RLC, PDCP reestablishment during inter eNB HO.
When the timInternalReestablishControl message is received due to the timer termination while waiting to receive the msgCrlcControlSuccess or msgCpdcpControlSuccess message after the msgCrlcControl or msgCpdcpControl message is sent for RLC, PDCP reestablishment during inter eNB HO
© SAMSUNG Electronics Co., Ltd.
3-27
819 LTE Optimization Engineering Guideline
Value DEC
822
823
HEX
0X0336
0X0337
Call Release Cause
Description
Collection Time
RRC_TMOUT_ internalBufferFlush
The msgCpdcpBufferFlushCn f message is not received after the msgCpdcpBufferFlush message is sent to the PDCB during handover.
When the timInternalBufferFlush message is received due to the timer termination while waiting to receive the msgCpdcpBufferFlushCnf message after the msgCpdcpBufferFlush message is sent to the PDCB during handover
RRC_TMOUT_ internalDataTransfe rStart
The msgCpdcpControlSucces s message is not received after the msgCpdcpControl message is sent.
When the timInternalDataTransferStart message is received due to the timer termination while waiting to receive the msgCpdcpControlSuccess message after the msgCpdcpControl message is sent - INCELLresume state: key refreshing - INTRAresume state: Intra Cell handover - INTERstart_T state: Inter e NB handover - REESTresume1 state: Reestablish
833
0X0341
RRC_USER_INAC TIVITY
UE is in inactive status.
When the msgCmacPhyUserInactivityInd message is received from the MACB. When the timer ends while running the timInternaReestablshTimeToWait timer after the msgCrlcMaxRetransInd message is received from the RLCB The MAC notifies the ECCB of the possible release of the uplink
834
0X0342
RRC_ARQ_MAX_ RE_ TRANSMISSION
After sending only as much as the RLC Max retransmission count, the UE status does not become active for a certain period of time.
835
0X0343
RRC_RADIO_LINK _ FAILURE
The radio link with the UE failed.
© SAMSUNG Electronics Co., Ltd.
3-28
819 LTE Optimization Engineering Guideline
Value DEC
HEX
Call Release Cause
Description The MAC notifies the ECCB of the possible release of the uplink radio link with the UE if it fails to receive the HARQ-ACK/NACK 200 times or more consecutively for the downlink data. If the ECCB is notified by the MAC of being InSync again (HARQ ACK/NACK received 20 times), or if it fails to receive the RRC Connection Reestablishment Request from the UE, the call is released after a time-out (default: 5 seconds).
Collection Time radio link with the UE if it fails to receive the HARQ-ACK/NACK 200 times or more consecutively for the downlink data (msgCmacPhyOutOfSynchInd). If the ECCB is notified by t he MAC of being InSync again (HARQ ACK/NACK received 20 times), or if it fails to receive the RRC Connection Re-establishment Request from the UE, the call is released after a time-out (default: 5 seconds, timInternaReestablshTimeToWait) .
RRC_REEST_FAIL _ INVALID_ STATE
The RRC Connection Reestablishment Request message is received in the invalid state.
When the RRC Connection Reestablishment Request message is received by the incorrect state (SB2DB state), then the RRC Connection Reestablishment Reject message is sent
0X0348
S1AP_RCV_S1_ UECTXTRELEASE CMD_ ABNORMAL_STAT E
The UE Context Release Command is received in the unexpected abnormal state (the cause in the message: normal release, detach, successful handover). The eNB triggers the cause when it receives the UE Context Release Command message including ‘normal release’ in a state that does not involve the Initial Context Setup procedure.
When the cause of the UE Context Release Command received from the MME is: normal_release, detach or successful_handover while the procedure with the MME is not complete
841
0X0349
RRC_RCV_RESET _ REQUEST_FROM _ECMB
The call is released after the Reset Request message is received from the ECMB block.
When the Reset Request message is received from the ECMB block.
842
0X034A
S1AP_RCV_S1_R ESET_ FROM_MME
The call is released by receiving the Reset message from the MME.
When the Reset message is received from the MME
0X034C
S1AP_S1_SCTP_ OUT_OF_SERVIC E
The call is released after the S1 Association changes to ‘out of service.’
When the S1 status in the msgCsctpStatusInd message received from the SCTP is ‘out_of_service’
0X034D
RRC_RCV_CELL_ RELEASE_IND_FR OM_ ECMB
The call is released after the Cell Release Ind message is received
- When the Cell Release Ind is received from the ECMB block due to the CPRI failure
838
840
844
845
0X0346
© SAMSUNG Electronics Co., Ltd.
3-29
819 LTE Optimization Engineering Guideline
Value DEC
846
847
848
849
851
875
876
880
HEX
Call Release Cause
Description
Collection Time
from the ECMB block.
- When the Cell Release Ind is received from the ECMB block due to the DSP failure
0x34E
RRC_DSP_AUDIT _RLC_ CALL_RELEASE
The call remains in the ECCB and MAC, but not in the RLC. This creates a resource mismatch and the call is released.
When the call remains in the ECCB and MAC, but not in the RLC when the msgCdspResourceNotification message is received
0x34F
RRC_DSP_AUDIT _MAC_ CALL_RELEASE
The call remains in the ECCB and RLC, but not in the MAC. This creates a resource mismatch and the call is released.
When the call remains in the ECCB and RLC, but not in the MAC when the msgCdspResourceNotification message is received
RRC_DSP_AUDIT _RLC_ MAC_CALL_RELE ASE
The call is cancelled due to the resource mismatch, because the ECCB has remaining calls but the RLC and the MAC have no call remaining.
When the call remains in the ECCB, but not in the RLC and MAC when the msgCdspResourceNotification message is received
0x351
RRC_SEC_ALGO RITHMS_COMBIN ATION_INVALID
The security algorithm value is received in the Initial Context Setup Request, S1 Handover Request, X2 Handover Request, and S1 UE Context Modification message. The ciphering algorithm should have the null algorithm value if the integrity algorithm supports the null algorithm. Otherwise, the call is released.
When the ciphering algorithm does not have the null algorithm value even if the integrity algorithm supports the null algorithm
0x353
ECCB_RELEASE_ DUE_ TO_ENB_GENERA TED_ REASON
The call is released due to the internal cause of the eNB.
When the relcallall command is executed
0x350
0X036B
RRM_MAX_DRB_ COUNT_ OVER
0X036C
RRM_QOSCAC_F AIL
0X0370
RRM_RBID_FULL
© SAMSUNG Electronics Co., Ltd.
If calls are generated more than the number of DRB that can be accommodated by cell, they are rejected by CAC. If calls with the QoS that cannot be accommodated by cell, they are rejected by CAC. If DRB is generated exceeding the MAX_DRB or MAX_LOGH per call, DRB ID and LOCH ID cannot be assigned.
When DRB ID and LOCH ID are assigned after the Initial Context Setup Request or E-RAB Setup Request message is received When the permission is checked to allow new calls after the Rrc Connection Request or Handover Request message is received. When DRB ID and LOCH ID are assigned after the Initial Context Setup Request or E-RAB Setup Request message is received
3-30
819 LTE Optimization Engineering Guideline
Value DEC
881
888
892
893
898
899
HEX
0x0371
0X0378
Call Release Cause
Description
Collection Time
ECCB_ERRM_BH CAC_FAIL
Occurs when the BH link usage by the QoS (GBR Bearer) exceeds the threshold defined in the PLD.
When the permission is checked to allow new calls after the Rrc Connection Request or Handover Request message is received.
RRM_SRS_MUST _BE_ ASSIGNED
If a new call supports both SRS and DRX, the SRS resources need to assigned in advance to assign the DRX resources but cannot assign the DRX resources because the SRS resource is not assigned.
When assigning the DRX resources if a new call supports both SRS and DRX
0X037C
RRM_CQIPMI_DB _ ABNORMAL
0X037D
RRM_CQIPMI_DB _FULL
0X0382
0X0383
RRM_SPS_DB_AB NORMAL
RRM_SPS_DB_FU LL
The database in the CQI/PMI is abnormal. CQI/PMI resources cannot be assigned to new calls. CQI/PMI resources are all assigned and not available any more.
During SPS resource assignment and cancellation, the SPS resource search is not allowed to exceed the Max value of the SPS resource DB.
SPS resources are all assigned and not available any more.
When assigning CQI/PMI resources
When assigning CQI/PMI resources - When SPS resources are assigned for the QCI 1 existing in the DRB after the Initi al Context Setup Request or E-RAB Setup Request message is received, or the SPS resources are cleared following the DRB release of the QCI 1 - When fnELIB_DecisionDrxSpsConfig is called. - When SPS resources are assigned for the QCI 1 existing in the DRB after the Initi al Context Setup Request or E-RAB Setup Request message is received - When fnELIB_DecisionDrxSpsConfig is called.
900
0X0384
RRM_SPS_ALREA DY_ ASSIGNED
© SAMSUNG Electronics Co., Ltd.
Assigning duplicate resources is not allowed since the SPS resources are already assigned.
- When SPS resources are assigned for the QCI 1 existing in the DRB after the Initi al Context Setup Request or E-RAB Setup Request message is received - When fnELIB_DecisionDrxSpsConfig is called.
3-31
819 LTE Optimization Engineering Guideline
Value DEC
901
903
905
907
908
909
910
919
920
921
HEX
0X0385
Call Release Cause
RRM_SPS_RNTI_ FULL
Description
RNTIs used for the SPS purpose are all assigned and not available any more.
Collection Time - When SPS resources are assigned for the QCI 1 existing in the DRB after the Initial Context Setup Request or E-RAB Setup Request message is received - When fnELIB_DecisionDrxSpsConfig is called.
0X0387
RRM_N1PUCCHA N_REP_ DB_ABNORMAL
n1PucchAnRep resources are all assigned and not available any more.
n1PucchAnRep resources are assigned after the Rrc Connection Request or Handover Request message is received.
0X0389
RRM_N1PUCCHA N_REP_ ALREADY_ASSIG NED
Since there are already assigned resources regarding the N1PUCCHAN_REP on the call, it is not assigned.
When assigning N1PUCCHAN REP resources
0X038B
RRM_N1PUCCH_ DB_ INSUFFICIENT
Cannot initialize because the capacity of N1PUCCH internal resource DB is too small.
When the database for N1PUCCHAN REP resources is initialized
RRM_SR_DB_ABN ORMAL
During SR resource assignment and cancellation, the SR resource search is not allowed to exceed the Max value of the SPS resource DB.
When SR resources are assigned after the Rrc Connection Request or Handover Request message is received, or the SR resources are cleared following the call release
0X038D
RRM_SR_DB_FUL L
SR resources are all assigned and not available any more.
When SR resources are assigned after the Rrc Connection Request or Handover Request message is received
0X038E
RRM_SR_ALREAD Y_ ASSIGNED
Since there are already assigned resources regarding the SR on the call, it is not assigned.
When assigning SR resources
0X0397
RRM_SRS_DB_ ABNORMAL
During SR resource assignment and cancellation, a database search for the SRS resource exceeds the range of resources secured.
When SRS resources are assigned after the Rrc Connection Request or Handover Request message is received, or the SRS resources are cleared following the call release
0X0398
RRM_SRS_DB_FU LL
SRS resources are all assigned.
When SRS resources are assigned after the Rrc Connection Request or Handover Request message is received
0X0399
RRM_SRS_ALREA DY_ ASSIGNED
Since there are already assigned resources regarding the SRS on the call, it is not assigned.
When assigning SRS resources
0X038C
© SAMSUNG Electronics Co., Ltd.
3-32
819 LTE Optimization Engineering Guideline
Value DEC
923
924
925
927
928
930
Call Release Cause
Description
Collection Time
0X039B
RRM_TPC_PUCC H_ RNTI_DB_ABNOR MAL
During TPC PUCCH RNTI resource assignment and cancellation, the TPC PUCCH resource search is not allowed to exceed the Max value of TPC PUCCH resource DB.
When TPC PUCCH resources are assigned after the Rrc Connection Request or Handover Request message is received, or the TPC PUCCH resources are cleared due to the call release
0X039C
RRM_TPC_PUCC H_ RNTI_FULL
TPC PUCCH RNTI resources are all assigned and cannot be assigned further.
When assigning TPC PUCCH resources
0X039D
RRM_TPC_PUCC H_ RNTI_ALREADY_ ASSIGNED
Assigning duplicate resources is not allowed since the TPC PUCCH resources are already assigned.
When TPC PUCCH resources are assigned after the Rrc Connection Request or Handover Request message is received
0X039F
RRM_SPS_MUST_ BE_ ASSIGNED
SPS resources which should be assigned prior to the TPC PUSCH resource assignment are not assigned.
When assigning TPC PUSCH resources
0X03A0
RRM_TPC_PUSC H_ RNTI_FULL
RNTIs used for the TPC PUSCH purpose are all assigned and not available any more.
When assigning TPC PUSCH resources
0X03A2
RRM_TPC_PUSC H_ RNTI_ALREADY_ ASSIGNED
Assigning duplicate resources is not allowed since the TPC PUSCH resources are already assigned.
When TPC PUSCH resources are assigned for the QCI 1 existing in the DRB after the Initi al Context Setup Request or E-RAB Setup Request message is received
The MME in service does not exist.
When the MME overload is controlled after the RRC Connection Request or RRC Connection Setup Complete message is received
If the MME is in Overload state, it cannot accommodate the calls because overloadAction and establishmetCause does not match.
When the MME overload is controlled after the RRC Connection Request or RRC Connection Setup Complete message is received
HEX
RRM_ALL_MME_N OT_ 933
0X03A5 SERVICE
934
0X03A6
RRM_MME_OVER LOAD
0X03A7
RRM_NOT_EXIST _MME
936
0X03A8
The MME to RRM_AVAILABLE_ accommodate new calls MME_NOT_EXIST does not exist.
937
0X03A9
RRM_UE_STMSI_ DUPLICATE
935
© SAMSUNG Electronics Co., Ltd.
In MME Pool, specific MME ID does not exist.
The existing call is released due to the same STMSI value.
When the MME overload is controlled after the RRC Connection Request or RRC Connection Setup Complete message is received When the MME overload is controlled after the RRC Connection Request or RRC Connection Setup Complete message is received When a new call connection has the same sTmsi value for accommodating new calls
3-33
819 LTE Optimization Engineering Guideline
Value DEC
1536
1538
1540
1541
1542
1792
1793
1794
HEX
Call Release Cause
Description
Collection Time - When receiving the msgCgtpSetupFailure as a response to msgCgtpSetupReq - SB2DB state: Initial Context Setup failure - DB2DBScomplete: E_RAB Setup Response, UE Context Release Request - DB2DBRfail: E_RAB Release Response, UE Context Release Request - INTERpath_S: UE Context Release Request - INTERprepare_T: S1 Handover Failure When Gtp Modify fails after the ModifyReq message is received from the ECCB
0X0600
GTP_Setup_Failur e
Use it if there i s response for Gtp setup fail after receiving the SetupReq message from the ECCB.
0X0602
GTP_Modify_Failur e
There is a response for Gtp setup fail after the ModifyReq message is received from the ECCB.
0X0604
GTP_Path_Failure
After the SetupReq message is received from the ECCB, a series of the GTP setup starts: create a GTP tunnel, set a timer to the echo request message to be sent to the dstip of the message, and respond to the E CCB if a response is not received three times within the time limit.
0X0605
A response is sent when the message received from the dst GTP_Not_Support_ peer during the tunnel setup EH has an extension header not supportable by the system.
When the message received from the dst peer has an extension header not supportable by the system
0X0606
GTP_GTP_Error_I nd
Send a response to cancel the call by responding to the ECCB when receiving the Error Indication message from dst peer.
When receiving Error Indication message from dst peer
0x0700
An invalid message response is sent when when the callid of PDCP_Invalid_Calli the downloaded message from d the ECCB is the value of the MAX_USER_ENB or higher.
When the callid of the downloaded message from the ECCB is the value of MAX_USER_ENB or higher
0x0701
PDCP_Invalid_RBi d
The messages are normal if the Rbid is below MAXS_RB when the message downloaded from the ECCB is PDCP_DRB, or below MAX_SRB when it is PDCP_SRB and an invalid message response is sent for all other cases.
When Rbid is above MAX_RB if the message downloaded from the ECCB is PDCP_DRB, and when Rbid is above MAX_SRB if it is PDCP_SRB
PDCP_Invalid_Nu mRb
An invalid message response is sent when the NumRb of the message downloaded from the ECCB is above CI_MAX_RB.
When the NumRb of the message downloaded from the ECCB is sent in the value of CI_MAX_RB or higher
0x0702
© SAMSUNG Electronics Co., Ltd.
3-34
819 LTE Optimization Engineering Guideline
Value DEC
1795
1796
1797
1798
HEX
Call Release Cause
Description
Collection Time
0x0703
PDCP_Invalid_Rlc Mode
An invalid message response is sent when the RLC mode of the message downloaded from the ECCB is invalid.
When the RLC mode of the message downloaded form the ECCB is invalid
0x0704
PDCP_Invalid_Set upType
An invalid message response is sent when the setupType of the message downloaded from the ECCB is invalid.
When the setup Type of the message downloaded form the ECCB is inappropriate value
0x0705
PDCP_Invalid_Cntl Type
An invalid message response is sent when the CntlType of the message downloaded from the ECCB is invalid.
When the CntlType of the message downloaded from the ECCB is the Unknown type
0x0706
PDCP_Invalid_Pdc pSnType
An invalid message response is sent when the SNType of the message downloaded from the ECCB is UM, but not
When the SNType of the message downloaded from the ECCB is UM, but not 7bit or 12-bit
7-bit or 12-bit.
1798
0x0706
PDCP_Invalid_Pdc pSnType
An invalid message response is sent when the SNType of the message downloaded from the ECCB is UM, but not
When the SNType of the message downloaded from the ECCB is UM, but not 7bit or 12-bit
7-bit or 12-bit.
1804
1805
2080
2081
0x0707
0x0708
0x0820
0x0821
PDCP_Invalid_Loc hType
An invalid message response is sent when the logical type of the message downloaded from the ECCB is other than either LOCH_DCCH (for the SRB) or LOCH_DTCH (for the DRB).
When the logical type of the message downloaded from the ECCB is other than either LOCH_DCCH (for the SRB) or LOCH_DTCH (for the DRB)
PDCP_Rohc_Setu p_Failure
Used when responding for the ROHC context setup procedure failure due to lack of memory while receiving ConfigReq from the ECCB.
When the ROHC context setup procedure fails due to lack of memory while receiving ConfigReq from the ECCB
RLCB_ECCB_INV ALID_ CELLNUM
An invalid message response is sent when the cell number of the message received from the ECCB is greater than the maximum cell number defined.
When the cell number of the message received from the ECCB is greater than the maximum cell number defined
RLC_ECMB_CELL _IS_ IDLE
An invalid message response is sent when the cell corresponding to the message received from the ECCB is idle.
When the cell corresponding to the message received from the ECCB is idle
© SAMSUNG Electronics Co., Ltd.
3-35
819 LTE Optimization Engineering Guideline
Value DEC
2082
2083
2084
2085
2086
2087
2088
2089
2090
HEX
Call Release Cause
Description
Collection Time
0x0822
RLCB_ECCB_INV ALID_ CALL_ID
The call ID of the message received from the ECCB is not the value within the defined range, respond that the message is not correct.
When the call ID of the message received from the ECCB is outside the defined range
0x0823
RLCB_ECCB_NU MRB_ ZERO
An invalid message response is sent when the number of RBs in the message received from the ECCB is zero.
When the number of RBs in the message received from the ECCB is zero
0x0824
RLCB_ECCB_NU MRB_ OVER_MAXRB
An invalid message response is sent when the number of RB of the message received from the ECCB is greater than the maximum value defined.
When the number of RBs in the message received from the ECCB is greater than the maximum value defined
0x0825
An invalid message response is sent when the poll retransmit ECCB_RLC_INVAL timer value of the message ID_T_ POLL received from the ECCB is greater than the maximum value defined.
When the poll retransmit timer in the message received from the ECCB is greater than the maximum value defined
0x0826
An invalid message response is sent when the poll pdu value ECCB_RLC_INVAL of the message received from ID_ POLL_PDU the ECCB is greater than the maximum value defined.
When the poll pdu in the message received from the ECCB is greater than the maximum value defined
0x0827
An invalid message response is sent when the poll byte RLCB_ECCB_INV value of the message received ALID_ POLL_BYTE from the ECCB is greater than the maximum value defined.
When the poll byte in the message received from the ECCB is greater than the maximum value defined
0x0828
RLCB_ECCB_INV ALID_ MAX_RETX
An invalid message response is sent when the max Retx value of the message received from the ECCB is greater than the maximum value defined.
When ‘max Retx’ in the message received from the ECCB is greater than the maximum value defined
0x0829
RLCB_ECCB_INV ALID_ SN_LENGTH
An invalid message response is sent when the sn Length value of the message received from the ECCB is greater than the maximum value defined.
When the ‘sn length’ in the message received from the ECCB is greater than the maximum value defined
0x082A
RLCB_ECCB_IVAL ID_ NUM_RB_UNMAT CH
An invalid message response is sent when there is no mapping value for the RB value of the message received from the ECCB.
When the RB in the message received from the ECCB has no mapping value
© SAMSUNG Electronics Co., Ltd.
3-36
819 LTE Optimization Engineering Guideline
Value DEC
2091
2092
2093
2094
HEX
Call Release Cause
Description
Collection Time
0x082B
RLCB_ECCB_CAL L_IS_ NOT_ACTIVE
An invalid message response is sent when the call ID status of the message received from the ECCB is not ACTIVE.
When the call ID in the message received from the ECCB is not active
0x082C
RLCB_ECCB_INV ALID_ CELLCALL_ID
When the cell call ID of the message received from the ECCB is not within the defined range, respond that the message is not correct.
When the cell call ID in the message received from the ECCB is outside the defined range
0x082D
RLCB_ECCB_INV ALID_ DELETE_FLAG
An invalid message response is sent when the ‘delete flag’ in the message received from the ECCB is outside the defined range.
When the ‘delete flag’ in the message received from the ECCB is outside the defined range
0x082E
RLCB_ECCB_INV ALID_ DELETE_NUMCAL L
An invalid message response is sent when the ‘delete numcall’ in the message received from the ECCB is outside the defined range.
When the ‘delete numcall’ in the message received from the ECCB is outside the defined range
0x082F
RLCB_ECCB_INV ALID_ MAX_T_REORDE R
An invalid message response is sent when the ‘T reorder’ in the message received from the ECCB is outside the defined range.
When the ‘T reorder’ in the message received from the ECCB is outside the defined range
0x0830
RLCB_ECCB_INV ALID_ MAX_T_STATUS_ PROHIBIT
An invalid message response is sent when the ‘T status prohibit’ in the message received from the ECCB is outside the defined range.
When the ‘T status prohibit’ in the message received from the ECCB is outside the defined range
0x0831
RLCB_ECCB_INV ALID_ PCCH_CFG_T
An invalid message response is sent when the ‘pcch cfg T’ in the message received from the ECCB is outside the defined range.
When the ‘pcch cfg T’ in the message received from the ECCB is outside the defined range
RLCB_ECCB_INV ALID_ PCCH_CFG_MOD _ PERIOD_COEFF
An invalid message response is sent when the ‘pcch cfg mode period coefficient’ in the message received from the ECCB is outside the defined range.
When the ‘pcch cfg mode period coefficient’ in the message received from the ECCB is outside the defined range
RLCB_ECCB_INV ALID_ PCCH_CFG_NB
An invalid message response is sent when the ‘pcch cfg nB’ in the message received from the ECCB is outside the defined range.
When the ‘pcch cfg nB’ in the message received from the ECCB is outside the defined range
2095
2096
2097
2098
0x0832
0x0833
© SAMSUNG Electronics Co., Ltd.
3-37
819 LTE Optimization Engineering Guideline
Value DEC
2099
2100
2101
2102
2103
2104
2106
2107
2108
HEX
Call Release Cause
Description
Collection Time
0x0834
C_RLCB_ECCB_L ACK_ OF_NUMOFRB
An invalid message response is sent if new connections are not allowed due to insufficient RBs that can be allocated to the message received from the ECCB.
When new connections are not allowed due to insufficient RBs that can be allocated to the message received from the ECCB
0x0835
An invalid message response RLCB_ECCB_DL_ is sent if new connections are LACK_ not allowed due to insufficient OF_AMDWINDOW AMD window pools that can be _POOL allocated to the message received from the ECCB.
When new connections are not allowed due to insufficient AMD window pools that can be allocated to the message received from the ECCB
0x0836
An invalid message response is sent when the ‘qci’ in the RLCB_ECCB_INV message received from the ALID_ QCI_VALUE ECCB is outside the defined range.
When the ‘qci’ in the message received from the ECCB is outside the defined range
0x0837
RLCB_ECCB_INV ALID_ RLC_MODE
An invalid message response is sent when the ‘rlc mode’ in the message received from the ECCB is outside the defined range.
0x0838
RLCB_ECCB_UL_ NO_ MORE_WIN_TAG_ POOL
An invalid message response is sent if there are not enough window tag pools that can be allocated to the message received from the ECCB.
When there are not enough window tag pools that can be allocated to the message received from the ECCB
0x0839
RLCB_ECCB_INV ALID_ LOCH_TYPE
An invalid message response is sent when the ‘loch type’ in the message received from the ECCB is outside the defined range.
When the ‘loch type’ in the message received from the ECCB is outside the defined range
0x083A
RLCB_ECCB_INV ALID_ CONTROL_TYPE
An invalid message response is sent when the ‘control type’ in the message received from the ECCB is outside the defined range.
When the ‘control type’ in the message received from the ECCB is outside the defined range
0x083B
RLCB_ECCB_INV ALID_ NUM_CALL
An invalid message response is sent when the ‘num Call’ in the message received from the ECCB is outside the defined range.
When the ‘num Call’ in the message received from the ECCB is outside the defined range
0x083C
RLCB_ECCB_INV ALID_ CALLID_UNMATC H
An invalid message response is sent when the ‘cell Call Id’ and ‘CallID’ in the message received from the ECCB do not match.
When the ‘cell Call Id’ and ‘CallID’ in the message received from the ECCB do not match
© SAMSUNG Electronics Co., Ltd.
When the ‘rlc mode’ in the message received from the ECCB is outside the defined range
3-38
819 LTE Optimization Engineering Guideline
Value DEC
HEX
Call Release Cause
Description
Collection Time
RLCB_ECCB_INV ALID_ POLL_RETX
An error code is sent when the tPollRetransmit timer value within the Config Request received from the ECCB (i.e., the call setup message) is incorrect.
When the config request sent to the RLC from the ECCB, i.e., the call setup message has an invalid ‘tPollRetransmit’ timer
0x083E
RLCB_ECCB_NOT _ EQUIPPED_QCI
An invalid message response is sent when the ‘qci’ in the message received from the ECCB is not in ‘equip’ status.
When the ‘qci’ in the message received from the ECCB is not in ‘equip’ status
2111
0x083F
RLCB_ECCB_UL_ NO_ MORE_CALL_POL L
An invalid message response is sent if there are not enough call pools that can be allocated to the message received from the ECCB.
When there are not enough call pools that can be allocated to the message received from the ECCB
2176
0x0880
RLC_EMPTY_MS G
An error code is sent when the message received from the RLC is NULL.
When the message received from the RLC is NULL
0x0881
RLC_UNKNOWN_ MSG_ID
An error code is sent when the message received from the RLC contains an unknown message ID.
When the message received contains an ID that the RLC is not allowed to receive
0x0882
RLC_INVALID_DA TA_LEN
An error code is sent when the size of the message received from the RLC is incorrect.
When the RLC received a message that is either greater than 8 Kbytes or l ess than zero
0x0883
RLC_NO_RSP_FR OM_DL
An error code is sent when no response message is received from the RLC downlink.
When the RLC downlink does not respond to the message received from the ECMB and ECCB
0x0884
RLC_NO_RSP_FR OM_UL
An error code is sent when the response message is not received from the RLC uplink.
When the RLC uplink does not respond to the message received from the ECMB and ECCB
0x0885
RLC_NO_RSP_FR OM_ DLUL
An error code is sent when no response message is received from the RLC downlink/uplink.
When the RLC downlink and uplink do not respond to the message received from the ECMB and ECCB
0x0886
RLC_RX_BEFORE _RLC_ READY
An error code is sent when the RLC uplink receives a signaling message before it is up and running properly.
When the RLC uplink receives a signaling message before it is ready
0x0887
An error code is sent when the transaction ID exceeds the RLC_INVALID_RL specified range while the RLC C_ processes the message TRANSACTION_ID received from the ECCB and ECMB
2109
2110
2177
2178
2179
2180
2181
2182
2183
0x083D
© SAMSUNG Electronics Co., Ltd.
When an invalid transaction ID is found during the signaling process in the RLC for internal purposes
3-39
819 LTE Optimization Engineering Guideline
Value DEC
2184
HEX
0x0888
Call Release Cause
Description
Collection Time
RLC_INVALID_CO NTEXT
An error code is sent when a reply for the signaling message already processed by the RLC is received from the RLC downlink.
When a response is sent again after the RLC signaling block completes the process
When the signaling messages received exceed the RLC capacity When the RLC cannot process the ‘cell num’
2185
0x0889
RLC_RLC_CONTE XT_FULL
An error code is sent when the number of signaling message received exceeds the RLC capacity.
2186
0x088A
RLCB_ERROR_RL C_ CONTEXT_FULL
An error code is sent if the RLC cannot process the ‘cell num.’
2304
0x0900
MAC_INVALID_MS GID
A undefined Msg ID is received.
2305
0x0901
MAC_INVALID_SE TUPTYPE
An undefined SetupType is received.
2306
0x0902
MAC_INVALID_CA LL_CELLID
The Call Cell ID received is outside the allowed range.
2307
0x0903
MAC_INVALID_PA RAMETER
A parameter received is outside the allowed range.
When processing all config messages.
MAC_INSUFFICIE NT_ RESOURCE
The RB cannot be allocated due to the i nsufficient MACB internal resource required to manage the RB.
When setting the logical channel within msgCmacPhyConfigReq_ty pe
2308
0x0904
When processing all ECCB/ECMB MAC messages When processing all messages that contain ‘SetupType’ When processing msgCmacPhyConfigReq_ty pe
When setting the logical channel reconfig/delete within msgCmacPhyConfigReq_ty pe When processing config/delete messages other than msgCmacPhyConfigReq_ty pe When setting the logical channel within msgCmacPhyConfigReq_ty pe When setting the logical channel within msgCmacPhyConfigReq_ty pe/msgCmacPhyReconfigC ommit_type
2309
0x0905
MAC_NOT_ASSIG NED_RB
A reconfig/delete request is received on the RB that is not allocated.
2310
0x0906
MAC_NOT_ASSIG NED_UE
A config/delete request is received on the UE that is not allocated.
2312
0x0908
MACB_NOT_ASSI GN_SRB1
The call setup message received does not have the SRB1 setup.
2313
0x0909
MACB_INVALID_R B_CONFIG
The RB number within the Logical Channel Config exceeds the maximum vaule
2314
0x090A
MACB_INVALID_C ELL_ID
The cell corresponding to the message received is idle.
When processing all ECCB/ECMB MAC messages
4095
0x0FFF
NO_FAULT
The call ends successfully.
When the call ends without any failures
© SAMSUNG Electronics Co., Ltd.
3-40
819 LTE Optimization Engineering Guideline
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 Electronics Co., Ltd.
4-1
