GSM Timers Document

MobilinkConfidentialProperty
TIMERS
RFOPTIMIZATION
ENGINEERINGACCESSNETWORK
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
informationobtainedherein.
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
personofrevisionsorchanges.

3
TABLEOFCONTENTS
1.0 Introduction 5
2.0 Whatdoesthemanualcover? 5
3.0 Whytheneedtostudytimers? 5
4.0 TimerCategorization 6
4.1 EntityBasedCategorization 6
4.2 ProcessFlowBasedCategorization 6
5.0 Breakdown 7
6.0 GSMTimers 9
6.1 CallSetup 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 CallClearing 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 CompiledList 71
7.1 MotorolaTimersList 71
7.2 AlcatelTimersList 73
7.3 HuaweiTimersList 76

5
1.0INTRODUCTION
Like any other wireless technology with a limited pool of resources,

GSMresourceallocationandterminationdependsprimarilyontimers.The
functionality and protocols may vary, but the presence of timer based
signaling and resource allocation is ubiquitous. Timer implementation is
presentineachdomainoftheGSMsystemfromMStoNSSend.
2.0WHATDOESTHISMANUALCOVER?
This document aims to describe all the major BSS timers involved in
theGSMarchitecture.Thetimersarecategorizedintodifferentsubgroups,
dependingupontheirparententityandtheprocessflowtheyareinvolved
in.Thedocumentproceedsfurtherbygivingadetailedexplanationofeach
timeralongwithitsimplementationinthePMCLnetwork.
3.0WHYTHENEEDTOSTUDYTIMERS?
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
customermightdotoaccessandutilizetheGSMnetwork.Therefore,fora
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
basestationstofacilitatecallhandovers.
Furthermore, the reason for a deep understanding of timers is also

reenforcedbythemultivendorimplementationpresentatalllevelsofthe
network. Such a scenario demands all database discrepancies to be
eliminatedtoensurecoherenceandintervendorcompatibility.

6
4.0TIMERCATEGORIZATION
4.1ENTITYBASEDCATEGORIZATION
As highlighted earlier there are different ways of categorizing timers. One

categorization can be done on the basis of entity which includes the
followingcategories:
4.2PROCESSFLOWBASEDCATEGORIZATION
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:
CallProcessing
CallSetup
Call
Release
Handovers
GPRS
Miscellaneous

7
5.0BREAKDOWN[PHASE1]
The task of documenting the GSM timers is not an easy paced

procedure. The project is divided into two phases. The first phase
comprisedoftheresearchforallthetimersinvolvedfromMStoBSSasper
the international GSM standards. In the second phase, vendor
implementationsofthesetimersweretakenintoconsideration.Acomplete
overviewofallthetimersinvolvedinPhase1isasunder:
Timer CallFlow Vendor Timer'sName Category

Default
Value
Range
T3120 CallSetup
Motorola MSTimer MSTimer
Alcatel MSTimer MSTimer
Huawei T3120 MSTimer
MinisRACH
T+2S;MAX5
MinisRACH
T+2S;MAX5
T3126 CallSetup
Huawei T3126 MSTimer
MinisRACH
T+2SMAX5
MinisRACH
T+2SMAX5
T3122 CallSetup
Motorola wait_indication_parameter BTS none 0to255sec
Alcatel T3122 MSTimer 0to255sec
Huawei T3122 CellTimer 10sec 0255sec
T3101 CallSetup
Motorola rr_t3101 BTS 5sec 0to1000sec
Alcatel T3101 BSClevel 3sec 0to25.5sec
Huawei T3101 CellTimer 3sec 0.5to60sec
T3230 CallSetup
Huawei T3230 MSTimer 15sec 15sec
T303 CallSetup
Huawei T303 MSCTimer 20sec
T310 CallSetup
Huawei T310 MSCTimer 20sec
T11 CallSetup
Motorola bssmap_t11 BTS 28sec 0to1000sec
Alcatel T11 BSS 6sec 0to19sec
Huawei T11 BSCTimer 8sec 1to30sec
T10 CallSetup
Alcatel bssMapT10 BSS 14sec
T313 CallSetup
Motorola MSCtimer
Alcatel T313 MS Timer
Huawei T313 MSCTimer 30sec 30sec
T8 Handover
Alcatel bssMapT8 BSS 14sec 0to25.5sec
T3103 Handover Motorola rr_t3103 BTS 30sec 0to1000sec

