RF TroubleShooting Guideline LA1.1

RF Troubleshooting Guideline LA1.
1
Document number: LTE/IRC/APP/032278
Document issue: V01.03 / EN
Document status: Approved Standard
Data classification: Internal
Date:09/Sep/2010
Alcatel-Lucent - Proprietary - Use pursuant to applicable agreements
Copyright 2010 Alcatel-Lucent, All Rights Reserved

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is write
protected; it may be altered only by authorized persons. While copies may be printed, it is not
recommended. Viewing of the master electronically ensures access to the current issue. Any hardcopies
taken must be regarded as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of AlcatelLucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information
contained herein confidential, shall disclose the information only to its employees with a need to know,
and shall protect the information from disclosure and dissemination to third parties. Except as expressly
authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained
herein. If you have received this document in error, please notify the sender and destroy it immediately.
RF Troubleshooting Guideline LA1.1
LTE Unit/ TIS-CEC/NPE
1 INTRODUCTION
The main interest of the document is to highlight the most used and know workaround
identified during LA1.1
1.1 SCOPE
The document covers the troubleshoot hints for the main RF features of Alcatel-Lucent LTE
release LA1.1
The procedures detailed in this document can be used to avoid long time debugging and
loose time during problems already face in the field.
1.2 AUDIENCE FOR THIS DOCUMENT

The audience of this document is typically involved in following activities:
Radio Network Design
Radio Network Optimization
Trials
2 PUBLICATION HISTORY
Version.Ed/
Language
01.01/EN
Status
Date
Name
27/May/2010
Draft
Sequeira Sergio
10/Jun/2010
Approved
preliminary
Reason of changes / short

description of significant
changes to previous edition
Creation
Jorge Santos
01.02/EN
Ricardo Costa
Reading Cycle Completed (DR4

Step)
Eman Moshneb
01.03/EN
09/Sep/2010
Approved
standard
Herv Julien
MAJCHER
DR.5 milestone
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 2/38
TABLE OF CONTENTS
1 INTRODUCTION ...........................................................................................................................2
1.1 SCOPE ...........................................................................................................................................2
1.2 AUDIENCE FOR THIS DOCUMENT ......................................................................................................2
2 PUBLICATION HISTORY .............................................................................................................2
3 REFERENCE DOCUMENTS ........................................................................................................7
4 WIPS .............................................................................................................................................7
4.1 WIPS RECOMMENDATIONS .............................................................................................................7
5 LLDM MASK .................................................................................................................................9
5.1 LOAD MASK....................................................................................................................................9
5.1.1 Short Description .................................................................................................................9
5.1.2 Proposed Tests....................................................................................................................9
6 ACCESSIBILITY .........................................................................................................................11
6.1 SLEEPING CELL ............................................................................................................................11
6.1.1 Short description ................................................................................................................11
6.1.2 Issue Description ...............................................................................................................12
6.1.3 Propose steps ....................................................................................................................12
6.1.4 Workaround .......................................................................................................................13
6.2 LAZY CELL ...................................................................................................................................14
6.2.2 Issue description ................................................................................................................14
6.2.3 Propose steps ....................................................................................................................15
6.2.4 Workaround .......................................................................................................................15
7 MOBILITY....................................................................................................................................16
7.1 RRC CONNECTION REESTABLISHMENT REJECT .............................................................................16
7.1.2.1
RRC Connection Reestablishment: .........................................................17
7.1.2.2
Tracking Area Update:.......................................................................17
7.1.3 Workaround .......................................................................................................................18

7.2 TCPACKFREQUENCY MODIFICATION ..............................................................................................18
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 3/38

7.2.3 Workaround .......................................................................................................................19
7.2.4 Important Notes /Comments: .............................................................................................21
8 STATIC TRANSPORT FIBER DELAY LENGHT........................................................................22
8.1 FIBER DELAY LENGTH CONFIGURATION ..........................................................................................22
8.1.3 CTC Examples ...................................................................................................................22
8.1.3.1
Comments: ....................................................................................23
8.1.3.2
Comments: ....................................................................................23
9 MULTI UE....................................................................................................................................23
9.1 UNFAIR UL THROUGHPUT SHARING ...............................................................................................23
9.1.2 Propose steps ....................................................................................................................23
9.1.4 Workaround .......................................................................................................................24
9.1.5 MU parameter setting.........................................................................................................24
9.1.5.1
UL Parameters ................................................................................24
9.1.5.2
DL Parameters ................................................................................25
10 NEIGHBOURS PLANNING AND CELL ID PLANNING ...........................................................25

10.1 NEIGHBORS PLANNING................................................................................................................25
10.1.1 Short description ..............................................................................................................25
10.2 CELL ID PLANNING .....................................................................................................................26
10.2.1.1
Comments: ....................................................................................27
10.3 RSRP CRITERIA.........................................................................................................................27

10.3.1.1
Comments: ....................................................................................28
10.4 DISTANCE CRITERIA....................................................................................................................28

