Network Doctor Reports Course

Babak Kardel Mehrdad Sedaghat April 2008

Topics
Introduction : Network Doctor Operation Report-196: UL and DL Quality, UL Interference Per TRX Report-208: Link Balance Per TRX Report-153: Handover Failure Ratio on Adjacency Report-163: TCH Drop Call Ratio Report-166: SDCCH Drop Ratio Report-204: NETWORK BENCHMARK STATISTICS Report-073: Undefined Adjacent Cells Reports Number 154, 156, 139, 187 and so on

4/8/2008

Introduction: Network Doctor Operation

Introduction- ND Operation (1)

Network Doctor for BSS Network Doctor for BSS offers a menu-based user interface in which you can move up and down the menu hierarchy. All reports are listed in the submenus. Self-documented reports, front-page descriptions, and column headers guarantee that the basic information is always available in a context-sensitive presentation. The descriptions of the counter formulas can be displayed on request. The Network Doctor reports produce an output file which opens in the dtpad editor window. You can modify the report, if necessary, and save it.

Introduction- ND Operation (2)

When running the BSS Network Doctor reports, a common query is made for the time period selected and the scope of the measurement. You can usually define the following parameters: Period of time Today, Absolute date, Relative date ending on the current hour, Relative date ending the previous midnight. Scope of report Maintenance Region, BSC, LAC, one BTS, all BTSs or all IUO BTSs, single Segment, single BCF, BSC SW version, Frequency band of dual band, BCF type for Base Station generation, manual Working Set with BTSs or with BCFs, MSC, and BTS having GPRS traffic.

Introduction- ND Operation (3)

Network performance can be evaluated using KPIs such as TCH drop call ratio. These indicators are either directly mapped to a counter or a formula of counters. Drop call ratio, for example, is currently a formula of several counters. KPIs need to be: monitored on network and area level for seeing the trends. monitored at cell level across the area to spot the BTSs potentially having problems. Often they are referred to as BTS Hit Lists or Top n Lists. analysed for a specific BTS when the BTS has been found on the Hit List. At this point, for example, you may be interested in the behaviour of the cell against a time profile.

Network Doctor for BSS : Main Menu

******************************************* * BSS NETWORK DOCTOR * * v.3.1.9 * * for NetAct OSS3.1ED3, BSC S11 * ******************************************* 1) Fault Management ... 2) Configuration Management ... 3) Performance Management BSS ... 4) Benchmark and analysis ... 5) NetAct Database Administration ... 6) Run a report by identification number 7) Display a model report by identification number 8) Generate auto script by identification number 9) User log 10) Connect as another user s) f) c) q) Search reports containing given formula or counter. Find description of given formula. Change history. Exit

Network Doctor for BSS : Sub Menu

Benchmark and analysis Benchmark 1 ) Performance statistics (heavy benchmark, use small area, 200) 2 ) Network benchmark statistics (heavy, use small area, 204) 3 ) Performance profiles for area, 10 days/24 h (heavy, use small area, 207) 4 ) Quality Survey (800) 5 ) BTS GSM KPI/PI table, dynamic object and time aggregation (205) 6 ) TRX level GSM KPI/PI table, dynamic time aggregation (206) Analysis 7 ) BSC doctor (212) 8 ) BTS analyser (216) 9 ) Base station site check (221) 10) Cell doctor (211) 11) BTS doctor (213) 12) Availability per BSC unit (215) 13) SDCCH, TCH and BSC out HO observation statistics (217) 14) Drop call trace (225) 15) BSC internal HO observation cause statistics (223) m ) Display a model report by ID number r ) Run any other report by ID number q ) Quit

Network Doctor for BSS : Sample

------------------------------------------------------------------------------------------------Report Generation Data ------------------------------------------------------------------------------------------------Date : Wed Sep 26 16:21:56 BST 2007 Menu Command Path : 6 / 132 User / Host : kardel / nscs2 Version / Report : ND BSS v.3.1.9 / 132 ======================================================== = CELLS HAVING SMS ESTABLISHMENT FAILURES = Network: PLMN = Area: BSC - 711883 = Period: from 20070926 to 20070926 = Aggregation: Segment = Threshold : nbr of failures >0 = Sorting : SMS fail ========================================================

Network Doctor for BSS : Sample

==================================================== This report shows cells having SMS establishment failures over a given period. This report can be run on BTS or segment level. Nbr of SMS est.attempts /sms_4 Number of SMS establishment attempts. SMS flr % on TCH /sms_2 SMS establishment failure ratio on TCH. SMS flr % on SDCCH /sms_3 SMS establishment failure ratio on SDCCH. Tot SMS flr % /sms_1 Total SMS establishment failure ratio. ====================================================

Network Doctor for BSS : Sample

