2G & 2.5G Optimization Nokia India

NOKIA BSS PARAMETER TRAIL TEST & ANALYSIS NETWORKS, AND SERVICE OPTIMIZATION STENIN. N. P

2nd Dec 2007.

1 (136 (136))


2 (136 (136))

2nd Dec 2007.

The information in this document is subject t o change without notice and describes only the product defined in the introducti on 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 assumes full responsibility 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 Siemens Networks Networks has made all reasonable reasonable efforts to ensure that the instruction instructions s containe contained d in the document document are adequate adequate and free of materia materiall errors errors and omissions. omissions. Nokia Siemens Siemens Networks Networks will, if necessary, explain issues which may not be covered by the document. Nokia Siemens Siemens Networks' Networks' liability liability for any errors in the document document is limited to the documentary correction of errors. Nokia Siemens Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN TH IS 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 acc ording to the applicable laws. NOKIA SIEMENS logo is a registered trademark of Nokia Siemens Corporation. Other product names m entioned 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


2 (136 (136))

2nd Dec 2007.

The information in this document is subject t o change without notice and describes only the product defined in the introducti on 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 assumes full responsibility 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 Siemens Networks Networks has made all reasonable reasonable efforts to ensure that the instruction instructions s containe contained d in the document document are adequate adequate and free of materia materiall errors errors and omissions. omissions. Nokia Siemens Siemens Networks Networks will, if necessary, explain issues which may not be covered by the document. Nokia Siemens Siemens Networks' Networks' liability liability for any errors in the document document is limited to the documentary correction of errors. Nokia Siemens Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN TH IS 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 acc ording to the applicable laws. NOKIA SIEMENS logo is a registered trademark of Nokia Siemens Corporation. Other product names m entioned 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 (136))

2nd Dec 2007.

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 thank Pradee Pradeep p Chatt Chattik ikal al,, Prash Prashant anth h k, Vikra Vikrant nt Arun Arun Dolas, Dolas, Muthu Muthu Krus Krushna hnan n and Rajiv Rajiv Mohan Mohan Gandh Gandhii from Nokia Siemens Network. (India) for their technical support and providing valuable sujections during the course of work.I would also also like to thank Avnish Kumar from NSN, NSN, contributing contributing for IBS solutions 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.

Date: December December 02 2007.

Stenin.N.P Networks, and Service Optimization. Nokia Nokia Siemens Siemens Network Network,, India. India.


4 (136)

2nd Dec 2007.

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

EXECUTIVE SUMMARY.........................................................................................4 INTRODUCTION ................................ ......................Error! Bookmark not defined. OBJECTIVE.............................................................................................................7 Voice Audit……….…………………………………………………………………………..8 Radio Network Capacity and Traffic ……………………………………………………8 Cell wise Capacity Utilization…………………………………………………………..10 Spectrum Loading …………………………………………………………………….. .11 BSC and A-Interface Capacity and Utilization………………………………………..11 BCSU Utilization and sujections ……………………………………………….12 SDCCH Utilization and Failure Observations………………………………………...12 LAC Subscribers and Paging analysis ……………………………………………….13 LAC Distribution ……………………………………………………………...…13 Handover Cause Distribution ………………………………………………………….17 Frequency Utilization …………………………………………………………… …….18 Network Discrepancies ………………………………………………………… …… 18 SDCCH Redimensioning Requirement ………………………………………18 Basic Parameter Discrepancy ………………………………………………. .19 AMR Parameter Discrepancy …………………………………………………2 0 Neighbor Discrepancies ………………………………………………… …..20 Path Imbalance …………………………………………………………….....21 Ghost SDCCH Analysis ……………………………………………………….21 Data Audit………………………………………………………………………………...23 Executive summary …………………………………………………………………..23 EDGE / GPRS Configuration Settings ……………………………………………..23 GPRS / EDGE Parameter Discrepancies …………………………………………24 NSCI Plan Review …………………………………………………………………...29 RAC Plan Review ……………………………………………………………………30 Paging success rate verses LAC Plan ………………………………………….. ...31 Territory U pgrade … ……………………………………………………...................32 Multi slot allocation …………………………………………………………………..33 Sleeping Cells ……………………………………………………….……………….36 EDAP Congestion …………………………………………………….……………..37 Gb Utilization ………………………………………………………….……………..39 Recommendations …………………………………………………………………..40 Parameter Audit. …………………………………………………………..….………..41 Transcoder Optimization …………………………………………...….…………41 Ignored Transcoder Failure_ITCF …………………………………….………….42 Explanation ………………………………………………………..……..…………42 Parameter Discreption …………………………………………….……..………..42 MML Command …………………………………………………..………..………43 Performance Plot ……………………………………………….…………..……..44 Rx_Level_Min_Cell [SL] ………………………………………….….……….…..46 Parameter Discreption ………………………………………….…………….......46 Expected Improvement ……………………………………………………….......47 Handover Improvement Plot ……………………………………………………...48 Drop due to HO Improvement Plot …………………………..……………….....50 LAPD Timer T200 Optimization …………………………………………………51 Software Requirement …………………………………………………………….51 Parameter Discreption …………………………………………………………….52


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)

2nd Dec 2007.

Performance Plot ………………………………………………………………..53 Handover Detection Analysis ……………………………………..…..……….54 ND 204 Analysis ……………………………………………….………..55 Level HO in the Down Link …………………………………………………56 Explanation …………………………………………….……………….56 Parameter Descreption …………………………….………………….56 Level HO in the Up Link ……………………………….………………..58 Explanation ……………………………………..………………………58 Parameter Descreption ……………………..…………………………59 Quality HO in the Down Link ………………….…………………………60 Explanation ……………………………….……………………………..61 Parameter Discreption ……………….…………………………………61 Quality HO in the Up Link ………………..………………………………..62 Explanation ………………………………………………………………63 Parameter Descreption …………………………………………………63 IBS Optimization ……………………………………………… …………………64 Umbrella Cell Concept …………………………………………………….…64 Explanation ……………………………………………………………………65 Parameter Discreption ……………………………………………………….65 Performance Enhancement Plot ……………………………………………67 IBS Design Verification and Analysis. ……………………………………68 Explanation ………….……………………………………………….… ..68 Cell site Information form ………………………………………………..69 Trunking Diagran Verification……………………………………………70 RLT & ARLT Analysis Report……………………………… …………………76 Parameter Descreption …………...…………………………………….76 RLT Performance Improvement Plot ………………………………….78 Explanation ……………………………………………………………….79 ARLT Improvement Plot …………………………………...……………80 Congestion Relief using TRHO …………………………………………..………81 Advantages ……………………………………………………………….81 Parameter Descreption ………………………………………………….82 Setting in the switch ………………………………………...…………..82 Performance Plot …………………………………………………………85 Optimizer Cycle…………………………………………………………………………...86 Optimizer 2.0 Explanation ……………………………………………………….86 TCH / BCCH Plan Generation ………………………….…………………..87 BSIC Plan Generation ………………………………………………………87 Optimizer Result, Before and After Iterations …………………………………87 BCCH and TCH Usage Plot ……………………………………………………..87 TRx Interference Distribution ……………………………………………………88 Performance Plot …………………………………………………………………89 EOSFLEX OPERATIONS ………………………………………………………………...91 General Information …………………………………………………………...92 Temporary Table ……………………………………………………………….92 EOSFLEX Release 5.2 Operations …………………………………………93 XML Scripts and bat file ……………………………………………………….94 EOS Scheduler ……………....................................................................... ..97 Scheduler Script ………………………………………………………………...98 Statistics Generated ………………………………………………………….101 Alarm Cause study……………………………………………………..………………..102 Alarm Number 7745 ………………………………………….……………………….104


7

8

9 10

6 (136)

2nd Dec 2007.

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 Check……………………………………………………………120 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)

2nd Dec 2007.

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 ado pted to achieve good Key perform ance Indicater were also covered for performance enhancement of Cellular Network.


1.

8 (136)

2nd Dec 2007.

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

Radio Network Capacity and Traffic .

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

Total Sites in the Network Total TRX in the Network

1362 10569

BTS Software Version: BSC Software Version: OSS Software Version: Switch Software Version:

S 11.5 CD 6.0 S 11.5 CD 6.0 OSS 4 CD 3.0 M12 CD 3.0

Traffic Split is as follows :(For 13th June 2007 from Dashdoard).


2nd Dec 2007.

9 (136)


1.2

10 (136)

2nd Dec 2007.

Cell wise Capacity Utilization

Cell wise capacity utilization Idea Cellular Delhi:

Number of cells which are utilized more than 90% in Idea cellular Delhi Network tend towards a percentage of 44. And there are al so 6% of cells th at 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)

2nd Dec 2007.

1.3

Spectrum Loading.

1.4

BSC and A-Interface Capacity and Utilization

Observations: Total number of BSCs BSC versions used BSS software load

:22 :5 BSC ( BSC 2i ) & 17 BSC ( BSC 3i) :S11.5 CD 6.0


