Mehmet TANIS LTE & WCDMA Optimization Expert +90 541 953 21 21 Skype Mehmet - Tanis

LTE
 Preface
 Network Optimization Flowchart
 Rf Optimization Flow Chart
 KPI Name & Definition
 KPI Formula
 KPI Affecting Factors
 Accessibility Fail Reason and solution
 Drop Call Reason and solution
 Handover Fail reason and solution
 Fault Diagnostic and reason of Fault
 Alarm explanation
 Handover Trigger settings
 Idle Reselection settings
 Lte timer settings.
 Lte Features for trial
 Fine Tuning study & trials
 LTE Operation and Configuration
 SIB Messages details Mehmet TANIS
LTE & WCDMA Optimization Expert
 LTE Hardware & Capacity +90 541 953 21 21
Skype ; mehmet_tanis
Why LT E ??
 more throughput speed more than 100 percentage from Dual cell with carrier aggreagation.
3G Dual carrier and LTE Carrier aggregation Speeds shown in below table..
Difference among CA and DC.

Dual cell is Carrier assembly in the same bands.
Carrier aggregation is carrier assembly in the different bands.
3G Dual Cell ( DC ) LTE / Carrier Aggregation ( CA )
F1 : 5 Mhz L 800 : 10 Mhz

F2 : 5 Mhz L 1800: 10 Mhz
Total : 20 Mhz
1 single user possible to see over than
Total : 10 Mhz 100 MB speed vith CA
1 single user will see max 42.3 MB Speed
Neden LTE ??
On the multi carrier, the data goes through the different carriers.
On the carrier aggregation data goes to on the as like one carrier via 2 or 3 different bands..
Neden LTE ??
Difference of LTE ad HSPA+ speeds shown in below table by bands.
Note : For single user HSPA + provide better speed than LTE but on real situation every cell has too many user , due to that condition
LTE provide better speed than HSPA+.
Bandwidth HSPA ++ LTE

5 Mhz 42 Mbps 37 Mbps
If there is 2X2 MIMO , possible to see 75 Mbps speed..

Neden LTE ??
There is LTE TTI time is 10 percentage of R99.. Due to LTE has low TTI time , data speed goes to more
speedy.
TEchnology HSUPA TTI Times

R99 10 miliscond
HSPA 2 milisecond
LTE 1 miliscond
FEC / HARQ
FEC : Forward error correction.. In the tems investigation page it s a HARQ..
2G has an average of 55 frequencies for Turkey, 2G has 11 Mhz band range. This 11 MHz band is divided by
200 kHz to obtain 55 frequencies. We give each 200 kHz band / frequency 8 to the subscribers who use
each timeslot 25 kHz ..
LTE PRB / RB / Symbol
LTE ~ 10 Mhz for each band. 1 subscriber gets 180 kHz for 1
millisecond .. Detailed calculation explanation is as below ..
 1 UE receives 14 symbols in 1 millisecond.
 1 UE has to get a minimum 12 Subcarrier ..
 It flows continuously at 1 millisecond and flows 15 kHz.
 1 15 kHz subcarrier.
 1 Subframe 12 Subcarrier * 15 kHz = 180 Khz.
 7 symbol = 1 Resource block (RB). (Called as a slot ..)
 14 symbol = 1 is called PRB ..
 There are 2 slots 1 PRB ..
 There is 50 resource block at 10 MHz. 50 carrier at 50 Mhz. 50 * 180 = 9

Mhz is the remaining 1 MHz part is quard part.
LTE Throughput Calculation
The smallest unit in the air is called the Resource element (RE).
RE = 1 symbol ( 15 khz of 1 millisecond )
1 UE minimum 1 subframe ( 71*14 ) using , from here 14*12 = 168 RE will be used.
1 slot will use 84 RE.

(50*12 RE)
MAxThroughput= bits/sn= 600*6*14 / 1 ms = 50400 / 1 ms *2
VOLTE Tput = bits/sn = 168*6 / 20 ms = 50.4

Fiziksek Channellar
Downlink Channels.
Uplink Channels.
PDCCH PHICH
PCFICH PUCCH
PDSCH
PUSCH
PBCH : Neighboring , handover time , trigger settings , parametric definition carrying on this channel
PDCCH devided to different channel . Important one is PCFICH channels, ( Pocket Control Formatting Indicator Channel )
: will define as a 1-2-3. 1 ise 14 symboldan 1 ini , 3 ise 14`ten 3`unu.. Decision of how many symbol will be used in PDcch channels..
What is PCI
PCI : There are total 504 PCI have. Those are between 0 – 503, Providing of communication between
antenna and UE..
PSS : 0-1-2
SSS : Between 0-167
PCI = PSS + 3*SSS

RS Power and RSRP
The expression called cpich in 3G is the LTE reference signal power. Expressed as RS.
The signal to the telephone is expressed as RSRP. RSRP is between -44 and -140 .. We are about to say
about -80 fulls .. -100 second later the signal is slowly weakening .
According to the technology, cell camping signal thresholds (operator and condition may vary)
20 watt
2G -100 43 dbm
2 watt
3G -116 33 dbm
0,066 miliwatt
4G -130 18,2 dbm
SINR
SINR : Signal Used Interference Noice