============================================================== Cells having SMS establishment failures between 20070926 and 20070926 Nbr of SMS flr SMS flr Tot SMS est. % % SMS flr Seg attempts on TCH on SDCCH % ID sms_4 sms_2 sms_3 sms_1 -------- --------------------------57 15 11.11 0.00 6.67 85 47 0.00 2.13 2.13 103 155 9.09 0.69 1.29

BSC Segment name --------------- --------------------B067N N2680B B067N NI21021A B067N NI21040A

==============================================================

Web-Based Browser
Network Doctor Browser in the Regional Cluster
Network Doctor Browser (ND Browser) is an optional web-based application that allows you to access the ready-made BSS reports provided by the HP-UX-based Network Doctor application.

ND Report-196:
UL and DL quality, UL interference per TRX

Contents
1. SAMPLE OF REPORT 2. DESCRIPTION 3. ADVANTAGE 4. ANALYS 5. EXPERIENCES 6. INFORMATION

Sample of Report 196 (Part 1)

Sample of Report 196 (Part 2)

Sample of Report 196 (Part 3)

Description of Report 196

This report have three parts:
Part 1: UL, DL Quality and UL Interference per TRX Part 2: Interference profile Part 3: Frequency profile

Advantage of Report 196

This report can be used to find hardware problems such as TRX faulty, VSWR, feeder and sector swap. Also this report can be used to detect interference and overshooting.

Analyze of Report 196

PART 1: TRX HIT LIST
For each TRX reported: q0..7 (%) UL /ulq_2 Cumulative % of uplink call samples. Target value example: q5 over 98 %. q0..7 (%) DL /dlq_2 Cumulative % of downlink call samples. Target value example: q5 over 98 %. Call min /trf_32a Call time in minutes counted from samples. The max call time for a TRX in a 6 hours period in a day=1 day* 6 hours*60 mins*8 RTSLs*2 (HR)= 5760 min Call dif /trf_21a The ratio of call samples of the most loaded TRX to that of the least loaded TRX in the same BTS. Sorting the report by using this value may help to detect abnormal traffic distribution in a cell. Intrf /itf_4 Average interference band (1-5, 5 being the worst) Freq Frequency of TRX. 'chgd' = frequency has been changed during the period. Blank means that there has been no calls.

Analyze of Report 196

Quality classes:
The quality classes are as defined in GSM recommendation GSM 05.08 (8.2). The calls are sampled every 480 ms for the quality class. Quality class info is used on Abis but BSC converts the quality classes into BER % figures using the default values. (Power control measurement shows BER figures). Class BER (GSM 05.08) ***** ****************** qua 0 (BER < 0.2%) qua 1 (BER 0.2 - 0.4%) qua 2 (BER 0.4 - 0.8%) qua 3 (BER 0.8 - 1.6%) qua 4 (BER 1.6 - 3.2%) qua 5 (BER 3.2 - 6.4%) qua 6 (BER 6.4 - 12.8%) qua 7 (BER >12.8%) The rule of thumb is that in quality classes 0-5 the MS user does not yet feel that the quality is bad.

Analyze of Report 196

UL Interference:
Band indicates the average interference band of TCH (idle). If there is no interference (uplink), average band should be 1. The band limits are defined in cell parameters by setting the boundaries in the interference averaging parameter set. ------------------ boundary 0 (value fixed: -110dBm) band 1 ------------------ boundary 1 (value eg.: -105dBm) band 2 ------------------ boundary 2 (value e.g.: -100dBm) band 3 ------------------ boundary 3 (value e.g.: -95dBm) band 4 ------------------ boundary 4 (value e.g.: -90dBm) band 5 ------------------ boundary 5 (value fixed: -47dBm)

Analyze of Report 196

PART 2: INTERFERENCE PROFILE
For each TRX exceeding the thresholds and having interference a 10day/24h breakdown is shown. - Check the 10-day/24-hour breakdown charts to find out what the pattern is. - If you suspect that the interference is from the BS itself (constant band 5 interference e.g. in all sectors) you may set the power to minimum for a while (this means that calls cannot be made!) and check from the BSC MML with ZERO command if the interference level has gone down in idle time slots. Then put the power back to the initial level. - After you have found the cells with obvious external UL interference you may a) mark the cells having a similar interference pattern on the map with the same colour and see if the antenna directions point to a certain place - It is also a good idea to check whether the cell is not reported by report 062, which could mean interference from an own adjacent cell. b) use Undefined Adjacent Cell measurement (possibly with the idle state BA list to define what are the strongest frequencies in the band that are not adjacent cells. c) You may also run the report 216 to get more details about the cell.

Analyze of Report 196

PART 3: FREQUENCY PROFILE