10.4.1.1
Comments: ....................................................................................28
11 ANTENNA POSITIONING.........................................................................................................29
11.1.1.1
Comments: ....................................................................................30
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 4/38
12 FAQS.........................................................................................................................................30
12.1 HOW TO AVOID CALL DROP? ........................................................................................................30
12.1.1 Propose steps ..................................................................................................................31
12.2 THE SNR IS GOOD, BUT THE UE COULD NOT ATTACH. WHAT CAN BE DONE? ..................................31
12.2.1 Propose steps ..................................................................................................................32
12.3 THE SNR IS BAD EVEN UNDER THE SITE, AND THE UE COULD NOT ATTACH. WHAT CAN BE DONE?....32
12.3.1 Propose steps ..................................................................................................................32
12.4 NAMING OF THE PATCH FILE FOR PQ3..........................................................................................32
12.4.1 Propose steps to install a designer UPA, FPGA, or DSP image on the CEM..................33
12.5 RRHS SUPERVISION LOST ..........................................................................................................33
12.5.1 Propose workaround ........................................................................................................34
12.6 LA1.1 G711 CODEC ISSUE ..........................................................................................................34
12.6.1 Propose workaround ........................................................................................................34
12.7 WHICH PARAMETERS ARE NEEDED TO CHANGE IN ORDER TO ENABLE DIFFERENT TRANSMISSION
MODES?.............................................................................................................................................34
12.7.1 MIMO CLOSE LOOP full mode (3GPP 36.213 : 7.2 , 7.2.1.C) ......................................34
12.7.2 MIMO CLOSE LOOP Mixed mode...................................................................................35
12.7.3 MIMO OPEN LOOP .........................................................................................................36
12.7.4 TXDIV ..............................................................................................................................36
12.7.5 All modes comparison......................................................................................................36
13 CONCLUSION...........................................................................................................................37
14 ABBREVIATIONS AND DEFINITIONS.....................................................................................37
14.1 ABBREVIATIONS ..........................................................................................................................37
14.2 DEFINITIONS ...............................................................................................................................38
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 5/38
LIST OF FIGURES
Figure 4.1-1: WIPS parameter changes............................................................................................................ 8
Figure 4.1-2: WIPS work order export ............................................................................................................. 9
Figure 5.1-1: Log Mask Setting Dialog............................................................................................................ 10
Figure 5.1-2: CH1 MASK Load Information ..................................................................................................... 11
Figure 6.1-1: RRC Connection scenario call flow........................................................................................... 12
Figure 6.1-2: T300 expire .............................................................................................................................. 13
Figure 6.2-1: MAC RA Problem ....................................................................................................................... 14
Figure 6.2-2: RRC connection establishment procedure ............................................................................... 15
Figure 7.1-1: RRC Connection ReestablishmentReject.................................................................................. 16
Figure 7.1-2: No data throughput during HO phase....................................................................................... 18
Figure 7.2-1: TSHARK - UE Hardware Interface ID......................................................................................... 19
Figure 7.2-2: TCPoptimizer Edit Registry .................................................................................................... 20
Figure 7.2-3: TCPoptimizer Add DWORD ..................................................................................................... 20
Figure 7.2-4: TCPoptimizer Modify Value.................................................................................................... 21
Figure 8.1-1: Cell 50 in Site 16 (Expo Axis) ................................................................................................... 22
Figure 8.1-2: Cell 198 in Site 66 (CTC Puxi Business Hall)............................................................................. 23
Figure 10.2-1: Cell ID Planning MOD 3 and MOD 6 matrix ............................................................................. 27
Figure 10.4-1: Sol3 Antenna Ports ................................................................................................................. 29
Figure 10.4-2: Antenna Distance Separation /Positioning............................................................................. 29
Figure 10.4-3: DL Traffic Impact ................................................................................................................... 30
Figure 12.1-1: LTE Cluster ............................................................................................................................. 31
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 6/38
LIST OF TABLES
Table 9-1: Unfair Throughput ........................................................................................................................ 24
Table 9-2: Fair Throughput ............................................................................................................................ 24
Table 12-1: All modes parameters change .................................................................................................... 37
3 REFERENCE DOCUMENTS
Ref.
Document Number
[1]
PPP/DDD/CCC/NNNN
Title
GPS US site team
http://nwswww.ih.lucent.com/~lte-gps/
LTE OUTDOOR RF DESIGN GUIDELINE (Advanced RF
Competence Center)
[2]
PPP/DDD/CCC/NNNN
https://wcdma-ll.app.alcatellucent.com/livelink/livelink.exe?func=ll&objId=54454844&objAct
ion=browse&sort=name&viewType=1
4 WIPS
4.1 WIPS RECOMMENDATIONS

In LA1.1 to change the parameter you could do directly in the system, edit the DLU file and
change the respective parameter, or you can extract the DLU file change the respected
parameter and upload again the DLU file in the system.
Open the XML database in the WIPS select the parameter you need to change, and after the
change to correctly update the parameter select SET to finalize the update.
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 7/38
Figure 4.1-1: WIPS parameter changes
After select SET is necessary create a work order to be ease to see the changes in the template
and to be able to roll back into the previous configuration.
Rename the work order and export the file into the live server repository.
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 8/38
Figure 4.1-2: WIPS work order export
5 LLDM MASK
5.1 LOAD MASK

Each time we start UE connection in LLDM software is necessary to define the MASK with
specific parameters.
The only log data items you choose in Log Mask Setting Tree View are collected at LTE UE side
and sent to LLDM.
5.1.1 Short Description

