What is TCH Blocking and Drop?

TCH call Blocking , it present how many subscriber asks for TCH
channel and network reply with no available resource. So it present
how many subscriber request TCH channel to reject this request
TCH call drop
After subscriber get TCH and start converstion during it the call is
dropped for some reasons not related to the subscribers .

What is difference between Congestion and Blocking

Congestion = time when all resources are occupied (no free TCH
available)
Blocking = rejected (blocked) attempts over all attempts in %.
Also there is different formulas for TCH blocking. For example in
subscriber perceived TCH Blocking all successful directed retries to
another cell are removed from the nominator.
Answer2:
Blocking dives you the non served calls
Congestion gives the time when no resource are available (it is
possible that nobody needs them so no blocks)
there is a possiblity to have high blocking and low congestion - this
means that you have a peak of the attempts.

What is GOS means?

Gos grade of service (blocking)
in radio part we design the network forcertian Gos , for example Gos in
2%, by erlang table B, there is a relation between number of channel ,
blocking rate ,and traffic.
So according to number of channel and Gos we can know the desgin
traffic.

What is Optimum Value of T200

we like to know the optimum value for T200 on LAPDm. All vendors
have different default values (Siemens 145 ms, Nokia 220 ms, Satellite
Abis 400 ms etc.) for this timer - but which value is the best to reduce
SDCCH drops and to keep the retransmissions at an acceptable level ?

Example: SDCCH/8
During a 51er multiframe the SDCCH/8 occupies four consecutive
TDMA frames (four bursts are sent). Than the MS / BTS has to wait for
the next 51er multiframe (i.e. 235 ms) before the next Layer 2 frame
could be sent. 145 ms / 220 ms are shorter than the 51er multiframe
(235 ms) so in case of an missing acknowledgement this is always a
T200 expiry. The SDCCH drop will occur if T200 expired N200+1 times.
If the T200 is increased (for example to 500 ms) we have two 51er
multiframe to get the acknowledgement and the SDCCH drops are
reduced.
The Qos Stats show a clear & strong corelation between the KPI and
the parameter T200. That's amazing !
Regarding the Ack from the BTS, I'm not sure (and I'm tired to look in
the 3GPP specs :) ). Take the subchannel "0" from the SDCCH ts.
in DL : the BTS sends SDCCH/0 on burst 0, 1, 2, 3 and the SACCH/0 on
burst 32, 33, 34, 35
in UL : th MS sends SDCCH/0 on burst 15, 16, 17, 18
and the SACCH/0 on 47, 48, 49, 50
And I ***believe*** that the Lapdm acknowledgments can be sent on
either the SACCH or the SDCCH, since both of them are sent over the
same LapDm link. I'm not sure at all about this though, but it sounds
logical.
The value of the SDCCH Drop due to Radio failures (in ALU) is usually
around 1% in a fairly good network. The SDCCH Drop due to Radio
Failures is a counter that encompasses both the Radio Link Timeout
and the "T200*N200+1 times" failures.
I am not able to test your changes because I am not working on a live
network (i am a gsm trainer, living in a world of theory...)
T200 = 220ms for sDCCH SAPI0
= 450ms for SDCCH SAPI3
= 900ms for SACCH associated to SDCCH
Looking at those timers, I fear that the LapDm link for SDCCH is
different than the LapDm link for the SACCH of the SDCCH... I'll let you
look it up though :)

Dropped Call (TCH Drop-SDCCH Drop)

1. Radio Link Time-Out
Every time a SACCH message can not be decoded the radio link timeout counter is decreased by 1. If the message can be decoded the
counter is incremented by 2. However, the value can not exceed the
initial value. The initial value is set by the parameter RLINKT for radio
link time-out in the mobile station and by RLINKUP for timeout in the
BSC. If the mobile moves out of coverage and no measurement reports
are received in the BSC, there will be a radio link time-out and the
message Channel Release (cause: abnormal release, unspecified) is
sent to the mobile station and the SACCH is deactivated in the BTS. A
Clear Request message is sent to the MSC. To be sure that the mobile
has stopped transmitting, the BSC now waits RLINKT SACCH periods
before the timeslot is released and a new call can be established on
the channel.
2. Layer 2 Time-Out
If the BTS never get an acknowledge on a Layer 2 message after the
time T200XN200, the BTS will send Error Indication (cause: T200
expired) to the BSC, which will send Channel Release (cause: abnormal
release, timer expired) to the mobile station and a Clear Request to the
MSC. The SACCH is deactivated and the BSC waits RLINKT SACCH
periods before the timeslot is released and a new call can use the
channel. This is only valid if the call is in steady state, i.e. not during
handover or assignment.

