45847764 gsm timers document

Mobilink Confidential Property

1

TIMERS

RF OPTIMIZATION ENGINEERING ACCESS NETWORK

PMCL [MOBILINK]


2

FOREWORD The document aims to describe various timers implemented in the GSM network. While reasonable efforts have been made to assure the accuracy of this document, PMCL assumes no liability resulting from any inaccuracies or omissions in this document, or from the use of the information obtained herein.

PMCL reserves the right to make changes from time to time in the content of this document and hereof with no obligation to notify any person of revisions or changes.


3

TABLE OF CONTENTS

1.0 Introduction 5 2.0 What does the manual cover? 5 3.0 Why the need to study timers? 5 4.0 Timer Categorization 6 4.1 Entity Based Categorization 6 4.2 Process Flow Based Categorization 6

5.0 Breakdown 7 6.0 GSM Timers 9 6.1 Call Setup 10 6.1.1 T3120 12 6.1.2 T3126 13 6.1.3 T3101 14 6.1.4 T3230 15 6.1.5 T303 16 6.1.6 T310 17 6.1.7 T11 18 6.1.8 T10 19 6.1.9 T313 20 6.1.10 T3107 21 6.1.11 T1 22 6.2 Call Clearing 23 6.2.1 T13 23 6.2.2 T3111 24 6.2.3 T3109 25 6.2.4 T3110 26 6.3 Handover 27 6.3.1 T3103 28 6.3.2 T8 29 6.3.3 T7 30 6.3.4 TQHO 31 6.3.5 T3121 32 6.4 GPRS 32 6.4.1 T3182 33 6.4.2 T3164 34 6.4.3 T3198 35 6.4.4 T3180 36 6.4.5 T3190 37 6.4.6 T3192 38 6.4.7 T3200 39


4

6.4.8 T3162 40 6.4.9 T3168 41 6.4.10 T3170 42 6.4.11 T3172 43 6.4.12 T3176 44 6.4.13 T3188 45 6.4.14 T3322 46 6.4.15 T3380 47 6.4.16 T3385 48 6.4.17 T3386 49 6.4.18 T3390 50 6.4.19 T3395 51 6.4.20 T3158 52 6.4.21 T3166 53 6.4.22 T3169 54 6.4.23 T3174 55 6.4.24 T3182 56 6.4.25 T3178 57 6.4.26 T3184 58 6.4.27 T3191 59 6.4.28 T3193 60 6.4.29 T3195 61 6.4.30 T3310 62 6.4.31 T3312 63 6.4.32 T3314 64 6.4.33 T3321 65 6.5 Miscellaneous 66 6.5.1 T3210 66 6.5.2 T3128 67 6.5.3 T3211 68 6.5.4 T3212 69 6.5.5 T3220 70

7.0 Compiled List 71 7.1 Motorola Timers List 71 7.2 Alcatel Timers List 73 7.3 Huawei Timers List 76


5

1.0 INTRODUCTION

Like any other wireless technology with a limited pool of resources, GSM resource allocation and termination depends primarily on timers. The functionality and protocols may vary, but the presence of timer based signaling and resource allocation is ubiquitous. Timer implementation is present in each domain of the GSM system from MS to NSS end.

2.0 WHAT DOES THIS MANUAL COVER?

This document aims to describe all the major BSS timers involved in the GSM architecture. The timers are categorized into different subgroups, depending upon their parent entity and the process flow they are involved in. The document proceeds further by giving a detailed explanation of each timer along with its implementation in the PMCL network.

3.0 WHY THE NEED TO STUDY TIMERS?

As already highlighted, timer implementation is present throughout the GSM architecture. Timers effect call setup procedures, handovers, call clearing, data usage (GPRS), VAS facilities; in short, everything that a customer might do to access and utilize the GSM network. Therefore, for a high quality network, it is imperative to have impeccable timing. Precise synchronization and timing improves call signal hand over performance between base stations; and, as an added benefit, reduces customer complaints. GSM networks are dependent on strict synchronization of the base stations to facilitate call handovers.

Furthermore, the reason for a deep understanding of timers is also

re‐enforced by the multi vendor implementation present at all levels of the network. Such a scenario demands all database discrepancies to be eliminated to ensure coherence and inter‐vendor compatibility.


6

4.0 TIMER CATEGORIZATION

4.1 ENTITY BASED CATEGORIZATION As highlighted earlier there are different ways of categorizing timers. One categorization can be done on the basis of entity which includes the following categories:

4.2 PROCESS FLOW BASED CATEGORIZATION A further classification of GSM timers can be done on the basis of

process flows involved in the system. These include the following basic categories:

• Call Processing Call Setup Call Release

• Handovers • GPRS • Miscellaneous


7

5.0 BREAKDOWN [PHASE 1]

The task of documenting the GSM timers is not an easy paced procedure. The project is divided into two phases. The first phase comprised of the research for all the timers involved from MS to BSS as per the international GSM standards. In the second phase, vendor implementations of these timers were taken into consideration. A complete overview of all the timers involved in Phase 1 is as under:

Timer Call Flow Vendor Timer's Name Category Default Value

Range

T3120 Call Setup

Motorola MS Timer MS Timer ‐ ‐Alcatel MS Timer MS Timer ‐ ‐

Huawei T3120 MS Timer Min is RACH T+2S; MAX 5

Min is RACH T+2S ;MAX 5

T3126 Call Setup

Motorola MS Timer MS Timer ‐ ‐Alcatel MS Timer MS Timer ‐ ‐

Huawei T3126 MS Timer Min is RACH T+2S MAX 5

Min is RACH T+2S MAX 5

T3122 Call Setup Motorola wait_indication_parameter BTS none 0 to 255 secAlcatel T3122 MS Timer ‐ 0 to 255 secHuawei T3122 Cell Timer 10 sec 0‐255 sec

T3101 Call Setup Motorola rr_t3101 BTS 5 sec 0 to 1000 secAlcatel T3101 BSC level 3 sec 0 to 25.5 secHuawei T3101 Cell Timer 3 sec 0.5 to 60 sec

