GSM Tmers Document

7/30/2019 GSM Tmers Document

1/76

MobilinkConfidentialProperty

1

TIMERS

RFOPTIMIZATION

ENGINEERINGACCESSNETWORK

PMCL[MOBILINK]


2/76


2

FOREWORDThe 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/76


3

TABLEOFCONTENTS1.0 Introduction 52.0 Whatdoesthemanualcover? 53.0 Whytheneedtostudytimers? 54.0 TimerCategorization 6

4.1 EntityBasedCategorization 64.2 ProcessFlowBasedCategorization 6

5.0 Breakdown 76.0 GSMTimers 9

6.1 CallSetup 106.1.1 T3120 126.1.2 T3126 136.1.3 T3101 146.1.4 T3230 156.1.5 T303 166.1.6 T310 176.1.7 T11 186.1.8 T10 196.1.9 T313 206.1.10 T3107 216.1.11 T1 22

6.2 CallClearing 236.2.1 T13 236.2.2 T3111 246.2.3 T3109 256.2.4 T3110 26

6.3 Handover 276.3.1 T3103 286.3.2 T8 296.3.3 T7 306.3.4 TQHO 316.3.5 T3121 32

6.4 GPRS 326.4.1 T3182 336.4.2 T3164 346.4.3 T3198 356.4.4 T3180 366.4.5 T3190 376.4.6 T3192 386.4.7 T3200 39


4/76


4

6.4.8 T3162 406.4.9 T3168 416.4.10 T3170 426.4.11 T3172 436.4.12 T3176 446.4.13 T3188 456.4.14 T3322 466.4.15 T3380 476.4.16 T3385 486.4.17 T3386 496.4.18 T3390 506.4.19 T3395 516.4.20 T3158 526.4.21 T3166 536.4.22 T3169 546.4.23 T3174 556.4.24 T3182 566.4.25 T3178 576.4.26 T3184 586.4.27 T3191 596.4.28 T3193 606.4.29 T3195 616.4.30 T3310 626.4.31 T3312 636.4.32 T3314 646.4.33 T3321 65

6.5 Miscellaneous 666.5.1 T3210 666.5.2 T3128 676.5.3 T3211 686.5.4 T3212 696.5.5 T3220 70

7.0 CompiledList 717.1 MotorolaTimersList 717.2 AlcatelTimersList 737.3 HuaweiTimersList 76


5/76


5

1.0 INTRODUCTIONLikeany otherwirelesstechnology witha limitedpool 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.0 WHATDOESTHISMANUALCOVER?ThisdocumentaimstodescribeallthemajorBSStimers involved in

theGSMarchitecture.Thetimersarecategorizedintodifferentsubgroups,

dependingupontheirparententityandtheprocessflowtheyareinvolved

in.The

document

proceeds

further

by

giving

a

detailed

explanation

of

each

timeralongwithitsimplementationinthePMCLnetwork.

3.0 WHYTHENEEDTOSTUDYTIMERS?As already highlighted, timer implementation is present throughout

theGSMarchitecture.Timerseffectcallsetupprocedures,handovers,call

clearing, data usage (GPRS), VAS facilities; in short, everything that a

customermight

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.GSMnetworksaredependenton strictsynchronizationof 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/76


6

4.0 TIMERCATEGORIZATION4.1 ENTITYBASEDCATEGORIZATION

Ashighlightedearlier there are differentways of categorizing timers. One

categorization can be done on the basis of entity which includes the

followingcategories:

4.2 PROCESSFLOWBASEDCATEGORIZATION

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:

CallProcessingCallSetupCallRelease

Handovers GPRS Miscellaneous


7/76


7

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

procedure. The project is divided into two phases. The first phase

comprisedof

the

research

for

all

the

timers

involved

from

MS

to

BSS

as

per

the international GSM standards. In the second phase, vendor

implementationsofthesetimersweretakenintoconsideration.Acomplete

overviewofallthetimersinvolvedinPhase1isasunder:

Timer CallFlow Vendor Timer'sName Category DefaultValue Range

T3120 CallSetupMotorola MSTimer MSTimer Alcatel MSTimer MSTimer Huawei T3120 MSTimer MinisRACH

T+2S;MAX

5

MinisRACH

T+2S;MAX

5

T3126 CallSetupMotorola MSTimer MSTimer Alcatel MSTimer MSTimer Huawei T3126 MSTimer MinisRACH

T+2SMAX5

MinisRACH

T+2SMAX5