12 (136)

2nd Dec 2007.

NOTE: BSC which have High Utilization can affect the performance of the BSC.Thus cells can be repranted appropriately.

1.5

SDCCH Utilization and Failure Observation.

SDCCH availability ........................../av a_63a 95.26 % Dynamic SDCCH allocation (TCH reconfigured to SDCCH )Attempts………/c1154

.


13 (136)

2nd Dec 2007.

T3101 expired (S7) .........................../c57020 SDCCH drop ratio without T3101 expiry....../sdr_4

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

LAC Subscribers and Paging analysis.

There are 26 LAC Created under 3 MSC. Cells planned under different LAC are as shown below.


14 (136)

2nd Dec 2007.

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)

2nd Dec 2007.

Cells of the same Site are given different LAC. LAC distribution is seen uneven in some of the geographical area for Idea Cellular Delhi,which can cause High signaling load due to high usage of SDCCH.


16 (136)

2nd Dec 2007.

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)

2nd Dec 2007.

FOR HANDOVER Idea Cear DELHI: 1.7 1.7

Handover Cause Distribution

USES FOR HANDOVER Idea Cellular DELHI: CAUSES FOR HANDOVER Idea Cellular DELHI:

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)

2nd Dec 2007.

Frequency Utilization:

Frequency Distribution Idea Cellular Delhi.

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

Network Database Discrepancies :

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)

2nd Dec 2007.

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)

2nd Dec 2007.

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)

2nd Dec 2007.

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)

2nd Dec 2007.

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)

2nd Dec 2007.

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

Executive Summary on the Network.            

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

EDGE / GPRS Configuration Settings:

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


24 (136)

2nd Dec 2007.



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

1418 cells 2610 cells 33 cells 13 cells 901 cells 2041 cells 165 cells 35 cells 919 cells 9 cells 4 cells

GPRS / EDGE Parameter Discrepancies 

Priority  



BCCH: 3096 cells Non-BCCH: 978 cells  It is recommended to have at least 2 GTRXs in cells prioritised with BCCH  This Priority helps in allocation of Data calls on the enabled priority first, and then move on to remaining TRx’s.

Alpha Binary Representation ALPHA (ALPHA) GSM Reference: ETS 300 940 (GSM 04.08) Q3 name: Alpha Modification: Online Range:

0...10 according to the following principle: 0: α=0.0 1: α=0.1 2: α=0.2 ... 10: α=1.0

MML default:

7 (GSM 800 and GSM 900) 8 (GSM 1800 and GSM 1900)

Description:

With this parameter you describe the binary representation of the parameter α.


Related command(s): Note:

25 (136)

2nd Dec 2007.

EUC, EUM, EUO OPTIONAL (GPRS)

This particular Network has the following Settings as listed below: Value  



Total cells:

0.7: 0:

4072 cells 2 cells  Recommended Value: 1

Gamma

GSM reference:

ETS 300 940 (GSM 04.08)

Q3 name:

Gamma

Modification:

Online

Range:

0...62 (dB) with a step size of 2

MML default:

34 (GSM 800 and GSM 900) 36 (GSM 1800 and GSM 1900)

Description:

With this parameter you describe the binary representation of the parameter τ ch for MS output power control.

Related command(s):

EUC, EUM, EUO

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)

2nd Dec 2007.

AGCH

Access Grant Channel requir ement 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.

This Network has the following settings as listed below. Value Total Cells.  

1: 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:

Prefer BCCH frequency GPRS (BFG) GSM reference:

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:

0…2

MML default:

0

Description:

With this parameter you define whether the BCCH TRX or other TRXs are preferred in GPRS channel allocation.

Related command(s):

EQV, EQO

TRX priority in TCH allocation (TRP) GSM reference:

No ref.


27 (136)

2nd Dec 2007.

Q3 name:

trxPriorityInTCHAlloc

Modification:

Online

Range:

0…3

MML default:

0

Description:

With this parameter you define whether the BCCH TRX or other TRXs are preferred in traffic channel allocation.

Related command(s):

EQM, EQO

This Network has the following settings as listed below. Value Total Cells.   



BFG = No; TRP = 1: 300 cells BFG = No; TRP = 2: 3096 cells BFG = Yes; TRP = 2: 678 cells  It is recommended to have at least 2 GTRXs in cells prioritised with BCCH

IFP

Idle mode signal strength filter period (IFP) GSM reference:

ETS 300 940 (GSM 04.08)

Q3 name:

TAvgW

Modification:

Online

Range:

0...25

MML default:

9

Description:

With this parameter you control the signal strength filter period for power control in the packet idle mode.

Related command(s):

EUC, EUM, EUO

Note:

OPTIONAL (GPRS)


28 (136)

2nd Dec 2007.

This Network has the following settings as listed below. Value Total Cells. 4065 cells  9: 9 cells  0:  Recommended Value: 9



TFP

Transfer mode signal strength filter period (TFP) GSM reference:

ETS 300 940 (GSM 04.08)

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):

EUC, EUM, EUO

Note:

OPTIONAL (GPRS) This Network has the following settings as listed below. Value Total Cells. 4065 cells  0: 2 cells  1: 7 cells  0:  Recommended Value: 13

 

NOTE: It is recommended to have at least 2 GTRXs in all cells prioritised as BCCH NOTE: Many cells need additional GTRXs / Value of CDED / CDEF to be increased  A sample list (top 50 such cells) is attached herewith  NOTE: Also many cells are defined with additional GTRXs than required. This would lead to PCU congestion in future and is hence recommended to be reduced  The cells which do not require additional channel seizures (ach_3 = 0) can be reDimensioned to 2 GTRXs after analysing the CDED / CDEF %.  A sample list (cells with more than 3 GTRXs) is attach ed herewith


2.4

29 (136)

2nd Dec 2007.

NSEI Plan Review. Network Service Control Information Elements (IEs)

 

NSEI plan to be re-worked NSEI should be planned on a geographical basis  The Cell sites which are closely located geographically, are expected to have the same NSEI to be used, else may have a possibility of Inter PCU reselection which can constitute to increased signaling and in turn reduction in the overall throughput


30 (136)

2nd Dec 2007.

NSEI – Current Plan Review:

 

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

RAC Plan Review.

Routing area code (RAC) GSM reference:

GSM 04.60

Q3 name:

Rac

Modification:

Online


2.6



31 (136)

2nd Dec 2007.

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):

EAC, EAM, EAO

Note:

OPTIONAL (GPRS)

Paging success rate verses LAC Plan

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)

2nd Dec 2007.

Territory Upgrade.

   

Territory Upgrade Success Rate is 96.338 % 3.662 % of the Territory Upgrade requests are blocked (totally denied) 2.721 % of the Territory Upgrade requests are blocked due to high CS Traffic load 0.940 % of the Territory Upgrade requests are blocked due to lack of PCU Resources (high PCU congestion)  30.529 % of the successful Territory Upgrades are served with lesser radio time slots than requested

PCU Congestion.

CS Traffic.


2.8

33 (136)

2nd Dec 2007.

Multi slot allocation 2911 3000

2500

2000

# Cells 1500

1000

500

65 0 DLMultislot Blocking%

10

7

<1%

>=1%<5%

>=5%<10%

>=10%<20%

2911

65

10

7

Blocking %

2 >=20% 2

DLMultislot Blocking %


 

34 (136)

2nd Dec 2007.

DL Multislot Blocking rate is 0.096 % 49 (out of 2992 cells reported) cells have DL Multislot blocking > 1% on a network level  This is primarily due to lack of radio resources (insufficient time slots).  This can be rectified by TRX addition, & removing faulty / bad time slots from the network (Alarm 7745 may be used for this purpose).

DL Multislot Blocking Low Allocated Success Rate.


35 (136)

2nd Dec 2007.

High Blocking:

DL Multislot Allocation Success:

DL Multislot Allocation Success % 870

900

869

800

700

590 600

500

# Cells

395 400

300

200

148 120

100

0 DLMultislot All ocation Success%

>= 9 9%

>= 90 % < 99 %

>= 8 0% < 9 0%

87 0

120

3 95

>= 70 % < 80 % 869

Blocking %

 

>= 6 0% < 7 0% 5 90

< 60 % 14 8

DLMultislot Allocation Success %

DL Multislot Allocation Success rate is 81.245 % 990 (out of 2992 cells reported) cells have DL Multislot Allocation success > 90 % on a network level Majority of the requests are not entirely denied, but served with lesser Tsl.  This can be improved if equipped with more than 1 GTRX / cell 


2.9 

2nd Dec 2007.

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)

2nd Dec 2007.

The above analysis is done using Nokia ND Report 239.

2.10

EDAP Congestion TBFs wi t ho ut EDAP DL

1400 1225

1200

1000

91 5

800 # Cells 600

51 8

39 0

400 22 2 15 3

200

11 8 66

0 TBFs without EDAP DL

5

49

6

34

1

2

5

10

153

66

518

222

118

1225

