VIETTEL TECH TOLOGIES., JSC.

Say it your way

Code No: QT.08.TKTU.01 Effective date: 16/08/2009 Issued time: 01 Pa e: 3/13

OPTIMIZI G KPIs FOR ERICSSON GSM SYSTEM

5. Content . 5.1 Workflow

Responsibility RNO Technical staffs

... , ,.
'~ .

Workflow Data Analysis

~
J

Section Step 1

RNO Technical staffs

r

.. .'f

.'.:..

Specifying th'ebad cells

I
I

Step 2

RNO Technical staffs

Cause Analysis

Step 3

I
RNO Technical staffs

Optimization procedure

I
Step 4
0

KPIs meet the target Yes RNO Technical staffs Report and Update Database

Step 5

VIETTEL TECHNOLOGIES.,
Say it your way

JSC.

Code No: QT.08.TKTU.01 Effective date: 16/0812009 Issued time: 01 Pa e: 3/13

OPTIMIZING KPIs FOR ERICSSON GSM SYSTEM

5. Content . 5.1 Workflow

Responsibility RNO Technical staffs

~: .'

Workflow Data Analysis

Section Step 1

~.

j ..:...

RNO Technical staffs

,

Specifying the bad cells

I
I

Step 2

RNO Technical staffs

Cause Analysis

Step 3

I
RNO Technical staffs

Optimization procedure

I
Step 4 No

KPIs meet the target Yes RNO Technical staffs Report and Update Database

Step 5

L._,-'
~L.-:Z-~

.,,~

r==>

'-"-.........

-"" Say it your way

5.2 Description . 5.2.1
,

VIETTEL TECHNOLOGIES., JSC. OPTIMIZING KPIs FOR ERICSSON GSM SYSTEM

Code No: QT.08.TKTU.01 Effective elate:16/0812009 Issued time: 01 Page: 4/13

CDR Optimization

.:. Step 1:Data analysis Technical staffs get statistic at cell level from ass by days/hours in one or more weeks. Perform analyzing at cell level or site level if necessary. Analyzed data consist of:
s

CDR: Call Drop Rate. TCHDrop:

r ,i

fr:

The total number of dropped TCH.

TDISTA: Total number of Disable Timing Advance. TDISSDL: Total number of Disable Signal strength in Down link. TDISSUL: Total number of Disable Signal strength in Up link. TDISSBL: Total number of Disable Signal strength in Both link. TDISQADL: Total number of Disable Quality in Down link.

TDISQA UL: Total number of Disable Quality in Up link. TDISQABL: Total number of Disable Quality in Both link.

TSUDLOS: Total number of Sudden loss. TCHDrop Other: Total number of Drop TCH with other reason .

:. Step 2: Specifying the bad cells Sort by CDR in descending order then by TCHDrop to specify worst cells (using Excel filter function). The bad cell is defined in section 4 above. Depend on the scope of this proj ect we can pick up from 5 to 10 worst cells to handle. The worst cells are cells that have highest No TCH Drop. E.g. Cell A has 3 calls dropped over 50 calls per day (CDR=6), it is not called bad cell but cell B which has 40 calls dropped over 800 calls (CDR=5) is a bad cells although it has better CDR (see "bad cell" definition) . :. Step 3: Cause analysis. With specified worst cell list, the causes are determined depend on all counters which have been shown in previous part. It consists of 10 counters.

----------------------------

~'f;r~
-c ~

, r~.~

:r~,,-~~
1'itiO'iJ;-To=m

'

VIETTEL TECHNOLOGIES., JSC. OPTIMIZING KPIs FOR ERICSSON GSMSYSTEM

Code No: QT.08.TKTU.01 Effective date: 16/08/2009 Issued time: 01 Page: 5/13

~.~~~~;:;;;;7
Say it your way

If TDISTA is high, TA exceeds the threshold. Possible cause is over-coverage . cell. E.g. serving cell is on the island, on the highland or covers toward the sea. In some cases, cell's height, tilt or azimuth is not suitable.
l :

Ii

If TDISSDL is high, possible causes are: - Narrow coverage, - Feeder fault (VSWR exceeds threshold),

,l'
'

.'
I

- Radio coverage-holes
/

/\.'....

- Missing neighbor or relation parameters are insufficient. If TDISSUL is high, possible causes are: - Over-coverage cell. , - Antenna feeder system fault. If TDISSBL is high, possible causes consist of both TDISSDL and TDISSUL causes. are: If one of TDISQADL or TDISQAUL or TDISQABL is high, possible causes

