11 List of system parameters

04.083GPPMobile radio interface Layer 3 specificationRelease 1998TS

The description of timers in the following table should be considered a brief summary. The precise details are found in clauses 3 to 6, which should be considered the definitive descriptions.

11.1 Timers and counters for radio resource management

11.1.1 Timers on the mobile station side

T3122: This timer is used during random access, after the receipt of an IMMEDIATE ASSIGN REJECT message.

Its value is given by the network in the IMMEDIATE ASSIGN REJECT message.

T3124: This timer is used in the seizure procedure during a hand-over, when the two cells are not synchronized.

Its purpose is to detect the lack of answer from the network to the special signal.

Its value is set to 675 ms if the channel type of the channel allocated in the HANDOVER COMMAND is an SDCCH (+ SACCH); otherwise its value is set to 320 ms.

T3126: This timer is started either

after sending the maximum allowed number of CHANNEL REQUEST messages during an immediate assignment procedure.

or

on receipt of an IMMEDIATE ASSIGNMENT REJECT message,

whichever occurs first.

It is stopped at receipt of an IMMEDIATE ASSIGNMENT message, or an IMMEDIATE ASSIGNMENT EXTENDED message.

At its expiry, the immediate assignment procedure is aborted.

The minimum value of this timer is equal to the time taken by T+2S slots of the mobile station’s RACH. S and T are defined in sub-clause 3.3.1.2. The maximum value of this timer is 5 seconds.

T3128: This timer is started when the mobile station starts the uplink investigation procedure and the uplink is busy.

It is stopped at receipt of the first UPLINK FREE message.

At its expiry, the uplink investigation procedure is aborted.

The value of this timer is set to 1 second.

T3130: This timer is started after sending the first UPLINK ACCESS message during a VGCS uplink access procedure.

It is stopped at receipt of a VGCS ACCESS GRANT message.

At its expiry, the uplink access procedure is aborted.

The value of this timer is set to 5 seconds.

T3110: This timer is used to delay the channel deactivation after the receipt of a (full) CHANNEL RELEASE. Its purpose is to let some time for disconnection of the main signalling link.

Its value is set to such that the DISC frame is sent twice in case of no answer from the network. (It should be chosen to obtain a good probability of normal termination (i.e. no time out of T3109) of the channel release procedure.)

T3134 This timer is used in the seizure procedure during an RR network commanded cell change order procedure. Its purpose is to detect the lack of answer from the network or the lack of availability of the target cell.

Its value is set to 5 seconds.

T3142: The timer is used during packet access on CCCH, after the receipt of an IMMEDIATE ASSIGNMENT REJECT message.

Its value is given by the network in the IMMEDIATE ASSIGNMENT REJECT message.

T3146: This timer is started either

after sending the maximum allowed number of CHANNEL REQUEST messages during a packet access procedure.

or

on receipt of an IMMEDIATE ASSIGNMENT REJECT message during a packet access procedure,

whichever occurs first.

It is stopped at receipt of an IMMEDIATE ASSIGNMENT message, or an IMMEDIATE ASSIGNMENT EXTENDED message.

At its expiry, the packet access procedure is aborted.

The minimum value of this timer is equal to the time taken by T+2S slots of the mobile station’s RACH. S and T are defined in sub-clause 3.3.1.2. The maximum value of this timer is 5 seconds.

T3164: This timer is used during packet access using CCCH. It is started at the receipt of an IMMEDIATE ASSIGNMENT message.

It is stopped at the transmission of a RLC/MAC block on the assigned temporary block flow, see 3GPP TS 04.60.

At expire, the mobile station returns to the packet idle mode.

The value of the timer is 5 seconds.

T3190: The timer is used during packet downlink assignment on CCCH. It is started at the receipt of an IMMEDIATE ASSIGNMENT message or of an PDCH ASSIGNMENT COMMAND message when in dedicated mode.

It is stopped at the receipt of a RLC/MAC block on the assigned temporary block flow, see 3GPP TS 04.60.

At expiry, the mobile station returns to the packet idle mode.

The value of the timer is 5 s.

11.1.2 Timers on the network side

T3101: This timer is started when a channel is allocated with an IMMEDIATE ASSIGNMENT message. It is stopped when the MS has correctly seized the channels.

