Cluster 2 Densif Optimization Report

7/30/2019 Cluster 2 Densif Optimization Report

http://slidepdf.com/reader/full/cluster-2-densif-optimization-report 1/39

All rights reserved © 2007, Alcatel-LucentOrange UMTS, March 2007

Alcatel-Lucent Team

Cluster Optimisation ReportBucharest Densification - Cluster 2

Introduction Overview

Drive test routes

Presentation of the Zone

Status Before Optimisation Scrambling Codes from Scanner

RSCP from Scanner

EcIo from Scanner

EcNo from Long Call UE Indoor

Optimisation Performed

Main Issues

Explanation

Antenna Modifications Summary Status After Optimisation

Scrambling Codes from Scanner

RSCP from Scanner

EcIo from Scanner

EcNo from Long Call UE Indoor

3G-2G Relationship

EcNo from Short Call UE Indoor 3G – 2G from Short Call UE Indoor

Main Indicators Short Call AMR Indoor Statistics

Main Indicators Summary

RNO Indicators

City Exits

Conclusions




Alcatel-Lucent Team

Cluster 2 Introduction

This study consisted of:

Performing measurements on selected routes.

Analysing these measurements and process some statistics.

Measurement description:

The following equipment was used:

Agilent E6474A (NITRO) V9.3

Mobile: Qualcomm T6275 in indoor daylight configuration (15 dB applied)

Agilent E6455C UMTS receiver (scanner) in outdoor configuration (external antenna)

The mobile configuration used for this report is:

AMR long call in indoor daylight with UE 3G locked.

AMR short call (2’ call + 40” pauses) in indoor daylight with UE in automatic mode.

The scanner has been connected in outdoor configuration for each drive.

All the sites were in commercial traffic during the optimisation.




Alcatel-Lucent Team

Cluster 2:Overview

Note: new sites are marked in red

Cluster 2 is composed of 8 old sites (all macro) and 11 new sites (10 macro + 1 micro). It’s

neighbours are clusters 1,3,5, and 6.




Alcatel-Lucent Team

Cluster 2:Drive Test Route

Comments :

The drive goes through each main road of the cluster and through each cell’s area of service.

The total length of the test drive route is about 130 km.




Alcatel-Lucent Team

Cluster 2 Results

Network StatusBefore the Optimisation




Alcatel-Lucent Team

Cluster 2 Results:Scrambling Codes from Scanner

Comments :

- a problem of crossed feeders was found and fixed on site BU_185

- some zones have problems of best-servers

- some cells have large coverage and may interfere




Alcatel-Lucent Team

Cluster 2 Results:RSCP from Scanner

Comments :

There are zones with low coverage. Specific investigations need to be done in order to

avoid as much as possible having “exclusion zones”.




Alcatel-Lucent Team

Cluster 2 Results:RSCP from Scanner Distribution




Alcatel-Lucent Team

Cluster 2 Results:EcIo from Scanner Outdoor

Comments :

Areas with low quality are revealed with this map.




Alcatel-Lucent Team

Cluster 2 Results:EcIo from Scanner Distribution




Alcatel-Lucent Team

Cluster 2 Results:EcNo from the Long Call UE Indoor

Comments :

The map above presents the worst zones to optimiseze (red points).




Alcatel-Lucent Team

Cluster 2 Results:EcNo from the Long Call UE Distribution




Alcatel-Lucent Team

Cluster 2 Remarks

Scrambling code analysis :

All sites were on air during the first drive except BI0661.

There are areas with best server problems, especially around new sites and sites that were late

on the initial optimisation phase.

RSCP analysis :

The RSCP level improved a lot in this Cluster (former Cluster 5) by the adding of the new sites.

However some sectors will have to be down-tilted in order to achieve a acceptable balance

between good coverage and good signal quality.

EcIo and EcNo analysis :

EcIo from the Scanner should be the reference for the interference optimisation as the EcNo from

he UEs can be influenced by missing neighbours or abnormal phone behaviour.

After the first drive Cluster 2 presented an overall good EcIo. Still areas exist with low EcIo level

mostly due to best server problems. Those areas have been considered for further investigations.

EcNo level is not very good. In most cases it reflects the bad EcIo, but in other the low level is

due to missing neighbours.




Alcatel-Lucent Team

Cluster 2

Network StatusOptimisation Performed




