You are on page 1of 11

Guideline For Dummies

2G CDR Fast Analyze


2017 Ngayum.sastrowardoyo@gmail.com
Procedure for Locating Access Faults 1/2

Table 1 Possible causes of low immediate assignment rates

Phase Symptom Possible Cause


SDCCH assignment After receiving random access requests from MSs, the BSC sends an SDCCH congestion and
immediate assignment rejection message because no standalone dedicated equipment faults
control channel (SDCCH) is available.

Channel activation The BSC sends the Channel Act message to the BTS, and the BTS responds Equipment faults
with the Channel Act Nack message.

The BSC sends the Channel Act message to the BTS, but the BTS does not Equipment and transmission
respond. faults

Immediate assignment delivery After channels are activated successfully, the BSC sends immediate Um interface faults and MS
assignment messages, but the MSs do not access the assigned channels. As faults
a result, the BSC does not receive any EST IND messages.
Procedure for Locating Access Faults 2/2

Table 2 Possible causes of low assignment success rates

Counter Possible Cause


CA312:Failed Assignments (Channel Unavailable) TCH congestion
A3169A:Failed Assignments (Um Cause) Um interface faults
A3129B:Failed Assignments (First Assignment, Terrestrial Resource Request Hardware faults, transmission faults, and incorrect BSC configuration
Failed)

A3129E:Failed Assignments (CIC Unavailable) BSC faults and MSC faults


A3129F:Failed Assignments (CIC Allocated) BSC faults and MSC faults
A3129H:Failed Assignments (Clear Commands Sent By MSC) Normal release and misoperations of peer end users
OSS KPI: SDSR

The improvement of SDCCH Success Rate (SDSR) can be acquired by


optimizing the 2 following indicators.
SDCCH Congestion Rate: It reflects the SDCCH collisions due to insufficient
resources. If SDCCH Congestion Rate is higher, SDSR will be worse.

SDCCH Drop Rate: It indicates the probability of call drops that occur when MSs
occupy SDCCHs. If SDCCH Drop Rate is higher, SDSR will be also worse.
Minimizing SDCCH Congestion & SDCCH Drop will result to Improve SDSR
OSS KPI: SDSR SDCCH Congestion Rate (1/2)
If SDSR degraded because of high SDCCH Congestion Rate, then check two
possible causes
1. Low SDCCH Availability Rate
When the SDCCH availability is low, available SDCCHs may be insufficient for the services and
consequently high congestion ratio on SDCCH occurs.
Actions: Check why SDCCH availability is low. Usually the problem is due to Hardware (e.g.
TRX) faulty and/or Abis transmission link down. So, confirm with alarm checking and escalate
the problems to BSS/Tx team.

Example of Low SDCCH Availability


due to E1 transmission problem
and causing higher SDCCH
congestion rate

Found relevant E1 alarm


OSS KPI: SDSR SDCCH Congestion Rate (2/2)

SDCCH Congestion Rate: two possible causes (cont)


2. Lack of SDCCH Resources
Meaning the configured SDCCH Timeslots are not sufficient to the actual SDCCH (signaling)
Traffic.
Actions:
Perform SDCCH dimensioning to find the optimal number of SDCCH based on the occurred
traffic. And configure it accordingly.
Commonly used configuration is 1SDCCH per 2TRX, a value by experience.
Ensure to always activate the Dynamic SDCCH, which largely expand the flexibility of
SDCCH configuration
Parameters Values Remarks
SDDYN YES SDCCH Dynamic Allocation Allowed

PDCH2SDEN YES Dynamic PDCH Conversion to SDCCH Allowed

If SDCCH congestion occurs because there is high SDCCH traffic due to Location Update, so
check if any improper LAC design (e.g. Mushroom LAC) then revise it. Or may try to adjust
CRH parameters
Parameters
to prevent
Values
tooRemarks
frequent Cell re-selections between the different-LAC cells.
CRH 6dB (default) Cell Reselect Hysteresis Parameters. For example: in case cell A having high SD traffic due to LU, we may
try to set CRH to higher value for different LAC neighbor cells of cell A
OSS KPI: SDSR SDCCH Drop Rate (1/4)

If SDSR degraded because of high SDCCH Drop Rate, then firstly check the drop causes
SDCCH Drop causes: Below message flow shows possible SDCCH drop causes with related counter
names.
OSS KPI: SDSR SDCCH Drop Rate (2/4)

Identify what is the major cause for SDCCH drops


Example of OSS statistics for SDCCH drop cause

Normally major SD drop causes are due to CONN Fail & ERR IND (T200 Expired)
OSS KPI: SDSR SDCCH Drop Rate (3/4)

Two major SDCCH drop causes


1. SDCCH Drop due to CONN Fail (Radio Link Failure)
This SD drop cause is indicating that a drop occurs on the Radio interface because of the abnormal
connection on the radio link layer. This type of SDCCH drops may be caused by:
Coverage Problems: refer to TDR coverage check
Interferences: refer to TDR Interference check . In general, BCCH freq has less tight freq reuse (so less
interference) than TCH freq, so if possible its preferred to configure SDCCH on BCCH to improve SDCCH
drop and SDSR
Improper parameter settings
Actions:
- Check below parameters that affect SDCCH call drop rate if they follow NPT values or not
RXLEV_ACCESS_MIN
RACH Min. Access Level
CRO
MS MAX Retrans
Random Access Error Threshold
These parameters relate to the network coverage and the balance between the uplink and the
downlink. If these parameters are set to improper values, MSs in the areas of poor coverage can access
the network and call drops are likely to occur. If the settings of these parameters lead to the imbalance
between the uplink and the downlink, call drops are likely to occur.
OSS KPI: SDSR SDCCH Drop Rate (4/4)

Two major SDCCH drop causes


2. SDCCH Drop due to ERR IND Received (T200 Expired)
Actions:
- Check below related parameters that affect SDCCH call drop rate due to T200 expiry

Parameters Values Remarks

T200SDCCH, (NPT) or If timer T200 is set to a smaller value, the transmit end may mistakenly regard that the
T200 SACCH optimized link is faulty and the data transmission fails before the transmit end receives a
SDCCH, response from the peer end. If timer N200 is set to a smaller value, the number of
T200 SDCCH data retransmissions is reduced and the success rate of transmission is reduced. If
SAPI3, timers T200 and N200 are set to greater values, the channels are seized all along
and N200 of when the link is faulty. Thus, resources are wasted.
SDCCH
End Of The Slide

You might also like