8
Alcatel T3103 BSS 16.5sec 0to25.5sec
T1 GPRS
Motorola bssmap_t1 BSC 30sec
0to1000000
msec
T13 CallClearing
Motorola bssmap_t13 BSC 40sec 0to1000sec
T7 Handover
Motorola bssmap_t7 BSC 30sec 0to1000sec
Alcatel bssMapT7 BSS 5sec 0to20sec
TQHO Handover
Motorola bssmap_tqho BSC 30sec 0to1000sec
Alcatel T_QHO BSS 3sec 0to20sec
Huawei TQHO BSCTimer 8sec 1to30sec
T3111 CallClearing
Motorola
rr_t3111_sd BTS 1.5sec 0to1000sec
rr_t3111_tch BTS 1.5sec 0to1000sec
Alcatel T3111 BSS 0.5sec 0to2sec
T3109 CallClearing
Motorola rr_t3109 BTS 14.4sec 0to1000sec
Alcatel T3109 BSS 12sec 0to35sec
Huawei T3109 CellTimer 27sec 135sec
T3121 Handover
Motorola MSCTimer
Alcatel T3121 BSS 14sec 0to25.5sec
Huawei T3121 CellTimer 10sec 0.5to60
T3107 CallSetup
Motorola RRSM_T10 BTS 28sec 0to1000sec
T200 Configurational
Motorola lapd_t200_timer BTS 2.5sec 1.4to5sec
Alcatel T200 BSS 0.3sec 0.3to1sec
Huawei T200(FACCH/F/H) CellTimer 0.05sec 1to0.255sec
T9101 CallClearing
Motorola
Alcatel T9101 Network 10sec 0to6553.5sec
Huawei SCCP_TREL(s) BSCTimer 15sec 10to20sec
T9104 CallClearing
Motorola
Huawei
TCLEARREQ(BSC) BSCTimer 5sec 1to150sec
TNT3(MSC) MSCTimer 6sec 1to120sec
T9108 CallClearing
Motorola
Alcatel T9108 Network 3sec 0to6553.5sec
Huawei
T3110 CallClearing
Huawei T3110 MSTimer 10sec 0.5to60sec

9
6.0GSMTIMERS

The description of GSM Timers in isolation can often lead to
confusion for the engineer. To ensure uniformity and ease of
understanding,aformathasbeenusedtodescribeindetaileachtimer.The
formatisasgivenbelow.
TimerName
This field will include the name of the Timer, as used in the
internationalGSMstandards.
Category
This field will indicate the placement of the timers in the GSM
network.ForExampleeitheratimerisusedinCallSetupprocedures
oritisusedtoadministeraHandover.
StartEvent
Thisfieldwillincludetheeventwhichtriggersthetimer.
StopEvent
Thisfieldwillincludetheeventuponwhich,thetimerstops.
ExpiryEvent
Thisistheeventwhichtakesplace,oncethetimerhasexpired.
Optional field include the values used by the vendors, ranges and
defaultvalues.


10
6.1CALLPROCESSING
This section deals with timers that essentially make up the call
requestandcallsetupprocedure.Askimthroughthecallflowshownbelow
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
suitableinformationonthem.

11
CallProcessing(Contd...)

12
6.1.1T3120
Category
This timer is included in the Call Request procedure which starts with the
RACHrequest.
StartEvent
ThistimerstartswhentheRACHrequestissenttothenetwork.
StopEvent
ThetimerstopsoncetheRACHacknowledgmentisreceived.
ExpiryEvent
Once the timer expires, the RACH request is reTransmitted on the air
interface.
Thedefaultvalueforthistimeris10seconds.
This is a MS based Timer and hence vendor implementation data is not

applicable.


13
6.1.2T3126
Category
This timer is included in the Call Request procedure which starts with the
RACHrequest.
StartEvent
This timer starts when the maximum amount of Channel requests have
beensentbytheMS.
StopEvent
Thetimerstopswhenimmediateassignmentmessageisreceivedfromthe
BSS.
ExpiryEvent
Once the timer expires, the procedure for immediate assignment is

aborted.
ThevalueofthistimerdependsonthesettingofRACHretransmission.
This is a MS based Timer and hence vendor implementation data is

unavailable.


14
6.1.3T3101
Category
This timer is included in the Call Setup procedure which starts with the
immediateassignmentprocedure.
StartEvent
This timer starts when the immediate assignment message is sent to the
MSbytheBSSentity.
StopEvent
ThetimerstopswhentheEstablishindicationmessageissentbytheMSto
theBSSentity.
ExpiryEvent
Oncethetimerexpires,theprocedureforcallsetupisaborted.
Thevendorbasedvaluesforthistimeraregivenbelowforreference.

Motorola Alcatel Huawei
T3101 2sec 3sec 3sec


15
6.1.4T3230
Category
StartEvent
ThistimerstartswhentheCMservicerequestissentbytheMStotheBSS
entity
StopEvent
The timer stops when the MS receives the message of CM Service request
acknowledged.ItisalsostoppedincaseaCMservicerejectisreceived.
ExpiryEvent
Oncethetimerexpires,thereleaseindicationisprovidedtotheBSSentity.

Thedefaultvalueforthistimeris15seconds

unavailable.


16
6.1.5T303
Category
StartEvent
This timer starts when the UA frame for the SDCCH connection is received
bytheMS.
StopEvent
ThetimerisstoppedwhentheCMservicerequestissentbytheMS.
ExpiryEvent
Incaseofanexpiryeventofthistimer,theCallsetupprocedureisaborted.


unavailable.


17
6.1.6T310
Category
StartEvent
ThisTimerstartswhentheMSreceivesCallproceedingmessage.
StopEvent
The timer stops once the Altering procedure begins and the call is
established.
ExpiryEvent
Incasethetimerexpiresandthealteringprocedurehasnotbegun,thecall
setupprocedureisabortedandNouserRespondingmessageissent.

unavailable.

18
6.1.7T11
Category
StartEvent
This timer starts when an assignment resource request is queued by the