Its value is network dependent.

NOTE 1: It could be higher than the maximum time for a L2 establishment attempt.

T3103: This timer is started by the sending of a HANDOVER message and is normally stopped when the MS has correctly seized the new channel. Its purpose is to keep the old channels sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost.

Its value is network dependent.

NOTE 2: It could be higher than the maximum transmission time of the HANDOVER COMMAND, plus the value of T3124, plus the maximum duration of an attempt to establish a data link in multiframe mode.)

T3105: This timer is used for the repetition of the PHYSICAL INFORMATION message during the hand-over procedure.

Its value is network dependent.

NOTE 3: This timer may be set to such a low value that the message is in fact continuously transmitted.

T3107: This timer is started by the sending of an ASSIGNMENT COMMAND message and is normally stopped when the MS has correctly seized the new channels.

Its purpose is to keep the old channel sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost.

Its value is network dependent.

NOTE 4: It could be higher than the maximum transmission time of the ASSIGNMENT COMMAND message plus twice the maximum duration of an attempt to establish a data link multiframe mode.

T3109: This timer is started when a lower layer failure is detected by the network, when it is not engaged in a RF procedure. It is also used in the channel release procedure.

Its purpose is to release the channels in case of loss of communication.

Its value is network dependent.

NOTE 5: Its value should be large enough to ensure that the MS detects a radio link failure.

T3111: This timer is used to delay the channel deactivation after disconnection of the main signalling link. Its purpose is to let some time for possible repetition of the disconnection.

Its value is equal to the value of T3110.

T3113: This timer is started when the network has sent a PAGING REQUEST message and is stopped when the network has received the PAGING RESPONSE message.

Its value is network dependent.

NOTE 6: The value could allow for repetitions of the Channel Request message and the requirements associated with T3101.

T3115: This timer is used for the repetition of the VGCS UPLINK GRANT message during the uplink access procedure.

Its value is network dependent.

NOTE 7: This timer may be set to such a low value that the message is in fact continuously transmitted.

T3117: This timer is started by the sending of a PDCH ASSIGNMENT COMMAND message and is normally stopped when the MS has correctly accessed the target TBF.

Its purpose is to keep the old channel sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost.

Its value is network dependent.

NOTE 8: It could be higher than the maximum transmission time of the PDCH ASSIGNMENT COMMAND message plus T3132 plus the maximum duration of an attempt to establish a data link in multiframe mode.

T3119: This timer is started by the sending of a RR-CELL CHANGE ORDER message and is normally stopped when the MS has correctly accessed the new cell. Its purpose is to keep the old channels sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost.

Its value is network dependent.

NOTE 9: It could be higher than the maximum transmission time of the RR_CELL CHANGE ORDER, plus T3134, plus the maximum duration of an attempt to establish a data link in multiframe mode.

T3141: This timer is started when a temporary block flow is allocated with an IMMEDIATE ASSIGNMENT message during a packet access procedure. It is stopped when the mobile station has correctly seized the temporary block flow.

Its value is network dependent.

11.1.3 Other parameters

Ny1: The maximum number of repetitions for the PHYSICAL INFORMATION message during a handover (see sub-clause 3.4.4.2.2). The value is network dependent.

Ny2: The maximum number of repetitions for the VGCS UPLINK GRANT message during an uplink access procedure (see sub-clause 3.3.1.2.2). The value is network dependent.

11.2 Timers of mobility management

Table 11.1/3GPP TS 04.08: Mobility management timers – MS-side

+—————————————————–+

│TIMER│MM│TIME│CAUSE FOR │NORMAL STOP │AT THE │

│NUM. │ST│OUT │START │ │EXPIRY │

│ │AT│VAL.│ │ │ │

+—–+–+—-+————+————-+————│

│T3210│3 │20s │-LOC_UPD_REQ│- LOC_UPD_ACC│ │

│ │ │ │sent │- LOC_UPD_REJ│ │

│ │ │ │ │- AUTH_REJ │Start T3211 │

│ │ │ │ │- Lower layer│ │

│ │ │ │ │ failure │ │

+—–+–+—-+————+————-+————│