Some occasions when setup the UE configuration is necessary to setup correctly the LOG MASK
that will allow processing all the information collected during the tests with LLDM. In some
specific cases if we select too many parameter to check the UE cannot hang on such load and
crash. To avoid this problem follow next steps.
5.1.2 Proposed Tests

Step 1 Select in the LOG MASK the parameters that is strictly necessary for your information.
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 9/38
Step 2 Connect the UE and check the CH information load.
Step 3 The channel information load should be between 30% and 40% of the capacity. In some
cases using 50% or higher we have UE crash.
Figure 5.1-1: Log Mask Setting Dialog
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 10/38
Channel 1
Load
Figure 5.1-2: CH1 MASK Load Information
6 ACCESSIBILITY
6.1 SLEEPING CELL

6.1.1 Short description
Sleeping Cells can be defined as Cells that do not provide support for LTE traffic for undefined
means i.e.
They have not been put into a locked state by the operator.
They do not report standard failure of service indications e.g. hardware or software alarms.
Due to their nature Sleeping Cells are difficult to detect and therefore cells in these conditions
can remain out of service for prolonged time periods causing major service outages.
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 11/38
This feature provides an initial capability of detecting sleeping cells in the LA2.0 release. It uses
alarm and performance information available from eNBs deployed in the field to detect sleeping
cell conditions.
6.1.2 Issue Description

t300, This UE timer is started when sending RRCConnectionRequest and is stopped upon
reception of RRCConnectionSetup or RRCConnectionReject. Defined in TS 36.331. Broadcast in
systemInformationBlockType2.
When the eNB transmits the RRC CONNECTION SETUP message to the UE a defense timer is
started in order to prevent the scenario when the UE does not receive the message due to e.g.;
cell reselection.
If the eNB does not receive RRC CONNECTION SETUP COMPLETE before the timer expiry, the
RRC connection is considered as failed and the eNB will delete UE context and release any
associated eNB resources.
Figure 6.1-1: RRC Connection scenario call flow
6.1.3 Propose steps

Step 1 Using LLDM please selected in the log MASK (Radio Problem Cause).
Step 2 Check the signal level (RSSI, SNR and RSRP).
Step 3 Using the signal log message is possible to see where message the connection fails.
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 12/38
Figure 6.1-2: T300 expire
6.1.4 Workaround
If timer t300 expires:
1 - Reset MAC, release the MAC configuration and re-establish RLC for all RBs that are
established;
2 - Inform upper layers about the failure to establish the RRC connection, upon which the
procedure ends.
3 Before the next two steps please take all the respected traces relevant for debugging
4 Lock/Unlock cell
5 Reboot cell
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 13/38
6.2 LAZY CELL

In the scenario of a Lazy Cell all looks OK from Network operation center - RRH is TX'ing, UE can
read MIB/SIB, RACH does work, UE will see rrcConnectionSetup, but
rrcConnectionSetupComplete is not received by eNB.
6.2.2 Issue description

In the Radio Problem Cause menu the MAC_RA_PROBLEM message is reported. This is indication
of Random access problem from MAC while neither T300, T301, T304 nor T311 is running.
Figure 6.2-1: MAC RA Problem
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 14/38
eNB doesnt receive

the RRCConnection
SetupComplete from
UE side
Figure 6.2-2: RRC connection establishment procedure
6.2.3 Propose steps
Step 1 Using LLDM please selected in the log MASK (Radio Problem Cause).
Step 2 Check the signal level (RSSI, SNR and RSRP).
6.2.4 Workaround
1 Before the next two steps please take all the respected traces relevant for debugging
2 Lock/Unlock cell
3 Reboot cell
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 15/38
7 MOBILITY
7.1 RRC CONNECTION REESTABLISHMENT REJECT

According to latest studies and recommendations from NPE and R&D side the following
parameters should be taken care of when enabling Hand over in a network.

During intra Ho phase when the decision arrived to change the cell, appears first
RRC_ConnectionReestablishmentReject
Figure 7.1-1: RRC Connection ReestablishmentReject
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 16/38

7.1.2.1 RRC Connection Reestablishment:
In a number of failure cases (e.g. radio link failure, handover failure, RLC unrecoverable error,
reconfiguration compliance failure), the UE initiates the RRC connection reestablishment
procedure, provided that security is active. If security is not active when one of the indicated
failures occurs, the UE moves to RRC_IDLE instead.
To attempt RRC connection re-establishment, the UE starts a timer known as T311 and performs
cell selection. The UE should prioritize searching on LTE frequencies. However, no requirements
are specified as to for how long the UE shall refrain from searching for other RATs. Upon finding
a suitable cell on an LTE frequency, the UE stops the timer T311, starts the timer T301 and
initiates a contention based random access procedure to enable the
RRCConnectionReestablishmentRequest message to be sent. In the
RRCConnectionReestablishmentRequest message, the UE includes the identity used in the cell in
which the failure occurred, the identity of that cell, a short Message Authentication Code and a
cause.
7.1.2.2 Tracking Area Update:

