WCDMA Adjacency Optimisation OPT2.3

1 © Nokia Siemens Networks Presentation / PLe /20.3.2010For public use – IPR applies

WCDMA Optimisation with Optimizer 2.3 WCDMA Adjacency Optimisation

2 © Nokia Siemens Networks Presentation / PLe / 20.3.2010For public use – IPR applies

Nokia Siemens Networks AcademyLegal notice

Intellectual Property RightsAll copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks.


Module Objectives

At the end of this module the trainee should be able to:

• Delete all types of WCDMA adjacencies

• Create adjacencies


WCDMA Adjacency Optimisation

• Deleting adjacencies

• Creating ADJS based on DSR

• Creating ADJS, ADJG and ADJI based on rotations

– creating the plans for candidate rotations

– creating the final plan for adjacency creation


Adjacency Optimisation Prerequisites

• Invalid adjacencies fixed

• Antennas defined for every cell

• Optional: Mandatory and forbidden constraints have been created

• KPIs available


Starting Adjacency Optimization Tool 1

• Check the KPI date and summarisation level

• Select target objects from the Navigator, Map, Browser or a scope


Starting Adjacency Optimisation Tool 2

• ADJW should be selected for bidirectional optimization with ADJGs


Summary Table

• Check the summary for the scope

• WCDMA Cells and All Adjacencies can be checked also


Rules

• Rules can be used to

– Make existing adjacencies consistent with constraints

– Create all missing intra-site adjacencies

– Make all unidirectional adjacencies bidirectional (requires “Use bidirectional optimization” activated in “Common” tab)


Common Options

• Bidirectional deletion of an adjacency requires ONE bad value in both directions

• Changes between Scope and buffer must be enabled if ADJWs need to be deleted and BSCs are not in scope


Deletion Options

• Deleting outgoing adjacencies to foreign target cells can be allowed

• It is recommended not to delete adjacencies to the same site cells

• Adjacencies without measurements will have 0 values for KPIs and are deleted if selected

• It is recommended to delete and create separately -> Switch off the tick box in creation

• Set/check common options for all adjacency types and individual options per type


ADJS Deletion Parameters

• KPI need to be selected before the threshold can be modified

• With multiple selections an adjacency is deleted if value is bad


ADJG Deletion Parameters

• Bidirectional deletion requires at least one bad value in both directions


ADJW Deletion Parameters

• To delete ADJWs together with ADJGs that have bad KPI values

– Define zero (0) value for Theta Angle

– Use bidirectional optimization (in Common tab)

– Changes enabled between scope and buffer (in Common tab)

• Note: Uni-directional ADJWs are also deleted in this case


ADJI Deletion Parameters


Adjacency Deletion

• Start optimization


Info on Deleted

• Info column shows the deletion reason

• KPI values available if specific Adjacency Types are selected


Saving the Results

• The results must be saved to the plan

• Save is possible only

– to the plan that was open whenAdjacency Optimization started

– to a new plan that is createdafter pressing Save

• After the save the results can belisted to Browser or shownon the Map


Exercise

• Check and set Common parameters

• Set Deletion parameters and start the optimisation

– Change parameters if needed and run optimisation again

• Save the results into your plan









Additional Prerequisites for Creation

• Templates and template assignment rules exist


Creating ADJS based on DSR (1/4)

• The licenses for the measurements needs to be in place first

( RAN189, RAN1189, RAN1191 and RAN1245)

• FMCS Object needs to be modified (DSRepBasedSHO should be set as 1 or 2)

• Autodef SHO and Autodef SHO DSR needs to be started by using the Administration of Measurements tool

• All ADJDs needs to be deleted manually prior the creation of ADJSs















Creating ADJS, ADJI and ADJG using rotation (1/6)

• Only existing ADJS, ADJG, and ADJI adjacencies can be measured

• Candidate adjacencies must be created to the network

• Maximum list length limitations must be obeyed– Only part of the possible candidates can be created at once

• To measure all possibilities the candidates have to be rotated

• In each rotation new candidates are created and old ones deleted

• Example:– Three days of measurements

– 3 rotation plans, each one provisioned in the night

– The 4th plan deletes the candidates of the last rotation


• Optimizer will not create candidates for a cell if

– The adjacency lists are already full

– The maximum number of WCDMA adjacencies is reached

– Allowing collisions is NOT enabled and▪ There are existing Scrambling Code collisions

▪ There are existing BCCH or BCCH-BSIC collisions

▪ New candidates would cause collisions

• Deletion plan could be implemented before starting the rotations

• There cannot be a deleted adjacency in plan without actual adjacency object in CM database

– Because of this earlier plans must always be provisioned before the next rotation plan is exported from Optimizer DB to CM DB

• If the traffic in the NW is low the KPI coverage may not be very high after just one day of rotations





• Do NOT select Use Bidirectional Optimisation

• Select Enable Changes between Scope and Buffer

• Check the maximum List Lengths

• Verify that nothing is selected in Deletion

• Go to Creation tab




• Recommended: Do NOT enable creating collisions

• Enable Include deleted adjacencies into rotation list

• Select #of measurement days+1 for Maximum number of plans in rotation process



• Maximum pool list length is the maximum amount of adjacencies which are rotated

• Pool Creation Threshold value is the Priority value (Distance, Theta)

• Rotation Slot Length is the maximum number of candidates per cell for each rotation plan


Save the Create Rotation Plans

• When the optimisation results are saved the rotation plans are created automatically


Example Creation Workflow

1. Optional: Check the template assignment rules and the availability of templates

2. Optional: Run SCA tool and fix existing collisions and/or increase reuse distance

3. Start Adjacency Optimisation

4. Create and save a candidate adjacency pool and 4+1 rotation plans

5. Close Adjacency Optimization

6. Rotation cycle (3 times)A. Export the (first / next / last) rotation plan to CM database

B. Provision the rotation plan the night before the measurements

C. Wait until the measurements stop for the day

D. Go to A until 3rd round.

7. Export and provision the last plan that deletes the candidates of the last rotation from the network

8. Start Adjacency Optimisation

9. Create the final plan for ADJS/ ADJG/ADJI adjacency creation

10. Export the final plan to CM DB and provision it to the network


Cell Specific Results

• Results are shown for the first rotation plan

• ADJSs List Length = Actual ADJSs + Created ADJSs









Starting the Tool

• Select the weekly level KPI and a date from the week when you collected the measurements

• Close all plans and start Adjacency Optimisation


ADJS Parameters for the Final Plan

• Distance may be limited to avoid creating adjacencies to distant cells

• ADJS parameters

• Any combination of KPIs may be selected

• With multiple KPI selections ALL values must be good to create a new adjacency


ADJG Parameters for the Final Plan

• Select Use Bidirectional Optimisation (in the Common tab) to get ADJWs

• Any combination of KPIs may be selected

• With multiple KPI selections ALL values must be good to create a new adjacency


ADJI Parameters for the Final Plan


Results

• View the results

• Modify parameters and run again until the result is good


Save and Check

• Save to a new plan

• View the results in Browser and on Map


Visualize the Results


Document change history

Date Version Name Change comment

20.3.2010 1.0 PLe First version for Optimizer 2.3

7.7.2010 2.0 PLe Updated after the review

Documents

WCDMA Adjacency Optimisation OPT2.3