Alcatel-Lucent Team

Optimisation performed:Main issues

Red circles represent areas of bad quality that need to be optimised.

12

3

4




Alcatel-Lucent Team

Optimisation performed: Area 1

Sectors BU_185_2, BU_185_3 and BU_121_3 were chosen to become best servers in this area.

All the other overshooting sectors were down-tilted. The following optimisations were performed:

up-tilt BU_185_2: from 4o

to 3o

up-tilt BU_185_3: from 5o to 3o

down-tilt BI_279_3: from 6o to 10o



down-tilt BU_201_2: from 6o to 10o and reduce it’s CPICH power by 5dB

down-tilt BU_448_1: from 3o to 7o

down-tilt BU_448_2: from 4o to 6o

The modifications produced the expected result and the EcIo improved a lot. Further improvementwould have been possible if sector BU_201_1 could have been down-tilted as well. This was not

possible however due to lost of coverage in other areas.

Case 1 EcIo Case 1 SC

Details:

This is an area with bad EcIo caused by the lack of a best server and the overshooting

neighbouring sites.




Alcatel-Lucent Team


The following modifications were performed:

- down-tilt BU_595_3: from 6o to 8o (Cluster 5)


- down-tilt BU_369_3: from 9o to 10o

The bad quality problem was solved.


Details:

BU_279_2 is the best server in this area, but it is interfered by overshooting sectors.




Alcatel-Lucent Team


Sectors BU_144_3 and BI_550_3 were chosen to act as best servers. Several other

sectors were down-tilted:


- down-tilt BI_550_3: from 1o to 4o (Cluster 3)



- down-tilt BI_688_1: from 1o to 7o


After these modifications were made the quality improved a lot.


Details:

This area dose not have a best server and interference is produced by overshooting sectors.




Alcatel-Lucent Team


The following optimisations were performed:











The EcIo level improved after the optimisation.


Details:

This area was initially covered by sector BI_448_3 with insufficient RSCP level. Sector BI_143_2

had to be added to improve coverage. Some overshooting sectors were down-tilted.




Alcatel-Lucent Team

Optimisation Performed: Antenna Modifications Summary (1)

SITE DATA BEFORE OPTIMISATION AFTER OPTIMISATION Sector Sector Name Electrical Tilt Azimuth Electrical Tilt Azimuth Comments

1 BI_0128_U_1 4 40 7 40 Case 4 2 BI_0128_U_2 4 160 8 160 3 BI_0128_U_3 2 280 7 280 Case 4 1 BI_0143_U_1 4 40 9 40 2 BI_0143_U_2 4 160 7 160 Case 4 3 BI_0143_U_3 2 280 4 280 1 BI_0279_U_1 7 40 7 40 2 BI_0279_U_2 7 155 7 155 3 BI_0279_U_3 6 270 10 270 Case 1 1 BI_0296_U_1 4 40 7 40 2 BI_0296_U_2 5 160 9 160 3 BI_0296_U_3 6 280 10 280 1 BI_0368_U_1 7 85 7 85 2 BI_0368_U_2 6 190 6 190 3 BI_0368_U_3 5 310 5 310 1 BI_0371_U_1 3 40 8 40 2 BI_0371_U_2 4 160 7 160 3 BI_0371_U_3 4 280 7 280 Case 3 1 BI_0661_U_1 2 40 7 40 Case 1 2 BI_0661_U_2 2 160 6 160 Case 1 3 BI_0661_U_3 2 280 5 280 1 BI_0674_U_1 2 50 6 50 Case 4 2 BI_0674_U_2 2 160 5 160 3 BI_0674_U_3 3 290 6 290 1 BI_0688_U_1 1 55 7 55 Case 3 2 BI_0688_U_2 3 160 6 160 Case 4 3 BI_0688_U_3 1 300 5 300 DN7 1 BI_0933_U_1 4 50 4 50 2 BI_0933_U_2 3 180 3 180 3 BI_0933_U_3 4 280 7 280 Case 4




Alcatel-Lucent Team

Optimisation Performed: Antenna Modifications Summary (2)

Comments :

Average electrical tilt on Cluster 2:

- Before the optimisation: 4.37°

- After the optimisation: 6.48°

