Escolar Documentos
Profissional Documentos
Cultura Documentos
Topics Covered
Parameter Audit
Some major parameters might have big impact to KPI. We briefly review those
parameter to make sure at least we are not optimizing at the unreachable value.
TCH Drop
RX diversity (RDIV) : enable/disable
Radio Link Timeout (RLT) : higher value less drop but more bad quality.
Radio Link Timeout AMR (ARLT) : higher value less drop but more bad quality
SDCCH Drop and SDCCH Success Rate
RxLev Access Minimum (RXP) : higher value less drop and less traffic.
C2 parameter
Cell reselection parameter Index (PI) enable/disable
Cell barring qualify (QUA)
Cell reselect offset (REO) : less value less drop and less traffic.
Temporary offset (TEO)
Penalty time (PET)
5
Bad quality in UL after rehoming because of RDIV parameter is not set YES anymore.
Few traffic in 1800 layer of a dual band 900/1800 network :-Idle Mode: C2 parameters not set properly
(temporaryOffset, penaltyTime)
10
1.
2.
3.
4.
5.
6.
Handover not happening when DL signal level of neighbour much greater than serving
cell
POC DL activated
Some sites did not hop as some frequencies were not correctly set!
Important to verify network parameters through MML
command!
11
Conclusion
Before suspecting anything, check the parameters
active in the network!!!
12
13
Firstly we need to check the KPI of Cluster Level & BSC level
After that Check the KPI of which BSC is going down and then find the
cells due to which KPIs going worst
Now check the Cells KPI ( Preferably CSSR, DCR & HOSR ) why it is
going worst
If CSSR KPI is worst then we need to check all the components of the
14
CSSR KPI
As we know CSSR depends on the 4 Components (TCH Blocking,
15
16
ND Report 166 S D
Drop Report
No. of SD transaction
failures due to the radio
failure (1003)
Formula:
100 * (traffic.sdcch_radio_fail + traffic.sdcch_rf_old_ho +
No. of SD transaction
traffic.sdcch_user_act + traffic.sdcch_bcsu_reset +
failures due to BTS
failure. (1036)
traffic.sdcch_netw_act + traffic.sdcch_bts_fail + sdcch_lapd_fail+
sdcch_a_if_fail_call+sdcch_a_if_fail_old) /
Number of SDCCH transactions ended
(traffic.sdcch_assign + traffic.sdcch_ho_seiz)
because of a failure in the A interface on
the source channel during an SDCCHSDCCH or SDCCH-TCH HO
No. of successful
SDCCH seizures for
a handover. (1006)
No. of SDCCH
assignments. (57021)
17
No. of SD transaction
failures due to BCSU
reset. (1038)
ND Report 166
If 7745 Channel Failure Rate Alarm persist on SDCCH then Shift the
SDCCH from that TRX to another TRX.
SD Drop can also be high due to high UL or DL issue in that cell. For UL we
can put TMA and for DL we can provide tilt or re orient that antenna.
system 1 SDCCH can take 5000 SDCCH attempts, for this dont consider
the daily KPI, please see the next slide for better explanation of this.
19
20
21
TASR FORMULA
22
As in the above given counters shows that suddenly some the counters
value ( ABIS interface fail, Radio fail etc) increased . Radio fail may be
due to some Radio problems as interference, overshooting etc and if
ABIS fail call increased it may be increased due to some Transmission
alarm.
23
24
BUSY
BUSY
BUSY
BUSY
BUSY
BUSY
BUSY
25
26
Formula: (Nom)
100 * [sum(a.tch_call_req - a.tch_norm_seiz)
Number of unsuccessful
handovers due to wrong Ainterface circuit type. (4097)
Number of unsuccessful
handovers due to wrong Ainterface circuit type.
(4101)
No. successful SD-TCH
HO. (4050)
Number of successful TCH
seizures in direct accesses to
a super-reuse TRX during the
call set-up phase. (1165)
27
Number of unsuccessful
handover due to wrong Ainterface circuit type. (4098)
Number of unsuccessful
handovers due to wrong Ainterface circuit type. (4097)
28
Number of unsuccessful
handover due to wrong Ainterface circuit type. (4098)
Number of unsuccessful
handovers due to wrong Ainterface circuit type. (4101)
TCH availability
Check alarms (are TRXs & TSLs in Working State? ), check availability
report and RxQuality report to verify whether there is a badly functioning
TRX. Make Loop Tests on TRX. Fix hardware problem.
TCH capacity
Bad TCH capacity dimensioning. Check number of TRXs.
29
30
Formula:
100 * (traffic.sdcch_busy_att - traffic.tch_seiz_due_sdcch_con)/
traffic.sdcch_seiz_att
Successful seizures of
TCH due to SDCCH
congestion (1099)
Total no. of SDCCH
seizure attempt (1000)
31
32
SDCCH blocking
SDCCH avalability
Check alarms (are TRXs & TSLs in Working State? ), check availability report
and RxQuality report to verify whether there is a badly functioning TRX. Fix
hardware problem.
SDCCH capacity
Check actual SDCCH configuration ( e.g. Combined BCCH/SDCCH, Number of
SDCCH channels). If there is insuficient SDCCH capacity and enough TCH
capacity, add SDCCH TSL. Other solution e.g. are to add TRX, activate
Dynamic SDCCH, activate FACCH Call Setup.
SDCCH traffic
Verify traffic distribution (LU, SMS and MOC in %);
Cell is covering a region greater than planned. Verify TA statistics. May need to
change DMAX, or downtilt.
33
parameters)
Bad Location area geographical configuration. Too small LA
definition will cause many LA updates. Border of LA in a
busy avenue will cause many LUs in both location areas!
Low value for CellReselectHysteresis
Verify if downtilt is needed or an increase in SDCCH
capacity (air and Abis interfaces).
SDCCH traffic due to SMS
34
35
DCR FORMULA
36
DCR ANALYSIS
As by the above counters you can directly say from what reasons drop call rate is high as it may be due to RF reasons or
may be due to Transmission Issues so we need to know about all the counters
37
38
TCH Drop
Radio Fails
Check alarms and RxQuality report to verify whether there is a badly functioning TRX.
Fix hardware problem. Check antenna line.
Coverage. Verify TA report and planning tool.
Interference. Check Frequency Plan. Solution e.g. add sites, downtilt antennas, increase
RxLevAccessMin.
Lack of neighbours
Bad neighbour declaration
Transcoder Failure
Due to synchronisation problem. Synchronisation source set in BTS clock. Change to
BSC.
AIF Failure:
Interface failures: problem with ET cards. Solution: block the circuits connected to this
card and then change ET card when available.
39
ND153 Report
ND154 Report
Is Blocking High?
Yes
Hardware issue
suspected
No
Check Alarm
No
RF Issues suspected
Check TRX
Configuration
Possible reasons: Target cell has co-channel/Adj channel interference, coverage gaps, neighbor BCCH/BSIC
frequency not updated, wrong CGI format in MSC, wrong HO number in MSC, Non-symmetric HO relations, synchronization
problem, excessive UL interference, site too high, Direct Retry traffic cause high HO Failures.
41
41
2005 Nokia
HARDWARE ALARMS
There are several hardware alarms in NOKIA system which are badly affecting the KPI
LAPD Failure
PCM Failure
Some alarm I have explained in the next slides, please see the given below slides
42
Please see the given below core analysis for the 7745 Alarm
02
01 01 00 00 00 00 00 00
01
04
100d
01 means Faulty Timeslot
02 represents Alarm on
SDCCH Channel
8 Time Slots
Shift the SDCCH channel from that TRX or remove SDCCH if there is extra SDCCH timeslots
The same scenario start for TCH but at the starts there is 01 in place of 02 and for that is any timeslot is faulty then we
can go for Locking Timeslot & Locking TRX and after Lock we can check the Performance in Hourly KPI
43
Regarding this Alarm we just need to remember one thing if this alarm persists the
OMU of the site blocked and at the same case dont reset the BCF, if we do this
reset BCF than after lock the BCF it will not be unlocked until OMU is not UP and
if OMU up then also site will be down because BCF is Locked so better when this
alarm comes dont Reset the BCF.
This above point is the main point regarding this Alarm, please remember it
always.
44
The BTS has had no successfully terminated calls or SDCCH transactions during
the supervision period.
The alarm is used for supervising the BTS traffic capacity.
Reason for the alarm
1 = no successful SDCCH seizures
2 = no successful TCH seizures
3 = no successful SDCCH nor TCH seizures
45
PCM Failure
Alarm 7704 is BCF-specific. It is used by the RNW recovery part of the BSS system. This alarm (and
cancel) will cause radio network recovery actions concerning objects connected through the faulty
PCM (ET). Alarm 7704 does not occur alone. There are always some other alarms ( 7767, 2900, 2915,
7706, 7704) active at the same time.
46
This alarm persists when BTS is not able to synchronize with the BSC / Core Network and due to this alarm
persist synchronization changed due to holdover mode.
May be this alarm persists sue to some error in Software upgrade for COMMON ABIS sites.
We can check the BTS configuration setting as after software upgraded may be some setting change.
Check the heater working properly or not if equipped.
Action Proposed to remove this alarm and you can try these given below steps also.
check the sync with MGW and BSC, MGW and MSS.
Just make the SYNC disconnect by the command ZDRD
After disconnect SYNC remove the punching cable or optical path cord as per your connection
After this run ZDRI and then state will be pleisochronous mode
After 10-15 min just punch the cable or connect the fiber and connect the 2M1 or 2M2 by ZDRC and then make the
state to hierarchal SYNC
After above all steps just restart the system
47
Transmission Alarm
There are lot of major alarms persists in the BSC but some of them are not affecting the KPIs
but some really affecting the KPIs, please see the given below alarm status
BTS & TC Unsynchronisation Clear calls due to A interface ( Affecting Drop Call Rate)
BTS & TC Unsynchronisation Clear calls due to ABIS interface ( Affecting Drop Call Rate)
Abnormal A interface Circuit Release ( Affecting Drop Call Rate)
SCCP Disturbance ( Affecting SDCCH Drop Rate)
AIS Received ( Site Fluctuates)
Fault Rate Monitoring ( Site fluctuates)
Telecom Link Overload
Signaling Link Load Over threshold
Adjacent Cell IDENTIFIER configuration error
48
adjacent cell information has been defined incorrectly in the BSDATA (BSS Radio Network configuration
Database). Either the MSC or the source BSC can detect the error during an external handover. When
the error has been detected, the handover attempt is interrupted
1182 : BTS ID
0 : the MSC has detected an error in the adjacent cell definitions
1 : the BSC has detected an error in the adjacent cell definitions
0-FF: BCC (Base Station Color Code). The target cell where handover has been attempted. The value is
set by the MSC
FF information is not available
0-FF: NCC (Network Color Code). The target cell where handover has been attempted. The value is set
by the MSC
FFFF identification of the target cell (BCCH)
65535: No information of BCCH
49
50
SCCP Disturbance
51
52
Radio Timeslot number on which calls are getting dropped. This is Air Interface Timeslot number
If calls are getting cleared by all the timeslot for the particular TRX firstly please lock the TRX and check the alarm after
sometime.
We can try to change the Channel TSL also if there is any free mapping given.
53
The alarm is used to supervise the traffic load of LAPD links and BCSU units and to detect the possible
overload situations. The alarm may also be caused by short breaks in the Abis interface.
54
By this command we can check which ET is fluctuating , and by this command we can see trunk circuit
disturbance statistics please see given below analysis
NOINSGN
incoming signal missing
AIS AIS state has been detected in the incoming line signal
(continuous "1-state")
FALOST - frame alignment has been lost
REMOTE - alarms from remote end
TOTAL TIME - measured total time
AVAIL TIME - time of availability
UNVAIL TIME - time of unavailability
EFS - seconds without errors
ES - seconds with errors
SES - seconds with a great number of errors
DM - deteriorated minutes
55
ND Report Analysis
56
Adjacency definition(061)
Cell A
57
Cell B
ZEAT Check
Co channel discrepancies , or
LAC discrepancies etc
Co channel discrepancies
58
=================================================================================
=
ADJACENCY DISCREPANCIES
=
Network:
PLMN
=
Area:
All BTSs selected
=
Sorting key:
source BSC name, source BTS ID
=================================================================================
This report lists the discrepancies of various parameters between the source cell adjacency parameters and target cell
parameters.
Impact of discrepancies:
Any difference between two identical parameters of the target BTS and the same parameter of adjacency usually results in
handover failures between the source and the target BTSs.
The first of each pair of lines indicates the adjacency of a source cell.
The second line indicates the target cell.
Parameters in the first line show the values in the adjacency (ADJ) of a source cell defined in c_adjacent_cell table.
Parameters in the second line (TGT) show the values of the target cell in c_bts table.
The checked parameters are: Location Area Code (LAC), Cell Identity (CI),Frequency (FREQ), Maximum power of MS (PMAX),
Network Colour Code (NCC) and Base Station Colour Code (BCC). These should be the same in the adjacency and in the
target cell.
In case there is any kind of discrepancy indicated by the report, do the following:
1) Upload adjacency data from the network for the claimed BTSs.
2) Run this check again.
3) If discrepancies are still found, check and correct them via MML.
================================================================================
Adjacency discrepancies in PLMN network
LAC CI
FREQ PMAX NCC BCC
=== ===
=== ==== === ===
Source BSC (BTSid)
Source BCF/BTS
ADJ ADJ
ADJ ADJ ADJ ADJ
Target BSC (BTSid)
Target BCF/BTS
TGT TGT
TGT TGT TGT TGT
------------------ ---------------------------- ------ ------ ---- ---- --- --BSC1KUTOJA(6)
SUOSAA004 / SUOSAA1006
1
10010 600 30 7
2
BSC1KUTOJA(10)
LAAJAL010 /LAAJAL1010
1
10010 773 30 7
2
BSC1KUTOJA(7)
SUOSAA004 / SUOSAA1007
1
10010 600 30 7
2
BSC1KUTOJA(10)
LAAJAL010 /LAAJAL1010
1
10010 773 30 7
2
BSC1KUTOJA(9)
LAAJAL009 / LAAJAL1009
1
10010 600 30 7
2
BSC1KUTOJA(10)
LAAJAL010 /LAAJAL1010
1
10010 773 30 7
2
BSC1KUTOJA(9)
LAAJAL009 / LAAJAL1009
2
20003 594 30 7
7
BSC2UPS1(3) 3UPS001 /3UPSULTRA2003
2
20003 764 30 7
7
BSC1KUTOJA(9)
LAAJAL009 / LAAJAL1009
2
20002 600 30 7
7
BSC2UPS1(2) 3UPS001 /3UPSULTRA2002
2
20002 762 30 7
7
BSC2UPS1(1) 3UPS001 /3UPSULTRA2001
2
20001 776 30 7
7
BSC2UPS1(10) 5KOM005 / 5KOM2010
1
10009 605 30 7
2
59
61
ND-074
62
63
64
ND-208 Analysis
Case1: Jumper from TRX 4 to combiner loose (check
connectors at both ends)
2005 Nokia
V1-Filename.ppt / yyyy-mm-dd / Initials
Nokia Siemens Networks
66
ND Report 196
2005 Nokia
V1-Filename.ppt / yyyy-mm-dd / Initials
66
Nokia Siemens Networks
ND Reports
ND196 Report
060 ND Report
ND061 Report
ND166 Report
ND 067 Report
ND163 Report
ND135 Report
ND150 Report
ND250 Report
ND154 Report
67
67
2005 Nokia
V1-Filename.ppt / yyyy-mm-dd / Initials
Nokia Siemens Networks
ND208 Report
ND153 Report
ND 074 Report
ND204 Report
Alarm Description
68
68
2005 Nokia
V1-Filename.ppt / yyyy-mm-dd / Initials
Nokia Siemens Networks
THANKS
69