│T3211│1 │15s │-LOC_UPD_REJ│- Time out │Restart the │

│ │2 │ │ with cause │- cell change│Location up-│

│ │ │ │ #17 netw. │- request for│date proc. │

│ │ │ │ failure │ MM connec- │ │

│ │ │ │-lower layer│ tion │ │

│ │ │ │ failure or │ establish- │ │

│ │ │ │ RR conn. │ ment │ │

│ │ │ │ released │- change of │ │

│ │ │ │ after │ LA │ │

│ │ │ │ RR conn. │ │ │

│ │ │ │ abort │ │ │

│ │ │ │ during loc.│ │ │

│ │ │ │ updating │ │ │

+—–+–+—-+————+————-+————│

│T3212│1,│Note│-termination│-initiation │initiate │

│ │2 │ 1 │ of MM ser- │ of MM ser- │periodic │

│ │ │ │ vice or MM │ vice or MM │updating │

│ │ │ │ signalling │ signalling │ │

+—–+–+—-+————+————-+————│

│T3213│1 │ 4s │-location up│- expiry │new random │

│ │2 │ │ dating fai │- change of │attempt │

│ │11│ │ lure │ BCCH para- │ │

│ │ │ │ │ meter │ │

+—–+–+—-+————+————-+————│

│T3220│7 │5s │-IMSI DETACH│- release │enter Null │

│ │ │ │ │ from RM- │or Idle, AT-│

│ │ │ │ │ sublayer │TEMPTING TO │

│ │ │ │ │ │UPDATE │

+—–+–+—-+————+————-+————│

│T3230│5 │15s │-CM SERV REQ│- Cipher mode│provide │

│ │ │ │ │ setting │release ind.│

│ │ │ │CM REEST REQ│- CM SERV REJ│ │

│ │ │ │ │- CM SERV ACC│ │

+—–+–+—-+————+————-+————│

│T3240│9 │10s │see sub-clause │ see sub-clause │ abort the │

│ │10│ │ 11.2.1 │ 11.2.1 │ RR connec- │

│ │ │ │ │ │ tion │

+—————————————————–+

│T3241│25│300s│ see sub-clause │ see sub-clause │ abort the │

│ │ │ │ 11.2.1 │ 11.2.1 │ RR connec- │

│ │ │ │ │ │ tion │

+—————————————————–+

NOTE 1: The timeout value is broadcasted in a SYSTEM INFORMATION message.

Table 11.2/3GPP TS 04.08: Mobility management timers – network-side

+————————————————————–+

│TIMER│MM│TIME│CAUSE FOR │NORMAL STOP │AT THE FIRST│AT THE │

│NUM. │ST│OUT │START │ │EXPIRY │SECOND │

│ │AT│VAL.│ │ │ │EXPIRY │

+—–+–+—-+————+————-+————+——–│

│T3250│6 │12s │TMSI-REAL- │TMSI-REALL- │ Optionally │ │

│ │ │ │CMD or │ COM received│ Release │ │

│ │ │ │LOC UPD ACC │ │ RR connec- │ │

│ │ │ │with new │ │ tion │ │

│ │ │ │TMSI sent │ │ │ │

+—–+–+—-+————+————-+————+——–│

│T3255│ │Note│LOC UPD ACC │CM SERVICE │Release RR │ │

│ │ │ │sent with │ REQUEST │Connection │ │

│ │ │ │"Follow on │ │or use for │ │

│ │ │ │ Proceed" │ │mobile sta- │ │

│ │ │ │ │ │tion termi- │ │

│ │ │ │ │ │nating call │ │

+—–+–+—-+————+————-+————+——–│

│T3260│5 │12s │AUTHENT- │AUTHENT- │ Optionally │ │

│ │ │ │REQUEST │RESPONSE │ Release │ │

│ │ │ │ sent │ received │ RR connec- │ │

│ │ │ │ │ │ tion │ │

+—–+–+—-+————+————-+————+——–│

│T3270│4 │12s │IDENTITY │IDENTITY │ Optionally │ │

│ │ │ │REQUEST │RESPONSE │ Release │ │

│ │ │ │ sent │ received │ RR connec- │ │

│ │ │ │ │ │ tion │ │