390

915

BSC

TBFs wi thou t EDAP DL

TBFs with inadeq. EDAP DL 119929

120000

100000 88265

80000

61714

# Cells

60000

41350

40000

36097 28013

27838

27971

27739

22574

20573

20000

17472 13658

13421

13946

12775

12844

11994

10453

0 T B F s w i t h i n a d e q. E D A P D L

15

18

8

4

41350

22574

13658

88265

2 13421

44 13946

79 1277 5

10 174 72

3 2 8013

18 27838

BSC





72 12844

46 10453

11 36097

5 27739

6 20573

6 1199 29

TBFs wit h i nadeq. EDAP DL

High no. of rejections are observed due to inadequate / no EDAP resource.  Multislot allocation and throughput get affected due to this  Capacity enhancement would be required for these cells  Recommended to have adequate Abis pool devices for EGPRS High rejections also observed due to lack of PCU resources  PCU re-dimensioning to be done on priority

1 27 971

5

10

11994

61714


TBF without EDAP DL

TBF with inadequate EDAP DL

2nd Dec 2007.

38 (136)


39 (136)

2nd Dec 2007.

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)

2nd Dec 2007.

Recommendations: It is recommended to configure GPRS on BCCH TRX, provided there is no limitation on the PCU  Since the power on the BCCH TRX is maintained to be constant, the signaling happens in a good RF environment, as compared to Non-BCCH TRX  The BCCH carrier, is also maintained to be cleaner than the hopping TCH layer, thereby reducing the interference on the BCCH layer It is recommended to have at least 2 GTRXs in all cells prioritised as BCCH  Since the TSLs available on the BCCH TRX is limited, it is recommended to have at least 2 GTRXs, to assist in territory upgrades Geographical allocation of RAC and NSEI  This will aid in better utilisation of the PCU resources, thereby enhancing the performance of the network PCU re-dimensioning to be done on priority  This will aid in better utilisation of the PCU resources, thereby enhancing the performance of the network


3.

41 (136)

2nd Dec 2007.

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

Presentation / Author / Date


42 (136)

2nd Dec 2007.

Transcoder Optimization was carried out on several BSC’s of Idea Cellular Delhi which was Dropping calls on the basic of Transcoder Failure:Parameter Fine tuning was carried out on the BSC Level with the help of Parameter ITCF (Number of Ignored Transcoder Fail) . This Paramet er is used to check how m any Transcoder Failure the system w ill receive before it Releases a part icular calls.

Explanation: After a s peech path connection has been established b etween 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.

Description:ITCF:- Number of ignored transcoder Failures. This parameter defines ,how many successive remote transcoder failure the BSC may receive before releasing the particular Call. Range: 0 to 5 Default: 0. Nokia Tested (2)




2nd Dec 2007.

IT C F P a r a m e t e r fr o m M M L : W i t h t h e h e lp o f m m l c o m m a n d

For internal use 1 © N o k ia S i e m e n s N et w o r k s

“ Z E E O : A L L ” , t h e s t a tu s o f IT C F c a n b e f o u n d o n th e B S C L e ve l .

P r e s e n ta ti o n / A u t h o r / D at e

P e r fo r m a n c e P l o t B D 0 17 :

For internal use 4 © N o k ia S i e m e n s N et w o r k s

P r e s e n ta ti o n / A u t h o r / D at e

43 (136)


P e rf o r m a n c e P l o t B D 0 19 :

For internal use 5 © N ok i a S i em en s N e t w o rk s

P r es e n tati o n / A u t h or / D a te

P e rf o rm a n c e P l o t B D 0 18 :

For internal use 6 © N o k i a S i e m en s N et w o r k s

P r e s e n t a ti o n / A u t h o r / D at e

2nd Dec 2007.

44 (136)


45 (136)

2nd Dec 2007.

P e rfo r m a n c e P lo t B D 0 20 :

For internal use 7 © N o k i a S i e m e n s N e t w or k s

P r e s e n t a t i o n / A ut h o r / D at e

TCH Drop N etwork Level Idea Ce llular Delhi:

TCH Drop call Improvement

For internal use 10 © N okia Siem en s N etworks

Pres entation / A uth or / Date

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

2nd Dec 2007.

Rx Level Min Cell (SL).

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 © N okia Siemens Networks


46 (136)


47 (136)

2nd Dec 2007.

Rx_Level_Min_Cell (SL) ,Optimization Performance :Rx_Level_Min_Cell (SL) Parameters was fine tuned for Four BSC’s (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)

2nd Dec 2007.

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 - 05 -H O S R IM P R O V E M E N T 10000

6 5

1000 4 d a t e o f i m p l i m e n t a t io n R E

100

3 2

10 1 1

2

0

0

7

0 -

7

2

0 -

0

0

7

0 -

7

2

-

0

0

7

0 -

7

2

-

0

0

7

0 -

7

2

-

0

0

7

0 -

7

2

-

0

0

7

0 -

7

2

-

0

0

7

0 -

-

7

2

0

T C H T r a f f ic ( E lr )

For internal use 3 © N o k i a S i e m en s N e t w o r k s

0

7

0 -

7

2

-

0

0

7

0 -

7

2

T C H d ro p

-

0

0

7

0 -

7

2

-

0

0

7

0 -

7

2

-

0

0

7

0 -

7

2

-

0

0

7

S d cch D ro p

0 -

7

2

-

0

0

7

0 -

7

2

-

0

0

7

0 -

7

2

-

0

0

H O F A IL

7

0 -

7

-

P o ly . ( H O F A I L )


D r o p c a l l d u e t o H a n d o v e r : Im p r o v e m e n t ( B S C 0 5 ) .

For internal use 4 © N ok ia S i e m e n s N etw o r k s

P r e s e n t a ti o n / A u th o r / D at e


49 (136)

2nd Dec 2007.

B S C -0 2 H O S R I m p ro v e m e n t Degradation is due to Re-Homing. Resolved on 30th

10000

7 6

Er

% 5

1000

4 100 date of i m p l i m e n t a t io n

3 2

10

1 1

6 1 7

7 1 7

5 1 7

8 1 7

9 1 7

0 2 7

1 2 7

2 2 7

3 2 7

4 2 7

5 2 7

6 2 7

7 2 7

8 2 7

9 2 7

0 3 7

0 -

0 -

0 -

0 -

0 -

0 -

0 -

0 -

0 -

0 -

0 -

0 -

0 -

0 -

0 -

0 -

7

7

7

7

7

7

7

7

7

7

7

7

7

7

7

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

0 0

0 0

0 0

0 0

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

T C H T ra f f i c ( E l r)


T C H d ro p

S d c c h D ro p

H O FA IL

0

P o ly . (H O F A IL )

P r e s e n t a t i o n / A u t h o r / D at e

D r o p c a l l d u e t o H a n d o v e r : Im p r o v e m e n t ( B S C 0 2 ) .

For internal use 6 © N ok ia S iem e n s Ne tw o rks

P r es e n tation / A uth o r / D a te


50 (136)

2nd Dec 2007.

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

1000

5 4

R E

100

d a t e o f i m p l i m e n t a t io n

3 2

10

1 1

2

0 0

0 7

0

7

2

0 7

0 0

7

2

0 0

0 7

7

2

0 0

0 7

7

2

0 0

0 7

7

2

0 0

T C H T ra f f i c ( E l r)


0 7

7

2

0 0

0 7

7

2

0 0

0 7

7

2

0 0

0 7

7

2

0 0

S d c c h D ro p

0 7

7

2

0 0

0 7

7

2

0 0

0 7

7

2

0 0

0 7

7

2

T C H d ro p

0 0

0 7

7

2

HO

0 0

0 7

7

FA I L

P o ly. (H O

FA I L )


H a n d o v e r Im p r o v e m e n t ( B S C 1 2 ) : -

BSC -012 HOSR Improvement 10000

7 6

1000

5 4

100 3

date of implime ntation

2

10

1 1

0

1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 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 0 0 0 0 0 0 0 0 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

T C H T r a f f ic (E lr )


T C H d ro p

S d cch D ro p

H O F A IL

P o ly . (H O F A IL )


Thus this Parameter can be implemented, Network Wide of Idea Cellular Delhi for Better “Handover Performance” Enhancement and “Drop Call” Due to Handover.


3.3

51 (136)

2nd Dec 2007.

LAPD T200 Timer Optimization.

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.

Minimum Software requirement: NOTE: - To have the Timer LAPD-T200 Modified or to view, the minimum software Requirements are. BSC Software: S11.5 CD 4.2 BTS Software: CX 4.1 CD 2.0 Discription:LAPD-T200 Timer:The Timer T200 Can be optimized to achieve a Maximum time the LAPD (Layer-2) transmitter (at the BSC) will wait for an acknowledgment before making a retransmission.


52 (136)

2nd Dec 2007.