BSSentity.
StopEvent
The timer is stopped when the resource request is allocated a resource by

theBSSentity.
ExpiryEvent
Oncethetimerexpires,theresourcerequestisrejectedandthecallsetup
procedureisaborted.
Thevendorbasedvaluesforthistimeraregivenbelowforreference.

Note:IfthevalueofT11timeriskeptmorethanthevalueofassign_successfultimer
[Motorola],thiscouldleadtopotentialmaskingofCallSetupBlocking.CSSR

T11 10sec 6sec 8sec

19
6.1.8T10
Category
StartEvent
This timer starts when assignment request is sent to the MS by the BSS
entity.
StopEvent
Thetimerisstoppedwhentheassignmentcompletemessageissentbythe
MStotheBSSentity.
ExpiryEvent
Once the timer expires, the assignment request is released and the call
setupprocedureisaborted.
Thevendorbasedvaluesforthistimeraregivenbelowforreference

Note:IfthevalueofT10timeriskeptmorethanthevalueofassign_successfultimer
[Motorola], this could lead to potential masking of RF_Losses_SD &
Intra_cell_HO_Losses.

20
6.1.9T313
Category
StartEvent
This timer starts when the call connect message is sent to the call
originatingmobile.
StopEvent
The timer stops when connect acknowledge message is received by the

networkentityfromtheMS.
ExpiryEvent
In case of an expiry even of this timer, the call setup procedure is aborted
andthecallisreleased.


21
6.1.10T3107
Category
StartEvent
ThistimerstartswhentheassignmentcommandissentbytheBSSentityto
theMS.
StopEvent
The timer is stopped when the Assignment complete message is received

byBSSentity.
ExpiryEvent
In case of an expiry event of this timer, an assignment failure command is

sentandthechannelsarereleased.



22
6.5.11T1
Category
StartEvent
This timer starts when a blocking message is sent by the BSS entity to the
MSCentityincaseofnonusableAinterfacetimeslot.
StopEvent
ThetimerisstoppedwhenaBlockingacknowledgmentmessageisreceived
bytheBSSentity.
ExpiryEvent
On first expiry of the timer, the BSS entity retransmits the Blocking
message. In case of a second expiry, the channel is set to nonusable
withoutMSCacknowledgment.



23
6.2CALLCLEARING
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.1T13
Category
ThistimerisusedintheResetProcedureinitiatedbytheMSC.
StartEvent
ThetimerstartswhenaResetmessageissentbytheMSCtotheBSSentity.
StopEvent
ThetimerstopsonwhentheMSCreceivesResetAcknowledgementbythe
BSSentity.
ExpiryEvent
Incaseofexpiryevent,theResetacknowledgmentissentbytheBSStothe
MSC.


24
6.2.2T3111
Category
ThistimerisincludedintheCallreleaseprocedurewhichincludesreleasing
ofTCHchannels
StartEvent
ThistimerstartswiththereceptionofReleaseindicationmessagefromthe
BSSentity.
StopEvent
The timer stops when the BSS entity sends the message for RF channel
releasetotherespectiveBTS.
ExpiryEvent
The expiry of this timer causes the forced channel release procedure to
startandthechannelisreleasedfromallendsofthenetwork.

T3111 1.5sec 0.5 1.5

25
6.2.3T3109
Category
ofTCHchannels
StartEvent
This timer starts when the channel release message is sent by the BSS
entitytothesubsequentBTS.
StopEvent
The timer is stopped when the release indication message is received by

theBSSentity.
ExpiryEvent
In case of an expiry event of this timer, the channels are released and call
procedureisaborted.


26
6.2.4T3110
Category
ofTCHchannels
StartEvent
This timer starts when the MS receives the Channel release message from
theBSSentity.
StopEvent
The timer stops once the MS receives a layer 2message from the BSS
entityforchannelrelease.
ExpiryEvent
Incasethetimerexpires,thenormalchannelreleasecontinuestillthecall
isreleased.

unavailable.


27
6.3HANDOVER

Thissectiondealswithtimersthatessentiallymakeupthehandover
procedure.Likecallprocessing,aladderdiagramforhandoverisalsogiven
belowfortheeaseofthereader.
Details for each of the mentioned timers will follow along with
suitableinformationonthem.


28
6.3.1T3103
Category
ThistimerisusedintheHandoverProcedure.
StartEvent
ThetimerstartswhentheinitiateHandovercommandissenttotheBTSby
theBSC.
StopEvent
TheTimerisstoppedwhenhandovercompletemessageisreceivedbythe
BSSentity.
ExpiryEvent
In case the timer expires, the handover procedure is aborted and the
Handoverattemptistermedasunsuccessful.

T3103 30sec 16.5sec 30sec

29
6.3.2T8
Category
StartEvent
ThetimerstartswhentheHandovercommandissenttotheMSviatheBSS
entity.
StopEvent
TheTimerisstoppedwhenhandovercompletemessageisreceivedbythe
BSSentity.
ExpiryEvent


Note:IfthevalueofT8timerissetgreaterthanthevalueofT3103,thiscouldleadto
potential masking of Out_Intra_BSS_HO_LostMS in Intra BSS HOs &
Out_Inter_BSS_HO_Return,Out_Inter_BSS_Equip_FailinInterBSSHOs.