+————————————————————–+

NOTE 2: The value of this timer is not specified by this recommendation.

11.2.1 Timer T3240 and Timer T3241

Timer T3240 is started in the mobile station when:

– the mobile station receives a LOCATION UPDATING ACCEPT message completing a location updating procedure in the cases specified in sub-clause 4.4.4.6 and 4.4.4.8;

– the mobile station receives a LOCATION UPDATING REJECT message in the cases specified in sub-clause 4.4.4.7;

– the mobile station has sent a CM SERVICE ABORT message as specified in sub-clause 4.5.1.7;

– the mobile station has released or aborted all MM connections in the cases specified in 4.3.2.5, 4.3.5.2, 4.5.1.1, and 4.5.3.1.

Timer T3240 is stopped, reset, and started again at receipt of an MM message.

Timer T3240 is stopped and reset (but not started) at receipt of a CM message that initiates establishment of an CM connection (an appropriate SETUP, REGISTER, or CP-DATA message as defined in 3GPP TS 04.08, 3GPP TS 04.10 or 3GPP TS 04.11).

Timer T3241 is started in the mobile station when entering MM state RR CONNECTION RELEASE NOT ALLOWED.

Timer T3241 is stopped and reset (but not started) when the MM state RR CONNECTION RELEASE NOT ALLOWED is left.

If timer T3241 expires, the MS shall abort the RR connection and enter the MM state MM IDLE.

11.2.2 Timers of GPRS mobility management

Table 11.3/3GPP TS 04.08: GPRS Mobility management timers – MS side

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON THE
1st , 2nd, 3rd , 4th EXPIRY Note 3

T3310

15s

GMM-
REG-INIT

ATTACH REQ sent

ATTACH ACCEPT received

ATTACH REJECT received

Retransmission of ATTACH REQ

T3311

15s

GMM-DEREG ATTEMPTING TO ATTACH or

GMM-REG ATTEMPTING TO UPDATE

ATTACH REJ with other cause values as described in chapter ‘GPRS Attach’

ROUTING AREA UPDATE REJ with other cause values as described in chapter ‘Routing Area Update’

Low layer failure

Change of the routing area

Restart of the Attach or the RAU procedure with updating of the relevant attempt counter

T3321

15s

GMM-

DEREG-INIT

DETACH REQ sent

DETACH ACCEPT received

Retransmission of the DETACH REQ

T3330

15s

GMM-ROUTING-UPDATING-INITIATED

ROUTING AREA UPDATE REQUEST sent

ROUTING AREA UPDATE ACC received

ROUTING AREA UPDATE REJ received

Retransmission of the ROUTING AREA UPDATE REQUEST
message

Table 11.3a/3GPP TS 04.08: GPRS Mobility management timers – MS side

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON
EXPIRY

T3302

T3212

Note 4

GMM-DEREG

or

GMM-REG

At attach failure and the attempt counter is greater than or equal
to 5.

At routing area updating failure and the attempt counter is greater than or equal to 5.

At successful attach

At successful routing area updating

On every expiry, initiation of the

GPRS attach procedure

or

RAU procedure

T3312

Default
54 min

Note1

GMM-REG

When READY state is left.

When entering state GMM-DEREG

Initiation of the Periodic RAU procedure

T3314

READY

Default
44 sec
Note 2

All except GMM-DEREG

Transmission of a PTP PDU

Forced to Standby

No cell-updates are performed

T3316
AA-READY

Default
44 sec
Note 2

Transmission of a PTP PDU

NOTE 1: The value of this timer is used if the network does not indicate another value in a GMM signalling procedure.

NOTE 2: The default value of this timer is used if neither the MS nor the Network send another value, or if the Network sends this value, in a signalling procedure.

NOTE 3: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.

NOTE 4: T3302 is loaded with the same value which is used to load T3212.

Table 11.4/3GPP TS 04.08: GPRS Mobility management timers – network side

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON THE
1st , 2nd, 3rd , 4th EXPIRY Note 3

T3322

6s

GMM-
DEREG-INIT

DETACH REQ sent

DETACH ACCEPT received

Retransmission of DETACH REQUEST

T3350

6s

GMM-COMMON-PROC-INIT