- Antenna feeder system fault, - Frequencies interference. If TSUDLOS is high, possible causes are: - DTRU, CDU or CXU fault. - Transmission fault. - CONF ACT parameter is not suitable. - Radio coverage holes. If TCNDROP Other is high, there could be BTS or BSC hardware fault.

Note: In some cases, TCNDROP Other is due to high HR traffic . :. Step 4: Optimization procedure
Every cause has corresponding handling procedure as following:

~t=~'l='"
~".~/

.a: "c,r~

__ 1""0/"''-''-

VIETTEL TECHNOLOGIES.,
.v

JSC.

Code No: QT.08.TKTU.01 Effective date: 16/08/2009 Issued time: 01 Page: 6/13

d " ..... ,-"..:....:.;..:1 ..

Say it your way

-

OPTIMIZING KPIs FOR ERICSSON GSM SYSTEM

No.

Possible cause

Handling procedure

Driving test Use Extended range feature. Adjust tilt, coverage Driving test Check\BTS output power Adjust tilt, coverage azimuth to expand cell azimuth to reduce cell

f ,

1. Over-coverage cell -

'.

..
t,,'#"

Optimize neighbors

~I
Jrf

i~

s-

2.

N arrow coverage cell

Optimize neighbors Check connectors (tighten if necessary). Check Tx/Rx cables connectivity (replace ifnecessary). Use BIRD Site Analyzer to check feeders. Check CDU, dTRU cards Driving test. Adjust tilt, coverage. azimuth to optimize cell

3.

VSWR exceeds threshold -

4. Missing neighbor or relation parameters are insufficient

Antenna feeder system fault Frequencies interference DTRU, CDU or CXU fault Transmission fault Radio coverage holes

Increase BTS output power if possible. Propose repeaters or a new site. Driving test Optimize parameters. neighbors and relation

5.

Check feeder order. Check tilt, azimuth, antenna type Driving test Optimize frequencies Swap well-operated card to faulty card. Call NOC for assistance.
6

6.
7.

8.
-

9.

VIETTEL

TECHN OLOGI=E=-:S=-..L' _JS_C_. -+-C_o_de_N_o_:_Q_T_.0_8._TK_T_U_._01-1

Effective date: 16/0812009 Issued time: Pa e: 7/13 01

.....,.-"'~--~-.-_, _ ;r

Say it your way

OPTIMIZING KPIs FOR ERICSSON GSM SYSTEM

. 10.

CONF ACT parameter suitable

IS

not

Adjust CONF ACT parameter.

'------'------------L-

__

.:. Step 5: Report and Update Database

I

In daily optimization: take note any change in "working day" form for monitoring. Any change in antenna, feeder system must be updated in Site full database. In project or short tennoptimization: all adjustments such as changing parameters, adding removing neighbor, changing frequencies, adjusting tilt, azimuth must be updated in "working day". Get KPIs datain one week after optimization and do report. 5.2.2 5.2.2 SDR Optimization

.:. Step 1:Data analysis Technical staffs get statistic at cell level from OSS by days/hours in one or more weeks. Perform analyzing at cell level or site level if necessary. Analyzed data consist of: ' SDR: SDCCH Drop rate. CNDROP: The total number of dropped SDCCH channels in a cell.

CNRELCONG: Number of released connection on SDCCH due to TCH - and transcoder congestion in underlaid and overlaid subcell. CDISTA: Dropped SDCCH connection at excessive Timing Advance (TA).

CDISSS: Dropped SDCCH connection at low signal strength on down - or uplink in underlaid subcell. CDISQA: Dropped SDCCH connection at bad quality down - or uplink per cell in underlaid subcell. SDDRop reason . Other = (SDDrop - except all causes above): SDCCH drop other

Step 2: Specifying the bad cells :. Sort by SDR in descending order then by CNDROP to specify worst cells (using Excel filter function). The bad cell is defmed in section 4 above. Depend on the scope of this project we can pick up from 5 to 10 worst cells to handle. The worst cells are cells that have highest No TCH Drop.

\ \ \

VIETTEL TECHNOLOGIES., JSC.

Say it your way

Code No: QT.08.TKTU.01 Effective date: 16/08/2009 Issued time: 01 Page: 8/13

OPTIMIZING KPIs FOR ERICSSON GSM SYSTEM

-:- Step 3: Cause analysis ~ If CNRELCONG is high, possible cause is TCH congestion.