Range: 220ms to 1000 msec Default: 220ms. Nokia Tested (780ms) T200 FACCH = 780ms T200 SDCCH = 780ms LAPD-N200 Counter:The counter N200 is used to achieve a maximum number of Retransmission a transmitter will make. LAPD-K Value:The K Value decides the maximum number of unacknowledgement frames a transmitter will allow before holding up the transmission. The K value is has dependency on the SAPI (Service access Point Identifier)

SDCCH Enhancement after timer T200 was finetuned appropriately from 0ms to 780ms (for both FACCH and SDCCH

For internal use 4 © N okia Siemens Networks



53 (136)

2nd Dec 2007.

T 2 0 0 P e r fo r m a n c e e n h a n c e m e n t : W i t h n o D e g r a d a t io n i n T C H D r o p f o r t h is P a r t ic u l a r B S C 1 8 .



Thus this Timer T-200 can be finetuned, Network Wide of Idea Cellular Delhi for Better SDCCH Performance Enhancement

3.4

Level and Quality Handover Decission Analysis.


54 (136)

2nd Dec 2007.

HANDOVER DETECTION ANALYSIS USING WINDOW, WEIGHTING, THRESHOLD, & NX / PX - OPTIMIZATION PERFORMANCE FOR LEVEL AND QUALITY HANDOVER CRITERIA. IDEA CELLULAR DELHI. 24th Aug 2007 .

Stenin.N.P Networks, and S ervice Optimipation.

.

Nokia.India

H A N D O V E R F O R ID E A

2 4

th

O P T IM IZ A T IO N

D IF F E R E N T C E L L U L A R

P E R F O R M A N C E

H A N D O V E R

,

C R IT E R IA :

D E L H I.

A u g 2 0 07 .

For internal use 2 © N ok ia S ie m e n s N et w or k s

P r e s e n t a t i o n / A ut h o r / D a t e

The Window and Weighting have dependency on the raw measurement done on the SACCH (480msec) for different Handover Criteria’s.


55 (136)

2nd Dec 2007.

         

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)

2nd Dec 2007.

Parameters associated with Level Handover in the Down Link: LDWS: Level Down link Window Size. LDW:-Weighting. LDR:-Threshold Level Downlink Rx Level. LDP (Px):-Number of samples to be satisfied out of the Nx. LDN (Nx):-Total Number of Averages.

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 SACCH’s 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 SACCH’s). So in this scenario there will be 6 SACCH’s 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)

2nd Dec 2007.

This Parameter has a dependency on the DTX ( Discontinuous Transmission) If Discontinuous Transmission in the Down link is switched off then the LDW Value should be set to 1, stating all SACCH’s taken into consideration. And in cause if Discontinuous Transmiss ion in the Down link is switched on, then the LDW 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. LDR:-Threshold Level Downlink Rx Level:Description:This Parameter compares the average values of signal strength in the Down link direction for triggering the handover process. In other words with this parameter one can set the threshold for Rx Level in the downlink. The averages has to overcome the value set by this particular parameter LDR. Range: -110 to -47dBm. MML Default: -95 dBm. LDN(Nx):-Total Number of Averages. Description:This Parameter, states number of Averages that have to be taken into account when making a Level based Downlink 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. LDP(Px):-Number of samples to be satisfied out of the Nx . Description:This Parameter, states the number of averages that should satisfy the threshold (LDR), out of the Total averages (LDN-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 downlink handover. 3(PX) out of 4(NX). NOTE:-NX should always be greater than PX. Diagram showing, how decision is made for Level based Downlink Handover:


2nd Dec 2007.

[ 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. Period. Range: 1 SACCH to 32 SACCH. SACCH. MML Default: 6 ( SACCH Period ). Example:Example:-

58 (136 (136))


59 (136 (136))

2nd Dec 2007.

If LUWS is set to a value of 6,means that for the consecutive 6 SACCH’s 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 SACCH’s). So in this scenario there will be 6 SACCH’s 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 off then the LUW Value should be set to 1,stating all SACCH’s taken into consideration. And in cause if Discontinuous Transmiss ion in the UP link is switched On, 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 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. link. The averages has to overcome the value set by this particular parameter LUR. Range: -110 110 to -47d -47dB Bm. MML Default: -95 dBm. LUN (Nx):-Total Number of Averages. 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. 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 NOTE:-If the decision have to be speeded up or slowed down, this parameter can be reduced or Incremented appropriately. 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. Exam Exampl ple: e: - If the value set is 3, then there should be a minimum of 3 averages that should satisfy the threshold threshold of the total of 4 averages (NX) for a decision decision making for Level based based UP link handover. handover. 3(PX) out of 4(NX).


60 (136 (136))

2nd Dec 2007.

NOTE:-NX NOTE:-NX should always be greater than PX.

[ CASE III ] QUALITY HANDOVER IN THE DOWN 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 Parameter has a dependency dependency on the DTX DTX ( Discontinuous Discontinuous Transmissi Transmission) on) If Discontinuous Transmission in the Down link is switched off then off then the QDW Value should be set to 1,stating all SACCH’s taken into consideration. And in cause if Discontinuous Transmiss ion in the Down link is switched On, 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 of 1. QDR:-Threshold Quality Downlink Rx Qual:Description:This Parameter Parameter compares the values of signal quality quality in the Down link direction direction for triggering triggering the handover process. In other words with this parameter one can set the threshold for Rx Quality in the downlink. downlink. This value value has to overcome overcome the value set by this particular particular parameter parameter QDR. Range: 0 to 7. MML Default: 4 (1.6% to 3.2%). QDN (Nx):-Total Number of Averages. Averages.


61 (136)

2nd Dec 2007.

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)

2nd Dec 2007.

[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 SACCH’s taken into consideration. And in cause if Discontinuous Transmiss ion 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)

2nd Dec 2007.

QUN (Nx):-Total Number of Averages. Description:This Parameter, states number of Averages that have to be taken into account when making a Quality based UP link 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. QUP (PX):-Number of samples to be satisfied out of the Nx. Description:This Parameter, states the number of averages that should satisfy the threshold (QUR), out of the Total averages (QUN-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 UP link 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 QUWS is by default set to one. H A N D O V E R D I S T R IB U T I O N B E F O R E A N D A F T E R O P T I M I Z A T IO N (Netw ork Leve l) :-

For i nter nal use 24 © N o k ia Si em en s N etw or k s

P res en ta ti on / A uth or / D ate


64 (136)

2nd Dec 2007.

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

IBS Parameter Optimization.

IBS OPTIMIZATION PERFORMANCE , USING UMBRELLA HANDOVER CONCEPT: IDEA CELLULAR DELHI. 4th July 2007 .

UMBRELLA HANDOVER CONCEPT: Umbrella handovers are used in scenarios, in which the handover is to Happen from external server to in building system.

In the umbrella handover concept, the in building system will have to be set as lower layer (Micro) as seen by external server (Macro).

The umbrella handover concept was applied for IBS site “HYATREG 2”of


65 (136)

2nd Dec 2007.

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.

Performance Enhancement Plot:


2nd Dec 2007.

P e r f o rm a n c e E n h a n c e m e n t P l o t:

For i nter nal use 6 © N o k ia S i e m en s N etw o rk s

P res en ta ti on / A uth or / D ate

66 (136)


67 (136)

2nd Dec 2007.

Performance Enhancement Plot:



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)

2nd Dec 2007.

IBS Design Verification and Analysis

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: •

•

•

•

•

•

•

Idea is having own IBS implemented in this Bldg. 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.


BTS CONFIGURATION DETAIL FORM.

2nd Dec 2007.

69 (136)


70 (136)

2nd Dec 2007.

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. PARK ROYAL HO TEL DELHI

T R U N K IN G D I A G R A M ULTRA MINI BTS SECTOR 1

LEVEL 3

15m

A

SHAFT 1

B

SHAFT 2

C

SHAFT 3

D

SHAFT 4

5m

A1-L4

19.85dBm

A1-L5

19.3 dBm

5m

A

10m 15 m 5m

A1-L6

19.85dBm

A1-L7

19.3dBm

A1-L8

19.85dBm

A1-L9

19.3 d B m

5m

10m 30m 5m

5m 10m 15m 5m

A1-L10

19.85dBm

A1-L11

19.3dBm

5m

10m

L E V E L 4 T O L E V E L 1 1 - G U E S T F L O O R S - SH A F T 1

1


71 (136)

2nd Dec 2007.

PARK ROYAL HO TEL DELHI

TRUNKING DIAGR AM 10

5m

20 m

B

10 m

A2-L4

17.75dBm

A2-L5

18.3 dBm

A2-L6

17.75 dBm

10 m

5m

30 m

5m

10 m

10 m

5m

10 m

10 m

A2-L7

19.4 dBm

A2-L8

19.95 dBm

A2-L9

19.4 dBm

A2-L10

18.85 dBm

A2-L11

19.4 dBm

A2-L12

18.85 dBm

LEVEL 4 TO LEVEL 12- GUEST FLOORS-SHAFT 2

5m

A3-L4

19.85dBm

A3-L5

19.3 dBm