3. Release Indication
When the BTS received a layer 2 DISC frame from the mobile it replies
with a Layer 2 UA frame to the mobile station and a Release Indication
to the BSC. The system does only react on Release Indication if it is
received during a normal disconnection situation. If such a message is
received unexpectedly this will usually cause radio link time-out or
timer T200 expiration as the mobile station stops the transmitting of
measurement reports. It is also possible that the release will be normal
depending on when the Release Indication is received.
4. MSC Time-Out
Normal Release:
If the MSC never received a response on a message (e.g. Identity
Request) and there is no radio link time-out or layer 2 time-out, the
MSC will send a Clear Command to the BSC. The time-out is depending
on the message. When receiving Clear Command, the BSC will send a
Channel Release (cause: normal release) and then deactivates the
SACCH.
Reject (only SDCCH):

If the MSC never receives a response on the first message after

Establish Indication, the MSC will send a reject message. If the
connection was a Location Update it will be a Location Update Reject
(cause: network failure) and if the connection was a mobile originating
call (CM Service Request) a CM Service Reject (cause: network failure)
will be sent. The MSC will then send a Clear Command to the BSC and
the call is cleared by Channel Release (cause: normal release).
5. Assignment to TCH
Before sending an Assignment Command from the BSC at TCH
assignment, the following two criterion have to be fulfilled:
a. There must be a TCH channel available, i.e. no congestion
b. The locating algorithm must have received at least one valid
measurement report.
If either of the criterion is not fulfilled, Assignment Command will not
be sent and a Channel Release (cause: abnormal release, unspecified)
will be sent to the mobile station and a Clear Request to the MSC.
TCH Drop reason (1)
The classification of TCH Drop Reasons are arranged in the order of
priority:
1.Excessive Timing Advance
2.Low Signal Strength
3.Bad Quality
4.Sudden Loss of Connection
5.Other Reasons
Excessive Timing Advance
The TCH Drop counters due to Excessive Timing Advance will pegged
when the during the time of disconnection, the last Timing Advance
value recorded was higher than the TALIM Parameter. This drop reason
is commonly apparent to isolated or island sites with a wide coverage
area.
Action:
Check if the cell parameter TALIM is < "63"
Solution:
Set TALIM to a value close to 63.
Tilt antenna/reduce antenna height/output power, etc. for co-channel
cells.
TCH Drop Reasons (2)
Low Signal Strength on Down or Uplink or Both Links

The drops counters due to Low Signal Strength will be pegged when
the Signal Strength during the last Measurement Report before the call
dropped is below the LOWSSDL and/or LOWSSUL Thresholds. LOWSSDL
and LOWSSUL are BSC Exchange Property parameters which is used
only for statistics purposes and does not affect the behavior of calls. If
both UL and DL Signal Strength are below the thresholds, only Drop
due to Low SS BL will pegged. Normally a call is dropped at the border
of large rural cell with insufficient coverage. Bad tunnel coverage
cause many dropped calls as well as so called coverage holes. Bad
indoor coverage will result in dropped calls. Building shadowing could
be another reason.
Action:
Check coverage plots.
Check output power.
Check power balance and link budget.
Check if Omni site.
Check antenna configuration & type.
Check antenna installation.
Perform drive tests & site survey.
Check TRX/TS with high CONERRCNT.
Solution:
Add a repeater to increase coverage in for example a tunnel.
Change to a better antenna (with higher gain) for the base station.
Add a new base station if there are large coverage holes.
Block/Deblock TRX
TCH Drop Reasons (3)
Poor Quality on Down or Uplink or Both Links
The drops counters due to Bad Quality will be pegged when the Signal
Strength during the last Measurement Report before the call dropped is
above the BADQDL and/or BADQUL Thresholds. BADQDL and BADQUL
(expressed in DTQU) are BSC Exchange Property parameters which is
used only for statistics purposes and does not affect the behavior of
calls. If both UL and DL Quality are above the thresholds, only Drop due
to BAD Quality BL will pegged.
Problem on Bad Quality is usually associated with Co-channel
Interference on BCCH or TCH. Faulty MAIO assignment can cause
frequency collisions on co-sited cells especially on 1x1 Reuse. External
interference is also one possible cause of problem on quality.