T3230 Call Setup Motorola MS Timer MS Timer ‐ ‐Alcatel MS Timer MS Timer ‐ ‐Huawei T3230 MS Timer 15 sec 15 sec

T303 Call Setup Motorola MS Timer MS Timer ‐ ‐Alcatel MS Timer MS Timer ‐ ‐Huawei T303 MSC Timer 20 sec ‐

T310 Call Setup Motorola MS Timer MS Timer ‐ ‐Alcatel MS Timer MS Timer ‐ ‐Huawei T310 MSC Timer 20 sec ‐

T11 Call Setup Motorola bssmap_t11 BTS 28 sec 0 to 1000 secAlcatel T11 BSS 6 sec 0 to 19 secHuawei T11 BSC Timer 8 sec 1 to 30 sec

T10 Call Setup Motorola bssmap_t10 BTS 28 sec 0 to 1000 secAlcatel bssMapT10 BSS 14 sec ‐Huawei T10 BSC Timer 7 sec 1 to 20 sec

T313 Call Setup Motorola ‐ MSC timer ‐ ‐Alcatel T313 MS Timer ‐ ‐Huawei T313 MSC Timer 30 sec 30 sec

T8 Handover Motorola bssmap_t8 BTS 28 sec 0 to 1000 secAlcatel bssMapT8 BSS 14 sec 0 to 25.5 secHuawei T8 Cell Timer 10 sec 0.5 to 60 sec

T3103 Handover Motorola rr_t3103 BTS 30 sec 0 to 1000 sec


8

Alcatel T3103 BSS 16.5 sec 0 to 25.5 secHuawei T3103 Cell Timer 10 sec 0.5 to 60 sec

T1 GPRS Motorola bssmap_t1 BSC 30 sec

0 to 1000000 msec

Alcatel bssMapT1 BSS 16 sec 10 to 25.5 secHuawei T1 BSC Timer 30 sec 1 to 300 sec

T13 Call Clearing Motorola bssmap_t13 BSC 40 sec 0 to 1000 secAlcatel bssMapT13 BSS 15 sec 0 to 6553.5 secHuawei T13 BSC Timer 150 sec 1 to 300 sec

T7 Handover Motorola bssmap_t7 BSC 30 sec 0 to 1000 secAlcatel bssMapT7 BSS 5 sec 0 to 20 secHuawei T7 Cell Timer 10 sec 0.5 to 60 sec

TQHO Handover Motorola bssmap_tqho BSC 30 sec 0 to 1000 secAlcatel T_QHO BSS 3 sec 0 to 20 secHuawei TQHO BSC Timer 8 sec 1 to 30 sec

T3111 Call Clearing Motorola

rr_t3111_sd BTS 1.5 sec 0 to 1000 secrr_t3111_tch BTS 1.5 sec 0 to 1000 sec

Alcatel T3111 BSS 0.5 sec 0 to 2 secHuawei T3111 Cell Timer 1 sec 0.5 to 60 sec

T3109 Call Clearing Motorola rr_t3109 BTS 14.4 sec 0 to 1000 secAlcatel T3109 BSS 12 sec 0 to 35 secHuawei T3109 Cell Timer 27 sec 1‐35 sec

T3121 Handover Motorola ‐ MSC Timer ‐ ‐Alcatel T3121 BSS 14 sec 0 to 25.5 secHuawei T3121 Cell Timer 10 sec 0.5 to 60

T3107 Call Setup Motorola RRSM_T10 BTS 28 sec 0 to 1000 secAlcatel T3107 BSS 14 sec 0 to 25.5 secHuawei T3107 Cell Timer 10 sec 0.5 to 60 sec

T200 Configurational Motorola lapd_t200_timer BTS 2.5 sec 1.4 to 5 secAlcatel T200 BSS 0.3 sec 0.3 to 1 secHuawei T200 (FACCH/F/H) Cell Timer 0.05 sec 1 to 0.255 sec

T9101 Call Clearing Motorola ‐ ‐ ‐ ‐Alcatel T9101 Network 10 sec 0 to 6553.5 secHuawei SCCP_TREL(s) BSC Timer 15 sec 10 to 20 sec

T9104 Call Clearing

Motorola ‐ ‐ ‐ ‐Alcatel T9104 BSS 2 sec 0 to 25.5 sec

Huawei TCLEARREQ(BSC) BSC Timer 5 sec 1 to 150 sec

TNT3(MSC) MSC Timer 6 sec 1 to 120 sec

T9108 Call Clearing Motorola ‐ ‐ ‐ ‐Alcatel T9108 Network 3 sec 0 to 6553.5 secHuawei ‐ ‐ ‐ ‐

T3110 Call Clearing Motorola MS Timer MS Timer ‐ ‐Alcatel MS Timer MS Timer ‐ ‐Huawei T3110 MS Timer 10 sec 0.5 to 60 sec


9

6.0 GSM TIMERS

The description of GSM Timers in isolation can often lead to confusion for the engineer. To ensure uniformity and ease of understanding, a format has been used to describe in detail each timer. The format is as given below.

Timer Name

This field will include the name of the Timer, as used in the international GSM standards.

Category

This field will indicate the placement of the timers in the GSM network. For Example either a timer is used in Call Setup procedures or it is used to administer a Handover.

Start Event

This field will include the event which triggers the timer.

Stop Event

This field will include the event upon which, the timer stops.

Expiry Event

This is the event which takes place, once the timer has expired.

Optional field include the values used by the vendors, ranges and default values.


10

6.1 CALL PROCESSING

This section deals with timers that essentially make up the call request and call setup procedure. A skim through the call flow shown below will help give the reader an idea of the positioning of the timers and their importance.

Details for each of the mentioned timers will follow along with

suitable information on them.


11

Call Processing (Contd...)


12

6.1.1 T3120 Category This timer is included in the Call Request procedure which starts with the RACH request.

Start Event This timer starts when the RACH request is sent to the network.

Stop Event The timer stops once the RACH acknowledgment is received.

Expiry Event Once the timer expires, the RACH request is re‐Transmitted on the air interface. The default value for this timer is 10 seconds. This is a MS based Timer and hence vendor implementation data is not applicable.


