Pw Lahiani IMCNE07

8/14/2019 Pw Lahiani IMCNE07

1/66

-1-

Master degree report

SFR NETWORK OPTIMIZATION

By

MOHAMED LAHIANI

In partial fulfilment of the requirements for the Degree of

International Master on Communication Networks Engineering

2007/2008

At the

Scuola Superiore SantAnna

September 10th, 2008

Academic tutor

Prof. Piero Castoldi

Scuola Superiore SantAnna

Company tutor ......

Dott. Alessandro Di Gennaro


2/66

-2-

Acknowledgements

I would like first, to praise God the Almighty for giving me life, health and for making me

what I am today. Thanks to Him, this work has been achieved.

This thesis is the result of a path which I have walked through since I was a child. For this

reason, I would like to thank all my family for their support and teachings. Father, mother,

brothers, sister, you have always been there when I needed you.

I will never be able to repay you.

I would also like to express my deep gratitude to LEADCOM INTEGRATED SOLUTIONS

for hosting and financing me during the last 4 months. I wish to particularly thank Alessandro

Di Gennaro, Alberto Montecchiari,Flora Huyghe , Laurent Griponne and all the LEADCOM

INTEGRATED SOLUTIONS staff: they gave me the unique opportunity to work with some

of the most exceptional minds in this research Field.

I will never thank enough Prof. Imed Frikha, Prof. Piero Castoldi and every-one that made

this master course a reality and possible.

Finally, I would like to express my gratitude to everyone that has contributed, directly or

indirectly, to the realization of this work.


3/66


4/66

-4-

4.2.2 Analysis Principles...........................................................................................434.2.3 Problem area analysis flow-chart ................................ ......................................44

II.5 PERFORMANCE OPTIMISATION PHASE.............................................................45II.5.1 Performance Survey ............................................................................................46II.5.2 Performance Analysis ..........................................................................................46

II.5.3 Network Performance Optimization.....................................................................465.3.1 Call set-up failure optimization ........................................................................475.3.2 Drop Call optimization .....................................................................................48

II.6 SOME OPERATIONAL BEST PRACTICE............................................................48II.6.1 Configuration Management Process.....................................................................48II.6.2 System problem investigation..............................................................................48II.6.3 Some Maintenance/Optim coordination processes ...............................................49

6.3.1 Maintenance support when drive test measurements.........................................496.3.2 Request to open a Trouble Ticket .....................................................................506.3.2 Daily Trouble Ticket report ..............................................................................506.3.23Configuration Management .............................................................................50

Chapter III: NETWORK PREOPTIMIZATION & OPTMIZATION................................ ....51III.1 DECLARATION OF NEIGHBORS .........................................................................51III.2 Determination of SCR, MODEL RADIO & PALIER................................................52III.3 Atoll Simulation Week-5 ..........................................................................................53III.4 KPI Analysis:............................................................................................................55III.5 Run of Qualification: ................................................................................................58

III.5.1 Protocol of Run..................................................................................................58III.5.2 Run of Qualification Analysis: ...........................................................................58

CONCLUSION....................................................................................................................64REFERENCE.......................................................................................................................65GLOSSARY.........................................................................................................................66


5/66

-5-

List of Figures

Figure 1.1 Architecture of UMTS network..............................................................................8Figure 1.2 Allocation of code .................................................................................................9Figure 1. 3 Node B with 3 secteurs. ......................................................................................10Figure 1.4 Illustration of a tilt and electrical diagram representation of radiation...................11Figure 1.5.Simulation coverage following an electric tilt. ................................ ..................... 11Figure 1.6 Illustration of a tilt and mechanical representation of the diagram radiation. ........11Figure 1.7.Simulation coverage due to a mechanical tilt........................................................11Figure 1.8 Principle of softer-handover.................................................................................12Figure 1.9 Principle of softer-handover.................................................................................12Figure 1.10: RF optimization flow ................................ ................................ ........................14Figure 1.11 Shows divided clusters in a project. ...................................................................22

Figure 2.1 Standard optimization process..............................................................................29Figure 2.2 Tuning method for coverage and dominant area optimization .............................. 44Figure 2.3 Process of Optimization.......................................................................................44Figure 2.4 Process flow-chart for optimization of call set-up failures ................................ ....47Figure 3.1 The main Window of ocean .................................................................................51Figure 3.2 Import of Neighbors ............................................................................................52Figure 3.3 Creation Of DM of MES......................................................................................52Figure 3.4 Getting the Number of DM for the CA.................................................................53Figure 3.5 Atoll Simulation Antenna U1 Tilt Initial T4 .......................................................54Figure 3.6 Atoll Simulation Antenna U1 Downtilt de 2 soit T6..........................................55Figure 3.7 KPI of RAB Voice..............................................................................................56Figure 3.8 KPI of RAB Visio................................................................................................57Figure 3.9 KPI of the ISHO (3G/2G) ....................................................................................57Figure 3.10KPI of the ISHO (3G/2G) Success ................................ ......................................58Figure 3.11 Distribution of pilot SC for the 1st Best Service Cell..........................................59Figure 3.12 RSCP for 1st Best Service Cell ................................ ................................ ..........61Figure 3.13 Mobile Dual CSF - Run Q ................................................................................62Figure 3.15 Scanner for Sectors of our Site...........................................................................63Figure 3.16 Scanner for Sectors of The First Couronne.........................................................63


6/66

Master Report: SFR NETWORK OPTIMIZATION

-6-

INTRODUCTION

Analog cellular systems are commonly referred to as first generation systems. The digital

systems currently in use, such as GSM, PDC, CDMA One (IS-95) and US-TDMA (IS-136),

are second generation systems. These systems have enabled voice communications to go

wireless in many of the leading markets, and customers are increasingly finding value also in

other services, such as text messaging and access to data networks, which are starting to grow

rapidly.

Third generation systems are designed for multimedia communication: with them person to-

person communication can be enhanced with high quality images and video, and access to

information and services on public and private networks will be enhanced by the higher data

rates and new flexible communication capabilities of third generation systems. This, together

with the continuing evolution of the second generation systems, will create new business

opportunities not only for manufacturers and operators, but also for the providers of content

and applications using these networks.

In the standardization forums, WCDMA technology has emerged as the most widely adopted

third generation air interface. Its specification has been created in 3GPP (the 3rd Generation

Partnership Project), which is the joint standardization project of the standardization bodies

from Europe, Japan, Korea, the USA and China. Within 3GPP, WCDMA is called UTRA(Universal Terrestrial Radio Access) FDD (Frequency Division Duplex) and TDD (Time

Division Duplex), the name WCDMA being used to cover both FDD and TDD operation.

Throughout this book, the chapters related to specifications use the 3GPP terms UTRA FDD

and TDD, the others using the term WCDMA. This book focuses on the WCDMA FDD

technology. The WCDMA TDD mode and its differences from the WCDMA FDD mode are

presented in Chapter 13, which includes a description of TD-SCDMA.


7/66


-7-

In this report we will try to present a manual for UMTS data collection and for optimization

also solutions for analyzing and the way for resolving problems in RF part of the WCDMA Network. Many cases of this manual are used from the SFR UMTS Network.


8/66


-8-

Chapter I: RF OPTIMIZATION

INTRODUCTIONI.1 UMTS: Notions of bases

I.1.1 Architecture

The architecture of UMTS network consists of:

The UTRAN (UMTS Radio Access Network) responsible for managing the resources

of the radio access network. CN (Core Network): Part of the core network operating all subscribers and their

services associated

Figure 1.1 Architecture of UMTS network.

I.1.2 Interface radio

In WCDMA (Wideband Code Division Multiple Access), users all use the same

frequency band at the same time; the separation between different users is provided by

a "code" for each. This code is determined by a combination of:


9/66


-9-

Channelization Code" (Code of Channlisation), type OVSF used primarily to

discriminate a type of communication for users.

"Scrambling Code" (Code of jamming) used one hand to discriminate system cells

between them and secondly it allows the mobile to detect and synchronize on the cellreceived better to read the information systems

.

Here is an example allocation code:

Figure 1.2 Allocation of code

DATA

Channelizationcode

Scramblingcode

Bit rate Chi rate Chi rate

CS1

CS2

CS3

C8,2 C8,3

C4,3

C8,2 C4,1

For channels descendants

1code Hash CS(scrambling) per cell forguarantee the independence

between

1 code CS jammingallocated by each mobilenetwork

Here, C8,2 is used

by 2 to 1mobilesamecell, butwith 2codesinterference UL diffrents.