1 BU_121_U_1 4 40 4 40 2 BU_121_U_2 8 170 6 170 3 BU_121_U_3 4 280 4 280 1 BU_144_U_1 3 45 6 45 Case 3 2 BU_144_U_2 4 160 7 160 3 BU_144_U_3 3 280 4 280 Case 3 1 BU_152_U_1 6 40 6 40 2 BU_152_U_2 5 160 5 160 3 BU_152_U_3 6 290 3 290 1 BU_163_U_1 7 30 7 30 2 BU_163_U_2 6 150 6 150 3 BU_163_U_3 7 270 7 270 1 BU_185_U_1 4 40 4 40 2 BU_185_U_2 4 160 3 160 Case 1 3 BU_185_U_3 5 280 3 280 Case 1 1 BU_201_U_1 2 40 3 40 2 BU_201_U_2 6 160 10 160 Case 1 3 BU_201_U_3 4 275 8 275 Case 4 1 BU_369_U_1 8 55 8 55 2 BU_369_U_2 8 160 8 160 3 BU_369_U_3 9 280 10 280 Case 2 1 BI_448_U_1 3 60 7 60 Case 1 2 BI_448_U_2 4 160 6 160 Case 1 3 BI_448_U_3 3 280 6 280 Case 4




Alcatel-Lucent Team

Cluster 2 Results

Network Status After the Optimisation




Alcatel-Lucent Team

Cluster 2 Results:Scrambling Codes from Scanner Outdoor

Comments :

Zones with multi-servers reduced compared to the first drive test.




Alcatel-Lucent Team

Cluster 2 Results:RSCP from Scanner Outdoor

Comments :

Even if some sectors had been down-tilted to improve the quality the RSCP level is

good in most areas.




Alcatel-Lucent Team

Cluster 2 Results:RSCP from Scanner Outdoor Distribution




Alcatel-Lucent Team

Cluster 2 Results:EcIo from Scanner Outdoor

Comments :

EcIo improved in all the cases considered for optimisation.




Alcatel-Lucent Team

Cluster 2 Results:EcIo from Scanner Outdoor Distribution




Alcatel-Lucent Team

Cluster 2 Results:EcNo from the Long Call UE Indoor

Comments :The EcNo improved after the optimisation. We can see on the map the zones where

problems might happen (red points).




Alcatel-Lucent Team

Cluster 2 Results:EcNo from the Long Call UE Distribution




Alcatel-Lucent Team

Cluster 2 Results:Remarks

Scrambling Code Analysis :

All sites were on air during the final drive.

Most of the best server problems have been solved.

RSCP Analysis :

Some sectors had to be down-tilted which led to a slight decrease in the RSCP level. Still the

RSCP level is sufficient all over the Cluster.

EcIo and EcNo Analysis :

The EcIo improved in the areas considered for optimisation. Very few zones remain with low

quality level.

The EcNo improved as well, but in at least two areas one of the UEs recorded a very bad EcNo

compared to the other UE or to the EcIo from the Scanner. This influenced the overall statistics.Some examples are given below:

Case 1: MS1 Case 1: MS2

Case 2: MS1 Case 2: MS2




Alcatel-Lucent Team

Cluster 2 Results

Network Status3G – 2G Relationship




Alcatel-Lucent Team

Cluster 2 Results:EcNo from Short Call UE Indoor

Comments :

We can see on this detailed map the zones where compress-mode (Event 2d_cm) andHHOs to GSM (Event 3a) might happen (black and red dots).




Alcatel-Lucent Team

Cluster 2 Results:3G-2G from Short Call UE Indoor

Results :

-4 3G-2G handovers during the final drive test (areas marked with green circles); one HHOwas not detected by Actix due to missing HO command message)

- in the area marked with a red circle MS2 lost the 3G signal unexpectedly due to a hardware

problem and initiated a call on the 2G layer (the quality recorded by both MS1 and theScanner is very good in that area, about -3dB)

- 95% of the drive was performed on the 3G layer




Alcatel-Lucent Team

Cluster 2 Results

Network StatusMain Indicators




Alcatel-Lucent Team

Cluster 2 Results:Short Call AMR Indoor with Load Statistics

Statistics before optimisation :

Statistics after optimisation :

No Setup

Fail

(Actix) No Drop

(Actix) No Setup

Fail real No Drop

real CSSR

real CSR

real CDR

real No

Attempts

2 5 3 0 96.84% 96.84% 0.00% 95

No Setup

Fail