30
6.3.3T7
Category
StartEvent
ThetimerstartswhenaHandoverRequestmessageissenttotheMSCfor
anexternalBSChandover.
StopEvent
The Timer is stopped when handover response message is received by the

BSSentity.
ExpiryEvent

T7 10sec 5sec 10sec


31

6.3.4TQHO
Category
ThistimerdefinesthemaximumQueuingtimeforaHandoverrequest.
StartEvent
The timer starts when the BSS places a Handover request in the resource
queueforallocation.
StopEvent
The timer is stopped when the Handover request is allocated the required
resourcebytheBSSentity.
ExpiryEvent
In case of an expiry event of this timer, the handover request is removed

fromthequeueandthehandoverprocedureisaborted.

TQHO 30sec 5sec 8sec


32
6.3.5T3121
Category
ThistimerISrelatedwithinterBSCand2G/3Ghandovers.
StartEvent
The timer is started when a request is sent for an interBSC or 2G/3G

handover.
StopEvent
The timer is stopped when a Handover complete message is received by

theBSSentity.
ExpiryEvent
In case of an expiry event of this timer, Clear request is sent and the
handoverprocedureisaborted.

TQHO NA 14sec 10sec


33
6.4GPRSTIMERS

6.4.1T3182
Category
This is an MS Based Timer and it is concerned with the RLC Window and
stallingofTBF.
StartEvent
IftheRLCtransmitwindowisfilledwithtransmittedblocksandanyofthem
isunacknowledged,thentheTBFwindowstallsandnomoreblockscanbe
set.Atthistime,T3182isstarted.
StopEvent
The timer stops once the acknowledgment for all the transmitted blocks
hasbeenreceived.
ExpiryEvent
If the timer expires, then another timer N3102 is decremented. The Radio
resources are released and the Mobile station tires to reestablish the TBF
withthesamecellthroughpacketchannelrequest.


34
6.4.2T3164
Category
ThisisanMSbasedtimerwhichisconcernedtheaccessproceduresduring
GPRSconnections.
StartEvent
MS access the network for a GPRS connection through the Packet data
request. The BTS send the packet uplink assignment message through the
USFaccess.Thetimerwillstartonreceptionofthisassignmentmessage.
StopEvent
ThetimerwillstoponcetheUSFuplinkaccesshasalsobeengrantedonthe
downlink.
ExpiryEvent
Ifthetimerexpires,andtheaccesshasnotbeengrantedonthedownlink,
thentheradioresourceswillbereleasedandtheMobilestationwillrepeat
thewholeprocedurefromthepacketdatarequestmessage.

35
6.4.3T3198
Category
This is an MS based timer which is concerned the acknowledgement of

transmittedRLCBlocks
StartEvent
When a RLC block is transmitted by the Mobile station, Timer T3198 is

started.
StopEvent
The timer is stopped when the acknowledgment of the transmitted RLC

blockisreceivedbytheMobilestation.
ExpiryEvent
If the timer expires with no acknowledgment for the transmitted blocks,

theRLCblocksistaggedasNACKintheMS.


36
6.4.4T3180
Category
ThistimerisrelatedwiththedynamicallocationofUplinkTBFintheGPRS
connection.
StartEvent
ThistimerisstartedduringthedynamicallocationoftheUplinkTBF.When
thelastblockissentaspermittedbytheUSFgranularity,theTimer3180is
startedwiththistransmission.
StopEvent
WhentheUSFisreceivedinthedownlinkbytheMS,thistimerisstopped.
ExpiryEvent
In case the timer expires, the MS abandons the TBF and the access
procedureisrepeatedwiththesamecell.


37
6.4.5T3190
Category
ThistimerisrelatedwiththedownlinkassignmentofPacketData.
StartEvent
ThetimerisstartedwhentheMobilestationreceivesthedownlinkpacket
dataassignmentfromtheBSSentity.
StopEvent
The timer is stopped when the Mobile station receives the downlink block
containingtheallocatedTFI.
ExpiryEvent
In case the timer expires, the mobile station releases the radio resources
andabortstheTBFconnection.Inadditiontothis,theMobilestationstarts
monitoringtheCommonControlPacketchannel.


38
6.4.6T3192
Category
ThistimerisconcernedwiththereleaseofPacketDataChannel
StartEvent
ThetimerisstartedwhenthelastblockofdownlinkTBFisreceived.
StopEvent
IfamessageforforcedreleaseofPacketDatachannelisreceived,thetimer
isstopped.
ExpiryEvent
When the timer expires, the radio resources are released and the packet
datasessioncomestoanend.Itistobenotedthatthevalueofthistimeris
smaller than T3193, in order to make it sure that the TFI of this MS is not
allocatedtoanyotherMSinthemeantime.


39
6.4.7T3200
Category
ThisTimerisrelatedwiththepartitionedtransmissionoftheRLCBlocks.
StartEvent
InthepartitionedtransmissionofRLCblocks,theRLCframesaredivedinto
segments with each segment having its own RTI (Radio Transaction
Indicator).IftheoneofthesegmentisnotreceivedwithitssubsequentRTI,
timerT3200isstarted.
StopEvent
The timer is stopped when the correct segment with the following RTI is
received.
ExpiryEvent
IncasethetimeexpiresandthecorrectRTIhasnotbeenreceived,thenthe
wholecontrolblockisrejectedasaoneormoresegmentsaremissing.