13

6.1.2 T3126 Category This timer is included in the Call Request procedure which starts with the RACH request.

Start Event This timer starts when the maximum amount of Channel requests have been sent by the MS.

Stop Event The timer stops when immediate assignment message is received from the BSS.

Expiry Event Once the timer expires, the procedure for immediate assignment is aborted. The value of this timer depends on the setting of RACH re‐transmission. This is a MS based Timer and hence vendor implementation data is unavailable.


14

6.1.3 T3101 Category This timer is included in the Call Setup procedure which starts with the immediate assignment procedure.

Start Event This timer starts when the immediate assignment message is sent to the MS by the BSS entity.

Stop Event The timer stops when the Establish indication message is sent by the MS to the BSS entity.

Expiry Event Once the timer expires, the procedure for call setup is aborted. The vendor based values for this timer are given below for reference.

Motorola Alcatel Huawei

T3101 2 sec 3 sec 3 sec


15


Start Event This timer starts when the CM service request is sent by the MS to the BSS entity

Stop Event The timer stops when the MS receives the message of CM Service request acknowledged. It is also stopped in case a CM service reject is received.

Expiry Event Once the timer expires, the release indication is provided to the BSS entity. The default value for this timer is 15 seconds This is a MS based Timer and hence vendor implementation data is unavailable.


16


Start Event This timer starts when the UA frame for the SDCCH connection is received by the MS.

Stop Event The timer is stopped when the CM service request is sent by the MS.

Expiry Event In case of an expiry event of this timer, the Call setup procedure is aborted. The default value for this timer is 20 seconds This is a MS based Timer and hence vendor implementation data is unavailable.


17

6.1.6 T310

Category This timer is included in the Call Setup procedure which starts with the immediate assignment procedure.

Start Event This Timer starts when the MS receives Call proceeding message.

Stop Event The timer stops once the Altering procedure begins and the call is established.

Expiry Event In case the timer expires and the altering procedure has not begun, the call setup procedure is aborted and No user Responding message is sent. The default value for this timer is 20 seconds This is a MS based Timer and hence vendor implementation data is unavailable.


18


Start Event This timer starts when an assignment resource request is queued by the BSS entity.

Stop Event The timer is stopped when the resource request is allocated a resource by the BSS entity.

Expiry Event Once the timer expires, the resource request is rejected and the call setup procedure is aborted. The vendor based values for this timer are given below for reference.

Note: If the value of T11 timer is kept more than the value of assign_successful timer [Motorola], this could lead to potential masking of Call Setup Blocking. CSSR




19


Start Event This timer starts when assignment request is sent to the MS by the BSS entity.

Stop Event The timer is stopped when the assignment complete message is sent by the MS to the BSS entity.

Expiry Event Once the timer expires, the assignment request is released and the call setup procedure is aborted. The vendor based values for this timer are given below for reference



Note: If the value of T10 timer is kept more than the value of assign_successful timer [Motorola], this could lead to potential masking of RF_Losses_SD & Intra_cell_HO_Losses.


20


Start Event This timer starts when the call connect message is sent to the call originating mobile.

Stop Event The timer stops when connect acknowledge message is received by the network entity from the MS.

Expiry Event In case of an expiry even of this timer, the call setup procedure is aborted and the call is released.


21


Start Event This timer starts when the assignment command is sent by the BSS entity to the MS.

Stop Event The timer is stopped when the Assignment complete message is received by BSS entity.

Expiry Event In case of an expiry event of this timer, an assignment failure command is sent and the channels are released. The vendor based values for this timer are given below for reference


T3107 11 sec 14 sec 10 sec


22


Start Event This timer starts when a blocking message is sent by the BSS entity to the MSC entity in case of non‐usable A interface timeslot.

Stop Event The timer is stopped when a Blocking acknowledgment message is received by the BSS entity.

Expiry Event On first expiry of the timer, the BSS entity retransmits the Blocking message. In case of a second expiry, the channel is set to non‐usable without MSC acknowledgment. The vendor based values for this timer are given below for reference




23

6.2 CALL CLEARING

Once a call is ended, the resources that were dedicated to it now need to be torn down so that they may be reused by other users. This process is called call clearing. This section describes the timers used in call clearing

6.2.1 T13 Category This timer is used in the Reset Procedure initiated by the MSC.

Start Event The timer starts when a Reset message is sent by the MSC to the BSS entity.

Stop Event The timer stops on when the MSC receives Reset Acknowledgement by the BSS entity.

Expiry Event In case of expiry event, the Reset acknowledgment is sent by the BSS to the MSC. The vendor based values for this timer are given below for reference




24

6.2.2 T3111 Category This timer is included in the Call release procedure which includes releasing of TCH channels

Start Event This timer starts with the reception of Release indication message from the BSS entity.

Stop Event The timer stops when the BSS entity sends the message for RF channel release to the respective BTS.

Expiry Event The expiry of this timer causes the forced channel release procedure to start and the channel is released from all ends of the network. The vendor based values for this timer are given below for reference


T3111 1.5 sec 0.5 1.5


25


Start Event This timer starts when the channel release message is sent by the BSS entity to the subsequent BTS.

Stop Event The timer is stopped when the release indication message is received by the BSS entity.

Expiry Event In case of an expiry event of this timer, the channels are released and call procedure is aborted. The vendor based values for this timer are given below for reference

Motorola Alcatel Huawei T3109 15 sec 12 sec 15 sec


26


Start Event This timer starts when the MS receives the Channel release message from the BSS entity.

Stop Event The timer stops once the MS receives a layer ‐2‐message from the BSS entity for channel release.

Expiry Event In case the timer expires, the normal channel release continues till the call is released. The default value for this timer is 10 seconds This is a MS based Timer and hence vendor implementation data is unavailable.


27

6.3 HANDOVER

This section deals with timers that essentially make up the handover procedure. Like call processing, a ladder diagram for handover is also given below for the ease of the reader.

Details for each of the mentioned timers will follow along with

suitable information on them.


28

6.3.1 T3103 Category This timer is used in the Handover Procedure.

Start Event The timer starts when the initiate Handover command is sent to the BTS by the BSC.

