1. RNO Wind
Part I

2. Part I - Content Active set usage Pollution Accessibility
Adjs Optimization
Pollution
Pollution Identification
Accessibility
Downlink and Uplink Admission Control algorithm (not enough radio or transport resource, UE-BTS synchronization problems) and Congestion

3. Active Set Usage

4. Active Set Usage
M1013
(These counters are referred to cell addition and cell replacement – no target for deletion)
Absolute Value must be considered not Failure Rate!

5. Active Set Usage
Minor
Major
High # out-going attempts?
High # out-going fails for a defined ADJS?
Yes
Failure ADJS
Unbalanced ADJS
Zero attempts?
Yes
Yes
High # attempts for a source?
Yes
In – out pairs?
High # fails for a source?
Failure WCEL
Low used Adjs
No Adjs
Yes
Yes
Minor
Ping-Pong
Unbalanced WCEL
Filtering over attempts must be taken into count that:
- statistical data must stabilized over time.
- traffic distribution is not considered and a double-check to localize the event and DT feedback is required to understand if fenomena is traffic driven or cell dependent
Filtering over failure in absolute terms it is possible to find the major critical events

6. Active Set Usage Filtering criteria: Major Minor
- High number of failures for a defined out-going adjs (failure ADJS)
- high number of fail for a defined source (failure WCEL)
Minor
- high number of attempts in-comig and out-going for a defined pair with occasional failure (ping-pong)
Filtering action are required to find bi-lateral corrispondence
- very low number of attempt with failure (low used adjs)
- zero number of attempt for declared adjs– stabilized value (no adjs)
- high number of attempts with occsional failure for an out-going adjs (unbalanced ADJS)
Either in-coming or out-going condition is sufficient
- high number of attempts with occsional failure for a defined source (unbalanced WCEL)

7. Failure ADJS
Failure ADJS
Once anlyzed the RSCP, the coverage plot taking care to the evaluation of intersite-distance, it is easy to understand if target can be used.
If not only down tilt is possible or DERR (ADJS object Paremeter) cell to avoid the failure during SHO.
Down tilt must be carefully anlyzed.
If from Ec/No the cell can be recovered an individual offset or filtering (ADJS object Parameter) can be introduced to fovourite it
Analyze RSCP from DT & NWP coverage plot considering inter-site distance
Very low value of RSCP that not allow the adjs to be used
Yes
Target act as polluter?
Yes
Down tilt possibile?
DERR cell
Down tilt
Analyze Ec/No from DT
Ec/No offset

8. Failure ADJS – Individual Ncell Offset
time
P CPICH 1
P CPICH 2
P CPICH 3
Reporting Range
Reporting Event 1B
Reporting Event 1A
AdjsEcNoOffset
to modify measurement reporting behaviour. Effectively 'moves' cell border (shrinks or enlarges cell)
Enlarging Cell 3 by x dB
Ec/Io

9. Failure ADJS – Forbidding Neighbour Cell
Time
P CPICH 1
P CPICH 2
P CPICH 3
PCPICH3 is forbidden to affect the reporting range as its quality is quite unstable.
Reporting Range
AdjsDERR
to forbid a cell from reporting range calculation in some instances
Ec/Io

10. WCEL polluted/interfered?
Failure WCEL
Failure WCEL
Analyze Ec/No &BLER from DT & NWP coverage plot considering inter-site distance
Most of the Target failure during the 1A or 1C event.
Once anlyzed the Ec/No, BLER, the coverage plot taking care to the evaluation of intersite-distance, it is easy to understand if the WCEL is interferered/Polluted
If not, two KPIs allow to separate the dominant contribute among the 1A and 1C.
Relaxing the parameters an improvement should be achieved
The following gives the number of attempts per event
RT Services
KPI(1) = M1007C10 CELL ADD_REQUEST ON SHO FOR RT TRAFFIC
KPI(2) = M1007C12 CELL REPL_ REQUEST ON SHO FOR RT TRAFFIC
NRT Services
KPI(1) = M1007C27 CELL ADD_ REQUEST ON SHO FOR NRT TRAFFIC
KPI(2) = M1007C29 CELL REPL_REQUEST ON SHO FOR NRT TRAFFIC
Yes
WCEL polluted/interfered?
Pollution/Interference
Analyze Ec/No from DT
Yes
KPI(1) ?
Tune 1A
The failure rate for all the procedure can be estimated as well
ADD(REPL)_ FAIL_ONSHO _FOR_x / ADD(REPL)_REQ_ON_SHO_FOR_x + ADD(REPL)_ FAIL_ONSHO _FOR_x
M1007C14 / M1007C12 + M1007C14
M1007C36 /M1007C11 + M1007C36
M1007C30 / M1007C27 + M1007C30
M1007C37 / M1007C28 + M1007C37
M1007C31 / M1007C29 + M1007C31
Yes
KPI(2) ?
Tune 1C