T3122 CallSetup Motorola wait_indication_parameter BTS none 0to255secAlcatel T3122 MSTimer 0to255secHuawei T3122 CellTimer 10sec 0255 sec

T3101 CallSetup Motorola rr_t3101 BTS 5sec 0to1000secAlcatel T3101 BSClevel 3sec 0to25.5secHuawei T3101 CellTimer 3sec 0.5to60sec

T3230

CallSetup

Motorola MSTimer MSTimer Alcatel

MS

Timer MS

Timer

Huawei T3230 MSTimer 15sec 15secT303 CallSetup Motorola MSTimer MSTimer Alcatel MSTimer MSTimer

Huawei T303 MSCTimer 20sec T310 CallSetup Motorola MSTimer MSTimer Alcatel MSTimer MSTimer

Huawei T310 MSCTimer 20sec T11 CallSetup Motorola bssmap_t11 BTS 28sec 0to1000secAlcatel T11 BSS 6sec 0to19 sec

Huawei T11 BSCTimer 8sec 1to30secT10

Call

Setup

Motorola bssmap_t10 BTS 28sec 0to1000secAlcatel

bssMapT10 BSS 14

sec

Huawei T10 BSCTimer 7sec 1to20secT313 CallSetup Motorola MSCtimer Alcatel T313 MS Timer

Huawei T313 MSCTimer 30sec 30secT8 Handover Motorola bssmap_t8 BTS 28sec 0to1000secAlcatel bssMapT8 BSS 14sec 0to25.5sec

Huawei T8 CellTimer 10sec 0.5to60secT3103 Handover Motorola rr_t3103 BTS 30sec 0to1000sec


8/76


8

Alcatel T3103 BSS 16.5 sec 0to25.5secHuawei T3103 CellTimer 10sec 0.5to60sec

T1 GPRS Motorola bssmap_t1 BSC 30sec0to1000000

msec

Alcatel bssMapT1 BSS 16sec 10to25.5secHuawei T1 BSCTimer 30sec 1to300 sec

T13 CallClearing Motorola bssmap_t13 BSC 40sec 0to1000secAlcatel bssMapT13 BSS 15sec 0to6553.5secHuawei T13 BSCTimer 150sec 1to300sec

T7 Handover Motorola bssmap_t7 BSC 30sec 0to1000secAlcatel bssMapT7 BSS 5sec 0to20 secHuawei T7 CellTimer 10sec 0.5to60sec

TQHO Handover Motorola bssmap_tqho BSC 30sec 0to1000secAlcatel T_QHO BSS 3sec 0to20secHuawei TQHO BSCTimer 8sec 1to30sec

T3111 CallClearing Motorolarr_t3111_sd BTS 1.5sec 0to1000sec

rr_t3111_tch BTS 1.5sec 0to1000sec

Alcatel T3111 BSS 0.5sec 0to2 secHuawei T3111 CellTimer 1sec 0.5to60sec

T3109 CallClearing Motorola rr_t3109 BTS 14.4sec 0to1000secAlcatel T3109 BSS 12sec 0to35secHuawei T3109 CellTimer 27sec 135sec

T3121 Handover Motorola MSCTimer Alcatel T3121 BSS 14sec 0to25.5secHuawei T3121 CellTimer 10sec 0.5to60

T3107 CallSetup Motorola RRSM_T10 BTS 28sec 0to1000secAlcatel T3107 BSS 14sec 0to25.5secHuawei T3107 CellTimer 10sec 0.5to60sec

T200 Configurational Motorola lapd_t200_timer BTS 2.5sec 1.4to5secAlcatel T200 BSS 0.3sec 0.3to1secHuawei T200(FACCH/F/H) CellTimer 0.05sec 1to0.255sec

T9101 CallClearing Motorola Alcatel T9101 Network 10sec 0to6553.5secHuawei SCCP_TREL(s) BSCTimer 15sec 10to20sec

T9104 CallClearingMotorola Alcatel T9104 BSS 2sec 0to25.5secHuawei TCLEARREQ(BSC) BSCTimer 5sec 1to150sec

TNT3(MSC) MSCTimer 6sec 1to120sec

T9108 CallClearing Motorola Alcatel T9108 Network 3sec 0to6553.5secHuawei

T3110 CallClearingMotorola MSTimer MSTimer Alcatel MSTimer MSTimer Huawei T3110 MSTimer 10sec 0.5to60sec


9/76


9

6.0 GSMTIMERSThe 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

formatisasgivenbelow.

