5 Requirements

3GPP44.013Performance requirements on the mobile radio interfaceRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1 General requirements

5.1.1 Response to layer 3 message

The requirements of subclause 5.1.1 apply if there are no specific requirements for a layer 3 message in other parts of clause 5.

If the last timeslot of the message block containing a network command occurs at time T, then the MS shall be ready to transmit the response before time T + 500 ms.

5.1.2 Response to an erroneous layer 3 message

If the last timeslot of the message block containing an erroneous RR, MM or CC message occurs at time T and if 3GPP TS 24.008 [4] and 3GPP TS 44.018 [4a] requires a status message to be returned to the network then the MS shall be ready to transmit the RR-STATUS or MM-STATUS or STATUS message before T + 500 ms.

5.2 Layer 3 Radio Resource signalling

5.2.0 Paging

If access to the network is allowed and the MS has been camped on a suitable cell for at least 2 s and if the last timeslot of the message block containing a PAGING REQUEST message addressing the MS occurs at time T, then the MS shall be ready to transmit the CHANNEL REQUEST message before T + 0,7 s.

5.2.1 Paging and cell reselection after channel release

If the last timeslot of the message block containing a CHANNEL RELEASE message occurs at time T the MS shall respond to PAGING REQUEST messages sent later than T + 1,0 s.

5.2.2 Paging commands and immediate assignment rejection (Timer T3122)

If the last timeslot of the message block containing an IMMEDIATE ASSIGNMENT REJECT message is sent at time T and contains a Wait Indication of W seconds then the MS shall at least respond to PAGING REQUEST messages sent later than T + (W + 1) s.

5.2.3 Immediate assignment (Timer T3101)

If the last timeslot of the message block containing an IMMEDIATE ASSIGNMENT (or IMMEDIATE ASSIGNMENT EXTENDED) message is transmitted at time T then, the MS shall be ready to transmit the SABM frame with its information field before T + 25 ms. This requirement shall apply for assignment to TCH/F, TCH/H and SDCCH.

5.2.4 Channel assignment

If the last timeslot of the message block containing an ASSIGNMENT COMMAND occurs at time T, then the MS shall be ready to transmit the ASSIGNMENT COMPLETE message before T + 600 ms.

If the last timeslot of the message block containing an ASSIGNMENT COMMAND occurs at time T and this ASSIGNMENT COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the ASSIGNMENT FAILURE message on the old channel before T + 2 s.

If the last timeslot of the message block containing an ASSIGNMENT COMMAND occurs at time T and this ASSIGNMENT COMMAND is such that the MS shall not attempt to establish a layer 2 link on the new channel, then the MS shall be ready to transmit any ASSIGNMENT FAILURE message on the old channel before T + 500 ms.

5.2.5 Channel mode modify

If the last timeslot of the message block containing a CHANNEL MODE MODIFY message occurs at time T, then the MS shall be ready to transmit the CHANNEL MODE MODIFY ACKNOWLEDGE message before T + 300 ms. In the case that the call is a voice group or voice broadcast call the MS shall be ready to transmit the CHANNEL MODE ACKNOWLEDGE message before T + 50 ms.

5.2.6 Handover access

5.2.6.1 Finely, pseudo and pre synchronized cases

If the last timeslot of the message block containing a HANDOVER COMMAND message to a full rate TCH occurs at time T, then the MS shall be ready to transmit the HANDOVER COMPLETE message before T + 650 ms.

If the last timeslot of the message block containing a HANDOVER COMMAND message to a half rate TCH occurs at time T, then the MS shall be ready to transmit the HANDOVER COMPLETE message before T + 900 ms.

If the last timeslot of the message block containing a HANDOVER COMMAND message to an SDCCH occurs at time T, then the MS shall be ready to transmit the HANDOVER COMPLETE message before T + 1,5 s.

If the last timeslot of the message block containing a HANDOVER COMMAND to a full rate TCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old full rate TCH before T + 2 s.

If the last timeslot of the message block containing a HANDOVER COMMAND to a half rate TCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old half rate TCH before T + 3 s.

If the last timeslot of the message block containing a HANDOVER COMMAND to an SDCCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old SDCCH before T + 5 s.

If the last timeslot of the message block containing a HANDOVER COMMAND occurs at time T and this HANDOVER COMMAND is such that the MS shall not attempt to establish a layer 2 link on the new channel, then the MS shall be ready to transmit any HANDOVER FAILURE message on the old channel before T + 500 ms.