Action:
Check C/I and C/A plots.
Check Frequency Plan (Co-BCCH or Co-BSIC Problem).
Check MAIO, HOP, HSN parameters.
Check FHOP if correctly configured (BB or SY).
Check for External Interference.
Perform drive tests.
Solution:
Change BCCH frequency.
Change BSIC.
Change MAIO, HOP, HSN.
Change FHOP.
Record RIR or on-site Frequency Scanning to identify source of
interference.
Use available radio features.
TCH Drop Reasons (4)
Sudden Loss of Connection
Drops due to Sudden Loss are drops that have not been registered as
low signal strength, excessive timing advance, bad quality or hardware
(other) reasons, and the locating procedure indicates missing
measurement results from the MS.
There are some common scenarios that could lead to Sudden Loss of
connections such as very sudden and severe drops in signal strength,
such as when subscribers enter into buildings, elevators, parking
garages, etc., very sudden and severe occurrence of interference, MS
runs out of battery during conversation, Handover Lost, BTS HW faults,
Synchronization or A-bis link fault (transmission faults), and
MS Faults.
Action:
Check BTS Error Logs, Alarms and Fault Codes.
Check CONERRCNT per TRX and TS.
Check Transmission Link (A-bis).
Check for DIP Slips.
Check LAPD Congestion.
Correlate Handover Lost to Drops due to Sudden Loss
Solution:
Fix Hardware Faults and Alarms.
Reset TRX with high CONERRCNT.
Ensure that Synchronization and A-bis Link are stable.
Change RBLT with high DIP Slips.

Change CONFACT or increase Transmission Capacity

Investigate HO Lost Problem
TCH Drop Reasons (5)
TCH Drops due to Other Reasons
TCH drops due to Other Reasons are computed by subtracting the sum
of drops due to Excessive TA, Low SS, Bad Quality and Sudden Loss
from the Total TCH Drop Counts. Drops due to Other Reasons are
generally associated with hardware problems, transmission link
problems on A-bis, Ater or Ainterfaces, and sometimes Handover Lost.
Action:
Check BTS Error Logs.
Check Alarms and Fault Codes.
Check CONERRCNT per TRX and TS.
Check Transmission Link (A-bis).
Check for DIP Slips.
Correlate Handover Lost to Drops due to Other Reasons
Solution:
Fix Hardware Faults and Alarms.
Reset TRX with high CONERRCNT.
Ensure that Synchronization and A-bis Link are stable.
Change RBLT with high DIP Slips.
Investigate HO Lost Problem
Problem reason of drop in SDCCH
Low Signal Strength on Down or Uplink
The reason for poor coverage could be too few sites, wrong output
power, shadowing, no indoor coverage or network equipment failure.
Action: Check coverage plots.Check output power. Perform drive tests.
Check BTS error log
Solution: Add new sites. Increase output power. Repair faulty
equipment.
Poor Quality on Down or Uplink
Action: Check C/I and C/A plots. Check frequency plan. Perform drive
tests.
Solution: Change frequency. Use available radio features.
Too High Timing Advance
Action: Check if the cell parameter TALIM is < style="font-weight:
bold;">Solution: Set TALIM to a value close to 63. Tilt antenna/reduce
antenna height/output power, etc. for cochannel cells.