y TimerNameThis field will include the name of the Timer, as used in the

internationalGSMstandards.

yCategory

This field will indicate the placement of the timers in the GSM

network.ForExampleeitheratimerisusedinCallSetupprocedures

oritisusedtoadministeraHandover.

y StartEventThisfieldwillincludetheeventwhichtriggersthetimer.

y StopEventThisfieldwillincludetheeventuponwhich,thetimerstops.

y ExpiryEventThisistheeventwhichtakesplace,oncethetimerhasexpired.

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

defaultvalues.


10/76


10

6.1 CALLPROCESSINGThis section deals with timers that essentially make up the call

requestandcallsetupprocedure.Askimthroughthecallflowshownbelow

willhelp

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/76


11

CallProcessing(Contd...)


12/76


12

6.1.1 T3120CategoryThis timer is included in the Call Request procedure which starts with the

RACHrequest.

StartEventThistimerstartswhentheRACHrequestissenttothenetwork.

StopEventThetimerstopsoncetheRACHacknowledgmentisreceived.

ExpiryEventOnce 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/76


13

6.1.2 T3126

CategoryThis timer is included in the Call Request procedure which starts with the

RACHrequest.

StartEventThis timer starts when the maximum amount of Channel requests have

beensentbytheMS.

StopEventThetimerstopswhenimmediateassignmentmessageisreceivedfromthe

BSS.

ExpiryEventOnce

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/76


14

6.1.3 T3101CategoryThis timer is included in the Call Setup procedure which starts with the

immediateassignmentprocedure.

StartEventThis timer starts when the immediate assignment message is sent to the

MSbytheBSSentity.

StopEventThetimerstopswhentheEstablishindicationmessageissentbytheMSto

theBSSentity.

ExpiryEventOncethetimerexpires,theprocedureforcallsetupisaborted.

Thevendorbasedvaluesforthistimeraregivenbelowforreference.

Motorola Alcatel HuaweiT3101 2sec 3sec 3sec


15/76


15



StartEventThistimerstartswhentheCMservicerequestissentbytheMStotheBSS

entity

StopEventThetimerstopswhentheMSreceivesthemessageofCMServicerequest

acknowledged.ItisalsostoppedincaseaCMservicerejectisreceived.

ExpiryEventOncethetimerexpires,thereleaseindicationisprovidedtotheBSSentity.

Thedefaultvalueforthistimeris15seconds


unavailable.


16/76


16



StartEventThistimerstartswhentheUAframefortheSDCCHconnection isreceived

bytheMS.

StopEventThetimerisstoppedwhentheCMservicerequestissentbytheMS.

ExpiryEventIncaseofanexpiryeventofthistimer,theCallsetupprocedureisaborted.

Thedefault

value

for

this

timer

is

20

seconds


unavailable.


17/76


17



StartEventThisTimerstartswhentheMSreceivesCallproceedingmessage.

StopEventThe timer stops once the Altering procedure begins and the call is

established.

ExpiryEventIncasethetimerexpiresandthealteringprocedurehasnotbegun,thecall

setupprocedureisabortedandNouserRespondingmessageissent.



unavailable.


18/76


18



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

BSSentity.

StopEventThetimer isstoppedwhentheresourcerequest isallocatedaresourceby

theBSSentity.

ExpiryEventOncethetimerexpires,theresourcerequestisrejectedandthecallsetup

procedureisaborted.

Thevendorbasedvaluesforthistimeraregivenbelowforreference.

Note:IfthevalueofT11timeriskeptmorethanthevalueofassign_successfultimer[Motorola],thiscouldleadtopotentialmaskingofCallSetupBlocking.CSSR



19/76


19



StartEventThis timer starts when assignment request is sent to the MS by the BSS

entity.

StopEventThetimerisstoppedwhentheassignmentcompletemessageissentbythe

MStotheBSSentity.

ExpiryEventOnce 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/76


20

6.1.9T313CategoryThis timer is included in the Call Setup procedure which starts with the


StartEventThis timer starts when the call connect message is sent to the call

originatingmobile.

StopEventThe timer stops when connect acknowledge message is received by the

networkentityfromtheMS.

ExpiryEventIncaseofanexpiryevenofthistimer,thecallsetupprocedure isaborted

andthecallisreleased.


21/76


21



StartEventThistimerstartswhentheassignmentcommandissentbytheBSSentityto

theMS.

StopEventThe timer is stopped when the Assignment complete message is received

byBSSentity.