C8,1CS2

C8,2CS2

C8,2CS1

C8,2CS3 C4,2

CS4

For channels amounts


10/66


- 10 -

I.1.3 Dimensionnement

1.3.1 The Sectorisation

The sectorisation is to increase the number of sectors of the same site in order to increase the

capacity of the cell. It does these using directional antennas that emit only in a specific

direction (azimuth) which has the effect of reducing the co-channel interference and services

to more mobile. The configuration most commonly used now is that a 3 sectors. There are

configurations 2 sectors (site bi sectoral) under the cover of a road for example, even 1 zone

(site mono sectoral) for blankets "In Building" (Centre commercial stations, theatres, Etc.).

Figure 1. 3 Node B with 3 secteurs.

Note: This is called zone "overlapping" (zone recovery) the area where an overlap in several

sectors. In this area that the motive may be lead to make a "HandOver" (passage relay).

1.3.2 Tilt electrical and mechanical:

The height of an antenna, the width of the beam and its properties inclination (tilting

properties") are parameters antenna which are of considerable importance as the coverage of a

network. The first two are manufacturers predefined parameters, which can only be amended

by the optimization team is none other than the third. There are two methods for a tilt antenna:

A. The "tilt electric" during a lowering of the antenna (downtilt"), the main lobe, the lobe

and the rear side lobes are affected by such change. It is therefore distort the diagram of

radiation.


11/66


- 11 -

Figure 1.4 Illustration of a tilt and electrical diagram representation of radiation.

Avant Aprs

Figure 1.5.Simulation coverage following an electric tilt.

The "tilt mechanics": the antenna is literally inclined. In the event that fall on the antenna, the

main lobe would be left lobe lowered and the rear would be high. In terms of side lobes, they

would be only partially affected. In other words there is no distortion of the radiation pattern.

Figure 1.6 Illustration of a tilt and mechanical representation of the diagram radiation.

Avant Aprs

Figure 1.7.Simulation coverage due to a mechanical tilt .


12/66


-12-

1.3.3 Meaning of HandOver:

The "HandOver" reflects the ability of mobile to be connected to several base stationssimultaneously. In general, this feature is made possible by the use of receiver rake in the mobile node

and B. The controller base station or RNC (Radio Network Controller) maintains a list of candidates to

enter cells in handover with the current cell ( "Active Set") as a criterion type Eb / No (current cell) - Eb /

No ( cell candidate) threshold rejection.

There are several types of handover:

The "Softer HandOver 'motive remains in the same area covered by one base station.

Figure 1.8 Principle of sof ter-handover.

The "Soft HandOver" changes the mobile base station

Figure 1.9 Principle of sof ter-handover.

The "Hard HandOver" on the meeting when the soft-handover is not possible ie during a changeover to

other sub bands FDD, the changeover to TDD mode and at a changeover to another technology (2G,

IEEE802.11, etc.).


13/66


-13-

I.2 Basic Processes for RF Optimization

Once all the sites are installed and verification is complete, RF optimization starts. In some situations for

a tight schedule, RF optimization might start after the construction of partial sites is complete. RF

optimization is usually performed after 80% of total sites in a cluster are constructed.

RF optimization stage is one major stage of RNO. It aims at the following aspects:

Optimizing signal coverage

Control pilot pollution

Control SHO Factor based on DT

RF optimization also involves optimizing list of neighbor cells.

When the indexes like DT and traffic measurement after RF adjustment meets KPI requirements, RF

optimization stage ends. Otherwise you must reanalyze data and adjust parameters repeatedly until all

KPI requirements are met. After RF optimization, RNO comes to parameter optimization stage.

I.2.1 Flow Chat of RF Optimization

RF optimization includes the following four parts:

Test preparations

Data collection

Problem analysis

Parameter adjustment


14/66


-14-

1.10 shows the RF optimization flow chat.

Figure 1.10: RF optimization flow

In 1.10, the data collection, problem analysis, and parameter adjustment might be repeatedly performed

according to optimization goal and actual on-site situations until RF indexes meet KPI requirements


15/66


-15-

2.1.1 Test Preparations

During test preparations, proceed as below:Decide KPI goals for optimization according to the contract:

Divide clusters properly and decide test route with the operator

The KPI test acceptance route is especially important.

Prepare tools and materials for RF optimization

This ensures smooth RF optimization .

2.1.2 Data Collection

Collect the following data:

UE and scanner data DT Indoor test Signaling tracing

Call data tracing at RNC side

Configuration dataThe configuration data and the call data tracing help to locate problems.

Data collection is a precondition for problem analysis.

2.1.3 Problem Analysis

You can locate problems by analyzing collected data. After analyzing coverage problems, pilot

pollution problems, and handover problems, provide corresponding adjustment solutions. After

adjustment, test the adjustment result. If the test result cannot meet KPI requirements, reanalyze problems

and readjust parameters until all KPI requirements are met.

Due to weak coverage, pilot pollution, and missing neighbor cells, the following problems are related to

location:


16/66


-16-

Downlink interference

Access problems

Call drop problems

The previous problems occur regularly. You can solve them by repeated optimization.

If the coverage is good, pilot pollution and missing neighbor cells are not present, the access and call drop

problems need to be solved during parameter optimization stage. You can refer to corresponding

guidebooks. The period for solving uplink interference problems (RTWP is over high but no high traffic

Matches it) is long, even as long as the RF optimization ends.

Output an updated list of engineering parameters and list of cell parameters after RF optimization. The list

of engineering parameters reflects adjustment of engineering parameters (such as down tilt and azimuth)

during RF optimization stage. The list of cell parameters reflects the adjustment of cell parameters (such

as neighbor cell configuration) during RF optimization stage.

I.2.2 Test Preparations

Test preparations include the following four aspects:

Deciding optimization goal

Dividing clusters

Deciding DT route

Preparing tools and data

2.2.1 Deciding Optimization Goal

The key of RF optimization is to solve problems as below:

Weak coverage

Pilot pollution

High SHO Factor based on DT


17/66


-17-

Actually, different operators might have different standards on KPI requirements, index definition, and

attention. Therefore the RF optimization goal is to meet the coverage and handover KPI requirements inthe contract (commercial deployment offices) or planning report (trial offices).

Define the indexes as required by contract as below:

The index definition is the percentage ratio of the sampling points with the index (such as CPICH Ec/Io)

greater than the reference value in all sampling points.

Usually after RF optimization, the network must meet the index requirements listed in 0.

0 lists the RF optimization objectives according to analysis of and suggestion to coverage by existing

network.

Index Reference Remarks97% in

urban areaCPICH Ec/Io 9dB 97% insuburbanarea

According to test result from the scanner,

in unloaded and outdoor conditions, in planning coverage areas, test in a grid-like route to cover all cells.

98% inurban area

CPICH RSCP 95dBm 95% insuburbanarea

According to test result from the scanner,in unloaded and outdoor conditions, in

planning coverage areas, test in a grid-like route to cover all cells. The coveragelevel request is basic. If operators have

penetration loss request, add the penetration loss to the coverage level.

SHO Factor based on DT 30%40%

The SHO Factor based on DT should be5% to 10% lower than the goal, because

the following optimizations cause the softhandover factor to increasePilot pollution ratio 5%

Table 1-1: List of RF optimization objectives in R99 networks

The RF optimization of HSDPA services aims to improve the distribution of UE CQI.

According to theoretical analysis, the CQI reported by UE and PCPICH Ec/Nt have relationship as below: CQIUE = Ec/NtPCPICH + MPO + 10log16 + 4.5dB


18/66


-18-

Where in,

Nt = (1- a) * Ior + Ioc + No

a is the orthogonal factor

lor is the signals of serving cell

loc is the interference signals from neighbor cells

No is the thermal noise

Io = Ior + Ioc + No

Therefore, PCPICH Ec/Nt is approximately equal to PCPICH Ec/Io.

MPO = Min (13, CellMaxPower PcpichPower MPOConstant)

The maximum transmit power of a cell is usually 43 dBm, and the pilot channel power is 33 dBm.

When MPOConstant is 2.5 dB, the default configuration by RNC, the MPO is 7.5 dB.

The 4.5 dB is obtained according to the linear relationship between the SNR of the entire subscriber's HS-

PDSCHs and the corresponding CQIs. Namely, SNR = 4.5dB + CQIUE, and SNR = Ec/NtHS-PDSCH +

10log16.

When calculating CQIUE at UE side, the UE assumes that the total transmit power of HS-PDSCH is

PHS-DSCH = PPCPICH + MPO. Wherein, PPCPICH is the transmit power of PCPICH. Therefore,

Ec/NtHS-PDSCH = Ec/NtPCPICH + MPO. As a result, the CQI reported by UE is as below:

CQIUE = Ec/NtPCPICH + MPO + 10log16 + 4.5dB


19/66


20/66


-20-

Lists the relationship among the CQI reported by UE, pilot Ec/Io, and throughput rate at MAC-HS layer

(MPO = 7.5 dB).

9 > CQI 15 > CQI 9 CQI 15Subscribers' feeling Poor Fair Goodthroughput rate atMAC-HS layer forsingle subscriber

0320 kpbs 320 kbps to1.39 Mbps > 1.39 Mbps

Ec/Io > 15dB 15dB to 9dB 9dB

Table 1-2: Relationship among the CQI reported by UE, pilot Ec/Io, and throughput rate at MAC-HSlayer

The throughput rate provided in is based on the test in the following conditions:

The codes and lub are not restricted.

The category 12 UE has a subscribed rate of 2 Mpbs.

The subscribed type is background or interactive service.

Power is dynamically distributed. Namely, without R99 subscribers, all the power is used by the HSDPA subscriber to guarantee rate as high as possible.

According to the requirements on RF optimization of unloaded R99network, the

CPICH Ec/Io 9 dB. After HSDPA is introduced, power isdynamically distributed, and the single HSDPA subscriber at celledge uses all the power. Meanwhile, the downlink load reaches 90%,and CPICH Ec/Io 15.5dB.

If operators' requirement on throughput rate at cell edge is not the recommended values as listed in

, search the required value in 0.

0 lists the mapping relationship of HSDPA Catogory12 UE CQI and TB size. The CQIs that is larger than

13 or smaller than 5 are excluded. The rate at MAC-HS layer for the subscriber is (TBsize / 2ms) * (1

BLER), wherein, the BLER is 10%.


21/66


-21-

CQI TB Size5 365

6 3657 3658 7119 71110 105511 140512 174213 2083

Table 1-3: Mapping relationship of HSDPA Catogory12 UE CQI and TB size

As previously mentioned, to optimize HSDPA is to optimize Ec/Io of target networks. Therefore, in terms

of optimization method, the HSDPA and R99 networks are consistent. The following optimization flow

will not distinguish HSDPA networks from R99 networks.

2.2.2 Dividing Clusters

According to the features of UMTS technologies, the coverage and capacity are interactional and the

frequency reuse factor is 1. Therefore RF optimization must be performed on a group of or a cluster of

NodeBs at the same time instead of performing RF optimization on single site one by one. This ensures

that interference from intra-frequency neighbor cells are considered during optimization.

Analyze the impact of the adjustment of an index on other sites before adjustment.

Dividing clusters involves approval by the operator. The following factors must be considered upon

dividing clusters:

According to experiences, the number of NodeBs in a clusterdepends on the actual situation. 1525 NodeBs in a cluster isrecommended. Too many or few NodeBs in a cluster is improper.

A cluster must not cover different areas of test (planning) full coverageservices.

Refer to the divided clusters for network project maintenance of theoperator.

Landform factor: Landforms affect signal propagation. Mountains block signal propagation, so they are natural borders for


22/66


-22-

dividing clusters. Rivers causes a longer propagation distance, sothey affect dividing clusters in various aspects. If a river is narrow,

the signals along two banks will interact. If the transportation between two banks allows, divide sites along the two banks in thesame cluster. If a river is wide, the upstream and downstream willinteract. In this situation, the transportation between two banks isinconvenient, dividing clusters by the bank according to actualsituation.

A cell-like cluster is much usual than a strip-like cluster.

Administrative areas when the coverage area involves severaladministrative areas, divide clusters according to administrativeareas. This is easily acceptable by the operator.

DT workload: The DT must be performed within a day for a cluster.A DT takes about four hours.

Figure 1.11 Shows divided clusters in a project.


23/66


-23-

2.2.3 Deciding Test Route

Confirm the KPI DT acceptance route with the operator before DT. If the operator already has a decidedDT acceptance route, you must consider this upon deciding the KPI DT acceptance route. If the objective

factors like network layout cannot fully meet the coverage requirements of decided test route by the

operator, you must point this out.

The KPI DT acceptance route is the core route of RF optimization test routes. Its optimization is the core

of RF optimization. The following tasks, such as parameter optimization and acceptance, are based on

KPI DT acceptance route. The KPI DT acceptance route must cover major streets, important location,VIP, and VIC. The DT route should cover all cells as possible. The initial test and final test must cover all

cells. If time is enough, cover all streets in the planned area. Use the same DT route in every test to

compare performances more accurately. Round-trip DT is performed if possible.

Consider actual factors like lanes and left-turn restriction while deciding test route. Before negotiating

with the operator, communicate these factors with local drivers for whether the route is acceptable.

2.2.4 Preparing Tools and Data

Prepare necessary software (listed in 01), hardware (listed in 02), because the following test and analysis

are based on them.

Preparing Software

Table 1-4: lists the recommended software for RF optimization

No. Software Function

1 Tems investigation Datacollection Data collection

2Tems RoutAnalysis, GenexAssistant

Analyzing DT data and checking neighborcells

3 Actix Analyzing performance, Network KPIs4 Mapinfo Displaying maps and generating route data

Table 1-4: Recommended software for RF optimization


24/66


-24-

Preparing Hardware

Table 1-5 lists the recommended hardware for RF optimization

No. Device Specification Remarks1 Scanner DTI Scanner

2 Test terminal and data line Sonny Ericsson K800i

At least two testterminals. If thereis HSDPArequest, use thedata card E620.

U626 does notsupport HSDPA.3 Laptop PM1.3G/512M/20G/USB/COM/PRN 4 Vehicle mounted inverter DC to AC, over 300W

Table 1-5: Recommended hardware for RF optimization

Preparing Data

Table 1-6 lists the data to be collected before optimization

No. Needed data Whether is necessary Remarks1 List of engineering parameters Yes 2 Map Yes By Mapinfo or in paper3 KPI requirements Yes 4 Network configuration parameters Yes 5 Survey report No 6 Single site verification checklist No 7 Floor plan of the target buildings Yes For indoor test

Table 1-6: Data to be collected before optimization

I.2.3 Data Collection

During RF optimization stage, the key is the optimization of radio signals distribution,with the major means of DT and indoor test. Before test, confirm with the customer careengineers the following aspects:

Whether the target NodeBs, RNCs, and related CN are abnormal dueto being disabled, blocked, congested, and transmission alarms.

Whether the alarms have negative impact on the validity of test result data.


25/66


-25-

If the alarms exist, solve the problems before test.

DT is a major test. Collect scanner and UE data of radio signals by DTtest. The data is applicable in analyzing coverage, handover, and pilot

pollution problems.

Indoor test involves the following areas:

Indoor coverage areas

Indoor coverage areas include inside buildings, department stores, and subways.

Inside areas of important facilities

Inside areas of important facilities include gymnasiums and government offices.

Areas required by the operator: Areas required by the operator include VICand VIP.

Test the previous areas to locate, analyze, and solve the RF problems.

Indoor test also involves in optimizing handover of indoor and outdoor intra-frequency, inter-frequency,and inter-system.

The DT and indoor test during RF optimization stage is based on VP service. According to the contract

(commercial deployment offices) and planning report (trial offices), if seamless coverage by VP service is

impossible in areas, such as, suburban areas and rural areas, the test is based on voice services.

For areas with seamless coverage by PS384K service or HSDPA service required by the contract

(commercial deployment office) or planning report (trial office), such as office buildings, press centers,

and hot spot areas, the test is based on the above services.


26/66


27/66


-27-

Indoor test consists of walking test and vertical test.

Indoor test services are services by seamless coverage required in the contract (commercial deployment

office) or planning report (trial office). The method for indoor test and requirements on collecting call

tracing data are the same as DT.

2.3.2 Collecting RNC Configuration Data

During RF optimization stage, collect neighbor cell data of network optimization and other data

configured in RNC database. In addition, check whether the configured data is consistent with the

previously checked/planned data.

While checking configured data, feedback the improperly configured data (if found) to product support

engineers. During checking, pay special attention to handover reselection parameters and power setting

parameters, as listed in Table1-8.

Configured parameters to be checked

Type Content to be checked

Handoverreselection

parameter

IntraFreqNCell (intra-frequency neighbor cell)

InterFreqNCell (inter-frequency neighbor cell)

InterRATNCell (inter-system neighbor cell)Powerconfiguration

parameter

MaxAllowedULTxPower (maximum uplink transmit power of UE)

PCPICHPower (PCPICH transmit power)

HSDPA cellconfiguration

Whether the HSDPA cell is activated

HS-PDSCH code configuration

HS-SCCH configuration

HS-PDSCH and HS-SCCH power configuration

Table1-8: RNC parameters


28/66


-28-

Chapter II: SFR & NOKIA SIEMENS NETWORKS

PROCESS

The optimization process is divided into the following sub processes that are separately described:

Preparation phase where the objective is to set the correct environment (including team building and tools set up). At this stage is also requested to perform a network health

check (via Configuration Management team) to ensure that the planned network is

implemented correctly.

Network Assessment & Preliminary Radio Optimization phase where the purpose is to

meet a minimum level of radio performance. It is based on hardware changes, i.e. antenna

type, tilt and orientation, and changes in the 3G-3G neighbor lists. Inter-system reselection

and voice handover is also optimized (only changes in the 3G-2G neighbor lists). It does

not include changes on parameters beyond neighbor definitions or CPICH power.

Performance Optimization phase where the purpose is to raise the level of network

performance to the targets set between Nokia and SFR. Performance increase is achieved

by a detailed analysis of failures causes (access and drops), a cell base analysis, and

parameter changes. For different parameters sets a small reference area will be selected.

Cluster Acceptance to validate that performance targets are reached over all cluster.

Figure below presents the overall optimisation process including links and data flow between project

teams.


29/66


- 29 -

Figure 2.1 Standard optimization process


30/66


- 30 -

II.1 TOOLSThe following table includes all software and hardware tools required in different phases of the

optimisation process.

Tool Function

II.1.1Radio Design Analy sis

NetAct WCDMAPlanner

Preliminary radio design analysis based on coverage prediction

Digital terrain databases are provided by SFR

MapInfo + Macro 3G3G & 3G2G Adjacencies validation/definition MapInfo tool which

graphically displays cells and shows its neighbors defined in OSSdatabases

II.1.2 3G Radio Layer Optimisation

MapInfo Dive test routes definition

Sub-cluster definition

MapInfo + Macro 3G3G & 3G2G Adjacencies validation/definition MapInfo tool whichgraphically displays cells and shows its neighbors defined in OSSdatabases

Nemo 3G Outdoor Acquisition plate-form for 6650 mobile phone and WCDMA Scanner

Nokia 6650 Mobile phone used at this stage for voice short (10 sec) and longcalls. Mobile is set to 3G single mode only

WCDMA Anritsu orDTI Scanner

CPICH RSCP, EcN0 and RSSI measurements

Actix Analyser RVS Post-processing and analysis of all field measurement (MS +Scanner)

NetAct WCDMAPlanner Used to validate site engineering changes (i.e. tilts, azimuths)

PlanEditor + Macro UTRAN parameters consistency checks

EoSFlex Network KPI collection and reporting

II.1.3 Performance Optimisation

Nemo 3G Outdoor Acquisition plate-form for 6650 mobile phone and WCDMA Scanner

NITRO Acquisition plate-form for Samsung Z105 mobile phone

Nokia 6650 Voice and PS measurements (3G single or dual mode)

Samsung Z105 Voice, Visio and PS measurements (3G single or dual mode)


31/66


32/66


- 32 -

SHO performance Call Setup performance NodeB HW/SW pbm (ie Sleeping Cell

detection)

Voice call measurements (3G sing le mode only)

Survey Equipment NEMO 3G Outdoor + Nokia 6650 (3G single mode) NITRO + Samsung Z105 (3G single mode)

Measurement scenario Voice MOC (to fixed line) 2 minutes with 1 minute pause

Data Collected Monitored cells Ec/No, UE transmit power, detectedcells, locations of dropped calls, location of accessfailures

Metrics for Analysis Best Server Ec/Io, Active Set Size, dropped calls,access failures

Objectives Missing 3G3G adjacencies SHO performance Drop call causes investigation Access failure causes investigation

Voice call measurements (dual mode)

Survey Equipment NEMO 3G Outdoor + Nokia 6650 (dual mode) NITRO + Samsung Z105 (dual mode)

Measurement scenario Voice MOC (to fixed line) 2 minutes with 1 minute pause

Data Collected Monitored cells Ec/Io, UE transmit power, detectedcells, locations of dropped calls, location of accessfailures


Objectives Missing 3G2G adjacencies ISHO performance

2G Idle Mode measurements

Survey Equipment NEMO 3G Outdoor + Nokia 6650 (2G single mode) NITRO + Samsung Z105 (2G single mode)Measurement scenario No calls performed, logs are with MS IdleData Collected GSM RxLev and RxQualMetrics for Analysis GSM RxLev and RxQualObjectives Evaluate GSM coverage quality

3G2G adjacency plan optimization (combinedwith CPICH scanner measurements)

Visio call measurements

Survey Equipment NITRO + Samsung Z105 (2 MS used)

Measurement scenario Visio MOC (called MS is also in the VAN) 2 minuteswith 1 minute pauseCalling MS is set to dual modeCalled MS is set to 3G single mode


33/66


- 33 -

Data Collected Monitored cells Ec/Io, UE transmit power, detectedcells, locations of dropped calls, location of access

failuresMetrics for Analysis Best Server Ec/Io, Active Set Size, dropped calls,

access failuresObjectives Visio performance evaluation

Drop call causes investigation Access failure causes investigation

FTP call measurements

Survey Equipment NEMO 3G Outdoor + Nokia 6650 (dual mode) NITRO + Samsung Z105 (dual mode)

Measurement scenario FTP 128DL : 3Mb file transfer (30 sec pause bw DL)FTP 64UL : 1Mb file transfer (30 sec pause bw UL)

Data Collected Monitored cells Ec/Io, UE transmit power, detectedcells, locations of dropped calls, location of accessfailures


Objectives FTP performance evaluation Drop call causes investigation Access failure causes investigation

II.2.2 Measurement strategy2.2.1 Measurement Routes

3 route types have been defined.

ROUTESid TYPE OBJECTIVESROUTE A Detailed Cluster

drive test routeThis route should extensively go through each sectors coveragearea in order to validate good service conditions are providedwhere expected. This route is defined for both site verification (tovalidate that the site performs correctly as a stand-alone unit), and

cluster validation.Cluster size : 10/15 NodeBOne route is designed per cluster

ROUTE B Global referenceroute over all area

This route should be defined overall cluster area to demonstrateregular evolution of KPI performances. This route should not beso dense and should be performed in max 6/10 hours.

ROUTE C Acceptance drivetest route

Should be defined between SFR and NOKIA at least 2 weeks before starting the acceptance phase


34/66


- 34 -

2.2.2 Measurement RUNsROUTE MS SERVICES MS SETTINGS OBJECTIVES ANALYSE REQUIRED

RUN 1 ROUTE A

1 NOKIA 66502 SAMSUNG Z105

SCANNERVOICE (2 min + 1 min pause)VISIO (2 min + 1 min pause)

SINGLE MODE 3GSINGLE MODE 3G

Radio Coverage Quality Evaluation (for both Voiceand CS Data services)3G3G Mobility Performance Evaluation

Coverage (CPICH RSCP, Ec/Io) Black Spots identificationFirst Tilts or other site engineering recos (ie azimuth)

proposalFirst 3G3G ADJ recos proposal

RUN 2

ROUTE A1 NOKIA 66501 NOKIA 6650

SCANNERVOICE (2 min + 1 min pause)

IDLE MODEDUAL MODESINGLE MODE 2G

GSM Radio Coverage Quality Evaluation3G2G Mobility Performance Evaluation

Identify possible exclusion area for Voice where GSMquality is not enoughFirst 3G2G ADJ recos proposal

RUN 3

ROUTE A1 NOKIA 6650

2 SAMSUNG Z105


DUAL MODESINGLE MODE 3G

1st Tilt, 3G3G and 3G2G ADJ recos validation3G3G Mobility Performance Evaluation3G2G Mobility Performance

Additional recos (Tilt, 3G3G ADJ,) proposalExclusion Area identification Evaluation

RUN 4

ROUTE A1 NOKIA 6650

2 SAMSUNG Z105


DUAL MODECALLING MS : DUAL MODE /CALLED MS : SINGLE MODE 3G

2st Tilt, 3G3G ADJS recos validation3G3G Mobility Performance Evaluation3G2G Mobility Performance Evaluation

Additional recos (3G3G, 3G2G ADJ,) proposalSpecific cell basis parameter changes proposal (ie SHOOffset to reduce "Canyon Effects")

RUN 5

ROUTE C1 NOKIA 6650

2 SAMSUNG Z105


DUAL MODECALLING MS : DUAL MODE /CALLED MS : SINGLE MODE 3G

Latest Overall Cluster Perfomance Evaluation Additional recos (3G3G, 3G2G ADJ,) proposalSpecific cell basis parameter changes proposal (ie SHOOffset to reduce "Canyon Effects")

CONTINIOUS PERFOMANCE BENCHMARK

ROUTE B1 NOKIA 6650

1 SAMSUNG Z105

SCANNERVOICE (2 min + 1 min pause)

VOICE (2 min + 1 min pause)

DUAL MODE

DUAL MODE

VOICE Performance EvaluationGap Analysis NOKIA 6650 vs SAMSUNG Z105

ROUTE B2 SAMSUNG Z105

SCANNERVISIO (2 min + 1 min pause) CALLING MS : DUAL MODE /

CALLED MS : SINGLE MODE 3G

VISIO Performance EvaluationGap Analysis Voice vs Visio

ROUTE B1 SAMSUNG Z1051 SAMSUNG Z105

SCANNERFTP UL64 (File 1 Mo)

FTP DL128 (File 3 Mo)DUAL MODEDUAL MODE

PS Data Performance Evaluation


35/66


- 35 -

II.2.3 Measurement standard procedure A typical procedure for drive test measurements is:

1) Check consistency of all parameters of the cells/sites belonging tothe cluster/sub-cluster prior the measurement starting.

2) Coordination between drive team (DT) and monitoring team (O&M);make sure all sites are unlocked for measurements, and normallyradiating, i.e. no alarm preventing measurements.