If the UE has moved to a cell which belongs to a different tracking area, it will establish a brief
signaling connection with the eNB to inform it about its new location within the new tracking
area before it enters the paging reception stage.
Since we have RRC ConnectionReestablishmentReject and after a tracking area update request
during some seconds we dont have any data transfer, as you can see in the figure bellow.
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 17/38
Figure 7.1-2: No data throughput during HO phase
7.1.3 Workaround
1 Check adjacency neighbor list
7.2 TCPACKFREQUENCY MODIFICATION

Accordingly to last trial feedbacks; it was observed that in some case there was a U-plane
packet loss during or shortly during HO.

It was found that with those settings the HO gap can be reduced as the impact of packet loss
during HO can be recovered quicker. It depends whether you see U-plane packet loss during or
shortly after HO.
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 18/38
7.2.3 Workaround
Step 1 TSHARK - UE Hardware Interface ID
Ensure Wireshark is installed, and then run TSHARK-CTC.bat to check
Choose the right device from the list
tshark-ctc.bat
E.g./ Samsung UE interface id = ****9DD2
Figure 7.2-1: TSHARK - UE Hardware Interface ID
Step 2 TCPoptimizer Edit Registry

Run TCP Optimizer
Go to Preference | Check Enable Registry Editor
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 19/38
Figure 7.2-2: TCPoptimizer Edit Registry
Step 3 TCPoptimizer Add DWORD

Go to tab Registry | TCPIP | Parameters | Interfaces
Choose correct ID (eg./ ****9DD2) | New | DWORD Value
Figure 7.2-3: TCPoptimizer Add DWORD

LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 20/38
Step 4 TCPoptimizer Modify Value
Edit DWORD Value | Value Data = 1 (Decimal)

Exit TCPoptimizer| Restart Windows
Figure 7.2-4: TCPoptimizer Modify Value
7.2.4 Important Notes /Comments:
In some cases, the same UE may be having different interface IDs.

After windows restart (or any new test campaign), run TSHARK-CTC to ensure UE is still having
the same ID as before.
Otherwise, repeat the steps described in this slides.
NOTE: There may be other ways to identify the ID not described in this slides.
BEST PRACTICE: Backup the registry before any modification.
CAUTION: Setting TcpAckFrequency = 1 is just a workaround for FTP throughput Gap issue
during HO. This setting may not be optimum for other test cases, as it increases the overhead
esp. on the uplink.
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 21/38
8 STATIC TRANSPORT FIBER DELAY LENGHT
8.1 FIBER DELAY LENGTH CONFIGURATION

The length of the fiber that connects the CpriRadioEquipment to the d2u is specified by the
staticTransportFiberDelayLength parameter. This value is specified in meters.

Based in recent investigations in Vlizy, a specific delay is advised to be used for the fiber
connection. This value is calculated based in calculus that for a fiber of 900m the delay to be
used is of 200ms. Then to calculate the value to be used one can linearly use the following
formula:
Correct delay parameter = (real fiber length d2U to RRH / 900m) * 200ms
8.1.3 CTC Examples

For the indoor installation site (cell 50 in site 16 (EXPO Axis)), was two equal fibers lengths
(530m) to connect indoor antennas, the calculated delay was 118ms.
Mainly the test bellow was to see impact of optimum configuration versus non configured delay
Below the test you can find Throughput comparison with different fiber parameterization.
Figure 8.1-1: Cell 50 in Site 16 (Expo Axis)
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 22/38
8.1.3.1 Comments:
Impact is more significant in DL FTP, while in UL FTP the gai is less significant.
For the Indoor installation for cell 198 in site 66 (CTC Puxi Business Hall) was used two equal
fibers lengths (2000m) to connect indoor antennas; the calculated delay was 444ms.
Mainly the test was to the compromise in performance when introducing different fibers lengths
delays beside the optimized one.
Below one can find Throughput comparison with different fiber parameterization
Figure 8.1-2: Cell 198 in Site 66 (CTC Puxi Business Hall)

8.1.3.2 Comments:
In this test main goal was to access different fibre lengths' delays (0m, 1Km, 1.5Km and 2Km).
Possible to see that for distances bellow 1km we had improvement, for distances higher than
1km the throughput decrease. Further tests need to run to confirm the results
9 MULTI UE
It was seen during the Multi UE tests that in some cases an Unfair UL throughput sharing was
occurring. In order correct this behavior this hint was built.
9.1 UNFAIR UL THROUGHPUT SHARING

When using 8 UE in parallel in different conditions such as in Near Cell, Medium Cell and Cell
Edge the throughput according to ulSchedPropFairAlphaFactor parameter could be allocated
different PRBs for each UE.
9.1.2 Propose steps

Step 1 Performed a FTP UL test with only one
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 23/38
Step 2 Check the throughput reach with one UE

Step 3 Performed a FTP UL test with 8UEs in different RF conditions
Step 4 Check the throughput reach with each UE