5m

C

10 m 15 m 5m

A3-L6

19.85 dBm

A3-L7

19.3 dBm

A3-L8

19.85 dBm

A3-L9

19.3 dBm

5m

10 m 30 m 5m

5m 10 m 15 m 5m

A3-L10

19.85 dBm

A3-L11

19.3 dBm

5m

10 m



72 (136)

2nd Dec 2007.

P A R K R O Y A L H O T E L D E LH I

TRUNKING DIAGRAM

5m

A4-L4

19.85 dBm

A4-L5

19.3 dBm

5m

D

10 m 15 m 5m

A4-L6

19.85 dBm

A4-L7

19.3 dBm

A4-L8

19.85 dBm

A4-L9

19.3 dBm

5m 10 m 30 m 5m

5m 10 m 15 m 5m

A4-L10

19.85 dBm

A4-L11

19.3 dBm

5m

10 m



73 (136)

2nd Dec 2007.

PARK ROYAL HOTEL DELHI

TRUNKING DIAGRAM ULTRA MINI BTS SECTOR 2

LEVEL 3

5m

A1-L0

15.35 dBm

A2-L0

14.8 dBm

10 m 10 m 10 m

30 m

40 m

L EV EL - 0

A3-L0

14.6 dBm

10dB 10 m 10 m

A4-L0

14..9 dBm

A5-L0

14.4 dBm

15 m

15 m 40 m 45 m

5m

A6-L0

15.5 dBm

A7-L0

14.1 dBm

A1-L1

18.2 dBm

A2-L1

17.2 dBm

20 m

40 m

5m 15 m 15 m 15 m 30 m

L E V E L 1 - B A N Q U E T F L OO R

A3-L1

16.2 dBm

A4-L1

16.2 dBm

A5-L1

18.7 dBm

40 m

30 m

7d B

10 m 5m

5m

30 m

17.9 dBm

A7-L1

17.2 dBm

30 m

25 m

TO LEVEL S1

A6-L1


74 (136)

2nd Dec 2007.

PARK ROYAL HOTEL DELHI

TRUNKING DIAGRAM

FROM LEVEL1

20 m

L E V E L – S 1 5m 20 m

30 m

20 m

7dB

A1-LS1

16.6 dBm

A2-LS1

15. 5dBm

A3-LS1

16.6dBm

10 m 20 m

15 m

15 m

30 m

10 m

5m

A4-LS1

17.1 dBm

A5-LS1

17.7 dBm

A6-LS1

16.0 dBm

A1-LS2

18.9 dBm

A2-LS2

18.35 dBm

15 m

15 m

L E VE L - S 2- H E AL T H CL UB 5m 20 m 40 m

A3-LS2

16.3 dBm

A4-LS2

14.65 dBm

A5-LS2

14.1 dBm

A6-LS2

18 dBm

30 m 25 m

35 m

10 m

A 7 - L S 2 - H C 15.8 dBm

45 m 10 m 5m

TO LEVEL B2

A8-LS2-HC 15.8 dBm A 9 -L S 2-H C 1 5 .8 d B m


75 (136)

2nd Dec 2007.

P A R K R O Y A L H O T E L D E L H I

T R U N K IN G D IA G R A M

FROM LEVELS2

10m

L E V E L – B 2 25m

5m

7dB

15m

20m

A1-L7

16.5 dBm

A1-L8

15.9dBm

A1-L9

15.4 dBm

15m 15m

A1-L1

18.5 dBm

A2-L1

16.9 dBm

20m 30m

10m

L E V E L – B 1

A1-L1

16.0 dBm

A2-L1

14.3 dBm

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)

2nd Dec 2007.

RLT & ARLT Analysis Report.

RLT(RADIO LINK TIMEOUT) AND ARLT (AMR RADIO LINK TIMEOUT) TEST REPORT AND ANALYSIS. IDEA CELLULAR DELHI. 29th Aug 2007 .

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 f or 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 (136))

2nd Dec 2007.

ARLT: AMR AMR Radio Link Link Timeout:Timeout:Similarly Similarly (ARLT) (ARLT) AMR Radio Radio Link Timeout Timeout can be fine tuned appropri appropriately ately to have performance enhancement on the Drop Call for cell s tending to Drop High on TCH with A MR 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 Value of 20. Nokia Tested 36 SACCH MML COMMANDE @ BSC FOR RLT & ARLT:


2nd Dec 2007.

Performance Improvement with RLT Fine tuning.

The below performance plot shows how cells had performance enhancement “ TCH_COMPLETION_RATE ” after fine tuning RLT from value of 20 to 24 SACCH

Cells improvement in the “TCH_Completion_Ratio” after RLT RLT Fine tuned.

78 (136 (136))


79 (136 (136))

2nd Dec 2007.

The above Diagram shows how RLT is incremented (Steps of 2) on successful decoding of a SACCH, and also Decrement Decrement (Steps of 1) on unsuccessful unsuccessful decoding decoding of Consecutive SACCH. 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)

2nd Dec 2007.

Performance Improvement with ARLT Fine tuning. TCHCompletion Ratio. 92.00 89.00 86.00 83.00 80.00 77.00 74.00 71.00 68.00 65.00

ARLTFinetunned to avalue of 36, dated 7th Aug 2007.

62.00 59.00 56.00 53.00 50.00

7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 7 / 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 0 0 0 / 4 4 / 4 / 5 / 5 / 5 / 5 / 5 / 5 / 5 / 5 / 5 / 5 / 6 / 6 / 6 / 6 / 6 / 6 / 6 / 6 / 6 / 6 / 7 / 7 / 7 / 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 0 0 0 / / 3 6 9 2 5 8 4 7 0 3 6 9 7 0 3 6 9 2 5 8 4 7 0 2 2 2 0 0 0 1 1 1 1 2 2 2 2 0 1 0 4 0 1 1 1 1 2 2 2 0 1 0 0 1

TCHCompletionRatio.



Thus optimizing RLT and ARLT parameters can bring in enhancement in performance on TCH_COMPLETION_RATIO (TCH Drop Call) appropriately

3.8

CONGESTION RELIEF USING TRHO.


81 (136)

2nd Dec 2007.

CONGECTION RELIEF USING (TRHO) TRAFFIC REASON HANDOVER, TEST REPORT AND ANALYSIS. IDEA CELLULAR DELHI. 30th Aug 2007 .

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.

Parameter setting for Congested Cell:


1) 2) 3) 4) 5) 6) 7)

82 (136)

2nd Dec 2007.

AMH Upper Load Threshold => AUT. AMH Max Load of Target Cell => AML. AMH TRHO Guard Time => TGT. THRO Target Level {n} => TRHO. Rx Level Min Cell {n} => SL. AMH TRHO Pbdgt Margin {n} =>ATPM. Ho Margin Pbdgt {n} => PMRG.

Parameter setting for Under Utilized Cell: 1) Ho Margin Pbdgt {n} => PMRG. Parameter Setting at the Switch:MML Commands. To View: ZEPO; To Modify: 1) ZEPI; BTS=“Source & Target cell id” RI=ON; RIM=PER. 2) ZEPH; BTS=“Source cell id” TRHO=ON; OUCT=98. 3) ZEPH; BTS=“Target cell id” TRHI=ON. Parameter Description: 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. Range: -109 to -47(dBm). N (Not used) MML Default: N (Not in use) Tested value -85dBm.

AMH Advance Multilayer Handling: AMH Consists of three different fe atures, 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 Cove rage by distributing traff ic 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 c ongested cell. AMH Dynamically distributes traff ic 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)

2nd Dec 2007.

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 tha n 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)


Tested value -6dBm. MML COMMAND @ SWITCH, “ZEPO”.

RI: Resource Indication Function:-

2nd Dec 2007.

84 (136)


85 (136)

2nd Dec 2007.

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%

TRHO handover statistics ND 155 Check report ND 222 Thus Congestion forms Healy loaded cell can be relived using TRHO appropriately for evenly distribution of traffic in the Cellular Network.

4.

Optimizer Cycle


86 (136)

2nd Dec 2007.

OPTIMIZER CYCLE 2

Date:15th Oct 2007 Stenin. Nokia Siemens Networks.

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)

2nd Dec 2007.

There were several iterations run for better efficacy of Plan and some of the results from the Plan is jotted down along with the Impr ovement in performance from Statistics e xtracted form Nokia OSS. Optimizer Results: Idea Cellular Delhi

BCCH & TCH Usage in the New Plan:


88 (136)

2nd Dec 2007.

TRX’s Interfered, Distribution The total number of TRX’s which were interfered have Come Down in the New Plan. Initially there were about 700 TRX’s 100% Interfered which have reduced to about 250 TRX’s in this scenario of New Plan.

Performance Enhancement with statistical Report.


89 (136)

2nd Dec 2007.

U L & D L Q U A L I T Y I d e a C e l lu l a r D e l h i .

2.60 2.50

2.40

Optimizer Cycle

2.40 2.30

2.20