3) Start/Continue measurements session; at any call drop:

a) Stop the van, if possible

b) Note any event that could have caused the drop (poor coverage,wrong SC, missing neighbour)

c) Goto 2)

4) On completion of the drive route:

a) Make sure that all the drive measurements has been correctlylogged in a file

b) Make sure all events that may have affected the results havebeen recorded

Coordination between drive team (DT) and monitoring team (O&M); DT should inform

O&M when NodeB instability is detected, and O&M should inform DT about any NodeB

operations.

II.2.4 Measurement chain As requested for the acceptance, measurements are executed in Incar mode. The

measurement procedure is the following:

2 antennas shall be installed on the roof top of the Van : 1 for theWCDMA scanner and another for the mobile phone

Mobile phone : the total losses in the measurement chain shallequal 7 dB to reproduce the Incar losses

WCDMA scanner : the total losses in the measurement chain shallequal 0 dB


36/66


- 36 -

II.3 PREPARATION PHASEII.3.1 Team Building & Tools Set Up

Objective here is to set up required resources and tools.

Dimensioning will depend on number of cluster, volume of sites par cluster and cluster

geographical distribution.

Main impact of this geographical distribution is clearly on dimensioning necessary

measurement Vans.

II.3.2 Cluster NEs Configuration ManagementThe Cluster network health check ensures that the planned network is