In the following table is possible to see the different throughput between different UEs.
The parameter ulSchedPropFairAlphaFactor was configure to be equal = 1 (aggressive
scheduler). With this the fairness is not
reached.
SNR
U E1
U E2
U E3
U E4
U E5
U E6
U E7
U E8
1 0.9 5
1.1 3
10 .6
1 9.8 9
9.4 7
1.4 9
1 0.8 1
1 9.8 7
u L 1T t p
uL 1 N tp
u T T I%
uR B %
u tR B %
uM C S
D L n a c k % R an k
PL avg
0 .5 3
0 .5 1
4 9 .51
1 1 .4
5 .65
10 .9 1
5 .5 3
2
91
0 .1 6
0 .1 6
1 4 .96
12 .2 1
1 .83
9 .0 3
2 .9 7
1 .9 8
10 1
1 .0 3
0 .9 8
7 1 .48
14 .0 8
1 0 .06
11 .6 8
6 .4 7
2
92
1 .2 4
1 .1 9
8 0 .53
1 4 .9
12
11 .7 7
5 .7 2
2
78
0 .9 3
0 .8 7
5 5 .8
15 .6 5
8 .73
11 .7 9
5 .6 4
2
84
1 .1 3
1 .0 6
7 6 .83
14 .4 1
1 1 .07
11 .6 6
5 .8 4
1 .5 1
94
1 .1 2
1 .0 6
7 9 .89
13 .3 9
1 0.7
11 .8 9
5 .7 4
2
84
0 .6 6
0 .6 2
5 7 .53
11 .3 8
6 .55
11 .4 6
6 .2 1
2
71
Unfair
Throughp
Table 9-1: Unfair Throughput
9.1.4 Workaround
The parameter ulSchedPropFairAlphaFactor could be configured to be less aggressive and like
this we had a fair throughput sharing
Setting up ulSchedPropFairAlphaFactor = 0 we are able to setup the UL throughput fairness in
all the UEs
UE1
UE2
UE3
UE4
UE5
UE6
UE7
UE8
SNR
uL1Ttp
uL1Ntp uTTI%
uRB%
utRB%
uMCS
DLnack% Rank
PLavg
10.59
0.76
0.73
65.89
12.14
8
11.36
5.57
2
92
0.8
0.8
0.76
70.05
11.52
8.07
11.24
15.8
1.97
101
10.21
0.81
0.77
65.47
12.51
8.19
11.66
5.6
2
92
19.71
0.81
0.78
49.41
16.6
8.2
11.23
5.86
2
78
9.2
0.8
0.77
62.62
13.14
8.23
11.55
5.6
2
85
1.83
0.8
0.77
50.86
16.54
8.41
10.93
5.83
1.63
93
10.38
0.81
0.77
61.78
13.07
8.08
11.57
6.22
2
84
19.47
0.8
0.77
60.62
13.38
8.11
11.58
5.92
2
71
Fair
Throughput
Table 9-2: Fair Throughput
9.1.5 MU parameter setting

9.1.5.1 UL Parameters
PUSCH SINR Target = 4 dB
FbFunction numberOfPoints = 2 (as per default Ed13 DLU)
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 24/38
FmFunction and FnFunction numberOfPoints = 4 (as per default Ed13 DLU)

ulSchedPropFairAlphaFactor = 0 (PF scheduler)
maxNbrOfUsersForStretchingPHlimit = 8
ulBOperiodicIncreaseEnabled = disabled (for all four MAC bearers)
UL Initial BLER Target = 10%
9.1.5.2 DL Parameters
dlSinrThresholdBetweenCLMimoTwoLayersAndOneLayer=10.0
dlSinrThresholdBetweenOLMimoAndTxDiv=10.0
nomPdschRsEpreOffset= -2
DL Tx Mode = CL-MIMO (Full Mode)
DL Initial BLER Target = 10%
10 NEIGHBOURS PLANNING AND CELL ID PLANNING

In commercial networks or trials that coexisting already many eNB Same approach can be
applied to adjacent cluster sites of an already optimized cluster;
First optimized adjacent sites must be included in the computation zone, but not in the focus
zone which should contain only the sites to optimize.
10.1 NEIGHBORS PLANNING

The main planning rule is to re-use cell ID with a sufficient distance in order to avoid
interferences.
This distance depends on propagation path loss, the environment and the frequency.
A correct RF design and optimization induces average number neighbors between 16 and 25 per
cell.
The main criteria are the following one:

Considering two cells cell A and cell B, on the same frequency carrier using the same cell ID,
the distance between those must satisfy the following criteria:
RSRP
At cell A edge (RSRPcellA
-115dBm) : RSRPcellA
At cell B edge (RSRPcellB
-115dBm): RSRPcellB
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 25/38
In term of distance the range of distance where the radio conditions detailed above are
analyzed.
Dense urban/ urban for all frequency bands
Maximum distance to analyze neighbors conditions: 8km
Suburban for all frequency bands
Rural for all frequency bands
10.2 CELL ID PLANNING

Cell ID plan use the same radio criteria than the ones for neighboring plan, but the process is
not the same, some added constraints must be taken into account.

One can find some quick note regarding the lessons learned about cell planning for LTE
Networks.
Theoretical definition should be:
PCI :(physicalLayerCellIdentityGroupIndex *3 ) + physicalLayerCellIdentityIndex
physicalLayerCellIdentityGroupIndex between 0 and 167 (included)
physicalLayerCellIdentityIndex between 0 and 2 (included)
So 3 sectors belonging to the same site have a common group index but different cell identity
index (0, 1 and 2).
Bear also in mind the cell ID planning. 2 cells with modulo 3 cell IDs interfere more against each
other in the DL.
Since the RS signal occupies each 6th RE within a OFDMA symbol, the Cell Planning should be
that the cell and its immediate neighbors should have cell Ids 0, 1, 2, 3, 4 and 5 surrounded by
cells 6, 7, 8, 9, 10, 11 etc...
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 26/38
Figure 10.2-1: Cell ID Planning MOD 3 and MOD 6 matrix
10.2.1.1 Comments:
Typical example case for a MOD 3 and 6 matrixes, that helps to identify the bad relations
between Cell IDs.
If Cell A is oriented to Cell B then we have to use the follow relation:
A = B + n*3, n = 0, 1, 2, 3, ...
10.3 RSRP CRITERIA