ExpiryEventIncaseofanexpiryeventofthistimer,anassignmentfailurecommand is

sentandthechannelsarereleased.




22/76


22

6.5.11T1CategoryThis timer is included in the Call Setup procedure which starts with the


StartEventThistimerstartswhenablockingmessage issentbytheBSSentitytothe

MSCentityincaseofnonusableAinterfacetimeslot.

StopEventThetimerisstoppedwhenaBlockingacknowledgmentmessageisreceived

bytheBSSentity.

ExpiryEventOn 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/76


23

6.2 CALLCLEARINGOnce 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

processis

called

call

clearing.

This

section

describes

the

timers

used

in

call

clearing

6.2.1T13CategoryThistimerisusedintheResetProcedureinitiatedbytheMSC.

StartEventThetimerstartswhenaResetmessageissentbytheMSCtotheBSSentity.

StopEventThetimerstopsonwhentheMSCreceivesResetAcknowledgementbythe

BSS

entity.

ExpiryEventIncaseofexpiryevent,theResetacknowledgmentissentbytheBSStothe

MSC.




24/76


24

6.2.2T3111CategoryThistimerisincludedintheCallreleaseprocedurewhichincludesreleasing

ofTCHchannels

StartEventThistimerstartswiththereceptionofReleaseindicationmessagefromthe

BSSentity.

StopEventThe timer stops when the BSS entity sends the message for RF channel

releasetotherespectiveBTS.

ExpiryEventThe expiry of this timer causes the forced channel release procedure to

startandthechannelisreleasedfromallendsofthenetwork.


Motorola Alcatel HuaweiT3111 1.5sec 0.5 1.5


25/76


25


ofTCHchannels

StartEventThis timer starts when the channel release message is sent by the BSS

entitytothesubsequentBTS.

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

theBSSentity.

ExpiryEventIncaseofanexpiryeventofthistimer,thechannelsarereleasedandcall

procedureisaborted.




26/76


26


ofTCHchannels

StartEventThistimerstartswhentheMSreceivestheChannelreleasemessagefrom

theBSSentity.

StopEventThe timer stops once the MS receives a layer 2message from the BSS

entityforchannelrelease.

ExpiryEventIncasethetimerexpires,thenormalchannelreleasecontinuestillthecall

isreleased.



unavailable.


27/76


27

6.3 HANDOVERThissectiondealswithtimersthatessentiallymakeupthehandover

procedure.Likecallprocessing,aladderdiagramforhandoverisalsogiven

belowfor

the

ease

of

the

reader.

Details for each of the mentioned timers will follow along with

suitableinformationonthem.


28/76


28

6.3.1 T3103CategoryThistimerisusedintheHandoverProcedure.

StartEventThetimerstartswhentheinitiateHandovercommandissenttotheBTSby

theBSC.

StopEventTheTimerisstoppedwhenhandovercompletemessageisreceivedbythe

BSSentity.

ExpiryEventIn case the timer expires, the handover procedure is aborted and the

Handoverattemptistermedasunsuccessful.


Motorola Alcatel HuaweiT3103 30sec 16.5sec 30sec


29/76


29

6.3.2 T8CategoryThistimerisusedintheHandoverProcedure.

StartEventThetimerstartswhentheHandovercommandissenttotheMSviatheBSS

entity.

StopEventTheTimerisstoppedwhenhandovercompletemessageisreceivedbythe

BSSentity.

ExpiryEventIn case the timer expires, the handover procedure is aborted and the




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


30/76


30

6.3.3T7CategoryThistimerisusedintheHandoverProcedure.

StartEventThetimerstartswhenaHandoverRequestmessageissenttotheMSCfor

anexternalBSChandover.

StopEventTheTimerisstoppedwhenhandoverresponsemessage isreceivedbythe

BSSentity.

ExpiryEventIn

case

the

timer

expires,

the

handover

procedure

is

aborted

and

the





31/76


31

6.3.4TQHOCategoryThistimerdefinesthemaximumQueuingtimeforaHandoverrequest.

StartEventThe timer starts when the BSS places a Handover request in the resource

queueforallocation.

StopEventThetimer isstoppedwhentheHandoverrequest isallocatedtherequired

resourcebytheBSSentity.

ExpiryEventIncase of anexpiry eventof this timer, the handover request is removed

fromthequeueandthehandoverprocedureisaborted.


Motorola Alcatel HuaweiTQHO 30sec 5sec 8sec


32/76


32

6.3.5T3121CategoryThistimerISrelatedwithinterBSCand2G/3Ghandovers.

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