implemented correctly, all cells are up and running and correct parameters are

set. These should be done before starting first measurements. There are many

checks to look at:

Alarm check (BTS, RNC, other)

SW (i.e. NodeB SW, AXC SW) and Parameter check (i.e.

DCN, Iub ATM) Neighbour consistency check

Cell load check

KPI check

NEs alarms should be investigated and solved by O&M team, and potential

misalignments in network parameterisation should be corrected by Configuration

Management team.

Prior first measurement campaign starting, five Configuration & Performance

Management reports should be set up and reported to optimization team:

NodeB configuration follow up (on a regular basis, ie 2 timesper month) To be produced by Configuration Managementteam

Cell Availability status (once per) To be produced byConfiguration Management team

NodeB alarms history report (on a daily basis) To beproduced by Configuration Management team


37/66


- 37 -

Trouble Ticket report (on a daily basis) To be produced byO&M team

EoSFlex Top KPI report (on a daily basis) To be produced byConfiguration Management team

In addition, before each measurement campaign and after each massive UTRAN

parameters changes (ie Neighbours), Cluster UTRAN parameter consistency

check should be performed.

II.4 NETWORK ASSESSMENT & PRELIMINARYRADIO OPTIMISATION PHASE

II.4.1 Radio Design Analysis As radio design of the cluster to optimise has been performed by SFR, the main activity