Cell id is required to identify each cell, a cell id is the combination of one of the 3 sequences
supported by P-SCH and the group Id supported by S-SCH.
So Realizing a cell id planning = realizing P-SCH planning and S-SCH planning
The strategy recommended is to use the same S-SCH per site which induces that each sector
uses a different P-SCH sequence
This distance depends on propagation path loss, the environment and the frequency.
The main criteria are the following ones:
Considering two cells cell A and cell B, on the same frequency carrier using the same
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 27/38
cell ID, the distance between those must satisfy the following criterias:
RSRP criterion to respect on the field
At cell A edge (RSRPcellA
-115dBm) : RSRPcellA
At cell B edge (RSRPcellB
-115dBm): RSRPcellB
10.3.1.1 Comments:
The above rules should be followed, to avoid the risk of getting extra interference.
10.4 DISTANCE CRITERIA

Distance criteria, but it can not be used alone as it assume an homogeneous environment which
is not always the case
Dense urban/ urban
2km @ 2600MHz considering 600m cell radius
2,4km @ 1800MHz and 2100MHz considering 700m cell radius
5,5km @ 850MHz and 900MHz considering 1,7km cell radius
6Km @ 700MHz considering 1,9km cell radius
Suburban
6km @ 2600MHz considering 1,8km cell radius
7km @ 1800MHz and 2100MHz considering 2,2km cell radius
18km @ 850MHz and 900MHz considering 5,5km cell radius
20Km @ 700MHz considering 6km cell radius
Rural
17km @ 2600MHz considering 6km cell radius
21km @ 1800MHz and 2100MHz considering 7km cell radius
60km @ 850MHz and 900MHz considering 18km cell radius
65Km @ 700MHz considering 20km cell radius
10.4.1.1 Comments:
The above rules should be followed, to avoid the risk of getting extra interference.
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 28/38
11 ANTENNA POSITIONING
In order to achieve the best performance in DL on filed is quite important to respect the
antenna separation and positioning on the roof top of the drive test car This was evaluated at
Shang Nang Area.
In the Figure 10.4-1: and Figure 10.4-2: , one can find some identification for the correct
cabling used and distance separation /positioning of the antennas.
Figure 10.4-1: Sol3 Antenna Ports
Figure 10.4-2: Antenna Distance Separation /Positioning
From the Figure 10.4-3: , what could be seen was that the positioning was influencing the
performance reached in the static test. In the different boxes identified with (1, 2 and 3) we
have different position /orientation setups. Accordingly to that the performance was changing.
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 29/38
Figure 10.4-3: DL Traffic Impact

11.1.1.1 Comments:
Detailed configuration used and performance highlight.
Rx DT antenna horizontal & Tx\Rx DT antenna vertical (~60Mbps)

Rx DT antenna vertical & Tx\Rx DT antenna vertical (~35Mbps)
Rx DT antenna vertical & Tx\Rx DT antenna horizontal (~40Mbps)
12 FAQS
12.1 HOW TO AVOID CALL DROP?

During RF optimization phase and RF parameter phase of a cluster, should be taken into account
the following actions to avoid call drop inside cluster:
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 30/38
Figure 12.1-1: LTE Cluster
12.1.1 Propose steps
Step 1 First check on site during optimization phase (Tilts, Azimuths, cables)
Step 2 Drive test to get the best serving cells in the entire cluster
Step 3 With Optimization report prepare all the adjacencies possible to not drop the call
during handover between sites.
Step 4 Check all parameters that could impact Inter-Handover and Intra-Handover.
Step 5 Run a battery of tests inside the cluster such has mobility tests, static tests, multi UE
tests and stability tests to avoid call drops.
12.2 THE SNR IS GOOD, BUT THE UE COULD NOT ATTACH.

WHAT CAN BE DONE?
In this case we have several possibilities for the UE couldnt connect to the network.
The best approach is check the messages in LLDM, would be easy to detect in witch way we
could go in the investigation.
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 31/38
Step 1 Check in the EPC if the IMSI associate to your UE is not blocked.
Step 2 Check in the PCRF if the IMSI from your UE is not block.
Step 3 Check if the cell is not locked
Step 4 In the previous chapters another possibilities could be (Lazy Cell and Sleepy Cell)
Step 5 Check the value for parameter qRxLevMin.
In here you could contact system engineering to take the correct traces when you try to connect
to investigate afterwards.
12.3 THE SNR IS BAD EVEN UNDER THE SITE, AND THE UE
COULD NOT ATTACH. WHAT CAN BE DONE?
In this case we have several possibilities for the bad SNR and the UE couldnt connect to the
network.
The best approach is check the messages in LLDM, would be easy to detect in witch way we
could go in the investigation.