Mobile Error
Some old mobiles may cause dropped calls if certain radio network
features are used. Another reason is that the MS is damaged and not
working properly.
Action: Check MS fleet.
Solution: Inform operator.
Subscriber Behavior
Poorly educated subscribers could use their handsets incorrectly by not
raising antennas, choosing illadvised locations to attempt calls, etc.
Action: Check customer complaints and their MS.
Battery Flaw
When a subscriber runs out of battery during a conversation, the call
will be registered as dropped call due to low signal strength or others.
Action: Check if MS power regulation is used. Check if DTX uplink is
used.
Congestion on TCH
The SDCCH is dropped when congestion on TCH.
Action: Check TCH congestion
Solution: Increase capacity on TCH or using features like Assignment
to another cell, Cell Load Sharing, HCS, Dynamic Half-Rate Allocation
and FR-HR Mode Adaptation etc.
T3103 and T3105 differences
Timer rr_t3103 (0-1000000, default 5000) digunakan untuk
menentukan switching menjatuhkan panggilan. Setelah menerima
pesan sukses switching sel target atau sel switching sumber informasi
gagal, rr_t3103 akan menghentikan jam. Setelah menerima pesan
sukses switching sel target atau sel switching sumber informasi gagal,
rr_t3103 akan menghentikan jam. Jika tidak, sekali rr_t3103 ke waktu,
memberitahu MSC, menghapus sambungan, menjatuhkan panggilan
beralih terjadi. Jika tidak, sekali rr_t3103 ke waktu, memberitahu MSC,
menghapus sambungan, menjatuhkan panggilan beralih
occurred.Timer rr_t3105, digunakan ketika mengaktifkan sel
asynchronous, menentukan apakah waktu yang tepat sebelum
informasi Timer fisik (informasi Fisik) dalam sistem GSM, proses
switching, stasiun bergerak menerima perintah jaringan switch, dikirim
ke target akses saluran switch (Handover ACCESS) pesan. Timer
rr_t3105, bila digunakan dalam switch sel asynchronous, menentukan
apakah waktu yang tepat sebelum informasi Timer fisik (informasi
Fisik) dalam sistem GSM, proses switching, stasiun bergerak menerima
perintah jaringan switch, dikirim ke target akses saluran switch
(penyerahan ACCESS) pesan. Jaringan menerima pesan, menghitung
karakteristik RF, berarti unit data yang dikirim ke stasiun mobile

informasi fisik, dan memulai timer T3105 (4,08 GSM spesifikasi

didefinisikan sebagai T3105, parameter sistem Ericsson didefinisikan
sebagai TIMER3105). Jaringan menerima pesan, menghitung
karakteristik RF, berarti unit data yang dikirim ke stasiun mobile
informasi fisik, dan memulai timer T3105 (4,08 GSM spesifikasi
didefinisikan sebagai T3105, parameter sistem Ericsson didefinisikan
sebagai TIMER3105). Jika T3105 belum menerima stasiun mobile
dikirim lapisan yang benar 2, jaringan informasi fisik akan diterbitkan
kembali, dan restart T3105. Jika T3105 belum menerima stasiun mobile
dikirim lapisan yang benar 2, jaringan informasi fisik akan diterbitkan
kembali, dan restart T3105. Fisik informasi sampai dengan jumlah
transmisi ulang dengan parameter "Jumlah maksimum dari informasi
secara fisik diulang sampai jumlah transmisi ulang dengan parameter"
jumlah maksimal kali untuk mengulang
Ketika jaringan saklar untuk mengirim stasiun mobile menerima pesan
akses, saluran fisik menjadi penting untuk mencapai status
sinkronisasi. Ketika jaringan saklar untuk mengirim stasiun mobile
menerima pesan akses, saluran fisik menjadi penting untuk mencapai
status sinkronisasi. Selama kualitas saluran komunikasi dapat dijamin
untuk menerima stasiun bergerak harus dapat memperbaiki informasi
fisik, dan mengirim struktur 2 lapisan jaringan frame. Selama kualitas
saluran komunikasi dapat dijamin untuk menerima stasiun bergerak
harus dapat memperbaiki informasi secara fisik, dan mengirim struktur
2 lapisan jaringan frame. Jika informasi fisik dikirim ke mobile station
tidak dapat menerima setelah masalah lapisan 2, biasanya, kualitas
fisik saluran miskin tidak dapat melakukan komunikasi normal,
kenaikan yang sesuai dalam jumlah fisik informasi yang diterbitkan
kembali, sehingga kualitas jaringan saluran fisik dalam kemajuan yang
diterbitkan oleh mobile station menerima layer 2 frame untuk
menyelesaikan proses switching, sehingga menghindari panggilan
yang tidak perlu menjatuhkan. Jika informasi fisik dikirim ke mobile
station tidak dapat menerima setelah masalah lapisan 2, biasanya,
miskin kualitas fisik saluran dapat komunikasi tidak normal, kenaikan
yang sesuai dalam jumlah fisik informasi yang diterbitkan kembali
untuk jaringan pada perubahan fisik untuk kualitas saluran yang lebih
baik untuk stasiun bergerak ketika tingkat menerima 2 dikeluarkan
untuk menyelesaikan proses switching, sehingga menghindari
panggilan yang tidak perlu menjatuhkan.
Serah terima kegagalan akses karena panggilan menjatuhkan alasan
utama: Handover kegagalan akses karena panggilan menjatuhkan
alasan utama:
? kurangnya jangkauan kekuatan sinyal yang tidak stabil, MS tidak
dapat benar diterima. ? kurangnya jangkauan kekuatan sinyal yang
tidak stabil, MS tidak dapat benar diterima. Hal ini terutama terjadi
dalam sebuah saklar darurat. Hal ini terutama terjadi dalam sebuah