handover.

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

theBSSentity.

ExpiryEventIn case of an expiry event of this timer, Clear request is sent and the

handoverprocedureisaborted.


Motorola Alcatel HuaweiTQHO NA 14sec 10sec


33/76


33

6.4 GPRSTIMERS

6.4.1 T3182CategoryThis is an MS Based Timer and it is concerned with the RLC Window and

stallingofTBF.

StartEventIftheRLCtransmitwindowisfilledwithtransmittedblocksandanyofthem

isunacknowledged,thentheTBFwindowstallsandnomoreblockscanbe

set.Atthistime,T3182isstarted.

StopEventThe timer stops once the acknowledgment for all the transmitted blocks

hasbeenreceived.

ExpiryEventIfthetimerexpires,thenanothertimerN3102 isdecremented.TheRadio

resources arereleased and theMobile station tiresto reestablish the TBF

withthesamecellthroughpacketchannelrequest.


34/76


34

6.4.2 T3164CategoryThisisanMSbasedtimerwhichisconcernedtheaccessproceduresduring

GPRSconnections.

StartEventMS access the network for a GPRS connection through the Packet data

request.TheBTSsendthepacket uplinkassignmentmessagethroughthe

USFaccess.Thetimerwillstartonreceptionofthisassignmentmessage.

StopEventThetimerwillstoponcetheUSFuplinkaccesshasalsobeengrantedonthe

downlink.

ExpiryEventIf

the

timer

expires,

and

the

access

has

not

been

granted

on

the

downlink,

thentheradioresourceswillbereleasedandtheMobilestationwillrepeat

thewholeprocedurefromthepacketdatarequestmessage.


35/76


35

6.4.3 T3198CategoryThis is an MS based timer which is concerned the acknowledgement of

transmittedRLCBlocks

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

started.

StopEventThe timer is stopped when the acknowledgment of the transmitted RLC

blockisreceivedbytheMobilestation.

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

the

RLC

blocks

is

tagged

as

NACK

in

the

MS.


36/76


36

6.4.4 T3180CategoryThistimerisrelatedwiththedynamicallocationofUplinkTBFintheGPRS

connection.

StartEventThistimerisstartedduringthedynamicallocationoftheUplinkTBF.When

thelastblockissentaspermittedbytheUSFgranularity,theTimer3180is

startedwiththistransmission.

StopEventWhentheUSFisreceivedinthedownlinkbytheMS,thistimerisstopped.

ExpiryEventIn case the timer expires, the MS abandons the TBF and the access

procedure

is

repeated

with

the

same

cell.


37/76


37

6.4.5 T3190CategoryThistimerisrelatedwiththedownlinkassignmentofPacketData.

StartEventThetimerisstartedwhentheMobilestationreceivesthedownlinkpacket

dataassignmentfromtheBSSentity.

StopEventThetimer isstoppedwhentheMobilestationreceivesthedownlinkblock

containingtheallocatedTFI.

ExpiryEventIn case the timer expires, the mobile station releases the radio resources

andabortstheTBFconnection.Inadditiontothis,theMobilestationstarts

monitoring

the

Common

Control

Packet

channel.


38/76


38

6.4.6 T3192CategoryThistimerisconcernedwiththereleaseofPacketDataChannel

StartEventThetimerisstartedwhenthelastblockofdownlinkTBFisreceived.

StopEventIf

a

message

for

forced

release

of

Packet

Data

channel

is

received,

the

timer

isstopped.

ExpiryEventWhen the timer expires, the radio resources are released and the packet

datasessioncomestoanend.Itistobenotedthatthevalueofthistimeris

smallerthanT3193, inordertomake itsurethattheTFIofthisMS isnot

allocated

to

any

other

MS

in

the

mean

time.


39/76


39

6.4.7 T3200CategoryThisTimerisrelatedwiththepartitionedtransmissionoftheRLCBlocks.

StartEventInthepartitionedtransmissionofRLCblocks,theRLCframesaredivedinto

segments with each segment having its own RTI (Radio Transaction

Indicator).IftheoneofthesegmentisnotreceivedwithitssubsequentRTI,

timerT3200isstarted.

StopEventThe timer is stopped when the correct segment with the following RTI is

received.

ExpiryEventIn

case

the

time

expires

and

the

correct

RTI

has

not

been

received,

then

the

wholecontrolblockisrejectedasaoneormoresegmentsaremissing.


40/76


40