Stop Event The Timer is stopped when handover complete message is received by the BSS entity.

Expiry Event In case the timer expires, the handover procedure is aborted and the Handover attempt is termed as unsuccessful. The vendor based values for this timer are given below for reference


T3103 30 sec 16.5 sec 30 sec


29

6.3.2 T8 Category This timer is used in the Handover Procedure.

Start Event The timer starts when the Handover command is sent to the MS via the BSS entity.

Stop Event The Timer is stopped when handover complete message is received by the BSS entity.



T8 28 sec 14 sec 28 sec Note: If the value of T8 timer is set greater than the value of T3103, this could lead to potential masking of Out_Intra_BSS_HO_LostMS in Intra BSS HOs & Out_Inter_BSS_HO_Return, Out_Inter_BSS_Equip_Fail in Inter BSS HOs.


30

6.3.3 T7

Category This timer is used in the Handover Procedure.

Start Event The timer starts when a Handover Request message is sent to the MSC for an external BSC handover.

Stop Event The Timer is stopped when handover response message is received by the BSS entity.





31

6.3.4 TQHO Category This timer defines the maximum Queuing time for a Handover request.

Start Event The timer starts when the BSS places a Handover request in the resource queue for allocation.

Stop Event The timer is stopped when the Handover request is allocated the required resource by the BSS entity.

Expiry Event In case of an expiry event of this timer, the handover request is removed from the queue and the handover procedure is aborted. The vendor based values for this timer are given below for reference


TQHO 30 sec 5 sec 8 sec


32

6.3.5 T3121 Category This timer IS related with inter BSC and 2G/3G handovers.

Start Event The timer is started when a request is sent for an inter‐BSC or 2G/3G handover.

Stop Event The timer is stopped when a Handover complete message is received by the BSS entity.

Expiry Event In case of an expiry event of this timer, Clear request is sent and the handover procedure is aborted. The vendor based values for this timer are given below for reference


TQHO N‐A 14 sec 10 sec


33

6.4 GPRS TIMERS

6.4.1 T3182 Category This is an MS Based Timer and it is concerned with the RLC Window and stalling of TBF.

Start Event If the RLC transmit window is filled with transmitted blocks and any of them is unacknowledged, then the TBF window stalls and no more blocks can be set. At this time, T3182 is started.

Stop Event The timer stops once the acknowledgment for all the transmitted blocks has been received.

Expiry Event If the timer expires, then another timer N3102 is decremented. The Radio resources are released and the Mobile station tires to reestablish the TBF with the same cell through packet channel request.


34

6.4.2 T3164 Category This is an MS based timer which is concerned the access procedures during GPRS connections.

Start Event MS access the network for a GPRS connection through the Packet data request. The BTS send the packet uplink assignment message through the USF access. The timer will start on reception of this assignment message.

Stop Event The timer will stop once the USF uplink access has also been granted on the downlink.

Expiry Event If the timer expires, and the access has not been granted on the downlink, then the radio resources will be released and the Mobile station will repeat the whole procedure from the packet data request message.


35

6.4.3 T3198 Category This is an MS based timer which is concerned the acknowledgement of transmitted RLC Blocks

Start Event When a RLC block is transmitted by the Mobile station, Timer T3198 is started.

Stop Event The timer is stopped when the acknowledgment of the transmitted RLC block is received by the Mobile station.

Expiry Event If the timer expires with no acknowledgment for the transmitted blocks, the RLC blocks is tagged as NACK in the MS.


36

6.4.4 T3180 Category This timer is related with the dynamic allocation of Uplink TBF in the GPRS connection.

Start Event This timer is started during the dynamic allocation of the Uplink TBF. When the last block is sent as permitted by the USF granularity, the Timer 3180 is started with this transmission.

Stop Event When the USF is received in the downlink by the MS, this timer is stopped.

Expiry Event In case the timer expires, the MS abandons the TBF and the access procedure is repeated with the same cell.


37

6.4.5 T3190 Category This timer is related with the downlink assignment of Packet Data.

Start Event The timer is started when the Mobile station receives the downlink packet data assignment from the BSS entity.

Stop Event The timer is stopped when the Mobile station receives the downlink block containing the allocated TFI.

Expiry Event In case the timer expires, the mobile station releases the radio resources and aborts the TBF connection. In addition to this, the Mobile station starts monitoring the Common Control Packet channel.


38

6.4.6 T3192 Category This timer is concerned with the release of Packet Data Channel

Start Event The timer is started when the last block of downlink TBF is received.

Stop Event If a message for forced release of Packet Data channel is received, the timer is stopped.

Expiry Event When the timer expires, the radio resources are released and the packet data session comes to an end. It is to be noted that the value of this timer is smaller than T3193, in order to make it sure that the TFI of this MS is not allocated to any other MS in the mean time.


39

6.4.7 T3200 Category This Timer is related with the partitioned transmission of the RLC Blocks.

Start Event In the partitioned transmission of RLC blocks, the RLC frames are dived into segments with each segment having its own RTI (Radio Transaction Indicator). If the one of the segment is not received with its subsequent RTI, timer T3200 is started.

Stop Event The timer is stopped when the correct segment with the following RTI is received.

Expiry Event In case the time expires and the correct RTI has not been received, then the whole control block is rejected as a one or more segments are missing.


40

6.4.8 T3162 Category This timer is concerned with the queuing procedure employed during the packet data access.

Start Event The timer is started when the MS receives the Packet Queue Notification from the BSS entity. This message is in response to the Packet access message.

Stop Event The timer is stopped in case of a packet assignment message or packet accesses reject method.

Expiry Event If the timer expires without any assignment or reject message, the access procedure is aborted and the mobile monitors the Packet data common control channel.


41

6.4.9 T3168 Category This timer is concerned with acquisition of TBF resources during a Packet Data session.

Start Event This timer starts when a packet data request is sent by the Mobile station for more data resources during a TBF session.

Stop Event The Timer is stopped when the assignment message is received for the new uplink resource of TBF.

Expiry Event In case the timer expires, the request of Packet Data resources is resent by the Mobile Station.


42