saklar darurat. Penyebab MS biasanya tidak dapat menerima pesan

INFO Phys. Penyebab MS biasanya tidak dapat menerima pesan INFO
Phys.
Salah switch, sebagai layanan mungkin ada sekitar dua komunitas
dengan BCCH sel, mengakibatkan aktivasi lain plot kesalahan sistem
dari TCH, MS INFO Phys pesan tidak dapat diterima dengan benar.
Salah switch, sebagai layanan mungkin ada sekitar dua komunitas
dengan BCCH sel, mengakibatkan aktivasi plot lain kesalahan sistem
dari TCH, MS INFO Phys pesan tidak dapat diterima dengan benar.
Saat ini sebagian besar sistem Ericsson, jaringan, T3105 dan NY1
menggunakan pengaturan default sistem, khusus untuk TIMER3105 =
4 (40 ms), NOOFPHYSINFOMSG = 35 (35 kali). Saat ini sebagian besar
sistem Ericsson, jaringan, T3105 dan NY1 menggunakan pengaturan
default sistem, khusus untuk TIMER3105 = 4 (40 ms),
NOOFPHYSINFOMSG = 35 (35 kali). Untuk beberapa gangguan yang
lebih serius dengan jaringan (seperti Cina Unicom Network GSM900 1
1), 40 ms latency dan 35 kali berat jelas bukan rambut yang tepat,
cahaya yang tepat untuk meningkatkan pengalaman dan NY1 T3105
(NOOFPHYSINFOMSG), efektif dapat mengurangi switching dalam
menjatuhkan panggilan terjadi. Untuk beberapa gangguan yang lebih
serius dengan jaringan (seperti Cina Unicom Network GSM900 1 1),
40 ms latency dan 35 kali berat jelas bukan rambut yang tepat, cahaya
yang tepat untuk meningkatkan pengalaman dan NY1 T3105
(NOOFPHYSINFOMSG), efektif dapat mengurangi switching dalam
menjatuhkan panggilan terjadi.
Penyebab langsung dari panggilan menjatuhkan, ada dua: 1, RF rugi.
Penyebab langsung dari panggilan menjatuhkan, ada dua: 1, RF rugi. 2,
beralih menjatuhkan panggilan (Catatan: Kegagalan beralih tidak
berarti terputusnya sambungan, switching> kegagalan beralih
panggilan menjatuhkan). 2, beralih menjatuhkan panggilan (Catatan:
Kegagalan beralih tidak berarti terputusnya sambungan, switching>
kegagalan beralih panggilan menjatuhkan). Analisis berikut kedua
kasus. Analisis berikut kedua kasus.
(1) RF loss (1) RF rugi
Kegagalan spesifikasi AA mendefinisikan downlink, mobile Taichung
timer S (T100), pada awal panggilan stasiun ponsel diberikan nilai
awal, yaitu, timeout link nirkabel (radio_link_timeout). Kegagalan
mendefinisikan spesifikasi downlink, mobile Taichung timer S (T100),
pada awal panggilan stasiun ponsel diberikan nilai awal, yaitu, timeout
link nirkabel (radio_link_timeout). Nilai ini disiarkan di BCCH. Nilai ini
disiarkan di BCCH. Setiap kali stasiun mobile tidak bisa benar decode
pesan SACCH (4 SACCH BLOK) waktu, S dikurangi 1. Setiap kali stasiun
mobile tidak bisa benar decode pesan SACCH (4 SACCH BLOK) waktu,
S dikurangi 1. Setiap kali stasiun bergerak dengan benar decode pesan
SACCH, S ditambah 2. Setiap kali stasiun bergerak dengan benar

decode pesan SACCH, S ditambah 2. Namun, definisi S tidak melebihi