6.4.8 T3162CategoryThis timer is concerned with the queuing procedure employed during the

packetdataaccess.

StartEventThe 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.

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

accessesrejectmethod.

ExpiryEventIf

the

timer

expires

without

any

assignment

or

reject

message,

the

access

procedure is aborted and the mobile monitors the Packet data common

controlchannel.


41/76


41

6.4.9 T3168CategoryThis timer is concerned with acquisition of TBF resources during a Packet

Datasession.

StartEventThistimerstartswhenapacketdatarequest issentbytheMobilestation

formoredataresourcesduringaTBFsession.

StopEventTheTimerisstoppedwhentheassignmentmessageisreceivedforthenew

uplinkresourceofTBF.

ExpiryEventIncasethetimerexpires,therequestofPacketDataresourcesisresentby

the

Mobile

Station.


42/76


42

6.4.10 T3170CategoryThistimerdeterminesthetimespanforwhichtheMobilestationwillwait

aftersendingtheallowednumberofPacketDatarequests.

StartEventThetimerstartswhenthe lastoftheallowedPacketDataRequest issent

bytheMobilestationtotheBSSentity.

StopEventThetimerisstoppedwhentheMobilestationreceivestheuplinkresources

assignmentmessagefromtheBSSentity.

ExpiryEventIn case the timer expires, the access procedure is aborted and the upper

layers

are

informed

as

well.


43/76


43

6.4.11 T3172CategoryThis Timer is concerned with the wait time used for retransmitting the

accessrequestforPacketData.

StartEventThe timer begins with the Packet Assignment Reject method and this

messagealsocontainstheamountoftime,thetimerhastoremainactive.

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

responsetotheaccessrequest.

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

the

Mobile

Station.


44/76


44

6.4.12 T3176CategoryThis timer is concerned with the signaling for cell change failure during

packetdatasession.

StartEventThetimerisstartedwhenthefirstmessageforcellchangefailureissentto

theBSSentity.

StopEventThetimerisstoppedifasuccessfulcellchangeoccursandtheconfirmation

messageissenttotheMobilestation..

ExpiryEventIncasethetimerexpires,thesignalingforthefailedcellchangesisstopped

and

the

Mobile

station

returns

to

normal

operation.


45/76


45

6.4.13 T3188CategoryThistimerisusedforthefixedallocationofuplinkTBF.

StartEventThetimerisstartedwhentheMobilestationsendsarequesttoBSSentity

regardingaccessforthefixeduplinkTBF..

StopEventThe timer is stopped once the Mobile station receives the assignment

messagefortheuplinkresource.

ExpiryEventIncasethetimerexpires,therequestfortheresourcesisresent.


46/76


46

6.4.14 T3322CategoryThistimerisinvolvedintheDetachprocessinthePacketDataconnection.

StartEventThetimerisstartedwhenthedetachrequestissentbytheMobilestation

totheBSSentity.

StopEventThe timer is stopped when the Mobile station receives the Detach accept

messagefromtheBSSentity.

ExpiryEventIn case the timer expires, the detach request is resent by the Mobile

station.


47/76


47

6.4.15 T3380CategoryThistimerisusedinthePDPContextactivationprocedure.

StartEventThe timer is started when the Mobile station sends the request for PDP

contextactivation.

StopEventThetimerisstoppedwhentheBTSentitysendstheconfirmationmessage

fortheattachprocedure.

ExpiryEventIn case the timer expires, the request for PDP context is resent by the

Mobilestation.


48/76


48

6.4.16 T3385CategoryThistimerisusedinthePDPContextactivationprocedure.

StartEventThetimer isstartedwhenthenetworksendstherequestforstartofdata

sessiontotheSGSN.

StopEventThetimerisstoppedwhentheSGSNentitysendstheconfirmationmessage

forthestartofdataconnection.

ExpiryEventIn case the timer expires, the request for data session is resent by the

network.


49/76


49

6.4.17 T3386CategoryThistimerisusedinthePDPContextmodificationprocedure.

StartEventThetimer isstartedwhenthenetworksendstherequestformodification

ofPDPcontexttotheMS.

StopEventThe timer is stopped when the network receives the response of the

modificationmessage.

ExpiryEventIn case the timer expires, the request for modification for PDP Context is

resentbythenetwork.


50/76


50

6.4.18 T3390CategoryThistimerisusedinthePDPContextdeactivationprocedure.

StartEventThetimerisstartedwhentheMSsendstherequestfordeactivationofPDP

contexttothenetwork.