in this phase is to acquire detailed information on the cluster, and then analyse this info

using NetAct WCDMA Planner tool, to identify potential problems and to define the

measurement strategy.

4.1.1 Pre-requisites analysisPre-requisites that should be provided by SFR for each cluster are listed

hereafter.

These pre-requisites have to be provided 6 weeks before the optimisation

contractual starting date (T0).

Pre-requisites Priority

KPIs service level (SILVER, GOLD, PLATINUM) & Number of KPIs to reach (5 or9)

1

List of Node-Bs to optimise 1

Cluster terrain database (5m resolution for dense urban and urban areas, 50m forsuburban and rural). This database includes ; DTM, Building Height, Clusterlayers).

1

CW measurements in 2GHz or 1.8 GHz bands and calibration reports whenavailable

2

SFR design engineering criteria and rules (coverage thresholds, power budgets,) 1

3G site database (including sites within the cluster & sites located 5 km around) : 1


38/66


- 38 -

Site coordinates (X, Y, Z)

Site ids (Site Name, Code, Cell Id,) Antenna height Sectors and Azimuths Tilt figures (mechanical + electrical relative to 0) Antenna type Cable losses Primary Scrambling Codes Powers of the common channels of each sector 3G3G and 3G2G neighbour list Radio parameter settings

2G site database (including sites within the cluster & sites located 5 km around) : Site engineering config (see details above) BSIC and BCCH frequency channel 2G2G neighbour list Radio parameter settings

1

Cluster contour definition (Radio KPIs will be measured inside this contour) 1

Cluster contour coverage statistics and the interference levels :

% Points with Pilot RSCP >= -91 dBm, % Points with Pilot Ec/Io >= -10 dB

Coverage plots for Incar CS64 and PS128 services

1

Site integration timetable 1

3G site folders including the following informations : Site implementation drawingson the scale (for all antenna installed on the site : antenna support location,antenna height, antenna type, azimuth, tilt, isolation distance, nearby obstaclesindication, feeder type and length), and panoramic photos.

1

Cluster digital maps (useful to define drive test routes) 2

Iub transmission topology (including Iub & DCN IP config) 2

Pre-requisites analysis consists in checking consistency of info provided by SFR,

and request for missing data.

Inconsistency report between Site Folders and Engineering Database

(IngeUTRAN) should be produced if needed.


39/66


- 39 -

4.1.2 Radio Design AnalysisMain tasks of this phase are:

Site radio engineering checking (photo, antenna implementation,Height, Azimuth, Tilt)

Digital terrain database integration in NetAct Planner (50m and/or5m resolution databases are provided by SFR, and should beconverted to NetAct planner format)

Propagation model tuning (Volcano model is used. Tuning will berequired when the standard deviation of our generic model ishigher than 9dB when compared to some WCDMA scannermeasurements. When available, this tuning will be performed withCW measurements provided by SFR. If not available, a softtuning only with WCDMA scanner measurements will be done).

Radio planning with NetAct WCDMA Planner (including 3Gparameters planning)

o Identification of poor coverage areaso Identification of good enough coverage areas, but poor

quality (bad EcI0)o Pilot pollution analysiso Identify possible site engineering changes (tilts, azimuths,

Power) 3G/3G neighbouring cells planning 3G/2G neighbouring cells planning Sub-cluster definition (cluster is divided into 10/20 sites sub-

clusters specific drive test route measurements are defined foreach sub-cluster)

Reference drive test routes definition (see 5.2.1 MeasurementRoutes)

o One global reference route (Route B)o One route for each sub-cluster (Route A )

During this phase its also possible to identify areas where the sites position if not

optimal and might prevent the full optimization. These cases must be discussed

with SFR.

The information in the planning tool can also be used in the following phases to

complement the measured data in the analysis and to support in the validation of

site engineering change request (ie Tilts and Azimuths).


40/66


- 40 -

NetAct Planner configuration and Radio Design analysis main steps are

presented the following documents:

[1] NetAct Planner Configuration Guidelines

[2] NetAct Planner Plots/Outputs

[3] 3G3G Adjacencies Planning

[4] 3G2G Adjacencies Planning

[5] Primary Scrambling Code re-uses analysis

[6] Preliminary Tilt analysis