STEP 1 - Sites overshooting; it is pretty normal to have sites overshooting in a brand new
network. Usually the first step when detected is to introduce additional tilt on the interferer
cell (considering that a specific cell should be dominant in a defined area). This step should be
repeated while possible to introduce tilt without killing also the cell.
STEP 2 - Other approach if we observe that the main lob of the interferer cell is shooting in an
undesired direction (azimuth); normally we can try to adjust the azimuth for this interferer
cell.
STEP 3 - Last step when all the other two steps are not possible to perform, due to logistics
reason or any other reason; we can go for power reduction approaches on the interferer cell.
NOTE: Take in to account that all these steps are interactive, and one should not expect to
perform it once and thats it. Usually it is necessary to perform several runs.
12.4 NAMING OF THE PATCH FILE FOR PQ3
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 32/38
The issue was to avoid renaming old pq3 files into .old as the software will use these instead of
the new ones.
12.4.1 Propose steps to install a designer UPA, FPGA, or DSP

image on the CEM
STEP 1 - ftp or sftp to the PQ2 (on the CEM board), go to the /active/pq3 directory and
transfer the private image(s) to that directory. Make sure you name the file the same as the
original in that directory.
NOTE: For LA2.0, you have to use the enb0xfer login and password. Also, if you want
to keep the original files by renaming them, do not simply append .org or .old to the name of
the file. Doing this will result in the eNB getting disabled, the BB getting disabled and a
Software_anomaly_CE_global_setup alarm will get
reported on the BB. We recommend that you rename the files, for example, to ori_ecectl.vx
and ori_ucu3x.dspa instead.
STEP 2 - The private loads can be downloaded from the following server (password is blank):
ftp://ST_DL_user@172.26.105.202/UPA_Designer_Loads.
For Murray Hill users, many of the designer loads can be found on the white website.
STEP 3 - It may be necessary to make the active filesystem writeable; to do so type: mount -o
remount rw /active
STEP 4 - Modify the cectlpackage.txt file. If you are familiar with modifying the CDMA GDF
files, then you will see that it follows the same structure. The first column is the board name,
the second one is the file name, third is the directory path, next is the filesize and the last
column is the checksum. Make sure you change the correct line.
It is a little confusing because there are 4 FGPA images: combiner, a, b and c. There is also the
DSP image. You have to update the file size, and for the checksum you have to either put the
correct checksum or all zeroes.
STEP 5 - Save your changes, and reboot the entire eNB
Example with private UPA, and DSP load:

77df74e0 cectlpackage.txt
BNJ103 cectl.vx ./ 5821265 0x00000000 0x00000001
filesize
<<< UPA LOAD
checksum
BNJ103:CFPG combiner_top_proc.zdat ./ 317396 0x0522d6ec 0x00000001

BNJ103:DSPA ucu3x.dspa ./ 1048576 0x00000000 0x00000001
<<< DSP LOAD
BNJ103:FPGA a_fpga.zdat ./ 465558 0x900d4cc5 0x00000001
<<< FPGA loads
BNJ103:FPGB b_fpga.zdat ./ 763567 0xb4e12bc3 0x00000001

BNJ103:FPGC c_fpga.zdat ./ 745364 0xc7524ccf 0x00000001
BNJ103:MOD cectl.mod ./ 1670016 0xfc441f27 0x00000001
12.5 RRHS SUPERVISION LOST

LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 33/38
Constant loss of the supervision of RRH's. On site intervention needed to electrically reboot
equipment in order for cell to be active again.
12.5.1 Propose workaround

A workaround included in the RRH load 11.012 was to reboot the RRH every 5 days. But it seems
now that the RRH load 11.014 will resolve the problem.
12.6 LA1.1 G711 CODEC ISSUE

During VoIP with G.711 on dedicated Bearer, eNB is dropping packets in DL.
12.6.1 Propose workaround

Root cause found (bad configuration) + G.711 is not supported on La1.1.
Propose to use AMR codec
12.7 WHICH PARAMETERS ARE NEEDED TO CHANGE IN

ORDER TO ENABLE DIFFERENT TRANSMISSION
MODES?
12.7.1 MIMO CLOSE LOOP full mode (3GPP 36.213 : 7.2 ,
7.2.1.C)
For Enb/1 cellConf/0 Cell2DLConf/0 attribute

transmissionMode = tm4
cqiReportingModeAperiodic = rm31
For Enb/1 CellConf/0 CellMIMOConf/0 attribute

dlFullCLMimoMode= true
dlMIMODefaultCodeBook = 1LayerCodebook0
dlMimoSinrSwitchAveragingCoefficient=252
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 34/38
dlSinrThresholdBetweenCLMimoTwoLayersAndOneLayer= 15.0
dlSpeedThresholdBetweenCLMimoTwoLayersAndOneLayer= 0
dlSpeedThresholdForDisablingPMI=0
For Enb/1 CellConf/0 CellMIMOConf/0 CodebookSubsetRestriction/0

attribute
n2TxAntennaTm4OneLayerCodebook0 = true
n2TxAntennaTm4TwoLayersCodebook1= true
12.7.2 MIMO CLOSE LOOP Mixed mode