ATTACH ACCEPT
sent with P-TMSI and/or TMSI

RAU ACCEPT sent with P-TMSI and/or TMSI

P-TMSI REALLOC COMMAND
sent

ATTACH COMPLETE received

RAU COMPLETE received

P-TMSI REALLOC COMPLETE received

Retransmission of the same message type, i.e. ATTACH ACCEPT, RAU ACCEPT or REALLOC COMMAND

T3360

6s

GMM- COMMON-PROC-INIT

AUTH AND CIPH REQUEST
sent

AUTH AND CIPH RESPONSE received

Retransmission of AUTH AND CIPH REQUEST

T3370

6s

GMM-COMMON-PROC-INIT

IDENTITY REQUEST sent

IDENTITY RESPONSE received

Retransmission of IDENTITY REQUEST

Table 11.4a/3GPP TS 04.08: GPRS Mobility management timers – network side

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON
EXPIRY

T3313

Note1

GMM_REG

Paging procedure initiated

Paging procedure completed

Network dependent

T3314

READY

Default
44 sec
Note 2

All except GMM-DEREG

Receipt of a PTP PDU

Forced to Standby

The network shall page the MS if a PTP PDU has to be sent to the MS

T3316 AA-

READY

Default
44 sec
Note 2

Receipt of a PTP PDU

Mobile Reachable

Default 4 min greater than T3312

All except GMM-DEREG

Change from READY to STANDBY state

PTP PDU received

Network dependent but typically paging is halted on 1st expiry

NOTE 1: The value of this timer is network dependent.

NOTE 2: The default value of this timer is used if neither the MS nor the Network send another value, or if the Network sends this value, in a signalling procedure. The value of this timer should be slightly shorter in the network than in the MS, this is a network implementation issue.

NOTE 3: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.

11.2.3 Timers of session management

Table 11.2c/3GPP TS 04.08: Session management timers – MS side

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON THE
1st , 2nd, 3rd , 4th EXPIRY

T3380

30s

PDP-
ACTIVE-PEND

ACTIVATE PDP CONTEXT REQUEST sent

ACTIVATE
PDP CONTEXT ACCEPT received

ACTIVATE
PDP CONTEXT REJECT received

Retransmission of ACTIVATE PDP
CONTEXT REQ

T3390

8s

PDP-
INACT-PEND

DEACTIVATE PDP CONTEXT REQUEST sent

DEACTIVATE PDP CONTEXT ACC
received

Retransmission of DEACTIVATE
PDP CONTEXT REQUEST

NOTE: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.

Table 11.2d/3GPP TS 04.08: Session management timers – network side

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON THE
1st , 2nd, 3rd , 4th EXPIRY

T3385

8s

PDP-
ACT-PEND

REQUEST PDP CONTEXT ACTIVATION sent

ACTIVATE PDP CONTEXT REQ received

Retransmission of REQUEST PDP CONTEXT ACTIVATION

T3386

8s

PDP-
MOD-PEND

MODIFY PDP CONTEXT REQUEST sent

MODIFY PDP CONTEXT ACC received

Retransmission of MODIFY PDP CONTEXT REQ

T3395

8s

PDP-
INACT-PEND

DEACTIVATE PDP CONTEXT REQUEST sent

DEACTIVATE PDP CONTEXT ACC received

Retransmission of DEACTIVATE PDP CONTEXT REQ

T3397

8s

PDP-
INACT-PEND

DEACTIVATE AA PDP CONTEXT REQUEST sent

DEACTIVATE AA PDP CONTEXT ACCEPT received

Retransmission of DEACTIVATE AA PDP CONTEXT REQUEST

NOTE: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.

11.3 Timers of circuit-switched call control

Table 11.3/3GPP TS 04.08: Call control timers – MS side

+————————————————————-+

│TIM.│TIM│ STATE OF │CAUSE OF │ NORMAL │AT FIRST │AT SECOND│

│NUM.│VAL│ CALL │ START │ STOP │EXPIRY │EXPIRY │

+—-+—+———-+———+———–+———+———│

│T303│30s│ Call │CM SER RQ│ CALL PROC,│Clear the│Timer is │

│ │ │initiated │ sent │or REL COMP│call │not │