2.20 2.10 2.00 i l

i l

2.00 a

a

u

u

1.90 Q

Q

1.80 L

1.80 U

L D

1.70 1.60

1.60 1.50

1.40

1.40 1.30 1.20

8 1 6 0 7 0 0 2

2 2 6 0 7 0 0 2

6 2 6 0 7 0 0 2

0 3 6 0 7 0 0 2

4 0 7 0 7 0 0 2

8 0 7 0 7 0 0 2

2 1 7 0 7 0 0 2

6 1 7 0 7 0 0 2

0 2 7 0 7 0 0 2

4 2 7 0 7 0 0 2

8 2 7 0 7 0 0 2

1 0 8 0 7 0 0 2

5 0 8 0 7 0 0 2

9 0 8 0 7 0 0 2

3 1 8 0 7 0 0 2

7 1 8 0 7 0 0 2

1 2 8 0 7 0 0 2

5 2 8 0 7 0 0 2

9 2 8 0 7 0 0 2

2 0 9 0 7 0 0 2

6 0 9 0 7 0 0 2

0 1 9 0 7 0 0 2

4 1 9 0 7 0 0 2

8 1 9 0 7 0 0 2

2 2 9 0 7 0 0 2

6 2 9 0 7 0 0 2

0 3 9 0 7 0 0 2

4 0 0 1 7 0 0 2

8 0 0 1 7 0 0 2

2 1 0 1 7 0 0 2

1.20

Date . U L Q u a lity

D L Q u a lity

Po ly . ( DL Q u a lity )

Po ly . ( UL Q u a lity )

H O P e r fo r m a n c e I d e a C e l lu l a r D e l h i:

40000 Optimizer Cycle

38000

36000

34000

32000 l E ic

(

30000 f

f a T

r

28000

26000

24000

22000

20000

8

2

6

0

4

8

2

6

0

4

8

1

5

9

3

7

1

5

9

2

6

0

4

8

2

6

0

4

8

2

1 6 0 7 0 0

2 6 0 7 0 0

2 6 0 7 0 0

3 6 0 7 0 0

0 7 0 7 0 0

0 7 0 7 0 0

1 7 0 7 0 0

1 7 0 7 0 0

2 7 0 7 0 0

2 7 0 7 0 0

2 7 0 7 0 0

0 8 0 7 0 0

0 8 0 7 0 0

0 8 0 7 0 0

1 8 0 7 0 0

1 8 0 7 0 0

2 8 0 7 0 0

2 8 0 7 0 0

2 8 0 7 0 0

0 9 0 7 0 0

0 9 0 7 0 0

1 9 0 7 0 0

1 9 0 7 0 0

1 9 0 7 0 0

2 9 0 7 0 0

2 9 0 7 0 0

3 9 0 7 0 0

0 0 1 7 0 0

0 0 1 7 0 0

1 0 1 7 0 0

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

D a t e . .. T CH T ra f f ic ( Elr )

H O F ail

Po ly . ( HO F a il)

7.80 7.60 7.40 7.20 7.00 6.80 6.60 6.40 6.20 6.00 5.80 5.60 5.40 5.20 5.00 4.80 4.60 4.40 4.20 4.00 3.80 3.60 3.40 3.20 3.00 2.80 2.60 2.40 2.20 2.00 H

a

n

d

o

v

e

r

_

F

a

li


90 (136)

2nd Dec 2007.

TCH & SDCCH DROP:Idea Cellular Delhi.

40000

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

Optimizer Cycle 37500

35000 . )r l E( ic

32500 ff a r T

30000

27500

25000

o r D _ H C C D S , p o r D _ H C T

8 2 3 2 8 0 3 0 8 1 3 1 8 2 3 2 8 0 2 0 7 1 2 1 7 2 2 2 7 0 1 0 6 1 1 1 6 2 1 2 6 0 1 0 6 1 1 1 6 - 0 6 - 0 6 - 0 7 - 0 7 - 0 7 - 0 7 - 0 7 - 0 7 - 0 8 - 0 8 - 0 8 - 0 8 - 0 8 - 0 8 - 0 9 - 0 9 - 0 9 - 0 9 - 0 9 - 0 9 - 1 0 - 1 0 - 1 0 0 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 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 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

Date... TCH Tr af f ic ( Elr )

TCH Dr op

SD Dr op

Po ly . ( TCH Dr op )

Po ly . ( SD Dr op )

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.

2nd Dec 2007.

EOSFLE (Release 5.52) OPERATION.

EOSFLEX OPERATIONS. Idea Cellular Delhi 11th-May-2007

Stenin.N.P Networks, and Service Optimipation. Nokia.India.



EOSFLEX Release 5.52:-Extended Operations Flexible Reporting.

91 (136)


92 (136)

2nd Dec 2007.

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).

EOS Scheduler operates with two separate entities. 1) Scheduler Engine. 2) The scheduled content definition.

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.

The reports Excel file offers. 1) Frozen panes (Column header and date / object identifiers are always available) 2) Web Link 3) support for markup coloring 4) support for number formatting 5) Vertical column header (Space saving) Eos scheduler supports file and directory cleanup.

SCRIPT: There are different tables from which the raw counters are to be extracted. Some of the commonly used tables are listed:

Way forward with EOSFLES Release 5.52. Log in using:- http://localhost


Main Report Selection Window:-

2nd Dec 2007.

93 (136)


2nd Dec 2007.

XML (Script for Voice) Example shown Script for TCH Drop Call.

94 (136)


95 (136)

2nd Dec 2007.

sum (sdcch_busy_att) sum (tch_seiz_due_sdcch_con) sum(sdcch_seiz_att) sum (sdcch_radio_fail) sum (que_all_ass_req_att) sum (drop_after_tch_assign) p_nbsc_traffic traffic sum (msc_i_tch_tch) sum (msc_i_sdcch_tch) sum (msc_i_tch_tch_at) sum (msc_i_sdcch_tch_at) sum (msc_i_sdcch_at) sum (msc_o_tch_tch) sum (msc_o_sdcch_tch) sum (cell_call_clr) p_nbsc_ho ho Nvl (decode (((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 )), 0, 0+null, 100-100* (Traffic.tch_radio_fail+ Traffic.tch_rf_old_ho+ traffic.tch_abis_fail_call+ traffic.tch_abis_fail_old+ traffic.tch_a_if_fail_call+ traffic.tch_a_if_fail_old+ traffic.tch_tr_fail+ traffic.tch_tr_fail_old+ traffic.tch_lapd_fail+ Traffic.tch_bts_fail+ traffic.tch_user_act+ traffic.tch_bcsu_reset+ traffic.tch_netw_act+ traffic.tch_act_fail_call)


96 (136)

2nd Dec 2007.

/ ( 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) Tch Comp ratio format %3.2f all Drop Call Ratio (dcr_3i) (%) p_nbsc_traffic 100
Idea_kpi
about_eosflx.htm gos_new 20< /bts_number> reuse on< /wrap_header> RC BTS 2g 20 20 2g_ran


97 (136)

2nd Dec 2007.

Note: The above script is saves @ D:\raproot\conf\nrbasic\eosflx\2g_ran\reports

The “ui _conf.xml” file idea_nw_rc idea_gprs.xml idea_gos.xml idea_edge.xml idea_KPI2.xml idea_KPI3.xml idea_KPI3.xml

Note:

The above script is used for display in the “Main report selection window”. After script is run to fetc h 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 f iles 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

SCHEDULER (. bat file) The scheduler script for different BSC. cd /raproot /apps/scheduler perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC1_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC10_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC11_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC12_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC13_CS_BH


98 (136)

2nd Dec 2007.

perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC14_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC15_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC16_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC2_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC3_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC4_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC5_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC6_CS_BH perl eos_scheduler.pl XML=IDEA_BSC_CS_BH.xml SCHED_REPORT=RepSuite_IDEA_KPI3.xml SCHED_INSTANCE=BSC7_CS_BH

Note:This script is stored @ D:\raproot \apps\scheduler The script for scheduler is stored as “ .bat ” file.

Scheduler script. europe idea_nw_rc /dlbrowser/{today}/


99 (136)

2nd Dec 2007.

All idea_nw_rc %cgi-bin%nrbasic/eosflx/eosflx.pl B=Generate IMPL=2g_ran UI_CONF= idea_ui_conf.xml DROP_XML=idea_KPI3.xml DROP_DSN={dsn} DSN_ATT=RC_2G PARENTLIST=190657 OBJECT=SEG_ID OBJECT_LEVEL=3 Agg =CS_BH Time=Relative Fdate = Tdate = RLength =1 RTselection= Day(s) RCAselection=Absolute Rdate ={yesterday} DROP_SORT= desc Sortby =None Threshold=None Max= Min= SCHEDULE=1 REPORTYPE= KPI= UI=1 MY_SCRIPT_CONF_LINK= script_conf.xml PM RC_2G PM RC_2G BSC10_CS_BH.xls BSC10_CS_BH  idea_report (1 day(s) end {yesterday}) Time Agg: CS_BH Object Type: BSC, Object(s): '190657' Object Aggregation: SCHEDULE=1 UI=1 5,5 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 /odrcache//eosflx_idea_KPI3.xmlidea_nw_rc_CS_BH??.??.????_??.??.????_3_190657__._desc___SE G_ID_.csv BSC_CS_BH_IDEA.zip {xlsfile}, {sumxls}, {sched_csv} RS_mail.csv {xlsfile}, {sumxls}, {zipdest}


2nd Dec 2007.

[email protected]

Statistical Report Generated The statistical report generated .csv file.

The above stat was generated for a particular BSC Using EOSFLEX.

6.

Alarm Cause study.

101 (136)


102 (136)

2nd Dec 2007.

NOKIA ALARM DESCREPTION AND ANALYSIS ON PERFORMANCE DEGRADATION. - a detailed analysis and field test for some of the Common Alarms and its Causes -

NOKIA India Pvt.Ltd Idea cellular Delhi.

Date:1st August 2007

List Of Important Alarms :

Some of the Important Alarma:-


Alarm Number

2nd Dec 2007.

Description

7745

CHANNEL FAILURE RATE ALARM

2992

bts and tc uns ynchronization clear calls on a interface

2993

bts and tc unsynchronization clear calls on abis interface

7508

RADIO TIMESLOT FAILURE IN TRX

7600

BCF FAULTY

7601

BCF OPERATION DEGRADED

7603

BTS FAULTY

7604

BTS Operation Degraded

7606

TRX FAULTY

7617

SEVERAL CALLS DROPPED DUE TO PROBLEM WITH TRANSCODER

7704

PCM FAILURE

7705

LAPD FAILURE

7715

CONTINUOUS RESTARTS OF BCF-TRX

7725

TRAFFIC CHANNEL ACTIVATION FAILURE

7738

BTS WITH NO TRANSACTIONS

7743

MEAN HOLDING TIME BELOW DEFINED THRESHOLD

2955

TRANSCODER CHANNEL FAILURE

7746

CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD

7767

BCCH MISSING

7939

FORWARD POWER TOO LOW AT TX ANTENNA

8112

FREQUENCY ERROR

103 (136)


104 (136)

2nd Dec 2007.

ALARM NUMBER 7745:- CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD: This alarm helps in finding out the timeslots which are blocked and causing High SDCCH or TCH Blocking.And in some scenarios calls get established on these timeslots and then drops with an cause of “Time out”. Alarm 7745 is explained as described below with an example.

Alarm number 7745 gives information on the Timeslot degraded.

This displays degradation of both SDCCH Timeslot and TCH Time slots that have gone faulty.At the foremost instent a soft reset (Locking that par ticular Time slot and then unlockimg )can help in overcommng the problem.If it is found to have all the Timeslots degraded ,then that particular TRX can be given a reset on a temporary basis. If the Problem still exists then change the TRX. Causes: 1) If Alarm noticed on BCCH Carrier, then swap BCCH /TCH Carrier appropriately. 2a) 7745 on One TRx Only: If there is alarm noticed on one single TRx, then check for SMA Cable(Cable that connects the Radio) at TX Connector to WCxA (Wide band combiner) of the TRx is properly tightned. 2b) 7745 on Two TRx of a cell. If alarm noticed on two TRx’s, then check if there exist, cross feeder in these two TRx’s


