Knowledge Transfer LTE
Proyecto Optimización Claro Colombia
1
01/08/2017 © Nokia 2014
Confidential
Agenda
1.
Idle Mode Mobility Load Balancing LTE2050 & Inactivity Timer
2.
Parameters for handover optimization
3.
Spectral Eficiency – UL
4.
Additional L1 Measurements
5.
RF Sniffing
2
01/08/2017
Confidential
© Nokia 2014
Idle Mode Mobility Load Balancing
LTE2050 & Inactivity Timer
Julio de 2017
3
01/08/2017 © Nokia 2014
Confidential
Activación feature LTE2050 en eventos masivos
Permite el desborde de usuarios LTE hacia 3G, según la carga del Nodo LTE.
Nota: Este feature se activa después de verificar capacidad disponible en 3G
Intra-Frequency
Inter-Frequency
Intra-LTE
Inter-RAT
Connected Mode Load Balancing Features
LTE1140 – Intra-Frequency Load
Balancing (RL70/RL55TD)
LTE1387 – Intra-eNB Inter-Frequency Load Balancing (RL40)
LTE1170 – Inter-eNB Inter-frequency Load Balancing
(RL50/RL35TD/RL50FZ)
LTE1531 – Inter-frequency Load Balancing Extensions
(RL60/RL45TD)
Este Feature está
activo para CSFB. Se
configura para InterRAT
Note: Arrows (
/
) signify the
extensions to features from previous
releases. The new/extension features
share the same activation flags as the
original features and aimed at adding
additional functionalities to legacy features.
LTE1841 – Inter Frequency Load Equalization (RL70/RL55TD)
Idle Mode Load Balancing Features
CRL0632 – Basic Idle mode Load Balancing (RL40)
LTE487 – Idle Mode Load Balancing (RL50/RL35TD/RL50FZ)
Se activa y configura
para acelerar
descarga de
usuarios
hacia 3G
4
01/08/2017 © Nokia 2014
Confidential
cuando
la celda LTE
esté cargada
LTE1677 – Idle Mode Load Balancing Extensions (RL60/RL45TD)
LTE2050 – Load Triggered Idle Mode Load Balancing (RL70/RL55TD)
Requiere parametrización específica en objetos LTE de
acuerdo a recomendaciones Nokia.
LTE 487 Idle Mode Mobility Load Balancing
▪
The LTE487 idle mode mobility load balancing (IMMLB) feature allows for statistical distribution of UEs towards
different frequency layers and RATs
•
A configurable percentage of UEs switching from connected to idle state are provided configurable dedicated IMMLB cell
reselection priorities for different frequency layers and RATs via RRC Release message
•
The provision of dedicated priorities is a means to steer UEs toward frequency layer or RAT with the highest priority
subject to cell reselection thresholds
•
There is no load trigger to start IMMLB, i.e. each UE release would initiate UE and target selection procedures
1. UEs connected to Freq1
Dedicated Cell Reselection
Priorities
Broadcasted Cell Reselection Priorities
Freq 1
High
Freq 2
Low
Low
Freq 2
High
5
01/08/2017
Confidential
© Nokia 2014
Low
Freq 2
High
2. UEs are released by
the cell
Dedicated Cell Reselection Priorities
Freq 1
Freq 1
4. UEs uses the
IMMLB priorities for
reselection
Broadcasted Cell Reselection
Priorities
Freq1
3. Selected UEs are sent
IMMLB priorities
Freq 1
High
Freq 2
Low
Broadcasted Cell Reselection
Priorities
Freq 1
High
Freq 2
Low
Freq2
Configuración objetos REDRT – LTE487 Idle Mode Mobility LB
6
01/08/2017 © Nokia 2014
Confidential
LTE1677 – Idle Mode Mobility Load Balancing Extensions
•
While UE in RRC_IDLE state is moving, Cell Reselections are done
•
Selection of Cell is done according to:
•
•
Legend for pictures:
-
Certain defined thresholds (based on RSRP, RSRQ)
-
Priorities (Broadcasted and Dedicated)
UE is in RRC
Connected State
Broadcasted Cell Reselection Priorities are contained in
SIBs and UE can read them
UE is in RRC Idle State
Freq2
Dedicated Cell Reselection Priorities are
used by Load Balancing (LB) features
-
-
Dedicated Cell Reselection Priorities
are sent only for UEs that are candidates
for LB
Freq1
Freq3
They are sent in Idle Mode Mobility
Control Info (IMMCI) that is a part of
RRC Connection Release Message
7
01/08/2017 © Nokia 2014
Confidential
Broadcasted Cell
Reselection Priorities
Freq 1
High
Freq 2
Medium
Freq 3
Low
LTE2050 – Load Triggered Idle Mode Load Balancing
When feature is activated (LNBTS:actIdleLb = true) its behaviour can
be split into 5 functional blocks
1) Load supervision and CAC calculation (Composite Available Capacity):
2) Check if IMMLB should be triggered
•
Source cell CAC is compared with configured load threshold
(LNCEL:idleLBCapThresh) that defines an IMMLB trigger point
•
According to configuration, proper IMMLB object is selected, from which
percentage of UEs as well as IMMLB weights are taken: UFFIM (UTRA FDD)
4) Candidate UE selection
•
For each UE that is being released, it is verified if IMMCI should be added
Check if IMMLB
should be triggered
IMMLB Objects
Selection
Candidate UE
Selection
IMMCI creation
5) IMMCI creation
Idle
8
01/08/2017 © Nokia 2014
Confidential
LTE487/LTE1677
3) IMMLB Objects Selection
Load supervision and
CAC calculation
Idle Mode Mobility Load Balancing
Measurements of source cell DL CAC (CACS)
LTE2050
•
Connected
Load supervision and CAC calculation
All load types are measured: GBR, PDCCH and nonGBR
DL GBR Load Measurements
•
•
•
DL GBR load (%) is defined as the ratio of the average DL GBR utilization to the
average available PRBs for dynamic scheduling
PDCCH Load Measurements
PDCCH load (%) is defined as the averaged ratio of utilized CCEs to total number
of available CCEs
DL nonGBR Load Measurements
DL non-GBR load (%) is defined as the ratio of the estimated resource utilization
for non-GBR bearers to the average available PRBs for non-GBR dynamic
scheduling
•
Load measurements (LM) are used for determination of Composite Available Capacity that is used by Load
Triggered Idle Mode LB (LTE2050) and other features.
•
Note LM are not needed by IMMLB functionality when LNCEL:idleLBCapThresh is set to 100%
9
01/08/2017 © Nokia 2014
Confidential
Load supervision and CAC calculation
• DL Composite Available Capacity is the
minimum of all AC:
CACDL = min(ACGBR, ACnonGBR, ACPDCCH)
LNCEL:loadSettings:mlbEicicOperMode
• Parameter
LNCEL:loadSettings:mlbEicicOperMode is used
to control CAC calculation
˗
allUes – DL GBR, DL nonGBR, PDCCH loads are
considered
˗
nonGbrPdcch – DL nonGBR and PDCCH loads are
considered
˗
nonGbrOnly – only nonGBR load is considered
10
01/08/2017 © Nokia 2014
Confidential
allUes
nonGbrPdcch
nonGbrOnly
LTE2050 – Parameter and objects Configuration
actIdleLb
idleLBCapThresh
11
01/08/2017 © Nokia 2014
Confidential
LTE2050 – Parameter and objects Configuration
idleLBPercentageOfUe
mlbEicicOperMode
12
01/08/2017 © Nokia 2014
Confidential
LTE2050 – Parameter and objects Configuration
t320
iFLBHighLoadPdcch
13
01/08/2017 © Nokia 2014
Confidential
LTE2050 – UFFIM object Configuration
14
01/08/2017 © Nokia 2014
Confidential
LTE2050 – Parameters description
Object
Parameter
LNBTS
actIdleLb
Description
The parameter activates the feature idle mode load balancing
Idle Mode Load Balancing Capacity Threshold.
LNCEL
idleLBCapThresh
Only if the Composite Available Capacity (CAC) is below or equal to this threshold, idle mode load balancing actions shall be triggered.
Default value: 100% (Inactive)
Valor recomendado en eventos = 85%
Percentage of UE to be selected for Idle Mode Load Balancing.
LNCEL
idleLBPercentageOfUe
Default value: 0
Valor recomendado en eventos = 10%
Mode for calculating the CAC in load balancing. This parameter selects the cell load evaluation profile.
LNCEL
mlbEicicOperMode
Default value: allUes
Valor recomendado en eventos = nonGbrPdcch
Timer T320. Defines the validity time of dedicated priorities defined in IdleModeMobilityControlInfo.
LNCEL
t320
Default value: 180min
Valor recomendado en eventos = 10min
Inter-frequency load balancing PDCCH high load.
LNCEL
iFLBHighLoadPdcch
If iFLBHighLoadGBRDL and iFLBHighLoadNonGBRDL and iFLBHighLoadPdcch are set to 100%, the cell will never enter active Inter Frequency
Load Balancing state.
Default value: 95%
Valor recomendado en eventos = 85%
15
01/08/2017 © Nokia 2014
Confidential
Ejemplo: Parámetros LTE2050 – Evento Plaza de Toros Bogotá, 29-ene-2017
idleLBCapThresh = 85%
idleLBPercentageOfUe = 20
Valores iniciales:
16
01/08/2017 © Nokia 2014
Confidential
idleLBCapThresh = 95%
idleLBPercentageOfUe = 10
BOG.San Martin_L1
BOG.San Martin_L2
17
01/08/2017 © Nokia 2014
Confidential
BOG.San Martin_L3
Kbps
LTE_806a_RRC Connected Users BOG.San Martin
PRB Utilization %
1000
900
800
700
600
500
400
300
200
100
0
25/01/2017
25/01/2017
25/01/2017
25/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
30/01/2017
30/01/2017
Pico RRC Conn Users: 907 ->91% de uso PRBs
Valor trigger inicial : 95%
0
25/01/2017
25/01/2017
25/01/2017
25/01/2017
25/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
30/01/2017
30/01/2017
30/01/2017
# Users
100
90
80
70
60
50
40
30
20
10
0
25/01/2017
25/01/2017
25/01/2017
25/01/2017
25/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
26/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
27/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
28/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
29/01/2017
30/01/2017
30/01/2017
30/01/2017
91
11
LTE_5276B_E-UTRAN Avg PRB usage per TTI DL- PRB Utilization %
20000
223
LTE_5292D_Avg PDCP cell thp DL- Kbps
Average DL user Throughput
16
15
14
13
12
11
10
9
8
7
6
LTE_5427A_Average CQI-
Throughput DL - BOG.San Martin_L2
40000
35000
30000
25000
15000
19,632
10000
5000
Average CQI
Ejemplo: Parámetros LTE2050 – Evento Plaza de Toros Bogotá, 29-ene-2017
PRB Utilization Average CQI - BOG.San Martin_L2
Inactivity timer Parameter (InactivityTimer)
Defines a possibility to set a time period after which expiration UE is indicated to go to RRC_IDLE state (During
Inactivity timer period UE is considered still as a RRC_CONNECTED).
Inactivity timer is a crucial parameter for number of Connected Users/RRC Connected users in the cell handling. Long values of
RRC inactivityTimer may result with high number of users in the cell. To decrease high cell load in terms of high number of
Connected users in the cell short inactivityTimer should be considered. The lower value of the inactivityTimer parameter the
higher decrease in the maximum and average number of the users in the cell can be expected. Recommended value of RRC
inactivity timer is 10s.
18
01/08/2017 © Nokia 2014
Confidential
Inactivity timer Parameter (InactivityTimer)
•
High Loaded Cells reduces their traffic after reduction of Inactivity Timer(10s5s) as per Active/RRC
Connected UE KPI.
•
RRC/ERAB attempt has Increased due to shortening of Inactivity Timer.
•
Accessibility, Mobility and Max PDCP DL TPUT remains maintain.
•
Data Volume (DL/UL) maintain same.
•
Inactivity timer(10sec5sec) can be helpful to reduce High loaded Cell to low loaded cell and it can be
Utilize for Event location Cell to Improve Performance of Claro Network in terms of Capacity.
19
01/08/2017 © Nokia 2014
Confidential
Parameters for handover optimization
20
01/08/2017 © Nokia 2014
Confidential
Key parameters for handover optimization
Object
Parameter
Parameter Name
Purpose
LNREL
handoverAllowed
Handover allowed
Forbid HO attempts in long distance neighbor.
LNREL
cellIndOffNeigh
Cell individual offsets of other neighbor cells
• Avoid ping pong handover.
• Reduce HO attempts in worst relations, especially in short
distance neighbor relation.
LNREL
removeAllowed
Remove allowed
Avoid removal of forbidden neighbor relation by NRR feature.
21
01/08/2017 © Nokia 2014
Confidential
handoverAllowed (Handover allowed)
•
•
•
•
This parameter is used to forbid the long distance neighbor relations which have high
failure rate.
From LTE_031 report the worst long distance neighbor relations can be identified.
The first step is to analysis the tilt of source and neighbor cells and check if they are
overshooting.
If the tilt value is ok then long distance neighbor relations should be forbidden.
Abbreviated Name
MO Class
Full Name
Range and step
Default Value
Modification
Required on
Creation
handoverAllowed
LNREL
Handover allowed
0: allowed
1: forbidden
2: onlyS1
0
On-line
Mandatory
22
01/08/2017 © Nokia 2014
Confidential
cellIndOffNeigh (Cell individual offsets of other neighbor cells)
•
•
•
This parameter is used to introduce cell individual offset to the specific neighbor relations.
For example, if this parameter is set to -3dB then the handover will be delayed and
number of HO attempts will reduce for that specific neighbor relation. Similarly +3dB
offset will make the handover early and HO attempts will increase.
Negative offset should be defined in high failure neighbor relations (especially short
distance neighbors) which will avoid the cases of ping pong handover and will reduce
number of handover failures.
Abbreviated Name
MO Class
Full Name
cellIndOffNeigh
LNREL
Cell individual offsets of
other neighbor cells
23
01/08/2017 © Nokia 2014
Confidential
Range and step
0: -24dB
1: -22dB
2: -20dB
3: -18dB
4: -16dB
5: -14dB
6: -12dB
7: -10dB
8: -8dB
9: -6dB
10: -5dB
11: -4dB
12: -3dB
13: -2dB
14: -1dB
15: 0dB
16: 1dB
17: 2dB
18: 3dB
19: 4dB
20: 5dB
21: 6dB
22: 8dB
23: 10dB
24: 12dB
25: 14dB
26: 16dB
27: 18dB
28: 20dB
29: 22dB
30: 24dB
Default
Value
Modificatio Required on
n
Creation
15 (0 dB)
On-line
Mandatory
removeAllowed (Remove allowed)
•
This parameter should be set to “0(false)” for all the forbidden neighbor relation.
•
If this parameter is set to “1” for forbidden neighbor relation then the NRR feature will
delete the neighbor relation and ANR feature will add the neighbor relation again with
default parameter settings.
Abbreviated Name
MO Class
Full Name
Range and step
Default Value
Modification Required on
Creation
removeAllowed
LNREL
Remove allowed
0 (false), 1 (true)
1 (true)
On-line
24
01/08/2017 © Nokia 2014
Confidential
Mandatory
Bogota: LTE_5048b Inter eNB HO SR Daily
BOGOTA - Inter eNB X2 HO Success Rate%
900000
800000
700000
500000
Implementación “forbbiden”
27-Jun-2017 @17:00 hrs
Implementación “forbbiden” y
“offset” 14-Jul-2017 @21:00 hrs
Implementación MIMO
4x2, 28-30 Nov 2016
Implementación “forbbiden”, “offset” y
E tilt 21-Jul-2017 @15:00 hrs
400000
300000
200000
100000
0
25
01/08/2017 © Nokia 2014
Confidential
2016
2017
Failures
600000
9/9/2016
9/15/2016
9/23/2016
10/20/2016
10/26/2016
11/3/2016
11/9/2016
11/15/2016
11/21/2016
11/27/2016
12/3/2016
12/9/2016
12/15/2016
12/21/2016
12/27/2016
1/2/2017
1/8/2017
1/14/2017
1/20/2017
1/26/2017
2/1/2017
2/7/2017
2/13/2017
2/19/2017
2/25/2017
3/3/2017
3/9/2017
3/15/2017
3/21/2017
3/27/2017
4/2/2017
4/8/2017
4/14/2017
4/20/2017
4/26/2017
5/2/2017
5/8/2017
5/14/2017
5/20/2017
5/26/2017
6/1/2017
6/7/2017
6/13/2017
6/19/2017
6/25/2017
7/1/2017
7/7/2017
7/13/2017
7/20/2017
%
BOGOTA - Sum of FAILS_INTER_ENB_HO
99.30%
99.20%
99.10%
99.00%
98.90%
98.80%
98.70%
98.60%
98.50%
98.40%
98.30%
98.20%
98.10%
98.00%
97.90%
97.80%
97.70%
97.60%
97.50%
97.40%
Spectral Eficiency - UL
26
01/08/2017
© Nokia 2014
Motivación
• El PS-NQI de LTE tiene la siguiente fórmula:
LTE NQI (%) =[ QDA(%) * QDR(%) * PS_RETENTION_LTE(%) * Weighted Availability(%) * QDE_DL(%) * QDE_UL(%) / 10e10 ]
• Donde uno de los principales ofensores es el componente QDE_UL con límite para ser considerado
muestra buena es de 0.35 bps/Hz de acuerdo al documento AMX-LTE NQI Rev K
27
01/08/2017
© Nokia 2014
Cambios para mejorar la Eficiencia Espectral UL (Cambios Online en tabla LNCEL)
28
Valor
Valor
Objetivo
Anterior Nuevo
Disminución de la cantidad de PRB,
10
4 para tener mayor densidad de
potencia por PRB
Parametro
Nombre del Parametro
Descripción
iniPrbsUl
Initial amount of PRBs in uplink
Defines the initial amount of maximum PRBs
in uplink.
iniMcsUl
Initial MCS in uplink
The parameter defines an initial Modulation
and Coding Scheme (MCS) to be used on
PUSCH for other use than random access
message 3
ulsNumSchedAreaUl
Number of scheduling areas for UL Defines the number of scheduling areas
scheduler
supported by the PUSCH.
3
ulpcLowqualSch
Uplink power control PUSCH
configuration - Lower SINR
threshold for PUSCH power
command decision
Lower threshold of the power control window
for the SINR (signal quality) for PUSCH / SRS
component
3
ulpcLowlevSch
Uplink power control PUSCH
configuration - Lower RSSI
threshold for PUSCH power
command decision
Lower threshold of the power control window
for the RSSI (signal level) for PUSCH / SRS
component
-103
ulpcUplevSch
Uplink power control PUSCH
configuration - Upper RSSI
threshold for PUSCH power
command decision
Upper threshold of the power control window
for the RSSI (signal level) for PUSCH / SRS
component.
-96
01/08/2017
© Nokia 2014
4
Al tener mayor potencia por PRB,
6 se pueden usar MSC más altos,
para mejorar la eficiencia espectral
Al pasar de 3 a 6 áreas principales
6 de asignación del espectro, se tiene
mayor utilización de este
Reducir la ventana de power
control relacionado con el SINR
9 inicialmente tiene un rango de 12
dB, con el cambio pasa a un rango
de 6dB
Para compenzar, cuando es
posible, el aumento de potencia
-106 transmitida por el terminal, por
hacer más exigente el
ulpcLowqualSch
Para compenzar, cuando es
posible, el aumento de potencia
-99 transmitida por el terminal, por
hacer más exigente el
ulpcLowqualSch
Valores Iniciales
+1 dB Or + 3dB
- 1dB
Valores Finales
SINR
SINR
Resumen Cambios
Power Control
-1dB
15 dB
+1 dB Or + 3dB
- 1dB
-1dB
+1 dB Or + 3dB
PC Window
0 db
-1dB
+1 dB Or + 3dB
+1 dB Or + 3dB
+1 dB Or + 3dB
15 dB
+1 dB Or + 3dB
PC Window
0 db
-1dB
+1 dB Or + 3dB
+1 dB Or + 3dB
+1 dB Or + 3dB
9dB
3dB
RSSI
RSSI
-103dB
-96dB
-106dB
Se hace más estrecha la ventana de Quality, haciendo más estricto el nivel bajo de
calidad, adicionalmente, se reduce la ventana de nivel en 3db
29
01/08/2017
© Nokia 2014
-99dB
Resumen Cambios
Number of scheduling areas for UL scheduler
Se aumenta la cantidad de áreas de scheduling de 3 a 6 haciendo un
mejor uso del espectro disponible, principalmente en escenarios de
ráfagas de datos, como es el caso de Claro Colombia
30
01/08/2017
© Nokia 2014
NQI Tendencia a mejora
Usaquen
Riohacha
Tunja
Villavicencio
Cluster Daily (LTE PS NQI): (All)
LTE PS NQI%
QDA %
QDR %
31
QDE DL%
QDE UL%
PS Retention %
Cluster Daily (LTE PS NQI): (Multiple Items)
Availability%
LTE PS NQI%
100.00%
95.00%
90.00%
85.00%
80.00%
75.00%
70.00%
65.00%
60.00%
55.00%
50.00%
100.00%
99.00%
98.00%
97.00%
96.00%
95.00%
94.00%
93.00%
92.00%
91.00%
90.00%
01/08/2017
© Nokia 2014
QDA %
QDR %
QDE DL%
QDE UL%
PS Retention %
Availability%
Top 10 Worst Cells
• Listado de los Top 10 Worst Cells, basados en variación de LTE_5218F – componente del
QDA, principal causa observada, sobre propagación de los sectores, se hace rollback de
la parametrización y se proponen cambios físicos
eNB Name
MED.Univentas
MED.Parque Itagui
MED.Univentas
MED.IND Corona Sumicol:H4
MED.IND Corona Sumicol:H1
MED.Ajizal
MED.Polideportivo Sur
MED.RB Centro Moda-2
MED.Equs
MED.Parque Itagui
32
01/08/2017
LNCEL_NAME
MED.Univentas_L3
MED.Parque Itagui_L3
MED.Univentas_L1
MED.IND Corona Sumicol:H4_L1
MED.IND Corona Sumicol:H1_L1
MED.Ajizal_L2
MED.Polideportivo Sur_L3
MED.RB Centro Moda-2_L3
MED.Equs_L2
MED.Parque Itagui_L2
© Nokia 2014
MRBTS
524572
524536
524572
524837
524834
524420
524667
524902
524742
524536
LNBTS
524572
524536
524572
524837
524834
524420
524667
524902
524742
524536
LTE_5218f Total E- LTE_5218f Total E- LTE_5218f Total ELTE_1339a
UTRAN RRC Conect UTRAN RRC Conect UTRAN RRC Conect
Average UE
LNCEL
Setup Succ Rati.
Setup Succ Rati.
Setup Succ Rati. distance to base
Interval 1
Interval 2
Variation
station
3
3
1
1
1
2
3
3
2
2
98
97.98
99.17
98.7
99.27
98.58
99.34
98.52
98.57
98.34
96.65
96.67
97.88
97.72
98.35
97.69
98.49
97.75
97.82
97.64
-1.38
-1.34
-1.3
-0.99
-0.93
-0.9
-0.86
-0.78
-0.76
-0.71
2.41
1.09
0.36
0.73
0.34
1.37
0.54
0.52
1.34
0.87
Top 10 Worst Cells RF Details
• Recomendaciones de cambios físicos
eNB Name
MED.Univentas
MED.Parque Itagui
MED.Univentas
MED.IND Corona Sumicol:H4
MED.IND Corona Sumicol:H1
MED.Ajizal
MED.Polideportivo Sur
MED.RB Centro Moda-2
MED.Equs
MED.Parque Itagui
33
01/08/2017
LNCEL_NAME
MED.Univentas_L3
MED.Parque Itagui_L3
MED.Univentas_L1
MED.IND Corona Sumicol:H4_L1
MED.IND Corona Sumicol:H1_L1
MED.Ajizal_L2
MED.Polideportivo Sur_L3
MED.RB Centro Moda-2_L3
MED.Equs_L2
MED.Parque Itagui_L2
© Nokia 2014
Baseline RF Tool
RF
Electrical Mechanical
MRBTS LNBTS LNCEL Antenna
Tilt, deg
Tilt, deg
Ht, m
524572
524536
524572
524837
524834
524420
524667
524902
524742
524536
524572
524536
524572
524837
524834
524420
524667
524902
524742
524536
3
3
1
1
1
2
3
3
2
2
17
34
17
12
12
17
20
25
11
34
10
10
10
6
8
6
7
0
3
10
0
4
5
0
0
6
0
9
3
7
Remarks
ET is at maximum already. Mechanical tilt changed from 0 to 3deg.
ET is at maximum already. Mechanical tilt change from 4 to 6deg.
ET is at maximum already. Mechanical tilt from 5 to 7deg.
Electrical tilt to change from 6 to 8deg.
Electrical tilt to change from 8 to 10deg.
Electrical tilt change from 6 to 8deg.
Electrical tilt change from 7 to 9deg.
Electrical tilt to change from 0 to 2deg.
Electrical tilt change from 3 deg to 6deg.
ET is at maximum already. Mechanical tilt change from 7 to 10deg.
LTE1491: Additional Layer 1 Performance Measurements
34
01/08/2017 © Nokia 2014
Confidential
Feature Description
.
The LTE1491: Additional Layer 1 Performance Measurements feature introduces the
new Layer 1 performance management (PM)
•
counters within the Flexi Multiradio BTS.
Motivation & benefits
Operator benefits:
- This feature improves performance monitoring capabilities by implementing additional
performance measurements.
•
•
End-user benefits:
- This feature does not affect the end-user experience.
Impact on network management tools
•
This feature has no impact on network management tools.
Impact on system performance and capacity
•
35
01/08/2017
Additional Layer 1 Performance Measurements feature introduces more than 600 new counters and the operator
should observe caution in having the counters collected within a 15-minute interval when enabling the feature (Claro
Colombia 60 minutes).
© Nokia 2014
Description - How does it work .
•
Feature introduces additional layer 1 measurements per sub bands according to frequency
-
These counters are introduced to fill the gaps in the Flexi Multi-radio BTS from what is currently
being provided in the BCU3 for KDDI
•
These counters will allow very detailed channel quality analysis
•
New measurement group:
-
New PM
counters
#612
8031 - LTE SINR
Note
•
36
New parameters introduced:
-
Activation flag LNBTS:actL1PM
-
Measurement interval PMRNL:mtSINR
01/08/2017
© Nokia 2014
Please note that feature introduces huge volume
of PM counters which can affect the performance
• eNB  in terms of overload decreased max number of
UEs per TTI
• NetAct  increased volume of PM data to be
downloaded and processed
Description - How does it work .
New counters overview
PRB usage
•Per 10 QCI groups:
1,2,3,4,5,6,7,8,9,10
•Per DL and UL separately
•For SRB separately
#22
counters
Transmission power
•Average tranasmission power
•Maximum transmission power
#2
counters
37
01/08/2017
© Nokia 2014
Received Total Wideband
Power (RTWP)
Average UL loT (Interference
over Thermal)
•Average RTWP for each Rx
Antenna 1-8(added antennas
3-8)
•Maximum RTWP
•PUSCH distribution, per cell
for the following bins: For the
following bins: Bin0 – Bin8
SINR distribution DL post
compensation
SINR distribution DL post compensation
#9
counters
•Per 10 subbands separately
•For the following bins: Bin0 Bin19
#280
counters
Average SIR distribution
•For the following bins: For the
following bins: Bin0 - Bin9
#9
counters
#10
counters
•Added to address the case where the UE responds with 2 CQIs for
MIMO)
•Two groups, one for subbands 1-13 – CW2, the other in total
•For the following bins: Bin0 - Bin19
#280
counters
Description - How does it work .
Subbands mapping
Subband
1
2
3
4
5
6
7
8
9
10
11
12
13
38
01/08/2017
PRBs for 1.4
MHz
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
© Nokia 2014
PRBs for 3
MHz
0 to 3
4 to 7
8 to 11
12 to 14
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
PRBs for 5
MHz
0 to 3
4 to 7
8 to 11
12 to 15
16 to 19
20 to 23
24
N/A
N/A
N/A
N/A
N/A
N/A
PRBs for 10
MHz
0 to 5
6 to 11
12 to 17
18 to 23
24 to 29
30 to 35
36 to 41
42 to 47
48 to 49
N/A
N/A
N/A
N/A
PRBs for 15
MHz
0 to 7
8 to 15
16 to 23
24 to 31
32 to 39
40 to 47
48 to 55
56 to 63
64 to 71
72 to 74
N/A
N/A
N/A
PRBs for 20
MHz
0 to 7
8 to 15
16 to 23
24 to 31
32 to 39
40 to 47
48 to 55
56 to 63
64 to 71
72 to 79
80 to 87
88 to 95
96 to 99
Description - How does it work .
New counters
12 new counters
Counter name
Description
AVG_RTWP_RX_ANT_{1-8}
(M8005C306 - M8005C313)
This measurements provide the average Received Total Wideband Power (RTWP) for Rx antenna
1-12 at the end of collection interval.
AVG_RTWP_RX_ANT_{9-12}
Trigger event: This measurements are updated by accumulating the RTWP in Watts for Rx
antenna 1-8 from every sample period and calculating the average at the end of the collection
interval. Note: This measurement is reported in the units of 0.1 dBm with an offset of 1300. If
the dBm is 0, this measurements are reported as 1300 and if the dBm is -130.0, this
measurements are reported as 0.
(M8005C336 - M8005C339)
#LTE Power and Quality UL
Average RTWP for Rx (LTE_1278a –
antenna {1-12} LTE1285a) =
39
01/08/2017
© Nokia 2014
AVG_RTWP_RX_ANT_{1-12}
Description - How does it work .
New counters
1 new counter
Counter name
Description
MAX_RTWP
(M8005C314)
This measurement provides the maximum Received Total Wideband Power (RTWP) at the end of
collection interval.
#LTE Power and Quality UL
Trigger event: This measurement is updated by collecting the individual antenna RTWP values
in milliwatts every sample period and comparing to a stored maximum value. If any of the new
collected values are larger than the existing maximum value, the largest collected value replaces
the maximum value. The measurement is reported with the maximum dBm value at the end of
the collection interval.
Max. RTPW (new) =
40
01/08/2017
© Nokia 2014
MAX_RTWP
Description - How does it work .
New counters
10 new counters
Counter name
Description
UL_PRB_USAGE_SAEB_QOS_1-9
(M8011C140 - M8011C148)
This measurements provide the percentage usage of uplink Physical Resource Blocks (PRB)
(partially/fully) for DTCH traffic for SAEB QoS levels 1_255.
UL_PRB_USAGE_SAEB_QOS_10_255
(M8011C149)
Trigger event: This measurements are determined by accumulating the number of uplink PRBs
(i.e. the sum of complete PRBs and fractions of PRBs) used for DTCH traffic for SAEB QoS levels
1-255 and the number of available uplink PRBs for DTCH traffic every sample period. At the end
of the collection interval the accumulated used PRBs are divided by the accumulated available
PRBs to obtain the measurement percentage value.
#LTE Cell Resource
LTE_1293a – LTE_1301a - Uplink PRB Usage for DTCH traffic for SAEB QoS level {1-9}
LTE_1302a - Uplink PRB Usage for DTCH traffic for SAEB QoS level 10 to 255
41
01/08/2017
© Nokia 2014
Description - How does it work .
New counters
1 new counter
Counter name
Description
UL_PRB_USAGE_SRB
(M8011C150)
This measurement provides the percentage usage of uplink Physical Resource Blocks (PRB)
(partially/fully) for DCCH and CCCH data.
#LTE Cell Resource
Trigger event: This measurement is determined by accumulating the number of uplink PRBs
(i.e. the sum of complete PRBs and fractions of PRBs) used for DCCH and CCCH data and the
number of available uplink PRBs for DCCH and CCCH data every sample period. At the end of
the collection interval the accumulated used PRBs is divided by the accumulated available PRBs
to obtain the percentage value.
% of UL PRB
usage for DCCH (new) =
and CCCH
42
01/08/2017
© Nokia 2014
UL_PRB_USAGE_SRB
Description - How does it work .
New counters
10 new counters
Counter name
Description
DL_PRB_USAGE_SAEB_QOS_{1-9}
(M8011C151 - M8011C159)
This measurements provide the percentage usage of downlink Physical Resource Blocks (PRB)
(partially/fully) for DTCH traffic for SAEB QoS level 1_255
DL_PRB_USAGE_SAEB_QOS_10_255
(M8011C160)
Trigger event: This measurements are determined by accumulating the number of downlink
PRBs (i.e. the sum of complete PRBs and fractions of PRBs) used for DTCH traffic for SAEB QoS
level 1-255 and the number of available downlink PRBs for DTCH traffic every sample period. At
the end of the collection interval the accumulated used PRBs are divided by the accumulated
available PRBs to obtain the measurement percentage value.
#LTE Cell Resource
LTE_1303a – LTE_1311a - Downlink PRB Usage for DTCH traffic for SAEB QoS level {1-9}
LTE_1312a - Downlink PRB Usage for DTCH traffic for SAEB QoS level 10 to 255
43
01/08/2017
© Nokia 2014
Description - How does it work .
New counters
1 new counter
Counter name
Description
DL_PRB_USAGE_SRB
(M8011C161)
This measurement provides the percentage usage of downlink Physical Resource Blocks (PRB)
(partially/fully) for DCCH and CCCH data.
#LTE Cell Resource
Trigger event: This measurement is determined by accumulating the number of downlink PRBs
(i.e. the sum of complete PRBs and fractions of PRBs) used for DCCH and CCCH data and the
number of available downlink PRBs for DCCH and CCCH data every sample period. At the end of
the collection interval the accumulated used PRBs is divided by the accumulated available PRBs
to obtain the percentage value.
% of DL PRB
usage for DCCH (new) =
and CCCH
44
01/08/2017
© Nokia 2014
DL_PRB_USAGE_SRB
Description - How does it work .
New counters
9 new counters
Counter name
Description
UL_IOT_PUSCH_DIST_BIN_{0-8}
(M8005C317 - M8005C325)
This measurements provide the 50 percentile value of the uplink Interference Power over
Thermal (IoT) Noise Power for the PUSCH Resource Block (RB) distribution bin 0-8.
#LTE Power and Quality UL
To increase the granularity, the counter is reported in 10* dB units.
To support the PUSCH RB distribution, there are 9 bins (bin0 to bin8).
The PUSCH RBs would be evenly distributed (as much as possible) across the 9 bins with bin 0
and bin 8 having an equal number of PUSCH RBs.
Trigger event: This measurements are updated by calculating the IoT every sample period the
noise measurement is received as per the PUSCH RB distribution bin 0-8 and taking the 50
percentile value at the end of the collection interval.
45
01/08/2017
© Nokia 2014
Description - How does it work .
New counters
10 new counters
Counter name
Description
AVG_SIR_DIST_BIN_{0-9}
(M8005C326 - M8005C335)
This measurements provide the number of PUSCH Resource Blocks (RB) having an average
Signal to Interference Ratio (SIR) value:
- less than 1.0 dB
- from 1.0 dB to less than 4.0 dB
- from 4.0 dB to less than 7.0 dB
- from 7.0 dB to less than 10.0 dB
- from 10.0 dB to less than 13.0 dB
- from 13.0 dB to less than 16.0 dB
- from 16.0 dB to less than 19.0 dB
- from 19.0 dB to less than 22.0 dB.
- from 22.0 dB to less than 25.0 dB
- equal or greater than 25.0 dB.
#LTE Power and Quality UL
Trigger event: This measurements are updated by calculating the SIR for each of the available
PRBs in the uplink (PUSCH) every sample period and incrementing the corresponding bin having
an average SIR value from adequate range (the same as above)
46
01/08/2017
© Nokia 2014
Description - How does it work .
New counters
2 new counters
Counter name
Description
AVG_TRANS_PWR
(M8010C74)
This measurements provide the average / maximum transmit power in milliWatts at the end of
the collection interval.
MAX_TRANS_PWR
(M8010C75)
Trigger event: This measurements calculate the total transmitted power (in milliWatts) every
sample period and determines average / maximum value at the end of collection interval.
#LTE Power and Quality DL
47
01/08/2017
© Nokia 2014
Maximum
transmit power (new) =
MAX_TRANS_PWR
Average
transmit power (new) =
AVG_TRANS_PWR
Description - How does it work .
New counters
260 new counters
Counter name
Description
DL_SINR_DIST_SB{1-13}_BIN{0-19}
(M8031C0 - M8031C259)
This measurement is provided for Subbands 1-13 downlink Signal to Interference and Noise
Ratio (SINR) post-compensation values that are greater than X dB and less than or equal to Y
dB.
{ X=(-10; -8; -6; -4; -2; 0; 2; 4; 6; 8; 10; 12; 14; 16; 18; 20; 22; 24; 26; 28),
Y=(-8; -6; -4; -2; 0; 2; 4; 6; 8; 10; 12; 14; 16; 18; 20; 22; 24; 26; 28; 30) }
#LTE SINR
Trigger event: This measurement is updated for each UE every TTI by using the UE's most
recent subband CQI to calculate Subbands 1-13 downlink SINR post-compensation and the bin
is incremented every sample period (5 seconds) with the respective number of calculated values
where each one is greater than X dB and less than or equal to Y dB.
48
01/08/2017
© Nokia 2014
Description - How does it work .
New counters
260 new counters
Counter name
Description
DL_SINR_DIST_CW2_SB{113}_BIN{0-19}
(M8031C260 - M8031C519)
This measurement is provided for Subbands 1-13 downlink Signal to Interference and Noise
Ratio (SINR) post-compensation values (2 CQIs or codewords) that are greater than X dB and
less than or equal to Y dB.
{ X=(-10; -8; -6; -4; -2; 0; 2; 4; 6; 8; 10; 12; 14; 16; 18; 20; 22; 24; 26; 28),
Y=(-8; -6; -4; -2; 0; 2; 4; 6; 8; 10; 12; 14; 16; 18; 20; 22; 24; 26; 28; 30) }
#LTE SINR
Trigger event: This measurement is updated for each UE every TTI by using the UE's most
recent subband CQIs (i.e. 2 CQIs or codewords) to calculate Subbands 1-13 downlink SINR postcompensation and the bin is incremented every sample period (5 seconds) with the respective
number of calculated values where each one is greater than X dB and less than or equal to Y dB.
49
01/08/2017
© Nokia 2014
Description - How does it work .
New counters
20 new counters
Counter name
Description
DL_SINR_DIST_WB_BIN{0-19}
(M8031C520 - M8031C539)
This measurement is provided for Wideband downlink Signal to Interference and Noise Ratio
(SINR) post-compensation values that are greater than X dB and less than or equal to Y dB.
{ X=(-10; -8; -6; -4; -2; 0; 2; 4; 6; 8; 10; 12; 14; 16; 18; 20; 22; 24; 26; 28),
Y=(-8; -6; -4; -2; 0; 2; 4; 6; 8; 10; 12; 14; 16; 18; 20; 22; 24; 26; 28; 30) }
#LTE SINR
Trigger event: This measurements are updated for each UE every TTI by using the UE's most
recent wideband CQI to calculate Wideband downlink SINR post-compensation and the bin is
incremented every sample period (5 seconds) with the respective number of calculated values
where each one is greater than X dB and less than or equal to Y dB.
50
01/08/2017
© Nokia 2014
Description - How does it work .
New counters
20 new counters
Counter name
Description
DL_SINR_DIST_CW2_WB_BIN{0-19}
(M8031C540 - M8031C59)
This measurement is provided for Wideband downlink Signal to Interference and Noise Ratio
(SINR) post-compensation values (2 CQIs or codewords) that are greater than X dB and less
than or equal to Y dB.
{ X=(-10; -8; -6; -4; -2; 0; 2; 4; 6; 8; 10; 12; 14; 16; 18; 20; 22; 24; 26; 28),
Y=(-8; -6; -4; -2; 0; 2; 4; 6; 8; 10; 12; 14; 16; 18; 20; 22; 24; 26; 28; 30) }
#LTE SINR
Trigger event: This measurements are updated for each UE every TTI by using the UE's most
recent wideband CQIs (i.e. 2 CQIs or codewords) to calculate Wideband downlink SINR postcompensation and the bin is incremented every sample period (5 seconds) with the respective
number of calculated values where each one is greater than X dB and less than or equal to Y dB.
51
01/08/2017
© Nokia 2014
Activation
Before you start
The Feature Activation Flag Additional Layer 1 PM (actL1PM)
parameter is used to activate the feature. Modification of this parameter does not require evolved node B (eNB) restart or cell locking.
Parameters used for activating and configuring LTE1491
1. Configure the LTE SINR (mtSINR) parameter.
a) Go to the Radio Network Configuration page.
b) Expand the MRBTS object.
c) Expand the LNBTS object.
d) Select the PMRNL object.
e) Set the LTE SINR (mtSINR) parameter to a permitted value. The default value is 15min.
2. Set the activation flag.
a) From the expanded MRBTS object, select the LNBTS object.
b) Set the Feature Activation Flag Additional Layer 1 PM (actL1PM) parameter value to true.
52
01/08/2017
© Nokia 2014
Test
For this TRIAL have chosen the following sites:
•
SUC.Chalan
•
CAR.Morros
•
BAR.Carulla 72
•
CAR.Mamonal-1
•
CAL.Recuerdo
•
MED.Los Huesos
The selection criterion used includes sites with high and low spectral efficiency and with an average number of RRC connected users
around 13.
MRBTS_NAME LTE_5747a DL Spectral efficiency LTE_5748a UL Spectral efficiency LTE_805a The average number of RRC connected users
SUC.Chalan
3.79
0.64
12.71
CAR.Morros
3.16
1.06
9.07
BAR.Carulla 72
1.94
1.10
7.95
CAR.Mamonal-1
1.56
0.37
23.14
CAL.Recuerdo
1.13
0.38
17.43
MED.Los Huesos
1.04
0.51
14.43
53
01/08/2017
© Nokia 2014
AVG RTWP
El promedio de RTWP, para
BAR.CARULLA 72 oscila entre los:
-92dBm => alto tráfico
-101 dBm =>bajo tráfico.
AVG RTWP (dBm)
Sitio
Alto tráfico Bajo tráfico
MED.Los Huesos
-92
-99
CAL.Recuerdo
-92
-98
CAR.Morros
-94
-101
BAR.Carulla 72
-92
-101
SUC.Chalan
-97
-101
CAR.Mamonal-1
-94
-100
En la tabla se observan los valores de Avg RTWP en cada uno de los sitios del trial. Para mayor detalle favor referirse a los reportes D+7.
54
01/08/2017
© Nokia 2014
LTE1434 Flexi Multiradio BTS antenna Rx RF-sniffing
Con ayuda del Feature LTE1434 “Flexi Multiradio BTS antenna Rx RF-sniffing” se obtuvo los niveles de señal en UL en tamaño de 75kHz.
Estas gráficas a horario de alto tráfico del sitio.
55
01/08/2017
© Nokia 2014
LTE1434 Flexi Multiradio BTS antenna Rx RF-sniffing
Esta gráfica de RF Sniffing muestra la acumulación de energía en un periodo de muestreo y span de frecuencia. El cálculo del promedio de
RTWP se realiza al final del intervalo de recolección.
En uno de esos periodos se observa un nivel de señal de -130.2dBm para una resolución espectral de 75kHz, por tanto, para poder compararlo
con el promedio obtenido en los contadores del feature se deben realizar algunos cálculos adicionales como se observa en la siguiente tabla:
Valor @75kHz (dBm) miliWatts @75kHz Energía RTWP @15MHz (mW) Contador AVG RTWP (dBm)
-130.2
9.54993E-14
1.90999E-11
-107.1897
1.
2.
3.
4.
56
Se realiza la conversión de dBm a miliwatts  =10^(-130.2/10)  9.55E-14
Se calcula el número de veces que está la resolución espectral en el ancho de banda manejado (15MHz)  =15000/75  200
El resultado anterior se multiplica por los miliwatts  =((10^(-130.2/10))*200)  1.90999E-11
Finalmente se vuelve a convertir a dBm el último resultado  =10*LOG10(1.90999E-11)  -107.18dBm
01/08/2017
© Nokia 2014
AVG SIR Distr_UL
Para BAR.Carulla 72 la mayor
utilización de PRBs en UL está
sobre 22dB en SINR.
Para CAR.Mamonal-1 es
necesario validar si el
comportamiento es el esperado o
si se debe mejorar los niveles de
SINR en UL.
57
01/08/2017
© Nokia 2014
AVG SIR Distr_UL
CAR.Mamonal1
Para validar el comportamiento del SINR en UL de los sitios mencionados se analiza la gráfica de Timing Advance de estos. En BAR.Carulla 72 se observa
que la mayor concentración de usuarios se encuentra en un rango cercano a la celda. Por otro lado, CAR.Mamonal-1 presenta muestras que superan
1km de distancia, esto es normal ya que su ubicación y área de cobertura están frente al mar y por tanto, el comportamiento de SINR para
CAR.Mamonal-1 es el esperado.
58
01/08/2017
© Nokia 2014
TRANSMIT POWER
Los picos máximos
llegan hasta 27W
La potencia oscila
entre 2.5W y 3.5W
Transmit Power (Watts)
Sitio
Max
Avg
BAR.Carulla 72
27
2.5 - 3.5
CAR.Morros
27.6
2.5 - 3.2
SUC.Chalan
28
3.1 - 4
Estos indicadores están disponibles en sitios con módulos RF FRMr2.3 o
superior ejemplo FRHD y FRHC
Con estadísticas como estas se puede determinar el máximo de potencia transmitida en un determinado eNB. En el caso de BAR.Carulla 72 como en
otros, se puede demostrar que la potencia transmitida está por debajo de la potencia total por antena (30W).
Estos dos indicadores pueden ser utilizados para tratar de dar cumplimiento a lo establecido en la resolución 000754 de la ANE, la cual tiene como
objeto “controlar los niveles de exposición de las personas a los campos electromagnéticos”.
59
01/08/2017
© Nokia 2014
AVG SIR Distr_UL
Comportamiento del SINR de la
sub-banda 1 para un ancho de
banda de 15 MHz
Con 75 PRBs tenemos contadores para las primeras 10 sub.bandas. Si al comparar las gráficas de distribución del DL SINR entre las diferentes
sub bandas se observa una diferencia considerable, es posible que exista alguna interferencia externa.
Adicionalmente, este feature podría ayudar a optimizar el uso del LTE1800 (Downlink interference shaping), el cual prioriza el uso del espectro.
60
01/08/2017
© Nokia 2014
Conclusiones
.
61
•
Este Feature con contadores adicionales mejora la capacidad de supervisión de la red, lo que permite detectar
degradaciones en UL, altas transmisiones de potencia en DL y posibles interferencias.
•
El grupo de contadores M8005C306-M8005C309 permite observar el promedio de RTWP en una celda, no obstante, se
debe tener presente que contrario a lo que ocurre en 3G, en LTE la asignación de recursos se realiza por PRBs (los menos
interferidos y cargados tienden a ser asignados primero), por lo tanto, el valor de RTWP no está relacionado necesariamente
con limitantes de capacidad o presencia de interferencia ya que la utilización del ancho de banda de la portadora no es
homogénea como se observó en las gráficas de RF Sniffing de alto tráfico.
•
El grupo de contadores M8005C326-M8005C335 permite observar la cantidad de PRBs usados en UL para determinados
rangos de SINR, lo que permite monitorear los niveles de éste en los eNB y con otros análisis determinar si el
comportamiento es el adecuado.
•
Los contadores de Transmit Power pueden ser utilizados para tratar de dar cumplimiento a lo establecido en la resolución
000754 de la ANE, la cual tiene como objeto “controlar los niveles de exposición de las personas a los campos
electromagnéticos”.
•
Este Feature no afecta la experiencia del usuario final.
01/08/2017
© Nokia 2014
Análisis RTWP realizado con estadísticas entre el 21 y 23 de Julio
Se toma el mínimo de los valores máximos reportados por las celdas en el período de observación
PERIOD_START_TIME
2017-07-21 03:00:00
2017-07-21 06:00:00
2017-07-22 22:00:00
2017-07-21 04:00:00
2017-07-21 03:00:00
2017-07-21 04:00:00
2017-07-23 05:00:00
2017-07-23 05:00:00
2017-07-22 23:00:00
2017-07-21 04:00:00
2017-07-21 09:00:00
2017-07-21 04:00:00
2017-07-21 06:00:00
2017-07-21 04:00:00
2017-07-21 02:00:00
2017-07-21 10:00:00
2017-07-23 15:00:00
2017-07-22 09:00:00
2017-07-23 03:00:00
2017-07-21 07:00:00
2017-07-22 05:00:00
2017-07-21 06:00:00
2017-07-22 00:00:00
2017-07-22 02:00:00
2017-07-22 04:00:00
2017-07-21 02:00:00
2017-07-21 04:00:00
2017-07-23 04:00:00
2017-07-22 04:00:00
62
01/08/2017
LNCEL_NAME
CAL.Shangai_L1
CAU.Corinto_L2
BOG.Villa de Zarzamora_L1
UBA.Universidad_L2
BUC.Alcaldia_L2
TOL.Flandes-2_L3
MET.San Luis de Cubaral_L2
CHI.Chia Norte_L1
TUN.Uniboyaca_L1
GIR.La Estacion-2_L3
MED.La America_L1
UBA.Universidad_L3
CAU.Corinto_L1
TUN.Muiscas_L2
CAU.Corinto_L3
PAL.Barrio Nuevo_L2
TUN.Uniboyaca_L3
HUI.Bruselas_L1
SUC.Tolu_L2
TUN.La Esmeralda_L1
CAL.Villa del Lago_L2
TUN.La Fuente_L1
PER.Tokyo_L2
CUN.Cachipay_L1
NAR.La Cruz_L1
BOG.Aero Nuevo Dorado_L1
BUC.Antonia Santos-2_L3
CAD.Marquetalia-2_L1
CAL.Los Lagos_L1
© Nokia 2014
M8005C306/10
Average RTWP
ANT 1
-48
-57
-87.9
-63.1
-65.9
-70.5
-73.5
-78.9
-78.3
-76.3
-92
-76.3
-80.1
-77.1
-77.7
-77.6
-85.2
-77.7
-80.3
-80.3
-79.1
-79.7
-85.9
-79.9
-80
-80.2
-80.2
-80.5
-83.1
M8005C307/10
Average RTWP
ANT 2
-95.4
-56.4
-57.5
-63
-68
-70.8
-71.4
-78.1
-76.1
-78.6
-91.6
-78.1
-80.2
-78.5
-78
-77.4
-82
-79.2
-85.8
-80.3
-84.1
-79.9
-79.7
-81.2
-85.2
-102
-84.9
-82.4
-81.9
M8005C308/10
Average RTWP
ANT 3
0
-55.3
0
-64.7
0
-71
-73.5
-82.2
-77.6
-78.8
-91.9
-80.9
-77.1
-77.4
-78.6
-77.8
-77.4
-78.6
-87.3
-79.2
-84.3
-80.6
-80
-83.2
-83.1
0
0
-83
-82.8
M8005C309/10
Average RTWP
ANT 4
0
-56.8
0
-62
0
-71.3
-76.8
-76.1
-77.2
-77
-76.3
-76.6
-80.3
-79.1
-77.2
-77.3
-78
-77.8
-77.8
-78.9
-81.2
-79.2
-85.1
-80
-84.7
0
0
-80.9
-80.6
Linear Average MinOfmax_RT
RTWP
WP
-71.7
-48
-56.375
-55.3
-72.7
-57.5
-63.2
-62
-66.95
-65.9
-70.9
-70.5
-73.8
-71.4
-78.825
-76.1
-77.3
-76.1
-77.675
-76.3
-87.95
-76.3
-77.975
-76.3
-79.425
-77.1
-78.025
-77.1
-77.875
-77.2
-77.525
-77.3
-80.65
-77.4
-78.325
-77.7
-82.8
-77.8
-79.675
-78.9
-82.175
-79.1
-79.85
-79.2
-82.675
-79.7
-81.075
-79.9
-83.25
-80
-91.1
-80.2
-82.55
-80.2
-81.7
-80.5
-82.1
-80.6
Observacion
Se sugiere revisión de O&M
Probable interferencia externa - RF Sniffing
Se sugiere revisión de O&M
Se sugiere revisión de O&M
Probable interferencia externa - RF Sniffing
Probable interferencia externa - RF Sniffing
Probable interferencia externa - RF Sniffing
Probable interferencia externa - RF Sniffing
Probable interferencia externa - RF Sniffing
RF Snifing CAU.Corinto, diferencia entre muestras 6 min aprox
63
01/08/2017
© Nokia 2014
CAD.Marquetalia-2_L1 Antena 1: Se observa una
probable interferencia externa
CAL.Los Lagos_L1 Antena 1: Se observa probable
interferencia externa
64
01/08/2017
© Nokia 2014
CAD.Marquetalia-2_L1 Antena 3: Se observa una probable
interferencia externa
CAL.Villa del Lago_L2 Antena 1: Se observa
interferencia externa
NAR.La Cruz_L1 Antena 1: Se observa posiblemente interferencia
externa
VAL.Yumbo-2_L2 Antena 1: Se observa interferencia externa
65
01/08/2017
© Nokia 2014
PAL.Barrio Nuevo_L2 Antena 1: Se observa interferencia externa
VAL.Yumbo-4_L3 Antena 1: Se observa posible
interferencia.
MET.Barranca de Upia
66
01/08/2017 © Nokia 2014
Confidential
MET.Barranca de Upia
RF Sniffing Julio 5 2017
67
01/08/2017 © Nokia 2014
Confidential
LTE1434 “Flexi Multiradio BTS antenna
Rx RF-sniffing”
68
01/08/2017
Confidential
LTE1434 “Flexi Multiradio BTS antenna Rx RF-sniffing”
LTE1434 provides functionality that enables quality assessment of the radio environment
(UL interference) and of the deployed passive equipment (cables, connectors, etc) based
on the eNB’s own radio receiver.
This allows not only initial verification on site roll-out, but also on-demand/periodical
supervision measurements and troubleshooting oriented activities.
More specifically, one may execute the following:
1. RF scanning – use the eNB as a field spectrum analyzer (can be done online).
2. Passive intermodulation (PIM) simulation (dual carrier configuration).
3. Test to determine possible impact of PIM on UL quality (noise rise/“desensitization”)
69
01/08/2017
Confidential
LTE1434 “Flexi Multiradio BTS antenna Rx RF-sniffing”
RF scanning.
Conceptually equivalent to bringing a spectrum analyzer (with a receiver
antenna) to the field.
UL
interference
eNB
M-plane
eNB provides RF receiver
and processing, no need to
have external analyzer
70
01/08/2017
Confidential
BTS SM
or CLI
tool
• Visualization
• Analytics
Results are
exported in
commonly-used
HDF5 format.
LTE1434 “Flexi Multiradio BTS antenna Rx RF-sniffing”
Passive intermodulation products.
PIM products are signals generated whenever two or more signals centered at
different frequencies pass through a defective (non-linear) equipment. These
spurious signals arrive to the Rx receiver, increasing the noise levels and
affecting the UL SINR.
Applicable scenarios: more than one DL carrier on the
same antenna line, e.g., RF sharing or dual LTE carrier
configuration.
71
01/08/2017
Confidential
LTE1434 “Flexi Multiradio BTS antenna Rx RF-sniffing”
Passive intermodulation products testing: “desensitization”.
Sensitivity of UL receiver refers to minimum SINR required for a given
performance (e.g., required TP at cell edge). PIM products arriving to the UL
receiver will increase the noise floor, thereby decreasing the sensitivity (or
increasing the SINR requirements), hence the name of the test.
Classical test consists of
switching the transmitter on
and inspecting the received
signal (in absence of traffic)
72
01/08/2017
Confidential
RFM
Dual
frequency Tx
Rx
Combiners,
cables,
antennas, etc.
Collect Rx antenna samples and inspect signal
spectrum, check if there is a rise in noise due to
DL signal and PIM
LTE1434 “Flexi Multiradio BTS antenna Rx RF-sniffing”
HW requirements
Only FSMr3 in conjunction with RF HW version 2.2 or 2.3 are supported.
Feature activation
Both RF scanning (online) and PMI testing (offline) require that an “activation
flag”-type of parameter to be “on”.
RF scanning requires parameter actRfiTesting.
PIM testing requires parameter actPimTesting.
73
01/08/2017
Confidential
LTE1434 “Flexi Multiradio BTS antenna Rx RF-sniffing”
BTS SM additional requirements
Current implementation of RF scanning is based on a prototype from the T&I
organization, which was written in Matlab. Rather than recoding the
functionality, BTSSM calls the compiled version behind scenes and therefore
requires the Matlab compiler runtime environment (MCR).
MCR download and installed size is rather bulky (750 / 1500 MB). The installed
version must match the compiler used when building the application – in this
case, R15a 32 bits – as indicated by BTS SM.
74
01/08/2017
Confidential
Download the MCR and install on BTS SM host computer (e.g., LMT).
Reuse downloaded package (700-800 MB) when possible.
LTE1434 “Flexi Multiradio BTS antenna Rx RF-sniffing”
RF scanning: basic test execution – toggle activation parameters.
75
01/08/2017
Confidential
LTE1434 “Flexi Multiradio BTS antenna Rx RF-sniffing”
RF scanning: basic test execution – HW support.
Only one
capture type
available in
this case. Only
supported
modules
shown.
76
01/08/2017
Confidential
Single carrier
setup, no cell id
available for
choosing (needs
more than one
carrier per RFM).
FXED (GAIA
based) was
connected to eNB
but not available
for the test.
LTE1434 “Flexi Multiradio BTS antenna Rx RF-sniffing”
RF scanning: basic test execution – reference case: no interference signal.
UL spectrum
is flat, no
interference
is visible.
77
01/08/2017
Confidential
78
01/08/2017
Confidential