#How is the CSSR formula ?

CSSR_w/o_block = ImmAss SR x SSS Proc SR x Ass TCH

ImAss Phase
SSS Proc Phase
TCH Assignment Phase
ImmAss SR = NSUCCHPC(APSD,CRSD,ECSD,OCSD)
NSUCCHPC(SMTCSD)
SSS Proc SR = TASSAT (F,H)
NSUCCHPC(APSD,CRSD,ECSD,OCSD)
TCH Ass SR =
TASSSUCC(F,H)+TASSFAIL(NRF,NRH)+SINTHINT(DR)+SUINBHDO(DR)+SUOISHDO(DR)
CSSR_w/o_block = ImmAss SR x SSS Proc SR x Ass TCH
ImmAss SR = NSUCCHPC(APSD,CRSD,ECSD,OCSD)-
SSS Proc SR = TASSAT (F,H)
NSUCCHPC(APSD,CRSD,ECSD,OCSD)-
TASSSUCC(F,H)+TASSFAIL(NRF,NRH)+SINTHINT(DR)+SUINBHDO(DR)+SUOISHDO(DR)
Analysis
#What factor can influence within this phase ?
Phase I : ATIMASCA - SUIMASCA
Loss probability :
a. No SDCCH available
- High number of request
- Lack of SDCCH resources
- Over idle coverage
b. Transmission problem
- flicker transmission
- not LOS transmission (obstacle)
- unnecessary cabling on DDF panel
- problems on COBA/COSA module
c. HW problem & wrong installation on BTS
- high VSWR
- broken module
- untight connector
- broken cable/feeder ; high loss
- fabrication faulty : BTS mainboard, module slot
- cell inversion : antenna, feeder, backplane, semirigid, wrong HW db creation
d. Radio Interface problem
- frequency interference
- unbalance UL & DL due to improper coverage (overshoot or lack of coverage), contour factor
- unnecessary db setting