6.4.10 T3170 Category This timer determines the time span for which the Mobile station will wait after sending the allowed number of Packet Data requests.

Start Event The timer starts when the last of the allowed Packet Data Request is sent by the Mobile station to the BSS entity.

Stop Event The timer is stopped when the Mobile station receives the uplink resources assignment message from the BSS entity.

Expiry Event In case the timer expires, the access procedure is aborted and the upper layers are informed as well.


43

6.4.11 T3172 Category This Timer is concerned with the wait time used for re‐transmitting the access request for Packet Data.

Start Event The timer begins with the Packet Assignment Reject method and this message also contains the amount of time, the timer has to remain active.

Stop Event The timer is stopped when the Packet Assignment message is received in response to the access request.

Expiry Event In case the timer expires, a request of Packet Data resources is resent by the Mobile Station.


44

6.4.12 T3176 Category This timer is concerned with the signaling for cell change failure during packet data session.

Start Event The timer is started when the first message for cell change failure is sent to the BSS entity.

Stop Event The timer is stopped if a successful cell change occurs and the confirmation message is sent to the Mobile station. .

Expiry Event In case the timer expires, the signaling for the failed cell changes is stopped and the Mobile station returns to normal operation.


45

6.4.13 T3188 Category This timer is used for the fixed allocation of uplink TBF.

Start Event The timer is started when the Mobile station sends a request to BSS entity regarding access for the fixed uplink TBF. .

Stop Event The timer is stopped once the Mobile station receives the assignment message for the uplink resource.

Expiry Event In case the timer expires, the request for the resources is re‐sent.


46

6.4.14 T3322 Category This timer is involved in the Detach process in the Packet Data connection.

Start Event The timer is started when the detach request is sent by the Mobile station to the BSS entity.

Stop Event The timer is stopped when the Mobile station receives the Detach accept message from the BSS entity.

Expiry Event In case the timer expires, the detach request is resent by the Mobile station.


47

6.4.15 T3380 Category This timer is used in the PDP Context activation procedure.

Start Event The timer is started when the Mobile station sends the request for PDP context activation.

Stop Event The timer is stopped when the BTS entity sends the confirmation message for the attach procedure.

Expiry Event In case the timer expires, the request for PDP context is resent by the Mobile station.


48

6.4.16 T3385 Category This timer is used in the PDP Context activation procedure.

Start Event The timer is started when the network sends the request for start of data session to the SGSN.

Stop Event The timer is stopped when the SGSN entity sends the confirmation message for the start of data connection.

Expiry Event In case the timer expires, the request for data session is resent by the network.


49

6.4.17 T3386 Category This timer is used in the PDP Context modification procedure.

Start Event The timer is started when the network sends the request for modification of PDP context to the MS.

Stop Event The timer is stopped when the network receives the response of the modification message.

Expiry Event In case the timer expires, the request for modification for PDP Context is resent by the network.


50

6.4.18 T3390 Category This timer is used in the PDP Context deactivation procedure.

Start Event The timer is started when the MS sends the request for deactivation of PDP context to the network.

Stop Event The timer is stopped when the MS receives the Deactivation accept message from the network.

Expiry Event In case the timer expires, the request for deactivation for PDP Context is resent by the MS.


51

6.4.19 T3395 Category This timer is used in the PDP Context deactivation procedure.

Start Event The timer is started when the GPRS Sub network sends the request for deactivation of PDP context to the network.

Stop Event The timer is stopped when the GPRS Sub network receives the Deactivation accept message from the network.

Expiry Event In case the timer expires, the request for deactivation for PDP Context is resent by the GPRS sub network.


52

6.4.20 T3158 Category This timer relates to Period between measurement reports. The Measurement reports may be made in packet idle mode or packet transfer mode, the timer being set by NC_REPORTING_PERIOD_I (packet idle) or NC_REPORTING_PERIOD_T (transfer).

Start Event Sending of previous measurement report.

Stop Event None

Expiry Event Next measurement report sent.


53

6.4.21 T3166 Category This timer is the One‐phase access contention timer

Start Event When the first RLC/MAC block is transmitted

Stop Event when a packet uplink ack/nack returning TLLI is received

Expiry Event On expiry, the mobile station must stop transmitting and disconnect from the radio resources. A contention failure or other failure has occurred.


54

6.4.22 T3169 Category Response to USF tolerance timer

Start Event N3101 reaches its allowed maximum count, N3101_MAX.

Stop Event None

Expiry Event On expiring, the USF is released (which means it can be reassigned to another mobile station).


55

6.4.23 T3174 Category Handover (cell change order) failure timer

Start Event When the GPRS sub‐network is in command of cell selection, it may tell the mobile station to change to another cell with packet cell change order. This command starts T3174 and the mobile station changes physical channels, sending a packet channel request to the new cell.

Stop Event When a packet uplink assignment is received from the new cell.

Expiry Event Handover or cell change has failed and T3176 starts.


56

6.4.24 T3182 Category Window stall timeout for dynamic allocation

Start Event When the RLC transmit window k is filled with transmitted RLC/MAC blocks, any one of which is unacknowledged, then the TBF window ‘stalls’ and no more blocks can be sent. T3182 is then started.

Stop Event Packet uplink acknowledge reception from the GPRS sub‐network, allowing the window to be advanced and transmissions to be resumed.

Expiry Event N3102 is decremented (by the amount PAN_DEC sent in packet system information), disconnects from the radio resources and attempts to re‐establish the TBF in the same cell with packet channel request.


57

6.4.25 T3178 Category Packet idle mode extended measurement report period The value of this timer is contained in the idle mode extended measurement reports command contained in PSI5 or PCCCH. The mobile station will report measurements with this periodicity.

Start Event N/A

Stop Event N/A

Expiry Event N/A


58

6.4.26 T3184 Category Fixed allocation packet uplink ack/nack tolerance timer

Start Event Receipt of packet uplink ack/nack.

Stop Event Receipt of the next packet uplink ack/nack.

Expiry Event Mobile station releases the TBF and radio resources.


59

6.4.27 T3191 Category Response to final data block tolerance timer

