Case Study

High SDCCH over A interface problem on

NSN BSCs with Hawaii MSC.

Author Name: Mohammed Hossam

Date: 12-October-2014

For internal use

1 © Nokia Siemens Networks 2013 CEF HR CoE C&B PMI / 2013-01-28 -- Version: 1.0 / Life Cycle: ATP 2013
 Case Study Reference Related case studies (documents):
Reference ID: 05-08-2014:Du:
BSC: S16.1 0.1.0
Author Reference: Mohammed Hossam

Case Study Type Case Study Audience:

High SDCCH over A interface problem over NSN BSCs with Direct audience: MBB1 Radio Team ,Customer Technical
Hawaii MSC. Manager

Indirect Audience: Project Manager ,Line Manager, Customer

Technical Manager, COM RSO Steam head

Case Study Status Case Study team

Role Name
Status Date
Author Mohammed Hossam
Completed 10-07-2014
Contribute 1 Mohamed Hafez
Date of correction 25-06-2014
Contribute 2 Bachir Cheaib

For internal use

2 © Nokia Siemens Networks 2013 CEF HR CoE C&B PMI / 2013-01-28 -- Version: 1.0 / Life Cycle: ATP 2013
 Case Study Problem Description Problem description symptoms
For the most degraded SDCCH_A_IF failures BSCs, it has HWs
We have check SDCCH_A_IF Failures trend over all NSN greater than 154 HWs and connected to Hawaii MSC
BSCs,
We have Found that some BSC have high failures
compared with others

Impact Symptoms based problem description

Affect in the SDDCH drop rate formula For the most degraded SDCCH_A_IF failures BSCs, it has
HWs greater than 154 HWs and connected to Hawaii MSC

For internal use

3 © Nokia Siemens Networks 2013 CEF HR CoE C&B PMI / 2013-01-28 -- Version: 1.0 / Life Cycle: ATP 2013
 Case Study Troubleshooting
Fishing trace has been performed on BSC to identify the
DX release cause on the BSC
From the trace we have found that SDCCH failure on the A
interface increase with several instances where DX
release_cause -> a_crct_alr_res_c is getting updated.
Meaning that A PCM_TSL which is reserved for a new call is
being used for another call before that call is getting
released, this makes RC0PRB to acknowledge AIVPRB with
failure indication for the circuit reservation (same PCM_TSL).
MSC is sending CIC (Circuit Identity Code) information to
AIV in assignment request containing the PCM_TSL which is
already reserved for another ongoing call. AIV will  unpack
the CIC and send to RC0PRB for the circuit reservation.
Attachments
For internal use
4 © Nokia Siemens Networks 2013 CEF HR CoE C&B PMI / 2013-01-28 -- Version: 1.0 / Life Cycle: ATP 2013
Investigation details
Since a call is already ongoing with same PCM/TSL, so the DX is
necking with the cause a_crct_alr_res_c, which confirm that there
is no problem from the BSC side.
Also it was noticed that BSC have two) connected to MGWJ1,
First AIETGs handled HWs 1 till 156 HW old one, and new second
one handled HWs from 157 till 190 HWs, with high CICs
assignment on the second AIETG
So the second AIETG will be full first, under this condition if the
MSC finds that the number idle circuits of second AIETG is
already 0, then MSC will always selects circuits from the first
AIETG.
Illustrations
DX release_cause -> a_crct_alr_res_c is getting updated
 Analysis of troubleshooting
Finally we suggest to core operation team to load sharing
same created number of CICs over 2 AIETG.
After above our suggested action , SDCCH failures over A
interface has been totally cleared and drops enhanced 95 % on
BSC as shown
Attachments
For internal use
5 © Nokia Siemens Networks 2013 CEF HR CoE C&B PMI / 2013-01-28 -- Version: 1.0 / Life Cycle: ATP 2013
Analysis Summary:
SDCCH_A_IF_call failures on BSC , there is assignment problem from
the MSC side over all the BSCs which created with HWs greater than
156 HWs , when second AIETG being used over the MSC ,
Illustrations
DX release_cause -> a_crct_alr_res_c is getting updated , during the performed trace
 Case Study Result Risks and impact:
:
High MSC assignment failures affected on the SDCCH_A_IF
failures

Solution steps:
Action items and next steps if any
 load sharing by create same number of CICs over 2 AIETG
from the core side over all affected BSCs

Recommendations Lessons learned

For any future implementation for created HWs

greater than 156 per BSC, its recommended to do
load sharing by create same number of CICs over 2
AIETG .
.
For internal use

6 © Nokia Siemens Networks 2013 CEF HR CoE C&B PMI / 2013-01-28 -- Version: 1.0 / Life Cycle: ATP 2013