ranop2 module3 neighbour&rf_optimization_ru10

1 © Nokia Siemens Networks Presentation / Author / Date

For internal use

3G RANOP2 RU10Module 3-Neighbour & RF Optimisation


For internal use

Module 3- Neighbour & RF Optimization

Objectives

After this module the participant shall be able to:

•Describe the main neighbour optimization methods and tools

•Describe KPI analysis for neighbour list optimization

•Learn how neighbour & RF optimization can be done with Optimizer2.0


For internal use

Contents

• Neighbour optimization Methods & Tools

• Adjacency Based Measurements

• NetAct Optimiser 2.0 overview

• Propagation Delay


For internal use

Neighbour optimization

• Handover measurement provides cell to cell HO statistic which can be used for neighbour performance optimisation

� 1013 Autodef SHO

� 1014 Autodef IFHO

� 1015 Autodef ISHO

• Autodef HO Measurement can be used and activated as any other basic RAN

performance measurements

• Autodef HO measurement are also used with help of the NetAct optimiser 2.0optional feature (automatic adjacency optimisation).

• NetAct Optimiser 2.0 use Autodef counters for deleting adjacencies and ICSU statistics for creating adjacencies.


For internal use

Neighbour list Combination procedure- SHO/ISHO to

undefined neighbour possible I• Active Set may contain cells, which are not necessary adjacencies with each other.

• The list of cells to be measured is send by the RNC in a MEASUREMENT CONTROL message and is changed at every Active Set Update. The RNC then combines the

Neighbour lists according to the following rules:

1. Active set cells are included

2. Neighbour cells which are common to three active set cells are included

3. Neighbours which are common to the controlling cell and a second active set cell are included.

(cell, other than the controlling cell, which has the highest CPICH Ec/Io)

4. Neighbour cells which are common to two active set cells are included

5. Neighbour cells which are defined for only one active set cell are included

6. Neighbours which are defined only for the second ranked cell are included

7. Neighbours which are defined only for the third ranked cell are included

• If the total number of cells to be measured exceeds the maximum value of 32 during any

step then handover control stops the Neighbour list generation


For internal use

Neighbour list Combination procedure II

• Because of the combination explained in the previous slide, it is possible to measure

handover activity between 2 cells which do not have an adjacency defined between them.

• In this example intra-frequency adjacencies exist between cells 2-6 and 6-7, but not

between 2-7. Activity is measured when the lists of cells 2 and 6 are combined and 7 can

be added, while 2 is still the best cell in the Active Set. The same effect applies for Inter-System list combining

Neighboured

Not neighboured

1

23 4

5

6

7

89

UE path

Neighboured

Not neighboured

1

23 4

5

6

7

89

UE path


For internal use

Active Set Add FAIL_UE/NO REPPLY- example (wcel

level)

0

5000

10000

15000

20000

25000

1 18 35 52 69 86 103 120 137 154 171 188 205 222 239 256 273 290 307 324 341 358 375 392 409

0

5

10

15

20

25

30

AS_UPDATE_RL_ADD_ATT

AS_UPDATE_RL_DEL_ATT

AS_UPDATE_RL_ADD_FAIL_UE

AS_UPDATE_RL_ADD_NOREPLY


For internal use

Active Set Add/Del success- example, RNC

0.9989

0.999

0.9991

0.9992

0.9993

0.9994

0.9995

0.9996

0.9997

0.9998

0.9999

5.3.

2008

6.3.

2008

7.3.

2008

8.3.

2008

9.3.

2008

10.3

.200

811

.3.2

008

12.3

.200

813

.3.2

008

14.3

.200

815

.3.2

008

16.3

.200

817

.3.2

008

18.3

.200

819

.3.2

008

20.3

.200

821

.3.2

008

22.3

.200

823

.3.2

008

24.3

.200

825

.3.2

008

0.00%

0.01%

0.01%

0.02%

0.02%

0.03%

0.03%

0.04%

0.04%

AS_UPDATE_RL_ADD_SUCC %

AS_UPDATE_RL_DEL_SUCC %

AS_UPDATE_RL_ADD_FAIL_UE %

AS_UPDATE_RL_ADD_NOREPLY %

Some failures due to no reply

to ASU


For internal use

Content






For internal use

Adjacency Based Measurements

• Each cell has its own neighbouring cell list initially defined by radio Network Planning. This

is a list of those neighbouring cells where the handover can be made.

• The results of neighbour cell measurements can be used to optimise those lists. The

benefits of optimised lists are better call quality and shorter handover delays.

• To find strong candidates that are missing from actual definition

• To locate and delete unused adjacencies

• Identify and optimise badly performing adjacencies

RNC

Serving BTS

UEs


For internal use

Adjacency Based Measurements Counters

M1013 Autodef SHO