dlFullCLMimoMode= false
dlMIMODefaultCodeBook = 2LayersCodebook1
dlSinrThresholdBetweenCLMimoAndTxDiv= 15.0
dlSpeedThresholdBetweenCLMimoAndTxDiv= 0
dlSpeedThresholdForDisablingPMI=0

attribute
n2TxAntennaTm4OneLayerCodebook0 = false
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 35/38
12.7.3 MIMO OPEN LOOP


dlFullCLMimoMode= false
dlMIMODefaultCodeBook = 2LayersCodebook1
dlSinrThresholdBetweenOLMimoAndTxDiv= 18.0
dlSpeedThresholdBetweenCLMimoAndTxDiv= 0

attribute
n2TxAntennaTm4TwoLayersCodebook1= false
n2TxAntennaTm4TwoLayersCodebook2= false
12.7.4 TXDIV
12.7.5 All modes comparison
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 36/38
Table 12-1: All modes parameters change
13 CONCLUSION
14 ABBREVIATIONS AND DEFINITIONS
14.1 ABBREVIATIONS
Acronym
Description
AMR
Adaptive Multi-Rate
BLER
Block Error Rate
CCCH
Common Control Channel
CH
Channel
DL
Downlink
DL-SCH
Downlink Shared Channel
D2U
Base Band Unit (BBU) d2U and d1U; A signal Distributed 2U (d-2U) digital unit, this
indoor unit contains the channel element cards and the control module.
eNB
Evolved NodeB (or eNodeB) (combines functions of UMTS NodeB and RNC)
EPC
Evolved Packet Core
FTP
File Transfer Protocol
HO
Handover
LLDM
LGE UE Diagnostic Monitor
LTE
Long Term Evolution
MIMO
Multiple Input Multiple Output antenna technique
OFDMA
Orthogonal Frequency Division Multiple Access DL air interface
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 37/38
PCRF
Policy Charging Rule Function
PRB
Physical Resource Blocks
P-SCH
Primary synchronization channel
PUSCH
Physical Uplink Shared Channel
RAT
Radio Access Technology
RF
Radio Frequency
RLC
Radio Link Control
RRC
Radio Resource Control (3GPP TS 36.331)
RRH
Remote Radio Head
RS
Reference Symbol
RSRP
Reference Signal Received Power
RSSI
Received Signal Strength Indicator
SNR
Signal to Noise Ratio
SINR
Signal to Interference-plus-Noise Ratio
S-SCH
Secondary Synchronization Channel
UDP
User Datagram Protocol
UE
User Equipment (similar to Access Terminal in EV-DO)
UL
Uplink (equivalent to EV-DO Reverse Channel) LTE supports peak data rate of 80 Mbps
UL
WIPS
Wireless Provisioning System
14.2 DEFINITIONS
END OF DOCUMENT
LTE/IRC/APP/032278
V01.03 / EN
Approved Standard
09/Sep/2010
Page 38/38

RF TroubleShooting Guideline LA1.1

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RF TroubleShooting Guideline LA1.1

Uploaded by

Copyright:

Available Formats

RF Troubleshooting Guideline LA1.

Copyright 2010 Alcatel-Lucent, All Rights Reserved

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

1.2 AUDIENCE FOR THIS DOCUMENT

Reason of changes / short

Reading Cycle Completed (DR4

Alcatel-Lucent - Proprietary - Use pursuant to applicable agreements

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

RRC Connection Reestablishment: .........................................................17

Tracking Area Update:.......................................................................17

7.1.3 Workaround .......................................................................................................................18

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

7.2.1 Short description ................................................................................................................18

10 NEIGHBOURS PLANNING AND CELL ID PLANNING ...........................................................25

10.3 RSRP CRITERIA.........................................................................................................................27

10.4 DISTANCE CRITERIA....................................................................................................................28

Alcatel-Lucent - Proprietary - Use pursuant to applicable agreements

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

Alcatel-Lucent - Proprietary - Use pursuant to applicable agreements

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

Alcatel-Lucent - Proprietary - Use pursuant to applicable agreements

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

4.1 WIPS RECOMMENDATIONS

Alcatel-Lucent - Proprietary - Use pursuant to applicable agreements

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

Figure 4.1-1: WIPS parameter changes

Alcatel-Lucent - Proprietary - Use pursuant to applicable agreements

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

Figure 4.1-2: WIPS work order export

5.1 LOAD MASK

5.1.1 Short Description

5.1.2 Proposed Tests

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

Step 2 Connect the UE and check the CH information load.

Figure 5.1-1: Log Mask Setting Dialog

Alcatel-Lucent - Proprietary - Use pursuant to applicable agreements

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

Figure 5.1-2: CH1 MASK Load Information

6.1 SLEEPING CELL

Alcatel-Lucent - Proprietary - Use pursuant to applicable agreements

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

6.1.2 Issue Description

Figure 6.1-1: RRC Connection scenario call flow

6.1.3 Propose steps

Step 2 Check the signal level (RSSI, SNR and RSRP).

Alcatel-Lucent - Proprietary - Use pursuant to applicable agreements

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE

Figure 6.1-2: T300 expire

Alcatel-Lucent - Proprietary - Use pursuant to applicable agreements

RF Troubleshooting Guideline LA1.1

LTE Unit/ TIS-CEC/NPE