Day2_06. Planning Support for 3G Roll-out_US

1 NOKIA Planning Support for 3G Roll-out.PPT/ 06.09.2006 / NN Copyright Nokia Corporation. All rights reserved

Planning Support for 3G Roll-out

MODULE 6

Copyright Nokia Corporation. This material, including documentation and any related computer programs, is protected by copyright controlled by Nokia Corporation. All rights are reserved. Copying, including reproducing, storing, adapting or translating, any or all of this material requires the prior written consent of Nokia Corporation. This material also contains confidential information which may not be disclosed to others without the prior written consent of Nokia Corporation.

Copyright Nokia Corporation. All rights reserved


Module Objectives

At the end of this module the participant will be able to: List the tools belonging to the NetAct Framework, which are relevant for site

integration

Describe the site integration process using the Nokia NetAct Framework

Explain how the work is split between radio and transmission planners

Describe the structure of the Nokia RAN parameter database

Copyright Nokia Corporation. All rights reserved


RNC

circuit switched (cs) domain

packetswitched (ps) domain

3GMSC/VLR

3GSGSN

RNC

Node B

Node B

Iub

Uu

Iu-C

S

Iu-PS

RNCNode B

Iur

AXC

AXC

AXC

COCO

COCO

Note:COCO is the logical objectCOCO

RAN Parameter Object Categorization1. RNW (RNC)

2. COCO

3. BTS SCF

4. AXC SCF


LACE (Lightly Automated Commissioning environment)

Makes UMTS RolloutMakes UMTS Rollout

FasterFaster DeploymentDeployment

Better Better PerformancePerformance


NetAct Planner is a part of the NetAct Framework. Export and Import functionality link NetAct Planner to the rest of the NetAct family products.

WCDMA Planner keeps track of changes since the latest synchronisation. This information is used to determine what needs to be exported. Synchronization clears exported information from WCDMA Planner.

NetAct Plan Editor supports 3G development and optimisation. It completes the functionality of NetAct Planner and NetAct RAC.

Nokia NetAct FrameworkIntegrated Tool Chain


Nokia NetAct FrameworkIntegrated Tool Chain

Reporter

Network

Administrator

3rd party tools

Rating & Charging

Unified Mediationand Adaptation

Service LevelManager

Monitor

ConfiguratorConfigurator

Planner

Workflow Manager


Nokia WCDMANokia WCDMAGSMGSM

Nokia NetAct EDGE WCDMA Common Management

1. Pre-planning based on GSM site and antenna info

1. Pre-planning based on GSM site and antenna info

2. Initial neighbor lists based on GSM neighbors

2. Initial neighbor lists based on GSM neighbors

3. Automatic update of GSM network changes to WCDMA

3. Automatic update of GSM network changes to WCDMA

4. Automatic GSM-WCDMA neighbor list optimization based on real traffic

4. Automatic GSM-WCDMA neighbor list optimization based on real traffic

3G pre-optimization

Faster 3G deployment

Less manual work

Less drop calls


NetAct PlannerProgram Modules

Integrated

Data & Environment

Microwave Link Planning

Link

Site Acquisition & Project Tracking

Rollout

Field MeasurementAnalysis

Quality

Multi Radio Planner2G & 3G Radio Network

Planning

Optimal PlannerAutomatic Network

Optimization

Transmission Network Planning

Transmission


Site Integration with Nokia NetAct

NetAct Planner

WCDMA

Planner

Transmission

Planner Plan Editor

NetAct Radio Access Configurator

PlanManagement

SiteConfiguration

Tool

RNC

AXC WBTS

Radio NetworkPlanner

Transport NetworkPlanner

LMT LMT

CommissioningEngineer

SCF for WBTSSCF for AXC

RNW Plan SCFs for AXC & WBTS

SCF for AXC SCF for WBTS

WBTS PhysicalTemplates

RNW LogicalTemplates

AXC PhysicalTemplates

Expert Content

Transport Radio Network

Required

RNW Plan

RNW Plan

Product (WBTS, AXC) Expertise Radio Network Planning Expertise

NetAct Plan EditorAXC SCF also contains

ATM Transmission Plan


Work Split Between Radio & Trs Planner

3G Radio Network Planning Engineer : NetAct Planner WCDMA Planner: define sites, cells, IDs and some parameters NetAct Plan Editor: complete RNW plan, parameters and needed WBTS HW configurations

with physical & Logical templates Data sent in CSV format to RIC for implementation

3G Transmission Network Planning Engineer: NetAct Planner - Transmission Planner: define Access and ATM parameters NetAct Plan Editor : Complete AXC parameters for commissioning; Physical Templates are

available separately

Two types of data have to be created as a result of network planning: Radio Network Plan (RNW Plan (radio) and Coco parameter (trs)) Site Configuration Files, SCF (AXC SCF (trs) and needed parameters for WBTS SCF

(radio&trs))


3) Defining the ATM layer parameters in RNC using a remote session from Radio Access Configurator