Start Event Transmission of the final RLC data block in a downlink TBF

Stop Event Receipt of packet downlink ack/nack or packet control ack

Expiry Event TFI and other resources are released.


60

6.4.28 T3193 Category Uplink RLC release timer. This is the network counterpart of T3192. This timer must be longer than T3192.

Start Event (See T3192)

Stop Event (See T3192)

Expiry Event (See T3192)


61

6.4.29 T3195

Category Linked to TBF and TFI

Start Event T3195 starts when N3105 reaches to maximum value

Stop Event N/A

Expiry Event The network releases TFI resource


62

6.4.30 T3310 Category Attach request timer

Start Event When attach request is sent.

Stop Event Attach accept is received.

Expiry Event Attach request message is resent.


63

6.4.31 T3312 Category Periodic routing area update Determines when the mobile station GMM function will perform an automatic RA update (irrespective of whether the RA has changed).

Start Event N/A

Stop Event N/A

Expiry Event N/A


64

6.4.32 T3314 Category Ready timer This timer specifies the maximum time that the mobile station is allowed to remain in GMM ready condition without an LLC PDU transfer with the GPRS sub‐network.

Start Event Sending of an LLC PDU to the GPRS sub‐network

Stop Event Sending of an LLC PDU to the GPRS sub‐network

Expiry Event Mobile station is forced to GMM standby.


65

6.4.33 T3321 Category GPRS sub‐network detach timer

Start Event Sending of detach request

Stop Event Reception of detach accept.

Expiry Event Mobile station resends the detach request


66

6.5 MISCELLANEOUS

6.5.1 T3128 Category This timer is related with the access procedure of Uplink investigation process.

Start Event The timer starts when the uplink busy message is sent to the MS upon receiving access request for uplink investigation.

Stop Event The timer is stopped when Uplink free message is sent to the MS.

Expiry Event In case of an expiry event of this timer, the Uplink investigation process is aborted. The default value for this timer is 1 second. This is a MS based Timer and hence vendor implementation data is unavailable.


67

6.5.2 T3210 Category This timer is related with the access procedure of Location Update.

Start Event The timer starts when the MS sends the location update request to the BSS entity.

Stop Event The timer is stopped when the Location_update_accept or reject message is received by the MS entity. This timer is also stopped in case of a lower layer failure.

Expiry Event In case of an expiry event of this timer, the BSS timer T3211 is started. The default value for this timer is 20 seconds. This is a MS based Timer and hence vendor implementation data is unavailable.


68

6.5.3 T3211 Category This timer is related with the access procedure of location update procedure.

Start Event This timer starts when location_update_reject is received with the cause value indicating network failure.

Stop Event The Timer is stopped when the location update takes place or cell for the particular MS is changed.

Expiry Event In case this timer expires, the request for location update is again sent to the BSS entity. The default value for this timer is 15 seconds.


69

6.5.4 T3212 Category This timer is related with the termination of MM signaling.

Start Event This timer starts with the termination of MM signaling.

Stop Event The timer stops when the message for the initiation of MM signaling is sent to the MS by the BSS entity.

Expiry Event In case the timer expires, a periodic request is sent for the LU update. The default value for this timer is 60 seconds. This is a MS based Timer and hence vendor implementation data is unavailable.


70

6.5.5 T3220 Category This timer is related with the IMSI detach procedure.

Start Event The timer starts when the MS sends an IMSI detach message to the BTS entity.

Stop Event The timer is stopped when the MS is removed from the MM sub‐layer.

Expiry Event In case the timer expires, the MS enters the Null period and request is sent for the status to be updated. The default value for this timer is 5 seconds. This is a MS based Timer and hence vendor implementation data is unavailable.


71

7.0 VENDOR BASED COMPILED LISTS

7.1 MOTOROLA TIMERS

Timers T_hand_rqd T3230 T_HAND_RQD T3240 T_SDCCH_HO_ALLOWED T4 t_stat_info T4 (ITU) T1 T4_TIMER T1 (ITU) T4_TIMER (Lb interface) T1_TIMER T4_TIMER_ID (Lb interface) T1_TIMER (Lb interface) T5 T1_TIMER_ID (Lb interface) T5 (ITU) T12 T5_TIMER T12_TIMER T5_TIMER (Lb interface) T12_TIMER (Lb interface) T5_TIMER_ID (Lb interface) T13 T6 T13_TIMER T6 (ITU) T13_TIMER (Lb interface) T6_TIMER_ID (Lb interface) T14 T7 T14_TIMER T7 (ITU) T14_TIMER (Lb interface) T7_EXP‐MSG_TYPE T17 T7_TIMER_ID (Lb interface) T17_TIMER TCH assignment‐successful T17_TIMER (Lb interface) TCH assignment‐unsuccessful T2 TCONN_EST T2 (ITU) Tqho T2_TIMER TREL

T2_TIMER (Lb interface) bssgp_t1_timer T2_TIMER_ID (Lb interface) bssgp_t2_timer T22 bssgp_t5_timer T22_TIMER bssmap_t1 T22_TIMER (Lb interface) bssmap_t10 T23 bssmap_t11 T23_TIMER bssmap_t13 T23_TIMER (Lb interface) bssmap_t19 T3 bssmap_t20 T3 (ITU) bssmap_t4 T3_TIMER_ID (Lb interface) bssmap_t7 T3101 bssmap_t8 T3103 bssmap_tqho T3105 bounce_protect_cong_tmr T3109 bounce_protect_qual_tmr T3111 bts_p_con_timer T3122 CLM_T1 T3210 CLM_T13 T3212 CLM_T19 T3220 CLM_T20


72

Timer