For all TRXs exceeding the thresholds and having frequency changed during the given time period a 10day/24h breakdown is shown. The value of zero means that there are no calls. Frequency changes must be considered when analysing interference behaviour.

Analyze of Report 196

Part 1 more analysis:
If 1 TRX in a cell has low quality : a- TRX faulty ; There is 7607 TRX operation degraded or 7530 TX output power level decreased alarm b-TX or RX jumper is out of work ; if TRX has no alarms and DL qual is low then TX jumper is out of work and when UL qual is low then RX jumper is out of work. If 1 TRX has no traffic or low traffic and call diff in cell is high and all RTSLs of this TRX is idle (ERO command), or TRX is block TRX then TRX is faulty. When BCCH TRX is faulty, the frequency of TRXs in this cell will change because BTS replace BCCH to a normal TRX. In these problems we can replace fault TRX with another TRX and check wiring before changing fault TRX. This way sometimes solves problems.

Analyze of Report 196

VSWR problem; 2 TRXs of a feeder in a BTS have low qual Feeder swap; 2 TRXs of a feeder in a BTS and 2 TRXs of a feeder in another BTS in same BCF have low qual Sector swap; all TRXs of 2 BTSs in same BCF have low qual without overshoot or interference Data base swap; it is like feeder or sector swap or cell has no traffic Overshoot ; all TRXs of a BTS have low qual. We have to check report 232 and site situation. Interference: a- interference in all TRXs; cells with same Frequency or same HSN, interference is from the BS itself (Talk family sites or 6+6+6 sites), external UL interference, overshoot b- interference only in BCCH TRX; check cells with same frequency around this cell and overshooting cells, replace BCCH to another TRX c- interference only in TCH TRXs; check cells with same frequency around this cell if cell use BB hopping, check HSN in cells with RF hopping, overshoot.

Sample 1 - N255A Call drop

Sample 1 - N255A Tems event

Call drop in N255A was happened after an intracell handover. N255 has a 6+6+6 configuration and has interference.

Sample 1 - N255A TCH ass fail

Sample 1 - N255A TA

Sample 1 - N255A report 196

Faulty in TRX 3 of N255A or in RX jumper

Sample 1 - N255A report 208

High DL path loss in TRX 3 of N255A

Sample 1 - N255A Alarm

TRX 3 of N255A is faulty

Sample 2 N2707C VSWR

Sample 3 N702B,C feeder swap

Sample 4 N010 data base swap

Sample 5 N032B interference and overshoot

ND Report-208:
Link Balance Per TRX

Contents
Sample of Report ND 208 Description of ND 208 Advantage of ND 208 Analyze (Examples) of ND 208 Information

Sample of Report 208

Description of Report 208

Loss from MS to BTS (UL & DL)

DL Path
Jumper loss between TRX and combiner Combiner loss Jumper loss between combiner and feeder Feeder loss Jumper loss between feeder and antenna

UL Path
Jumper loss between antenna and feeder Feeder loss Jumper between feeder and duplexer duplexer loss Jumper between duplexer and TRX (main and diversity)

Description of Report 208

For having balanced coverage, DL loss should be equal to UL loss Ideally (DL Loss-UL Loss=0). if DL and UL paths be not balanced for example DL loss be higher than UL loss- then BTS receives good level from MS but MS receives low level from BTS and the quality of call in one direction will be weak, cause dropped call. DL Path Loss = BS Power Combiner Loss DL Signal Strength UL Path Loss = MS Power UL Signal Strength Normal Path Loss in DL & UL : 100~115 dbm Absolute of Normal Balance : < 3~4 dbm Delta: Deference between lowest and upper link Balance in deferent TRXs Delta shows if the several TRXs in a cell have the same situation or not. We should detect faulty path and solve it. Problems: Rx-Tx BTS Jumper Problem, Combiner Problem, Feeder line Problem, Upper antenna Jumper Problem, loosing connectors and Antenna problem.

Advantage of Report 208

ND Report 208 is a good report for Nokia BTS troubleshooting. BTS engineers can use this report for detecting faulty objects and replace them and check again if the problem resolved.

Report 208 VSWR Problem

Delta > 3 Unbalanced Link

N2007B has VSWR Problem

VSWR SolutionConnector Loosing

VSWR Problem was solved in N2007B.

Report 208 Feeder Problem

Before Changing Feeder After Changing Feeder

Feeder Problem in N990B (VSWR in middle of Feeder)

Report 208 Jumper Problem

Case1: Jumper from TRX 4 to combiner loose (check connectors at both ends)

Report 208 Jumper Problem

Case2: Jumper from Duplexer to TRX 4 (check connectors at both ends)

Report 208 Feeder Problem