│ │ │ │ │received │ │restarted│

│ │ │ │ │ │ │ │

│T305│30s│Disconnect│ DISC │REL or DISC│REL sent.│Timer is │

│ │ │ Request │ sent │received │ │not │

│ │ │ │ │ │ │restarted│

│ │ │ │ │ │ │ │

│T308│30s│ Release │ REL │REL COMP │Retrans. │Call ref.│

│ │ │ request │ sent │or REL │RELEASE │release │

│ │ │ │ │received │restart │ │

│ │ │ │ │ │T308 │ │

│ │ │ │ │ │ │ │

│T310│30s│ Outgoing │ CALL │ALERT,CONN,│Send DISC│Timer is │

│Note│ │ call │ PROC │DISC or │ │not │

│ 1 │ │Proceeding│received │PROG rec. │ │restarted│

│ │ │ │ │ │ │ │

│T313│30s│ Connect │ CONN │CONNect │Send DISC│Timer is │

│ │ │ Request │ sent │ACKnowledge│ │not │

│ │ │ │ │received │ │restarted│

│ │ │ │ │ │ │ │

│T323│30s│ Modify │ MOD │MOD COMP │Clear │Timer is │

│ │ │ Request │ sent │or MOD REJ │the call │not │

│ │ │ │ │received │ │restarted│

│ │ │ │ │ │ │ │

│T332│30s│ Wait for│ START_CC│ CC-EST. │Clear │Timer is │

│ │ │ network │ sent │ received │the call │not │

│ │ │ info. │ │ │ │restarted│

│ │ │ │ │ │ │ │

│T335│30s│ CC-Est. │CC-EST │ RECALL │Clear │Timer is │

│ │ │ Confirmed│CONF.sent│ received │the call │not │

│ │ │ │ │ │ │restarted│

│ │ │ │ │ │ │ │

+————————————————————-+

NOTE: T310 is not started if progress indicator #1, #2, or #64 has been delivered in the CALL PROCEEDING message or in a previous PROGRESS message.

Table 11.4/3GPP TS 04.08: Call control timers – network side

+————————————————————+

│TIM.│DFT │STATE OF │CAUSE │NORMAL STOP│AT FIRST│AT SECON │

│NUM.│TIM │CALL │FOR │ │EXPIRY │EXPIRY │

│ │VAL │ │START │ │ │ │

+—-+—-+———-+——–+———–+——–+———│

│T301│Min │Call │ALERT │CONN │Clear │Timer │

│Note│180s│received │received│received │the call│is not │

│ 1 │ │ │ │ │ │restarted│

│ │ │ │ │ │ │ │

│T303│Note│Call │SETUP │CALL CONF │Clear │Timer │

│ │ 2 │present │sent │or REL COMP│the call│is not │

│ │ │ │ │received │ │restarted│

│ │ │ │ │ │ │ │

│T305│30s │Disconnect│DISC │REL or DISC│Network │Timer │

│ │ │Indication│without │received │sends │is not │

│ │ │ │progress│ │RELEASE │restarted│

│ │ │ │indic. │ │ │ │

│ │ │ │#8 sent │ │ │ │

│ │ │ │or CCBS │ │ │ │

│ │ │ │Possible│ │ │ │

│ │ │ │ │ │ │ │

│T306│30s │Disconnect│DISC │REL or DISC│Stop the│Timer │

│ │ │Indication│with │received │tone/ │is not │

│ │ │ │progress│ │announc.│restarted│

│ │ │ │indic. │ │Send REL│ │

│ │ │ │#8 sent │ │ │ │

│ │ │ │but no │ │ │ │

│ │ │ │CCBS │ │ │ │

│ │ │ │possible│ │ │ │

│ │ │ │ │ │ │ │

│T308│Note│Release │REL sent│REL COMP │Retrans.│Release │

│ │ 2 │request │ │or REL │RELEASE │call │

│ │ │ │ │received │restart │reference│

│ │ │ │ │ │T308 │ │

│ │ │ │ │ │ │ │

│T310│Note│Incoming │CALL │ALERT, CONN│Clear │Timer │

│ │ 2 │call pro- │CONF │or DISC │the call│is not │

