Soc Classification level 1 © Nokia Siemens Networks Presentation / Author / Date

Guideline

Neighbor Optimization and Pilot Pollution CleaningVersion 1.1

Soc Classification level 2 © Nokia Siemens Networks

• To have the optimum number of ADJS/ ADJI/ ADJG of 3G network both in F1 and F2.

• To optimize the 3G coverage in both layers. This can help to– Clean up Pilot Pollution,

– Reduce Overshooting

– Increase Cell Capacity

– Reduce the possibility of SC conflict.

Objective

Soc Classification level 3 © Nokia Siemens Networks

Scope

• Optimisation will be done for 2nd carrier cluster only. This may have to include sites outside the cluster that affect the performance of sites in the cluster.

Soc Classification level 4 © Nokia Siemens Networks Presentation / Author / Date

Network Design Scenario Connected Mode Strategy (Macro)

• Inter frequency handover adjacency is defined oneway F2 -> F1 to ensure mobility (except for colocated site, IFHO F1 -> F2 must be defined only for HSDPA to make sure HSPA Capability Handover)

• ADJG from F2 on 3G-2G border to ensure mobility. One-Way From F2 2G Only

F2: HSDPA+R99

F1: R99 HS+R99

2G

F2 Border

Soc Classification level 5 © Nokia Siemens Networks

Network Design Scenario Connected Mode Strategy (Site-Level) Zoom In

F2: HSDPA+R99

F1: R99

S1 S2 S3

Below ADJI Strategic is ideally used for Capability Based Handover. Figure shows How to define ADJI in one site.

Soc Classification level 6 © Nokia Siemens Networks

Methodology

• Neighbour Optimisation– Deletion

– Addition

• Coverage Optimisaton (Tilting)

Data and Tools

• OSS Data– Autodef (RSRAN044/ RSRAN045/ RSRAN046)

– PRACH Delay Class 0-20 (M1006C128 – C148)

– SHO Overhead (RSRAN028) (optional)

• PE Dump ( To get actual ADJx)

• Site Location Info ( To get Latitude/ Longitude)

• MapInfo ( To have visualize for neighbor planning)

• Planning Tool to calculate Antenna Tilting

Soc Classification level 7 © Nokia Siemens Networks

Propagation Distance Mapping Table

Our Parameter Setting for Propagation Cell Range is:

PRACHDelayRange = 3 (20 km)

Soc Classification level 8 © Nokia Siemens Networks

Propagation Distance Distribution

205 Cells in UPD3 is having propagation distance farer than 7 km. Need to carefully visualize on Mapinfo for downtilt decisions.

Value can be changed

depend on cluster

environment

Soc Classification level 9 © Nokia Siemens Networks

Propagation Distance list

Microsoft Excel Worksheet

This is an example PRACH Delay Class from OSS.

(7 days data)

This could be used as an indicator for cells with having improper coverage footprint (Overshoot).

We may plot the MAX PRACH Delay Class on Mapinfo for better visualization of coverage footprint of cells in our cluster. (See Next Slide)

Soc Classification level 10 © Nokia Siemens Networks

Propagation Delay Plot on MapInfo

Overshooting detected by Autodef+ PRACH Delay

Missing ADJS detected by Autodef

From Propagation Delay on Mapinfo, we can get an insight of How coverage propagation look like.

Soc Classification level 11 © Nokia Siemens Networks

Data from Autodef

Deletion ADJ

Yes

NoHO Attempts < 20/10/10

or HO Share <0.01%

Adj Distance > 5 km.

Yes

Double Compare to Propagation List

Delete Adj after Downtilting done

Yes

In line with the list

Keep the Adj(Use for PreventiveOr Low att due to Capacity issue)

No

Visualise on Mapinfo required

No

Downtilt required?

Yes

No

Neighbour Deletion Diagram

Use Autodef Data for last 7 days, Aggregate “Whole Period”

Distance can be changed according

to environment

Value can be changed depend on

traffic density in each cluster.

Adjs/Adji/Adjg respectively

Soc Classification level 12 © Nokia Siemens Networks

Neighbour Addition Diagram

Use Autodef Data for last 7 days, Aggregate “Whole Period”

Data from Autodef

Addition ADJ

Yes

HO Attempts > 50/15/15

Adj Distance < 2 km.

Yes

Downtilt Required?

Add AdjIf Nbr of all adjx < 36

No

Yes

Yes

No

Double Compare to Propagation List

Add Adj until Downtilting done

In line with the list

Visualise on Mapinfo required

No

Value can be changed depend on

traffic density in each cluster.

Adjs/Adji/Adjg respectively

Soc Classification level 13 © Nokia Siemens Networks

Optimisation Sequence

1. Start with ADJx Deletion. F1 and F2 (Autodef 7-days Data)2. Delete ADJI F1 F2 for Non-Collocated Site, if any3. Create ADJI F1<--> F2 for Collocated Site (like Page 5)

4. ADJS Addition in each Layer.(Autodef 7-days Data) F1 <-> F1 F2 <-> F2 ADJS addition MUST be done before ADJI and ADJG addition. Good ADJS planning can

significantly reduce interference, as a result number of required ADJG and AGJI will also decrease.

5. ADJI Addition. (Autodef 3-5 days Data) F1 <-> F2 F2 <-> F1 Again, well planned for ADJI will reduce Number of ADJG neighbors

6. ADJG Addition (Autodef 3-5 days Data)F2 2GF1 2G

At the end, we also expect to see number of ADJG from:

F2 GSM < F1 GSM

**F2 GSM (for F2 Border)

1/2/3 can be executed at the same night.

Soc Classification level 14 © Nokia Siemens Networks

SIB11 Planning

• IF ADJS+ADJG+ADJI <= 47, Set ADJx = SIB11(1) for all ADJx

• IF ADJS+ADJG+ADJI > 47,– For F1

Set ADJx = SIB11(1) for (all ADJS + main ADJI + main ADJG) <= 47

Set ADJx = SIBbis(2) for the “Remaining” ADJI and ADJG.– For F2

Set ADJx = SIB11(1) for (main ADJS + all ADJI + main ADJG) <= 47

Set ADJx = SIBbis(2) for the “Remaining” ADJG and ADJS.

• IF Overshooting case,

Set ADJx = Not Broadcast (0).

[This is not to allow UE camping on cells that very far away and later the ADJx will be deleted anyway, when downtilt done]

Soc Classification level 15 © Nokia Siemens Networks

End Results

• In general case, Final combined Neighbour (Adjs+Adjg+Adji) <= 36 Neighbours

• Try NOT to use SIB11bis, or use it as less as possible.

• No Cell blocking Alarm due to Too many neighbors (Alarm ID_7771)

• Provide Antenna Downtilting List to Customer.

Soc Classification level 16 © Nokia Siemens Networks Presentation / Author / Date

Thank You