40
6.4.8T3162
Category
This timer is concerned with the queuing procedure employed during the
packetdataaccess.
StartEvent
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.
StopEvent
The timer is stopped in case of a packet assignment message or packet

accessesrejectmethod.
ExpiryEvent
If the timer expires without any assignment or reject message, the access
procedure is aborted and the mobile monitors the Packet data common
controlchannel.


41
6.4.9T3168
Category
This timer is concerned with acquisition of TBF resources during a Packet

Datasession.
StartEvent
This timer starts when a packet data request is sent by the Mobile station
formoredataresourcesduringaTBFsession.
StopEvent
TheTimerisstoppedwhentheassignmentmessageisreceivedforthenew
uplinkresourceofTBF.
ExpiryEvent
Incasethetimerexpires,therequestofPacketDataresourcesisresentby
theMobileStation.


42
6.4.10T3170
Category
ThistimerdeterminesthetimespanforwhichtheMobilestationwillwait
aftersendingtheallowednumberofPacketDatarequests.
StartEvent
The timer starts when the last of the allowed Packet Data Request is sent
bytheMobilestationtotheBSSentity.
StopEvent
ThetimerisstoppedwhentheMobilestationreceivestheuplinkresources
assignmentmessagefromtheBSSentity.
ExpiryEvent
In case the timer expires, the access procedure is aborted and the upper
layersareinformedaswell.

43
6.4.11T3172
Category
This Timer is concerned with the wait time used for retransmitting the
accessrequestforPacketData.
StartEvent
The timer begins with the Packet Assignment Reject method and this
messagealsocontainstheamountoftime,thetimerhastoremainactive.
StopEvent
The timer is stopped when the Packet Assignment message is received in

responsetotheaccessrequest.
ExpiryEvent
In case the timer expires, a request of Packet Data resources is resent by

theMobileStation.

44
6.4.12T3176
Category
This timer is concerned with the signaling for cell change failure during
packetdatasession.
StartEvent
Thetimerisstartedwhenthefirstmessageforcellchangefailureissentto
theBSSentity.
StopEvent
Thetimerisstoppedifasuccessfulcellchangeoccursandtheconfirmation
messageissenttotheMobilestation..
ExpiryEvent
Incasethetimerexpires,thesignalingforthefailedcellchangesisstopped
andtheMobilestationreturnstonormaloperation.


45
6.4.13T3188
Category
ThistimerisusedforthefixedallocationofuplinkTBF.
StartEvent
ThetimerisstartedwhentheMobilestationsendsarequesttoBSSentity
regardingaccessforthefixeduplinkTBF..
StopEvent
The timer is stopped once the Mobile station receives the assignment
messagefortheuplinkresource.
ExpiryEvent
Incasethetimerexpires,therequestfortheresourcesisresent.


46
6.4.14T3322
Category
ThistimerisinvolvedintheDetachprocessinthePacketDataconnection.
StartEvent
ThetimerisstartedwhenthedetachrequestissentbytheMobilestation
totheBSSentity.
StopEvent
The timer is stopped when the Mobile station receives the Detach accept
messagefromtheBSSentity.
ExpiryEvent
In case the timer expires, the detach request is resent by the Mobile
station.


47

6.4.15T3380
Category
ThistimerisusedinthePDPContextactivationprocedure.
StartEvent
The timer is started when the Mobile station sends the request for PDP
contextactivation.
StopEvent
The timer is stopped when the BTS entity sends the confirmation message
fortheattachprocedure.
ExpiryEvent
In case the timer expires, the request for PDP context is resent by the
Mobilestation.


48
6.4.16T3385
Category
ThistimerisusedinthePDPContextactivationprocedure.
StartEvent
The timer is started when the network sends the request for start of data
sessiontotheSGSN.
StopEvent
ThetimerisstoppedwhentheSGSNentitysendstheconfirmationmessage
forthestartofdataconnection.
ExpiryEvent
In case the timer expires, the request for data session is resent by the
network.


49
6.4.17T3386
Category
ThistimerisusedinthePDPContextmodificationprocedure.
StartEvent
The timer is started when the network sends the request for modification
ofPDPcontexttotheMS.
StopEvent
The timer is stopped when the network receives the response of the
modificationmessage.
ExpiryEvent
In case the timer expires, the request for modification for PDP Context is
resentbythenetwork.


50
6.4.18T3390
Category
ThistimerisusedinthePDPContextdeactivationprocedure.
StartEvent
ThetimerisstartedwhentheMSsendstherequestfordeactivationofPDP
contexttothenetwork.
StopEvent
The timer is stopped when the MS receives the Deactivation accept

messagefromthenetwork.
ExpiryEvent
In case the timer expires, the request for deactivation for PDP Context is
resentbytheMS.