Case3: Check common feeder line from Top of cabinet to Antenna port ( loose
connectors at either end or High VSWR problem, TRX 2&4 in this case use the same feeder)

In this case, the Path imbalance (DL-UL) varies between +1.6 to -4dB which doesnt tell much BUT DL pathloss variations between TRXs is from 112.8 to 136dB & UL pathloss variations between TRXs is from 111.2 to 140dB DEFINITELY A PROBLEM!

How to identify the worst cells in network?

Import DL & UL pathlosses for all TRXs of all cells into separate columns Use a pivot table to get Min and Max values of dL and Ul pathlosses in a cell Identify all cells with DL TRX pathloss variatons >10dB (for a NW with huge TI quality issues , start with 15dB) The same can be done for UL also A combined analyses for DL& UL with >10dB diff gave a list of 58 cells for UP (West) attached below. Go back to 208 report for detailed analysis

208_HW issues

ND Report-153:
Handover Failure Ratio on Adjacency

REPORT 153 (HANDOVER FAILURE RATIO ON ADJACENCY )

1. SAMPLE OF REPORT 2. DESCRIPTIONS 3. ADVANTAGE 4. ANALYS 5. INFORMATION

REPORT 153 (HANDOVER FAILURE RATIO ON ADJACENCY )

Source ****** SEGMENT NAME (ID) BCF NAME BSC NAME BAND BCF TYPE Target ****** SEGMENT NAME (ID) HO=> HO=> HO=> <=HO <=HO <=HO Target BCF NAME **** **** **** **** **** **** ****** BSC NAME Att Blck Fail Fail Blck (%) (%) (%) (%) Att LAC CI BAND BCF TYPE

------------------ ------ ---- ---- ---- ---- ------ ------ -----------------N2219C (63) N215 B026N GSM1800 UltraSite N230A (28) N217 B026N GSM900 UltraSite 58 0 7 0 0 29 0 7 4 0 23 6210 N603A (7) B026N GSM900 UltraSite 0 2214 N456C (72) B017N GSM900 UltraSite

12786 N2215

32268 N456C

REPORT 153 (HANDOVER FAILURE RATIO ON ADJACENCY )

DESCRIPTIONS:
THE ADJACENCIS HAVING HIGH HO FAILURE RATIO , REPORT 153 IS BASED ON THE OPTIONAL BSC MEASUREMENT HO ADJACENT CELL. YOU CAN USE THE THRESHOLDS TO FOCUS ON PROBLEMATIC ADJACENCIES ONLY. THIS FAMOUS REPORT SPEAKS ABOUT HANDOVER ATTEMPTS ,HANDOVER BLOCKS, HANDOVER FAILS FROM ONE CELL TO THE NEIGHBORS AS TARGET CELLS AND VICE VERSA .

REPORT 153 (HANDOVER FAILURE RATIO ON ADJACENCY )

ADVANTAGE: 1. THIS REPORT IS VERY USEFULL TO CHECK HANDOVER

PERFORMANCE FOR A CERTAIN CELL IN BSC

2. WE CAN FIND OUT HANDOVER PROBLEMS (FAILURES)

INCOMING OR ONCOMING HANDOVER

EITHER

3.WE CAN FIND OUT WHICH RELATIONS ARE UNNECESSARY AND

WITH CONSIDERING DISTANCE AND DIRECTION OF RELATION WE CAN DELETE IT SIMPLY.

REPORT 153 (HANDOVER FAILURE RATIO ON ADJACENCY )

ANALYS:
1.IF WE HAVE NONE ATTEMPT FROM ONE SIDE WE FIND OUT THERE IS A PROBLEM FOR THIS RELATION LIKE AS : ONESIDE DIRECTION , HARDWARE PROBLEM , 2. IF WE HAVE NONE ATTEMPT FROM BOTH SIDE WE FIND OUT THAT THERE IS MAJOR PROBLEM, LIKE AS : ERROR DEFINITION NEIGHBORING IN BSC OR THE RELATION IS WRONG AND SHOULD BE REMOVED 3. IF WE HAVE A LOT OF ATTEMPTS BUT WITH HIGH HANDOVER FAILURES WE MUST CHCK INTERFERENCE IN RADIO INTERFERENCE OR CHECK SYNC ALARM FOR TARGET CELL.

REPORT 153 (HANDOVER FAILURE RATIO ON ADJACENCY )

4. IF WE HAVE HIGH ATTEMPTS WITH 100% FAILURE WE MUST COMPARE CELL DEFINITION IN BSC AND MSC. 5. IF WE HAVE ATTEMPTS WITH HIGH NUMBER BLOCKS WE MUST CHECK TCH CONGESTION IN TARGET CELL.

ND Report-163:
TCH Drop Call Ratio