StopEventThe timer is stopped when the MS receives the Deactivation accept

messagefromthenetwork.

ExpiryEventIn case the timer expires, the request for deactivation for PDP Context is

resentbytheMS.


51/76


51

6.4.19 T3395CategoryThistimerisusedinthePDPContextdeactivationprocedure.

StartEventThe timer is started when the GPRS Sub network sends the request for

deactivationofPDPcontexttothenetwork.

StopEventThetimerisstoppedwhentheGPRSSubnetworkreceivestheDeactivation

acceptmessagefromthenetwork.

ExpiryEventIn case the timer expires, the request for deactivation for PDP Context is

resentbytheGPRSsubnetwork.


52/76


52

6.4.20 T3158CategoryThistimerrelatestoPeriodbetweenmeasurementreports.The

Measurementreportsmaybemadeinpacketidlemodeorpackettransfer

mode,thetimerbeingsetbyNC_REPORTING_PERIOD_I(packetidle)or

NC_REPORTING_PERIOD_T(transfer).

StartEventSending

of

previous

measurement

report.

StopEventNone

ExpiryEventNext

measurement

report

sent.


53/76


53

6.4.21 T3166CategoryThistimeristheOnephaseaccesscontentiontimer

StartEventWhenthefirstRLC/MACblockistransmitted

StopEventwhenapacketuplinkack/nackreturningTLLIisreceived

ExpiryEventOnexpiry,themobilestationmuststoptransmittingand

disconnectfromtheradioresources.Acontentionfailureorotherfailure

hasoccurred.


54/76


54

6.4.22 T3169CategoryResponsetoUSFtolerancetimer

StartEventN3101reachesitsallowedmaximumcount,N3101_MAX.

StopEventNone

ExpiryEventOnexpiring,theUSFisreleased(whichmeansitcanbereassignedto

anothermobilestation).


55/76


55

6.4.23 T3174CategoryHandover(cellchangeorder)failuretimer

StartEventWhentheGPRSsubnetworkisincommandofcellselection,itmaytellthe

mobilestationtochangetoanothercellwithpacketcellchangeorder.This

commandstartsT3174andthemobilestationchangesphysicalchannels,

sendingapacketchannelrequesttothenewcell.

StopEventWhenapacketuplinkassignmentisreceivedfromthenewcell.

ExpiryEventHandoverorcellchangehasfailedandT3176starts.


56/76


56

6.4.24 T3182CategoryWindowstalltimeoutfordynamicallocation

StartEventWhentheRLCtransmitwindowkisfilledwithtransmittedRLC/MACblocks,

anyoneofwhichisunacknowledged,thentheTBFwindowstallsandno

moreblockscanbesent.T3182isthenstarted.

StopEventPacketuplinkacknowledgereceptionfromtheGPRSsubnetwork,allowing

thewindowtobeadvancedandtransmissionstoberesumed.

ExpiryEventN3102isdecremented(bytheamountPAN_DECsentinpacketsystem

information),disconnects

from

the

radio

resources

and

attempts

to

re

establishtheTBFinthesamecellwithpacketchannelrequest.


57/76


57

6.4.25 T3178CategoryPacketidlemodeextendedmeasurementreportperiod

Thevalueofthistimeriscontainedintheidlemodeextended

measurementreportscommandcontainedinPSI5orPCCCH.Themobile

stationwillreportmeasurementswiththisperiodicity.

StartEventN/A

StopEventN/A

ExpiryEventN/A


58/76


58

6.4.26 T3184CategoryFixedallocationpacketuplinkack/nacktolerancetimer

StartEventReceiptofpacketuplinkack/nack.

StopEventReceiptofthenextpacketuplinkack/nack.

ExpiryEventMobilestationreleasestheTBFandradioresources.


59/76


59

6.4.27 T3191CategoryResponsetofinaldatablocktolerancetimer

StartEventTransmissionofthefinalRLCdatablockinadownlinkTBF

StopEventReceipt

of

packet

downlink

ack/nack

or

packet

control

ack

ExpiryEventTFIandotherresourcesarereleased.


60/76


60

6.4.28 T3193CategoryUplinkRLCreleasetimer.ThisisthenetworkcounterpartofT3192.This

timermustbelongerthanT3192.

StartEvent(SeeT3192)

StopEvent(SeeT3192)

ExpiryEvent(SeeT3192)


61/76


61

6.4.29 T3195CategoryLinked

to

TBF

and

TFI

StartEventT3195startswhenN3105reachestomaximumvalue