51
6.4.19T3395
Category
ThistimerisusedinthePDPContextdeactivationprocedure.
StartEvent
The timer is started when the GPRS Sub network sends the request for
deactivationofPDPcontexttothenetwork.
StopEvent
ThetimerisstoppedwhentheGPRSSubnetworkreceivestheDeactivation
acceptmessagefromthenetwork.
ExpiryEvent
In case the timer expires, the request for deactivation for PDP Context is
resentbytheGPRSsubnetwork.


52
6.4.20T3158
Category
ThistimerrelatestoPeriodbetweenmeasurementreports.The
Measurementreportsmaybemadeinpacketidlemodeorpackettransfer
mode,thetimerbeingsetbyNC_REPORTING_PERIOD_I(packetidle)or
NC_REPORTING_PERIOD_T(transfer).
StartEvent
Sendingofpreviousmeasurementreport.
StopEvent
None
ExpiryEvent
Nextmeasurementreportsent.

53
6.4.21T3166
Category
ThistimeristheOnephaseaccesscontentiontimer
StartEvent
WhenthefirstRLC/MACblockistransmitted
StopEvent
whenapacketuplinkack/nackreturningTLLIisreceived
ExpiryEvent
Onexpiry,themobilestationmuststoptransmittingand
disconnectfromtheradioresources.Acontentionfailureorotherfailure
hasoccurred.

54
6.4.22T3169
Category
ResponsetoUSFtolerancetimer
StartEvent
N3101reachesitsallowedmaximumcount,N3101_MAX.
StopEvent
None
ExpiryEvent
Onexpiring,theUSFisreleased(whichmeansitcanbereassignedto
anothermobilestation).

55
6.4.23T3174
Category
Handover(cellchangeorder)failuretimer
StartEvent
WhentheGPRSsubnetworkisincommandofcellselection,itmaytellthe
mobilestationtochangetoanothercellwithpacketcellchangeorder.This
commandstartsT3174andthemobilestationchangesphysicalchannels,
sendingapacketchannelrequesttothenewcell.
StopEvent
Whenapacketuplinkassignmentisreceivedfromthenewcell.
ExpiryEvent
HandoverorcellchangehasfailedandT3176starts.


56
6.4.24T3182
Category
Windowstalltimeoutfordynamicallocation
StartEvent
WhentheRLCtransmitwindowkisfilledwithtransmittedRLC/MACblocks,
anyoneofwhichisunacknowledged,thentheTBFwindowstallsandno
moreblockscanbesent.T3182isthenstarted.
StopEvent
PacketuplinkacknowledgereceptionfromtheGPRSsubnetwork,allowing
thewindowtobeadvancedandtransmissionstoberesumed.
ExpiryEvent
N3102isdecremented(bytheamountPAN_DECsentinpacketsystem
information),disconnectsfromtheradioresourcesandattemptstore
establishtheTBFinthesamecellwithpacketchannelrequest.


57
6.4.25T3178
Category
Packetidlemodeextendedmeasurementreportperiod
Thevalueofthistimeriscontainedintheidlemodeextended
measurementreportscommandcontainedinPSI5orPCCCH.Themobile
stationwillreportmeasurementswiththisperiodicity.
StartEvent
N/A
StopEvent
N/A
ExpiryEvent
N/A


58
6.4.26T3184
Category
Fixedallocationpacketuplinkack/nacktolerancetimer
StartEvent
Receiptofpacketuplinkack/nack.
StopEvent
Receiptofthenextpacketuplinkack/nack.
ExpiryEvent
MobilestationreleasestheTBFandradioresources.


59
6.4.27T3191
Category
Responsetofinaldatablocktolerancetimer
StartEvent
TransmissionofthefinalRLCdatablockinadownlinkTBF
StopEvent
Receiptofpacketdownlinkack/nackorpacketcontrolack
ExpiryEvent
TFIandotherresourcesarereleased.


60
6.4.28T3193
Category
UplinkRLCreleasetimer.ThisisthenetworkcounterpartofT3192.This
timermustbelongerthanT3192.
StartEvent
(SeeT3192)
StopEvent
(SeeT3192)
ExpiryEvent
(SeeT3192)


61
6.4.29T3195
Category
LinkedtoTBFandTFI
StartEvent
T3195startswhenN3105reachestomaximumvalue
StopEvent
N/A
ExpiryEvent
ThenetworkreleasesTFIresource


62
6.4.30T3310
Category
Attachrequesttimer
StartEvent
Whenattachrequestissent.
StopEvent
Attachacceptisreceived.
ExpiryEvent
Attachrequestmessageisresent.


63
6.4.31T3312
Category
Periodicroutingareaupdate
DetermineswhenthemobilestationGMMfunctionwillperforman
automaticRAupdate(irrespectiveofwhethertheRAhaschanged).
StartEvent
N/A
StopEvent
N/A
ExpiryEvent
N/A


64
6.4.32T3314
Category
Readytimer
Thistimerspecifiesthemaximumtimethatthemobilestationisallowedto
remaininGMMreadyconditionwithoutanLLCPDUtransferwiththeGPRS
subnetwork.
StartEvent
SendingofanLLCPDUtotheGPRSsubnetwork
StopEvent
SendingofanLLCPDUtotheGPRSsubnetwork
ExpiryEvent
MobilestationisforcedtoGMMstandby.