11. Failure WCEL - 1A RNC Ec/Io time ActiveSetWeightingCoefficient
is used to weight either the measurement result of the best active set cell (0) or the sum of measurement results of all active set cells (<>0)
Ec/Io
Strongest CPICH in AS:
P CPICH 1
AdditionWindow
determines the relative threshold used by the UE to calculate the reporting range of event 1A. The threshold is either relative to the CPICH Ec/No measurement result of the best active set cell (0), or to the sum of active set measurement results (<>0)
P CPICH 2 1A
P CPICH 3
AdditionTime
defines the 'time-to-trigger' interval between the cell entering the reporting range and the UE sending the measurement report to the RNC with the 1A event
AdditionReportingInterval
defines the period of time that the UE wait, if the RNC is unable to add Ncell to AS, before sending further reports periodically, with interval AdditionReportingInterval, until the Ncell moves out of reporting range, or RNC adds Ncell to AS.
time
Measurement Report no
Add to
the AS?
RNC

12. Failure WCEL - 1C Ec/Io time ReplacementWindow
determines the margin by which the CPICH Ec/No measurement result of the monitored cell (MNew) must exceed the CPICH Ec/No measurement result of the an active set cell (MInAS) before the UE can send the event 1C triggered Measurement Report to the RNC: MNew >= MInAs + ReplacementWindow / 2
Ec/Io
AS has 3 cells
P CPICH 1
P CPICH 2
P CPICH 4 1C
weakest CPICH in AS
P CPICH 3
ReplacementTime
Defines the period of time the monitored cell must continuously stay within the reporting range before the UE can send a Measurement Report to the RNC in order to replace an active set cell with the monitored cell (event 1C).
time
ReplacementReportingInterval
If the RNC is not able to replace the active cell with the monitored cell, the UE continues reporting after the initial report by reverting to periodical measurement reporting. The parameter Replacement Reporting Interval determines the interval of periodical measurement reports when such reporting is triggered by the event 1C. no
Measurement Report
AS update?
RNC

13. NO ADJS
No Adjs
Zero attempts?
Comparing the ADJS plan provisioned into the network with the M1013 matrix, it is easy to find if one declared ADJS is not used (not present in the list)
Statistic data must be stabilized before decide to remove it and DT analysis can help n estimating the amount of residual noise if down tilt is not possible
Repeat Analysis
Yes
Statistic Stable?
Yes
DT analysis for the Adjs
Remove ADJS

14. Low used ADJS
Low used Adjs
Analyze DT result and NWP data
It is not difficult in live network to find some pair working with very low
For low used ADJS has to be intended and ADJS that has few number of attemps in one day (e.g <3)
with occasional failure.
The ADJS removal has to be considered as the last option, after the quality has been monitored by drive test result, considering the overall capability of the target to be recovered (e.g. inter-site distance, power budget) and other options are available for that area.
Statistic data must be stabilized before decide to remove it and DT analysis can help in estimating the amount of residual noise if down tilt is not possible
Yes
Monitored Qual from DT acceptable?
Alter. ADJS present?
ADJ Offset
Yes
Interference evaluation
Remove ADJS