5.2.6.2 Non synchronized case

If the last timeslot of the message block containing the (one and only) PHYSICAL INFORMATION message occurs at time T, then on a full rate TCH the MS shall be ready to transmit the HANDOVER COMPLETE message before T + 500 ms.

If the last timeslot of the message block containing the (one and only) PHYSICAL INFORMATION message occurs at time T, then on a half rate TCH the MS shall be ready to transmit the HANDOVER COMPLETE message before T + 750 ms.

If the last timeslot of the message block containing the (one and only) PHYSICAL INFORMATION message occurs at time T, then on an SDCCH the MS shall be ready to transmit the HANDOVER COMPLETE message before T + 1,5 s.

If the last timeslot of the message block containing a HANDOVER COMMAND to either a full rate or a half rate TCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old TCH before T + 1,1 s.

5.2.7 Encryption

If the last timeslot of the message block containing a CIPHERING MODE COMMAND message occurs at time T, then the MS shall be ready to transmit the CIPHERING MODE COMPLETE message before T + 500 ms.

5.2.8 Classmark change

While the MS has an active RR connection, any change in the MS’s capabilities that are indicated in the Mobile Station Classmark 2 or 3 IEs shall cause a CLASSMARK CHANGE message to be sent to the network. The MS shall be ready to transmit the CLASSMARK CHANGE message not later than 1 second after the change in capabilities.

5.2.9 Classmark interrogation

If the last timeslot of the message block containing a CLASSMARK ENQUIRY message occurs at time T, then the MS shall be ready to transmit the CLASSMARK CHANGE message before T + 300 ms.

5.2.10 Release (Timer T3110)

If the last timeslot of the message block carrying the CHANNEL RELEASE message occurs at time T, then the MS shall cease transmissions on all channels before T + 500 ms.

5.2.11 Early sending of the CLASSMARK CHANGE message

During a contention resolution procedure, if the last timeslot of the block containing a Layer 2 UA frame, occurs at time T, then the MS shall be ready to transmit the CLASSMARK CHANGE message, if applicable (see 3GPP TS 44.006 [3] and 3GPP TS 44.018 [4a]), before T + 40 ms.

5.3 Layer 3 Mobility Management signalling

5.3.1 Periodic location updating timer

When the T3212 time-out value is set to the non-zero value P and the last timeslot of the message block containing a CHANNEL RELEASE message is transmitted at time T then, assuming the next event shall be the periodic location update, the next CHANNEL REQUEST message shall be transmitted between time T + P decihours – 15 seconds and time T + P decihours + 15 s.

5.3.2 Identification

If the last timeslot of the message block containing an IDENTITY REQUEST message occurs at time T, then the MS shall be ready to transmit the IDENTITY RESPONSE message before T + 600 ms. This requirement assumes that the ME has to wait less than 100 ms to obtain any necessary responses from the SIM.

5.3.3 Authentication

If the last timeslot of the message block containing an AUTHENTICATION REQUEST message occurs at time T, then the MS shall be ready to transmit the AUTHENTICATION RESPONSE message before T + 1 s. This requirement assumes that the ME has to wait less than 500 ms to obtain any necessary responses from the SIM.

5.3.4 T3240 expiry

If the last timeslot of the message block containing an AUTHENTICATION REJECT message; or a LOCATION UPDATING ACCEPT message (without a Follow On Proceed IE); or a LOCATION UPDATING REJECT message; or a CM SERVICE REJECT message (and no other MM connection is active) occurs at time T, and the network does not send a CHANNEL RELEASE message but does maintain the RR connection, then the MS shall cease transmission on all channels before T + 12 s.

5.3.5 TMSI reallocation

If the last timeslot of the message block containing either a TMSI REALLOCATION COMMAND, or a LOCATION UPDATING ACCEPT with a TMSI in the Mobile Identity IE, occurs at time T, then the MS shall be ready to transmit the TMSI REALLOCATION COMPLETE message before T + 500 ms.

5.3.6 IMSI detach

The requirements of this subclause only apply if the network indicates on the BCCH that IMSI detach shall be used.

If it is possible to switch the mobile off, or if it is possible to remove the SIM whilst the mobile is powered on, then when such an action is performed in idle mode at time T, the first CHANNEL REQUEST message for the IMSI Detach procedure shall be transmitted before T + 2 s.