Contents
Sample of Report Explanation Notes Definitions in Report CDR Formulas Example: TR Problem and Solution

Report 163 TCH Drop - Sample

Explanation Notes
ND-Report 163 gives the TCH drop call ratio and the reasons per cell. With this report we can find the most reasons of drop call in TCH channel such as RF , ABIS, Transcoder parts. There is several ways for occupying TCH in a cell: Normal Call Setup, Directed Retry, FAACH Call Setup and incoming Handover. Bids means the sum of total TCH occupation in a cell. It depends on the formula that is using for dcr.

Explanation Notes
There is two type of dropped call (call and old): Dropped call on RF call means that the call on existing TCH will be dropped because of bad radio condition for example bad Rx-Qual or Low Rx-Level. This is considered as RF dropped call. Dropped call on RF old means that the MS wants to take handover from existing TCH channel to a new TCH channel but it can not take handover because of bad condition on radio condition. This is considered as RF old dropped call. and is same for TR, ABIS and Aif parts.

Report 163 - Definitions

Report 163 DCR Formulas

There is 4 formulas for dcr in Report 163. The dcr_3i shows dropped call only on call setup TCH and my experience shows that dcr_3i should not greater than 2-3. dcr_4e includes the handover dropped calls too.

dcr _ 3i = 100

Number of TCH Call Dropped Total Number of TCH Channel Setup because of ( Normal Call Setup & DR Call Setup & FAACH Call Setup)

Example: N2990c: Bids= 1008 +130 + 0 = 1138 Dcr_3i= (Total Dropped Call in Bids)/1138= 75.9%

Transcoder Fail Problem Before AMR

RE-ES SDCCH DROP RATIO BTS Name RF CALL TR CALL

N603A N2101B N2229A N2230C N230C N2223C N229B N717C N603B N2603A N230B N2007B N3047A N455C N2101C N2990A N216C N2676B N2455A N990B N3047B

15317 991 1030 292 5937 541 2794 9121 12817 985 1015 1156 933 7767 842 1729 9234 548 1401 6483 699

19715 18296 12386 6967 9358 9858 4068 10003 21361 20005 503 19658 11067 8195 13801 24778 10335 0 12920 10675 8484

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

1.2 1.1 1.4 0.8 1.3 0.9 1.2 1.4 1.5 0.6 0.7 0.7 1.4 1.4 0.6 0.5 1.2 0.2 1 0.9 0.7

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

We havent Transcoder dropped call before the AMR activation.

T-T HO

Call

Transcoder Fail Problem Before AMR

N219B N1047B N101B N455A N990A N2990B N2990C N2705A N223C N223A NM113A N2705B N676B N717A N219C N2705C N101A N223B N2603C 11947 5656 5806 8623 16643 807 1129 476 4472 3789 226 1784 5490 8683 10681 751 5843 4463 416 15434 4483 5746 5745 22568 0 15365 9560 5638 5469 23 18701 6270 7322 0 8018 4729 10067 15694 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.8 1 0.9 0.7 1 0.4 0.7 1 0.6 0.6 0 0.5 0.5 0.6 0.7 0.4 0.4 0.5 0.7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Transcoder Fail Problem- After AMR

RE-ES SDCCH DROP RATIO RE-ES TCH BTS Name RF CALL TR CALL RF OLD T-T HO

Call

N 2216B N 2455A N 2603C N 2219C N 717B N 2603B N 2990A N 2216C N 2705B N 2717A N 2990B N 2717B N 229A N 2219A

1375 1764 2245 880 14898 1521 1747 744 1099 991 570 1375 12611 838

23951 14135 19857 13798 17235 23705 20819 13451 15566 12306 17485 15281 19020 19179

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

5 .8 0 .4 0 .2 1 2 .1 0 .4 0 .4 1 .1 0 .8 1 0 .9 3 .1 1 .8 1

2 .4 0 .7 0 .5 1 .4 0 .9 0 .2 1 .4 1 1 .2 1 1 .4 1 .3 0 .5 2 .4

2 2 .6 2 1 .6 1 3 .3 1 1 .4 1 1 .3 1 0 .7 1 0 .5 1 0 .1 7 .6 7 .2 6 .4 6 .3 4 .9 4 .6

31 23 14 14 15 11 12 12 9 10 8 11 7 9

The most dropped call is because of Transcoder problem after the AMR activation.

TCSM 112 was SE-NH but it's ET was working. We change the state of ET to SE-NH.

Transcoder Fail Problem-After Solution

Transcoder dropped call resolved with blocking the faulty TCSM. It affected normal Half-Rate so much. (Rep-204)

Transcoder Fail Problem-After Solution

ND Report-166:
SDCCH Drop Ratio