CLM_T4 rr_t3111 hop_count_timer rr_t3111_sd lb_int_ss7_l2_t1 rr_t3111_tch lb_int_ss7_l2_t2 rr_t3212 lb_int_ss7_l2_t3 RRSM_AUDIT_TIMER lb_int_ss7_l2_t4 RRSM_T10 lb_int_ss7_l2_t5 RRSM_T11 lb_int_ss7_l2_t6 RRSM_T8 lb_int_ss7_l2_t7 ss7_l2_t1 lb_int_ss7_l3_t1 ss7_l2_t2 lb_int_ss7_l3_t12 ss7_l2_t3 lb_int_ss7_l3_t13 ss7_l2_t4 lb_int_ss7_l3_t14 ss7_l2_t5 lb_int_ss7_l3_t17 ss7_l2_t6 lb_int_ss7_l3_t2 ss7_l2_t7 lb_int_ss7_l3_t22 ss7_l3_t1 lb_int_ss7_l3_t23 ss7_l3_t12 lb_int_ss7_l3_t4 ss7_l3_t13 lb_int_ss7_l3_t5 ss7_l3_t14 lb_int_ss7_slt_t1 ss7_l3_t17 not aligned timer ss7_l3_t2 ns_alive_timer ss7_l3_t22 ns_block_timer ss7_l3_t23 ns_reset_period ss7_l3_t4 ns_reset_timer ss7_l3_t5 ns_test_timer wait for clear command from the BSS‐based SMLC timer penalty_time wait for SCCP release complete timer PENALTY_TIME wait for SCCP released message from SMLC timer PERF_LOC_TIMER wait_for_reselection rr_ny1_rep wait_indication_parameters rr_t3101 waiting for changeback acknowledgement (rst attempt) timer rr_t3103 waiting for changeback acknowledgement (second attempt) timer rr_t3105 waiting for changeover acknowledgement timer rr_t3109 waiting for force uninhibit timer to 3‐62, 3‐210, 3‐212, 3‐214, 3‐10 waiting for inhibition acknowledgement timer rr_t3110 add_access_class rf_chan_rel_ack sccp_tconn_est retry_cand_period radiochanrel exrtrycandprd sccp_released validcandperiod assign_successful radio_link_timeout bsc_audit link_fail bsc_audit_response linkabouttofail clear_command channel_act clear_cmd_ext_ho channel_teardown circuit_reset_ack cipher_comp_ms ciphering_successful ho_complete ext_ho_allocation mode_modify ho_allocation modeRRModifyAck ho_request register_exp ho_successful


73

7.2 ALCATEL TIMERS

Timer Entity Timer Entity T(conn est) BSC T_GSL_ACK (BSC) BSC T(iar) BSC T_HO_REQD_LOST BSC T(sst) BSC T_INHIBIT_CPT BSC T_ALLOC_BTS BSC T_LB_OV BSC T_AVG_T (MFS) MFS T_LCS_RESTART (BSC) BSC T_BA_CHANGE MFS T_Location BSC T_BTS_RLS_CNF BSC T_MAX_FOR_MS_SYNCHRO MFS T_CBC_READY BSC T_MAX_STREAMING_BUFFERING MFS T(ias) BSC T_MS_CELL_REJ BSC T_ACK_WAIT MFS T_NC_PING_PONG MFS T_AUTOCLEANING_MEAS_REP BSC T_NC2_LOAD_RANKING MFS T_AVG_W (BSC) BSC T_One_Block MFS T_BIND_CNF BSC T_COUNT_I BSC T_BURST BSC T_DELAY_GSL BSC T_CFI_TR BTS T_DELAYED_DL_TBF_POL_INITIAL MFS T(rel) BSC T_dl_assign_ccch MFS T_ACK_WAIT_DRX_PCCCH MFS T_DSP_LOAD_REPORT MFS T_AVG_T (BSC) BSC T_EXTENDED_UL_TBF_POL MFS T_AVG_W(MFS) MFS T_flow_ctrl_cell MFS T_BTS_EST_CNF BSC T_GCH_INACTIVITY_LAST MFS T_CANDIDATE_TBF_REALLOC MFS T_GSL_ACK (MFS) MFS T_CHANGE_RLC_MODE MFS T_i BSC T_CONFIG_TBF MFS T_INITIAL_PDCH MFS T_DELAY BSC T_LCS_Delay_Tolerant MFS T_DELAY_PAGING_EXT MFS T_LCS_RESTART (MFS) MFS T_Delayed_DL_TBF_Pol_UL MFS T_Location_Longer BSC T_DL_EGPRS_MeasReport MFS T_MAX_FOR_TBF_SCHEDULING MFS T_DTM_ASSIGN MFS T_MIN_POLL MFS T_FAST_DL_margin MFS T_MS_CONTEXT_FLUSH_PERSISTENCE MFS T_flow_ctrl_ms MFS T_NC_REJ_CELL MFS T_GPRS_Resume BSC T_NETWORK_RESPONSE_TIME MFS T_HCP BSC T_OVL_MSC BSC T_IA BSC T_PAG_CS (BSC) BSC T_INTRF_L3 BSC T_PAG_PS (MFS) MFS T_LCS_Low_Delay MFS T_PDA BSC T_Loc_abort BSC T_PUA BSC T_MAX_EXTENDED_UL MFS T_RECOVERY BSC T_MAX_RETRANS_DL MFS T_REPETITION_UPLINK_FREE BSC T_MPDCH_EST_PROC (BSC) BSC T_RESET_COUNTER BTS T_MS_Context_Lifetime MFS T_RMS_BSC_RESTART BSC T_NC_RXQUAL_VALID MFS T_RRLP_Low_Delay MFS T_NOTIF_RESPONSE_DELAY BSC T_SHARED_DTM_INFO (BSC) BSC T_CONNECT BSC T_SMSCB_RESP BSC T_delay_gch MFS T_SYNC BTS T_DELAYED_DL_TBF_POL MFS T_ta BTS T_DELAYED_FINAL_PUAN MFS T_TFO BSC T_DL_GPRS_MeasReport MFS T_ul_assign_pccch MFS T_DYN_SDCCH_HOLD BSC T_WAIT_CS_PROC MFS


74

Timer Entity Timer Entity