If it is possible to switch the mobile off, or if it is possible to remove the SIM whilst the mobile is powered on, then when such an action is performed in the Active (U10) state of a call at time T, the MS shall be ready to transmit the IMSI DETACH INDICATION message before T + 1 s.

If the last timeslot in which the IMSI DETACH message is sent occurs at time T then the MS shall cease transmission on all channels before T + 6 s.

5.3.7 Location updating with random access failure

In an environment with only one suitable cell (see 3GPP TS 43.022 [2] for the definition of a "suitable cell"), if a location updating attempt suffers a random access failure (see 3GPP TS 44.018 [4a]) with the last CHANNEL REQUEST message being transmitted at time T, then the first re-attempt shall result in a CHANNEL REQUEST message being transmitted before T + 15 s.

5.3.8 Follow on call

If the last timeslot of the message block containing a LOCATION UPDATING ACCEPT message with a Follow on Proceed IE occurs at time T and the MS has a CM application request pending, then the MS shall be ready to the CM SERVICE REQUEST message before T + 500 ms.

5.4 Layer 3 Call Control signalling

5.4.1 Time to send SETUP message

In the case of a MS originated call, if the last timeslot of the message block containing a CM SERVICE ACCEPT message occurs at time T then the MS shall be ready to transmit the SETUP message before T + 500 ms. In the case that the call is a voice group or voice broadcast call the MS shall be ready to transmit the SETUP message before T + 50 ms.

In the case of a MS originated call, if the last timeslot of the message block containing a CIPHERING MODE COMMAND message occurs at time T, then the MS shall be ready to transmit the SETUP message before T + 750 ms. In the case that the call is a voice group or voice broadcast call the MS shall be ready to transmit the SETUP message before T + 50 ms.

In the case of a MS originated call, if the last timeslot of the message block containing a MM GO ON message occurs at time T, then the MS shall be ready to transmit the SETUP message before T + 50 ms. In the case that the call is a voice group or voice broadcast call the MS shall be ready to transmit the SETUP message before T + 50 ms.

5.4.2 Response times to CC messages

For the commands and responses listed in table 1, the following shall apply:

– if the last timeslot of the message block in which the "command" message is sent occurs at time T, then the MS shall be ready to transmit any one of the possible "responses" before time T + W.

In table 1, the second figure, where provided, represents the time that must be achieved in the case of a voice group or voice broadcast call.

Table 1: Call Control message response times

command	response(s)	W
(network –> MS)	(MS –> network)
CONNECT	CONNECT ACKNOWLEDGE	500 ms, 50 ms
SETUP	(as first response message)
	CALL CONFIRMED or
	ALERTING or
	CONNECT or
	RELEASE COMPLETE	1 s, 50 ms
SETUP	(as second response message)
	ALERTING or
	CONNECT or
	DISCONNECT	2 s
SETUP	(as third response message)
	CONNECT	no requirement
DISCONNECT	RELEASE	500 ms
RELEASE	RELEASE COMPLETE	500 ms
STATUS ENQUIRY	STATUS	500 ms

5.4.3 User alerting

If the MS has some form of user alerting and if for a mobile terminating call the MS sends the ALERTING message before the CONNECT message then:

– if the last timeslot carrying a SETUP message containing the Signal IE occurs at time T, the user alerting shall be initiated before time T + 1 s.

5.4.4 Call establishment

If the MS’s service indication indicates that service is available (see 3GPP TS 43.022 [2]) and after the entry of suitable number digits, then if the "SEND" or "Emergency SEND" function on the MS is activated at time T, the first CHANNEL REQUEST message shall be transmitted before time T + 2 s.

5.4.5 Call reestablishment

The requirement of this subclause relates to the following environment and conditions:

– the MS is the active (U10) state of a speech call on cell A;

– the NCC of cell B is indicated as permitted in the SYSTEM INFORMATION messages of cell A, but cell B may be in a different location area;

– cells A and B are the only cells which have C1 > 0 (see 3GPP TS 45.008 [7]);

– cell B is in at least the BA(SACCH) list of cell A;

– cell B allows call reestablishment.

If the transmissions from cell A are disrupted such that the MS shall detect a radio link failure at time T then the MS shall transmit a CHANNEL REQUEST message to cell B before time T + 3 s.

5.4.6 In call modification

For network originated in call modification, if the MS transmits the last timeslot of the message block containing the MODIFY message at time T then the MS shall be ready to transmit the MODIFY COMPLETE message before time T + 500 ms.