65
6.4.33T3321
Category
GPRSsubnetworkdetachtimer
StartEvent
Sendingofdetachrequest
StopEvent
Receptionofdetachaccept.
ExpiryEvent
Mobilestationresendsthedetachrequest


66
6.5MISCELLANEOUS
6.5.1T3128
Category
This timer is related with the access procedure of Uplink investigation

process.
StartEvent
The timer starts when the uplink busy message is sent to the MS upon
receivingaccessrequestforuplinkinvestigation.
StopEvent
ThetimerisstoppedwhenUplinkfreemessageissenttotheMS.
ExpiryEvent
In case of an expiry event of this timer, the Uplink investigation process is

aborted.

Thedefaultvalueforthistimeris1second.

unavailable.


67
6.5.2T3210
Category
ThistimerisrelatedwiththeaccessprocedureofLocationUpdate.
StartEvent
ThetimerstartswhentheMSsendsthelocationupdaterequesttotheBSS
entity.
StopEvent
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
layerfailure.
ExpiryEvent
Incaseofanexpiryeventofthistimer,theBSStimerT3211isstarted.

unavailable.


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

procedure.
StartEvent
This timer starts when location_update_reject is received with the cause

valueindicatingnetworkfailure.
StopEvent
The Timer is stopped when the location update takes place or cell for the
particularMSischanged.
ExpiryEvent
In case this timer expires, the request for location update is again sent to
theBSSentity.



69
6.5.4T3212
Category
ThistimerisrelatedwiththeterminationofMMsignaling.
StartEvent
ThistimerstartswiththeterminationofMMsignaling.
StopEvent
ThetimerstopswhenthemessagefortheinitiationofMMsignalingissent
totheMSbytheBSSentity.
ExpiryEvent
Incasethetimerexpires,aperiodicrequestissentfortheLUupdate.


unavailable.


70
6.5.5T3220
Category
ThistimerisrelatedwiththeIMSIdetachprocedure.
StartEvent
The timer starts when the MS sends an IMSI detach message to the BTS
entity.
StopEvent
ThetimerisstoppedwhentheMSisremovedfromtheMMsublayer.
ExpiryEvent
Incasethetimerexpires,theMSenterstheNullperiodandrequestissent
forthestatustobeupdated.


unavailable.


71
7.0VENDORBASEDCOMPILEDLISTS
7.1MOTOROLATIMERS
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(Lbinterface)
T1_TIMER T4_TIMER_ID(Lbinterface)
T1_TIMER(Lbinterface) T5
T1_TIMER_ID(Lbinterface) T5(ITU)
T12 T5_TIMER
T12_TIMER T5_TIMER(Lbinterface)
T12_TIMER(Lbinterface) T5_TIMER_ID(Lbinterface)
T13 T6
T13_TIMER T6(ITU)
T13_TIMER(Lbinterface) T6_TIMER_ID(Lbinterface)
T14 T7
T14_TIMER T7(ITU)
T14_TIMER(Lbinterface) T7_EXPMSG_TYPE
T17 T7_TIMER_ID(Lbinterface)
T17_TIMER TCHassignmentsuccessful
T17_TIMER(Lbinterface) TCHassignmentunsuccessful
T2 TCONN_EST
T2(ITU) Tqho
T2_TIMER TREL
T2_TIMER(Lbinterface) bssgp_t1_timer
T2_TIMER_ID(Lbinterface) bssgp_t2_timer
T22 bssgp_t5_timer
T22_TIMER bssmap_t1
T22_TIMER(Lbinterface) bssmap_t10
T23 bssmap_t11
T23_TIMER bssmap_t13
T23_TIMER(Lbinterface) bssmap_t19
T3 bssmap_t20
T3(ITU) bssmap_t4
T3_TIMER_ID(Lbinterface) 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_t7
ss7_l2_t1
lb_int_ss7_l3_t1 ss7_l2_t2
lb_int_ss7_slt_t1 ss7_l3_t17
notalignedtimer 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 waitforclearcommandfromtheBSSbasedSMLCtimer
penalty_time waitforSCCPreleasecompletetimer
PENALTY_TIME waitforSCCPreleasedmessagefromSMLCtimer
PERF_LOC_TIMER wait_for_reselection
rr_ny1_rep wait_indication_parameters
rr_t3101 waitingforchangebackacknowledgement(rstattempt)timer
rr_t3103 waitingforchangebackacknowledgement(secondattempt)timer
rr_t3105 waitingforchangeoveracknowledgementtimer
rr_t3109 waitingforforceuninhibittimer
to362,3210,3212,3214,310 waitingforinhibitionacknowledgementtimer
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.2ALCATELTIMERS
Timer Entity Timer Entity