│ │ │ceeding │received│received │ │restarted│

│ │ │ │ │ │ │ │

│T313│Note│Connect │CON sent│CON ACK │Clear │Timer │

│ │ 2 │Indication│ │received │the call│is not │

│ │ │ │ │ │ │restarted│

│ │ │ │ │ │ │ │

│T323│30s │Modify │MOD sent│ MOD COMP │Clear │Timer │

│ │ │request │ │or MOD REJ │the call│is not │

│ │ │ │ │ received │ │restarted│

│ │ │ │ │ │ │ │

│T331│Note│ CC │ CM-SERV│ START CC │Clear │Timer │

│ │ 2 │ Connec. │ PROMPT │ received │the call│is not │

│ │ │ Pending │ sent │ │ │restarted│

│ │ │ │ │ │ │ │

│T333│Note│ CC-Est. │START CC│CC-EST.CONF│Clear │Timer │

│ │ 2 │ Present │received│or REL COMP│the call│is not │

│ │ │ │ │ received │ │restarted│

│ │ │ │ │ │ │ │

│T334│Min │ CC-Est. │ RECALL │ SETUP │Clear │Timer │

│Note│ 15s│ Confirmed│ sent │ received │the call│is not │

│ 3 │ │ │ │ │ │restarted│

│ │ │ │ │ │ │ │

│T338│Note│Disconnect│ DISC │REL or DISC│stop any│Timer │

│ │ 2 │indication│ with │received │tone/ │is not │

│ │ │ │ CCBS │ │announc.│restarted│

│ │ │ │possible│ │Send REL│ │

│ │ │ │ │ │ │ │

+————————————————————+

NOTE 1: The network may already have applied an internal alerting supervision function; e.g. incorporated within call control. If such a function is known to be operating on the call, then timer T301 is not used.

NOTE 2: These time values are set by the network operator.

NOTE 3: When applied to the supplementary service CCBS, the timer T334 can either represent the recall timer T4 or the notification timer T10 (see 3GPP TS 03.93). Thus the timer T334 can take two different values. 3GPP TS 03.93 defines the range of these values.

Annex A (informative):
Example of subaddress information element coding

This annex is informative.

This annex gives an example of how the Called Party Subaddress IE is encoded to carry subaddress digits that use IA5 characters. This example is also applicable to the Calling Party Subaddress IE.

8 7 6 5 4 3 2 1 octet

+—————————————————–+

│ 0 │ 1 1 0 1 1 0 1 │ 1

│ │ called party subaddress IEI │

+—————————————————–│

│ 0 0 0 0 0 1 1 1 │ 2

│ Length │

+—————————————————–│

│ 1 │ 0 0 0 │ X │ 0 0 0 │ 3

│ not │ NSAP │odd/ev│ │

│ ext │(X.213/ISO 8348 AD2)│note 1│ note 2 │

+————————–+————————–│

│ 0 1 0 1 0 0 0 0 │ 4

│ AFI (note 3) │

+————————–+————————–│

│ IA5 Character (note 4) │ 5

+————————–+————————–│

│ IA5 Character (note 4) │ 6

+————————–+————————–│

. .

. .

+————————–+————————–│

│ IA5 Character (note 4) │ 9,

+—————————————————–+ note 5

NOTE 1: The value of this bit has no significance when the type of subaddress is "NSAP".

NOTE 2: These bits are spare.

NOTE 3: The Authority and Format Identifier code 50 (in BCD) indicates that the subaddress consists of IA5 characters (see ISO standard 8348 AD2).

NOTE 4: IA5 character as defined in ITU-T Recommendation T.50/ISO 646 and then encoded into two semi-octets according to the "preferred binary encoding" defined in X.213/ISO 8348 AD2. (Each character is converted into a number in the range 32 to 127 using the ISO 646 encoding with zero parity and the parity bit in the most significant position. This number is then reduced by 32 to give a new number in the range 0 to 95. The new number is then treated as a pair of decimal digits with the value of each digit being encoded in a semi-octet.)

NOTE 5: the number of IA5 characters in the subaddress may vary, subject to an upper limit of 19 IA5 characters.

Annex B (normative):
Compatibility checking

This annex is normative.