15. Unbalanced ADJS
Unbalance ADJS
Analyze RSCP from DT & NWP coverage plot considering inter-site distance e traffic distribution
An high number of attempt could be an indication of a problem and even in case of the failure is not associated an evaluation is required.
The key point is the inviduation of the attempt distribution, that in case are not justified but partcualar populated area, coluld generate lot of signalling.
The attempts could be genarated by 1B event ever the same UE not counted in the M1013.
The possibility to recover the ADJS is the favourite option and the down tilt carefully analyzed considering the failure associated.
Attempt over the same UE?
No action required
Yes
Yes
Yes
Target act as polluter?
Down tilt possibile?
DERR cell
Down tilt
Analyze Ec/No from DT & evaluate unbalance
Ec/No offset

16. Interference / pollution
Unbalanced WCEL
Unbalanced WCEL
Analyze RSCP from DT & NWP coverage plot considering inter-site distance and traffic distribution
An high number of attempt could be an indication of a problem and even in case of the failure is not associated an evaluation is required.
The key point is the inviduation of the attempt distribution, that in case are not justified but partcular populated area, coluld generate lot of signalling.
The attempts could be genarated by 1B event ever the same UE not counted in the M1013.
The possibility to have an interference/pollution increase respect to the unbalanced ADJS.
The optimization should be performed at WCEL level
The KPI reported are the same of Failure WCEL
Attempt over the same UE?
No action required
Yes
Yes
WCEL interfered
polluted?
Interference / pollution
Analyze Ec/No from DT
Yes
KPI(1) ?
Tune 1A
Yes
KPI(2) ?
Tune 1C

17. Ping Pong
Down tilt
DERR cell
Yes
Down tilt possibile?
Ping-pong
No action required
Yes
In this particular case the high number of attempt is concentrated in a pair
From A >> B and from B >>A as in the picture
As in the previous case could be an indication of a problem and even in case of the failure is not associated an evaluation is required to avoid to use a lot signalling.
The optimization should be performed at ADJS level considering that the filtering option could get to smoother measured value
Analyze RSCP from DT & NWP coverage plot considering inter-site distance
Attempt from the same UE?
pollution
One of them act as polluter?
Analyze Ec/No from DT
Not stable, Fading?
Comparable value?
Yes
Yes
Filtering
Histeresys using
Ec/NoOffset on the pair

18. I am in the CELL_DCH sub-state
Ping Pong - Filtering
Node B
UTRAN
RNC UE
Measurement Control [ ]
I am in the CELL_DCH sub-state
Measurement Type: Intra-frequency measurements
Reporting events:
1A: Event 1A triggered when CPCIH Ec/Io of the measured cell enters UE
reporting range for a defined period of time
1B: Event 1B triggered when CPICH EC/I0 of the measured cell drops out
of the UE reporting range for a defined period of time
1C: Event 1C triggered when CPICH EC/IO of the measured cell enter in
AS by a defined margin for a defined period of time
System Information [ ]
EcNoFilterCoefficient
EcNoAveragingWindow
Applied for averaging of periodical meas. reports
Ec/NoFilterCoeff
controls the higher layer filtering of physical layer measurements before the event evaluation and measurement reporting is performed by the UE.

19. Pollution

20. Polluter Detection
The best way to individuate a Polluter is the Drive Test
A feedback can come from coverage plot, RNP feedback and Counters
A polluter can be of different type:
PSC Pollution
Too high reuse factor for the PSC. New PSC plan is required
DL Noise raise
ADJS signal strength out of usage window (will be never utilized by the UE)
A down tilt or power reduction is the solution evaluating all the side effects
Dominant site
A dominant site over-shooting the ADJ becoming congested

21. Isolated/unavailable WCEL
PSC Pollution
A confirm for the polluter of the first type can come from the counter
M1007C38-47 CELL SPECIFIC CPICH EC/NO - CLASS x
Pollution Criteria:
The M1007C gives an indication of Ec/No distribution value measured during event 1A . Having the distribution higly unbalanced (normally centered on class 2, 3, 4) we have an indication of a probable problem. For example unbalancing towards the scarce vaue of Ec/No but continuing to add cells to AS could give an indication of pollution
High number of class0-3?
Yes
High number of class>6?
Isolated/unavailable WCEL
Not Polluted WCEL
Yes
Polluted WCEL