Contents
Sample of Report ND 166 Description of ND 166 Advantage of ND 166 Analyze (Examples) of ND 166 Information

Sample of Report 166

Description of Report 166

Advantage of Report 166

With this report we can analyze the sdcch drop ratio in details and understand which part has the most effect in drop of sdcch channels in network. Abis and RF are the most common reason for sdcch dropped call. In a optimised network, sdcch dropped call must be below 10% in nokia system.

Advantage of Report 166

Reasons for sdcch dropped call:
TRX problem: whole TRX or Time Slot that SD channel is placed on it may be has faulty. We can check with MML command ZEOL to check the TRXs. We can change the location of sdcch channel and change the faulty TRX. Abis link problem: We can check with MML command ZYMO. O&M team should solve the link problem. Interference: We should check frequency plan of network and check Report196 for interference. A-Link Problem: sometimes bad connectors on BSC or MSC side or some mismatches maybe cause A-Interface fail on SDCCH. O&M and MSC teams should solve the problem.

Report 166 High SD Drop and Solution

N990B had high Sdcch drop ratio

1 Sdcch/8 was on TRX-8 and TRX-8 had alarm

We changed the position of Sdcch/8 from TRX-8 to TRX-2

ND Report-204:
NETWORK BENCHMARK STATISTICS

Contents
Sample of Report ND 204 Description of ND 204 Advantage of ND 204 Analyze (Examples) of ND 204 Information

Description
This Report shows BSC wise KPIs and PIs. SDCCH Failure, TCH Failure, SDCCH Drop, TCH Drop, TCH Traffic, TCH Codecs, HO Causes, HO Success and Failure, RXQuality , We can find in a look that which part has problem: for Example if A-interface or ABIS interface has problem, we can see immediately in this report.

SDCCH Channel

TCH Channel

TCH Codec Versions

Handovers

Handover Causes

UL, DL QUALITY/LEVEL DISTRIBUTION

UL, DL QUALITY DISTRIBUTION PER CODEC

Expeirence: Transcoder Fail in B026N

UL, DL QUALITY DISTRIBUTION PER CODEC

Expeirence: CSSR Problem in B067N

Expeirence: CSSR Problem in B067N

ND Report-073:
Undefined Adjacent Cells

Contents
1. SAMPLE OF REPORT 2. DESCRIPTION 3. ADVANTAGE 4. ANALYS 5. EXPERIENCES 6. INFORMATION

Sample of Report 073

Description of Report 073

NCC BCC BCCH Per dura Nbr of per Nbr of samples Avg DL sig str Sort factor Nework Colour Code of UAC. Base Sation Colour Code of UAC. BCCH carrier number (ARFN) of UAC. Average period duration. Number of periods. Nbr of samples for calculating the average DL signal strength (*100). Average DL signal strength received from UAC. Sorting factor (average level)/1000

Advantage of Report 073

This report can be used to check the network plan for adjacencies,complete analyzation rep 153 and check interference.

Analyze of Report 073

This report gives all undefined adjacent cells UAC (cells measured by MS but not defined as neighbour of the serving cell) for all BTSs in the selected area. If "Active BA list = adjacent cell definitions) or If "Active BA list = idle BA list = 0" (active BA list = adj. cell definitions), BSC uses adj. cell definitions when it matches the BA indexes and the BCCH. If "Active BA list = idle BA list = list 1", BSC uses "list 1" when it matches the BA indexes and the BCCH. Undefined cells measurement is an optional feature in the BSC. UACs with good signal strength and large number of samples are important. Other reports that can be used to check the network plan for adjacencies are 070,071,072,074,075.

Analyze of Report 073

Undefined adj cells (UAC)
BCCH=BCCH of DAC BSIC<>aa Rep 073 can give this UAC

Serving cell
BA List=A

Defined adj cell (DAC)

BCCH=one freq of A BSIC=aa

BCCH=BCCH of DAC BSIC=aa

Rep 073 can not give this UAC but Rep 153 can show HO fail in this BCCH

BCCH<>one freq of A

MS can not measure this cell Rep 073 can not give this UAC

Experiences

1)N2254C - sample that indicates problem in neighbour definition and interference in BCCH frequency 2)NM861B - sample that indicates sector swap 3)N2255A - sample that is not important

Sample 1: problem in neighbour definition and interference in

BCCH frequency

Sample 1: problem in neighbour definition and interference in

BCCH frequency

Serving cell: N2254C UAC: N254A DAC: N097C BCCH=124,BSIC=16 BCCH=124,BSIC=10

Sample 1: Neighbours of N2254C (EAO)