Before starting the first measurement campaign 3G/3G & 3G/2G have to be

implemented in the network both in RNC and BSC see 10.1 Configuration

Management Process.

II.4.2 3G Radio Layer OptimizationThe main target of this phase is to optimise the radio environment, both from coverage

and quality point of view.

Main tasks of this phase are:

Radio measurement & post-processing Problem analysis (coverage and dominance main issues) Site visit for specific radio coverage problems Cross feeder identification Site engineering modification requirements (mainly electrical tilt) 3G3G and 3G2G neighbouring cells and CPICH Power

requirements and implementation Radio measurement control of specific problems Reporting of major issues

The first step is to perform a measurement campaign, where radio measures

(WCDMA Scanner) are performed together with 1 Voice call and 1 Visio call

(RUN 1). The results are then processed to produce reports and analysed.


41/66


- 41 -

In some specific radio coverage problems (i.e. poor coverage or strong

dominance), site visit will be planned. So, site access to Nokia has to be

guarantee by SFR.

The outcome of the analysis is a number of recommendations for changes to

software (mainly 3G3G and 3G2G neighbouring cells and CPICH Power), site

configuration parameters (Tilt, Azimuth) and site wrong configuration (cross-

feeder).

While the software parameters are handled directly by Nokia engineers, the site

configuration changes other than electrical tilt must be approved by SFR. In case

they are accepted, the changes should take place within a lead-time agreed

between SFR and Nokia, from the moment they are submitted by Nokia. Delays

in this will necessarily reflect on the overall duration.

In case they are rejected, Nokia and SFR should agree to find an alternative

solution. In some extreme case, where no alternative solutions can be found (i.e.

the exclusion of some areas from KPI evaluation will be negotiated).

All the changes identified through the measurement campaign are documented,in order to be inserted in SFR Data Bases (IngeUTRAN). see 10.1

Configuration Management Process.

4.2.1 Radio Optimization stepsThree specifics runs can be defined:

1) First Run Improve overall radio coverage performances

a. Measurements are performed over sub-cluster routes(measurement protocol used is described in 5.1.1)

b. First corrections should focus on electrical tilts and 3Gneighbouring

c. After corrections implementation, a validation drivetest is performed over the same sub-cluster routes

2) Second Run Focus on remaining poor radio areas (improveEc/Io, reduce pilot pollution)


42/66


- 42 -

a. Analyse poor coverage (Scanner CPICH RSCP < -92dBm)

- Detailed measurements are performed overselected poor coverage area in order to evaluateare size

- Is there any possible optimization actions (otherthan adding a new site) to improve the coverage(ie Antenna height, bearing, Azimuths)?

- If yes, validate possible actions with NetAct

Planner- If no, exclusion area should be reported

b. Analyse good coverage, poor Ec/Io (Scanner CPICHRSCP > - 90dBm, Ec/Io < -12dB)

- Detailed measurements are performed over selectedpoor quality area in order to evaluate are size

- Is there any possible optimization actions (other thanchanging Powers) to improve the quality (ie improvecell dominance/cell overshooting with fine tuning Tilts,

Azimuths)?

- If yes, validate possible actions with NetAct Planner

- If no, goto to 3)

3) Third Run Focus on remaining poor radio areas where no re-engineering actions can improve performances

- Evaluate possible CPICH Tx Power changes(use NetAct for validation)

- Is some quality improvement?

- If no, set previous CPICH Tx Power andexclusion area should be reported


43/66


- 43 -

4.2.2 Analysis PrinciplesCell Availability and Trouble Tickets reports should be checked before starting analysis

in order to identify possible NodeB instability impact on measurements.

If for any faults/problems reasons site/cells seem to be faulty, a site trouble report to

O&M team should be issued for further inspection on the site status and alarms.

From OMC/EoSFlex some report tables (ie Service level report and Cell resource and

cell availability report) should be also in the analysis.

To provide sufficient RSCP and clear dominant is a basic concept in optimisation. Use

Actix to check RSCP and Ec/Io of each SC distributed to that area. Antenna panning /tilting might be required to optimise and create a dominant cell area.

Minimum performance should be achieved by avoiding unnecessary overlapping

The cause(s) of dropped calls and its origin like poor coverage, radio quality, and UE or

network problem should be analysed. Studying the layer3 messages are useful to identify

these problems and their root-cause.

In some cases we observed dropped call due to the reach of the UL Coverage limit.

Uplink coverage of UE is smaller compared to serving cells downlink coverage. This

UL/DL imbalance result into that the UEs Tx power is not sufficient to reach serving cell

in some areas. This UL/DL imbalance can be due to MHA wrong parameter settings. In

this case NodeB commissioning file should be checked.

If the current serving cell is far distant from UE but there is a candidate cell, which is

closer to UE to serve the problematic point, the candidate cell needs to be optimised to

serve the area.

However, it should be confirmed that there are not too many scrambling codes distributed

to this area by increasing the coverage with a new candidate cell. It is favourable to use

the Anritsu scanner data to analyse this problem.

The tuning method to optimise coverage and cell dominance area was tabulated below.


44/66


- 44 -

Down-tilting of int erfering cellsantenna, which generate pilot pollution Change CPICH Tx Power: Increaseserving cells Tx power but decreaseinterfering cells Tx power Change antenna bearing angles of cellsinvolved in pilot pollution Change antenna patterns of cellsinvolved in pilot pollution. Smaller gainsfor interfering cells and higher gain forvictim cell Decrease antenna height of interferingcells and increase antenna height ofvictim cell with adequate tilting angle

Down-t ilting of interfering cellsantenna, which generate pilot pollution Change CPICH Tx Power: Increaseserving cells Tx power but decreaseinterfering cells Tx power Change antenna bearing angles of cellsinvolved in pilot pollution Change antenna patterns of cellsinvolved in pilot pollution. Smaller gainsfor interfering cells and higher gain forvictim cell Decrease antenna height of interferingcells and increase antenna height ofvict im cell with adequate tilt ing angle

Up-tilt ing of serving cells antenna toextend coverage radius and to improveunsatisfied coverage area Increase CPICH Tx Power of serving cell Change Antenna Bearing Angle: Focusthe main beam of antenna to coverageholes and low RSCP area Change Antenna Pattern: Displace withhigher gain antenna with adequateantenna tilting Increase serving cells antenna height toget higher effective antenna gain butthere is risk to make undesirable inter-cell interference to adjacent cells

Up-tilting of serving cells antenna toextend coverage radius and to improveunsatisfied coverage area Increase CPICH Tx Power of serving cell Change Antenna Bearing Angle: Focusthe main beam of antenna to coverageholes and low RSCP area Change Antenna Pattern: Displace withhigher gain antenna with adequateantenna tilt ing Increase serving cells antenna height toget higher effective antenna gain butthere is risk to make undesirable inter-cell int erference to adjacent cells

Tuning met hods forCoverage Problem AreaTuning methods forCoverage Problem Area Tuning met hods forDominance Problem AreaTuning methods forDominance Problem AreaHigh PriorityHigh Priority

Figure 2.2 Tuning method for coverage and dominant area optimization

4.2.3 Problem area analysis flow-chartDrive Test

Measurement

Coverage area optimization

Dominance areaoptimization / SHO opt

Dominance area optimization /SHO opt

CompleteMeasurement

Analysis

Best servers CPICHRSCP>-92dBm

Nth best serverCPICH RSCP>- 92dBm

Best serversEc/No


45/66


- 45 -

Some optimisation guidelines and processes are detailed in the following documents:

[7] Actix Analyser Configuration Guidelines

[11] 3G3G Adjacencies Optimization (based on field measurements)

[12] 3G2G Adjacencies Optimization (based on field measurements)

II.5 PERFORMANCE OPTIMISATION PHASE After the radio layer, the End-to-End services are optimised. This is done again

through a measurement campaign, where the services to be optimised are tested. At the same time, radio parameters are checked again to verify the effect of the

changes.

Main tasks of this phase are:

Service performance (Voice, Visiophony, FTP) measurement & post- processing

Radio coverage and End-to-End KPI status Detailed problem analysis (Drop Calls, SHO failures, Call set-up

failures)

3G3G neighbouring cells and 3G parameters modification requirementsand implementation

3G2G neighbouring cells modification requirements and implementation Reporting of major issues

The measurement reports are analysed, and, where needed, changes are made to software

parameters. In case changes are needed on equipment not provided by Nokia, like

Transmission or Core network, Nokia will submit a change request to SFR. The change

should be completed within a lead-time agreed between SFR and Nokia, to avoid impact