Maximum value 30` 30 is the Best value of SINR.
If the SINR is between 16 and 25 througput is very well expected 64QAM modulation. If it is smaller
than 16, it goes to 16QAM and QPSK modulations.
If the SINR is very good but the throughput does not exceed about 30 MB and is lower;
 Transmission quality or capacity problems should be investigated. (Transport or Transmission units)

 The settings on the Core Network side should be controlled. (PS Core)
 Security Gateway definitions and controls should be provided.
RSRQ
-3 and -20 .. -3 is the best.
When It goes straight to -20 , it means it

is going to worst values..
CSFB / Fast Return
CS Fall Back , If the UE Volte does not support, it is delayed by 3g or 2G. If parameter is 2g or 3g, it changes
gore. If it is not over 3g in one place, setting may be done as 2g. It should be controlled by MML .. It can be
controlled by following command.
CS goes with RRC conn release with Fall back blind redirection ..
Fast Return, When CS Fallback finishes, it is 4G in 1 second. The following command can be used to
control the switch.
MOD UCELLHOCOMM:CELLID=2001,FASTRETURNTOLTESWITCH=PERFENH_PS_FAST_RETURN_LTE_SWITCH-
1&HO_UMTS_TO_LTE_FAST_RETURN_SWITCH-1;
Network Optimization Flowchart
Network Optimization Process
 Single site verification Single site verification, the first phase of network optimization,
involves function verification at each new site.
Single site verification aims to ensure that each site is properly installed and that
parameters are correctly configured.
RF optimization RF (or cluster) optimization starts after all sites in a planned area are
installed and verified.
RF optimization aims to control pilot pollution while optimizing signal coverage, increase
handover success rates, and ensure normal distribution of radio signals before parameter
optimization.
RF optimization involves optimization and adjustment of antenna system hardware and
neighbor lists.
 The first RF optimization test must traverse all cells in an area to rectify hardware faults.
RF Optimization Flowchart
Preparations for RF Optimization
Check List..
 Network plan , network structure diagram , site distribution, site

information, and engineering parameters.
 Drive test results ( such as service drop points and handover failure points)
in the current area.
 Reference signal received power ( RSRP ) coverage diagram
 Signal to interference plus noise raito ( SINR ) distribution diagram.
 Measured handover success rates.
Areas to be optimized can be determined by comparing the distribution of

RSRPs,SINRs and handover success rates with the optimization baseline.
Network Optimization Methods
LTE RF Optimization Objects and Target Baseline W
RSRP
Note: Different from GSM or TD-SCDMA systems, TD-LTE systems have multiple subcarriers
multiplexed. Therefore, the measured pilot signal strength is the RSRP of a single subcarrier (15 kHz)
not the total bandwidth power of the frequency.
The RSRPs near a cell, in the middle of a cell, and at the edge of a cell are determined based on the
distribution of signals on the entire network. Generally, the RSRP near a cell is -85 dBm, the RSRP in the
middle of a cell is -95 dBm, and the RSRP at the edge of a cell is -105 dBm. Currently, the minimum RSRP
for UEs to camp on a cell is -120 dBm.
Empirical RSRP at the edge of a cell: The RSRP is greater than -110 dBm in 99% areas at the TD-LTE site
in Norway. The RSRP is greater than -110 dBm in 98.09% areas in the Huayang field in Chengdu.
Power Adjustment Method
Service power configuration (calculating PDSCH power based on RS power) RS power PA and PB are
delivered using RRC signaling. For two antennas, PA is ρA and ρB is calculated based on the right table.
PDSCH power is calculated based on PA and PB. Currently, it is recommended that PB be set to 1 dB and
PA be set to -3 dB. That is, the pilot power for symbols including pilot symbols accounts for 1/3. This setting
optimizes network performance and ensures that the pilot power for Type A and Type B symbols is
equivalent to the service channel power. In scenarios with special requirements, for example, in rural
scenarios requiring low edge rates, PB can be set to 2 or 3 dB to enhance coverage. Subcarriers share the
transmit power of an eNodeB, and therefore the transmit power of each subcarrier depends on the
configured system bandwidth (such as 5 MHz and 10 MHz). A larger bandwidth will result in lower power
of each subcarrier. LTE uses PA and PB parameters to adjust power. ρA: indicates the ratio of the data
subcarrier power of OFDM symbols excluding pilot symbols to the pilot subcarrier power. ρB: indicates the
ratio of the data subcarrier power of OFDM symbols including pilot symbols to the pilot subcarrier power.
Definitions in 3GPP specifications Control channels Power of PDCCHs, PHICHs, PCFICHs, PBCHs,
primary synchronization channels, and secondary synchronization channels is set using an offset from RS
power.
General mentioned LTE KPI’s should be as like
on tables , before and after parameter r
features activation and deactivation
Drive test KPI’s Cell base Optimization KPI’s
L800
Frequency Locked Before After
FTP Throughput DL 7119 7561  Check High PRB Utilizied site / bands
PDCP Throughput DL 6906 6009
Check which site has High Downlink pocket lost rate
Resource Block Average 34.37 34.56
RSRP Avg -99.15 -92.78 Check which site has high Downlink Paket Delay rate.
RSRQ Avg -12.51 -12.58 VolTE e rab establishment success rate
RS SINR Tem.36 Haz.88 Volte Drop
LTE Locked Before After CQI analysis
FTP Throughput DL 7294 10808 Traffic analysis between bands
PDCP Throughput DL 7450 12268 DL_UL Througput
Accessibility
Resource Block Average Carrier1 50.82 60.08 Retainability
Mobility
Resource Block Average Carrier2 32.83 71.57 Availability
Serving Cell L800 72.62 62.7 Utilization
Traffic
Serving Cell L1800 Nis.19 0
Latency
Serving Cell L900 23.19 37.3
Integrity
RSRP Avg -88.49 -89.04
RSRQ Avg -12.28 -12.41
Dedicated Mode settings / start search threshols.. trials
Dedicated mode’da sorun interfrequency search icin compressed mode gibi gap periyoduna girilmesi ve gap mode boyunca 15% throughput kaybi yasanmasi.
Bu nedenle coverage based A2 threshold’larini asagiya cekmektense frequency priority based handover daha faydali olacaktir..
Coverage based gibi burda da A2 threshold’u var fakat always search olmuyor. 3 sn search edip uygun target bulamazsa bir sonraki search’u sadece cell change olursa yapiyor.
Topic Parameter SET0 example SET1 example
Coverage based Frequency priority based Coverage Based
L800-->L900 start search A2 interfreq -109 -86 -109
L900-->L800 start search A2 interfreq -104 -82 -104
L800-->L900 target threshold A4+Qoffsetfreqconn -101 -78 -101
L900-->L800 target threshold A4+Qoffsetfreqconn -105 -82 -105
Methodology Coverage based Coverage + Frequency priority based

SET2 example SET3 example SET4 example SET5(cell based)
Topic Parameter SET0 example trial SET1 example trial
trial trial trial example trial
L800-->L900 start search SNonIntraSearch 9(-110) 16(-96) 19(-90) 21(-86) 23(-82) Cell based
L900-->L800 start search SNonIntraSearch always search 31(-66) 28(-72) 26(-76) 25(-78) Cell based
Cell based interfreq
L800-->L900 target threshold ThreshXlow/QoffsetFreq 13(-102) L900>L800+18dB L900>L800+16dB L900>L800+14dB L900>L800+8dB
Cell based interfreq

L900-->L800 target threshold ThreshXhigh/QoffsetFreq 10(-108) L800>L900-14dB L800>L900-12dB L800>L900-10dB L800>L900-4dB
L900/L800/L1800/L2600 idle priority CellReselPriority 4/5/6/7 5/5/6/7 5/5/6/7 5/5/6/7 5/5/6/7 5/5/6/7
LTE – KPI’S
LTE Key Performance Indicators for LTE RF Design
LTE is still a developing technology, and it is important to note that as more field trials are carried out and results
validated against the deployed LTE network performance goals, the design targets outlined in this section are subject
to change. The quality of the LTE RF design will be evaluated using planning Tool. This will be based on a
combination of area predictions and Monte Carlo simulations. It is important to note that the emphasis of the design
evaluation will be on focusing where demand is and where potential LTE users are located. The following are a non
comprehensive list of key performance indicators that will be used to validate the quality of the LTE RF network
design.
Reference Signal Received Power (RSRP)

Reference signal received power (RSRP) identifies the signal level of the Reference Signal. It is defined
as the linear average over the power contributions of the resource elements that carry cell-specific
reference signals within the considered measurement frequency bandwidth.
Design KPI for RSRP:

10MHz Channel Bandwidth (700MHz & AWS): -98 dBm /-103 dBm
5MHz Channel Bandwidth (700MHz & AWS): -98 dBm /-103 dBm
A minimum of 95% of the weighted average of the LTE design service area (Cluster or Polygon) must
meet the RSRP targets specified above. The criterion of 95% is based on a weighting using the same
clutter weights used for traffic spreading. The target specified above is after taking into consideration the
indoor loss values assigned per clutter type (In-building losses enabled).
Note: The targets for AWS are only applicable in cases where the AWS design is being carried out as a
standalone design and not be used as a capacity layer over an existing 700 MHz layer LTE network.
LTE – KPI’S
Reference Signal Received Quality (RSRQ)
Reference Signal Received Quality (RSRQ) identifies the quality of the Reference Signal. It 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 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 cochannel
serving and non-serving cells,adjacent channel interference, thermal noise etc. The Design KPI
is based on traffic load—traffic load is discussed later in Sections 3.5 and 5.5.
Design KPI for RSRQ:

2 Transmit Paths:
50% Load: -15 dB
100% Load: - 18 dB
A minimum of 95% of the weighted average of the LTE design service area (Cluster or Polygon) must
meet the RSRQ targets specified above. The criterion of 95% is based on a weighting using the same
clutter weights used for traffic spreading.
LTE – KPI’S
Overlapping Zones (Number of Servers)
The overlapping zones (number of servers) criteria are used to establish the quality of the RF propagation environment from an interference point of view.
The goal of the number of servers‘ criteria is to establishdominance and reduce the waste of network resources and degraded network performance that may
occur when multiple servers exist in the same geographic area. The calculation is based on the reference
Signal (RS) signal levels of the servers.
Design KPI for Overlapping Zones (Number of Servers):

Within 5 dB of the best server
· % area with 4 or more servers should be < 2%.
· % of area with 2 or more servers should be < 30%.
Within 10dB of the best server
· % of area with 7 or more servers should be < 2%.
·
The calculation is based on area importance. The clutter weights used for traffic spreading establishesthe importance of the geographic area. The idea here is
to focus the LTE design where LTE users are located (for example, core urban areas, convention centers, major stadiums, etc.) instead of areas within
the LTE polygon with no users (for example, scrublands, forests, etc.)
DL Cell Aggregate Throughput
The DL Cell Aggregate throughput is the sum of the throughputs to all the users in the cell at an instant in time. This is to be measured following Monte
Carlo simulations only.
Design KPI for DL Cell Aggregate Throughput:
· 10MHz Channel Bandwidth: 13.4 Mbps per cell
· 5MHz Channel Bandwidth: 6.7 Mbps per cell
A minimum of 90% of the cells in the LTE design reference area (Cluster or Polygon) should have the DL
Cell Aggregate Throughput exceeding the minimum design KPI values specified above. No cells should
have Aggregate DL Throughput less than 50% of this KPI target.
LTE – KPI’S
DL Cell Edge User Throughput
The DL Cell Edge User Throughput is established as the minimum throughput for users at the cell edge of
the network at 50% loading. This is to be measured following Monte Carlo simulations only.
Design KPI for DL Cell Edge User Throughput:

· 10MHz Channel Bandwidth: 1000 kbps per user
· 5MHz Channel Bandwidth: 500 kbps per user
A minimum of 90% of all users in the LTE design reference area should have the DL Cell Edge User
Throughput exceeding the minimum design KPI values specified above. No more than 2% of the users
should have a DL Cell Edge User Throughput less than 50% of this KPI target.
All the statistics for the LTE designs must be generated on a cluster by cluster or super cluster basis
following the criteria defined later in the document. In addition to the quantitative evaluation of the LTE
design using the KPIs stated above, a qualitative evaluation of the design will also be carried out as
outlined in the design evaluation. The exit criteria of a design are met when both the quantitative (KPIs)
and qualitative evaluation of the designs are successfully completed.
LTE – Fault Diagnostic
Check the generic hardware fault alarm , such as hardware with

hardware failure or link failure..
Solution : Replace the faulty component..

To ensure the coverage the DL Power parameters should be properly

set such as below tables shown..
Check DL Power configuration
To ensure the coverage , the DL power parameters should be properly set
 RS Power = Maximum RRU power/channel-10log(totalsubcarriers)+10log(Pb+1)

- If the single antenna , Pb=0
- If 2 or 4 antennas, Pb=1
 PDSCH Power = PA + RS Power

- If single antenna , PA=0
- If 2 or 4 antennas , PA=-3
Related Command:
 LST PDSCHCFG : Check Pb and RS power setting

 LST CELLDLPCPDSCHPA : check Pa setting
If the bandwidth is 10Mhz or above , the CPRI rate should be equal or more than 2.5Gbps , otherwise
the cell cant be setup.
Check CPRI rate via below command ( DSP CPRLBR )

If SCTP link is faulty , check the SCTP configuration , suc as peer IP adress , SCTP port number.
If S1 interface state is faulty , check the PLMN and operator ID.
Solution : Replace the faulty component..
Check the S1 interface status via below command DSP S1INTERFACE

If the cell is barred , cell cannot get rrc attempt due to Barred status during idle service.. When see any
barred cells , use the below commands to change barred status to Not_Barred..
The barred cell only impacts on initial UE access, handover in is not affected.
Check the Cell Barred status LST CELLACCESS
If cell is barred , use the following cmmand to recover it

High RSSI causes by the interferences
Check the RF Channel Problem
 Due to the bad feeder quality , incorrect feeder connection or strong interference , it might affect
Rf Channel performance which has impact on UE access.
Relevant Problem :
* High Vswr : ALM-26529 Rf Unit Vswr Threshold Crossed

* Low RSSI : ALM-26521 Rx Unit Rx Channel RSSI Too Low
* RSSI unbalance : ALM-26522 Rf Unit Rx Channel RSSI Unbalances
- RSSI of the main Rx channel and the RSSI of the diverstiy Rx channel exceeds 10 db.
Cause Of High VSWR
 Vswr : Voltage Standard Wave Ration , indicate the if feeder

impedance is match or not. The normal Vswr range is 1-1.5. If Solution for High Vswr
current Vswr is more than a specified threshold , then eNodeb will
generate relevant alarm.
 Alarm generation :
* Cell is activated.
* Rf Power is more than 34 dbm/channel
* Vswr is more than a specified threshold
 Possible cause
* Rf Unit Hardware Fault
* RRU / RFU wrong connection
* Bad Feeder quality or nonstandard feeder installation
Cause of Low RSSI
 Alarm generation : If RSSI is less than a specified value
 Incorrect Rx attenuation setting

* If no TMA , the attenuation should be 0
* If 12 db TMA is used , the attenuation should be 4 to 11 db
* If 24 db TMA is used , the attenuation should be 11 to 22 db
 Feeder problem
* Due to bad feeder wuality , causing additional loss
* RRU Fault
Solution for Low RSSI

Step1 : Check if RRU Rx attenuation is correct
Step2 : If attenuation is correct , than check the feeder installation and connection.
Cause of Imbalance of RSSI
 Alarm generation : RSSI of the main R channel and the RSSI of the diversity RX Channel exceeds 10 db.
 Possible Cause
* High interference Solution of Imbalance RSSI
* RRU cross connections
 UL Interference check
- From WebLMT:Perform spectrum detection to evaluate UL ınterference
- From M2000 client : Perform interference detect monitoring
- Find out interference source
 Check RRU connections,avoid cross connections,show as below
Classification of Interference
 Passive inter-module interference
Due to non-linearity of radio component , the high phase harmonic wave might be
generated and inter-modulated by Rx signal , this the new inter-module signal will arrive the
receiver causing the interference.
 External interference :
Interference from the other system , such as 2g,3g,Cdma , radio , radar , any other external
resources..
How to Located Inter-modulated Interference

 This kind of interference increases with eNodeb transmist power , so we can
simulate the DL load , and check RSSI , if it obsiously increases with the DL
load incensement , then we can determine the interference
Load Simulation
How to Located External Interference

 If we exclude inter-modulated interference , then it should be external interference
Shutdown the Tx of RRU/RFU , if RSSI still high , then we can conclude this is external
interference
LTE – Analysis of Tracing
Analysis of Tracing
 Drive test tracing analysis

We can get all UU ınterface messages,internal UE message as weel as RSRP value
 eNodeb tracing analysis

We can get UU interface message and S1 interface messages
 Form the above tracing analysis, we can locate the problem with the following cause
* Random access failure
* RRC setup failure
* NAS procedure failure
* ERAB setup failure
LTE – Analysis of Tracing / Random Access Failure
Random Access Failure
 Generic scenario : There is no “RRC connect request” message

Possible cause :
* UE doesnt support band
- Scenario : UE doesnt receive any system messsage
- Solution : Check if UE band is identical with eNodeb configuration
* Poor coverage
- Scenario : Due to poor DL or UL coverage , UE or eNodeb miss receiving the relevant random access message
- Solution : Perform Rf tuning , use TMA on Uplink
* Cell is barred
- Check the cell status , should be not barred.
LTE – Analysis of Tracing / RRC Connecton Failure
This failure is caused by eNodeB admission failure. If PUCCH or SRS resource is limited, eNodeB should stop admit all services
including RRC.
Scenario1 : eNodeb directly send reject message

- Possible cause : No radio resource due to not enough resource for PUCCH and SRS
- Solution : Chec the cell load status , if it is very high , consider capacity extension
Scenario 2 : UE doesnt receive “RRC Connection setup message and repeat sending request
message until timer is out.
- Possible cause : Poow DL coverage , check Rsrp and Rsrq
- Solution : Perform RF Tuning
Scenario 3 : eNodeb send RRC setup message , but doesnt get complete message
- Possible cause : If UE doesnt reply RRC complete , it should be Ue problem
If Ue already send RRC complete , then it should be poor UL coverage
Relevant RRC Fail counters
LTE – Analysis of Tracing / e-Rab Setup Failure
This failure refers the fault between “Initial context setup request” message and “Initial context
setup response” message. If any step occur fault, then ERAB setup procedure fails.
Conf
LTE – Analysis of Tracing / e-Rab Setup Failure
E-rabsetup failure cause
If any failure occurs during ERAB setup,we can directly get the failure
cause from performances statistic,the relevant counters are ;
 L.E-Rab.FailEst.NoReply (No response from UE )

 L.E-Rab.Failest.MME ( EPC Fault )
 L.E-Rab.Failest.TNL ( Transport Fault )
 L.E-Rab.Failest.RNL ( Radio Network Fault )
 L.E-Rab.Failest.NoRadioRes ( No radio resource )
 L.E-Rab.Failest.SecurmodeFail ( Security mode setup dault )
LTE – Analysis of Tracing / Faulty Signaling of no UE Response
Scneario: the L.E-RAB.FailEst.NoReply counter is incremented each time the eNodeB receives no responses from the UE
before the corresponding timer expires after sending an RRC signaling message to the UE during the initial UE context setup
procedure or the E-RAB setup procedure
Possible cause:
 Poor DL/UL coverage which cause message missing.
 UE internal process error
Faulty Signaling of No Response

LTE – Analysis of Tracing / Fault signaling of Other Cause
Faulty signaling of other cause

Scenario : eNodeB receives “initial context setup request or “E-Rab setup request” message , after
that , if failures happen , then eNodeB replies response message with failure cause.
LTE – Analysis of Radio Network Fault
Analysis of Radio Network Fault
 Possible Cause
* UU message process failure due to UE capability ( UE doesnt

support relevant service )
* ENodeB failure during eRAB setup
Solutions
* Check UE Capability
* Check eNodeb status
LTE – Analysis of No Radio Resource
Analysis of No Radio Resource
 Possible Cause
* Radio admission failure for eRab
Solutions
* Check if admission parameters arrre correct

* Consider to enable load balance algorithm
* Consider capacity extension
LTE – Key Factors for Lte throughput
 Cell bandwidth: determines the maximum available spectrum resource (number of resource blocks
(RBs) MCS: determines the coding efficiency. Examples are 64QAM, 16QAM, & QPSK
LTE – Key Checking steps
Start Procedure
 Check whether the traffic is normal

 Check alarms and basis parameters on the eNodeB
 If the UE is in TCP transmission , use UDP transmission to replace the TCP transmission
 If the UE is in TCP transmission , upload multiple files using multiple threads or simultaneously
 Check TCP Parameters
 Use the TCP fault location module for TTI tracing.
 If the UE is in UDP transmission,perform UDP packet transmission using multiple threads
 Check the aggregate maximum bit rate ( AMBR )
 Check Whether the closed-loop ( CL ) power control is valid
 Check whether the locall cell has traffic from other Ues
 Check interference
 Check unbalance between the main and diversity antennas of the UE
 Check the UE capability restrictions Send the deliverables for UL throughput fault location
End 
LTE – Typical Downlink Fault Diagnostic
Typical Air-interface Fault Location
 If a DL throughput fault occurs and can be identified to be an air

interface problem , investigate the reasons of the fault from the following
five perspectives in direction from left to right
Insufficient DL Scheduling
 Insufficient DL scheduling can be detected by using the monitoring tool on the UE or on the eNodeb. The
measurement is performed every one second. The number of scheduling attempts cann be calculated as follows.
Number of scheduling attempts of a UE = 1000/Number of UE in the cell. If the total number of DL grants in the
monitoring period is less than %95 of the UE scheduling attempts , the DL schedling is insufficient
Insufficient DL scheduling also occurs if the number of UE scheduling attempts fluctuates for %50.
Insufficient DL scheduling 2
 Check the aggregate maximum bit rate ( AMBR ) and guaranteed bit rate ( GBR ). If
the configured AMBR and GBR are greater than the data rate on the air interface ,
insufficient DL scheduling is not caused by insufficient data transmitted by the EPC.
The example shows DL transmission of
a 50 Mbit packet. The value in red
frame is converted as follows: 6199732 x
8/1000/1000 = 49.597856 Mbit.
Actually, the traffic volume is a
received volume from the EPC to the
Ge interface. This volume can prove
whether the traffic volume is sufficient
to meet the requirements.  Then check whether the data received from the S1 interface is sufficient as
follows.
 Set the control format indicator (CFI) to 3 and increase the PDCCH TX power.
 Query the CFI and PDCCH TX power by running the following commands:
LST CELLPDCCHALGO: LocalCellId=0;
LST CELLDLPCPDCCH: LocalCellId=0;
 Modify the CFI and PDCCH TX power by running the following commands:
MOD CELLPDCCHALGO: LocalCellId=0, InitPdcchSymNum=3, PdcchSymNumSwitch=OFF;
MOD CELLDLPCPDCCH: LocalCellId=0, DediDciPwrOffset=0;
 Restore the CFI and PDCCH TX power by running the following commands:
MOD CELLPDCCHALGO: LocalCellId=0, PdcchSymNumSwitch=ON; Insufficient DL scheduling 3
MOD CELLDLPCPDCCH: LocalCellId=0, DediDciPwrOffset=-30; If the problem persists,perform the following operations.
Insufficient DL Scheduling RBs
Identification—average number of Ue scheduling RBs persecond<Number of RBs in the cell at

the bandwidth/Number of UE in the cell
Insufficient DL Scheduling RBs
 Check the information about UE capability on the air interface,different Ue support

different number of RBs.
 Check whether the frequency selection scheduling or DL inter-cell interference
coordination (ICIC ) is enabled.
Search for the RRC connection Reconfiguration message containing MEasurementconfig,

if the value of reportOnleave is true , the ICIC A3 measurement is used
 Policy for the current version: when the UE DL MIMO Fault
accesses the network for the first time, the MIMO
mode is TM2, and then switched to TM3 after the
channel quality becomes good. In the case of a link
synchronization failure, cell re-setup, or handover,
the MIMO mode is switched to TM2 again, and
then adapts automatically to TM3. Query the air
message to observe the MIMO mode, as shown in
the figure on the top right.
 To identify an MIMO fault, check whether the

rank reported by the UE is inappropriate and the
report feedback is abnormal. Generally, if the
reference signal received power (RSRP) difference
between two antennas is no more than 3 dB, the
TX and RX correlation is no more than 0.5, and the
average SINR is greater than 15 dB, dual-codeword
transmission is available. If dual-codeword
transmission is unavailable, check the rank
reported by the UE and the rank received on the
eNodeB, and then send collected data to Huawei
headquarters for analysis.
Diverged DL BLER
Two cases:
 The DL IBLER fails to converge to 0% in a scenario
where the UE reaches the peak throughput,
 In a peak-throughput scenario where the DL BLER fails

to converge to 0%, the on-site SNR cannot meet the
demodulation capability of the UE. This problem can
be resolved by changing the location of the UE.
 remains at 15% in a scenario where the UE does not
reach the peak throughput.
 This can be identified by the flow chat above.

LTE Traffic Fault Diagnosis
If a DL throughput problem persists after the preceding four aspects are checked, the problem may be caused by a low
DL MCS order.
Low DL MCS Order
 A low DL MCS order is caused by the following three reasons.

 The DL SINR after MIMO equalization is low , resulting in a low DL throughput.
 The DL CRC becomes faulty, resulting in a low DL MCS order in the adapive
modulation and coding (AMC) adjustment.
 In a outdoor test , if the DL MCS order is low , the problem maybe caused by
inaccurate time and frequency tracing
 UL feedback is faulty , resulting in abnormal AMC adjustment and o low DL MCS
order.
 The first two reasons cannot be seperated.For example , if the DL SNR

after MIMO equalization is low i the DL CRC becomes faulty and
therefore te DL MCS order is low.
Low DL SNR or CRS Fault Identification
High DL correlation Observation methods: High DL Correlation
 If both RxChCorFactor and TxChCorFactor are greater than 0.5, the

TX and RX correlation is high. As the two values grow to 1, the
correlation becomes higher while the demodulation capability
becomes worse.
 Solution:
- Laboratory test:
- Modify the networking to make the main and diversity antennas
connected separately.
- Cables in the VAM must also be connected separately.
- Check interference in the laboratory. If the interfering signal is
strong, the TX and RX signal correlation becomes high.
 Outdoor test:
- In a scenario with line of sight, the correlation is high. Avoid an
area with line of sight.
- If external antennas are used, enlarge the interval between two
antennas or place the two antennas vertically.
Interference Observation methods: Low DL SNR or CRC Fault Identification ( 2 )

 Check whether there are multiple cells under Detected Cell
and whether the difference between the RSRP of more than
one cell and that of the local cell is within 3 dB. If the Interference from a neighbouring cell
difference is within 3 dB, strong interference is received from
neighboring cells.
- The PCI of a neighboring cell contained in the
detected cells cannot be the same as that of the local cell.
- Check whether the CQI of the DL subband is
excessively low in a section. If the CQI is excessively low in a
section, DL transmission encounters severe narrowband
interference.
- Estimate the difference between RSRP and SNR. If the
difference is greater than –115 dBm, strong interference is
received.
 Solution:
- Strong interference from neighboring cells can be
eliminated by adjusting the direction of the antenna.
- Severe narrowband interference can be eliminated by
removing the interference sources detected through spectrum
scan.
LTE – Typical Downlink Fault Diagnostic Low DL SNR or CRC Fault Identification (3)
Signal Processing fault on the RRU
1) Unbalanced channels on the RRU make the UE demodulation capability
 For unbalanced channel, Check the RSRP deteriorate,resulting a low MCS order.The observation method is as follows
difference between two antennas. If the RSRP
difference is 5 dB or greater, the channels are
unbalanced. You need to adjust the UE
antennas.
 For UE receiving power problem 2) The UE receiving power generally ranges from -50 dbm to -90 dbm.A
receiving power greater than -50 dbm may cause a clipping and then a low
DL SNR.A receiving power lower than -90 dbm may lead to a low DL
- In a laboratory test, you can adjust the path
SNR,affecting the DLDL transmission performance.Observer the UE
loss to resolve the problem.
receiving power with the following methods.
- In an outdoor test, you can adjust the
interval between sites and the power ratio of the
eNodeB. This problem must be reported to
Huawei headquarters for analysis and
optimization.
LTE Traffic Fault Diagnosis 3) In cases of inconsistent Tx delay on the RRU,spectrum leakage,local
oscillation leakage , and faults in internal modules of the RRU,collect
and send basebad data to Vendor headquarters for analysis..
LTE – Accessibility KPI’s
RRC Setup Success Rate (Service)

E-RAB Setup Success Rate (VoIP)
Measurement point for MME-initiated E-RAB setup

Measurement points for UE-triggered E-RAB setup
E-RAB Setup Success Rate (All)

Call Setup Success Rate

Call Drop Rate (VoIP)
Service Drop Rate (All) Service Drop Rate (Always Online)

LTE – Mobility KPI’s
Intra-Frequency Handover Out Success Rate

Scenario for intra-frequency intra-eNodeB
Scenario A for intra-frequency inter-eNodeB HO
handover
Intra-Frequency Handover Out Success Rate

Scenario B for intra-frequency inter-eNodeB HO
Handover In Success Rate

Intra-eNodeB HO Scenario A for inter-eNodeB HO
Inter-RAT Handover Out Success Rate (LTE to CDMA)
Inter-RAT Handover Out Success Rate (LTE toWCDMA and LTE to GSM)
Inter-RAT handover (LTE to WCDMA/GSM/TD-SCDMA)

Cell Downlink / Uplink Average and Maximum Throughput

Resource Block Utilizing Rate

Drop Call Failure Causes.. Possible causes of interferences shown in below table
Drop Call Cause To high RSSI >-90 dbm can be caused by
external interference • External resources

poor signal • Antenna faults
quality -DL/UL or both ULDL Handover Failure • Parameter of TMA ul gain setting not match with real tma
PCI Dominance pollution • Connector problem
Tx Power limited • Tight cable bends
PCI collision
Radio Link Failure ( Transmission issue ) T310 , T311 , To Low UL RSSI (<-108 dbm) can be caused by:
T301 exprire
cong of target cells • TMA not powered up and incorrect TMA settings
HW capability problem • Incoorect plumbing , broke connector , cable etc..
Missing configuration
Overshooting Cell U What is the UL RSSI : Received Signal strength indicator of th
navailability time total wideband received power within the entire channel
High path delay bandwidth
High latency
Any MME Down Note : RSSI does not distinguish between own , other , any other
Random access problem issue unwanted internal or external interferences..
Drop Call Failure Causes..
Explanation of parameter related to Drop call caused by radio
Handover Failure Causes and troubleshooting..
Handover Failure Reason
Check connected users , check network load
Check drop call causes
Check UL RSSI
Bad RF condition
Target cell has poor accessibility
Poor coverage
Parameter inconsistency
High S1 delay time
incorrect azimuth or tilt
antenna down tilt and azimuth issue.
Transmission bottleneck on target eNode B.
Availability of target cells
missing nieghbors.
Improper MME Configuration
incorrect parameter setting.
Target cannot interpret the contents in HO request message.
Improper MME Configuration.
Insufficient SR & CQI resources for target.
PCI Collision.
Hardware faults.
Swapped Sectors.
Overshooting.
Unreasonable neighbor relation.
Badly tuned handover parameters.
any MME down or intermittent in pool which defined in eNB cause of drop.
Drop due to Random Access problem
Throughput analysis and troubleshooting..
Low Throughput Issue Radio Analysis - Downlink
CQI (Channel Quality Index) and RI (Rank Indicator) reported from UE.
Poor coverage (BLER)
Transmission Mode: MIMO (tm3) vs. TxD (tm2) vs. SIMO (tm1)
avaibility issue. These are the fundamental areas of analysis for downlink:
MCS vs. number of assigned PRBs vs. assignable bits in scheduler CQI and RI provides us the SINR/antenna layer reception reports from the UE point of view
Uplink Interference. Transmission modes 1 (SIMO),2 (Transmit Diversity) and 3 (Open Loop Spatial Multiplexing) are
UE Scheduling percentage of TTIs (how often is the UE scheduled) supported by the eNB in L11A.
A poor RACH deconding SR. Understanding the relationship between chosen MCS, assigned PRBs and assignable bits in the
CFI (number of OFDM symbols for PDCCH) vs. MCS vs. % scheduling
high error on S1 link. scheduler are important for sorting core network issues/UE issues from air interface issues
HARQ Scheduling percentage means the amount of TTIs (typically measured per second) that the UE was
delay on S1 link towards MME & SGW. scheduled. This is also related to the resources allocated for PDCCH (control channels)
RLC retransmissions PDCCH CFI impacts the % TTI scheduling but also reduces the maximum MCS achievable.
accessiblity issue. HARQ will be presented using tracing. Check also the Uplink HARQ for more detailed theoretical
Another cause of low (or lower than expected) throughput is that the explanation.
Handover failure. UE is not being scheduled in every TTI.
RLC retransmissions will be touched on briefly, including how to trace RLC status messages and some
Lack of PRBs. parameters involved.
Packet loss can lead to (retransmissions, dropped in RBS, etc)
Problemtic UE.
Downlink Interference (Bad CQI) Radio Analysis – Uplink
MIMO Parameters Uplink scheduling overview
High VSWR BSR (Buffer Status Report) These are the fundamental areas of analysis for uplink:
We’ll begin this section with an overview of uplink scheduling
PHR (Power Headroom Report) – is the UE at maximum power?
high radio errors or instability issue. BSR is the mechanism the UE uses to inform the eNB about the amount of data waiting in its RLC
Cell bandwidth vs. maximum allowable PRBs buffers
Maximum number of RRC connections active per cell Link Adaptation PHR is the mechanism the UE uses to inform the eNB about remaining power at the transmitter (or
power limitations)
Maximum number of users per TTI supported per cell. MCS available and 16QAM The number of PRBs available for uplink scheduling has some 3GPP specified limitations which
Core network, MME/SGW, etc PDCCH SIB scheduling colliding with UL grant different from downlink. This means that, for example, the maximum number of PRBs (for a single
UE) able to be scheduled in 5MHz is 20 and not 23 (with 2 reserved for PUCCH).
Transmission insability & bottleneck. HARQ (less important, because we can measure SINR) Link adaptation inputs for uplink vary from downlink. One difference is the CQI (estimate of SINR) is
not needed because the eNB can itself measure SINR of PUSCH transmissions.
incorrect parameter setting. PDCCH collisions can occur with SIB/downlink transmissions as downlink and uplink grants are both
QPSK cases in UL has increased from ~30% to ~40%. If more QPSK cases
scheduled using the same PDCCH resources.
Badly tuned handover parameters. then there are more UEs in poor radio conditions
The theory of HARQ in uplink is presented.
High traffic on Cell limit THp
CS Fall Back Fail Cause
CSFB Failure Reason

UE auto detach: fail reason, establish SGs interface between MME and
MSC/VLR
RWR TO LTE FAIL after csfb call, CSFB call succeed, but failed to fast return to
LTE ( Fast return feature activated )
 TAU reject without active bearer,in idle mode, Field CSFB call succeed, but
TAU to LTE reject
Service Reject for Mobile Terminating CSFB Intermittent
Reselection Time back to LTE (when UE has moved to 2G)
 Idle Reselection from LTE to 2G
Poor Target 3G Coverage
TAU Rejection following RAU Failure in 3G – after CSFB
TMSI mismatch, the MME sent a wrong or mismatched to SGSN
CSFB failure due to missing SGs interfaces, RNC have been rehomed to MSC
which belong to HLRs which don’t support CSFB
 Congestion on WCDMA
A UE in attached mode looks for a better handover candidate based on sMeasure. This parameter defines the
Handover & Events serving cell quality threshold at which UE needs to perform measurements.
Recommended value of this parameter is 0 which means that UE will always be looking for a better neighboring
candidate.
Offset value (a3offset) is added to the source whereas hysteresis value is subtracted from target (hysteresisA3)
during evaluation i.e.
Mn is neighboring cell measured value (RSRP/RSRQ) and Ms is serving cell
cellIndividualOffsetEutran can also be used. It is possible to set it per cell
relationship. The value is added during evaluation.
Event For Report Configuration following condition should be met for successful handover
Handover & Events
Cell Selection ( Idle , intra , inter , rat )
Idle Mode selection parameters
High Priority LTE to Low Priority Inter/ IRAT Reselection

Cell Selection ( Idle , intra , inter , rat )
E-utran to Utran Cell Reselection parameters
Utran – Eutran Cell Reselection parameters
LTE Timers
LTE Timers
LTE Timers
Drive Test
Drive Test
what can be checked in Drive test
RSRP(from -44 to -140 dBm)
RSRQ (-3 to -19)
PCI(0 to 503)
CQI(15 to 0)
SINR (30 to -6 dB)
MCS DL/UL (max 28)
RI (MIMO Rank Indicater 1, 2 & 4)
TBS(maximum of two TBs generated per TTI per UE)

RSSI
BLER
Jitter
NBR cell
UE TX POWER
 Ping
DL/UL troughput
PRB DL/UL
 EARFCN
An example of UE Tx Power Distribution
Drive Test
Factors Affecting Coverage

For Downlink
 Downlink Tx Power
 Path Loss in downlink For Uplink
 Carrier frequency
 Distance of UE
 Uplink Tx Power
 Propagation Envoirenment
 Path Loss in uplink
Antenna gain
 Carrier frequency
 Haight of antenna
 Distance of UE
 Tilt of antenna
 Propagation Envoirenment
 Azimuth of antenna
 Gain of Rx diversity in eNodeb
Important KPI of Drive Test
Drive Test
• The RRCConnectionReconfiguration message is the command to modify an RRC connection. It may For some network tunning projects, maybe some
convey information for measurement configuration, mobility control, radio resource configuration other KPIs more than coverage KPI are needed. The
(including RBs, MAC main configuration and physical channel configuration) including any
associated dedicated NAS information and security configuration. following are some examples
• PDCP: integrity protection and ciphering;
• RLC: reliable and in-sequence transfer of information
• RSSI = wideband power= noise + serving cell power + interference power
• RSRP (dBm)= RSSI (dBm) -10*log (12*N), high BW è less RSRP
§ Value 00 (-140) to 97 (-44), step 1
§ Independent of load
 LTE/SAE attach success rate
• RSRQ = N x RSRP / RSSI, high BW
§ Value 00 (-19.5) to Value 34 (-3), step .5
 E-Rab setup success rate
§ Dependent on load
• RSRQ -3 to -19, RSRP -140 to -44
 Call drop rate
o RSRQ=RSRP/(RSSI/N) = RSRP*N/(IN_n + ρ*12*N*Psc) and
o SINR=S/(IN_m)
 Intra Lte handover succcess rate
• SNR -15 to 40
• CINR=RSRQ
 Intra LTE handover delay
• UE estimates SINR based on the Power Spectral Density of the downlink RS and PSD offset  Ftp download average throughput
between PDSCH and RS. The SINR is Channel Quality Indicator (CQI).
 Ftp Upload average throughput
• UE will report lower CQI values when using MIMO as opposed to SIMO in same RF environment
(SINR), UE will typically use lower Modulation/MCS
• CQI 0 to 15, MCS 0 to 28
• CINR -25 to 40dB
• RSRP -150 to -30
• RSSI -120 to 0
• UE PRACH TX Power -10 to 23 dBm
• RSRQ 0 to -40
• BLER 0 to 100% tolerable till 10%
• FER 0 to 100%
• UE categories 1(low) to highest(5)
• Transmission modes Mode 1 to 9 (highest), open/closed loop, antenna ports, MIMO (tm3) vs. TxD
(tm2) vs. SIMO (tm1)
Drive Test
 Weak Coverage means the Rsrp of the reference signal in a

coverage is smaller than a threshold ( The typical threshold is 110
dbm )
 Cross Coverage generally means that the coverage area of an

eNodeb goes beyond the planned scope , and generates
discontinious dominant areas in thhe coverage areas of other
eNodeBs.
 Lack of Dominant cell means a type of area where there is no

dominant cell or the dominant cell is changed frequently
RRC Reestablishment
Conditions for Triggering RRC Connection Reestablishment
RRC Connection Reestablishment procedure
A UE triggers an RRC connection reestablishment in the following scenerio.
 Upon detecting a radio link failure ( RLF )

 Upon handover failure
 Upon an E-Utran originated inter-Rat handover Failure
 Upon receiving and integrity check failure indication from lower layers
 Upon an RRC connection reconfiguration failure
A UE detects an RLF when any of the following condition is met :
 The timer T310 expires

 The random access fails and the timer T300,T301,T304(T304 for Eutran and T304 for Geran ) or
T311 is not running.
 The number of RLC retransmission reaches the maximum
Note : Upon receiving consecutive N310 “out of sync” indications from lower layers while none of
T300,T301,T304 or T311 is running , the UE starts T310.
Upon receiving consecutive N311 “in-sync” indications from lower layers while T310 is running ,
the UE stops T310.
For details about T300 , T301 , T304,T310,T311 and N311 , see eNodeB MO Reference.
After an RRC connection is reestablished successfully , SRB1 can be restored but other radio
bearers cannot.
IP Path Detection Function
Run the DSP IPPATH command to check the status
of the Ip path , as shown in below table
Run the MOD GTPU command to enable the detection
function for the IP Paths cooresponding to the S1 If Ip path check result is Fault , the Ip path is faulty ,
interface. in this case , check whether the Ip path is correctly
configured.
Enabling the IP path detaction dunction
Run the ADD ENODEBPATH command to add the

application type of the IP path cooresponding to the S1
interface
KPI Huawei MS formula
RRC connection L.RRC.ConnReq.Att.Emc +L.RRC.ConnReq.Att.HighPri +L.RRC.ConnReq.Att.Mt
establishment Attempt +L.RRC.ConnReq.Att.MoSig+L.RRC.ConnReq.Att.MoData
(L.RRC.ConnReq.Succ.Emc +L.RRC.ConnReq.Succ.HighPri +L.RRC.ConnReq.Succ.Mt
RRC connection +L.RRC.ConnReq.Succ.MoSig+L.RRC.ConnReq.Succ.MoData)/
LTE KPI Formula -1 establishment Success rate (%) (L.RRC.ConnReq.Att.Emc +L.RRC.ConnReq.Att.HighPri +L.RRC.ConnReq.Att.Mt
+L.RRC.ConnReq.Att.MoSig+L.RRC.ConnReq.Att.MoData)*100
L.E-RAB.AttEst.QCI.2+L.E-RAB.AttEst.QCI.3+L.E-RAB.AttEst.QCI.4+L.E-RAB.AttEst.QCI.5+L.E-RAB.AttEst.QCI.6+L.E-
E-RAB establishment Attempt
RAB.AttEst.QCI.7+L.E-RAB.AttEst.QCI.8+L.E-RAB.AttEst.QCI.9
(L.E-RAB.SuccEst.QCI.2+L.E-RAB.SuccEst.QCI.3+L.E-RAB.SuccEst.QCI.4+L.E-RAB.SuccEst.QCI.5+L.E-RAB.SuccEst.QCI.6+L.E-
RAB.SuccEst.QCI.7+L.E-RAB.SuccEst.QCI.8+L.E-RAB.SuccEst.QCI.9)/
E-RAB establishment success rate (%)
(L.E-RAB.AttEst.QCI.2+L.E-RAB.AttEst.QCI.3+L.E-RAB.AttEst.QCI.4+L.E-RAB.AttEst.QCI.5+L.E-RAB.AttEst.QCI.6+L.E-
RAB.AttEst.QCI.7+L.E-RAB.AttEst.QCI.8+L.E-RAB.AttEst.QCI.9)*100
L.E-RAB.AbnormRel.QCI.1+L.E-RAB.AbnormRel.QCI.2+L.E-RAB.AbnormRel.QCI.3+
E-RAB Abnormal Release L.E-RAB.AbnormRel.QCI.4+L.E-RAB.AbnormRel.QCI.5+L.E-RAB.AbnormRel.QCI.6+
L.E-RAB.AbnormRel.QCI.7+L.E-RAB.AbnormRel.QCI.8+L.E-RAB.AbnormRel.QCI.9
(L.E-RAB.AbnormRel.QCI.1+L.E-RAB.AbnormRel.QCI.2+L.E-RAB.AbnormRel.QCI.3+
L.E-RAB.AbnormRel.QCI.4+L.E-RAB.AbnormRel.QCI.5+L.E-RAB.AbnormRel.QCI.6+
L.E-RAB.AbnormRel.QCI.7+L.E-RAB.AbnormRel.QCI.8+L.E-RAB.AbnormRel.QCI.9)/
[(L.E-RAB.AbnormRel.QCI.1+L.E-RAB.AbnormRel.QCI.2+L.E-RAB.AbnormRel.QCI.3+
E-RAB drop rate (%)
L.E-RAB.AbnormRel.QCI.4+L.E-RAB.AbnormRel.QCI.5+L.E-RAB.AbnormRel.QCI.6+L.E-RAB.AbnormRel.QCI.7+L.E-
RAB.AbnormRel.QCI.8+L.E-RAB.AbnormRel.QCI.9)+(L.E-RAB.NormRel.QCI.1+L.E-RAB.NormRel.QCI.2+L.E-
RAB.NormRel.QCI.3+L.E-RAB.NormRel.QCI.4+L.E-RAB.NormRel.QCI.5+L.E-RAB.NormRel.QCI.6+L.E-RAB.NormRel.QCI.7+L.E-
RAB.NormRel.QCI.8+L.E-RAB.NormRel.QCI.9)]*100
Intra eNB Handover Attempt L.HHO.IntraeNB.IntraFreq.ExecAttOut+L.HHO.IntraeNB.InterFreq.ExecAttOut

Intra eNB Handover (L.HHO.IntraeNB.IntraFreq.ExecSuccOut +L.HHO.IntraeNB.InterFreq.ExecSuccOut)/
Success Rate (%) (L.HHO.IntraeNB.IntraFreq.ExecAttOut+L.HHO.IntraeNB.InterFreq.ExecAttOut)*100
Inter eNB Handover Attempt L.HHO.IntereNB.IntraFreq.ExecAttOut+L.HHO.IntereNB.InterFreq.ExecAttOut
Inter eNB Handover (L.HHO.IntereNB.IntraFreq.ExecSuccOut+L.HHO.IntereNB.InterFreq.ExecSuccOut)/
Success Rate (%) (L.HHO.IntereNB.IntraFreq.ExecAttOut+L.HHO.IntereNB.InterFreq.ExecAttOut)*100
DL_Volume_GB L.Thrp.bits.DL/8/1024/1024/1024
UL_Volume_GB L.Thrp.bits.UL/8/1024/1024/1024
Average Active User L.Traffic.User.Avg
Max Active User L.Traffic.User.Max
LTE KPI Formula -2
KPI Formula
RRC Setup Success Rate [%] L.RRC.ConnReq.Succ / L.RRC.ConnReq.Msg *100
(L.RRC.ConnReq.Succ.Emc + L.RRC.ConnReq.Succ.HighPri + L.RRC.ConnReq.Succ.Mt +
L.RRC.ConnReq.Succ.MoData + L.RRC.ConnReq.Succ.DelayTol) / (L.RRC.ConnReq.Att.Emc +
RRC Setup Success Rate [%] (Service)
L.RRC.ConnReq.Att.HighPri + L.RRC.ConnReq.Att.Mt + L.RRC.ConnReq.Att.MoData +
L.RRC.ConnReq.Att.DelayTol) *100
RRC Setup Success Rate [%] (Signalling) L.RRC.ConnReq.Succ.MoSig / L.RRC.ConnReq.Att.MoSig *100
Accessibility
S1 Establishment Success Rate [%] L.S1Sig.ConnEst.Succ / L.S1Sig.ConnEst.Att *100
ERAB Setup Success Rate [%] L.E-RAB.SuccEst / L.E-RAB.AttEst *100
E2E Call Setup Success Rate [%] RRC Setup * S1 Estab * ERAB Setup
Random Access Success Rate [%] (L.RA.GrpA.ContResolution + L.RA.GrpB.ContResolution) / (L.RA.GrpA.Att + L.RA.GrpB.Att) *100
CSFB Preparation Success Rate [%] L.CSFB.PrepSucc / L.CSFB.PrepAtt *100
VoLTE Drop Call Rate [%] L.E-RAB.AbnormRel.QCI.1 / (L.E-RAB.AbnormRel.QCI.1 + L.E-RAB.NormRel.QCI.1) *100
Retainability Radio Bearer Drop Rate (All) [%] L.ERAB.AbnormRel.eNBTot / (L.ERAB.AbnormRel.eNBTot + L.E-RAB.NormRel)
Service Drop Rate (Carrying data) [%] L.E-RAB.AbnormRel / (L.ERAB.AbnormRel.eNBTot + L.E-RAB.NormRel)
(L.HHO.IntraeNB.IntraFreq.ExecSuccOut + L.HHO.IntereNB.IntraFreq.ExecSuccOut) /
Intra Frequency Handover Sucess Rate [%]
(L.HHO.IntraeNB.IntraFreq.ExecAttOut + L.HHO.IntereNB.IntraFreq.ExecAttOut) *100
(L.HHO.IntraeNB.InterFreq.ExecSuccOut + L.HHO.IntereNB.InterFreq.ExecSuccOut) /
Mobility Inter Frequency Handover Sucess Rate [%]
(L.HHO.IntraeNB.InterFreq.ExecAttOut + L.HHO.IntereNB.InterFreq.ExecAttOut) *100
Inter-RAT Handover Success Rate (LTE to WCDMA) L.IRATHO.E2W.ExecSuccOut / L.IRATHO.E2W.ExecAttOut *100
Inter-RAT Handover Success Rate (LTE to GRAN) L.IRATHO.E2G.ExecSuccOut / L.IRATHO.E2G.ExecAttOut *100
LTE KPI Formula -3
KPI Formula
DL Throughput Per UE (kbps) L.Thrp.bits.DL / (L.Traffic.User.DLData.Avg * reporting period * 1000)
UL Throughput Per UE (kbps) L.Thrp.bits.UL / (L.Traffic.User.ULData.Avg * reporting period * 1000)
L.Thrp.bits.DL / (L.Thrp.Time.Cell.DL.HighPrecision)
Cell Downlink Average Throughput (kbps)
Global formülü L.Thrp.bits.DL / (L.Thrp.Time.Cell.DL *1000)
L.Thrp.bits.UL / (L.Thrp.Time.Cell.UL.HighPrecision)
Cell Uplink Average Throughput (kbps)
Global formülü L.Thrp.bits.UL / (L.Thrp.Time.Cell.UL *1000)
Cell Downlink Maximum Throughput (kbps) L.Thrp.bits.DL.Max / 1000
Cell Uplink Maximum Throughput (kbps) L.Thrp.bits.UL.Max / 1000
Quality
Packet Loss Rate DL [%] (1-(€ {L.Traffic.DL.PktDelay.Num.QCI.n} / € {L.Traffic.DL.PktUuLoss.Tot.QCI.n })*100 n=1,2,3..8,9
Packet Loss Rate UL [%] € {L.Traffic.UL.PktLoss.Loss.QCI.n} / € {L.Traffic.UL.PktLoss.Tot.QCI.n } *100 n=1,2,3..8,9
€ {L.Traffic.DL.PktDelay.Time.QCI.n } n=1,2,3,4,5,6,7,8,9 ya da L.Traffic.DL.PktDelay.Time.QCI.n
eNodeB DL Packet Delay [ms] / L.Traffic.DL.PktDelay.Num.QCI.n
PDU Retransmission Rate DL [%] L.Traffic.DL.AM.Retrans.TxPackets / L.Traffic.DL.AM.TxPackets *100
PDU Retransmission Rate UL [%] L.Traffic.UL.AM.Retrans.RxPackets / L.Traffic.UL.AM.RxPackets *100
PDU Discard Rate DL [%] L.Traffic.DL.AM.TxDropPackets / L.Traffic.DL.AM.TxPackets *100
Average CQI L.ChMeas.CQI.DL.n * n / € {L.ChMeas.CQI.DL.n} n=0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
Downlink Traffic Volume [KB] L.Thrp.bits.DL / (8*1000)
Traffic
Uplink Traffic Volume [KB] L.Thrp.bits.UL / (8*1000)
Max Active users DL L.Traffic.User.DLData.Max & L.Traffic.ActiveUser.DL.Max
Avg Active users DL L.Traffic.User.DLData.Avg & L.Traffic.ActiveUser.DL.Avg
Max Active users UL L.Traffic.User.ULData.Max & L.Traffic.ActiveUser.UL.Max
Avg Active users UL L.Traffic.User.ULData.Avg & L.Traffic.ActiveUser.UL.Avg
Max Active users L.Traffic.User.Data.Max & L.Traffic.ActiveUser.Max
Capacity
Avg Active users L.Traffic.User.Data.Avg & L.Traffic.ActiveUser.Avg
Max RRC connected users L.Traffic.User.Max
Avg RRC connected users L.Traffic.User.Avg
PRB Utilization DL [%] (L.ChMeas.PRB.UL.Used.Avg
L.ChMeas.PRB.DL.Used.Avg /-L.ChMeas.PRB.DL.Avail
L.ChMeas.PRB.PUCCH.Avg) *100/ (L.ChMeas.PRB.UL.Avail -
PRB Utilization UL [%] L.ChMeas.PRB.PUCCH.Avg) *100
RLC – PDPC Parameters
LTE Features and possible trials parameters
LTE Features
 ICIC: this features used to avoid interference.(working well in Ericsson)
 Redirection to UTRAN
 RACH resources adjustment (to improve UL througput)
 MLB for Inter frequency
 MLB for IRAT
 ANR
 Beamforming
 DRX for idle & connected.
 MIMO adpative TM3 & TM2.
 Dynamic QoS Modification(Ericsson Feature)
 PDDCH dynamic allocation(Huawei).
 CSFB
 MIMO closed loop for FDD (improve DL throughput5% but UE speed slow than Open loop.
 Intererfernece Rejection combining(Ericsson).
 UE Measurement & Cell Trace (Ericsson Feature).
 4way diversty 2T4R
 TCP Optimization feature is ericsson features, reduce delay in downlink by introducing active queue management(AQM), manage the
buffer space).
 SRS from access first to experience first along with beamforning.
 TA timer change can improve UL THp & UL spectrm effeciency
 PDCCH enhanced CFI improve DL THp
 LTE PUSCH DTX detection ( save PUSCH RB & improve UL Thp and decrease UL RBLER) eNB can detect it as PUSCH DTX.
If DTX is detected, New Transmission is performed. While NACK detected, retransmission is performed thus resource is wasted
 FSS frequency scheduling (improve DL THROUGHPUT)
 RBG Add padding to the data to constitute an integral multiple of RBG(scheduling once).
 PDCP discard timer from infinity to 1500ms(improve PDCP latency from 85 to 68 aboserved
 Frequency Hopping improve RRC & ERAB SR
 Flow Control to improve ERAB SR.
 CCE adjustment (dcrease PDDCh 2 & 3 usage & improve throughput)
LTE Specific Alarms
Alarm ID Alarm Name Alarm Level Details
ALM-29201 S1 Interface Fault Major
ALM-29204 X2 Interface Fault Major
eNodeB Control Plane Status of all the SCTP links (no less than two) that carry services (such as the S1 or X2
ALM-29207 Major
Transmission Interruption interfaces) is abnormal
ALM-29240 Cell Unavailable Major
Base station detects that the cell power configuration on the Physical Downlink Shared Channel
ALM-29241 Cell Reconfiguration Failed Minor
(PDSCH) fails to be modified.
ALM-29242 No Traffic Volume in the Cell Minor Base station detects that there is no UE access to the cell during a preset period.
RF resources, baseband resources, or inter-board link resources of a base station do not meet
ALM-29243 Cell Capability Degraded Major the specifications of the cell configuration, or configurations for carrier aggregation (CA) are
inconsistent.
ALM-29245 Cell Blocked Major
ALM-29246 Cell Simulated Load Startup Minor The user starts the simulated load in the cell. RMV CELLSIMULOAD
The serving cell and a cell in the neighboring cell list (NCL) have the same physical cell identifier
(PCI) and downlink frequency.
ALM-29247 Cell PCI Conflict Warning
The serving cell and a cell of the same base station have the same PCI and downlink frequency.
Cells in the neighboring relation table (NRT) containing the serving cell have the same PCI.
ALM-29248 RF Out of Service Major An RRU fails to provide services in a multi-RRU cell.
ALM-29249 eNodeB Out of Service Major All cells in a FDD mode under an eNodeB are unavailable.
ALM-25891 IKE Negotiation Failure Major Base station detects that the Internet Key Exchange (IKE) negotiation with the peer device fails.
The local and peer ends of a user-plane link carrying upper-layer services fail to communicate
ALM-25952 User Plane Path Fault Major
with each other
System detects that data configuration becomes abnormal (for example, PRACH Root Sequence
ALM-26247 Configuration Failure Minor
configuration conflict occurs).
ALM-26252 Board Unrecognizable Major System detects a board but cannot recognize the board type
Licensed Feature Entering Keep-Alive
ALM-26815 Warning Licensed feature expires and enters the keep-alive period (grace period).
Period
ALM-26816 Licensed Feature Unusable Minor The grace period of an expired feature controlled by a license elapses.
ALM-26817 License on Trial Major A license enters the grace period.
ALM-26818 No License Running in System Critical System detects that there is no valid license.
Data Configuration Exceeding Licensed
ALM-26819 Warning Data configuration of the NE exceeds the licensed limit.
Limit
NE detects that a certificate has not taken effective, has expired, or fails to be loaded. An invalid
ALM-26841 Certificate Invalid Major
certificate cannot be used for Internet Key Exchange (IKE).
DMCR Activation
DMCR Activation
DMCR Activation
Enhanced RRC release with redirect . Defreed Measurement Control Reading ( DMCR ) procedures( WCDMA )
the DMCR feature avoıds readıng spesıfıc SIBs wıth ınfırmatıon that can be receıved at another occasion. The maximum time for reading
system information without this indication is 1280 ms.
DMCR Activation
DMCR (Deferred Measurement Control Reading) feature..
Impact : Rnc+basic CSFB ( First CSFB UE support DM CR by default )

Characteristics :
- CS -0.8 s higher call setup time for Utran
- PS stop in non-DTM GERAN or RAU to establish PS bearers ( 5-6s )
In RNC additional Nodes impacted : DMCR support

Additional Network Impcat : DMCR to be rolled out in RNC.
Benefit : faster call set-up times compared to the non enhanced solution.
CSFB Call Setup time improved.
Command Lines
For whole RNC’s all cells must be run below command
MOD UCELLMEAS:CELLID=xxx,DEFERMCREADIND=TRUE;
ENodeB SRVCC 3G B1 Threshold
For SRVCC Success improvement all e-Nodeb “SRVCC 3g B1 EcNo threshold can be set to -12 db’s.
Command Lines.
For all e-NodeB
MOD INTERRATHOCOMM:INTERRATHOUTRANB1MEASQUAN=ECN0;
All E-NodeB Locall Cells

MOD INTERRATHOUTRANGROUP:LOCALCELLID=XX,INTERRATHOUTRANGROUPID=1,INTERRATHOUTRANB1THDECN0=-24;
For LL900
ADD INTERRATHOCOMMGROUP: LocalCellId=7X, InterRatHoCommGroupId=1, InterRatHoA1A2Hyst=2, InterRatHoA1A2TimeToTrig=640ms, InterRatHoA1ThdRsrp=-108, InterRatHoA2ThdRsrp=-112;
MOD INTERRATHOCOMMGROUP: LocalCellId=7X, InterRatHoCommGroupId=1, InterRatHoA1A2Hyst=2, InterRatHoA1A2TimeToTrig=640ms, InterRatHoA1ThdRsrp=-108, InterRatHoA2ThdRsrp=-112;
ADD INTERRATHOGERANGROUP: LocalCellId=7X, InterRatHoGeranGroupId=1, InterRatHoGeranB1Hyst=2, InterRatHoGeranB1Thd=-94, InterRatHoGeranB1TimeToTrig=640ms;
MOD INTERRATHOGERANGROUP: LocalCellId=7X, InterRatHoGeranGroupId=1, InterRatHoGeranB1Hyst=2, InterRatHoGeranB1Thd=-94, InterRatHoGeranB1TimeToTrig=640ms;
ADD INTERRATHOUTRANGROUP: LocalCellId=7X, InterRatHoUtranGroupId=1, InterRatHoUtranB1ThdEcn0=-24, InterRatHoUtranB1ThdRscp=-95, InterRatHoUtranB1Hyst=2, InterRatHoUtranB1TimeToTrig=320ms;
MOD INTERRATHOUTRANGROUP: LocalCellId=7X, InterRatHoUtranGroupId=1, InterRatHoUtranB1ThdEcn0=-24, InterRatHoUtranB1ThdRscp=-95, InterRatHoUtranB1Hyst=2, InterRatHoUtranB1TimeToTrig=320ms;
MOD CELLSTANDARDQCI:QCI=QCI1,LOCALCELLID=7X,INTERRATHOCOMMGROUPID=1,QCIPRIORITYFORHO=1,INTERRATHOGERANGROUPID=1,INTERRATHOUTRANGROUPID=1;
MOD CELLSTANDARDQCI:QCI=QCI5,LOCALCELLID=7X,QCIPRIORITYFORHO=2;
For L800/L1800/L2600
ADD INTERRATHOCOMMGROUP: LocalCellId=1/3/5X, InterRatHoCommGroupId=1, InterRatHoA1A2Hyst=2, InterRatHoA1A2TimeToTrig=640ms, InterRatHoA1ThdRsrp=-114, InterRatHoA2ThdRsrp=-118;
MOD INTERRATHOCOMMGROUP: LocalCellId=1/3/5X, InterRatHoCommGroupId=1, InterRatHoA1A2Hyst=2, InterRatHoA1A2TimeToTrig=640ms, InterRatHoA1ThdRsrp=-114, InterRatHoA2ThdRsrp=-118;
ADD INTERRATHOGERANGROUP: LocalCellId=1/3/5X, InterRatHoGeranGroupId=1, InterRatHoGeranB1Hyst=2, InterRatHoGeranB1Thd=-94, InterRatHoGeranB1TimeToTrig=640ms;
MOD INTERRATHOGERANGROUP: LocalCellId=1/3/5X, InterRatHoGeranGroupId=1, InterRatHoGeranB1Hyst=2, InterRatHoGeranB1Thd=-94, InterRatHoGeranB1TimeToTrig=640ms;
ADD INTERRATHOUTRANGROUP: LocalCellId=1/3/5X, InterRatHoUtranGroupId=1, InterRatHoUtranB1ThdEcn0=-24, InterRatHoUtranB1ThdRscp=-95, InterRatHoUtranB1Hyst=2, InterRatHoUtranB1TimeToTrig=320ms;
MOD INTERRATHOUTRANGROUP: LocalCellId=1/3/5X, InterRatHoUtranGroupId=1, InterRatHoUtranB1ThdEcn0=-24, InterRatHoUtranB1ThdRscp=-95, InterRatHoUtranB1Hyst=2, InterRatHoUtranB1TimeToTrig=320ms;
MOD CELLSTANDARDQCI:QCI=QCI1,LOCALCELLID=1/3/5X,INTERRATHOCOMMGROUPID=1,QCIPRIORITYFORHO=1,INTERRATHOGERANGROUPID=1,INTERRATHOUTRANGROUPID=1;
MOD CELLSTANDARDQCI:QCI=QCI5,LOCALCELLID=1/3/5X,QCIPRIORITYFORHO=2;
SmartPreallocation Activation for the trial area if, improvement
observed , can activate on whole netwrok..
With SmartPreallocation Latency can decrease more than 10 percentage as

well.
Smart Preallocation-UL Scheduling Improvement
- Users will be preallocated during Preallocation period. This period will be restarted every time the UE receives a DL packet. The
preallocation periodicity determines the period between two UL grants.
- When the UE is assigned with UL grants but has no data to transmit still need to send “dummy” bits.
Smart Preallocation-UL Scheduling Improvement
Pros:
 Reducing network latency measurements by 5-10 ms approximately.
 Increasing UL 1M average throughput and decreasing the upload average time (around 10%).
 Slightly decreasing Call Setup Time by 8 ms approximately.
 Improving PS Call Drop Rate by 25% according to network KPIs.
Cons:
 Increase UE Battery consumption. The parameters have been adjusted not to impact UE Battery consumption. We will request a battery
consumtion test from QA to confirm.
 Slightly Increase UL Interference depending on the settings (possible impact in UL&DL average network throughput).
 Increase the resources used in DL for PDCCH so less available resources for PDSCH which can impact downlink cell throughput.
MML Commands:
MOD CELLULSCHALGO:LOCALCELLID=14,SMARTPREALLOCATIONDURATION=50,SMARTPREALLOCDURAFORSPARSE=100,PreAllocationBandwidthRatio=25;
MOD CELLALGOSWITCH:LOCALCELLID=11,ULSCHSWITCH=PreAllocationSwitch-1&SmartPreAllocationSwitch-1;
 Trial has been performed in XXXXXXXX City Center and 14ms improvement observed. This is over expectations. Expectation
was 5-10ms. It is under investigation If there is another improvement in transport network.
.
CSFB Fine Tuning (RIM Nei Strategy)
Bugüne kadar Huawei tarafından RIM komşulukları topolojiye göre yapılıyordu. CSFB RIM den faydalandığı taktirde CST da 1 sn lik iyileşme sağlanıyor.
CSFB RIM kullanım oranını artırabilmek amacı ile 3G-3G komşuluk sayılarına göre komşuluk belirleyerek Ankara ve Konyada deneme yapıldı, CSFB ile olan
attemplerde RIM kullanımı % 10-20 civarında arttığı görülmüştür.
Kendi bölgelerinizde bu işlemi yapmak için;
 LTE cell in co3G cellinin F1 i ve bu cellin en cok handover yaptıgı 7 tane F1 cell ini belirlemek. (Toplam 8 cell)
 Bu 8 cell in LTE cell e komşu olup olmadığını belirleyerek, değilse komşu olarak eklemek.
 Sonrasında yukarıda belirlenen 8 cell için UTRANNCELL altında BlindHoPriority = 32 yaparak, kalan diğer komşular için BlindHoPriority = 0 yapmak.
İstatistik kontrolünü aşağıdaki counterlar ile yapabilirsiniz.

VS.RRC.AttConnEstab.WithSI.CsDomain / (RRC.AttConnEstab.TmConvCall + RRC.AttConnEstab.EmgCall + RRC.AttConnEstab.OrgConvCall +
RRC.AttConnEstab.CallReEst)
Symbol Power Saving Feature Trial
 Symbol power saving enables the eNodeB to turn off PAs during the periods for the symbols that do not contain any data to
transmit.
 For each cell, the eNodeB dynamically checks for empty symbols within each subframe and shuts down PAs within these
symbols
As shown in this figure, symbols 1, 2, 3, 5, and 6 in each timeslot do not contain

any data to transmit. Therefore, during these symbols, PAs can be turned off to
save power
MML Command:
MOD ENODEBALGOSWITCH: PowerSaveSwitch=SymbolShutdownSwitch-1;
Between %5 - % 8 energy
saving per area
3GPP Evolution
LTE requirements and targets
Reduced delays, in terms of both connection establishment (less then 100ms) and
transmission latency (less then 10ms)
Increased user data rates: (Peak data-rate requirements are 150 Mbit/s and 50 Mbit/s for
downlink and uplink respectively, when operating in 20MHz allocation) (with MIMO)
Improved spectral efficiency
MIMO is supported by LTE, basically this is Spatial multiplexing which can increase data
rate prominently
Supporting flexible spectrum allocation (1.4, 3, 5, 10, 15 and 20 MHz) to meet the
complicated spectrum situation requirement
Multi-Antenna Technique -- MIMO
Receive diversity: Transmit diversity: Multi-antenna reception
SIMO MISO and transmission: MIMO
Fundamentals of MIMO:
 The data to be sent will be divided into multiple concurrent data streams.
 The data streams are simultaneously transmitted from multiple antennas through the spatial
dimensions, through different radio channels, and received by multiple antennas.
 And then can be restored to the original data according to the spatial signature of each data
stream.
LTE Frequency Bands
In LTE, ten 1 ms subframes compose a 10 ms frame. Each subframe divides into two slots.
The smallest modulation structure in LTE is the Resource Element. A Resource Element is
one 15 kHz subcarrier by one symbol. Resource Elements aggregate into Resource Blocks. A
Resource Block has dimensions of subcarriers by symbols. Twelve consecutive subcarriers in
the frequency domain and six or
seven symbols in the time domain form each Resource Block.
The number of symbols depends on the Cyclic Prefix (CP) in use. When a normal CP is used,
the Resource Block contains seven symbols. When an extended CP is used, the Resource
Block contains six symbols. A delay spread that exceeds the normal CP length indicates the
use of extended CP.
Transmission Bandwidth is the number of active Resource Blocks in a transmission. As the
bandwidth increases, the number of Resource Blocks increases. The Transmission
Bandwidth Configuration is the maximum number of Resource Blocks for the particular
Channel Bandwidth. The maximum occupied bandwidth is the number of Resource Blocks
multiplied by 180 kHz.
LTE Frequency Bands
Lte EARFC calculater usable in below links..

http://niviuk.free.fr/lte_band.php
Basic Data Configuration
Name & Numbering Rule
MO Band Sector 1 Sector 2 Sector 3 Sector 4

L800 11 12 13 14
L1800 31 32 33 34
Cell ID / Locell ID L2600 51 52 53 54
L900 71 72 73 74
L2100 91 92 93 94
L800 40 41 42 43
L1800 60 61 62 63
Sector ID / Sector Equipment ID L2600 80 81 82 83
L900 100 61 62 63
L2100 120 81 82 83
L800 40 41 42 43
L1800 60 61 62 63
RRU Chain No. L2600 80 81 82 83
L900 100 101 102 103
L2100 120 121 122 123
L800 100 101 102 103
L1800 120 121 122 123
RRU Subrack No. L2600 140 141 142 143
L900 160 161 162 163
L2100 180 181 182 183
Radio Data Configuration-1
If a board which is used to process baseband signals needs to be specified for a cell, run the ADD BASEBANDEQM command to add baseband equipment. In this step,
set UMTS UL Demodulation Mode to NULL(NULL) and it is good practice to set Baseband Equipment Type to ULDL(Combined UL and DL) because uplink and
downlink resource groups are combined for LTE cells.
Burada Antenna channel seçilirken ilgili RRU tipinin datasheet’ine bakmakta fayda var.
RRU’nun Rx ve Tx channel desteğine göre set edilmelidir.
2T2R Sector Configuration

Radio Data Configuration-2
2T4R Sector Configuration (Based on RRU/RFU Type)
Burada Antenna channel seçilirken ilgili RRU tipinin datasheet’ine bakmakta fayda var.
RRU’nun Rx ve Tx channel desteğine göre set edilmelidir.

Radio Layer Basic Concept
 Same SSS with PSS = 0, 1, 2

preferred in cells of same
eNB
 Same PCI can be used for

cells of same sector with
different freq
Once UE knows the PCI for a given cell, it also knows the location of cell Reference signals. Reference signals are used in channel estimation, cell selection / reselection
and handover procedures.
Cell Data Configuration example-1
2T2R Cell Configuration
E- DL UL UL
Package DL
UTRAN Bandwidth Frequency Frequency EARFC BW CP Length BW
name EARFCN
Band (MHz) (MHz) N
A1 20 (UL: 842-852 , DL: 801-811) 806 6300 847 24300 10Mhz Normal 10Mhz
C3 3 (UL: 1774.9-1784.9 , DL: 1869.9-1879.9) 1874,9 1899 1779,9 19899 10Mhz Normal 10Mhz
E2 7 (UL: 2525-2540 , DL: 2645-2660) 2652,5 3075 2532,5 21075 15Mhz Normal 15Mhz
Cell Data Configuration example -2
Preamble Format & Root Sequence Index
 Several UEs will access PRACH at the same time

 3GPP designed PRACH to provide 64 codes for simultaneous access
 The PRACH area removes capacity from the uplink access. 3GPP reserved
6 PRBs x 1 to 3 subframes for the Random Access.
Preamble format:
 3GPP specifies 5 Formats for the Preamble

 To accommodate larger cells a 2 and 3 subframes formats were created
 In some of the formats the preamble symbol is repeated twice, so it can be more easily detected
Preamble Format & Root Sequence Index
 The 64 preambles are not implicitly communicated to
the UEs by the eNodeB but rather, the UE is informed
about the process of how to generate them via
parameters broadcast in SIB2.
 3GPP specifies 838 root sequences (with 839 symbols
each)
 One root sequence can generate several preambles. One
or more root sequences are needed to generate all
preambles in a cell.
 Neighbor cells should use different orthogonal codes to
avoid intercell interference
 Larger cell sizes require the use of more than one Root
Sequence
3GPP specifies 838 root sequences (with 839 symbols each)

• Each cells has 64 preamble sequences, created by equally
spaced shifts
– There are 838 cyclic shifts of a Root Sequence (1 shift ≈ cell
range of 143 m) 120km/838
– To generate 64 sequences the shift between sequences must
be 13 sub-carrier symbols
– This corresponds to a cell size of 0.76 km
Cell – Sector Equipment mapping

Reference signal power: Indicates the reference signal power of the cell sector device.
The value 32767 indicates that this reference signal power parameter is invalid. In this
case, the reference signal power of the cell equals the value of the PDSCHCfg parameter.
For details, see 3GPP TS 36.213.This parameter is valid only when a multi-RRU cell works
in SFN,MPRU_AGGREGATION or cell combination mode.
Cell – TAC mapping (CNOPERATORTA)
Baseband equipment ID: When this parameter is set to 255, the baseband equipment
serving a cell is not specified. In this scenario, the LTE baseband processing units
(LBBPs) serving a cell are selected among all LBBPs in the eNodeB, and the LBBPs to
which the cell's serving RRU is connected are preferentially selected.
When this parameter is set to a value other than 255, the cell is served by LBBPs in the
specified baseband equipment, and the LBBPs to which the cell's serving RRU is
connected are preferentially selected.
Power Setting
MME configure number: Indicates the number of MMEs configured for a cell. This
parameter specifies whether to support the TDD/FDD cell configured with dedicated
MME scenario.
When this parameter is set to 0, the TDD/FDD cell configured with dedicated MME
scenario is not supported, and no MME can be configured for a cell.
When this parameter is set to a value between 1 and 4, the TDD/FDD cell configured
with dedicated MME scenario is supported, and the number of MMEs for a cell can be
configured according to the parameter value. An MME is uniquely specified by the MME
group identifier (MMEGI) and MME code (MMEC).
Basics of DL power allocation
Power control for the PDSCH, OFDM symbols in one slot can be classified into type A and type B:
 Type A symbols are those that appear during a symbol period when there is no reference signal.
 Type B symbols are those that appear during a symbol period when there are reference signals.
The transmit power for the two types of OFDM symbols on the PDSCH is defined by PPDSCH_A and PPDSCH_B.
The calculation formulas are as follows:
 PPDSCH_A = ρA + ReferenceSignalPwr
 PPDSCH_B = ρB + ReferenceSignalPwr
 For all PDSCH transmission schemes except multi-user MIMO and UE without 4 cell-specific antenna ports,
ρA = PA. PA is sent to the UE by means of RRC signaling for PDSCH demodulation.
 ρB depends on the power factor ratio ρB/ρA. Table lists the values of the cell-specific ratio ρB/ρA
corresponding to different PB values in scenarios with different quantities of antenna ports. PB is set using
the Pb parameter.
Bizdeki durum 2or4 Antenna için geçerli. Normalde Huawei bu durumda

Pb=1 PA=-3 öneriyor. Ancak burada özellikle initial şebeke için Pb=0 PA=0
önermişler. Huawei öneri olarak trafik %30-40 civarında ise 0-0 yap;
trafik>50% ise 1-(-3) yap diyor. En başta trafik az olduğu için bizim
interference’ımız reference signal kaynaklı olacak, o yüzden bu şekilde
reference signal gücünü diğer data PDCSH’lerden daha az yapmış oluyoruz.
Örn data için olanlar 5/4 oluyor , reference signal ise 1 oluyor.
Power Setting example -1
RS Power=10*LOG10((Port Power*1000)/(RB Number*12))-(PA)
Parameter MML Command 900(3M) 800(10M) 1800(10M) 2600(15M) Remark
MOD
PaPcOff DB0_P_A DB0_P_A DB0_P_A DB0_P_A
CELLDLPCPDSCHPA
No power boosting for RS

Pb 0 0 0 0
MOD PDSCHCFG
ReferenceSignalPwr 16.0 18.2 18.2 16.5
SchPwr MOD CELLCHPWRCFG 0 , 16 0 , 18.2 0 , 18.2 0 , 16.5 SCH
PbchPwr MOD CELLCHPWRCFG 0 , 16 0 , 18.2 0 , 18.2 0 , 16.5 PBCH
PchPwr MOD CELLCHPWRCFG 3 ,19 3 , 21.2 3 , 21.2 3 ,19.5 PCH
DediDciPwrOffset MOD CELLDLPCPDCCH 0 , 16 0 , 18.2 0 , 18.2 0 , 16.5 PDCCH
PcfichPwr MOD CELLCHPWRCFG 0 , 16 0 , 18.2 0 , 18.2 0 , 16.5 PCFICH
PwrOffset MOD CELLDLPCPHICH 3 , 19 3 , 21.2 3 , 21.2 3 , 19.5 PHICH
RaRspPwr MOD CELLCHPWRCFG 3 , 19 3 , 21.2 3 , 21.2 3 , 19.5 RAR

Power Setting example -2
Neighboring Cell Overview
Neighboring Cell Configuration-1
eNodeB ID : Indicates the eNodeB identity of the external E-UTRAN cell. It uniquely identifies an eNodeB within a PLMN. The 28-bit E-UTRAN cell identity is
comprised of the cell identity and the eNodeB identity (represented by the most significant 20 bits). The cell global identity (CGI) of an E-UTRAN cell is comprised of
the E-UTRAN cell identity and the PLMN ID. For details, see 3GPP TS 36.413.
A maximum of 2304 external E-UTRAN cells can be configured for an eNodeB.
The total number of intra- and inter-frequency neighboring cells configured for an E-UTRAN cell cannot exceed 256.
E-UTRAN intra-frequency neighbor:

For 1800M
For 800M
A maximum of eight neighboring E-UTRAN frequencies can be configured for an E-UTRAN cell. (EUTRANINTERNFREQ)
A maximum of 2304 external E-UTRAN cells can be configured for an eNodeB.
The total number of intra- and inter-frequency neighboring cells configured for an E-UTRAN cell cannot exceed 256.
E-UTRAN inter-frequency neighbor: example for 800M => 1800M

UTRAN neighbor:
A maximum of 16 neighboring UTRAN frequencies can be configured for each E-UTRAN

cell. (UTRANNFREQ)
A maximum of 2304 external UTRAN cells can be configured for an eNodeB.
A maximum of 128 neighboring relations with UTRAN cells can be configured for each E-
UTRAN cell.
CS and PS handover indicator: Indicates whether the external UTRAN cell supports single radio
voice call continuity (SRVCC) for concurrent CS and PS services. If this parameter is set to
BOOLEAN_FALSE, the external UTRAN cell does not support SRVCC for concurrent CS and PS
services.
Cell Measure Priority: Indicates the priority of measurement on the neighboring UTRAN cell.
The eNodeB preferentially contains the information about a neighboring cell with this priority set
to HIGH_PRIORITY while delivering a measurement configuration. In the measurement
configuration for an inter-RAT handover to UTRAN, the eNodeB includes information about a
limited number of neighboring UTRAN cells. If this parameter is set to HIGH_PRIORITY, it is
more likely that this neighboring cell is included in the measurement configuration.
Overlap Indicator: Indicates whether the neighboring UTRAN cell is manually identified as a
neighboring cell overlapping the E-UTRAN cell. The default value is NO. The parameter value
YES indicates that the neighboring UTRAN cell is manually identified as a neighboring cell
overlapping the E-UTRAN cell. The parameter value NO indicates that the neighboring UTRAN
cell is not manually identified as a neighboring cell overlapping the E-UTRAN cell.
GERAN neighbor:

A maxim um of 16 neighboring GERAN carrier frequency groups
can be configured for each E-UTRAN cell. A GeranNfreqGroup MO
consists of the parameters related to a neighboring GERAN frequency
group. The configuration of this MO is shared by all frequencies in the
group, and is used in measurement control for inter-RAT handovers to
GERAN and also used for inter-RAT cell reselections to GERAN.
Starting ARFCN: Indicates the first ARFCN in the GERAN carrier
frequency group.
Band indicator: Indicates the GERAN band indicator. If the GERAN
ARFCN is between 512 and 810, this parameter indicates whether the
GERAN ARFCN is in the 1800 MHz band or the 1900 MHz band. If the
GERAN ARFCN is not in either band, this parameter does not take
effect and can be set to either value and one ARFCN can only in one
frequency band.
Frequency Priority for Connected Mode: Indicates the frequency
group priority based on which the eNodeB selects a target frequency
group for blind redirection or delivers a frequency group in
measurement configuration messages. If a blind redirection is triggered
and the target neighboring cell is not specified, the eNodeB selects a
target frequency group based on the setting of this parameter. If a
measurement configuration is to be delivered, the eNodeB
preferentially delivers the frequency group with the highest priority. If
this parameter is set to 0 for a frequency group, this frequency group is
not selected as the target frequency group for a blind redirection. A
larger value indicates a higher priority.
A maximum of 31 neighboring GERAN ARFCNs can be

configured under each neighboring GERAN carrier frequency
group of an E-UTRAN cell. A maximum of 64 neighboring GERAN
ARFCNs can be configured for each E-UTRAN cell, including the
first GERAN ARFCNs and other GERAN ARFCNs in the
neighboring GERAN carrier frequency groups.
A maximum of 1152 external GERAN cells can be configured for

an eNodeB.
A maximum of 64 neighboring relations with GERAN cells can be

configured for each E-UTRAN cell.
Neighboring Cell Configuration-4 LTE neighbor in RNC:
An RNC can be configured with up to 9600 LTE cells.
EUTRAN Cell Identity: This parameter is used to uniquely

identify an LTE cell in the PLMN. EutranCellId consists of
eNodeBID of 20 bits and CellID of 8 bits, that is
EutranCellId=eNodeBID x 256 + CellID. For details about
the parameter description, see 3GPP TS 36.300.
The RNC can be configured with a maximum of 163200 LTE

neighbor relationships.
If two LTE cells have the same values in CellPHYID and LTE neighbor in BSC:
LTEArfcn, cannot configure them as the neighboring cells
for one UMTS cell. Because the RNC cannot discover a
unique neighboring LTE cell based on the physical ID and
downlink frequency of the LTE cell in the event report.
CellPHYID and LTEArfcn are configured by ADD ULTECELL.
Each UMTS cell supports up to 96 neighboring LTE cells.
A maximum of 10240 neighboring LTE external cells can

be added using this command for a BSC.
All the neighboring LTE cells of a GSM cell operate

on a maximum of 8 frequencies, and each frequency can
be configured with a maximum of 16 neighboring cells that
do not support cell reselection.
Carrier Aggregation Evolution EDGE+ HSPA+ LTE-A
Dual Carriers in DC-HSDPA Carrier Aggregation
Downlink
300 Mbit/s (2CC
20Mhz)
Carrier aggregation is used in LTE-Advanced in order to 450 Mbit/s (3CC
increase the bandwidth, and thereby increase the 20Mhz)
bitrates
84 Mbit/s
(4C HSPA)
984 kbit/s
CC – Component Carrier
Based on 3gpp:
Max CC number – 5
CC BW – 1.4, 3, 5, 10, 15, 20 M
Carrier Aggregation Introduction-1
Band 1
LTE Carrier 1 LTE Carrier 2 LTE Carrier 3 f
Combined LTE Carrier 1 and LTE

Intra-Band, Contiguous
Carrier 2
LTE-A Carrier LTE Carrier 3 f
Band 1
Operator 1 Operator 2 Operator 1

f
LTE Carrier 1 LTE Carrier 2 LTE Carrier 3
Intra-Band, Non-
Combined LTE Carrier 1 and LTE Carrier 3 Contiguous
Operator 1 Operator 2 Operator 1 f
LTE-A Carrier LTE Carrier 2 LTE-A Carrier
Band 1 Band 2
LTE Carrier 1 LTE Carrier 2 f

Inter-Band, Non-Contiguous
LTE Carrier 1 in Band 1 Combined LTE Carrier 2 in Band 2
f
LTE-A Carrier LTE-A Carrier
Carrier Aggregation Introduction-2
Primary and Secondary serving cells. Each component carrier corresponds to a serving cell.
The different serving cells may have different coverage, useful for heterogeneous cell-planning.
Huawei Supported Carrier Aggregation

Bands
7 (2.6GHz) + 3 (1.8GHz) •Band7 {10, 15, 20}

•Band3 {5, 10, 15, 20}
7 (2.6GHz) + 20 •Band7{10, 15, 20}
(800MHz) •Band20 {5, 10}
3 (1.8GHz) + 20 •Band3 {5, 10, 15, 20}
(800MHz) •Band20 {5, 10}
3 (1.8GHz) + 7 (2.6GHz) •Band3 {5, 10, 15, 20}
+ •Band7{10, 15, 20}
20 (800MHz) •Band20 {5, 10, 15, 20}
Carrier Aggregation Configuration-1
CA Between 800M & 1800M
 MOD ENODEBALGOSWITCH:CAALGOSWITCH=PdcchOverlapSrchSpcSwitch-1&CaCapbFiltSwitch-0&PccAnchorSwitch-1&SccBlindCfgSwitch-1&
FreqCfgSwitch-0&SccA2RmvSwitch-1&CaTrafficTriggerSwitch-0&HoWithSccCfgSwitch-0&SccModA6Switch-0&GbrAmbrJudgeSwitch-0;
 ADD
EUTRANINTERNFREQ:LOCALCELLID=11,DLEARFCN=1899,ULEARFCNCFGIND=NOT_CFG,CELLRESELPRIORITYCFGIND=CFG,CELLRESELPRIORITY=6,SPEEDDEPENDSPCFGIND=NOT_CFG,MEASBANDWIDTH=
MBW50,PMAXCFGIND=NOT_CFG,QQUALMINCFGIND=NOT_CFG;
 ADD
EUTRANINTERNFREQ:LOCALCELLID=31,DLEARFCN=6300,ULEARFCNCFGIND=NOT_CFG,CELLRESELPRIORITYCFGIND=CFG,CELLRESELPRIORITY=5,SPEEDDEPENDSPCFGIND=NOT_CFG,MEASBANDWIDTH=
MBW50,PMAXCFGIND=NOT_CFG,QQUALMINCFGIND=NOT_CFG;
 ADD EUTRANINTERFREQNCELL: LocalCellId=11, Mcc="286", Mnc="02", eNodeBId=72735, CellId=31;

 ADD CAGROUP: CaGroupId=0, CaGroupTypeInd=FDD;
 ADD CAGROUPCELL: CaGroupId=0, LocalCellId=11, eNodeBId=72735, PreferredPCellPriority=7;

 ADD CAGROUPSCELLCFG: LocalCellId=11, SCelleNodeBId=72735, SCellLocalCellId=31, SCellBlindCfgFlag=TRUE, SCellPriority=6;

PreferredPCellPriority in CaGroupCell can be set (0~7), 0 by default, 7 is

highest
Only effective when UE initiates a RRC connection
IFHO to preferred PCC with highest priority based on A4 measurement
CA Between 800M & 1800M & 2600M – Flexible CA from Multiple Carriers
 ADD
EUTRANINTERNFREQ:LOCALCELLID=11,DLEARFCN=1899,ULEARFCNCFGIND=NOT_CFG,CELLRESELPRIORITYCFGIND=CFG,CELLRESELPRIORITY=6,SPEEDDEPENDSPCFGIND=NOT_CFG,
MEASBANDWIDTH=MBW50,PMAXCFGIND=NOT_CFG,QQUALMINCFGIND=NOT_CFG;
 ADD
 ADD
 ADD
 ADD
 ADD

 ADD EUTRANINTERFREQNCELL: LocalCellId=51, Mcc="286", Mnc="02", eNodeBId=72735, CellId=31; Flexible 2CC CA from three carriers is based on UE capability and carrier managem
principle.
 ADD CAGROUP: CaGroupId=0, CaGroupTypeInd=FDD; Choose cell with highest SCellPriority as SCell among candidate SCells.
Blind configurable SCell is preferred among all candidate SCells with
 ADD CAGROUPCELL: CaGroupId=0, LocalCellId=11, eNodeBId=72735, PreferredPCellPriority=7; identical priority
CA Between 800M & 1800M & 2600M – Flexible CA from Multiple Carriers

 ADD CAGROUPSCELLCFG: LocalCellId=11, SCelleNodeBId=72735, SCellLocalCellId=51, SCellBlindCfgFlag=FALSE, SCellPriority=7;
 ADD CAGROUPSCELLCFG: LocalCellId=31, SCelleNodeBId=72735, SCellLocalCellId=51, SCellBlindCfgFlag=FALSE, SCellPriority=7;
CA Between 800M & 1800M & 2600M –CA for Downlink 3CC
Addition to Flexible CA from Multiple Carriers:

 MOD CAMGTCFG:LOCALCELLID=11,CELLCAALGOSWITCH=CaDl3CCSwitch-1;
Flexible 2CC CA from three carriers is based on UE capability and carrier management
principle.
Choose cell with highest SCellPriority as SCell among candidate SCells.
Blind configurable SCell is preferred among all candidate SCells with
identical priority
License Management-1
License Management-2
LTE Idle signaling SIB messages details.
Scheduling of SIBs
3900 Series Base Station Types
BBU3900 & BBU3910 Boards
UMPT Board & Main Functions
UMPT can support 4 Modes Concurrency

(GULT)
Support GUL Co-transmission
High signalling capability
The UMPT performs the following

functions:
• Controls and manages the entire base station
in terms of configuration, equipment,
performance monitoring, radio resources, and
active/standby switchovers.
• Processes signaling messages.
• Provides a reference clock, transmission ports,
and an OM channel to the LMT or U2000.
• Interconnects two BBU3900s with UCIU
boards and exchanges control information,
transmission information, and clock
information between them.
UMPT Board & Main Functions
UMPT Board Ports

UBBP Board & Main Functions
The UBBP performs the
following functions:
 Provides CPRI ports for

communication with the
RF modules.
 Provides a port for
interconnection with
another baseband board
to share the baseband
resources.
UBBP Board can support Multi-mode concurrency in one Board.

SW Configurable for a specific RAT, among GULT 4 RATs
Up to GUL 3 RATs concurrency
Max Capacity ( 1024 CE(U)/6*20M 4T4R(L)/48TRX(G)
Support 12 cells resource group in the UL
Other Boards in BBU
Blade RRU
Site Type Selection
L800 L80 YES
0 Free space for LTE-
START or
RRU?
DBS3900 1
L900?
L90 NO
0
Is there any existing YES

BTS3900x with free Existing BTS3900x 2
slots?
NO
YES
Is there any free space 3
New BTS3900L
for new BTS3900L?
NO
Is there any free space YES

to swap BTS3900 with Swap to BTS3900L 4
BTS3900L?
NO
New BTS3900 5
Existing Cabinet 6
BTS3900L Advantage
BBU Configuration-FlowChart
Change WMPT with UMTb2

Free Space in BBU Change UEIU with UPEUc
Existing YE
Connect 3G and 4G to UMPTb2
for addition S 1
Cabinet or Existing BBU Add UBBPd3/UBBPd6 for LTE
UBBPd3/UBBPd6
DBS3900 carriers
? Connect LTE RRUs/RFUs to
UBBPd3/UBBPd6
*Details are in page-4-5
N
O
Change WBBPb2 with UBBPd3 for

3G
Is there any Change WMPT with UMTb2
YE Change UEIU with UPEUc
WBBPb2 can be S
START change with
Connect 3G and 4G to UMPTb2 2
Add UBBPd3/UBBPd6 for LTE
UBBPd3 for 3G? carriers
Connect LTE RRUs/RFUs to
UBBPd3/UBBPd6
NO
*Details are in page-6
Add new UMTb2

Connect 4G to UMPTb2
New Cabinet Add New BBU
Add UBBPd3/UBBPd6 for LTE 3
carriers
Connect LTE RRUs/RFUs to
UBBPd3/UBBPd6
*Details are in page-7

BBU Configuration-1-a
1) If there are free slots in existing BBU:
a) If one UBBPd6 will be enough for LTE: First UBBPd6 can be installed in any
free slot in BBU.
Existing BBU Configuration Updated BBU Configuration

UBBPd3/UBBP
d6 UPEUc
UEIU
FANc GTMU FANc GTMU
WBBPf3 WBBPf3
UPEUc UPEUc
WBBPd2 WMPT WBBPd2 UMPTb2
 Change WMPT with UMPTb2

 Change UEIU with UPEUc
 Connect 3G and 4G to UMPTb2
 Add first UBBPd3/UBBPd6 for LTE carriers in any slot
 Connect LTE RRUs/RFUs to UBBPd3/UBBPd6
BBU Configuration-1-b
1) If there are free slots in existing BBU:
b) If second UBBPd6 will be needed for LTE: Second UBBPd6 should be installed in slot-2 or slot-3.
UBBPd3/UBBPd
UEIU 6 UPEUc
FANc GTMU FAN WBBPd2
GTMU
WBBPd2 UBBPd6
UPEUc UPEUc
WBBPf3 WMPT UMPTb2
WBBPF3

 Add First UBBPd3/UBBPd6 in slot-2
 Add Second UBBPd6 in any free slot
BBU Configuration-2-a
2) If there are no free slots in existing BBU:
a) If there is WBBPb2 in BBU: WBBPb2 should be changed with WBBPf3 or UBBPd3
Updated BBU Configuration

Existing BBU Configuration
UBBPd3/UBB
WBBPb2 UBRI (G-BRI) Pd6 UBRI (G-BRI) UPEUc
UEIU
WBBPd2 WBBPd2
FANc GTMU FANc GTMU
WBBPf3/UBB
WBBPb2 Pd3
UPEUc UPEUc
WBBPd2 WMPT WBBPd2 UMPTb2
UBBPd6 can be installed in any free slot in BBU.
 Change WBBPb2 with UBBPd3 for 3G

 Add UBBPd3/UBBPd6 for LTE carriers
BBU Configuration-2-b
2) If there are no free slots in existing BBU:
b) If there is no any WBBPb2 in BBU: New BBU will be needed for 4G
WBBPd/f UBRI (G-BRI)
UEIU
WBBPd/f
Existing BBU Configuration FANc GTMU
WBBPd/f
WBBPd/f UBRI (G-BRI) UPEUc
UEIU WBBPd/f WMPT
WBBPd/f
FANc GTMU New BBU Configuration
WBBPd/f
UPEUc
WBBPd/f WMPT UEIU
FANc
UBBPd3/UBB UPEUc
It will better to use slot-2 or slot-3 for UBBPd6 in new BBU. UMPTb2
Pd6
 Add new UMPTb2

 Connect 4G to UMPTb2
 Add UBBPd3/UBBPd6 for LTE carriers
UBBPd Boards Capacity
GO
(GSM UO (UMTS Only) LO (LTE Only) Multi-mode concurrency
Only)
Model RRC
Cell
HSDPA/ connec
(TRX) UL/DL CE Cells configuratio DL/UL rate GU GL UL/GUL
HSUPA ted
n
user
12TRX+192/256
UBBPd1 24 384/512 6 288/288 NA NA NA
Board Capacity in Different Modes: CE
12TRX+256/384
UBBPd2 24 512/768 6 384/384 NA NA NA
CE
12TRX+192/256 12TRX+3*10M2T
UBBPd3 24 384/512 6 288/288 3*20M 2T2R 450/225 3600 NA
CE 2R
12TRX+256/384 12TRX+3*10M2T
UBBPd4 24 512/768 6 384/384 3*20M 4T4R 600/225 3600 NA
CE 2R
18TRX+384/512 18TRX+3*20M4T
UBBPd5 36 768/768 6 512/512 6*20M 2T2R 600/300 3600 NA
CE 4R
UL:512/768CE+3*20
M4T4R
1024/102 24TRX+512/768 24TRX+3*20M4T
UBBPd6 48 12 768/768 6*20M 4T4R 900/450 3600 GUL: 12TRX +
4 CE 4R
256/384CE +
3*20M4T4R
• LTE-800MHz Site is planned with UBBPd6.

• UBBPd6 will be used as LO Mode in LTE Site.
• LTE-900MHz Site is planned with UBBPd3 or UBBPd6.
• UBBPd3 will be used instead of WBBPf3 for UMTS Site
• UBBPd3 will be used as UO mode in UMTS.
RRU – BBU Connection for LTE-800 and LTE-900 Site
LTE-800/UMTS2100/GSM900: LTE-900/UMTS2100/GSM900:
 UMPTb2 has 2 FE ports and to seperate transmission of 3G and 4G is possible.

 If different BBU will be used for 4G, trasnmission of 4G will be different from 3G
automatically.
 3G and 4G will be in same M2000.
RRU – BBU Connection for LTE site with Carrier Aggregation
LTE-800/1800/2600/UMTS2100/GSM900:
LTE-800/1800/UMTS2100/GSM900:
 UMPTb2 has 2 FE ports and to seperate transmission of 3G and 4G is possible.

 If different BBU will be used for 4G, trasnmission of 4G will be different from 3G
automatically.
 3G and 4G will be in same M2000.
RRU Specification
Specification of most common LTE RRUs:
√
Typical Power Max Power Dimension (H x Weight
Band Type TX&RX Power Mode Consumption Consumption W x D) (mm) (kg)
800M √ RRU3268 2T2R 2*40W L 845W 1085W 400x300x100 ≤ 14
1800M √ RRU3959 2T2R 2*60W GO/LO/GL 955W 1220W 400x300x100 14.4
1800M RRU3953 2T4R 2*80W (GO:2*60W) GO/LO/GL 865W 1225W 400x300x150 20

√
Blade RRU
1800M RRU3971 4T4R 4*40W Will be available in 2016-Q1
2600M √ RRU3260 2T4R 2*40W L 860W 1100W 400x300x100 ≤ 14
2600M RRU3262 2T4R 2*60W L 988W 1318W 400x300x100 ≤ 14
2600M RRU3281 4T4R 4*40W Will be available in 2016-Q1
 800 MHz  Preferred RRU is RRU3268

 1800 MHz  Preffered RRU is RRU3953 and RRU3971
 2600 MHz  Preffred RRU is RRU3260 and RRU3281
Power Consumption in BBU-1
Specification of common UPEUs:
 UPEUa is a old technology,
Power √
 UPEUc is a common board
1 UPEUa 300W
√  UPEUd will be deployed with BBU3910
1 UPEUc 360W
2 UPEUc 650W
1 UPEUd 650W
Power Consumption for boards in BBU:

BBU Max Common BBU Required
Power Config Power
Ver.C FAN 31W 1 31W
 According to common BBU config, 1 UPEUc will be not
UBBPd6 91W 2 182W
enough.
UBBPd3 91W
WBBPf4 91W  Second UPEUc addition have been given in next page.
WBBPf3 91W
WBBPd2 73W 2 146W
WBBPb3 30W
WBBPb2 26W
WBBPb1 26W
UMPTb2 42W 1 42W
GTMU 27W 1 27W
Required Power: 428W
Power Consumption in BBU-2
UPEU Requirement:
a) If there is UPEUa in BBU : A type UPEU should be changed with C type UPEU, than second UPEUc
can be added
UBBPd6 UBBPd2 UBBPd6 UBBPd2

UEIU UPEUc
UBBPd2 UBBPd2
FANa GTMU GTMU
WBBPf3 FANc WBBPf3
UPEUa
WBBPd6 UMPTb2 UPEUc
UMPTb2
WBBPd6
b) If there is UPEUc in BBU : Second UPEUc can be added
Updated BBU Configuration

UBBPd6 UBBPd2
UBBPd6 UBBPd2 UPEUc
UEIU UBBPd2
UBBPd2 GTMU
FANc GTMU FANc WBBPf3
WBBPf3
UPEUc UPEUc
WBBPd6 UMPTb2 UMPTb2
WBBPd6
LTE800+LTE1800+LTE2600 (2T2R) with Triple Band Antenna Example
Current Antenna Triple-band antenna.
790Mhz-960Mhz 1710Mhz -2180Mhz Port 790Mhz-960Mhz 1710Mhz -2180Mhz 1710Mhz -2690Mhz
GU900(SDR)
GSM900 +
UMTS2100
UMTS2100
2600
LTE 800
1800
L1800
LTE
Evolve
LTE
Blade RRU
AAU- Clean site solution
Active Antenna - Quickview
2.1 A + 1.8A + 1.8 ~ 2.6 P + 0.7~0.9 P

AAU3902 200 x 35 x 26 cm ; 65 kg ; 2x40 W
(3H1L) 12 EDT ; 3 MT; 65 HBW ; 10 VBW
2.1 A + 1.8 A + 2.6 P + 790~960 P

AAU3911 200 x 37 x 29 cm ; 65 kg ; 2x60 W
(3H1L) 10 EDT ; 8 MT; 65 HBW ; 10 VBW
 Compact equipment includes 3 H-1 L band antennas; 2 H Band RUs and RET system
 Vertical Beamforming features to increase UL or DL capacity

Mehmet TANIS LTE & WCDMA Optimization Expert +90 541 953 21 21 Skype Mehmet - Tanis

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Mehmet TANIS LTE & WCDMA Optimization Expert +90 541 953 21 21 Skype Mehmet - Tanis

Încărcat de

Drepturi de autor:

Formate disponibile

LTE

Difference among CA and DC.

F1 : 5 Mhz L 800 : 10 Mhz

Bandwidth HSPA ++ LTE

If there is 2X2 MIMO , possible to see 75 Mbps speed..

TEchnology HSUPA TTI Times

FEC : Forward error correction.. In the tems investigation page it s a HARQ..

 1 UE receives 14 symbols in 1 millisecond.

 1 UE has to get a minimum 12 Subcarrier ..

 It flows continuously at 1 millisecond and flows 15 kHz.

 1 Subframe 12 Subcarrier * 15 kHz = 180 Khz.

 7 symbol = 1 Resource block (RB). (Called as a slot ..)

 14 symbol = 1 is called PRB ..

 There are 2 slots 1 PRB ..

 There is 50 resource block at 10 MHz. 50 carrier at 50 Mhz. 50 * 180 = 9

RE = 1 symbol ( 15 khz of 1 millisecond )

1 slot will use 84 RE.

VOLTE Tput = bits/sn = 168*6 / 20 ms = 50.4

PCI = PSS + 3*SSS

SINR : Signal Used Interference Noice

 Transmission quality or capacity problems should be investigated. (Transport or Transmission units)

-3 and -20 .. -3 is the best.

When It goes straight to -20 , it means it

 Network plan , network structure diagram , site distribution, site

Areas to be optimized can be determined by comparing the distribution of

Topic Parameter SET0 example SET1 example

Coverage based Frequency priority based Coverage Based

L800-->L900 start search A2 interfreq -109 -86 -109

L900-->L800 start search A2 interfreq -104 -82 -104

L800-->L900 target threshold A4+Qoffsetfreqconn -101 -78 -101

L900-->L800 target threshold A4+Qoffsetfreqconn -105 -82 -105

Methodology Coverage based Coverage + Frequency priority based

Cell based interfreq

Reference Signal Received Power (RSRP)

Design KPI for RSRP:

Design KPI for RSRQ:

Design KPI for Overlapping Zones (Number of Servers):

DL Cell Edge User Throughput

Design KPI for DL Cell Edge User Throughput:

Check the generic hardware fault alarm , such as hardware with

Solution : Replace the faulty component..

To ensure the coverage the DL Power parameters should be properly

Check DL Power configuration

To ensure the coverage , the DL power parameters should be properly set

 RS Power = Maximum RRU power/channel-10log(totalsubcarriers)+10log(Pb+1)

 PDSCH Power = PA + RS Power

 LST PDSCHCFG : Check Pb and RS power setting

Check CPRI rate via below command ( DSP CPRLBR )

If S1 interface state is faulty , check the PLMN and operator ID.

Solution : Replace the faulty component..

Check the S1 interface status via below command DSP S1INTERFACE

Check the Cell Barred status LST CELLACCESS

If cell is barred , use the following cmmand to recover it

High RSSI causes by the interferences

Check the RF Channel Problem

* High Vswr : ALM-26529 Rf Unit Vswr Threshold Crossed

Cause Of High VSWR

 Vswr : Voltage Standard Wave Ration , indicate the if feeder

 Incorrect Rx attenuation setting

Solution for Low RSSI

How to Located Inter-modulated Interference

How to Located External Interference

 Drive test tracing analysis