If CDISTA is high, TA exceeds the threshold. Possible cause is over-coverage cell. E.g. serving cell is on the island, on the highland or covers toward the sea. In some

cases, cell's height, tilt or azimuth is not suitable. ~ If CDrSSS is high, possible cause is: - Narrow coverCj.geor over-coverage. - Feeder fault eVSWR exceeds threshold).
If

'

,'.f

- Radio coverage holes. - Missing neighbor or relation parameters are insufficient. If CDISQA is high, possible cause is: - Antenna feeder system fault. - Frequencies interference. If SDDrop Other is high, possible cause is: - DTRU, CDU or CXU fault. - Transmission fault. - CONF ACT parameter is not suitable. - Radio coverage holes. - BTS or BSC hardware fault. -:- Step 4: Optimization procedure Every cause has corresponding handling procedure as following: No. Possible cause 1. Over-coverage cell Handling procedure Driving test Use Extended range feature. tilt, azimuth to reduce cell

- Adjust coverage -

Optimize neighbors Driving test

8

2.

N arrow coverage cell

..

. / ..tt.__

~
.~
""I.,.;.;

-------_t'

~-fr--ck~I~

VIETTEL TECHNOLOGIES., JSC . OPTIMIZING KPIs FOR ERICSSON GSM SYSTEM -

Code No: QT.08.TKTU.01 Effective date: 16/08/2009 Issued time: 01 Page: 9/13

.,.-... .7--::~

--

Say it your way

