1.

Phenomenon Description:
Subscriber complains from area A for call setup problem after we have changed the parameters T3109 and RLT of some cells of BSC X in the border region of LAC Y and Z. So many attempts were made but very few of them are succeeded to set up a call. The cells are in suburban area. The BTS version was BTS312 and the BSC software version was V300R002C12.

2. Alarm Information:
None.

3. Cause Analysis:
The probable reasons behind the problem was the call setup problem a) Any hardware e.g. TRX or CDU fault can cause call setup problem. b) High value of VSWR can cause such problem. c) CGI mismatch can cause call setup and location update problem. d) Co-BCCH and Co-BSIC with adjacent cells can cause call setup problem. e) Very high value of TCH congestion. f) Very high value of SDCCH congestion.

4. Handling Procedure:
We followed the following steps to find out the problem a) First we have checked all the TRXs and CDUs. We also measured the VSWR. But there was no hardware problem and no VSWR problem either. b) Then we have checked the CGI of the sites but no mismatch was found. c) TRX frequencies of adjacent cells have been checked and frequency configuration was ok. There was no co- or adj- channel problem. d) After all the previous effort we collect the traffic data of the cells of problem area from OMC. We have analyzed the data and found very little value of TCH congestion but very high value of SDCCH congestion. Since the cells are at border region of two adjacent LACs we could expect some congestion obviously due to more signaling load for location updating. But the value we have found was quite unusual and far worse than expected. e) Then we changed the value of T3109 from 5s to 30s and that of RLT from 64 to 52. SDCCH congestion came to normal. The problem was solved. Hence the CSSR of those cells increased.

5. Suggestion and Summary:

The thing we have done previously was changing the values of T3109 and RLT according to the default specification of previous BSC Software version G3BSC32.10101.06.1120A where the default values are 5 and 64 respectively. But according to the BSC software version V300R002C12 we had to follow the equation T3109 = a + Radio Link Timeout * 0.48s, a = 1 or 2s to configure the parameters properly. The fact that happened in the problem was the increase of unnecessary signaling due repeated reassignment of radio resource which cause SDCCH congestion, which prevent call setup. T3109(s) Range: Unit Default: 3~34 Second T3109 = a + Radio Link Timeout * 0.48s, a = 1 or 2s. The timer starts at delivering message CHANNEL RELEASE, and stops at receiving message RELEASE INDICATION. Description: T3109 must be greater than the value of "Radio Link Timeout". Otherwise, the radio resource is reassigned before the Radio Link Timeout timer times out (that is, the radio link is not released yet). Radio Link Timeout Range: Unit 4~64, with a step-length of 4. SACCH period (480ms) Area with very little traffic (remote area): 52~64 Area with less traffic or large coverage (suburbs or rural area): 36~48 Default: Area with large traffic (urban area): 20~32 Area with very large traffic (covered by micro cells): 4~16

MS uses this parameter to determine when to disconnect the connection when SACCH decoding fails. Once MS is assigned with SDCCH, it starts the timer S with its initial value being this parameter. S decrements by 1 Description: every time when an SACCH decoding fails and S increments by 2 every time when a SACCH decoding succeeds. If S = 0, it indicates the DL radio link is faulty. Thus, the release or re-establishment of connection is guaranteed to be performed on those connections whose quality level has

deteriorated to an intolerable level. But if the parameter is too small, it will cause call-drop due to radio link faults. While when it is too large, MS will not release the resource in a long time, thus lowering the resources availability rate (this parameter works for the downlink only).