105 (136)

2nd Dec 2007.

2c) Noticed on all TRx. Check for Cross feeder, Bad connectors, Connection to DVxA ( Duplexer). Solution: a) Temporary => Inservicing appropriate Time slots. b) Permanent => Replace Hardware (Radio). STATISTICS ANALYSIS:7745. The statistics showing no calls been handled by a particular Timeslot found to be having this alarm 7745 .

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)

2nd Dec 2007.

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)

2nd Dec 2007.

ALARM NUMBER 7601:- BCF OPERATION DEGRADED: This alarm 7601 is generated at the BTS.

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

I. Fault reason: Cabinet I2C bus is jammed. Solution: 1. Switch the site power Off and On. 2. Check the fan unit, the power supply unit and the TRXs. If necessary, replace the faulty units(s). 3. If the fault reappears, replace the cabinet. The units Inside the cabinet can be reused in the new cabinet

II. Fault reason: Incompatible unit presence has been detected in the BTS.


108 (136)

2nd Dec 2007.

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: 1. Check the synchronisation settings of the transmission interface.

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

V.

Fault reason: Flash operation failed in BOI or TRX.

Solution: 1. Replace the BOI. 2. BOI=Base station operation Interface unit 3. If it is TRX change the TRX


109 (136)

2nd Dec 2007.

Descrpition of Supplementary information: 1-6

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

ALARM NUMBER 7738:- BTS WITH NO TRANSCATIONS This alarm helps in finding out that BTS has had no successfully terminated calls, SDCCH or Transcations GPRS TBF releases during the supervision period. 



 

This alarm is used for supervising the BTS traffic capacity and to indicate sudden loss of service on BTS level This is a BTS Specific alarm. BF=Temporary Block Flows

No SDCCH Transaction

Descrpition of Supplementary information:


01 =

2nd Dec 2007.

No successful SDCCH seizures

02 = No successful TCH seizures 03 = No successful SDCCH nor TCH seizures 10 = No successful GPRS transactions 11 = No successful SDCCH seizures and No succesful GPRS transactions 12 = No successful TCH seizures and No succesful GPRS transactions

13 = No successful SDCCH nor TCH seizures nor GPRS transactions

NO SDCCH TRANSACTION

110 (136)




NO GPRS TRANSACTION

2.

NO GPRS Transaction

2nd Dec 2007.

111 (136)


2nd Dec 2007.

112 (136)


2nd Dec 2007.

113 (136)


114 (136)

2nd Dec 2007.

Temporary solution: Reset the Sector (BTS) Permanent solution: Replace the Hardware

ALARM NUMBER 7604:- BTS OPERATION DEGRADED Description: Major fault (or faults) has occurred in a unit (or units) that Belong to the sector indicated in the alarm.This alarm belong to particular sector.



Following are the Fault Reasons for BTS Operation Degraded. I. Fault Reason: Remote tune combiner temperature is dangerously high.

Solution: 1. Ensure that the ambient temperature of the base station is within Specified limits. 2. Check the cabinet fans. 3. Replace the remote tune combiner.

II. Fault

reason: Remote tune combiner temperature is low.

Solution: 1. Ensure that the ambient temperature of the base station is within

Specified limits. 2. Check the cabinet heater if it is installed. 3. Replace the remote tune combiner.

III. Fault reason: Rx levels differ too much between main and diversity antennas. Solution:

1. Check the RSSI measurements by BTS Manager. 2. Locate the cause of the alarm (unit, cable, antennas).Check unit , cable and antennas, 3. RSSI: Received Signal Strength indicator. 4. Imp alarm where call gets blocked.


115 (136)

2nd Dec 2007.

Descrpition of Supplementary information: 1-6

XX XX XX XX XX XX 1 2 3 4 5 6

7. Rack (cabinet) number 8. 9.

shelf number slot

10. Type of unit 11. unit number 12. subunit number

This supplementary information is valid for 1 to 3 fault reasons.

IV: Fault Reason: Fault in the chain between power unit and high gain MNxx with.

Supplementary information: By pass

ALARM NUMBER 7744:- EXCESSIVE TCH INTERFERNCE

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 



Supplementary information fields

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)

2nd Dec 2007.

If the time slot is not a TCH time slot, the value is 0 9

the threshold level of excessive interference. The values are 0, 1, 2, 3 and 4

10

the TCH channel's alarm threshold percentage of the time spent In excessive interference, 1 - 100 %. The alarm is generated if at least one TRX time slot reaches the threshold

 

.

These alarms basically indicate the uplink interfencence, check MAIO, HSN. MAIOSTEP Check any Repeaters installed near the site, fine tune the repeaters

ALARM NUMBER 7606:- TRX FAULTY . Descrpition:



Critical fault has occurred in a TRX. This alarm blocks the TRX.



Call drops will be severely with the faulty TRX.



Following are the Fault Reasons for TRX Faulty. I.

.Fault reason: Failure detected during TRX configuring.

Solution : 

Either the TRX is faulty or its frequency band is different from the one that was configured into BSC. Replace the TRX with a functional TRX or with another TRX with correct frequency band.

II.

Fault reason: Antenna connection faulty.


117 (136)

2nd Dec 2007.

Solution :  Check the antenna and cabling. If the antenna and cabling are faulty, correct the problem and run TRX test to cancel the alarm.

If the antenna and cabling are OK, TRX is faulty. Replace the faulty TRX. 

7.

Drive Test Analysis.

Check List for Cell site. For better understanding for enhancement in performance, requiring field analysis, which was carried out for problematic cells in Idea Cellular Delhi Networks.There were Drive carried out for data collection in the following scenarios: Basic Information. Idle Mode Dedicated mode Handover Checks Made. Data Drive (GPRS / EDGE ) The following were the checks made during the Drive test for each of the scenarios. Basic Information from Drive Test.

