Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1 (136)
2 (136)
The information in this document is subject to change without notice and describes only the product defined in the introduction of
this documentation. This document is intended for the use of Nokia Siemens Networks' customers only for the purposes of the
agreement under which the document is submitted, and no part of it may be reproduced or transmitted iin any form or means
without the prior written permission of Nokia Siemens Networks. The document has been prepared to be used by
professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens
Networks welcomes customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned
hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia
Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the
instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if
necessary, explain issues which may not be covered by the document.
Nokia Siemens Networks' liability for any errors in the document is limited to the documentary correction of errors. Nokia
Siemens Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR
ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use
of this document or the information in it.
This document and the product it describes are considered protected by copyright according to the applicable laws.
NOKIA SIEMENS logo is a registered trademark of Nokia Siemens Corporation.
Other product names mentioned in this document may be trademarks of their respective companies, and they are
mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2007. All rights reserved
3 (136)
ACKNOWLEDGEMENTS:It was indeed quite difficult to acknowledge the entire crowd who had a major influence on
the conception and fruition of this document.To the best of my ability I shall attempt to do so.I would like
to thank Pradeep Chattikal, Prashanth k, Vikrant Arun Dolas, Muthu Krushnan and Rajiv Mohan Gandhi
from Nokia Siemens Network. (India) for their technical support and providing valuable sujections during
the course of work.I would also like to thank Avnish Kumar from NSN, contributing for IBS solutions for
Idea Delhi Network.
My gratitude also to grand me and my team an opportunity of testing several queries and
features on Idea cellular Delhi Network and also on some of the Hutch Networks in India.
Stenin.N.P
Networks, and Service Optimization.
Nokia Siemens Network, India.
4 (136)
Table of contents:i.
ii.
iii.
1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
2.
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2.11
2.12
3
3.1
3.2
3.3
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.6
3.6.1
3.6.2
3.6.3
3.7
3.7.1
3.7.2
3.7.3
3.7.4
3.8
3.8.1
3.8.2
3.8.3
3.8.4
4
4.1
4.2
4.3
4.4
4.5
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
6
6.1
5 (136)
9
10
6 (136)
6.1.1
Descreption ...104
6.1.2
Statistical Analysis ....105
6.1.3
Field Test Trial ..106
6.1.4
Script...106
5.1.5
Performance Plot ..106
6.2
Alarm Number 7601 ..107
6.2.1
Description ...108
6.2.2
Fault Reasons with solutions ....108
6.2.3
Description of supplementry Information .109
6.3.
Alarm Number 7738 ....109
6.3.1
Description ....109
6.3.2
Description of supplementry Information .110
6.3.3
Field Trial ..110
6.4
Alarm Number 7604 .114
6.4.1
Alarm Description ....114
6.4.2
Fault Reasons and Solutions .114
6.4.3
Supplementary Information..115
6.5
Alarm Number 7744 .116
6.5.1
Alarm Description 116
6.5.2
Supplementary Information..115
6.6
Alarm Number 7606 ....117
6.6.1
Alarm Description ...117
6.6.2
Fault Reasons and Solutions ..117
Drive test Analysis.118
7.1
Check List for Cell site.118
7.2
Basic Information..118
7.3
Idle Mode Information..118
7.4
Dedicated Information..119
7.5
Handover Information...119
7.6
Data Drive Information GPRS.119
7.7
Radio Efficacy Check120
7.8
Benchmarking Drive using Swis Qual 7.5..121
7.8.1
Drive Test Session ...122
7.8.2
Data Service Drive test Measurement ..122
7.8.3
Executive summary Voice ..123
7.8.4
Executive summary Data 123
7.8.5
Mobile service Quality in Nutshell .113
Voice Service Quality Lpot. ..124
Data Service Performance Plot 125
Summerised KPI Comparision .126
Nokia Macros .....128
8.1
Nokai Macro Dictionary for ND ..128
8.2
Nokia Macro Dictionary for MML ...129
8.3
Details of Nokia Macros ..129
Summary of Idea Delhi Optimization....130
Network Performance Plots .131
APPENDIX..137
7 (136)
i. INTRODUCTION:The heigh marketing demand for better efficacy in the field of Optimization with less of
investement on the cellular Network has lead to conduct several Test Trials, which are summerised into
one single document. The test was done on technologies like GSM, GPRS and EDGE for both Voice
and Data. The document also covers some of the critical Alarms and the way forward to handle these
Alarms. Some of the methods that were adopted to achieve good Key performance Indicater were also
covered for performance enhancement of Cellular Network.
1.
8 (136)
Voice Audit
Network Audit for GSM Network carried out with analysis of different Nokia ND Reports and OSS
Extracted statistics .The Voice Audit gives an understanding of the GSM Network and the discrepancies
in the Network, which can be corrected on time to time basis for better Efficacy of Network Operation.
1.1
This gives details of the Network taken for Voice Audit as listed below as for Idea Cellular
Delhi (India).
Observations Idea_Cellular-Delhi:
Total Cells in the Network
3563
Total Sites:Metro=
Total Sites: Ultra=
128
1234
1362
10569
S 11.5 CD 6.0
S 11.5 CD 6.0
OSS 4 CD 3.0
M12 CD 3.0
9 (136)
1.2
10 (136)
Number of cells which are utilized more than 90% in Idea cellular Delhi Network tend towards a percentage of 44.
And there are also 6% of cells that are Under Utilized.
Utilization of cells can be planned appropriately for Idea Cellular Delhi Network.
Total Operational Cells in the Network 2993 for Idea Cellular DELHI Circle
11 (136)
1.3
Spectrum Loading.
1.4
Observations:
:22
:5 BSC ( BSC 2i ) & 17 BSC ( BSC 3i)
:S11.5 CD 6.0
12 (136)
1.5
13 (136)
4658584
1.78
7.56%
1.78%
NOTE: There seems a lot of SDCCH Utilized for Location Updates, for which The LAC ReDimension will be carried out appropriately.
NOTE: The major share of the drop at the SDCCH is seen due to T3101 Expiry and also at
the Abis.
1.6
There are 26 LAC Created under 3 MSC. Cells planned under different LAC are as shown
below.
14 (136)
Comment:
The cells distributed under Different LAC are seen uneven.As some of the LAC has large
number of cells defined under them where as some other have few cells defined
The distribution can be done according to study made with respect to Paging Load and Location
update.Possibility of site rehoming, etc.LAC Distributed for Idea Cellular DELHI is as shown
below.
15 (136)
16 (136)
LAD redimensioning requirement for the following cells for Idea Cellular Delhi:
The cell listed in the attachment requires LAC Changes appropriately, to reduce signalling Load in the
Network.
17 (136)
Recommendation:
From the cause for Handover Network wide.The power budget Handover can be further
improved from a value of 29.31%.
Interfering frequency requires correction appropriately to reduce the Handover due to
interference as shown there is 14.66 % Ho, due to DL Interference.
NOTE: The most critical is the DL Interference of 14.66 demanding correction immediately.
1.8
18 (136)
Frequency Utilization:
NOTE;The BCCH Plan for Idea Cellular Delhi shows the difference between the most commonly used BCCH
Frequency and the Least BCCH Frequency used in the Network.
1.9
With appropriate Nokia ND reports the following Discrepancies were found when Network Audit for
Voice was conducted for Idea Cellular Delhi Netwrork.
SDCCH Redimensioning Requirement.
NOTE- SDCCH RE-Dimensioning Requiremnt for Cells having High SDCCH Blocking (Considering that the cells do not
have time slots Blocked carrying SDCCH denoted by Alarm 7745) .Taking Optimization of SDCCH further, we can have
Dynamic SDCCH also switch on for better efficacy of SDCCH.
19 (136)
Basic Parameter Discrepancy:Some of the Discrepancies in the parameters were audited for better operation of
Cells in the Network.The data taken for audit was from OSS Statistics, ND Reports and BSS Dump.
The above discrepancy includes Prioritising of Cells for their Voice calls, Cells which
are barred from Operations, Call Re establishment requirements, Hysterisis papameter, Temporary
Offsets, Penality time requirements, Power controm Parameter enabled, and Handover papameters.
The above parameter describes the Band Requirement, Transmit power requirement, Access
grand requirement , Periodic MS location update, Discontinious Transmission, and power budjet
parameters.
The above table shows the RTSL which are not in use requiring Checks for those TRX.
20 (136)
AMR Parameter Discrepancy:The Discrepancies in the AMR Parameters are listed in the table for Idea Cellular Network.
Neighbor Discrepancies:The Neighbor Discrepancies for Idea Cellular Network, showing cells which are not
synchronised.
Cells which required Neighbours to be added and as well as to be deleted are done appropriately
with the analysis of Neighbor Stats taking help of the percentage of Handover attempts for these
perticular cells .
21 (136)
Path Imbalance:Path imbalance in the cells of the network can be analysed with the help of Nokia ND report 183.This
report can be used to find the Transmitted power inbalance, the sensitivity of both MS and Basae station,
High VSWR in these cells.
Note:-For Voltage Standing Wave Ratio (VSWR) the alarm threshold should be set to appropriate value
in advance to a value of about 1.2. So as to indicate if the value shoots more than the set value of 1.2.
The positive value indicates the Imbalance is in the Transmitted Path, and the Negative value
indicates the Imbalance in the Reception path with respect to the Base Transcive Station.
NOTE-Cells having Path Imbalance requires checks like Cable, Transmit Power , Connectors , VSWR
etc checked for these cells appropriately
Ghost SDCCH Analysis:The Phantom or Ghost SDCCH is due to reasons like Interference Both External and internal
Interference in the Network. Parameter Changes requirement for Ghost SDCCH Establishment- Idea
Cellular Delhi. By fine tuning changing the training Sequence the Ghost SDCCH can be reduced to an
extend in the cell site.
22 (136)
The Training sequence changes required for Non BCCH TRX Only as Listed in the table above
Note: There should not be any changes made in the Training Sequence for BCCH Trx as, it would be
difficult for a call to macheure, if the Training sequence differes from the BCC on the BCCH TRX of a
Sector, then there would be difficulty in the calls getting mechured.
2.
23 (136)
Data Audit
Network Audit for Data (GPRS / EDGE) Network carried out with analysis of different Nokia ND
Reports and OSS Extracted statistics .The Data Audit gives an understanding of the Cellular Network
and the discrepancies in the Network related to Data, which can be corrected on time to time basis for
better Efficacy of Network Operation for smooth and agreed Data Throughput and efficacy.
2.1
2.2
MSC:
5
BSC:
22
Sites:
1393
Cells:
4038
TRX:
8517
Spectrum:
6.2 MHz (GSM 900)
Radio Network Capacity (Erlang):
Radio Network Capacity (Erlang) - Data:
VLR Subscribers (Attached):
Registered GPRS Subscribers:
Total BBH Traffic (Erlang):
Total NBH Traffic (Erlang):
36008.65
2512.35
945594
16450
36358
33623
The configuration settings helps to explain the total cells with GPRS and EGPRS
Enabled cells in the Network, and of the enabled cells with details of the Dedicated and Default
(Switchable) timeslots availability.
GPRS Enabled
Yes
No
EGPRS Enabled
Yes
No
GPRS TRX
1 TRX
2 TRX
3 TRX
4 TRX
3285
789 (to be verified with MML commands)
750
3324
3875
174
22
4
CDED (%)
0 Ts:
1 Ts:
2 Ts:
3 Ts:
CDEF (%)
0 Ts:
1 Ts:
2 Ts:
3 Ts:
4 Ts:
6 Ts:
9 Ts:
2.3
24 (136)
1418 cells
2610 cells
33 cells
13 cells
901 cells
2041 cells
165 cells
35 cells
919 cells
9 cells
4 cells
MML default:
MML default:
Description:
Related command(s):
Note:
25 (136)
Total cells:
0.7:
4072 cells
0:
2 cells
Recommended Value: 1
Gamma
GSM reference:
Q3 name:
Gamma
Modification:
Online
Range:
MML default:
Description:
With this parameter you describe the binary representation of the parameter ch
for MS output power control.
Related
command(s):
Note:
OPTIONAL (GPRS)
This Network has the following settings as listed below.
Value
Total Cells.
18:
26:
34:
3812 cells
6 cells
256 cells
Recommended Value: 28
26 (136)
AGCH
Access Grant Channel requirement for the Network depends on the kind of Mode.
That is Combined and Non Combined Mode.
If combined mode ie (BCCH + SDCCH) then the requirement for AGCH is 1, and is Non
Combined mode ie separate BCCH and Separate SDCCH, then AGCH requirement is 2.
2 cells
4072 cells
Recommended Value: 2
The Recommended value is taken as 2, since most of the cells in the GSM
network are found to be with Combined Mode.
BFG / TRP:
No ref.
Q3 name:
preferBCCHfreqGPRS2
Modification:
You can modify the BFG parameter online when the value of the GENA
parameter is N. If the value of the GENA parameter is Y, you must lock the
BTS before modifying the BFG parameter.
Range:
02
MML default:
Description:
With this parameter you define whether the BCCH TRX or other TRXs are
preferred in GPRS channel allocation.
Related
command(s):
EQV, EQO
No ref.
27 (136)
Q3 name:
trxPriorityInTCHAlloc
Modification:
Online
Range:
03
MML default:
Description:
With this parameter you define whether the BCCH TRX or other TRXs
are preferred in traffic channel allocation.
Related
command(s):
EQM, EQO
IFP
Idle mode signal strength filter period (IFP)
GSM reference:
Q3 name:
TAvgW
Modification:
Online
Range:
0...25
MML default:
Description:
With this parameter you control the signal strength filter period for power control
in the packet idle mode.
Related
command(s):
Note:
OPTIONAL (GPRS)
28 (136)
TFP
Q3 name:
TAvgT
Modification:
Online
Range:
0...25
MML default:
13
Description:
With this parameter you control the signal strength filter period for power
control in the packet transfer mode.
Related
command(s):
Note:
OPTIONAL (GPRS)
This Network has the following settings as listed below.
Value
Total Cells.
0:
4065 cells
1:
2 cells
0:
7 cells
Recommended Value: 13
2.4
29 (136)
30 (136)
Few NSEIs have exceeded the capacity (64 cells) as highlighted in the circled regions
Many NSEIs have exceeded the recommended threshold (48 cells) as highlighted in the circled regions,
while some have very few cells associated to them.
PCU re-dimensioning to be done on priority to improve performance and also ensure better
utilisation of PCU resources.
2.5
GSM 04.60
Q3 name:
Rac
Modification:
Online
2.6
31 (136)
Range:
0.. 255
MML default:
255
Description:
With this parameter you define the routing area code in the adjacent cell. In the
adjacent cell creation if this parameter is not given and the SEG and the adjacent
cell are in the same BSS, the value of this parameter is copied from the SEG.
Related
command(s):
Note:
OPTIONAL (GPRS)
Few sites have different LACs even amongst their cells as highlighted in the circled regions.
This needs to be rectified on priority.
2.7
32 (136)
Territory Upgrade.
PCU Congestion.
CS Traffic.
33 (136)
2500
2000
# Cells 1500
1000
500
65
0
DLMultislot Blocking%
10
< 1%
>= 1%< 5%
2911
65
10
Blocking %
2
>= 20%
2
DLMultislot Blocking%
34 (136)
DL Multislot Blocking
Low Allocated Success Rate.
35 (136)
High Blocking:
900
869
800
700
590
600
500
# Cells
395
400
300
200
148
120
100
0
DL Mult islot Allocat ion Success %
>= 99%
870
120
395
Blocking %
< 60%
590
148
DL Multislot Allocation
Success %
Majority of the requests are not entirely denied, but served with lesser Tsl.
2.9
Sleeping Cells
Two main categories
Sleeping GPRS (filter N0) ava_71
No data activity (filter N1) ava_72
Sleeping GPRS (ava_71) further divided into the following sub-categories
Zero TSL (N10)
Bouncing GPRS (N20)
High UL TBF Establishment Fail (N30)
UL no DL (N40)
High DL TBF Fail (N50)
36 (136)
37 (136)
2.10
EDAP Congestion
TBFs wit hout EDAP DL
1400
1225
1200
1000
915
800
# Cells
600
518
390
400
222
153
200
118
66
0
TBFs w it hout EDAP DL
49
34
10
153
66
518
222
118
1225
390
915
BSC
120000
100000
88265
80000
# Cells
61714
60000
40000
41350
36097
28013
27838
20000
0
T B F s wit h inadeq. ED A P D L
13421 13946
13658
20573
17472
12775
12844
15
18
44
79
10
41350
22574
13658
88265
13421
13946
12775
17472
28013
11994
10453
18
72
46
11
10
27838
12844
10453
36097
27739
20573
119929
27971
11994
61714
BSC
27971
27739
22574
38 (136)
39 (136)
Limited by PCU
2.11
Gb Utilization
Most of the Gb links are with CIR of either 64k or 128k
Certain links have crossed their threshold levels or are nearing them as
highlighted in the circular regions
Recommended to increase the capacity on these links
2.12
40 (136)
Recommendations:
3.
41 (136)
Parameter Audit.
Different Nokia Parameters are audited for their better Performnace with the Help of statistics
analysis and Field Test Trials.
3.1
Transcoder Optimization.
XCDR Optimization
(ITCF). Performance Report
Idea Cellular Delhi
23rd-July-2007
Stenin.N.P
Networks, and Service Optimipation.
Nokia.India.
For internal use
1
Nokia Siemens Networks
42 (136)
Explanation:
After a speech path connection has been established between the BTS and the TC, they try to align
with each other to enable speech coding both in uplink and downlink directions. If the alignment procedure
fails, speech decoding also fails and speech is no longer audible. In this case, the BTS sends
CONNECTION_FAILURE_INDICATION message to the BSC. The BSC requests for a clearing and then
releases the resources connected to the call. The cause field in this failure indication message is "REMOTE
TRANSCODER FAIL
When more aggressive HR is introduced, due to the interference in the air interface and signaling
messages can be lost. Re-sending the messages one or more times can lengthen the call establishment
dramatically and this might lead to trigger of REMOTE TRANSCODE FAIL counters.
IT C F P a r a m e te r fro m M M L : W ith th e h e lp o f m m l c o m m a n d Z E E O :A L L , th e s ta tu s o f IT C F c a n b e fo u n d o n th e B S C L e v e l.
F or in t er n a l u s e
1
N o k ia S ie m e n s N e t w o r k s
P r es e n t a tio n / A u t h o r / D a t e
P e r fo r m a n c e P lo t B D 0 1 7 :
F o r in t e r n a l u s e
4
N o k ia S ie m e n s N e t w o r k s
P r e s e n t a tio n / A u t h o r / D a t e
43 (136)
P e r fo r m a n c e P lo t B D 0 1 9 :
F o r in t e r n a l u s e
5
N o k ia S ie m e n s N e t w o r k s
P r e s e n t a tio n / A u t h o r / D a t e
P e r f o r m a n c e P lo t B D 0 1 8 :
F o r in t e r n a l u s e
6
N o k ia S ie m e n s N e t w o r k s
P r e s e n t a tio n / A u t h o r / D a t e
44 (136)
45 (136)
P e r fo r m a n c e P lo t B D 0 2 0 :
F o r in t e r n a l u s e
7
N o k ia S ie m e n s N e tw o r k s
P r e s e n ta tio n / A u th o r / D a te
F or internal us e
10
N okia Siem ens N etworks
Thus there was improvement on TCH Drop which was due to Transcoder failure, and there by enhancing
TCH Drop Call Performance on the Network Level.
3.2
Parameter
Optimization Performance Reprot.
Rx_Lev_Min_cell (SL)
Idea Cellular Delhi
31st-July-2007
Stenin N.P
Nokia Siemens Network.
For internal use
1
Nokia Siemens Networks
46 (136)
47 (136)
Rx_Level_Min_Cell (SL) ,Optimization Performance :Rx_Level_Min_Cell (SL) Parameters was fine tuned for Four BSCs (BSC02 ,BSC05
,BSC15,BSC12) for Idea Cellular Delhi Network.
Description :Rx_Lev_Min_Cell (SL):This Parameter defines the minimum signal level of an adjacent cell when an handover is allowed
to the Neighboring cell.
Range: -110 to -47 dBm.
Default: -100 dBm. Nokia Tested (-92dBm)
Note : The Value for SL can be Fine tuned to a value of -96dBm for Border Cells in the network for better
Performance Enhancement.
Expected Improvement:- With this Parameter fine tuning there should be improvement in
Handover success Rate and also Enhancement in drop Call which were dropping due to
handover.
48 (136)
H a n d o v e r Im p r o v e m e n t (B S C 0 5 ): -
B S C - 0 5 - H O S R IM P R O V E M E N T
10000
6
5
1000
4
ERL
d a te o f im p lim e n ta tio n
100
3
2
10
1
1
-0
-1
6
7
-0
-1
7
7
-0
-1
5
7
-0
-1
8
7
-0
-1
9
7
-0
-2
0
7
-2
-0
T C H T r a f f ic ( E lr )
F o r in t e r n a l u s e
3
N o k ia S ie m e n s N e tw o r k s
1
7
-0
-2
2
7
-0
T C H d ro p
-2
3
7
-0
-2
4
7
-0
-2
5
7
-0
-2
6
7
S d cch D ro p
-0
-2
7
7
-0
-2
8
7
-0
-2
H O F A IL
9
7
-0
-3
P o ly . ( H O F A I L )
P r e s e n t a tio n / A u t h o r / D a t e
D r o p c a ll d u e to H a n d o v e r : Im p r o v e m e n t ( B S C 0 5 ) .
F o r in t e r n a l u s e
4
N o k ia S ie m e n s N e t w o r k s
P r e s e n t a tio n / A u t h o r / D a t e
49 (136)
B S C -0 2 H O S R Im p r o v e m e n t
D e g r a d a ti o n is d u e
to R e -H o m in g .
R e s o l v e d o n 3 0 th
10000
7
6
%
5
E rl
1000
4
100
d a te o f
im p lim e n t a t io n
3
2
10
T C H T ra f f i c ( E l r)
F o r in t e r n a l u s e
5
N o k ia S ie m e n s N e tw o r k s
T C H d ro p
S d c c h D ro p
H O FA IL
2 0 0 7 -0 7 -3 0
2 0 0 7 -0 7 -2 9
2 0 0 7 -0 7 -2 8
2 0 0 7 -0 7 -2 7
2 0 0 7 -0 7 -2 6
2 0 0 7 -0 7 -2 5
2 0 0 7 -0 7 -2 4
2 0 0 7 -0 7 -2 3
2 0 0 7 -0 7 -2 2
2 0 0 7 -0 7 -2 1
2 0 0 7 -0 7 -2 0
2 0 0 7 -0 7 -1 9
2 0 0 7 -0 7 -1 8
2 0 0 7 -0 7 -1 5
2 0 0 7 -0 7 -1 7
2 0 0 7 -0 7 -1 6
1
0
P o ly. (H O F A IL )
P r e s e n t a ti o n / A u t h o r / D a t e
D ro p c a ll d u e to H a n d o v e r : Im p ro v e m e n t ( B S C 0 2 ) .
F or in ter n a l u s e
6
N o k ia S ie m e n s N e tw o r ks
P r es e n ta tio n / A u th o r / D a te
50 (136)
H a n d o v e r Im p r o v e m e n t (B S C 1 5 ): -
B S C - 0 1 5 - H O S R IM P R O V E M E N T
10000
7
6
ER L
1000
5
4
100
d a te o f im p lim e n ta tio n
3
2
10
1
1
-0
-1
-0
-1
7
7
-0
-1
5
7
-0
-1
-0
-1
9
7
-0
-2
T C H T ra f f i c ( E l r)
F o r in t e r n a l u s e
7
N o k ia S ie m e n s N e tw o r k s
0
7
-0
-2
1
7
-0
-2
2
7
-0
-2
-0
S d c c h D ro p
-2
4
7
-0
-2
-0
-2
-0
-2
T C H d ro p
-0
-2
8
7
-0
-3
H O FA IL
P o ly. (H O F A IL )
P r e s e n t a tio n / A u t h o r / D a t e
H a n d o v e r Im p r o v e m e n t ( B S C 1 2 ) : -
B S C -0 1 2 H O S R Im p rov e m e n t
10000
7
6
1000
5
4
100
d a te o f
im p lim e n ta tio n
10
1
1
-0
7
2
-1
0
-0
7
2
-1
0
-0
7
2
-1
0
-0
-1
-0
7
2
-1
0
-0
7
2
-2
0
-0
7
2
-2
0
T C H T r a f f ic ( E lr )
F o r in t e r n a l u s e
9
N o k ia S ie m e n s N e t w o r k s
-0
-2
-0
7
2
-2
0
T C H d ro p
-0
7
2
-2
0
-0
7
2
-2
0
-0
-2
-0
S d cch D ro p
7
2
-2
0
-0
7
2
-2
0
-0
7
2
-2
0
H O F A IL
-0
-3
P o ly . ( H O F A IL )
P r e s e n t a tio n / A u t h o r / D a t e
Thus this Parameter can be implemented, Network Wide of Idea Cellular Delhi for Better Handover
Performance Enhancement and Drop Call Due to Handover.
51 (136)
LAPD-T200 Timer
Optimization Performance Report
Idea Cellular Delhi
20th-July-2007
Stenin.NP.
Nokia Siemens Networks.
For internal use
1
Nokia Siemens Networks
Optimization of LAPD-T200 Timer, LAPD-N200 along with LAPD-k Value:Fine tuning of Timer LAPD-T200 to enhance SDCCH Drop call rate on BSC18 Idea
Cellular Delhi Network.
52 (136)
SDCCH Enhancement after timer T200 was finetuned appropriately from 0ms to
780ms (for both FACCH and SDCCH
53 (136)
T 2 0 0 P e rfo rm a n c e e n h a n c e m e n t :
W ith n o D e g r a d a tio n in T C H D r o p f o r th is P a r tic u la r B S C 1 8 .
F o r in t e r n a l u s e
5
N o k ia S ie m e n s N e tw o r k s
P r e s e n t a tio n / A u t h o r / D a t e
Thus this Timer T-200 can be finetuned, Network Wide of Idea Cellular Delhi
for Better SDCCH Performance Enhancement
3.4
54 (136)
Stenin.N.P
Networks, and Service Optimipation.
Nokia.India
H A N D O V E R O P T IM IZ A T IO N P E R F O R M A N C E ,
F O R D IF F E R E N T H A N D O V E R C R IT E R IA :
ID E A C E L L U L A R
D E L H I.
2 4
th
A u g 2 0 0 7 .
F o r in t e r n a l u s e
2
N o k ia S ie m e n s N e tw o r k s
P r e s e n ta tio n / A u th o r / D a te
The Window and Weighting have dependency on the raw measurement done on the SACCH (480msec)
for different Handover Criterias.
55 (136)
Power Budget UL
Power Budget DL
Quality Handover UL
Quality Handover DL
Level Handover UL
Level Handover DL
Interference Handover UL
Interference Handover DL
Distance Handover UL
Distance Handover DL.
Each of these Handover Criteria have parameters which can be fine tuned
such as Window size ,Weighting , Threshold and NX and PX Value appropriately for better Performance
in Handover of a cellular Network. The analysis done is for Level and Quality based handover.
Statistics from ND 204,with cause values for Handover, Idea Cellular Delhi:-
[ CASE I ]
LEVEL HANDOVER IN THE DOWN LINK:
56 (136)
LDWS: Level Down link Window Size:Description:Parameter calculates average value from signal strength in the Downlink
Measurement. Window size represents the average window size in SACCH Period.
Range:
1 SACCH to 32 SACCH.
MML Default:
6 SACCH.
Example:If LDWS is set to a value of 6,means that for the consecutive 6 SACCHs in the downlink, it will
take in the level and average it to get one value.The next average will happen between 2nd to 7th
SACCH period (For next 6 consecutive SACCHs). So in this scenario there will be 6 SACCHs taken into
account to make an average as set by LDWS=6 as shown in the diagram below.
LDWS: Level Down link Window Size:-
LDW:-Weighting
LDW:-Level Down Link Weighting.
Description:-
57 (136)
[ CASE II ]
LEVEL HANDOVER IN THE UP LINK:
Parameters associated with Level Handover in the UP Link:
LUWS: Level UP link Window Size.
LUW:-Weighting.
LUR:-Threshold Level UP link Rx Level.
LUP (Px):-Number of samples to be satisfied out of the Nx.
LUN(Nx):-Total Number of Averages.
LUWS: Level UP link Window Size:Description:Parameter calculates average value from signal strength in the UPlink
measurement. Window size represents the average window size in SACCH Period.
Range:
1 SACCH to 32 SACCH.
MML Default:
6 ( SACCH Period ).
Example:-
58 (136)
59 (136)
If LUWS is set to a value of 6,means that for the consecutive 6 SACCHs in the UP link, it will
take in the level and average it to get one value.The next average will happen between 2nd to 7th
SACCH period (For next 6 consecutive SACCHs). So in this scenario there will be 6 SACCHs taken into
account to make an average as set by LUWS=6 .
LUW:-Weighting.
LUW:-Level UP Link Weighting.
Description:This Parameter has a dependency on the DTX ( Discontinuous Transmission)
If Discontinuous Transmission in the UP link is switched off then the LUW Value should be set to
1,stating all SACCHs taken into consideration.
And in cause if Discontinuous Transmission in the UP link is switched On, then the LUW Value should
be set to 2 / 3 appropriately, stating blank speech in between, not a continuous Transmission.
Range:
1 to 3.
MML Default:
Value of 1.
LUR:-Threshold Level UP link Rx Level:Description:This Parameter compares the average values of signal strength in the UP link direction for
triggering the handover process. In other words with this parameter one can set the threshold for Rx
Level in the UP link. The averages has to overcome the value set by this particular parameter LUR.
Range:
-110 to -47dBm.
MML Default:
-95 dBm.
LUN (Nx):-Total Number of Averages.
Description:This Parameter, states number of Averages that have to be taken into account when making a
Level based UP link handover decision.
Range:
1 to 32.
MML Default:
Value of 1.
Example:- If the value set is 4, then total of 4 averages are used for decision making.
NOTE:-If the decision have to be speeded up or slowed down, this parameter can be reduced or
Incremented appropriately.
LUP(Px):-Number of samples to be satisfied out of the Nx .
Description:This Parameter, states the number of averages that should satisfy the threshold (LUR), out of
the Total averages (LUN-NX).
Range:
1 to 32.
MML Default:
Value of 1.
Example: - If the value set is 3, then there should be a minimum of 3 averages that should satisfy the
threshold of the total of 4 averages (NX) for a decision making for Level based UP link handover.
3(PX) out of 4(NX).
60 (136)
[ CASE III ]
QUALITY HANDOVER IN THE DOWN LINK:
Parameters associated with Quality Handover in the Down Link:
QDWS: Quality Down link Window Size.
QDW:-Weighting.
QDR:-Threshold Quality Downlink Rx Qual.
QDP(Px):-Number of samples to be satisfied out of the Nx .
QDN(Nx):-Total Number of Averages.
QDWS: Quality Down link Window Size:Description:Parameter calculates average value from quality in the Downlink
measurement. Window size represents the average window size in SACCH Period.
Range:
1 SACCH to 32 SACCH.
MML Default:
1 ( SACCH Period ).
Example:If QDWS is set to a value of 1,means that for every SACCH (480msec) in the downlink, it will
take in the quality.
NOTE:-As in cause of Level varies at a very fast rate compared to Rx Quality. Thus for Quality QDWS
the default is taken as 1,ie decision taken for every SACCH period.
QDW:-Quality Down Link Weighting.
Description:This Parameter has a dependency on the DTX ( Discontinuous Transmission)
If Discontinuous Transmission in the Down link is switched off then the QDW Value should be set to
1,stating all SACCHs taken into consideration.
And in cause if Discontinuous Transmission in the Down link is switched On, then the QDW Value
should be set to 2 / 3 appropriately, stating blank speech in between, not a continuous Transmission.
Range:
1 to 3.
MML Default:
Value of 1.
QDR:-Threshold Quality Downlink Rx Qual:Description:This Parameter compares the values of signal quality in the Down link direction for triggering the
handover process. In other words with this parameter one can set the threshold for Rx Quality in the
downlink. This value has to overcome the value set by this particular parameter QDR.
Range:
0 to 7.
MML Default:
4 (1.6% to 3.2%).
QDN (Nx):-Total Number of Averages.
61 (136)
Description:This Parameter, states number of Averages that have to be taken into account when making a
Quality based Downlink handover decision.
Range:
1 to 32.
MML Default:
Value of 6.
Example: - If the value set is 6, then total of 6 averages are used for decision making.
NOTE:-If the decision have to be speeded up or slowed down, this parameter can be reduced or
Incremented appropriately.
QDP (PX):-Number of samples to be satisfied out of the Nx.
Description:This Parameter, states the number of averages that should satisfy the threshold (QDR), out of
the Total averages (QDN-NX).
Range:
1 to 32.
MML Default:
Value of 4.
Example: - If the value set is 4, then there should be a minimum of 4 averages that should satisfy the
threshold of the total of 6 averages (NX) for a decision making for Quality based downlink handover.
4(PX) out of 6(NX).
NOTE:-NX should always be greater than PX.
NOTE:-In cause of Level, there are two trailing SACCH considered for decision making .But where as for
Quality, the sliding average is done only once as QDWS is by default set to one.
Diagram showing, how decision is made for Quality based Downlink Handover:
62 (136)
[CASE IV]
QUALITY HANDOVER IN THE UP LINK:
Parameters associated with Quality Handover in the UP Link:
QUWS: Quality UP link Window Size.
QUW:-Weighting.
QUR:-Threshold Quality UP link Rx Qual.
QUP (PX):-Number of samples to be satisfied out of the Nx.
QUN (Nx):-Total Number of Averages.
QUWS: Quality UP link Window Size:Description:Parameter calculates average value from quality in the UP link
Measurement. Window size represents the average window size in SACCH Period.
Range:
1 SACCH to 32 SACCH.
MML Default:
1 (SACCH Period).
Example:If QUWS is set to a value of 1, means that for every SACCH (480msec) in the UP link, it will
take in the quality.
NOTE:-As in cause of Level varies at a very fast rate compared to Rx Quality. Thus for Quality QUWS
the default is taken as 1, ie decision taken for every SACCH period.
QUW:-Weighting.
QUW:-Quality UP Link Weighting.
Description:This Parameter has a dependency on the DTX (Discontinuous Transmission)
If Discontinuous Transmission in the UP link is switched off then the QUW Value should be set to 1,
stating all SACCHs taken into consideration.
And in cause if Discontinuous Transmission in the UP link is switched on, then the QUW Value should
be set to 2 / 3 appropriately, stating blank speech in between, not a continuous Transmission.
Range:
1 to 3.
MML Default:
Value of 1.
QUR:-Threshold Quality UP link Rx Qual:Description:This Parameter compares the values of signal quality in the UP link direction for triggering the
handover process. In other words with this parameter one can set the threshold for Rx Quality in the UP
link. This value has to overcome the value set by this particular parameter QUR.
Range:
0 to 7.
MML Default:
4 (1.6% to 3.2%).
63 (136)
F or in t er n a l u s e
24
N o k ia S ie m e n s N e t w o r k s
P r es e n t a tio n / A u t h o r / D a t e
64 (136)
Thus these parameters can be fine tuned appropriately for Level and Quality for better Handover
performance. Further fine tuning requirement for improvement Power budget Handover and Handover
due to Interference for Both UP Link and Down Link on the Network Level after appropriate.
3.5
The umbrella handover concept was applied for IBS site HYATREG 2of
65 (136)
Idea Cellular Delhi Network, where there was performance enhancement seen in Handover and TCH
Drop Call.
Parameter used for fine tuning:
The above param eters are explained in the previous session, on their operations.
P e rfo rm a n c e E n h a n c e m e n t P lo t:
F or in ter n a l u s e
6
N o k ia S ie m e n s N e tw o r ks
P r es e n ta tio n / A u th o r / D a te
66 (136)
67 (136)
Thus there was improvement in Handover and TCH Drop Call for Site HYATREG of Idea
Cellular Delhi, with no degradation in performance of the neighboring sites.
3.5
68 (136)
The basis IBS Design verification was carried out for one of the IBS Cell at Idea
cellular Delhi Network for performance enhancement.
SUMMARY
In- Building survey was conducted for the Park Royal Hotel, Delhi. Summery of this
survey is as follows:
Due to uneven EIRP & improper IBS design there are some poor coverage areas inside
the Bldg. & on the window of rooms.
To improve the coverage & performance of this IBS site we had re-designed the Park
Royal IBS. This design gives sufficient & even EIRP to all planned antennas inside the
bldg.
As at present we are not having access to put antennas inside the Hotel rooms so we
may not have sufficient indoor coverage at the window of rooms to avoid Idea customer
to camp or latch on outdoor signal. On these windows at present we are facing PingPong condition.
After implementation of new design if we face same problem on the window of Hotel,
then we propose the dedicated outdoor site to give the proper indoor coverage inside the
rooms.
For the implementation of proposed new IBS design at Hotel Park Royal Hotel, we
require IDEA Delhi team help to get access inside the building & floor plan of all floors of
this Hotel. Also we require some extra IBS material.
As per new design antennas are having EIRP between 14 to 19 dBm. In old design EIRP
was 0 dBm to 10 dBm.
69 (136)
70 (136)
The Trunking diagram was modified appropriately with a new Design for better efficacy, by
having the Metro cell replaced by ultra cell adding in more capacity.And also by splitting the sector to
have a constatnt and high EIRP appropriately.
PA RK RO YA L H O TEL D ELH I
T R U N K IN G D IA G R A M
U L T R A M IN I
BTS
SECTO R 1
LEVEL 3
15m
SH AFT 1
SH AFT 2
SH AFT 3
SH AFT 4
5m
A 1 -L 4
1 9 .8 5 d B m
A 1 -L 5
1 9 .3 d B m
5m
10m
15 m
5m
A 1 -L 6
1 9 .8 5 d B m
A 1 -L 7
1 9 .3 d B m
A 1 -L 8
1 9 .8 5 d B m
A 1 -L 9
1 9 .3 d B m
5m
10m
30m
5m
5m
10m
15m
5m
A 1 -L 1 0
1 9 .8 5 d B m
A 1 -L 1 1
1 9 .3 d B m
5m
10m
L E V E L 4 T O L E V E L 1 1 - G U E ST F L O O R S -SH A F T 1
71 (136)
PA R K R O YA L H O TEL D ELH I
TRUNK ING DIAG RAM
10
5m
20m
10m
A2 -L4
17.75dBm
A2 -L5
18.3 dB m
A2 -L6
17.75 dBm
10m
5m
30m
5m
10m
10m
5m
10m
10m
A2 -L7
19.4 dB m
A2 -L8
19.95 dBm
A2 -L9
19.4 dB m
A2 -L10
18.85 dBm
A2 -L11
19.4 dB m
A2 -L12
18.85 dBm
5m
A3 -L4
19.85dBm
A3 -L5
19.3 dB m
5m
10m
15 m
5m
A3 -L6
19.85 dBm
A3 -L7
19.3 dB m
A3 -L8
19.85 dBm
A3 -L9
19.3 dB m
5m
10m
30m
5m
5m
10m
15m
5m
A3 -L10
19.85 dBm
A3 -L11
19.3 dB m
5m
10m
72 (136)
P A R K R O YA L H O TEL D ELH I
TR U N K IN G D IA G R AM
5m
A4 -L4
19.85 dB m
A4 -L5
19.3 dB m
5m
10m
15 m
5m
A4 -L6
19.85 dB m
A4 -L7
19.3 dB m
A4 -L8
19.85 dB m
A4 -L9
19.3 dB m
5m
10m
30m
5m
5m
10m
15m
5m
A4 -L10
19.85 dB m
A4 -L11
19.3 dB m
5m
10m
73 (136)
P A R K R O Y A L H O T EL D ELH I
T R U N K IN G D IA G R AM
U L T R A M IN I
BTS
SE C T O R 2
LEVEL 3
5m
A1 -L0
1 5 .3 5 dB m
A2 -L0
1 4 .8 dB m
10m
10m
10m
30m
40m
LEVEL - 0
A3 -L0
1 4 .6 dB m
10d B
10m
10m
A4 -L0
1 4 ..9 dB m
A5 -L0
1 4 .4 dB m
15m
15m
40m
45m
5m
A6 -L0
1 5 .5 dB m
A7 -L0
1 4 .1 dB m
A1 -L1
1 8 .2 dB m
A2 -L1
1 7 .2 dB m
20m
40m
5m
15m
15m
15m
30m
L E V E L 1- B A NQ UE T FLO O R
A3 -L1
1 6 .2 dB m
A4 -L1
1 6 .2 dB m
A5 -L1
1 8 .7 dB m
40m
30m
7d B
10m
5m
5m
30m
1 7 .9 dB m
A7 -L1
1 7 .2 dB m
30m
25m
T O LE V EL S 1
A6 -L1
74 (136)
PA R K R O YA L H O TEL D ELH I
T R U N K IN G D IA G R A M
F R O M L EV EL 1
20m
L E V E L S1
5m
20m
30m
20m
7d B
A 1 -L S1
1 6 .6 dB m
A 2 -L S1
1 5 . 5 dB m
A 3 -L S1
1 6 .6 dB m
A 4 -L S1
1 7 .1 dB m
A 5 -L S1
1 7 .7 dB m
A 6 -L S1
1 6 .0 dB m
A 1 -L S2
1 8 .9 dB m
A 2 -L S2
1 8 .3 5 dB m
10m
20m
15m
15m
30m
10m
5m
15m
15m
L E V E L - S2- H E AL TH C L UB
5m
20m
40m
A 3 -L S2
1 6 .3 dB m
A 4 -L S2
1 4 .6 5 dB m
A 5 -L S2
1 4 .1 dB m
A 6 -L S2
1 8 dB m
30m
25m
35m
10m
A 7 -L S2 -H C 1 5 .8 dB m
45m
10m
5m
T O LE V EL B 2
A 8 -L S2 -H C 1 5 .8 dB m
A 9 -L S2 -H C 1 5 .8 dB m
75 (136)
PA RK RO YA L H O TEL D ELH I
T R U N K IN G D IA G R A M
FRO M LEVELS2
10m
LEVEL B2
A 1 -L 7
25m
5m
7dB
15m
20m
A 1 -L 8
A 1 -L 9
1 6 .5 d B m
1 5 .9 d B m
1 5 .4 d B m
15m
15m
A 1 -L 1
1 8 .5 d B m
A 2 -L 1
1 6 .9 d B m
20m
30m
10m
LEVEL B1
A 1 -L 1
1 6 .0 d B m
A 2 -L 1
1 4 .3 d B m
40m
25m
The EIRP before plan was unevenly distributed with some nodes having very low EIRP when compared
to some nodes with quite high EIRP, which was finetuned in the new design appropriately with the help
of 2 ways to 3 ways couplers.Sectorisation helped in power increment and Capacity enhancement as
well.
3.7
76 (136)
Stenin.N.P
Networks, and Service Optimipation.
Nokia.India
Parameter Description:
RLT:-Radio Link Timeout:Parameter (RLT) Radio Link Timeout can be fine tuned appropriately to
have performance enhancement on the Drop Call for cells tending to Drop High on TCH.
Description:This Parameter defines the maximum value of radio link counter expressed in SACCH frame.
Range:
0 to 64 SACCH.
With a step size of 4 SACCH.
MML Default:
Value of 4.
Nokia Tested 20 SACCH
77 (136)
ARLT: AMR Radio Link Timeout:Similarly (ARLT) AMR Radio Link Timeout can be fine tuned appropriately to have
performance enhancement on the Drop Call for cells tending to Drop High on TCH with AMR
Implemented.
Description:This Parameter defines the maximum value of radio link counter expressed in SACCH frame for
AMR Calls.
Range:
4 to 64 SACCH.
With a step size of 4 SACCH.
MML Default:
Value of 20.
Nokia Tested 36 SACCH
MML COMMANDE @ BSC FOR RLT & ARLT:
The below performance plot shows how cells had performance enhancement
TCH_COMPLETION_RATE after fine tuning RLT from value of 20 to 24 SACCH
78 (136)
79 (136)
The above Diagram shows how RLT is incremented (Steps of 2) on successful decoding of a SACCH,
and also Decrement (Steps of 1) on unsuccessful decoding of Consecutive SACCH.
Similarly ARLT was fine tuned from a value of 20 SACCH to 36 SACCH on the Network Level for
Idea Cellular Delhi Network with enhancement in TCH_COMPLETION_RATIO as shown in the
Performance plot below.
80 (136)
ARLTFinetunned to a value of
36, dated 7th Aug 2007.
62.00
59.00
56.00
53.00
50.00
/07 4/07 4/07 5/07 5/07 5/07 5/07 5/07 5/07 5/07 5/07 5/07 5/07 6/07 6/07 6/07 6/07 6/07 6/07 6/07 6/07 6/07 6/07 7/07 7/07 7/07 7/07
/04
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
/0
23
26
29
02
05
08
11
14
17
20
23
26
29
01
04
07
10
13
16
19
22
25
28
01
04
07
10
TCHCompletion Ratio.
Thus optimizing RLT and ARLT parameters can bring in enhancement in performance
on TCH_COMPLETION_RATIO (TCH Drop Call) appropriately
3.8
81 (136)
Stenin.N.P
Networks, and Service Optimipation.
Nokia.India
Advantage of TRHO:-
Distributes traffic between cells in close proximity.Increases coverage area of under utilized target cell.
Reduces congested coverage area of a particular cell.
1)
2)
3)
4)
5)
6)
7)
82 (136)
AMH Advance Multilayer Handling:AMH Consists of three different features, related to network Load.
a) BSC Initiated TRHO.
b) IUO Load Control (Intelligent Underlay Overlay)
c) Multilayer Load Control (Dual band network operation)
AMH provided both Capacity and Coverage by distributing traffic evenly over the network.
Used especially in 1) Multi band (GSM 900/ GSM 800)
2) Micro cellular or Multilayer (IUO) Network.
AMH is used to relief load of a congested cell. AMH Dynamically distributes traffic to appropriate cell /
Layer / Frequency band according to load in the Network.
To avoid additional handover, back to heavy loaded cell, the AMH has a particular penalty system. Thus
mobiles cannot be directed back to original heavy loaded cell before the penalty timer expires.
TRHO: AMH TRHO TARGET LEVEL:This Parameter defines the minimum signal level when a traffic reason handover is allowed to
an adjacent cell.
This parameter is set in the Neighbor defined in the Source Cell.
83 (136)
Range: -109
to -47(dBm).
N (Not used)
MML Default:
N (Not in use)
Tested value -85 dBm.
AUT: AMH Upper Load Threshold:This Parameter defines the upper threshold for load of the Base station .This parameter
triggers, BSC Controlled traffic reason handover. In other words, the Traffic reason handover will get
triggered in the Congested (Source) cell, when the load of this source cell goes above set value in the
AUT (say source cell loaded more than 80%, triggrs TRHO).
Range: 0 to 100 or
N (Not used)
MML Default: N (Not in use)
Tested value 80.
AML: AMH Max Load Of Target Cell:This Parameter defines maximum traffic load in the adjacent cell that is allowed to be the target
cell for Traffic reason handover. In other words, when the Traffic reason handover get triggered in the
Congested (Source) cell with AUT 80, the target cell where the traffic should be distributed should not be
loaded more than 60.
Range: 0 to 100 or
N (Not used)
MML Default:
N (Not in use)
Tested value 60.
TGT: TRHO Guard Time:This Parameter defines the guard time after a BSC-controlled or an MSC-controlled TRHO,
during which a handover back to the original cell is not allowed. In other words the MS will not be
directed back to the original heavy loadad cell until the time set by TGT is attained.If TGT set to 20 sec,
then the handover from target back to source will happen after 20 sec only.
Range:
0 to 120 Sec.
MML Default:
30
Tested value 20.
SL: Rx level min cell:This Parameter defines the minimum signal level of an adjacent cell when a handover is allowed to the
Neighboring cell
Range:
-110 to -47 dBm.
MML Default: -100
Tested value -92 dBm.
ATPM:AMH TRHO Pbdgt Margin:This Parameter defines the guard time after a BSC-controlled or an MSC-controlled TRHO,
during which a handover back to the original cell is not allowed. In other words the MS will not be
directed back to the original heavy loadad cell until the time set by TGT is attained.If TGT set to 20 sec,
then the handover from target back to source will happen after 20 sec only.
Range:
-24 to 24 dBm. Or N.
MML Default:
N (Not active)
84 (136)
85 (136)
Range:
On/Off
MML Default:
Off
RIM: Resource Indication Method:Range:
No Indication.
Per=Periodic Indication
MML Default: No Indication
TRHO: Traffic Reason Ho function from Cell:-
Range:
On / Off
MML Default:
Off
TRHI: Traffic Reason Ho function to Cell:-
Range:
On / Off
MML Default:
Off
OUTC: Out Criterion:-
Range:
MML Default:
10%
Nokia Tested 98%
4.
Optimizer Cycle
86 (136)
OPTIMIZER CYCLE 2
General Information:
Optimizer 2.0 was run for Idea Cellular Delhi Network, with measurements enabled for consecutive three
days having the Network Freeze for this duration.
Optimizer had plans generated for:
TCH & BCCH Frequency Plan
BSIC Plan.
There were also Prediction's made for Cell sites that were planned for the month of Oct 2007, yet to be
rolled out.
87 (136)
There were several iterations run for better efficacy of Plan and some of the results from the Plan is
jotted down along with the Improvement in performance from Statistics extracted form Nokia OSS.
Optimizer Results: Idea Cellular Delhi
88 (136)
89 (136)
U L & D L Q U A L IT Y Id e a C e llu la r D e lh i.
2 .6 0
2 .5 0
2 .4 0
O p tim iz e r
C y c le
2 .4 0
2 .3 0
2 .2 0
2 .1 0
2 .0 0
2 .0 0
1 .9 0
1 .8 0
1 .8 0
D L Q u a lit y .
U L Q u a lit y .
2 .2 0
1 .7 0
1 .6 0
1 .6 0
1 .5 0
1 .4 0
1 .4 0
2007-10-12
2007-10-08
2007-10-04
2007-09-30
2007-09-26
2007-09-22
2007-09-18
2007-09-14
2007-09-10
2007-09-06
2007-09-02
2007-08-29
2007-08-25
2007-08-21
2007-08-17
2007-08-13
2007-08-09
2007-08-05
2007-08-01
2007-07-28
2007-07-24
2007-07-20
2007-07-16
2007-07-12
2007-07-08
2007-07-04
2007-06-30
2007-06-26
2007-06-22
1 .2 0
2007-06-18
1 .3 0
1 .2 0
Date .
U L Q u a lit y
D L Q u a lit y
Po ly . ( D L Q u a lit y )
Po ly . ( U L Q u a lit y )
40000
O p tim iz e r
C y c le
38000
36000
32000
30000
28000
26000
24000
D a t e ...
T C H T r a f f ic ( Elr )
H O F a il
Po ly . ( H O F a il)
2007-10-12
2007-10-08
2007-10-04
2007-09-30
2007-09-26
2007-09-22
2007-09-18
2007-09-14
2007-09-10
2007-09-06
2007-09-02
2007-08-29
2007-08-25
2007-08-21
2007-08-17
2007-08-13
2007-08-09
2007-08-05
2007-08-01
2007-07-28
2007-07-24
2007-07-20
2007-07-16
2007-07-12
2007-07-08
2007-07-04
2007-06-30
2007-06-26
20000
2007-06-22
22000
2007-06-18
T r a f f ic ( E lr ) .
34000
7 .8 0
7 .6 0
7 .4 0
7 .2 0
7 .0 0
6 .8 0
6 .6 0
6 .4 0
6 .2 0
6 .0 0
5 .8 0
5 .6 0
5 .4 0
5 .2 0
5 .0 0
4 .8 0
4 .6 0
4 .4 0
4 .2 0
4 .0 0
3 .8 0
3 .6 0
3 .4 0
3 .2 0
3 .0 0
2 .8 0
2 .6 0
2 .4 0
2 .2 0
2 .0 0
H a n d o v e r _ F a ilu r e .
H O P e r fo r m a n c e I d e a C e l l u l a r D e l h i :
90 (136)
40000
Optimizer
Cycle
37500
Traffic (Elr) .
35000
32500
30000
27500
25000
18 - 23 - 28 - 03 - 08 - 13 - 18 - 23 - 28 - 02 - 07 - 12 - 17 - 22 - 27 - 01 - 06 - 11 - 16 - 21 - 26 - 01 - 06 - 11
66
6
7
7
7
7
7
7
8
8
8
8
8
8
9
9
9
9
9
9
0
0
0
-0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -0 7 -1 7 -1 7 -1
7
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
3.00
2.90
2.80
2.70
2.60
2.50
2.40
2.30
2.20
2.10
2.00
1.90
1.80
1.70
1.60
1.50
1.40
1.30
1.20
1.10
1.00
0.90
0.80
0.70
0.60
0.50
0.40
0.30
0.20
0.10
0.00
TCH_Drop , SDCCH_Drop .
Date ...
TCH Traf f ic (Elr)
TCH Drop
SD Drop
Thus there was improvement in performance of Uplink Quality, Down Link Quality, Handover,
and also on TCH Drop and SDCCH Drop Call on the Network Level.
5.
EOSFLEX OPERATIONS.
Idea Cellular Delhi
11th-May-2007
Stenin.N.P
Networks, and Service Optimipation.
Nokia.India.
For internal use
1
Nokia Siemens Networks
91 (136)
92 (136)
This Nokia Propriety tools EOSFLEX Release 5.52, helps in extracting statistical Data
from a 2G, 2.5G and WCDMA Networks, by querying the Data base server at the Nokia OSS.
Different .xml scripts are written for extraction of the required Data from the OSS.
The data extraction can be scheduled, with the help of a scheduler for atomizing the
stats extraction task, wherein reducing the time requirement for Data extraction.
Once a query is made for a particular day for a particular data from the OSS, and the
task is carried out for the second time for stats of the same day, the tool reduces the time it will
take after the first attempt to query the Data base server, which is time consuming.
Note: The output can be extracted as .csv (Excel output).
Note: The engine handles all scheduled jobes.It process scheduled jobs defined in the XML
file.
The engine contains of Perl script, supporting modules for Excel, Zip, and mailing
interface
The engine starts via WIN2K Task scheduler.
SCRIPT: There are different tables from which the raw counters are to be extracted.
Some of the commonly used tables are listed:<temp_table create="yes" name="traffic">
<temp_table create="yes" name="ho">
<temp_table create="yes" name="res_avail">
<temp_table create="yes" name="service">
<temp_table create="yes" name="res_access">
<temp_table create="yes" name="pcu">
<temp_table create="yes" name="qual">
<temp_table create="yes" name="rxqual">
<temp_table create="yes" meas_level="" name="mcs">
93 (136)
94 (136)
95 (136)
96 (136)
/
( traffic.tch_norm_seiz
+ho.msc_i_sdcch_tch
+ho.bsc_i_sdcch_tch
+ho.cell_sdcch_tch
-traffic.tch_succ_seiz_for_dir_acc
+traffic.tch_seiz_due_sdcch_con)
), null)
</formula>
<kpi_alias>
Tch Comp ratio</kpi_alias>
<kpi_format>format %3.2f</kpi_format>
<kpi_mark></kpi_mark>
<area_level>all</area_level>
<kpi_info>
<title>Drop Call Ratio (dcr_3i)</title>
<use></use>
<use_experience></use_experience>
<known_problems></known_problems>
<open_questions></open_questions>
<formula></formula>
<pm_class></pm_class>
<unit>(%)</unit>
<tables> p_nbsc_traffic</tables>
</kpi_info>
</kpi>
<info>
<release number="5"/>
<maxrows>100</maxrows>
<header>Idea_kpi </header>
<help_file> about_eosflx.htm</help_file>
<csv_title> gos_new </csv_title>
<bts_number>20< /bts_number>
<csv_rule>reuse</ csv_rule>
<wrap_header>on< /wrap_header>
<dst>RC</dst>
<nokia_counter_id_help_file></nokia_counter_id_help_file>
<nokia_counter_db_help_file></nokia_counter_db_help_file>
<nokia_kpi_help_file></nokia_kpi_help_file>
<external_kpi_help_file></external_kpi_help_file>
<report_version></report_version>
<min_obj_agg>BTS</min_obj_agg>
<nw_tp>2g</nw_tp>
<obj_number>20</obj_number>
<bts_number>20</bts_number>
<implementation>2g_ran</implementation>
<addon_sorting></addon_sorting>
<help_text><!-- <br> -->
</help_text>
</info> <! -- ============================ end =============================== -->
</conf_file>
97 (136)
Note: The above script is used for display in the Main report selection window.
After script is run to fetch report is stored @ D:\raproot\apps\scheduler\log\01.05.2007
Thus the output is calculated with the formula in the script and displayed in the above link after zipping
the output file appropriately.
After continuous execution of report using EOSFLEX, the old files can be cleared from over
loading the system from D:\raproot\data\incs\odrcache.
To add script for a new BSC Integrated D:\raproot\apps\scheduler\ IDEA_BSC_CS_BH.xml
98 (136)
Scheduler script.
<sched>
<!--The <info> node contains general definitions applicable to each report node/entry -->
<info id="info"> <!--Optional: The host IP address is used in report links for the title of the XLS sheet -->
<!--If the host IP address is not defined here the Scheduler will lookup the host name -->
<host_ip></host_ip> <!--The date format affects the name of the default XLS output directory and file
names -->
<date_format>europe</date_format>
<!--The default dsn is used if no report specific dsn(s) are defined. Also used in the default XLS dir -->
<dsn>idea_nw_rc</dsn>
<!--The default XLS directory structure. The directory structure will be put under the
SCHEDULER_OUTPUT path. On WAS this is equivelent to
%DIR_PERLAPI%/wwwroot/htdocs/dlbrowser -->
<xls_dir>/dlbrowser/{today}/</xls_dir>
</info>
99 (136)
100 (136)
column headers and object info in window while scrolling results in Excel.-->
5,5
</freezepane>
<sumxls> <!-- The name of the summary XLS file (leave empty if not required). Use the same
<sumxls>
name for several reports and each report will be a sheet in the same Excel workbook. You may use
variables
in the name.-->
</sumxls>
<markup>
<!-- Define markup for certain KPI results, e.g. "rlt5" = "red < 5" -->
</markup>
<datasetformat> <!-- Define the format for each column., e.g. "%5.2f" = "floating point 5 digits, two
decimals" -->
undef,undef,undef,undef,undef, %8u, %.2f, %.2f, %.0f, %.2f, %3i, %.2f, %3.2f, %.2f, %3.2f,
%.2f, %.0f, %.1f, %.1f, %8u, %8u, %3.2f, %.2f, %3.2f, %.0f, %.0f, %.0f, %.0f, %.0f, %.0f, %.0f, %.0f,
%.0f, %.0f, %.0f, %.0f, %.0f, %.0f, %.0f, %.0f, %8u, %8u, %0u, %.0f, %.0f, %.0f, %3.2f, %.0f, %.0f,
%.0f
, %.0f , %.0f , %.0f , %.0f , %.0f , %.0f , %.0f , %.0f , %.0f , %.1f , %.0f , %.0f , %.0f , %3.2f, %3.2f,
%.0f, %.0f, %3.2f, %.0f, %3.2f, %.0f, %.0f, %3.2f, %3.2f, %.0f, %.0f, %3.2f, %3.2f, %.0f, %.0f
</datasetformat>
</xls>
<sched_csv>
<!-- The CSV file name pattern. The question marks (??) in the sched_csv tag represent date specific
numbers; e.g. 20031109-20031110 -->
/odrcache//eosflx_idea_KPI3.xmlidea_nw_rc_CS_BH??.??.????_??.??.????_3_190657__._desc___SE
G_ID_.csv
</sched_csv>
<sched_csv_age>
</sched_csv_age>
<zip go="yes">
<zipfile>
BSC_CS_BH_IDEA.zip
</zipfile>
<sourcefiles>
{xlsfile}, {sumxls}, {sched_csv}
</sourcefiles>
</zip>
<mail go="no">
<mailfile>
RS_mail.csv
</mailfile>
<sourcefiles>
{xlsfile}, {sumxls}, {zipdest}
</sourcefiles>
<mailaddress>
your.name@company.com
</mailaddress>
</mail>
</instance>
</report>
</sched>
The above stat was generated for a particular BSC Using EOSFLEX.
6.
101 (136)
102 (136)
Alarm Number
Description
7745
2992
2993
7508
7600
BCF FAULTY
7601
7603
BTS FAULTY
7604
7606
TRX FAULTY
7617
7704
PCM FAILURE
7705
LAPD FAILURE
7715
7725
7738
7743
2955
7746
7767
BCCH MISSING
7939
8112
FREQUENCY ERROR
103 (136)
104 (136)
105 (136)
Time slot number 2 showing Alarm 7745 for TRX -002 of Site AMITYSCHL1 of BSC015
Statistics showing no calls been handled by this particular Timeslot number 2 of TRx-002 of site
AMITYSCHL1 of BSC15.
FIELD TEST TRIAL, FOR ALARM 7745:
106 (136)
The alarm 7745 shows for this particular cell SARAIJLNA1 that Timeslot (TS0 & TS1) to be
working fine and Timeslots(TS2, TS3,TS4,TS5,TS6, & TS7) not carrying calls(blocked).
Field test was conducted with TEMS for this particular cells at non busy hour and could find that the
Mobile could latch on to Time slot TS0 & TS1 only and and the remaining Time slots ( TS2, TS3, TS4, TS5,
TS6, & TS7 ) could not get calls going on tending the timeslot Faulty.
107 (136)
BD018
BCF-0030
EQUIPM 2007-07-24 04:20:45.42
** ALARM
(14652) 7601 BCF OPERATION DEGRADED
Difference between PCM and base station frequency reference.
02 01 07 96 00 00
II. Fault reason: Incompatible unit presence has been detected in the BTS.
108 (136)
Solution:
1. Replace the high power or EDGE TRX(s) with normal type TRX(s)
and reset the BCF.
2. Or, replace the normal type FAN and power supply with high power
or EDGE units. Now EDGE and high power TRXs are supported.
III. Fault reason: Difference between the PCM and BTS frequency reference.
Solution:
1. Check the synchronisation settings of the transmission interface.( DAC Value)DAC
value Range from 1800 t0 2200.
2. If the settings are OK, check the transmission chain.
3. If the alarm stays active or reappears after the recovery actions
above, reset the BCF.
4. If the alarm reappears after the BCF reset, replace the BTS.
Note: If this Supplementary alarm appears there is Drift in clock value(DAC). That
leads to HO failures
IV. Fault reason: Oven oscillator control is close to its margins. The oven
might be outdated.
Solution:
109 (136)
XX XX XX XX XX XX
1 2 3 4 5 6
1. Rack (cabinet) number
2.
3.
shelf number
slot
4. Type of unit
5. unit number
6. subunit number
This alarm is used for supervising the BTS traffic capacity and to indicate sudden loss
of service on BTS level
No SDCCH
Transaction
NO SDCCH TRANSACTION
110 (136)
NO GPRS TRANSACTION
2.
NO GPRS
Transaction
111 (136)
112 (136)
113 (136)
114 (136)
III. Fault reason: Rx levels differ too much between main and
diversity antennas.
Solution:
115 (136)
XX XX XX XX XX XX
1 2 3 4 5 6
7. Rack (cabinet) number
8.
9.
shelf number
slot
IV: Fault Reason: Fault in the chain between power unit and high gain MNxx with.
Descrpition: During the supervision period, the TCH time slot has suffered
Excessive interference in idle mode that is equal to or higher than
the operator-defined alarm threshold percentage.
That is the ,Interference in the time slot has lasted longer than is acceptable.
The interference level classified as excessive is defined by the
Operator. The alarm is used to supervise the BTS traffic capacity
1-8 the percentage (per each TRX time slot) that the channel has
Spent in excessive interference during the supervision period.
The number is a hexadecimal, 0 - 64 %.
116 (136)
10
Critical fault has occurred in a TRX. This alarm blocks the TRX.
Call drops will be severely with the faulty TRX.
117 (136)
Solution:
7.
Site ID
Site Name
Site Connected to BSC
TRX Configuration.
118 (136)
119 (136)
Inter MSC Incoming Handovers with all surrounding MSC's (if applicable) checked
OK
GPRS Attach
GPRS PDP Context Activation
GPRS PDP Context Deactivation
GPRS Routing Area Update (If applicable)
GPRS Detach
Site ID:
TRX #
Sector 1
10
11
12
10
11
12
10
11
12
Freq.
RxLev
TRX #
Sector 2
Freq.
RxLev
TRX #
Sector 3
Freq.
RxLev
TRX #
Sector 4
Freq.
801 805
808
RxLev
-51
-57
-49
120 (136)
10
11
12
Remarks
In the above example the efficacy of the Radio per sector can be checked in the field for better
performance.Say for Example, in sector 4 as shown above, having 3 TRX, and when tested of their
RXLev should not have a difference in the RXLev of not more than 5dbm between the TRX of the same
sector.
And as this test is to be conducted in a close proximity to the cell site, should not have an RXLev
not less than -55dbm proximately in each of the TRX.
Along with RXQual and Level Plot from the Drive, Problems like Hardware Faulty, Sector Swap,
Cable Swap, Etc can be further analysed with Field Drive testing.
121 (136)
Data Session
FTP Download
Attach & PDP Context
Activation
HTTP
Browsing
FTP Upload
Email
Send
Email
Receive
The data test comprised of sequence of Attach, then PDP Activation, followed by FTP Download,
HTTP Brouser, FTP Upload, Email Sending and then Email Reception.
122 (136)
Overall Idea has good Call Setup success rates, most of the failed calls are due to
coverage issues.
Idea slightly under performs with regards to the call completion rate and should be
worked upon.
Ideas speech quality is found good and speech samples for both the Uplink as well as
Downlink are well balanced .
With respect to call Accessibility and Retainability Dolphin is clearly underperforming.
In International comparison Airtel appears to have a fairly high cell density and is also the
highest compared to local competitors.
M o b ile S e rv ic e s Q u a lity in a N u ts h e ll
D e lh i, O c to b e r 2 0 0 7
DCQI
VCQI
t o p 2 0 % p e r fo r m e r s
i n t e r n a t i o n a lly
2
4
4 5
in t e rn a t io n a l a v e ra g e
5
2
1
1
ID E A
2
A i r te l
3 D o lp h in
4
H u tc h
5 R e lia n c e
22
N o k ia S ie m e n s N e tw o r ks
B e n c h m a r k S e r vic e R e p o rt / P M & R H / 2 0 .1 1 .2 0 0 7
lo w 2 0 % p e r fo r m e r s
i n t e r n a t i o n a lly
CST
V o ic e S e rv ic e Q u a lity
2 3
CCR
= Ca ll Co m p le t i o n Rat e
M OS
= M e a n Op i n io n Sco r e
CSSR
3 .3
3 .7
2
3
MOS
CCR
2 .6
= Ca ll Se t u p Ti m e
CSSR = Ca ll Se t u p Su cce ss Ra t e
C S T *)
VCQI
123 (136)
100%
9 9 .3 %
3 .9 4
1 00 %
9 9 .4 %
9 8 .2 %
9 6 .1 %
9 8 .6 %
3 .6 9
9 7 .0 %
4 .5
2
3
3 .6 0
4
1
5
1
ID E A
2
A i r te l
3 D o lp h in
4
H u tc h
5 R e lia n c e
24
3 .3 8
N o k ia S ie m e n s N e tw o r ks
9 .4
B e n c h m a r k S e r vic e R e p o rt / P M & R H / 2 0 .1 1 .2 0 0 7
7 4 .6 %
8 9 .2 %
* ) CST sco r e f o r Re li a n ce se t t o m e d ia n v a lu e
2 .9 5
124 (136)
DCQI
HTTP
FTPDL
FTPUL
SMS
MMS
1
2
GPRSAttach
PDPContext
4
2
4
4
4
5
45
5
1
2
2
5
1
1
2
12
35
The above plot shows Performance for Voice and Data when compared to other competator
Operators at Delhi area.
125 (136)
126 (136)
The table above gives an overview about the most important performance figures collected during
this 2G Benchmarking campaign.
8.
Nokia Macros:-
127 (136)
128 (136)
The Detailed List of availability of Macros for ND and MML is listed above.
129 (136)
9.
130 (136)
Drop on the TCH could be brought down to a value of 1.01 from an initial value of 2.6, with
taking the new sites getting integrated in the Network.
TCH BLOCKING:
Traffic Distribution:
131 (136)
SDCCH Drop:
SDCCH Blocking:
132 (136)
Handover Failure:
RACH Failure:
133 (136)
UL & DL Quality:
134 (136)
135 (136)
10.
Appendices.
End.
NETWORKS, AND SERVICE OPTIMIZATION
NOKIA SIEMENS NETWORKS.
136 (136)