Phase II : SUIMASCA - NSUCCHPC
Loss probability :
a. Transmission problem
- see point b on phase I explanation
b. AGCH overload
- see statistic meas : difference between TACCBPRO (
- if the differences > 0
c. Radio Interface problem
MS might be due to MS used 'phantom' RACH when send CHNREQ
- see point d on phase I explanation
d. HW problem & wrong installation on BTS
- see point c on phase I explanation
Action
Phase I : ATIMASCA - SUIMASCA
a. No SDCCH available -> SDCCH attempt meeting blocked
High number of request
Lack of SDCCH resources
Over idle coverage
b. Transmission problem - Abis interface -> messages loss (CHNAV, CHNAK) between BTS and BSC
flicker transmission
not LOS transmission (obstacle) -> wrong transmission planning
unnecessary cabling on DDF panel
problems on COBA/COSA module
c. HW problem & wrong installation on BTS -> bad processing/failure, un-received/sent of messages toward BTS/MS
untight connector
broken cable/feeder ; high loss
fabrication faulty : BTS mainboard, module slot
cell inversion : antenna, feeder, backplane, semirigid, wrong HW db creation
d. Radio Interface problem -> messages loss between MS and BTS
frequency interference
unbalance UL & DL due to improper coverage (overshoot or lack of coverage), contour factor
unnecessary db setting
Phase II : SUIMASCA - NSUCCHPC
a. Transmission problem - Abis interface -> messages loss (IMASS, ESTIN) between BTS and BSC
see point b on phase I explanation
see statistic meas : difference between TACCBPRO (2) - NACSUCPR(2)
if the differences > 0 means there are AGCH overload
c. Radio Interface problem -> messages (IMASS, SABM, CMSREQ) loss between MS and BTS ; no SABM sent to BTS by
MS might be due to MS used 'phantom' RACH when send CHNREQ
see point d on phase I explanation
d. HW problem & wrong installation on BTS -> bad processing/failure, un-received/sent of messages toward BTS/MS
see point c on phase I explanation
a. SDCCH capacity overhandling might be done by :
- adding SDCCH TS within TRX
- more selective on filtering MS for accessing network => only MS with good UL level can access the cell and get RACH
(set RXLEVAMI, RACHBT)
- reduce the (over) coverage by tilting adjustment
b. Radio Interface quality improvement :
- frequency retune
- hopping optimization (hop mode, hop activation, HSN, maio, mall lists
- power control mechanism (threshold, step size)
- no over coverage for preventing interfering with others => done by coverage adjustment
- antenna optimization (ant type with proper beamwidth, ant height, azimuth, tilt)
c. HW problem & wrong installation fixing :
- changing any broken module/equipment
- fix any wrong installation
d. Transmission problem overhandling :
- transmission replan by TNP (if no LOS) by antenna
- fix any transmission cabling/connection problem and module failure

a. Solving AGCH overload by :
- adding block AGCH reserved => set NBLKACGR, but must consider PCH reserved reducing impact by increasing this AGCH capacit
b. Radio Interface quality improvement :
- see point b on explanation above
c. HW problem & wrong installation fixing :
- see point c on explanation above
d. Transmission problem overhandling :
- see point d on explanation above
a. SDCCH capacity overhandling might be done by :
adding SDCCH TS within TRX
more selective on filtering MS for accessing network => only MS with good UL level can access the cell and get RACH
(set RXLEVAMI, RACHBT)
reduce the (over) coverage by tilting adjustment
b. Radio Interface quality improvement :
frequency retune
hopping optimization (hop mode, hop activation, HSN, maio, mall lists - check it all) - for dedicated mode
power control mechanism (threshold, step size) - for dedicated mode
no over coverage for preventing interfering with others => done by coverage adjustment
antenna optimization (ant type with proper beamwidth, ant height, azimuth, tilt)
c. HW problem & wrong installation fixing :
changing any broken module/equipment
fix any wrong installation
d. Transmission problem overhandling :
transmission replan by TNP (if no LOS) by antenna w optimization (height), transmission re-route
fix any transmission cabling/connection problem and module failure
a. Solving AGCH overload by :
adding block AGCH reserved => set NBLKACGR, but must consider PCH reserved reducing impact by increasing this AGCH capacity
b. Radio Interface quality improvement :
see point b on explanation above
c. HW problem & wrong installation fixing :
see point c on explanation above
d. Transmission problem overhandling :
see point d on explanation above
#What kind of process (procedures) occurred within this phase ?
#How can the SDCCH connection become drop ?
Counter Sub Counter Description
1 T200 expired
2 unsolicited DM response, multi frame established state
N
F
R
L
S
D
C
C

(
1
,
3
)
- SSS Procedure Phase start from CMS REQ
- SDCCH are already seized within this phase.
- Many SSS procedure events are performed during this phase, that are authentication, ciphering, IMEI check, TMSI re
procedures.
- From BSS point of view, loss analysis can be got from
Authentication Process
Ciphering Process
When BTS has sent layer
layer 2 acknowledgement from MS (reasons : any radio problems may exist)


What may be the most drop reason can be known from mesurement counter NRFLSDCC [1-9] :
MS has sent a Um layer
BTS has detected irregularities in the Um layer
3 sequence error
4 T_MSRFPCI expired
5 distance limit exceeded
6 handover access failure
7 radio link failure
8 remote transcoder failure
9 unspecified (others)
N
F
R
L
S
D
C
C

(
1
,
3
)
Radio Problems (interference, coverage, HW&Installation)
TRACK/TRAU module failure, COBA/CU failure, wrong DB setting (TTRAU > T
Failure on HO SDCCH-SDCCH ; Causes : Radio Problems (interference, coverage,
BTS has detected irregularities in the Um layer
T_MSRFPCL is not adjustable on database
MS-BTS distance exceeds the threshold
SSS Procedure Phase start from CMS REQ message sent from BSC towards MSC, and stop after receipt of ASS REQ.
SDCCH are already seized within this phase.
Many SSS procedure events are performed during this phase, that are authentication, ciphering, IMEI check, TMSI re-allocation, setup message, and digit translation
, loss analysis can be got from SDCCH drop counter (NRLFSDCC_1-9)
IMEI Check & TMSI
Reallocation Procedure
Setup Message & Digit
Translation Procedure
When BTS has sent layer 2 message in acknowledge mode (that is I frame message : ASS CMD) N200+1 times to the MS without receiving
acknowledgement from MS (reasons : any radio problems may exist) until T200 timer expired, then the connections are dropped.
MS has sent a Um layer 2 (LAPDm) message DM (Mode) to the BTS while the BTS-MS communication is in multiple frame stablished
BTS has detected irregularities in the Um layer 2 (LAPDm) flow control functions (wrong message sequence) useds inacknowledged mode
Radio Problems (interference, coverage, HW&Installation)
TRACK/TRAU module failure, COBA/CU failure, wrong DB setting (TTRAU > T8 , TTRAU > T10, TTRAU = TSYNC => This setting is for ensuring that a signaling failure (T
Failure on HO SDCCH-SDCCH ; Causes : Radio Problems (interference, coverage,
BTS has detected irregularities in the Um layer 2 (LAPDm) flow control functions (wrong message sequence) useds inacknowledged mode
T_MSRFPCL is not adjustable on database
BTS distance exceeds the threshold
, TTRAU = TSYNC => This setting is for ensuring that a signaling failure (T8 and T10) is detected before transcoder failure (TSYNC and TTRAU)
#How is this phase ?
#TASSFAIL causes ?
TCH/F TCH/H
6 11
7 12
8 13
9 14
10 15
Sub Counter for CHAN TYPE
Counter Description
T
A
S
S
F
A
I
L

(
1
,
3
0
)
Radio Interface Message Failure
Radio Interface Failure - reversion to old channel
No radio resource available
Directed Retry
Al Other Cause
- TCH Assignment Phase start after receiving assignment request
- BSS Counter start from TASSATT and end by TASSSUCC
- Actually TCH Blocking influence this phase,
formula
- There is still loss probability on
- Any TCH Assignment Failure will increment
TASSFAIL due to Radio Interface Message Failure
ASS CMD message is lost, may be caused by :
- Radio Interface problem : Interference, Coverage, HW Failure / Wrong Installation
- unnecessary
Counted as TCH Assignment Success on KPI CSSR
Formula HCPT -> see shet formula
TASSFAIL due to Radio Interface Failure - reversion to old channel
SABM message is lost while using FACCH, assignment TCH fail and
- Radio Interface problem : Interference, Coverage, HW Failure / Wrong Installation
- unnecessary T
Directed Retry HO ACCESS
- Radio Interface problem : Interference, Coverage, HW Failure / Wrong Installation
Directed Retry HO ACCESS
- Radio Interface problem : Interference, Coverage, HW Failure / Wrong Installation
TASSFAIL due to Directed Retry
When Directed Retry
TCH Assignment Phase start after receiving assignment request (ASS REQ) message on BSC from MSC, and stop after assignment complete (ASS COM) message sending
BSS Counter start from TASSATT and end by TASSSUCC
Actually TCH Blocking influence this phase, BUT on KPI Formula HCPT for CSSR, TCH blocking is excluded from TCH assignment failure, but counted as TCH Assignment Success
There is still loss probability on SDCCH Drop with T200 expiry reason within this phase => check if any radio problem which cause loss of ASS CMD message
Any TCH Assignment Failure will increment TASSFAIL counter in BSC
message is lost, may be caused by :
Radio Interface problem : Interference, Coverage, HW Failure / Wrong Installation
unnecessary T10 setting
Counted as TCH Assignment Success on KPI CSSR
> see shet formula
message is lost while using FACCH, assignment TCH fail and back to SDCCH , may be caused by :
Radio Interface problem : Interference, Coverage, HW Failure / Wrong Installation
unnecessary T10 setting
Directed Retry HO ACCESS message is lost while using FACCH, assignment TCH fail and back to SDCCH on old cell , may be caused by :
Radio Interface problem : Interference, Coverage, HW Failure / Wrong Installation
Directed Retry HO ACCESS message is lost while using FACCH, assignment TCH fail and back to SDCCH on old cell , may be caused by :
Radio Interface problem : Interference, Coverage, HW Failure / Wrong Installation
Directed Retry HO is performed, TASSFAIL(9) counter will be incremented
message sending
from TCH assignment failure, but counted as TCH Assignment Success -> see on sheet
which cause loss of ASS CMD message
DB Parameter Related
RXLEVAMI BTS
Minimum received level at the MS
required for access to the network
Increase => Idle coverage shrinking, less attempt SDCCH
Decrease => Idle coverage enlargement, more attempt SDCCH
RACHBT BTS Threshold for the signal level on RACH
Increase => Low UL level can access RACH, more attempt
SDCCH, less HO fail possibility due to FACCH rejected.
Decrease => Only good UL level can access RACH, less
attempt SDCCH, more HO fail possibility due to FACCH
rejected.
NBLKACGR BTS
Specifies the number of CCCH blocks
to be reserved in CCCH TS for AGCH ;
MAINBCCH provides 9 CCCH blocks
(shared between PCH and AGCH)
Increase => Add CCCH blocks to be reserved for AGCH,
decrease blockes to be reserved for PCH.
Decrease => vica versa from statement above.
T200 BTS
LAPDm timer 200 ; determines the
waiting time for a layer 2 frame
acknowledgement
Should be attended that this timer setting can much reduce drop
call / signalling conection, but can also deliver non realistic
image of the actual radio interface quality (less drop but poor
quality). So need proper adjustment as trade off
IERCHOSDCCH BTS
To enable / disable intercell SDCCH
HO
Set True => activate intercell SDCCH HO, more SDCCH usage,
more possibility on SDCCH fail/drop. Set FALSE => disabling
intercell SDCCH HO, less SDCCH usage, less possibility on
SDCCH fail/drop
IRACHOSDCCH BTS
To enable / disable intracell SDCCH
HO
Set True => activate intercell SDCCH HO, more SDCCH usage,
more possibility on SDCCH fail/drop. Set FALSE => disabling
intercell SDCCH HO, less SDCCH usage, less possibility on
SDCCH fail/drop
EISDCCHHO BTS
To enable / disable interBSC SDCCH
HO
Set True => activate intercell SDCCH HO, more SDCCH usage,
more possibility on SDCCH fail/drop. Set FALSE => disabling
intercell SDCCH HO, less SDCCH usage, less possibility on
SDCCH fail/drop
TTRAU BTS
Timer supervision start from sending
UL TRAU frame and stop when first DL
TRAU frame received by BTS
Must set to proper value ; Must follow the rule : TTRAU > T8,
TTRAU > T10, TTRAU = TSYNC for ensuring signalling failure
is detected before transcoder failure
TSYNC
BTS ;
TRAU
Timer supervision start of TRAU frame
handling. Start when 3 DL TRAU frame
haven't correctly received, and reset
when correct frame is received again.
Must be set to proper value ; Must follow the rule : TSYNC =
TTRAU ; TSYNC setting in BTS object must be same with
TSYNC setting in TRAU object
T10 BSC
Time to return assignment complete
(ASS CMP) message. Start from
sending message ASS CMD and stop
when ASS CMP received.
Must be set to proper value ; In the case of call setup, the
setting must follow the rule : T10 < TTRAU
Value Setting Trade Off DB Parameter Object Description