Site ID Site Name Site Connected to BSC TRX Configuration.


2nd Dec 2007.

Idle Mode Information from Drive test.

Frequencies (Sys info type1) BSIC correctly defined Cell_Reselect_Offset, Temp_Offset Penalty_Time are as planned (sys info3) The Site Radio parameters in Layer3 messages Sys. Info type 3, as planned. The LAC is correctly defined Location Update procedure is checked (If applicable) MO-SMS MT-SMS

Dedicated Mode Information from Drive test.

DL_QUALs for all TRX's is zero below the antenna DL_LEVELs for all TRX's comparable and steady Uplink power control is min below the antenna All TCHs and corresponding TS's are OK Site configuration (Micro / Macro / Umbrella …etc) is correct Mobile Terminating calls Mobile Originating calls are tested OK Rescue and Concentric cells handovers, checked wherever applicable Frequency Hopping is activated.

Handover Data From Drive Test.

Neighbors definition from layer3 type 5 messages is OK Subsequent Handovers from and back to each cell checked OK Handovers to main umbrella(s) and neighbor(s) work fine Intra BSC Outgoing handovers checked OK Intra BSC Incoming handovers checked OK Inter BSC Outgoing handovers with all surrounding BSC's checked OK Inter BSC Incoming handovers with all surrounding BSC's checked OK Inter MSC Outgoing Handovers with all surrounding MSC's (if applicable) checked OK

118 (136)


119 (136)

2nd Dec 2007.

Inter MSC Incoming Handovers with all surrounding MSC's (if applicable) checked OK

Data Drive for GPRS.

GPRS GPRS GPRS GPRS GPRS

Attach PDP Context Activation PDP Context Deactivation Routing Area Update (If applicable) Detach

General Information from Drive Test.

Installed antenna is of the planned type Overall performance and coverage area as expected by a brief drive test

Radio Efficacy Check Per Cell. Site Name:

Site ID:

TRX # Sector 1

1

2

3

4

5

6

7

8

9

10

11

12

1

2

3

4

5

6

7

8

9

10

11

12

1

2

3

4

5

6

7

8

9

10

11

12

Freq. RxLev TRX #

Sector 2

Freq. RxLev TRX #

Sector 3

Freq. RxLev


TRX # Sector 4

1

2

3

Freq.

801 805

808

RxLev

-51

-57

-49

4

120 (136)

2nd Dec 2007.

5

6

7

8

9

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 conducte d 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, Sect or Swap, Cable Swap, Etc can be further analysed with Field Drive testing.

Benchmarking Drive using Swis Qual 7.5 The Benchmarking of 2G networks for Idea, Airtel, Dolphin, Hutch (all GSM), Reliance (CDMA) was conducted with Measurement period from Sept 16, 2007 – Oct 26, 2007 Test done at static locations were SMS, MMS & FTP test. Measurement systems used: SwissQual 7.5 for Voice and Data drive tests SwissQual QualiPoc for SMS & MMS static tests N6680 for GSM, LG RD6000 for CDMA Per operator approximately: 2100 two-minute voice calls (mobile to fixed) evaluated 300 FTP up- and downloads, 300 Emails send and received, 300 HTTP requests, 200 SMS, 60 MMS tests performed 2600 km of routes driven – – –

– –

–

The Benchmarking Tool Swis Qual version 7.5 was used to analyse competator network at Delhi Region for both Voice and Data.The following are the summerised comparision found as described below.

Drive Test session:


121 (136)

2nd Dec 2007.

Simultanious Drive done for Voice and Data, during test.

Data Services Drive Test Measurement Data Session

FTP Download

Attach & PDP Context

HTTP Browsing

FTP Upload

Email

Email

Detach & PDP Context

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.

Executive Summary - Voice Idea shows an average overall voice service performance in Delhi. Call Setup Time of Idea is exceptionally good, also in international comparison they show one of the best statistics here. • •


•

•

•

• •

122 (136)

2nd Dec 2007.

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. Idea’s 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.

Executive Summary – Data The overall data performance for Idea in Delhi can be rated as poor. All data services except SMS have poor performance levels in Delhi. For some of the data services Idea is amongst the poor 20% networks globally. Hutch shows up with a better data performance in Delhi as compared to Idea. Reliance being a CDMA service provider is also good when it comes to data statistics in Delhi. Having used EDGE for almost all the sessions the average throughput of Idea is found to be very low. This is the major reason for having low success rates as well. The MMS performance of Idea needs improvement. Long delivery times and only a 60% success rate puts Idea’s performance amongst one of the most poor performers measured globally. • •

•

•

•

M o b ile S er vic e s Q u a lity in a N u ts h ell Delhi, October 2007 D C Q I

VCQI

top 20 % perform ers internationally

2 4 4

5

international average

1

3

5 2

1

1 ID E A 2 A irte l 3 D o lp h in 4 H u tch 5 R e lia n c e

22

© N o ki a S ie m en s N etw or k s

B en c hm ar k Se r v ic e R ep o r t / P M & RH / 2 0 .1 1.2 00 7

low 2 0% p erform ers internationally


2nd Dec 2007.

V o ic i c e S e rv r v ic ic e Q u a li li t y C S T

VCQI

= Ca Ca l l Se Se t u p T i m e = Call Setu Setu p Success Rate

CCR

= Ca Ca l l Co Co m p l e t i o n R a t e

MOS

= M e a n O p i n i o n Sc o r e

100%

4

2 1 3. 3 3. 7

M O S

CCR

2. 6

3

CST CSSR

C S S R

*)

1 2

123 123 (136) (136)

3 .9 4

100%

9 9 .3 %

5

99.4%

9 8 .2 %

2

3

4 5

9 6 .1 %

98.6%

1

4

3 .6 9

97.0%

4. 5

2

3

4

1

2

3 .6 0

3

4 1 3 .3 8

5

3

5

1 ID E A 2 A irte l 3 D o lp h in 4 H u tch 5 R e lia n c e

9. 4

7 4 .6 %

89.2%

* ) CS CS T sc sc o r e f o r R e l i a n c e s e t t o m e d i a n v a l u e 24

© N o ki ki a S ie ie m en en s N et et w or or k s

B en en c hm hm ar ar k Se Se r v i c e R ep ep or or t / P M & RH R H / 2 0 .1 .1 1. 1. 2 00 00 7

2 .9 5


124 124 (136) (136)

2nd Dec 2007.

Dat ata a Ser Servi vice ce Perf Perform ormance ance

D C Q I

H T T P

F T P D L

F T P U L

S M S

M M S

1

E m a il

G P R S A tta c h

P D P C o n te x t

4 4

2 2

4

4

4

2

5 5 45 1

5 5

5

5 2

5

5

2 1

2

2 1

4

1

4

1 2

12

4

1

1

1 ID E A 2 A irtel 3 D o lph in4 n4 H u tch 5R elia ian c

*) MMSscore orefor for Reliance set to median medianvalue value 35

©No ©Nokia Siemens Networks rks

Benchmark Servic rvice e Report / PM& RH / 20 20.11 .11.20 .2007

The above plot shows Performance for for Voice and Data when compared to other competator Operators at Delhi area.


2nd Dec 2007.

125 125 (136) (136)


126 (136)

2nd Dec 2007.

The table above gives an overview about the most important performance figures collected during this 2G Benchmarking campaign.


8.

2nd Dec 2007.

Nokia Macros:-

Table shows the availability of Macros for differend Nokia ND Reports.

127 (136)


2nd Dec 2007.

128 (136)


2nd Dec 2007.

The Detailed List of availability of Macros for ND and MML is listed above.

129 (136)


9.

130 (136)

2nd Dec 2007.

Summary of Idea Delhi Optimization:

After consecutive effersts put in to optimize Idea Cell ular Delhi Network, with Parameter Optimization, Basic Design reviw, Field Optimization, AMR Finetuning, Data Optimization for 2G and 2.5G, Hardware Fault Verification, Timer Optimization, Alarms Handling and threshold Verification, had the performance enhancement listed below on the Network Level. TCH Drop.

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:

2nd Dec 2007.

131 (136)


SDCCH Drop:

SDCCH Blocking:

2nd Dec 2007.

132 (136)


Handover Failure:

RACH Failure:

2nd Dec 2007.

133 (136)


UL & DL Quality:

2nd Dec 2007.

134 (136)


2nd Dec 2007.

To cover in the Next Review. DAC Performance Analysis Threshold verification for DAC Path Imbalance Analysis Repeater Optimization Analysis AMR Parameter Optimization TMA / TMB Performance Analysis Micro / Macro Cellular Model Analysis Physical Audit Other Methods of KPI Enhancement Discontinious Transmission [DTX] / Reception [DRX]. Transmission related Alarms 2000 series.

135 (136)

2G & 2.5G Optimization Nokia India

Recommend Documents