on the duration of the service.

All the changes are reported to SFR, together with the relevant measurement reports.

For detailed analysis, some logs from UTRAN & CORE sub-system interfaces (Iub,

IuCs, IuPs, Gn, Gi, Gr) can be used. So, UTRAN & CORE interfaces access to Nokia for

measurement purpose (via network analysers) has to be guarantee by SFR.


46/66


- 46 -

A final report is generated, containing the measurement report showing the fulfilment of

the KPIs requested. This report shows that the cluster is ready for final acceptance, from

the 3G performance point of view.

II.5.1 Performance SurveyAll services are tested over the detailed sub-cluster routes.

This performance survey is used to evaluate overall E2E performances.

It can be run before end of the previous 3G Radio Layer Optimisation.

II.5.2 Performance Analysis

Detailed drop calls and access failures analysis are performed in order to evaluate all potential failure causes.

An action plan is defined to:

Identify without ambiguity failures causes Validate possible corrective parameter settings

Action plan should focus on main issues (high priority is given to cause which have main

impact).

Failures should be sorted by cells/sites. Sites with higher failure occurrence should be

checked. Cell availability / Trouble Ticket reports and OSS counters/KPI should be cross-

checked in order to identify possible NodeB faults. If needed a site trouble report to

O&M team should be issued for further inspection on the site status and alarms.

Some new parameter templates can be evaluated. For that purpose, a small trial area (a

sub-cluster for instance) should be selected.

II.5.3 Network Performance OptimizationA measurement / analysis / changes loop is implemented and run until KPI commitments

are reached.Global reference route will be measured on a regular basis (ie 2 times per month) to

evaluate the gap still to improve to reach the commitments.

One of the outcomes at this stage is also identification of all reasons that can prevent KPI

achievements (Burden proof mechanism):

UE-specific problems (hanging onto the cell, poor cell reselection, poor power control)

UE-NW incompatibilities


47/66


- 47 -

BTS, RNC or network faults Other sub-system (CNCS, CNPS), third party faults

5.3.1 Call set-up failure optimizationIt was observed that call set-up failures came from the UE itself or due to a network

problem. In these cases the Service level report together with drive-test analysis was

profound in the troubleshooting.

The basic process of call set-up failure optimisation is summarized in a flow chart below.

Check failure cause(Not radio problem/cell update)

Start

Best serversRSCP > -92dBm

Best serversEc/No > -9dB

DL Coverage Optimizat ionDominant area optimization

UL coverage Opt imization(Change serving cell )

(DCH) RRCConnection setupCompleted sent f rom UE?

(Reason of probl em:L1 sync fail)

Radio Bearer setupfailureReceived?(Check failure cause)

Yes

Yes

No

No

Yes

No

Yes

No

Yes

No

Neighbor listOptimization

MissingNeighbor ?

Yes

NoOther Good

Candidate Cell(from Scanner data)

?

Cell Reselect ionOptimization

No

Yes

UETx Pwr = Max (24dBm)&

Received Power increase TPC?

Check failure cause(Not radio problem/cell update)

Start

Best serversRSCP > -92dBm

Best serversEc/No > -9dB

DL Coverage Optimizat ionDominant area optimization

UL coverage Opt imization(Change serving cell )

(DCH) RRCConnection setupCompleted sent f rom UE?

(Reason of probl em:L1 sync fail)

Radio Bearer setupfailureReceived?(Check failure cause)

Yes

Yes

No

No

Yes

No

Yes

No

Yes

No

Neighbor listOptimization

MissingNeighbor ?

Yes

NoOther Good

Candidate Cell(from Scanner data)

?

Cell Reselect ionOptimization

No

Yes

UETx Pwr = Max (24dBm)&

Received Power increase TPC?

Figure 2.4 Process flow-chart for optimization of call set-up failures

Detailed Call set-up failure optimisation process is presented in document [9] Call Set up

Failure Analysis.


48/66


- 48 -

5.3.2 Drop Call optimizationThe concept of drop optimisation is the same as for call set-up failure analysis, i.e. to

provide sufficient RSCP and clear cell dominance areas. Studying layer3 messages are

also important here to identify problems.

Detailed Drop Call optimisation process is presented in document [8] Drop Call Analysis.

Additional guidelines and processes used at this stage are presented in the following

documents:

[10] Top KPI Analysis

[13] Sleeping Cell Analysis

[14] Cell Interference Analysis

II.6 SOME OPERATIONAL BEST PRACTICEII.6.1 Configuration Management Process

1. Send parameter change requests (with right format) to Nokia Configuration

Management team.

2. CM team has to confirm the date when those changes will be implemented in the

network (few changes are implemented the same day).

3. As soon as the implementation date is confirmed (normally it should be confirmed

the same day of your request), send the required file for IngUTRAN update purpose

to your SFR radio interfaces + put in the loop SFR CA (Centre d'Administration)

4. SFR radio team should afterwards confirm you when IngUTRAN is updated (to

be sure, request an IngUTRAN extract)

II.6.2 System problem investigationFor unknown or unclear drop or access failures causes, a site request for investigation

has to be sent to System Support team.

Template of this request Site Problem tracking form is attached in Annex 2.

To qualify/describe as much as possible the problem, before each request following

checks are mandatory:


49/66


- 49 -

1. TOP KPI + Cell avalaibility report Check for instance if the site/cell is

Blocked or in Sleeping state

2. Alarm history Check possible HW issues

3. Trouble Tickets

4. Site Configuration follow up report - Check possible config misalignment (ie

MHA with wrong settings) or synchro pbm (ie DAC Word)

II.6.3 Some Maintenance/Optim coordination processes

6.3.1 Maintenance support when drive test measurements1) Friday W-1, Zone Managers have to send to Nokia monitoring team (O&M) (Franck

Papo & Yannick Marquette), a detailed measurement plan for week W (measurement

plan template is attached in Annex 3).

2) Prior starting the measurement, coordination between drive test team (DT) and O&M

team ; make sure all sites are unlocked for measurements, and normally radiating, i.e. no

alarm preventing measurements. It's up to DT to call O&M team.

3) Start/Continue measurements session; at any abnormal event (several access failure in

the same site with no coverage pbm, missing SC...):a) Stop the van, if possible

b) Note the event

c) Goto 2)

4) When NodeB instability/suspected alarms are detected by O&M team, O&M team

has to inform DT team. Also, DT team has to be informed about any NodeB operations.

5) On completion of the drive test, DT has to :

a) Make sure that all the drive measurements has been correctly logged ina file

b) Make sure all events that may have affected the results have beenrecorded/reported


50/66


- 50 -

6.3.2 Request to open a Trouble Ticket

6) When suspected NodeB pbms are noticed by Optimization team, a request to open a

TT has to be sent to O&M team. This request should describe as much detailed as

possible the suspected pbm and the operation type to plan (i.e. 10 MHz meas, WSC card

change...).

7) This request should be acknowledged by O&M team; TT number, date of operation

should be confirmed.

8) When the NodeB operation is completed, a report has to be sent to Optimization team

(Ing who sent the request + Zone Manager). This report should describe; site status

before operation, operation performed, site status after operation.

6.3.2 Daily Trouble Ticket reportA daily TT report has to be sent by O&M team. This report should include; TT number,

pbm description, date of operation.

Cluster alarms and cell availability reports will be provided by Stephane Ponot. As TOP

KPI report, those reports will be stored by Stephane on a daily basis in the appropriate

project folders.

6.3.23Configuration ManagementCluster site configuration report will be from now on performed by EoS team.

This report will be done on a weekly basis for all clusters. Only DAC Word values are

not reported (value still to be checked by System Support team).


51/66


- 51 -

Chapter III: NETWORKPREOPTIMIZATION & OPTMIZATION

III.1 DECLARATION OF NEIGHBORS

The firs step to do for the integration for one site is the declaration of his neighbors

3G/3G and 3G/2G.

After the declaration we inject the neighbors in a specific Database which is Ocean.For the declaration of neighbors we should respect many rules defined by SFR such as

SIB11 criteria (the criteria changes from one Region to another).

Figure 3.1 The main Window of ocean


52/66


- 52 -

Figure 3.2 Import o f Neighbo rs

III.2 Determination of SCR, MODEL RADIO & PALIER

Before the Integration we should determinate the SCR of each sector by w specific tool

and we should create the Model Radio of the site and inject all this information on the

ocean database.

After injecting the neighbors and inject all the information about the site we create a DM

for the Mise En Service (when the site will be on air)

.