(Actix) No Drop

(Actix) No Setup

Fail real No Drop

real CSSR

real CSR

real CDR

real No

Attempts

19 6 17 4 85.83% 82.50% 3.88% 120




Alcatel-Lucent Team

Cluster 2 Results:Main Indicators Summary

Call Setup Success Rate analysis:

Actix found 19 Access Failures for the first drive and 2 during the second but some of them are

wrong. Actix didn’t considered some real Access Failures but has counted some other. A detailed

analysis is given below:

For the first drive:

- 17 real failures were found:

• 2 due to radio problems

• 5 due to the “SignallingConnectionRelease” problem

• 7 due to problems with the test line (Requested Circuit Not Available)

• 2 due to network errors

• 1 due to “RRCConnectionReject” message with cause “Congestion”

- 6 fake failures found by Actix due to missing “Connect” messages

For the second drive:

- 2 fake fails found by Actix due to missing “Connect” messages

- 3 real fails due to network problems (not found by Actix)

No fail occurred due to radio problems.

Call Drop Analysis after Investigation:

For the first drive, Actix counted 6 call drops (only 4 turned out to be real due to radio causes).

For the second drive Actix found 5 drops. All of them were fake, 4 due to missing “Disconnect”

message and one due to missing HHO command message.

No real call drop occurred on the final drive.




Alcatel-Lucent Team

Cluster 2 Results:RNO Indicators

Daily_Call_Drop_IuCS_release

010

20

30

40

50

60

70

80

03/17/2007 03/18/2007 03/19/2007 03/20/2007 03/21/2007

0

0.05

0.1

0.15

0.2

0.25

0.3

0.35

QCDCIUCS_N

QCDCIUCS_R

03/17/2007 03/18/2007 03/19/2007 03/20/2007 03/21/2007 0.13 0.31 0.25 0.23 0.28

Daily IuCS Call Drop Rate from 17.03 to 21.03

Call Setup Success Rate

05

10152025

3035404550556065707580859095

100

03/17/2007 03/18/2007 03/19/2007 03/20/2007 03/21/2007

%

03/17/2007 03/18/2007 03/19/2007 03/20/2007 03/21/2007 RAB Setup Success Rate 99.10% 98.95% 98.37% 99.14% 99% RRC Setup Success Rate 97.64% 97.91% 97.27% 97.70% 73.46% Call Setup Success Rate 96.76% 96.88% 95.68% 96.85% 72.72%

Call Setup Success Rate (RAB Setup Success * RRC Setup Success) from 17.03 to 21.03




Alcatel-Lucent Team

Cluster 2 Results:City Exits

Two City Exits were considered for investigation in Cluster 2:

• DN1A to Mogosoaia

• DN7 to to Chitila

In both cases the call was successfully handed over to GSM at the edge of 3G coverage.

City Exit on DN1A City Exit on DN7



Cluster 2 Results:Conclusions

Results:

The tables on previous pages show that the main indicators are good on Cluster 2.

The coverage on this Cluster improved a lot after this densification phase (11 new sites were

added). The RSCP level is very good at street level all over the cluster. Still, new sites may

be considered in the future to improve the deep indoor coverage needed especially for static

users which require high data rate services.The quality improved after the optimisation. In the very few places left with bad quality (blow

-12dB), the calls were successfully handed over to the GSM layer during the drive tests.

Call Drop Rate and Access Success Rate:

As seen from the drive test and the RNO exports the Call Drop and Call Access indicators

are good on this Cluster.

The Call Drop Rate during the final drive test was 0, while the RNO recorded a Drop Ratebelow 0.3% on IuCS after the final optimisations were completed.

3 Access Fails occurred on the final drive test, but these were not due to radio problems.

The Access Success Rate from the RNO (calculated as the RRC Connection Success

multiplied by the RAB Setup Success) is above 95%. The lower rate on 21.03 was due to

the fact that site BU_185 had a RRC Connection Success problem. This problem was

solved.

Main recommendations or task to work on:

This report concludes the Densification Phase of Cluster 2.

Further optimisation campaigns should be conducted on denser routes in order to fine tune

the antenna parameters on the sites even more.

RNO parameters should be observed in the future and modifications should be considered

on sites that will present lower KPIs.

Cluster 2 Densif Optimization Report

Documents

Transcript of Cluster 2 Densif Optimization Report