BSC B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N Source BTS BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C BTS-168 N2254C Neighbour N097C N1161C N124A N124B N2048B N2048C N2097C N2124A N2124B N2254A N2254B N2261C N2460B N254B N254C N261C N694A N694B FREQ 124 110 108 116 613 606 587 605 590 603 599 608 607 117 113 123 119 107 NCC 1 2 2 2 1 7 1 1 1 1 1 1 1 2 2 1 1 1 BCC 6 7 6 3 1 7 4 2 2 1 6 3 6 6 7 4 0 4

Sample 1: Find BCCH=124,BSIC=10 from parameter general cell

BSC

BTS

BCCH

BSIC

B023N

BTS-024 N254A

124

10

B021N

BTS-030 N435B

124

10

Sample 1: problem in neighbour definition and interference in

BCCH frequency

N097C Defined adj cell BCCH=124 BSIC=16

Serving cell N2254C

N254A Undefined adj cell BCCH=124 BSIC=10

Sample 2 : problem in hardware (sector swap) but not in neighbour

definition

Sample 2 : problem in hardware (sector swap) but not in neighbour

definition

GC site

Sample 2 : problem in hardware (sector swap) but not in neighbour

definition

BSC B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N

Source BTS BTS-194 NM861B BTS-194 NM861B BTS-194 NM861B BTS-194 NM861B BTS-194 NM861B BTS-194 NM861B BTS-194 NM861B BTS-194 NM861B BTS-194 NM861B BTS-194 NM861B BTS-194 NM861B BTS-194 NM861B

Neighbour N033B N2033B N205A N205B N205C N2205A N2205C N255C NM017A NM094B NM861A

FREQ 122 610 118 112 124 597 607 109 103 105 95 100

NCC 1 1 1 2 1 2 2 2 1 2 2 2

BCC 2 4 3 3 5 0 0 5 3 3 7 4

NM861B Neighbours

BSC B023N B066N B075N

BCF BCF-011 BCF-012 BCF-004

BTS BTS-115 N033A BTS-034 N419B BTS-010 N1082C

BCCH 112 112 112

BSIC 26 26 26

All cells with BCCH=112,BSIC=26

Sample 2 : problem in hardware (sector swap) but not in neighbour definition

BSC ID B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N

Source Cell NM861B NM861B NM861B NM861B NM861B NM861B NM861B NM861B NM861B NM861B NM861B NM861B

ATT 6536 2692 1826 360 143 141 2 0 0 0 0 0

BLK 71 0 0 39 0 0 0 0 0 0 0 0

FAIL 1 1 1 3 9 2 50 0 0 0 0 0

FAIL 7 1 2 24 23 23 33 0 0 0 0 0

BLK 14 34 19 7 5 15 0 50 0 0 0 0

ATT 1932 7358 1139 219 77 62 3 2 0 0 0 0

LAC 5215 5215 5215 5215 5215 5215 5215 5215 5215 5215 5213 0

CI 16092 52153 22153 16673 33097 63097 13097 43097 23097 22727 14070 0