(
,
; !

Check BTS output power tilt, azimuth to expand cel1

- Adjust coverage -

Optimize neighbors Check connectors (tighten if necessary).

3.

VSWR exceeds threshold

; ,

Check Tx/Rx cables connectivity (replace if necessary). - Use feeders. BIRD Site Analyzer to check

Check CDU, dTRU cards Driving test. tilt, azimuth to optimize cel1

4.

Radio coverage holes

Adjust coverage. -

Increase BTS output powe~ ifpossible. Propose repeaters or a new site. Driving test neighbors and relation

5.

Missing neighbor or relation parameters are insufficient

Optimize parameters. -

Check feeder order. Check tilt, azimuth, antenna type Driving test Optimize frequencies Swap well-operated card to faulty card.

6.

Antenna feeder system fault

7.

Frequencies interference

8. 9.
10.

DTRU, CDU or CXU fault Transmission fault CONF ACT parameter is not suitable Cal1NOC for assistance. Adjust CONF ACT parameter.

-.-,-

--

Say it your way

OPTIMIZING KPis FOR ERICSSON GSM SYSTEl\1

See 5.2.4

Effective date: 16/08/2009 Issued time: 01 Pa e: 10113

\11.

\ TCH Congestion

~:~ Step 5: Report and Update Database

e

In daily optimization: take note any change in "working day" form for monitoring.

Any change in antenna, feeder system must be updated in Site full database. In project or short term optimization: all adjustments such as changing parameters, adding removing neighbor, changing frequencies, adjusting tilt, azimuth ... must be updated in "working day". Get KPIs data in one week after optimization and do report. 5.2.3 Optimizing HOSR

~:~ Step 1:Data Analysis Technical staffs get statistic: at cell level from ass by days/hours in one cr more weeks. Perform analyzing at cell level or site levelif necessary. Analyzed data consist of: Total HO Attempts Incoming HO Success Rate Outgoing HO Success Rate Total Number of Outgoing HO

~:~ Step 2: Specifying the bad cells Sort by HOSR in ascending order then by Total Number of Outgoing HO to specify worst cells (using Excel filter function). The bad cell is defined in section 4 above. Depend on the scope of this proj ect we can pick up from 5 to 10 worst cells to handle. The worst cells are cells that have highest Total Number of Outgoing RO. ~:~ Step 3: Cause analysis Feeder fault. Missing neighbor or relation parameters are insufficient. Serving cells or neighbor cells hardware fault. Frequencies interference. Target cell is being TCH congestion. Cell border is not optimized.
10

,""''''~'P,~ L~,,"~~

~<!l~iirp=r' ',,./~''''':''7 ""=~-, --

VIETTEL TECHNOLOGIES., JSC. OPTIMIZING KPIs FORERICSSON GSM SYSTEM

Code No: QT08TKTU,01 Effective elate:16/08/2009 Issued time: 01 Page: 11/l3

Say it your way

.:. Step 4: Optimization procedure No.

f

Possible cause Antenna feeder system fault Missing neighbor or relation parameters are insufficient Antenna feeder system fault Frequencies interference e DTRU, CDU or

Handling procedure

1.

Check feeder order. Check tilt, azimuth, antenna type Driving test Optimize parameters. neighbors and relation

2.

3.
4.

Check feeder order. Check tilt, azimuth, antenna type Driving test Optimize frequencies ,
f

5. 6. 7.

cxu.rseu

.,

Swap well-operated card to faulty card. Call NOC for assistance. See 5.2.4

Transmission 'fault TCH Congestion

.:. Step 5: Report and Update Database In daily optimization: take note any change in "working day" form for monitoring. , , Any change in antenna, feeder system must be updated in Site full database. In project or short term optimization: all adjustments such as changing parameters, adding removing neighbor, changing frequencies, adjusting tilt, azimuth must be updated in "working day". Get KPls data in one week after optimization and do report.
5.2.4. TCR Optimization

.:. Step 1: Data analysis Technical staffs get statistic at cell level from OSS by days/hours in one or more weeks. Perform analyzing at cell level or site level if necessary. Analyzed data consist of: TCH Traffic: average traffic per hour TCH Traffic (Peak): rush-hour traffic TCH Traffic HR (Peak): rush-hour HR traffic TCHAssiAtt: Subscriber number of setup call Perceived TCH Congestion (TCR): rush-hour TCH Congestion Rate

Average Number of Available TCH

11

L4~'''''''-:-~ ..., .!'"__ .

~b=~~
~~~

VIETTEL TECHNOLOGIES., JSC. OPTIMIZING KPIs FOR ERICSSON GSM SYSTEM

Code No: QT.08.TKTU.01 Effective date: 16/08/2009 Issued time: 01 Page: 12/13

~~
..,JJ.O-?

;;;

Say it your way

TV Non HR: Non HR TCH Utilization

.:. Step 2: Specifying the bad cells

;.

Sort by TCR in descending order then by TCHAssiAtt

to specify worst cells (using

Excel filter function). The bad cell is defined in section 4 above. Depend on the scope of this project we can pick up from 5 to 10 worst cells to handle. The worst cells are cells that have highest TCHAssiAtt. Step 3: Cause analysis If there is abnormal TCH congestion, possible causes are: - Special events,
.:

f:

- Block card, TRx, TS .

; I

- Adjacent cells have errors.

r-

TCH congestion for a long time (over 4 days per week), possible causes are: - Over-coverage cell. - Increasing traffic. - Missing neighbor.

.:. Step 4: Optimization procedure No. Possible cause 1. Special events Handling procedure Enable HR or increase HR percentage. Adjust cells coverage. Upgrade configuration. Cells load sharing. Use portable sites. Reset card. Check whether cards are faulty, replace if necessary. Check hardware errors Driving test Use Extended range feature. Adjust tilt, azimuth to reduce cell coverage Optimize neighbors
12

2. 3.

Block card, TRx, TS Adjacent cells have errors

4.

Over-coverage cell

.M.:.:.

..~ ~ .,---~,
Say it your way

"'-t-i.ll~l~

~-'

VIETTEL TECHNOLOGIES., JSC .

s-

Code No: QT.08.TKTU.01 Effective date: 16/08/2009 Issued time: 01 Page: 13/13

-'"

OPTIMIZING KPIs FOR ERICSSON GSM SYSTEM

Increasing traffic

Enable HR or increase HR percentage. Upgrade configuration. Cells load sharing. Adjust cells coverage. Propose new sites. Driving test Optimize parameters. neighbors and relation

5.

6. Missing neighbor
r

~
,"

~:~ Step 5: Report and Update Database In daily optimization: take note any change in "working day" form for monitoring. Any change in antenna, feeder system must be updated in Site full database. In project or short term optimization: all adjustments such as changing parameters, adding removing neighbor, changing frequencies, adjusting tilt, azimuth ... must be updated in "working day". Get KPIs data in one week after optimization and do report. 6. Archives No 1. 2. 3. Document Working day CR Optimization result report Stored at Technical staff Technical staff Technical staff Stored time 5 months 5 years 5 years ote

7. Appendices No 1. 2. 3. CRfonn Working day form Optimization result report form Appendix CodeNo
BM.O 1/QT.08. TKTU.O 1 BM.02/QT.08.TKTU.Ol BM.03/QT.08.TKTU.Ol

13