T(connest) 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

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
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.3HUAWEITIMERS
Timers
T200SDCCHSAPI3(5ms) PBGTValidTime(s)
T200SACCHSDCCH(10ms) PBGTWatchTime(s)
T200SACCHTCHSAPI3(10ms) LayerHOValidTime(s)
T200SACCHTCHSAPI0(10ms) LayerHOWatchTime(s)
T200FACCH/H(5ms) EdgeHOAdjCellValidTime(s)
T200FACCH/F(5ms)
EdgeHOAdjCellWatchTime(s)
T200SDCCH(5ms) EdgeHOValidTime(s)
AHRRadioLinkTimeout(SACCHperiod(480ms)) EdgeHOWatchTime(s)
AFRRadioLinkTimeout(SACCHperiod(480ms)) UpdatePeriodofCHRecord(min)
AHRSACCHMultiFrames(SACCHperiod(480ms)) TCHMinimumRecoveryTime(s)
AFRSACCHMultiFrames(SACCHperiod(480ms)) ReleaseDelayofDownlinkTBF(ms)
SACCHMultiFrames(SACCHperiod(480ms)) InactivePeriodofExtendedUplinkTBF(ms)
TDD3GBetterCellHOValidTime(s) ReleaseDelayofNonextendedUplinkTBF(ms)
TDD3GBetterCellHOWatchTime(s) CellReselectInterval(s)
QuickHandoverPunishTime(s) CellPenaltyLastTime(s)
QuickHandoverLastTime(0.5s) CellReselectionForbiddenTime
QuickHandoverStaticTime(0.5s) NonDRXPeriod
NumberofSatisfactoryMeasurements(s) GPRSPenaltyTime
TotalNumberofMeasurements(s) ExtensionMRPeriod
InterULAndOLSubcellsHOPenaltyTime(s) Max.DurationofDRX(s)
OLSubcellLoadDiversityHOPeriod(s) T3192
ModifiedStepLengthofULLoadHOPeriod(s) T3168
ULSubcellLoadHierarchicalHOPeriod(s) CellReselectionMRPeriodinPacketTransferMode
3GBetterCellHOValidTime(s) CellReselectionMRPeriodinPacketIdleMode
3GBetterCellHOWatchTime(s) TimerforULDataForward(ms)
PenaltyTimeafterOtoUHOFail(s) WaitforRelIndAMRHR
PenaltyTimeafterUtoOHOFail(s) WaitforRelIndAMRFR
PenaltyTimeofUtoOHO(s) T3103C(ms)
UnderlayHOStepPeriod(s) T3122(s)
UOHOValidTime(s) TREESTABLISH(ms)
UOHOWatchTime(s) T3111(ms)
PenaltyonMSFastMovingHO T3109(ms)
CfgPenaltyTimer T8(ms)
UmPenaltyTimer T3121(ms)
RscPenaltyTimer T3107(ms)
PenaltyTimeafterAMRTCHFHHOFail(s) T7(ms)
PenaltyTimeafterTAHO(s) T3103A(ms)
PenaltyTimeafterBQHO(s) ImmAssAInterfCreationTimer(ms)
MinIntervalforConsecutiveHOs T3101(ms)
MinIntervalforSDCCHHOs AidingDelayProtectTime(min)
MinIntervalforTCHHOs CCCHLoadIndicationPeriod(s)
TIGHTBCCHHOValidTime(s) RadioResourceReportPeriod(s)
TIGHTBCCHHOWatchTime(s) FrameStartTime
IntracellFHHOLastTime(s) Interf.CalculationPeriod(SACCHperiod(480ms))
IntracellFHHOStatTime(s) SpeedPenaltyTime

GSM Timers Document

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

GSM Timers Document

Hochgeladen von

Copyright:

Verfügbare Formate

MobilinkConfidentialProperty

The document aims to describe various timers implemented in the

Like any other wireless technology with a limited pool of resources,

As already highlighted, timer implementation is present throughout

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

As highlighted earlier there are different ways of categorizing timers. One

A further classification of GSM timers can be done on the basis of

The task of documenting the GSM timers is not an easy paced

Timer CallFlow Vendor Timer'sName Category

This is a MS based Timer and hence vendor implementation data is not

Once the timer expires, the procedure for immediate assignment is

This is a MS based Timer and hence vendor implementation data is

This timer starts when an assignment resource request is queued by the

The timer is stopped when the resource request is allocated a resource by

Motorola Alcatel Huawei

The timer stops when connect acknowledge message is received by the

The timer is stopped when the Assignment complete message is received

In case of an expiry event of this timer, an assignment failure command is

Once a call is ended, the resources that were dedicated to it now

Motorola Alcatel Huawei

The timer is stopped when the release indication message is received by

The Timer is stopped when handover response message is received by the

In case of an expiry event of this timer, the handover request is removed

The timer is started when a request is sent for an interBSC or 2G/3G

The timer is stopped when a Handover complete message is received by

This is an MS based timer which is concerned the acknowledgement of

When a RLC block is transmitted by the Mobile station, Timer T3198 is

The timer is stopped when the acknowledgment of the transmitted RLC

If the timer expires with no acknowledgment for the transmitted blocks,

The timer is stopped in case of a packet assignment message or packet

This timer is concerned with acquisition of TBF resources during a Packet

The timer is stopped when the Packet Assignment message is received in

In case the timer expires, a request of Packet Data resources is resent by

The timer is stopped when the MS receives the Deactivation accept

This timer is related with the access procedure of Uplink investigation

In case of an expiry event of this timer, the Uplink investigation process is

The timer is stopped when the Location_update_accept or reject message

This timer is related with the access procedure of location update

This timer starts when location_update_reject is received with the cause

Timer Entity Timer Entity

Das könnte Ihnen auch gefallen