5) Installing the network elements, commissioning them with the parameter files, and producing commissioning reports using theLocal Management Tool

4) Downloading parameter files and installation instructions for 3G BTSsand AXCs from the web server ofRadio Access Configurator to Local Management Tool

Remoteaccess to BTS

and AXCis possible

7) Downloading the radio network parameters using Radio Access Configurator Site

operational

6) Uploading the commissioning report from Local Management Tool to Radio Access Configurator

DCNoperational

User of NetAct PlannerUser of NetAct Planner User of RACUser of RAC Installation EngineerInstallation Engineer

Site Integration with Nokia NetAct

2) Completing plans with site specific default parameter templates in Plan Editor

1) Planning of WCDMA Radio Network and ATM Transmission in NetAct Planner


XML Transfer from Planner to Plan Editor

NetAct PlannerXML Transmission Planner

XML

files

NetActPLAN EDITOR

NetAct RAC

NetAct Transmission Planner allows the creation of an AXC

configuration file in XML format that can be exported to NetActPlan Editor. NetAct Plan Editor sends the configuration data to the relevant network element

via Element Managers.

More than 90% of radio parameters defined with plan editor e.g: Power control, Handover control, Adjacencies, etc. parameters

3G radio parameters from WCDMA Planner 4.0

2G&2.5G parameters from Radio Planner 4.0

3G trs/ATM parameters from Transmission Planner 4.0


Plan Editor & Templates

Over 90% of RNW parameters are still defined with PlanEditor even if WCDMA Planner is used.

10 -15% of TRS parameters are defined with PlanEditor, the rest of them comes from Transmission Planner.

Radio Network Planner creates required radio network plan with NetAct WCDMA Planner and completes it with PlanEditor by using templates:

Logical templates define default parameter sets for different kind of cells in different environments (e.g. Urban macrocell).

Physical templates manage the wide variety of WBTS sellable physical configurations (e.g. 1+1+1 ROC 20W).

Templates reduce the amount of manual steps in the object creation and reduce amount of typing errors --> faster object creation.

Templates available in Plan Editor BTS HW configuration template AXC configuration template set ATM parameter templates


Quality Assurance in LACE

Subcontractedsite work

Installation and Integration of WBTS and AXCRNC connection established

Planning Guidelines

Customer objectives & frame

agreement

TRS

RF

FIELD WORK

RIC & INTEGRATION MANAGEMENTNETWORK PLANNING RNW plan in Agreed

format(CSV)

NW plan(Coco & AXC)

in Agreed format SCF for

AXC

NETWORK 2G/3G RAN

WBTS

NetAct

RNC preparation work at NetAct, e.g. in RICRemote troubleshooting and NW expansion &

Configuration for WBTS/AXC

One placeand setfor verifiedparameters

A3A3

BB

AA

SCF forTRS COCOparameters

in RNC

SCF forRF

parametersin RNC

SCF forBTS

RNC

CC

PM:Delivered NE configuration

Nokia PM/TM

TM/PcoBTS SCF templates

NokiaRAN engineerA2A2

A1A1

DD

CC


Quality Assurance

A1, A2,A3A1, A2,A3

AA &B&B

CC

DD

A3: Network plan (TRS, Radio planner)Precise network plan in agreed format to RIC

Input: Accurate of delivery information (PM) A1

A2: BTS commissioning Template (RAN engineer)Precise BTS commissioning template in agreed format to RIC

Input: Accurate of delivery information (PM) A1

A: par after RIC process in OSS tools & B: XML output file from OSS tools (1.RNW (RAN&BSS), 2.AXC SCF, 3.BTS SCF, 4.Coco)

Precise information BEFORE putting into the network

RIC responsible to ensure A1+A2+A3 = A = Bprior to implementing to network

C: parameter in live network

Precise information is in the network

RIC responsible to ensure A1+A2+A3 = A = B = CRight after the implementation

D: Regular Audit (by Planners with RAN/OSS engineer support)


RNW Parameter Implementation process

OSSOSSOSS

eventsevents

eventsevents

RNCRNCRNCRNW plan activation

Local/Remoteoperations

OSSOSSOSS

eventseventseventsevents

eventseventseventsevents

RNCRNCRNCRNW plan activation

Local/Remoteoperations

Plan Editor

Import the CSV file

Export in XML format and import the output XML file into OSS

RNW datafillin

CSV format

RNW plan in XML format

CM plan Manager -For import plan to OSS DB

CM Provisioner For RNW plan activation

For Monitoring

WBTS

Parameter audit should be done after implementation to assure the correctness of the actual parameters and plan


Example of 3G Parameter Database Structure

Radio Network Controller (=RNC):With RAS05.1 512 Maximum WBTS objects 1152 Maximum WCELL objects 400 Maximum COCO objects Maximum 100 FMCx could be created for each FMCxMaximum 100 HOPx could be created for each HOPx

WCDMA Base Station (=WBTS):One BTS can have up to 24 WCELL and 1 COCO

WCDMA Cell (=WCEL):Maximum ADJS per WCEL : 31 (id1 31)