T_FILTER BSC T_WAIT_PMR_MARGIN MFS T_GCH_INACTIVITY MFS T1_0858 BSC T11 BSC T3168 (BSC) BSC T_PAG_CS (MFS) MFS T3180 MFS T_PAGING_EXT MFS T3191 MFS T_PSCD_SCHEDULE_ACK MFS T3208n MFS T_qho BSC T391 MFS T_release TC T7 BSC T_REROUTING_REQUEST_GUARD MFS T17 BSC T_RMS_BSC BSC T19 BSC T_RMS_BTS BSC T200 (BSC) BSC T_SAGI_GUARD MFS T200_GSL (BSC) BSC T_SHARED_DTM_INFO (MFS) MFS T200_S3 BTS T_STOP_FR_EMISSION MFS T200_TF BTS T_SYNCd BTS T203 (BSC) BSC T_TBF_ACTIV MFS T203_GSL (MFS) MFS T_ul_access_max MFS T3105_D BSC T_UL_CONGESTION MFS T3105_F_HR BSC T_WAIT_DTM MFS T3106_D_STOP BSC T_WAIT_UPLINK_ACCESS BSC T3107 BSC T1_long BSC T3115 BSC T11_FORCED BSC T3148n BSC T_PAG_PS (BSC) BSC T3168 (MFS) MFS T_PAGING_REORG MFS T3182n MFS T_PSI_PACCH MFS T3192 (BSC) BSC T_RCR_ACK BSC T3212(BSC) BSC T_REPETITION_CHANNEL_RELEASE BSC T4 BSC T_RESEL MFS T8 BSC T_RMS_BSC_RECONF BSC T18 BSC T_RRLP_Delay_Tolerant MFS T2_0858 BSC T_SDCCH_PC BSC T200_D BTS T_SMSCB_READY BTS T200_GSL (MFS) MFS T_SUP BTS T200_SD BTS T_SYNCu BTS T200_TH BTS T_TBF_BCK_REL MFS T203 (BTS) BTS T_ul_assign_ccch MFS T3101 BSC T_USF_Scheduling_AGCH MFS T3105_D_STOP BSC T_WAIT_FLUSH MFS T3105_F_STOP BSC T_WAIT_UPLINK_REQUEST_ACK BSC T3106_F BSC T1_short BSC T3109 BSC T13 BSC T3121 BSC T14 BSC T3166n MFS T18_Overload BSC T3169 MFS T20 BSC T3190n MFS T200_D3 BTS T3192 (MFS) MFS T200_OMU BTS T3212 (MFS) MFS T200_ST BTS T5_RA_CAP_UPDATE MFS T200_TRE BTS T9101 BSC T203_GSL (BSC) BSC T9103 BSC


75

Timer Entity Timer Entity T3103 BSC T9108 BSC T3105_F_FR BSC T9113 BSC T3106_D BSC T9104 BSC T3106_F_STOP BSC T9110 BSC T3111 BSC T9105 BSC T3122 BSC T9112 BSC


76

7.3 HUAWEI TIMERS

Timers T200 SDCCH SAPI3(5ms) PBGT Valid Time(s) T200 SACCH SDCCH(10ms) PBGT Watch Time(s) T200 SACCH TCH SAPI3(10ms) Layer HO Valid Time(s) T200 SACCH TCH SAPI0(10ms) Layer HO Watch Time(s) T200 FACCH/H(5ms) Edge HO AdjCell Valid Time(s) T200 FACCH/F(5ms) Edge HO AdjCell Watch Time(s) T200 SDCCH(5ms) Edge HO Valid Time(s) AHR Radio Link Timeout(SACCH period (480ms)) Edge HO Watch Time(s) AFR Radio Link Timeout(SACCH period (480ms)) Update Period of CH Record(min) AHR SACCH Multi‐Frames(SACCH period (480ms)) TCH Minimum Recovery Time(s) AFR SACCH Multi‐Frames(SACCH period (480ms)) Release Delay of Downlink TBF(ms) SACCH Multi‐Frames(SACCH period (480ms)) Inactive Period of Extended Uplink TBF(ms) TDD 3G Better Cell HO Valid Time(s) Release Delay of Non‐extended Uplink TBF(ms) TDD 3G Better Cell HO Watch Time(s) Cell Reselect Interval(s) Quick Handover Punish Time(s) Cell Penalty Last Time(s) Quick Handover Last Time (0.5s) Cell Reselection Forbidden Time Quick Handover Static Time(0.5s) Non‐DRX Period Number of Satisfactory Measurements(s) GPRS Penalty Time Total Number of Measurements(s) Extension MR Period Inter UL And OL Subcells HO Penalty Time(s) Max. Duration of DRX(s) OL Subcell Load Diversity HO Period(s) T3192 Modified Step Length of UL Load HO Period(s) T3168 UL Subcell Load Hierarchical HO Period(s) Cell Reselection MR Period in Packet Transfer Mode 3G Better Cell HO Valid Time(s) Cell Reselection MR Period in Packet Idle Mode 3G Better Cell HO Watch Time(s) Timer for UL Data Forward(ms) Penalty Time after OtoU HO Fail(s) WaitforRelIndAMRHR Penalty Time after UtoO HO Fail(s) WaitforRelIndAMRFR Penalty Time of UtoO HO(s) T3103C(ms) Underlay HO Step Period(s) T3122(s) UO HO Valid Time(s) TREESTABLISH(ms) UO HO Watch Time(s) T3111(ms) Penalty on MS Fast Moving HO T3109(ms) CfgPenaltyTimer T8(ms) UmPenaltyTimer T3121(ms) RscPenaltyTimer T3107(ms) Penalty Time after AMR TCHF‐H HO Fail(s) T7(ms) Penalty Time after TA HO(s) T3103A(ms) Penalty Time after BQ HO(s) ImmAss A Interf Creation Timer(ms) Min Interval for Consecutive HOs T3101(ms) Min Interval for SDCCH HOs Aiding Delay Protect Time(min) Min Interval for TCH HOs CCCH Load Indication Period(s) TIGHT BCCH HO Valid Time(s) Radio Resource Report Period(s) TIGHT BCCH HO Watch Time(s) Frame Start Time Intracell F‐H HO Last Time(s) Interf.Calculation Period(SACCH period(480ms)) Intracell F‐H HO Stat Time(s) Speed Penalty Time

45847764 gsm timers document

Documents

vendor implementation

call setup

mobile station

stopevent

packet assignment

ms based timer

call request

mobile station