5.4.7 DTMF

This requirement applies when the MS’s DTMF function is not disabled.

When the first number key is pressed on the MS during the Active (U10) state of a call at time T, then the MS shall be ready to transmit the START DTMF message before time T + 500 ms.

5.5 Supplementary service signalling

5.5.1 Advice of Charge Charging (AoCC)

The following requirements only apply to mobile stations that support the Advice of Charge Charging supplementary service defined in 3GPP TS 24.086 [5].

If the last timeslot of the message block in which a Call Control message with a Facility information element containing the operation ForwardChargeAdvice with the SS code set to AoCC occurs at time T, then the MS shall be ready to transmit a message with a Facility information element containing a Return result with the same Invoke ID before time T + 1 s.

5.6 Short Message Services Point-to-Point

These requirements relate to signalling using SAPI 3.

5.6.1 CP-DATA

If the last timeslot of the message block containing a CP-DATA message occurs at time T, then the MS shall be ready to transmit the CP-ACK message before T + 500 ms.

5.6.2 RP-DATA

If the last timeslot of the message block containing a RP-DATA message which will be stored in the ME and for which the ME has storage room available occurs at time T, then the MS shall be ready to transmit the RP-ACK message before time T + 1 s.

If the last timeslot of the message block containing a RP-DATA message whose destination is the SIM and for which the SIM has storage room available occurs at time T, then the ME shall start to send the short message on the ME – SIM interface before time T + 250 ms.

If the last timeslot of the message block containing a RP-DATA message whose destination is the TE occurs at time T, then the ME shall start to send the short message on the ME – TE interface before time T + 250 ms.

In the case of a short message supplied to the SIM, if the response from the SIM that triggers the sending of the RP-ACK message is completed on the SIM-ME interface at time T, then the MS shall be ready to transmit the RP-ACK message before time T + 250 ms.

In the case of a short message supplied to the TE, if the response from the TE that triggers the sending of the RP-ACK message is completed on the TE-ME interface at time T, then the MS shall be ready to transmit the RP-ACK message before time T + 250 ms.

Annex A (informative):
Change History

SMG No.	TDoc. No.	CR. No.	Section affected	New version	Subject/Comments
SMG#14				4.0.2	ETSI Publication
SMG#15	414/95	A002 A003		4.1.0	Performance requirement on early sending of the CLASSMARK CHANGE message Erroneous release time reqirement
SMG#16	584/95	001 002 003		4.2.0	PE Comments
SMG#20				5.0.2	Release 1996 version
SMG#21	054/97	A006		5.1.1	CR on GSM 04.13 on Time response to RP-DATA with an RP-ACK
SMG#27				6.0.0	Release 1997 version
SMG#28				6.0.1	ETSI Publication
SMG#29				7.0.0	Specification version 6.0.1 upgrade to Release 1998 version 7.0.0
				7.0.1	Version update to 7.0.1 for Publication
SMG#31				8.0.0	Specification upgrade to Release 1999
				8.0.1	Version update to 8.0.1 for Publication
CN#11			3GPP TS 44.013	4.0.0	Release 4 version after CN#11
NP-16	NP-020224	001	3GPP TS 44.013	4.1.0	Various clean-up of wrong references, eg towards 44.018
NP-16			3GPP TS 44.013	5.0.0	Plenary decision to make this TS also for Rel-5.
NP-26			3GPP TS 44.013	6.0.0	Plenary decision to make this TS also for Rel-6.
				7.0.0	Plenary decision to make this TS also for Rel-7.
CP-42				8.0.0	Plenary decision to make this TS also for Rel-8.
CP-46				9.0.0	Plenary decision to make this TS also for Rel-9.
CP-51				10.0.0	Plenary decision to make this TS also for Rel-10.
CP-57				11.0.0	Plenary decision to make this TS also for Rel-11.
CP-65				12.0.0	Plenary decision to make this TS also for Rel-12.
CP-70				13.0.0	Upgrade to Rel-13

Change history
Date	Meeting	TDoc	CR	Rev	Cat	Subject/Comment	New version
2017-03	SA#75					Upgrade to Rel-14	14.0.0
2018-06	SA#80					Upgrade to Rel-15	15.0.0
2020-06	SA#88e					Upgrade to Rel-16	16.0.0
2022-04	SA#95e	–	–	–	–	Update to Rel-17 version (MCC)	17.0.0