Target Cell NM861A N2033B N033B NM017A N205C N2205C N205A N2205A N205B NM094B (#### ()

Target BSC B023 B023 B023 B023 B023 B023 B023 B023 B023 B023 BSC

Sample 2 : problem in hardware (sector swap) but not in neighbour

definition

Sector swap in NM861A,B

Sample 3 : There is no problem in neighbour definition

Sample 3 : There is no problem in neighbour definition

Sample 3 : There is no problem in neighbour definition

N2255A Neighbours

Sample 3 : There is no problem in neighbour definition

BSC ID B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N B023N

Source Cell N2255A N2255A N2255A N2255A N2255A N2255A N2255A N2255A N2255A N2255A N2255A N2255A N2255A N2255A N2255A N2255A N2255A N2255A

ATT 13884 8882 7434 3583 3026 2612 1847 1303 1082 883 751 479 254 109 58 18 5 1

BLK 0 75 78 68 55 0 0 0 0 0 0 24 0 0 3 0 0 0

FAIL 13 1 3 1 3 1 3 1 9 3 1 2 5 46 11 11 20 100

FAIL 2 2 1 1 0 3 2 3 5 4 3 0 0 0 0 15 0 0

BLK 22 76 86 74 0 17 15 20 16 15 21 0 0 9 0 17 0 0

ATT 22544 5970 14381 6515 0 3772 2325 2892 2293 2981 1327 0 0 53 0 24 0 0

LAC 5215 5215 5215 5215 5210 5215 5215 5215 5215 5215 5215 5210 5210 5215 5215 5215 5215 5215

CI 15210 52159 55210 65210 55227 22159 32159 13033 35210 25210 23033 52726 22726 15207 42809 35207 12809 32147

Target Cell N255A N2124B N2255B N2255C N2422B N124B N124C N1161A N255C N255B N1161B N2560B N560B N254A N2694A N254C N694A N234C

Target BSC B023 B023 B023 B023 B021 B023 B023 B023 B023 B023 B023 B021 B021 B023 B023 B023 B023 B023

Call Setup Scenario:

ND Reports & Formulas

Contents

1. 2. 3. 4. 5.

Call Setup Scenario in MOC ND formulas for Call Success ND Reports for Call Success MCI Formulas in KPI Information

Signalling in MOC Call Setup - General

1. 2. 3. 4. 5. 6. 7. 8.

Immediate assignment (RACH & AGCH) Service Request (SDCCH) Authentication (SDCCH) Ciphering mode setting (SDCCH) Call initiation (SDCCH) Assignment of traffic channel (SDCCH & FACCH) Call confirmation (FACCH) Call accepted (FACCH)

Signalling in MOC Call Setup - 1

Signalling in MOC Call Setup - 2

Signalling in MOC Call Setup - 3

Signalling in MOC Call Setup - 4

Signalling in MOC Call Setup - 5

Signalling in MOC Call Setup - 6

Signalling in MOC Call Setup - 7

Signalling in MOC Call Setup - 8

Signalling in MOC Call Setup - 9

Traffic channel access and success

The overall call success is the product of the following factors:
SDCCH access SDCCH success TCH access TCH success

Network Doctor Reports shows the situation at each part in BTS or Area level.

ND Formulas for Call Success

csf_1 (SDCCH access probability, before FCS) csf_1a (SDCCH access probability, after FCS) csf_2a (SDCCH success ratio) csf_2e (SDCCH success ratio) csf_2j (SDCCH success ratio) csf_2m (SDCCH success ratio)

csf_2n (SDCCH success ratio) csf_3i (TCH access probability without DR) csf_3l (TCH access probability, real) csf_3m (TCH access probability without DR and Q) csf_4u (TCH success ratio, area, before call re-establishment) csf_4x (TCH success ratio, BTS, after call re-establishment)

SDCCH access probability

Gives the probability to access SDCCH. Applicable for area and BTS level..A low value means high traffic on SDCCH and lack of SDCCH resources, that is SDCCH blocking.

Before FACCH Call Setup:

After FACCH Call Setup:

SDCCH success ratio

The formula does not separate the SDCCH call seizures from other seizures (such as LU). The failure rate in the case of a call or LU can greatly differ from one another, wherefore you cannot use this formula for SDCCH call success ratio calculation. It is not exactly known how large a share of sum (sdcch_abis_fail_call + sdcch_abis_fail_old) really are setup failures. Most of them are because of Ghosts.

The best values seen are around 98%.

SDCCH success ratio

Includes A interface blocking. Suitable for BTS level.

TCH access probability

This PI indicates what would be the TCH blocking if DR was not used. Does not contain the congestion of the A interface circuit pool.

TCH success ratio

Before Re-Establishment:

After Re-Establishment:

ND Reports for Call Setup

ND Report 250

ND Reports for Call Setup

ND Report 251

We can use different formulas for Reports 250 & 251(csf_1, csf_1a and so on)

ND Reports for Call Setup

ND Report 207
This report provides 10-day profiles of the indicators listed below.
-

SDCCH availability SDCCH usage TCH availability TCH usage TCH traffic SDCCH access probability SDCCH success ratio TCH access probability TCH success ratio

ND Reports for Call Setup

ND Report 207

ND Reports for Call Setup

ND Report 204

ND Report 130 SDCCH Congestion

ND Report 135 TCH Congestion

ND Report 181- TCH Traffic Profile

Formula

Formula

SDCCH Congestion formula in MCI KPI

SDCCH cong

100*(SDCCH_BUSY_ATT - TCH_SEIZ_DUE_SDCCH_CONG) / SDCCH_SEIZ_ATT

SDCCH Congestion = (1 SDCCH access probability)*100 =100- csf_1a

CSSR formula in MCI KPI

(100-SDCCH Cong)

CSSR

*(TCH_NEW_CALL_ASSIGN+TCH_RE_EST_ASSIGN-BSC_I_SDCCH_TCHMSC_I_SDCCH_TCH+MSC_O_SDCCH_TCH+BSC_O_SDCCH_TCH) / (SDCCH_RE_EST_ASSIGN+SDCCH_NEW_CALL_ASSIGN-SDCCH_SMS_ASSIGN)

CSSR= (SDCCH Access Probability) * (SDCCH Success Probability) * (TCH Access Probability) = csf_1a * csf_2a * csf_3

ND formulas for performance evaluation

Nokia defined several formulas for Call Success factors (SDCCH & TCH). So Optimisation engineers can investigate performance of several network elements and features. For example, we can see the effect of Directed Retry or Queuing features on Call Setup Success Rate.