22. DL Noise Raise
The NO ADJS and low used ADJS criteria before presented can give a confirm for a pollution of this type.
After the statistical data are stabilized, making across-check with the provisioned ADJS Plan the probable polluters are individuated.
This is obviously a cautelative estimation to be integrated and confirmed by drive test results

23. Dominant site
Filtering the M1013 pairs for the recurrent target cell with associated occasional failure we have an estimation of the probable polluters
For the polluters, originating failures a down tilt is required
Polluted Cell Criteria:
SHO over head can give a soft help in individuating cell where polluter/overshooting site can be present or where unbalanced cell criteria could apply

24. Accessibility

25. Accessibility If LOW accessibility RRC from:
Accessibility Statistical Counters
DRIVE TEST
Specific counter for Resource monitoring can be evaluated:
RRC_CONN_STP_FAIL_AC/RRC_CONN_STP_FAIL_all >> UL/DL Cell Load & code allocation
RRC_CONN_STP_FAIL_BTS/ RRC_CONN_STP_FAIL_all >> CE usage
RRC_CONN_STP_FAIL_TRANS/ RRC_CONN_STP_FAIL_all >> CAC rej or AAL2 setting up fail
RRC SETUP FAIL DUE TO IUB AAL2 TRANS / RRC_CONN_STP_FAIL_all >> AAL2 shortage
RRC CONN SETUP FAIL DUE TO RNTI ALLO FAIL / RRC_CONN_STP_FAIL_all >> RRMU overload
Could be useful for congestion detection to not neglect the analysis of failure in access phase with cause RADIO
RRC_CONN_ACC_FAIL_RADIO/RRC_SETUP_COMP (Sync) >> UL/DL Cell Load and coverage plot

26. RRC Accessibility RRC FAIL AC
If the condition triggered is RRC_CONN_STP_FAIL_AC the power analysis is required either Tx or Rx and code availability
If the thresholds are correctly settled but the cell seems to be congested according to the class3 and class4 permanence time a cross check on the effective traffic present is required.
Some interferer can be discovered by the drive test result.
Otherwise an expansion must be considered
RRC fail from DT & Statistic
Radio Congestion
Yes
Yes
Yes
RRC fail AC?
KPI(1)?
CE Congestion
Interference et al.
Yes
Yes
RRC fail BTS?
KPI(2)?
RRC Fail BTS
RL rejection from BTS sending a NBAP: RL Setup Failure.
Old counters M1005 are replaced by the one created for 3GGP Iub
The most important cause for RNO included in is the lack of CE
WSP expansion or new site is required
HW problem et al.
RRC fail Trans?
Iub not Congested
AAl2 Congestion
Yes
Yes
Iub Congestion
RRC fail AAL2?

27. RRC Accessibility – AC Congestion
Uplink Cell load
Downlink Cell load
KPI (1)
Code blocking
Average Code Tree Occupancy

28. RRC Accessibility – BTS Congestion
CE Usage
KPI (2)

29. RAB Accessibility If Low accessibility RAB from: DUETTO DRIVE TEST
Considering that after RANAP: Rab Assignment Request from Core a double check is
requested.
Due to DCH0/0 allocation more significant are CS for AC and BTS fail cause and PS for TRANS
after reconfiguration
PS services that can suffer more the following cases can be evaluated: CS
RAB SETUP FAILURES DUE TO AC PS
RAB SETUP FAILURES DUE TO BTS
RAB SETUP FAILURES DUE TO TRANSPORT (AAL2)
RAB SETUP FAILURES DUE TO IUB AAL2 TRANS

30. RAB Accessibility
When a RRC Fail TRANS is triggered a KPI for CAC rej & AAL2setup failure can be
useful to evaluate the failure rate

31. How to use Nokia core and secondary colors
Nokia secondary color palette (secondary blue, secondary neutrals, secondary brights) can only be used in charts and shapes, in addition to core colors.
Nokia blue
Nokia green
Nokia secondary blue
Nokia secondary colors for charts & shapes
R 000
G 051
B 204
R 068
G 165
B 028
R 175
G 212
B 240
R 235
G 233
B 216
R 191
G 215
B 218
R 230
G 192
B 031
R 175
G 148
B 023
R 206
G 150
B 032