radio_link_timeout awal. Namun, definisi S tidak melebihi
radio_link_timeout awal. Jika jumlah S adalah nol, mobile station
menyerah sambungan radio sumber daya, masukkan modus siaga. Jika
jumlah S adalah nol, stasiun bergerak untuk menyerah sambungan
radio sumber daya, masukkan modus siaga. Terjadi sekali menjatuhkan
panggilan. Terjadi sekali menjatuhkan panggilan.
B. B. Uplink uplink kegagalan kegagalan
Sistem gagal untuk memantau parameter uplink adalah link_fail.
Sistem gagal untuk memantau parameter uplink adalah link_fail. Ketika
base station tidak dapat benar decode pesan SACCH, HDPC di counter
(nilai maksimum yang ditentukan oleh link_fail) dikurangi 1, base
station benar dipecahkan pesan SACCH, plus dua counter (tidak lebih
dari nilai yang ditetapkan Link_fail counter) . Ketika base station tidak
dapat dengan benar membaca sandi pesan SACCH, HDPC di counter
(nilai maksimum yang ditentukan oleh link_fail) minus 1, base station
benar diselesaikan pesan SACCH, plus dua counter (tidak lebih dari
nilai yang ditetapkan Link_fail counter) . Ketika counter nol, base
station untuk menghentikan tembakan SACCH downlink, sementara
mulai rr_t3109 timer (rr_t3109> T100). Ketika counter nol, base station
untuk menghentikan tembakan SACCH downlink, sementara mulai
rr_t3109 timer (rr_t3109> T100). T100 timeout ketika mobile station,
mobile station kembali ke modus siaga, menjatuhkan panggilan terjadi.
T100 timeout ketika mobile station, mobile station kembali ke modus
siaga, menjatuhkan panggilan terjadi. Ketika stasiun pangkalan sampai
timer rr_t3109 ke rilis saluran nirkabel. Ketika stasiun pangkalan
sampai timer rr_t3109 ke rilis saluran nirkabel. BSC juga perlu
mengirim permintaan Hapus untuk pesan MSC. BSC juga perlu
mengirim permintaan Hapus untuk pesan MSC.
Uplink dan downlink kegagalan pihak manapun, akan menghentikan
pengiriman ke setiap SACCH lain. Uplink dan downlink kegagalan pihak
manapun, akan menghentikan pengiriman ke setiap SACCH lain. Radio
sumber daya untuk memulai proses melepaskan pihak lain. Radio
sumber daya untuk memulai proses melepaskan pihak lain. TCH terjadi
di sebuah link_fail, statistik untuk RF_LOSSES_TCH pertama. TCH terjadi
di sebuah link_fail, statistik untuk RF_LOSSES_TCH pertama. Terjadi di
sebuah link_fail SDCCH, statistik untuk RF_LOSS_SD pertama. Terjadi di
sebuah link_fail SDCCH, statistik untuk RF_LOSS_SD pertama. Dalam
teori, timer dapat mempersingkat rr_t3109 rilis awal sumber daya
radio (untuk memastikan rr_t3109> T100), untuk mempersiapkan
untuk distribusi ke stasiun mobile lainnya, bisa sedikit mengurangi
kemacetan saluran. Dalam teori, timer dapat mempersingkat rr_t3109
rilis awal sumber daya radio (untuk memastikan rr_t3109> T100),
untuk mempersiapkan untuk distribusi ke stasiun mobile lainnya, bisa
sedikit mengurangi kemacetan saluran. Optimasi proses sebenarnya
tidak diubah sama sekali. Optimasi proses sebenarnya tidak diubah

sama sekali.
Parameter link nirkabel Ultra (radio_link_timeout) akan mempengaruhi
ketika ukuran tingkat drop call dan pemanfaatan sumber daya jaringan
nirkabel. Parameter link nirkabel Ultra (radio_link_timeout) akan
mempengaruhi ketika ukuran tingkat drop call dan pemanfaatan
sumber daya jaringan nirkabel. Jika diset terlalu kecil, mudah untuk
memulai handoff sebelumnya, T100 time-out, yang mengakibatkan
terputusnya sambungan yang disebabkan oleh kegagalan link nirkabel.
Jika diset terlalu kecil, mudah untuk memulai handoff sebelumnya,
T100 time-out, yang mengakibatkan terputusnya sambungan yang
disebabkan oleh kegagalan link nirkabel. Jika Anda menetapkan terlalu
besar, maka kualitas panggilan buruk, sistem waktu yang lama untuk
melepaskan sumber daya radio untuk mengurangi pemanfaatan
sumber daya. Jika Anda menetapkan terlalu besar, maka kualitas
panggilan buruk, sistem waktu yang lama untuk melepaskan sumber
daya radio untuk mengurangi pemanfaatan sumber daya.