StopEventN/A

ExpiryEventThenetworkreleasesTFIresource


62/76


62

6.4.30 T3310CategoryAttachrequesttimer

StartEventWhenattachrequestissent.

StopEventAttach

accept

is

received.

ExpiryEventAttachrequestmessageisresent.


63/76


63

6.4.31 T3312CategoryPeriodicroutingareaupdate

DetermineswhenthemobilestationGMMfunctionwillperforman

automaticRAupdate(irrespectiveofwhethertheRAhaschanged).

StartEventN/A

StopEventN/A

ExpiryEventN/A


64/76


64

6.4.32 T3314CategoryReadytimer

Thistimerspecifiesthemaximumtimethatthemobilestationisallowedto

remaininGMMreadyconditionwithoutanLLCPDUtransferwiththeGPRS

subnetwork.

StartEventSendingofanLLCPDUtotheGPRSsubnetwork

StopEventSendingofanLLCPDUtotheGPRSsubnetwork

ExpiryEventMobilestationisforcedtoGMMstandby.


65/76


65

6.4.33 T3321CategoryGPRSsubnetworkdetachtimer

StartEventSendingofdetachrequest

StopEventReception

of

detach

accept.

ExpiryEventMobilestationresendsthedetachrequest


66/76


66

6.5 MISCELLANEOUS

6.5.1T3128CategoryThis timer is related with the access procedure of Uplink investigation

process.

StartEventThe

timer

starts

when

the

uplink

busy

message

is

sent

to

the

MS

upon

receivingaccessrequestforuplinkinvestigation.

StopEventThetimerisstoppedwhenUplinkfreemessageissenttotheMS.

ExpiryEventIncaseofanexpiryeventofthistimer,theUplink investigationprocess is

aborted.

Thedefaultvalueforthistimeris1second.


unavailable.


67/76


67

6.5.2T3210CategoryThistimerisrelatedwiththeaccessprocedureofLocationUpdate.

StartEventThetimerstartswhentheMSsendsthelocationupdaterequesttotheBSS

entity.

StopEventThetimer isstoppedwhentheLocation_update_acceptorrejectmessage

is received bythe MSentity.This timer isalso stopped in case of a lower

layerfailure.

ExpiryEventIncaseofanexpiryeventofthistimer,theBSStimerT3211isstarted.



unavailable.


68/76


68

6.5.3T3211CategoryThis timer is related with the access procedure of location update

procedure.

StartEventThis timer starts when location_update_reject is received with the cause

valueindicatingnetworkfailure.

StopEventTheTimer isstoppedwhenthe locationupdatetakesplaceorcell forthe

particularMSischanged.

ExpiryEventIncasethistimerexpires,the request for location update isagainsentto

theBSSentity.



69/76


69

6.5.4T3212CategoryThistimerisrelatedwiththeterminationofMMsignaling.

StartEventThistimerstartswiththeterminationofMMsignaling.

StopEventThe

timer

stops

when

the

message

for

the

initiation

of

MM

signaling

is

sent

totheMSbytheBSSentity.

ExpiryEventIncasethetimerexpires,aperiodicrequestissentfortheLUupdate.



unavailable.


70/76


70

6.5.5T3220CategoryThistimerisrelatedwiththeIMSIdetachprocedure.

StartEventThe timer starts when the MS sends an IMSI detach message to the BTS

entity.

StopEventThetimerisstoppedwhentheMSisremovedfromtheMMsublayer.

ExpiryEventIncasethetimerexpires,theMSenterstheNullperiodandrequestissent

forthestatustobeupdated.



unavailable.


71/76


71

7.0 VENDORBASEDCOMPILEDLISTS7.1 MOTOROLATIMERS

TimersT_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(Lb

interface)

T5_TIMER_ID

(Lb

interface)

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/76


72

TimerCLM_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_t2lb_int_ss7_l3_t12 ss7_l2_t3









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/76


73

7.2 ALCATELTIMERSTimer 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/76


74

Timer Entity Timer EntityT_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/76


75

Timer Entity Timer EntityT3103 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/76


7.3 HUAWEITIMERSTimers

T200SDCCHSAPI3(5ms) PBGTValidTime(s)

T200SACCHSDCCH(10ms) PBGTWatchTime(s)

T200

SACCH

TCH

SAPI3(10ms)

Layer

HO

Valid

Time(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

PenaltyTime

of

UtoO

HO(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)

GSM Tmers Document

Documents

Transcript of GSM Tmers Document