Professional Documents
Culture Documents
Single RAN, Rel. SRAN 18A, Operating Documentation, Issue 03 (HTML) > BSC/TCSM and
mcBSC/mcTC > BSC Parameters > PAFILE Timer and Parameter List > PAFILE timer and parameter
lists
BSC timers
Interpretation: The timer T4 supervises the sending of the RESET message from the BSC
to the MSC.
Timer start condition: The timer T4 starts automatically when a BSC reset occurs.
Timer stop condition: The timer T4 stops when a RESET_ACK message has been received
from the MSC.
Action performed on timer expiry: When the timer T4 expires, the BSC repeats the whole
procedure.
Appropriate value:
Min. = 10 s.
Max. = 120 s.
Def. = 60 s.
Rule = -
Signalling diagram:
localhost:1024/informationbrowser/index.jsp 1/20
4/14/2021 BSC timers
Timer start condition: The timer T7 starts when the BSC sends the
HANDOVER_REQUIRED message to the MSC.
Timer stop condition: The timer T7 stops when the HANDOVER_COMMAND or the
HANDOVER_REQUIRED_REJECT message has been received from the MSC. When the
HANDOVER_REQUIRED_REJECT message is received from the MSC the BSC may send
the following HANDOVER_REQUIRED message to the MSC. However, it can send the
message only after the timer MinIntBetweenUnsuccHoAttempt has expired.
Appropriate value:
Min. = 5 s.
Max. = 30 s.
Def. = 20 s.
Rule = -
Signalling diagram:
Interpretation: The timer T8 supervises the external handover procedure in the serving
BSC.
Timer stop condition: The timer T8 stops when a CLEAR_COMMAND message (in the
case of external handover) has been received from the MSC. It also stops when a
HANDOVER_FAILURE message is received from the MS (in the case of any handover
failure).
Action performed on timer expiry: When the timer T8 expires, the BSC sends a
CLEAR_REQUEST message to the MSC.
Appropriate value:
localhost:1024/informationbrowser/index.jsp 2/20
4/14/2021 BSC timers
Min. = 8 s.
Max. = 30 s.
Def. = 12 s.
Rule = -
Signalling diagram:
Timer start condition: The timer T10 starts before the BSC sends a
PHYSICAL_CONTEXT_REQUEST message to the BTS.
Timer stop condition: The timer T10 stops when the MS sends either an
ASSIGNMENT_COMPLETE or an ASSIGNMENT_FAILURE message to the BSC.
Action performed on timer expiry: When the timer T10 expires, the BSC sends an
ASSIGNMENT_FAILURE message to the MSC.
Appropriate value:
Min. = 4 s.
Max. = 30 s.
Def. = 8 s.
Rule = T10 > T3103, T10 > T3107
Signalling diagram:
localhost:1024/informationbrowser/index.jsp 3/20
4/14/2021 BSC timers
Interpretation: The timer T13 serves as a guard period for a local call clearing procedure.
Timer start condition: The timer T13 starts when a RESET message has been received
from the MSC.
Timer stop condition: The timer T13 stops when an SSP/SPI (subsystem
prohibited/signalling point inhibited) message is received from the SCCP.
Action performed on timer expiry: When the timer T13 expires, a reset acknowledgement
message is sent to the MSC.
Appropriate value:
Min. = 5 s.
Max. = 30 s.
Def. = 15 s.
Rule = -
Signalling diagram:
Interpretation: The timer T17 supervises the overload procedure in MSC overload.
Timer start condition: The timer T17 starts when an OVERLOAD message is received from
the MSC. For a detailed description see 3GPP TS 08.08, MSC-BSS Interface, Layer 3
Specification.
Action performed on timer expiry: When the timer T17 expires, the BSC takes new
OVERLOAD messages into account.
Appropriate value:
Min. = 1 s.
Max. = 120 s.
Def. = 4 s.
Rule = T17 < T18
This timer is started with T18, and must expire before T18 expires.
localhost:1024/informationbrowser/index.jsp 4/20
4/14/2021 BSC timers
Signalling diagram:
Interpretation: The timer T18 supervises the overload procedure. For a detailed description
see 3GPP TS 08.08, MSC-BSS Interface, Layer 3 Specification.
Timer start condition: The timer T18 starts when an OVERLOAD message is received from
the MSC. The traffic is reduced by one step. This step reduction involves barring of one
mobile access class.
Action performed on timer expiry: When the timer T18 expires, the traffic is increased on
the next level.
Appropriate value:
Min. = 3 s.
Max. = 180 s.
Def. = 12 s.
Rule = T18 > T17
This timer is started with T17, and must expire after T17 expires.
Signalling diagram:
localhost:1024/informationbrowser/index.jsp 5/20
4/14/2021 BSC timers
8. T25
Interpretation: This parameter defines the BSSMAP timer waiting for Internal Handover
Command from MSC after sending Internal Handover Required to MSC.
Timer start condition: The T25 timer starts when BSC sends INTERNAL HANDOVER
REQUIRED to MSC.
Timer stop condition: The T25 timers stops when Internal Handover Command or Internal
Handover Required Reject is received from the MSC.
Action performed on timer expiry: Internal HO Required is retried when T25 timer expires
from the MSC, based on the value of the parameter REPEAT COUNT FOR INTERNAL HO
REQUIRED. If the timer expires beyond the above count, then Internal HO procedure is
aborted in the BSC and the MS moves back to the source channel.
Appropriate value:
Min. = 5 s.
Max. = 30 s.
Def. = 20 s.
Rule = -
Timer start condition: The timer T3101 starts when the BSC sends an
IMMEDIATE_ASSIGNMENT_CMD message to the BTS.
Timer stop condition: The timer T3101 stops when an ESTABLISH_IND message is
received from the MS.
Action performed on timer expiry: When the timer T3101 expires, the BSC sends an
RF_CHANNEL_REL message to the BTS.
Appropriate value:
localhost:1024/informationbrowser/index.jsp 6/20
4/14/2021 BSC timers
Min. = 1 s.
Max. = 5 s.
Def. = 3 s.
Rule = -
Signalling diagram:
Timer start condition: The timer T3103 starts when the BSC sends a HANDOVER_CMD
message to the MS (via a BTS).
Timer stop condition: The timer T3103 stops when the BSC receives either a
HANDOVER_CMPL message on the new channel or HANDOVER_FAILURE message on
the old channel from the MS.
Action performed on timer expiry: When the timer T3103 expires, a CLEAR_REQ
message is sent to the MSC and the new channel is released.
Appropriate value:
Min. = 3,5 s.
Max. = 28 s.
Def. = 6 s.
Rule = T3103 < T10
Signalling diagram:
localhost:1024/informationbrowser/index.jsp 7/20
4/14/2021 BSC timers
Timer stop condition: If the network receives a correctly decoded layer 2 frame or the
HANDOVER_FAILURE message, it stops the timer T3105_d.
Action performed on timer expiry: When the timer T3105_d expires, the sending of the
PHYSICAL_INFORMATION message is repeated.
Appropriate value:
Signalling diagram:
Timer start condition: When the network sends the PHYSICAL_INFORMATION message,
the timer T3105 is set.
Timer stop condition: If the network receives a correctly decoded TCH frame from the MS
or the HANDOVER_FAILURE message, it stops timer T3105_f.
Action performed on timer expiry: When the timer T3105_f expires, the sending of the
PHYSICAL_INFORMATION message is repeated.
Appropriate value:
Signalling diagram:
Interpretation: The timer T3107 supervises the assignment procedure and the internal
intracell handover.
Timer start condition: The timer T3107 starts when the BSC sends an
ASSIGNMENT_CMD message to the MS (via a BTS).
Timer stop condition: The timer T3107 stops when the BSC receives either an
ASSIGNMENT_CMPL or ASSIGNMENT_FAILURE message from the MS.
Action performed on timer expiry: When the timer T3107 expires, the new and the old
channel are released, all the appropriate MS connections are cleared, and an
ASSIGNMENT_FAILURE message is sent to the MSC. In the case of the internal intracell
handover, a CLEAR_REQUEST message is sent to the MSC.
Appropriate value:
Min. = 3,5 s.
Max. = 28 s.
Def. = 6 s.
Rule = T3107 < T10
Signalling diagram:
Timer start condition: The timer T3109 starts when the BSC sends a CHANNEL_REL
message to the MS (via a BTS).
localhost:1024/informationbrowser/index.jsp 9/20
4/14/2021 BSC timers
Timer stop condition: The timer T3109 stops when the BTS sends a
RELEASE_INDICATION message. This is done after the BTS has received a DISC frame
from the MS.
Action performed on timer expiry: When the timer T3109 expires, the BSC sends an
RF_CHANNEL_REL message to the BTS.
Appropriate value:
Min. = 8 s.
Max. = 15 s.
Def. = 12 s.
Rule = -
Signalling diagram:
Interpretation: The timer T3111 delays the channel deactivation after disconnection of the
main signalling link. Its purpose is to let some time for possible repetition of the
disconnection.
Timer start condition: The timer T3111 starts when the BSC receives the
RELEASE_INDICATION message from the MS if there is no need to release the A
interface connection. If the A interface connection has to be released after the
RELEASE_INDICATION message has been received, the timer T3111 starts when the
BSC receives the CLEAR_COMMAND message from the MSC.
Action performed on timer expiry: When the timer T3111 expires, an RF_CHANNEL_REL
message is sent to the BTS.
Appropriate value:
Signalling diagram:
localhost:1024/informationbrowser/index.jsp 10/20
4/14/2021 BSC timers
Interpretation: This timer is used to supervise the CS connection release of a DTM call.
The timer is started when a RELEASE INDICATION message is received from the BTS.
When the timer expires, the BSC sends an RF CHANNEL RELEASE message to the BTS
and releases the DTM allocation that was made for the DTM call.
The timer value should be so large that the BTS has time to re-send the UA message to
the MS once if the original transmission was not received successfully. On the other hand,
the timer value should be so short that the BSC has time to release the DTM allocation
before the MS re-establishes the PS data connection in normal EGPRS mode. It is
estimated that the default value of 300 ms satisfies these conditions.
Appropriate value:
Min. = 0 ms.
Max. = 1000 ms.
Def. = 300 ms.
Rule = This timer will be used instead of the existing
T3111 timer in case of DTM call release (i.e. when the
CS connection is released in the middle of a DTM call).
17. T3121 GSM to WCDMA RAN handover procedure supervision in the source BSC
Interpretation: The timer T3121 supervises the external handover procedure from GSM to
WCDMA RAN in the serving BSC.
Timer start condition: The timer T3121 starts when a HANDOVER_COMMAND message
is received from the MSC.
Timer stop condition: The timer T3121 stops when a CLEAR_COMMAND message has
been received from the MSC. It also stops when a HANDOVER_FAILURE message is
received from the MS.
Action performed on timer expiry: When the timer T3121 expires, the BSC sends a
CLEAR_REQUEST message to the MSC.
localhost:1024/informationbrowser/index.jsp 11/20
4/14/2021 BSC timers
Appropriate value:
Min. = 8 s.
Max. = 15 s.
Def. = 12 s.
Rule = -
Signalling diagrams:
Interpretation: The timer T3122 delays the sending of another channel request.
Timer start condition: The timer T3122 starts when the MS receives an
IMMEDIATE_ASSIGNMENT_REJECT message from the BTS.
Timer stop condition: The timer T3122 stops when the MS makes a reselection for
another cell.
Action performed on timer expiry: When the timer T3122 expires, the MS sends a new
CHANNEL_REQUEST message.
Appropriate value:
Min. = 2 s.
Max. = 255 s.
Def. = 6 s.
Rule = -
Signalling diagram:
localhost:1024/informationbrowser/index.jsp 12/20
4/14/2021 BSC timers
Interpretation: The timer T3168 is used on the mobile station side to define when to stop
waiting for a Packet Uplink Assignment message after sending of a Packet Resource
request message. The unit is 500 ms (0 = 500 ms, 1 = 1 s, 2 = 1.5 s, etc.).
Appropriate value:
Min: 0
Max: 7
Def: 1
Rule = -
Note that after a modification to this timer it takes about 5 minutes for processes to get the
new values. After 5 minutes disable and then re-enable GPRS in those cells where GPRS is
active for the change to take effect.
20. T3192 Wait for release of the TBF after reception of the final block
Interpretation: The timer T3192 is used on the mobile station side when the mobile station
has received all of the RLC data blocks. When the timer T3192 expires the mobile station
shall release the resources associated with the TBF (for example TFI) and begins to
monitor its paging channel. The unit is 500 ms (0 = 500 ms, 1 = 1 s, 2 = 1.5 s).
Appropriate value:
Min: 0
Max: 2
Def: 0
Rule = -
Note that after a modification to this timer it takes about 5 minutes for processes to get the
new values. After 5 minutes disable and then re-enable GPRS in those cells where GPRS is
active for the change to take effect.
21. T3192_SAT
Interpretation: The timer T3192_SAT is used with PCU2 in satellite Abis case. The original
T3192 timer is used with PCU2 in terrestrial Abis case and with PCU1. The timer
T3192_SAT is used on the mobile station side when the mobile station has received all of
the RLC data blocks. When the timer T3192_SAT expires the mobile station shall release
the resources associated with the TBF (for example TFI) and begins to monitor its paging
channel. The unit is 500 ms starting from 1 s (1 = 1 s, 2 = 1.5 s).
localhost:1024/informationbrowser/index.jsp 13/20
4/14/2021 BSC timers
Appropriate value:
Min: 1
Max: 2
Def: 2
Rule = -
Note that after a modification to this timer it takes about 5 minutes for processes to get the
new values. After 5 minutes disable and then re-enable GRPS in those cells where GPRS is
active for the change to take effect.
22. T3226
Interpretation: This parameter is used to define the value of T3226 timer for EC-GSM IoT.
Parameter is sent in EC-SI message to MS's. MS uses this timer value to delay the
PACCH monitoring after transmission of last allocated RLC data block in UL against fixed
uplink allocation (FUA).
The parameter value is coded into EC-SI message according to the following:
000 20 ms
001 60 ms
010 100 ms
011 200 ms
100 500 ms
101 700 ms
110 1000 ms
111 1200 ms
23. T3230
Interpretation: The timer T3230 indicates the time for which the signalled individual
priorities are valid.
Timer start condition: The timer T3230 starts when the MS receives an Individual priorities
IE. The value of the timer T3230 is supplied in the Individual priorities IE.
Timer stop condition: The timer T3230 uses 3 bits to indicate the time for which the
signalled Individual priorities are valid:
localhost:1024/informationbrowser/index.jsp 14/20
4/14/2021 BSC timers
0 0 0 5 minute timeout;
0 0 1 10 minute timeout;
0 1 0 20 minute timeout;
0 1 1 30 minute timeout;
1 0 0 60 minute timeout;
1 0 1 120 minute timeout;
1 1 0 180 minute timeout;
Timer start condition: The timer T9101 starts when the BSC sends the
CLEAR_COMPLETE message to the MSC.
Timer stop condition: The timer T9101 stops when the RLSD message has been received
from the MSC.
Action performed on timer expiry: When the timer T9101 expires, the BSC releases the
SCCP connection by sending the RLSD message.
Appropriate value:
Def. = 10 s. (non-modifiable)
Signalling diagram:
Timer start condition: The timer T9103 starts when the BSC sends the
CHANNEL_ACTIVATION message to the BTS.
Timer stop condition: The timer T9103 stops when the CHANNEL_ACTIVATION_ACK or
the CHANNEL_ACTIVATION_NACK message has been received from the BTS.
localhost:1024/informationbrowser/index.jsp 15/20
4/14/2021 BSC timers
Action performed on timer expiry: When the timer T9103 expires, an RF_CHANNEL_REL
message is sent to the BTS.
Appropriate value:
Def. = 2 s. (non-modifiable)
Signalling diagram:
Interpretation: The timer T9104 supervises the clear command that comes from the MSC.
Timer start condition: The timer T9104 starts when the BSC sends a CLEAR_REQ
message to the MSC.
Timer stop condition: The timer T9104 stops when the BSC receives a CLEAR_CMD
message from the MSC.
Action performed on timer expiry: When the timer T9104 expires, the CLEAR_REQ
message is repeated a maximum of four times.
Appropriate value:
Min. = 5 s.
Max. = 30 s.
Def. = 15 s.
Rule = -
Signalling diagram:
localhost:1024/informationbrowser/index.jsp 16/20
4/14/2021 BSC timers
Timer start condition: The timer T9105 starts when the BSC sends an
SCCP_CONNECTION_REQ message to the MSC.
Timer stop condition: The timer T9105 stops when the BSC receives either an
SCCP_CONNECTION_CONFIRM or SCCP_CONNECTION_REFUSED message from
the MSC.
Action performed on timer expiry: When the timer T9105 expires, the BSC sends a
CHANNEL_REL message to the MS (via a BTS).
Appropriate value:
Min. = 2 s.
Max. = 240 s.
Def. = 10 s.
Rule = -
Signalling diagram:
Interpretation: The timer T9108 supervises the physical context request procedure.
Timer start condition: The timer T9108 starts when the BSC sends the
PHYSICAL_CONTEXT_REQUEST message to the BTS.
Timer stop condition: The timer T9108 stops when the BSC receives the
PHYSICAL_CONTEXT_CONFIRM message from the BTS.
Action performed on timer expiry: When the timer T9108 expires, the BSC sends an
ASSIGNMENT_FAILURE message to the MSC.
Appropriate value:
Def. = 2 s. (non-modifiable)
Signalling diagram:
localhost:1024/informationbrowser/index.jsp 17/20
4/14/2021 BSC timers
29. T9113 Supervision of the external handover procedure in the target BSC
Interpretation: The timer T9113 supervises the external handover in the target BSC.
Timer start condition: The timer T9113 starts when the BSC sends a
HANDOVER_REQUEST_ACK message to the MSC.
Timer stop condition: The timer T9113 stops either when the MS sends a
HANDOVER_CMP message or the MSC sends a CLEAR_CMD message.
Action performed on timer expiry: When the timer T9113 expires, the BSC sends a
CLEAR_REQUEST message to the MSC.
Appropriate value:
Min. = 8 s.
Max. = 30 s.
Def. = 13 s.
Rule = -
Signalling diagram:
Figure: T9113 timer activation with a CLEAR_CMD message from the MSC
Interpretation: The TBBI timer supervises the Measurement Relation Initiation procedure
in the BSC - BSC interface.
Timer start condition: The TBBI timer starts when a MEASUREMENT RELATION
INITIATION REQUEST message is sent to the other BSC.
Timer stop condition: The timer TBBI stops when a MEASUREMENT RELATION
INITIATION RESPONSE message has been received from the other BSC. It also stops
localhost:1024/informationbrowser/index.jsp 18/20
4/14/2021 BSC timers
Action performed on timer expiry: When the timer TBBI expires, the 'Unknown potentially
interfering cell for DFCA' alarm is set.
Appropriate value:
Min. = 1 s.
Max. = 60 s.
Def. = 15 s.
Rule = -
Note that this timer has effect only if the DFCA application software is activated.
Signalling diagram:
31. CSDAP
Timer start condition: Penalty timer for the CSDAP starts when penalty threshold of
detected hunting errors is exceeded.
Timer stop condition: Penalty timer for the CSDAP stops when one successful resource
allocation and normal release has been performed for the CSDAP during the trial period
or trial period timer expires.
Action performed on timer expiry: If there are no working circuits in CSDAP or there is
detected a hunting error or erroneous call release then penalty timer is restarted.
Appropriate value:
Min. = 1 s.
Max. = 255 s.
localhost:1024/informationbrowser/index.jsp 19/20
4/14/2021 BSC timers
Def. = 90 s.
Rule = -
localhost:1024/informationbrowser/index.jsp 20/20