• M1013C0 Number of Intra Frequency SHO attempts

• Counter is Updated when SRNC starts a Branch Addition or Branch Replacement procedure.

• M1013C1 Number of completed Intra Frequency SHO

• Counter is updated when SRNC successfully ends the Branch Addition or Branch Replacement procedure.

M1014 Autodef IFHO

• M1014C0 Number of Inter Frequency HHO attempts

• Counter is updated when SRNC starts inter-frequency HHO

• M1014C1 Number of completed Inter Frequency HHO

• Counter is updated when SRNC successfully ends inter-frequency HHO

M1015 Autodef ISHO

• M1015C0 Number of Inter System HHO attempts

• Counter is updated when SRNC starts inter-system HHO

• M1015C1 Number of completed Inter System HHO

• Counter is update when SRNC receives RANAP:IU RELEASE COMMAND from core network after successful Inter System HHO


For internal use

For each measurements (SHO, IFHO and ISHO) Statistic show:

• # of HO attempts

• # of HO completed (successful)

to source and target cell objects

Measurement is carried out in SRNC

HO completion is considered successful if the SRNC during the handover decision does not detect any errors (errors in the source RNC side or failure messages from RRC/Iu/Iur/Iub interfaces)

Object identifiers for M1013 and M1014

Source-RNC/Source-CID

Target-RNC/Target-CID

MCC/MNC

Object identifiers for M1015 (ISHO)

Source-RNC/Source-CID

GSM-LAC/GSM-CID

MCC/MNC

Adjacency Based Measurements Counters


For internal use

SHO Share

• HO Share provides distribution of HO attempts from the source cell

• Useful detect neighbour relations which has exceptional amount of attempts

• It is possible to get the total number of outgoing HO attempts from the Autodef HO

measurements by taking a sum over all the adjacencies reported for a source cell

• SHO HO Share (M1013 AutoDef SHO)

• IFHO HO Share (M1014 AutoDef IFHO)