Maximum ADJG per WCELL: 32Maximum ADJI per WCELL: 48 (max 32 per frequency)


Example of 3G Parameter Database Structure

Each cell will be assigned the following for HC: One intra-frequency measurement control parameter set (FMCS), separate set for RT and

NRT traffic

One inter-frequency measurement control parameter set (FMCI), when inter-frequency neighbour cells are defined

One inter-system measurement control parameter set (FMCG), when inter-system neighbour cells are defined

Upto 32 intra-frequency neighbour cells (ADJS). Each neighbour cell will be assigned an intra-frequency handover path parameter set (HOPS), separate HOPS set for RT and NRT traffic

Upto 48 inter-frequency neighbour cells (ADJI). Each neighbour cell will be assigned an inter-frequency handover path parameter set (HOPI)

Upto 32 inter-system neighbour cells (ADJG). Each neighbour cell will be assigned an inter-system handover path parameter set (HOPG).


RIC

Run parameter checking macro to verify the correctness at the final stage.

Plan 1-4

RNW datafillin

Agreed format(CSV)

Default parameter

rules

Fixed Copy value to the datafill

User User defined parameter. Need to check range or name convention before assign it to the datafill.

Condition Some parameters depend on other parameters.In this case, there is condition for the parameter value. We need to check that all parameters correspond with the condition or not.

Plan - Make sure that the parameters retrieved from Plan1-4 are correct.

Data from the actual network (E.g RNC id,name ,2G ADJ cell id,2G ADJ related parameter) needs to be verified.

Final RNW datafill(CSV)

Parameter checking concept in LACE


Initial Parameter Planning

Scrambling code planning

Neighbour planning principles


Scrambling code

Each cell within the radio network plan have to be assigned a primary scrambling code

The 512 downlink primary scrambling codes are organised into 64 groups of 8

Group 0 = SC 07 Group 1 = SC 815 Group 63 = SC 504511


Scrambling code planning rules Main target to achieve sufficient isolation between cells which are assigned the same scrambling

code Ensure that a UE never simultaneously receives the same scrambling code from more than a

single cell UE never receives a scrambling code from one cell while it is expecting to receive the same

scrambling code from second cell SHO failures

Scrambling code planning may require co-ordination at international borders

Scrambling code planning can be completed independently for each RF carrier

An important part of scrambling code planning is to perform checks that neighbour lists do not include duplicate scrambling codes

Measured (neighbour) cell is identified by the scrambling code only


Example SC plan for ROC configuration Strategy: Maximise the number of neighbours belonging to the same code group When upgrade ROC Node B CEC Node B

Additional four scrambling codes from each group Two SCs for future expansion

Group 0

Group 2

Group 3

Group 4

Group 1

sc32

sc33

sc17

sc16

sc25

sc24

sc8

sc9

sc0sc1

Group 0

Group 2

Group 3

Group 4

Group 1

sc32

sc33

sc17

sc16

sc25

sc24

sc8

sc9

sc0sc1


Scrambling code planning methods

Using a radio network planning tool NetAct Planner is able to plan scrambling codes according to a

specific strategy

Using a home-made tool

Manually For small areas (e.g. less tan 30 sites)

Consideration should be given to moving the scrambling code plan to and from the live network


Neighbour planning and planning process

In general it is recognised that high quality neighbour lists are critical to the performance of the network

It is often assumed that neighbour lists will be refined during pre-launch or post-launch optimisation

Initial neighbour list planning does not have to be very accurate Impact upon pre-launch optimisation have to be recognised Pre-launch optimisation is usually limited to a specific drive route

Neighbours which are required away from the drive route must be identified during the planning process

It is difficult to generate ideal neighbour lists during the neighbour list planning because of differences between predicted and actual propagation

Pre-launch or post-launch optimisation required


3G Intra-frequency neighbour list

3G intra-frequency neighbour list planning is absolutely critical to network performance

3G intra-frequency neighbours are used for intra-frequency cell re-selection, softer handover, soft handover and intra-frequency hard handover

Excessive neighbours increase the UE measurement time and may lead to important neighbours being deleted during soft handover

Specification allows the network to specify a maximum of 32 intra-frequency cells for the UE to measure

Serving cell + 31 Intra-frequency neighbours when not in soft handover

2-3 serving cells + 30-29 neighbours in soft handover

Missing neighbours result in unnecessarily poor signal to noise ratios


Neighbour planning tools

Neighbour list planning can be completed using Planning tool, e.g. Netact Planner which utilises

Propagation predictions Minimum CPICH Ec/Io requirements Inter-cell interference Maximum allowed neighbour list size

A home-made tool Make use of distance and antenna azimuth rather than path loss

Using the 2G neighbour plan In networks which are primarily co-sited with existing 2G sites

Manually Small networks (e.g. less than 30 sites)

Intra-frequency neighbour lists should always be generated such that every neighbour relationship is bi-directional

Documents

Day2_06. Planning Support for 3G Roll-out_US