neighbour optimization

7/21/2019 Neighbour Optimization

http://slidepdf.com/reader/full/neighbour-optimization 1/44

For internal use only

/1 © Nokia Siemens Networks

Neighbour Optimization Report

Globe Project

Prepared byYudha Oscarian

Ranjan Padhi

Wijaya Dody

Abhishek RathYosana Prayitno

Reviewed By Adji Caecilia





Project Information

Customer Information : GLOBE Telecom

OSS Target : Pioneer OSS (RC1)

Valero OSS (RC3)

Frequency Band : GSM 900GSM 1800

UMTS 2100

License and Build Details : Optimizer 2.0





RC1: Pioneer OSS





RC1: BSC Target > 29 BSCs





RC1: BSC CBD Area





RC1: RNC Target > 5 RNCs





RC1: Summary Adjacency Optimization

• Deletion adjacency is a deletion unwanted adjacency which is recommendedbased on KPI and distance.

• Creation adjacency is a creation which is recommended based on distance andmissing neighbour fixing.

• Parameter value on adjacency creation were discussed and agreed by theGLOBE Team

RC1 - Pioneer Creation Deletion

ADCE (2G - 2G) 3252 11

ADJG (3G - 2G) - 23

ADJW (2G - 3G) - 84

ADJS (3G - 3G) 135 307

ADJI (3G - 3G): Inter- Frequency 53 23





RC1: ADCE Deletion

• 11 Far Away ADCEs detectedwhich were deletedfrom the Scope

BSC afterverification from

Globe team.

File Name : ADCE_Deletion_Faraway_04022010.xls





RC1: ADCE Creation

• 3252 ADCEs werecreated based ondistance and samesite missing

neighbour fixingwith parametervalue which hadbeen discussedand verified with

Globe team.

File Name : ADCE_Creation_RC1_09022010.xls





Zoomed in RC1: ADCE Creation Snapshot





RC1: KPI - HO Success Rate improvement





RC1: KPI - SDCCH Drop improvement





RC1: ADJG & ADJW Deletion File Name : ADJG-W_Deletion_RC1_01032010.xls

• 23 ADJGs and 84 ADJWs beingdeleted based onKPI (HO Attempts,HO Success Rate)and distancewhich weredeleted from theScope BSC after

verification fromGlobe team.





RC1: ADJS Deletion

• 311 ADJSsdetected based onKPI and distancewhich 307 ADJSswere deleted fromthe Scope BSCafter verificationfrom Globe team.

File Name : ADJS_Deletion_RC1_21022010.xls





Zoomed in RC1: ADJS Deletion Snapshot





Further zoomed in RC1: ADJS Deletion Snapshot





RC1: ADJS Creation File Name : ADJS_Creation_RC1_24022010.xls

• 135 ADJSs werecreated based ondistance, one-wayneighbour fixingand same-sitemissing neighbour fixing withparameter valuewhich had been

discussed andverified with Globeteam.





Zoomed in RC1: ADJS Creation Snapshot

RC1 ADJI D l ti





RC1: ADJI - Deletion

• 23 ADJIsdetected basedon KPI anddistance whichwere deletedfrom the ScopeBSC afterverification fromGlobe team.

File Name : ADJI_Deletion_RC1_24022010.xls

RC1 ADJI C ti





RC1: ADJI – Creation File Name : ADJI_Creation_RC1_25022010.xls

• 53 ADJIs were createdbased on distance andsame-site missingneighbour fixing withparameter value whichhad been discussedand verified with Globeteam.

RC1 ADJI C ti S h t





Zoomed in RC1: ADJI – Creation Snapshot





RC3: Valero OSS







RC3 - Valero Creation Deletion

ADCE (2G - 2G) 1181 8

ADJG (3G - 2G) 1468 189

ADJW (2G - 3G) 1215 381

ADJS (3G - 3G) 61 66

ADJI (3G - 3G) Inter- Frequency 52 73

• Deletion adjacency is a deletion unwanted adjacency which is recommendedbased on KPI and distance.

• Creation adjacency is a creation which is recommended based on distance andmissing neighbour fixing.

• Parameter value on adjacency creation were discussed and agreed by theGLOBE Team

RC3 – ADCE Deletion





RC3 – ADCE Deletion

• ADCEs Deletion wasdone on the basis ofHO Attempts, HOSuccess Rate and13 995 l

RC3 – ADCE Creation File Name: ADCE Creation 11FEB2010.xls





RC3 ADCE Creation

• 1181 ADCEs werecreated based onsame-site missingneighbour fixingwith parametervalue which hadbeen discussedand verified withGlobe team.

_ _

Zoomed in RC3 – ADCE Creation Snapshot





Zoomed in RC3 ADCE Creation Snapshot

Zoomed in RC3 – ADCE Creation Snapshot





Zoomed in RC3 ADCE Creation Snapshot

RC3: KPI - HO Success Rate improvement





RC3: KPI HO Success Rate improvement

RC3: KPI - SDCCH Drop improvement





RC3: KPI SDCCH Drop improvement

RC3: ADJG & ADJW Deletion File Name : ADJG-ADJW_Deletion_RC3_28022010.xls





• 189 ADJGs and 381 ADJWs beingdeleted based onKPI (HO Attempts,HO Success Rate)

and distance whichwere deleted fromthe Scope BSCafter verificationfrom Globe team.

Zoomed in RC3: ADJG & ADJW Deletion Snapshot





p

RC3: ADJG & ADJW Creation File Name : ADJW_ADJG_Creation_RC3_8Mar10.xls





• 1468 ADJGs and1215 ADJWs werecreated based ondistance, one-wayneighbour fixing

and same-sitemissing neighbour fixing withparameter valuewhich had beendiscussed andverified with Globeteam.