SDCCH Success Rate Analysis-Nokia System-2

Problem Analysis :
1. Check possibility Co. or Adj. Interference and clear the BCCH
frequency.
2. Check SDCCH utilization and add SDCCH if needed.
3. Change TRP or change SDCCH allocation on TRX with good quality
based on ND 196.
4. Check TRX alarm (mostly 7745 together with7743 or 7746). Check
TRX configuration.
6. Check TA distribution, coverage distribution and propose physical
tune.
3. Optimizing parameter C2 also if Location update is the highest
contributor of SD Drop.
4. Highest contributor: Fail on RADIO, ABIS, A_IF, TR or LAPD.
5. Check TRX alarm (mostly 7745 alone or together with 7743)
7. Check RX Lev Access Min and Max Number of Retransmission. Check
RACH Rejected and SDCCH request (fails or ghost).

SDCCH Success Rate Analysis-Nokia System-1

Possible :

Interference on BCCH frequency

SDCCH Blocking

SD Drop on Location Update

A_If, TRC or LAPD Fail

HW faulty

Excessive TA

Data Collection :

ND Report 72 to check BCCH clearance

Alarm Log

TA distribution ND Report 232

Quality and Link Balance ND Report 195 and 196.

Interference UL and ND 196

HOSR Analysis-Tips on Nokia System-1

Possibilities :

Co or Adjacent BCCH

High TCH Blocking on target cell

Wrong TSC setting regarding BSIC allocation

Bad Neighbor Relation

HW faulty or Unbalance TRX power among a sector

Others ( Inter BSC-Inter MSC)

Preparation Data :
BCCH, BSIC planning, ND report 072
Cell Stat or TQM of HO distribution and ND report 153
Alarm (ZEOH & ZEOL) and site visit
Timing Advance 232
Adjacent Consistency Check ND060, 62 or 69
ND Report 73 to check Undefined Neighbor.

HOSR Analysis-Tips on Nokia System-2

Problem Analysis
1. Check possibility Co. or Adj. Interference then change BCCH
frequency.
2. Check neighbor traffic & TCH blocking, check possibility for traffic
sharing or directed retry.
3. TSC value should be same with BCC, check performance HO out and
incoming.
4. Parameter setting ADJE to make delay on worst target cell or faster
HO on best target, focused on High HO Fail. Relate parameter FMT or
AUCL.
5. Check TRX alarm (mostly 7745 together with 7743 or 7746). Check
TRX configuration.
6. Optimize coverage from TA distribution or update missing Neighbor
from ND 73.
7. Check the highest handover cause: by interference, quality, level,
power budget, GPRS, etc. Check for the highest HO failure: by Blocked,

Conn. Fail., Return to Old, End of HO,etc. The highest value is possible
as the highest contribution of HO fail.

KPI Analysis on Nokia System-TCH drop-1

Possibilities :
- Interference on BCCH TRX
- Interference on hopping TRX(DL Interference)
- External Interference (UL interference)
- Bad Neighbor Relation (bad HO)
- Low Coverage
- HW Faulty or TRX Power Unbalance
- Other : A_If, TR or LAPD Fail
Some Important Reports number for Nokia system to analyze
the TCH drop:
Preparation Data :
- BCCH Planning, ND report 072 (DL Interference distribution)
- ND Report 216, 196 and Alarm (Interference)
- ND Report 204, 153, 195 ( HO fail and Path Balance)
- ND Report 232 ( Coverage cell)
- ND Report 163 or TQM drop per causes

KPI Analysis on Nokia System-TCH drop-2

Problem Analysis:
1. Check possibility Co. or Adj. Interference. Check clean BCCH
frequency.
2. Check DL quality Distribution and Check MAL and MAIO
3. Check UL quality Distribution, check UL interference Pwr Contrl
setting to compensate interference.
4. Check % of HO fail from adjacencies, focused on High HO Fail. Check
TCH_RF_HO_OLD. Check possibility to add some neighbor. Try to
prevent un proper HO and use FMT to reduce drop.
5. Check best serving cell, possibility HO to best serving cell (Macro or
Indoor) make it faster to prevent drop.
6. Check TRX alarm (mostly 7745 together with 7743 or 7746). Check
TRX configuration or reset TRX if needed.
7. Check TA distribution, coverage spillage and proposed physical tune.
8. Check and compare which one the highest: Fail on RADIO, ABIS, A_IF,
TR or LAPD.