Figure 3.3 Creation Of DM of MES


53/66


- 53 -

Figure 3.4 Getting the Number of DM fo r the CA

III.3 Atoll Simulation Week-5

Before the integration of the site we should do some simulations for our site and also for

the Cluster in order to do some recommendations of Electric Tilt.

Setting antenna down tilt depends on the following factors:

Relative height to around environment

Coverage range requirements

Antenna types


54/66


- 54 -

If the antenna down tilt is improper, signals are received in the areas which are covered

by this site.

Therefore interferences to other areas cause pilot pollution. Even worse, interferences

might cause call drop.

Figure 3.5 Atoll Simulation Antenna U1 Tilt Initial T4

130015

130041

130075

130132

130743

130752

130

130761

1 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 9

130770

131736

131744

132080

132108

132231

133622

846 500 847 000 847 500 848 000

1 4

5 0 0

1 8

1 5

0 0 0

1 8

1 5

5 0 0

1 8

1 6

846 500 847 000 847 500 848 000

1 8 1 4

1 8 1

5 0

0 0

1 8 1

5 5

0 0

0 0 0


55/66


- 55 -

Figure 3.6 Atoll Simulation Antenna U1 Downtilt de 2 soit T6

III.4 KPI Analysis:After the integration of the site and the Mise en service we should check the results of the

KPI to generate the report J+1 and S+1. We should attend the Rate of KPI defined by

SFR to validate the site. If we discover that the Rate of KPI are bad so we should do

some investigations such as Add and Dell of neighbors using the Flux (a database

generated to define the traffic and exchanges between the different sectors and sites.

RSCP: Received Signal Code Power.

RSCP is an acronym used in UMTS and other CDMA cellular communications systems

and stands for

While RSCP can be defined generally for any CDMA system, it is more specifically used

in UMTS.

130015

130041

130075

130132

130743

130752

13076

130761

1 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 91 3 0 7 6 9

130770

131736

131744

132080

132108

132231

133622

8 4 6 5 0 0 8 4 7 0 0 0 8 4 7 5 0 0 8 4 8 0 0 0

8 1 4

5 0 0

1 8

1 5

0 0 0

1 8

1 5

5 0 0

1 8

1 6

8 4 6 5 0 0 8 4 7 0 0 0 8 4 7 5 0 0 8 4 8 0 0 0

1 8 1 4 5

1 8 1

5 0

0 0

1 8 1

5 5

0 0

6

0 0 0


56/66


- 56 -

Also, while RSCP can be measured in principle on the downlink (DL) as well as on the

uplink (UL), it is usually associated only with the downlink and thus it is presumed to be

measured by the UE and reported to the Node-B.

In brief, the received power on one code after de-spreading measured by UE on the pilot

bits on a given channel. The reference point for the RSCP is the antenna connector of the

UE. If Tx diversity is applied on the measured channel then the received code power

from each antenna is separately measured and summed together in watt to produce a total

received code power on the measured channel.

Figure 3.7 KPI of RAB Voice


57/66


- 57 -

Figure 3.8 KPI of RAB Visio

Figure 3.9 KPI of the ISHO (3G/2G)


58/66


- 58 -

Figure 3.10KPI of the ISHO (3G/2G) Success

III.5 Run of Qualification:III.5.1 Protocol of Run

Scanner Mob1: Long call 3G locked Mob2: Short call 2min 1min Dual mode (50 calls minimum) Mob2: Idle 2G locked

III.5.2 Run of Qualification Analysis:Usually, the strongest RSCP received by each scanner in the coverage area must be above

95 dBm.Start Assistant. Analyze scanner-based RSCP for 1st Best ServiceCell , and you can

obtain the distribution of weak coverage area.

Weak coverage areas with RSCP smaller than 95 dBm in the DT route. According to

scanner and UE, the pilot RSCP is acceptable. If the scanner antenna is mounted outside

the car, and the UE is inside the car, there is a penetration loss of 5 to 7 dB. Use scanner


59/66


- 59 -

data to avoid incomplete pilot information measured by UE due to missing neighbor

cells.

Cell primary pilot analysis is analyzing cell scramble information obtained in DT.

Start Assistant. Analyze scanner-based RSCP for SC , and you can obtain the

signal distribution of each cell (scramble). According to DT data, if the scramble signals

of a cell are not present, probably some sites cannot transmit signals during test. If a cell

cannot transmit signals during DT, the DT of relative areas must be re-performed. Very

weak coverage might be result of blocked antennas, so you must check the survey report

of the site and check installation of on-site antennas. No (poor) coverage cell might be

due to that the DT route does not cover the cell coverage area. In this case, reevaluate the

DT route for the rationality and perform DT again.

Figure 3.11 Distribu tion of pilo t SC for the 1st Best Service Cell


60/66


- 60 -

Start Assistant. Analyze scanner-based RSCP for SC, and you can obtain the signal

distribution of each cell (scramble). If the signals of a cell are widely distributed, even in

the neighbor cells and the cells next to its neighbor cells, the signals of the cell is present,

the cell encounters a cross-cell coverage which might be due to over high site or

improper down tilt of antenna. The cross-cell coverage cells interferes neighbor cells, so

the capacity declines. You can solve the problem by increasing the down tilt of antenna

or lowering the height of antenna. Avoid forming new weak coverage areas while solving

cross-coverage problems. Pay special attention to the adjustment of engineering

parameters which might cause coverage voids. Be conservative that cross-cell coverage is

better than coverage voids if no other choices are available.

Start Assistant. Analyze scanner-based SC for 1st Best Service Cell, and you can obtain

The scramble distribution of the best cell. If multiple best cells changes frequently in an

cell, the cell is a no primary pilot cell, as shown in 0 No primary pilot cell forms due to

the following causes:

o Cross-cell non-seamless coverage due to over high site

o Pilot pollution in some areas

o Coverage voids at edges of coverage areas

Missing neighbor cells, improper parameters of soft handover, cell selection and

reselection cause the consistent between scanner primary pilot cell and camped cell in

idle mode or Best Service Cell in the active set in connection mode of UE. Afteroptimization, the Ec/Io for 1st Best Service Cell of UE.


61/66


- 61 -

Figure 3.12 RSCP for 1st Best Service Cell


62/66


- 62 -

Figure 3.13 Mobile Dual CSF - Run Q

Figure 3.14 Mobile 3G locked Drop Call and CSF - Run Q


63/66


- 63 -

Figure 3.15 Scanner for Sector s of ou r Site

Figure 3.16 Scanner for Sectors of The Firs t Couronne


64/66


- 64 -

CONCLUSION

In this reports we tried to make a manual for pre-optimizing/optimizing WCDMA

networks which contents many cases of problems in WCDMA RF interface. It was

requested by the company which did my internship to keep it as reference for next

optimization projects. And I m Introduced a sample of Incident Reports and KPI report

which I have been delivering those kind of report to the customer (SFR UMTS

OPTIMIZATION) during this project In which I was involved as WCDMA Optimizer

Consultant with Nokia Siemens Networks.

This internship was useful for me since I improved my Skills in Mobile networkOptimization Filed. And based on that I will be able to find a good job opportunity in

wireless planning and optimization filed overall the world.


65/66


- 65 -

REFERENCE

Following process and guidelines have been defined and customised for SFR SolutionPlaque project.

[1] NetAct Planner Configuration Guidelines (P. Cirella)

[2] NetAct Planner Plots/Outputs (P. Cirella)

[3] 3G3G Adjacencies Planning (B. Hani)

[4] 3G2G Adjacencies Planning (B. Hani)

[5] Primary Scrambling Code re-use analysis (B. Hani)

[6] Preliminary Tilt analysis (B. Hani)

[7] Actix Analyser Configuration Guidelines (G. Borges)

[8] Drop Call Analysis (B. Guillard)

[9] Call Set up Failure Analysis (B. Guillard)

[10] Top KPI Analysis (B. Guillard, B. Hani)

[11] 3G3G Adjacencies Optimisation (based on field measurements) (B. Hani)

[12] 3G2G Adjacencies Optimisation (based on field measurements) (B. Hani)

[13] Sleeping Cell Analysis (B. Guillard)

[14] Cell Interference Analysis (B. Guillard)

[15] UTRAN parameter consistency check tools and process (P. Cirella)


66/66


GLOSSARY

NW NetworkCS Circuit SwitchedPS Packet Switched

SC Scrambling CodeSW SoftwareHW HardwareUE User Equipment (aka MS)

Pw Lahiani IMCNE07

Documents

Transcript of Pw Lahiani IMCNE07