Zoom-in RC3: ADJG & ADJW Creation Snapshot





RC3 – ADJS Deletion File Name : ADJS_Deletion_RC3_19022010_with _Opt i_Comments.xls





• 90 ADJSs detectedbased on KPI anddistance which 66 ADJSs weredeleted from the

Scope BSC afterverification fromGlobe team.

Zoomed in RC3 – ADJS Deletion Snapshot





RC3 – ADJS Creation File Name : ADJS_Creation_RC3_23022010.xls





• 61 ADJSs werecreated based ondistance, one-wayneighbour fixing andsame-site missing

neighbour fixing withparameter valuewhich had beendiscussed andverified with Globeteam.

Zoomed in RC3 – ADJS Creation Snapshot





RC3: ADJI - Deletion File Name : ADJI_Deletion_RC3_24022010.xls





• 73 ADJIsdetected basedon KPI anddistance whichwere deleted

from the ScopeBSC afterverification fromGlobe team.

RC3: ADJI – Creation File Name : ADJI_Creation_RC3_25022010.xls





• 52 ADJIs werecreated based ondistance andsame-site missingneighbour fixing

with parametervalue which hadbeen discussedand verified withGlobe team.

RC3: KPI - ISHO Success Rate





RNC 106 ISHO Success Rate %

94.500%

95.000%

95.500%

96.000%

96.500%

97.000%

97.500%

98.000%

98.500%

3 / 1 / 2 0 1 0

3 / 2 / 2 0 1 0

3 / 3 / 2 0 1 0

3 / 4 / 2 0 1 0

3 / 5 / 2 0 1 0

3 / 6 / 2 0 1 0

3 / 7 / 2 0 1 0

3 / 8 / 2 0 1 0

3 / 9 / 2 0 1 0

3 / 1 0 / 2 0 1 0

3 / 1 1 / 2 0 1 0

3 / 1 2 / 2 0 1 0

3 / 1 3 / 2 0 1 0

3 / 1 4 / 2 0 1 0

3 / 1 5 / 2 0 1 0

3 / 1 6 / 2 0 1 0

3 / 1 7 / 2 0 1 0

3 / 1 8 / 2 0 1 0

3 / 1 9 / 2 0 1 0

3 / 2 0 / 2 0 1 0

ImplementationDay

RNC 105 ISHO Succ ess Rate %

95.500%

96.000%

96.500%

97.000%

97.500%

98.000%

98.500%

3 / 1 / 2 0 1 0

3 / 2 / 2 0 1 0

3 / 3 / 2 0 1 0

3 / 4 / 2 0 1 0

3 / 5 / 2 0 1 0

3 / 6 / 2 0 1 0

3 / 7 / 2 0 1 0

3 / 8 / 2 0 1 0

3 / 9 / 2 0 1 0

3 / 1 0 / 2 0 1 0

3 / 1 1 / 2 0 1 0

3 / 1 2 / 2 0 1 0

3 / 1 3 / 2 0 1 0

3 / 1 4 / 2 0 1 0

3 / 1 5 / 2 0 1 0

3 / 1 6 / 2 0 1 0

3 / 1 7 / 2 0 1 0

3 / 1 8 / 2 0 1 0

3 / 1 9 / 2 0 1 0

3 / 2 0 / 2 0 1 0

ImplementationDay

RC3: KPI - ISHO Attempts





RNC 106 ISHO Attempts

0

50000

100000

150000

200000

250000

3 / 1 / 2 0 1 0

3 / 2 / 2 0 1 0

3 / 3 / 2 0 1 0

3 / 4 / 2 0 1 0

3 / 5 / 2 0 1 0

3 / 6 / 2 0 1 0

3 / 7 / 2 0 1 0

3 / 8 / 2 0 1 0

3 / 9 / 2 0 1 0

3 / 1 0 / 2 0 1 0

3 / 1 1 / 2 0 1 0

3 / 1 2 / 2 0 1 0

3 / 1 3 / 2 0 1 0

3 / 1 4 / 2 0 1 0

3 / 1 5 / 2 0 1 0

3 / 1 6 / 2 0 1 0

3 / 1 7 / 2 0 1 0

3 / 1 8 / 2 0 1 0

3 / 1 9 / 2 0 1 0

3 / 2 0 / 2 0 1 0

ImplementationDay

RNC 105 ISHO Attempts

0

20000

40000

60000

80000

100000

120000

140000

160000

180000

200000

3 / 1 / 2 0 1 0

3 / 2 / 2 0 1 0

3 / 3 / 2 0 1 0

3 / 4 / 2 0 1 0

3 / 5 / 2 0 1 0

3 / 6 / 2 0 1 0

3 / 7 / 2 0 1 0

3 / 8 / 2 0 1 0

3 / 9 / 2 0 1 0

3 / 1 0 / 2 0 1 0

3 / 1 1 / 2 0 1 0

3 / 1 2 / 2 0 1 0

3 / 1 3 / 2 0 1 0

3 / 1 4 / 2 0 1 0

3 / 1 5 / 2 0 1 0

3 / 1 6 / 2 0 1 0

3 / 1 7 / 2 0 1 0

3 / 1 8 / 2 0 1 0

3 / 1 9 / 2 0 1 0

3 / 2 0 / 2 0 1 0

ImplementationDay

Conclusion





• Connection to Pioneer OSS is extremely slow

• There is massive missing NB on 2G adjacency while on 3G adjacency justhaving some missing NB.

• Significant KPI improvement of HO Success Rate for Pioneer OSS andValero OSS after massive missing NB addition in both OSS (illustration on

slide: 11-12 & 30-31)

Thank You

neighbour optimization

Documents