• ISHO HO Share (M1015 AutoDef ISHO)

)_____(______

)_____(*100903___

ATTSHOFREQINTRAADJSHOcellthefromadjaalloverSum

ATTSHOFREQINTRAADJSHOsumaRNCShareSHO =

)_____(______

)_____(*100904___

ATTHHOFREQINTERADJHHOcellthefromadjaalloverSum

ATTHHOFREQINTERADJHHOsumaRNCShareIFHO =

)_____(______

)_____(*100905___

ATTHHOSYSINTERADJHOcellthefromadjaalloverSum

ATTHHOSYSINTERADJHOsumaRNCShareISHO =


For internal use

HO Success per Adjacency

• The HO success rate per adjacency can be calculated by using formulas below

• Can be used to detect badly performing neighbours

• SHO Success per Adjacency (M1013 AutoDef SHO)

• IFHO Success per Adjacency (M1014 AutoDef IFHO)

• ISHO Success per Adjacency (M1015 AutoDef ISHO)

)_____(

)_____(*100900_____

ATTSHOFREQINTRAADJSHOsum

COMPLSHOFREQINTRAADJSHOsumaRNCADJSpersuccessSHO =

)_____(

)_____(*100901_____

ATTHHOFREQINTERADJHHOsum

COMPHHOFREQINTERADJHHOsumaRNCADJIpersuccessIFHO =

)_____(

)_____(*100902_____

ATTHHOSYSINTERADJHOsum

COMPLHHOSYSINTERADJHOsumaRNCADJGpersuccessISHO =


For internal use

Content




• Creating ADJx based on PM data



For internal use

Automated Adjacency Optimisation for 3G in Optimizer

2.0

• Accurate and efficient process for optimising operational WCDMA cell adjacencies

• Measurement based optimisation

• Current adjacency status analysis

• Deletion of unused adjacencies

based on KPIs

• HO attempts, HO success

• Adjacency candidate identification,

activation and measurement

• Interfering intra-frequency cells

• Cell pair Ec/No difference from WCDMA

• Neighbour cell signal strength from GSM

• Final adjacency list optimisation

• Scrambling code re-allocation

• Full visibility and control to the user


For internal use

• A fast way to identify missing intra-frequency adjacencies

• Interference measurements colleted from RNC

• New adjacencies can be created based on that statistics

• Rotation method used to achieve the optimal lists

for other adjacency types

• Optimizer creates adjacency candidates

• Candidates are downloaded to network and measured

• Statistics collected directly from RNC

• Cell pair Ec/No difference

• Successful BSIC verifications & BSIC verification time

• Final adjacency list is generated

Creating new adjacencies


For internal use

Content




• Creating ADJx based on PM data (AutoDef)

• Creating ADJx based on DSR measurements (ICSU)

• WCDMA Interference analysis



For internal use

Creating ADJx based on PM data (AutoDef)

• Optimizer will show adjacency based SHO amounts for undefined neighbours

• Purpose is to search all ADJS and ADJG new neighbours which are within certain max distance

• Example 1-5 km in urban area and 4-10 km outside urban area.

• After that only those will be selected which have enough SHO/ISHO attempts.

• The selected neighbours could be provisioned straight away to the network


For internal use

How to create Missing ADJx based on PM data-1

1. Select area from the map

And start the ADJ

Optimization tool

2. Select ADJG, ADJS and ADJW types


For internal use


3. Select right actions from rules,

common Deletion and

Creation tabs


For internal use


4. Purpose is to search all ADJS and ADJG new

neighbours which are within certain max distance like

1-5 km in urban area and 4-10 km outside urban area. After that only those will be selected which have

enough SHO/ISHO attempts.

5. Start from here

6. Save plan from here with

any name


For internal use


7. List all new neighbors


For internal use

How to create Missing ADJx based on PM data-58. Select the whole week

or one day for PM data analysis

10. Update the list of

Neighbours from here

9. Select the right profile to

browser (ADJG, ADJS)

11. Sort according to

the PM attempts


For internal use


12. See the ADJ on top of the map

13. Provision the selected neighbors to the network

Note ! These neighbors are defined only for one way direction.

See next slides how to make those bidirectionally (Refresh actual operation with RAC)


For internal use


14. Open the CM data exchange

under the main window

15. Select refresh actual and wait

Until the data is updated

16. Open the adjacency optimization without selecting any

tabs from Deletion or Creation, just to find just created one way ADJx


For internal use


17. Save the plan and list the planned elements

18. You can see now the ADJx neigbours which

can now provisioned to the network


For internal use

Content






• WCDMA Interference Analysis



For internal use

Creating ADJx based on DSR measurements (ICSU)

• Detected set measurements coming from undefined neighbours (based on ICSU logs)

• Aim is to find source of interference

• cell having many DSR results but no SHO attempts (with neighhbour list combination

list)

• Solutions

• Add found cell to the neighbour

• Downtilt to decrease the interference

• DSR measurements are suitable also for ADJG neighbours


For internal use

DSR activation

• When DSR is not activated, UE monitors only cells in its NCL (either read from BCCH or sent from RNC in SHO case).

• When DSR IS activated, UE scans ALL scrambling codes in same frequency band and if cells are found that fulfil certain criteria, UE reports this/these cell(s) as detected cells.

• criteria for detection is that UE has to be able to detect if Ec/N0 is greater than

-18 dB

• for a DSR to be triggered, detected cell/s must fulfil "normal" HO criteria, i.e. for

example, are within the reported range relative to P-CPICH of strongest AS cell.

• Details of activation :MML command that is sent to RNC that sets some flag active and RNC orders UE to measure and report. It can be done by HIT macro, but Optimizer is not (supposed to) using them but same commands that are in HIT macros are sent directly to RNC.


For internal use

1. Select scope, area from map

Or individual site or cell

2. Select tools/ Adjacency Optimization

3. Select ADJS,(ADJS=3G/3G,

ADJG=3G->2G,ADJW=2G->3G

ADJI= 3G-3G,ADJE=2G-2G)


For internal use

6. ChangeDSR parameters

from here

4. Rules: Fill and keep adjacencied in

same Site and Fill bidirectionality

5. Common: Use Bidirectional Optimisation

and Enable Changes between

Scope and Buffer area


For internal use

7. If you want look at cells,which are seen by DSR, but are not in combined list

(no SHO attempts to that one), select SHO attempts big enough to find

The cells which are purely interference sources


For internal use

Tästä halutut solut kartalle

8. Start optimization and you see the found created adjacencies

in browser, if you want to see the cells on map, the plan should be stored


For internal use

9. Here you can see DSR reports

10.If you want implement this neighbor, just select both directions from Adjacencies tab:

list to browser and further by selecting both directions and with right mouse button:

Provision instantly


For internal use

Select both directions and provision instantly


For internal use

Optimizer does not create neighbours if one rule below is true.However if all missing neighbours want’s to be seen, these rules can be omitted (and see all interfering cells based

on DSR). If you want to add neighbors, it is recommended to check SC problems with by Scrambling code allocation tool. Don’t use this in normal operation.


For internal use

11. It is possible to find ADJG/ADJW based on Measurement data, if bidirectional

Neighbours are wanted both ADJG and ADJW should be selected


For internal use

Content









For internal use

WCDMA Interference Analysis

• it is possible to see WCDMA internal interference situation of certain cell which is caused by other WCDMA cells (in terms of distance,RSCP and EcNo level). Also non-neighbours can be measured with DSR.

• Both Incoming and Ongoing interference levels can be studied with certain cell pairs.

• Interference information is based on UE measurements where the signal strength and quality of every Primary Scrambling code is reported to RNC.

• Before interference analysis the following actions should be done

1. Start WCDMA interference measurements

2. Activate measurements from Interference matrix (from selective RNCs or all measurements)

3. Start Interference analyzer for WCDMA –tool (from Scope, RNC or site)

4. Analyze the selection which was done in step 3


For internal use

WCDMA Interference Analysis

• The analysis shows for example the number of measured adjacencies with number of reports (SHO + DSR measurements) and if it is neighbour or not.

• If there is lot of reports from non-neighbour cell it would make sense to add it to the neighbour, at least if the distance is reasonable and if the RSCP levels are high. This will mean that the cell could be interferer, especially if there is not much SHOs (low SHO share %) to that cell (even with SHO combination).

DSR result

from no

neighbourRSCP,EcNo

criteria


For internal use

Content









For internal use

Propagation delay counters

• PRACH propagation delay statistics is presented using a distribution consisting of 21

counters M1006C128-M1006C148. One of the counters is updated by value 1 when the

UE sends RRC Connection Request or Cell Update.

• Each counter covers one or more PROP_DELAY values and the mapping of measured

values to counters can be controlled by WCEL parameter PRACHDelayRange that defines

five different mapping tables for various cell sizes

Range 60 km (this is fixed in RAS06)

bin 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

from(m) 0 234 468 936 1170 1638 2106 3042 3978 4914 6084 7020 7956 10062 14976 19890 25038 29952 34866 40014 50076

PROP_DELAY (from) 0 1 2 4 5 7 9 13 17 21 26 30 34 43 64 85 107 128 149 171 214

to(m) 234 468 936 1170 1638 2106 3042 3978 4914 6084 7020 7956 10062 14976 19890 25038 29952 34866 40014 50076 infinite

PROP_DELAY (to) 0 1 3 4 6 8 12 16 20 25 29 33 42 63 84 106 127 148 170 213

bin size(m) 234 234 468 234 468 468 936 936 936 1170 936 936 2106 4914 4914 5148 4914 4914 5148 10062


For internal use

PRACH example, RNC, 2 weeks data

0

100000

200000

300000

400000

500000

600000

PR

AC

H_D

ELA

Y_C

LAS

S_0

PR

AC

H_D

ELA

Y_C

LAS

S_1

PR

AC

H_D

ELA

Y_C

LAS

S_2

PR

AC

H_D

ELA

Y_C

LAS

S_3

PR

AC

H_D

ELA

Y_C

LAS

S_4

PR

AC

H_D

ELA

Y_C

LAS

S_5

PR

AC

H_D

ELA

Y_C

LAS

S_6

PR

AC

H_D

ELA

Y_C

LAS

S_7

PR

AC

H_D

ELA

Y_C

LAS

S_8

PR

AC

H_D

ELA

Y_C

LAS

S_9

PR

AC

H_D

ELA

Y_C

LAS

S_1

0

PR

AC

H_D

ELA

Y_C

LAS

S_1

1

PR

AC

H_D

ELA

Y_C

LAS

S_1

2

PR

AC

H_D

ELA

Y_C

LAS

S_1

3

PR

AC

H_D

ELA

Y_C

LAS

S_1

4

PR

AC

H_D

ELA

Y_C

LAS

S_1

5

PR

AC

H_D

ELA

Y_C

LAS

S_1

6

PR

AC

H_D

ELA

Y_C

LAS

S_1

7

PR

AC

H_D

ELA

Y_C

LAS

S_1

8

PR

AC

H_D

ELA

Y_C

LAS

S_1

9

PR

AC

H_D

ELA

Y_C

LAS

S_2

0

0.00%

20.00%

40.00%

60.00%

80.00%

100.00%

120.00%

average

CDF

Main Distance 468-936 m


For internal use

PRACH example, WCEL, one day

0

50

100

150

200

250

300

350

400

450

4605

246

125

4612

845

79312

101

4580

946

03845

799

4606

611

995

4609

346

11648

388

4580

312

200

1018

113

03846

516

4608

346

09145

797

45987

4684

647

415

45274

4609

445

076

46924

PRACH_DELAY_CLASS_12









Class 14: 14.5 km-20km

Sorted by Class12


For internal use

Extended cell

Counter id Counter name Distance [meters]

M1006C128 PRACH_DELAY_CLASS_0 0...234




















M1006C148 PRACH_DELAY_CLASS_20 greater than 50076

• Feature "RAN1127: Extended Cell (180 km)" extends the theoretical maximumcell range from 20 km to 180 km

• Counters in RRC measurements (M1006) can be used to evaluate how far UEsare from the cell

ranop2 module3 neighbour&rf_optimization_ru10

Technology