13.5 UE RRC Procedure Performance

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

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

This subclause defines the performance requirements related to RRC procedures in the UE. Where the total delay is impacted by processing of variable length on the physical layer (e.g. physical layer synchronisation), references to appropriate specifications are given.

13.5.1 Definitions

The following definitions of N1 and N2 are valid only for this UE RRC Procedure Performance specification.

N1 = upper limit on the time required to execute modifications in UE after the reception of a UTRAN -> UE message has been completed. Where applicable (e.g. the physical layer transmission is impacted), the changes shall be adopted in the beginning of the next TTI starting after N1. N1 is specified as a multiple of 10 ms.

N2 = number of 10 ms radio frames from end of reception of UTRAN -> UE message on UE physical layer before the transmission of the UE -> UTRAN response message must be ready to start on a transport channel with no access delay other than the TTI alignment (e.g. DCH, therefore excluding delays caused by RACH procedure etc). The UE response message transmission from the physical layer shall begin at the latest (N2*10)+TTI ms after completion of the reception of the last TTI carrying the triggering UTRAN -> UE message. When Target State is CELL_DCH, the UE response message transmission from the physical layer may be additionally delayed by the value of IE "SRB delay".

N1 and N2 are independent (e.g. N2-N1 is not restricted to being less than or equal to 10ms).

13.5.2 RRC procedure performance values

NOTE: Times indicated in the table do not include cell reselection.

Procedure title:	UTRAN -> UE	UE -> UTRAN	N1	N2	Notes
RRC Connection Management Procedures
Broadcast of system information	SYSTEM INFORMATION				N2 is not applicable for any system information messages, because there is no response message from the UE.
Master Information Block	SYSTEM INFORMATION		5	NA	No system information data shall be lost due to processing of a MIB received with no detectable errors. This means that the UE shall buffer all system information data received after the MIB until the data can be processed according to the information in the MIB, unless the MIB was received erroneously.
System Information Block type 1	SYSTEM INFORMATION		10	NA
System Information Block type 2	SYSTEM INFORMATION		10	NA
System Information Block type 3	SYSTEM INFORMATION		10	NA
System Information Block type 4	SYSTEM INFORMATION		10	NA
System Information Block type 5 or System Information Block type 5bis	SYSTEM INFORMATION		10	NA
System Information Block type 6	SYSTEM INFORMATION		10	NA
System Information Block type 7	SYSTEM INFORMATION		5	NA
System Information Block type 11 or System Information Block type 11bis	SYSTEM INFORMATION		10	NA
System Information Block type 11ter	SYSTEM INFORMATION		10	NA
System Information Block type 12	SYSTEM INFORMATION		10	NA
System Information Block type 13	SYSTEM INFORMATION		10	NA
System Information Block type 14	SYSTEM INFORMATION		10	NA
System Information Block type 15 or 15bis or 15.1 or 15.1bis or 15.1ter or 15.2 or 15.2bis or 15.2ter or 15.3 or 15.3bis or 15.4 or 15.5 or 15.6 or 15.7 or 15.8	SYSTEM INFORMATION		10	NA
System Information Block type 16	SYSTEM INFORMATION		10	NA
System Information Block type 18	SYSTEM INFORMATION		10	NA
System Information Block type 19	SYSTEM INFORMATION		10	NA
System Information Block type 20	SYSTEM INFORMATION		10	NA
System Information Block type 21	SYSTEM INFORMATION		10	NA
System Information Block type 22	SYSTEM INFORMATION		10	NA
System Information Block type 23	SYSTEM INFORMATION		10	NA
System Information Block type 24	SYSTEM INFORMATION		5	NA
System Information Block type 25	SYSTEM INFORMATION		5	NA
System Information Change Indication	SYSTEM INFORMATION		10	NA
RRC connection establishment Target state CELL_DCH	RRC CONNECTION SETUP	RRC CONNECTION SETUP COMPLETE	10	NA	N1 measures time to the start of tx / rx on DPCH. N2 cannot be specified, because RRC CONNECTION SETUP COMPLETE message is transmitted only after physical layer synchronisation, which also depends on the Node B. The performance of the physical layer synchronisation procedure is specified in [19] and [20]
RRC connection establishment Target state CELL_FACH	RRC CONNECTION SETUP	RRC CONNECTION SETUP COMPLETE	10	11	N1 and N2 applicable as defined (N2 can be tested from the initiation of the power ramp on RACH).
RRC connection release From CELL_DCH state	RRC CONNECTION RELEASE	RRC CONNECTION RELEASE COMPLETE	5	8	N1 sets the requirement for the time from the completion of the last repetition of the RRC CONNECTION RELEASE COMPLETE message to the release of the physical channel. N2 sets the requirement from the end of successful reception of the RRC CONNECTION RELEASE message to the start of the first transmission of the RRC CONNECTION RELEASE COMPLETE message.
RRC connection release From CELL_FACH state	RRC CONNECTION RELEASE	RRC CONNECTION RELEASE COMPLETE	NA	11	N1 represents UE internal configuration that cannot be externally observed.
Paging	PAGING TYPE 1	CELL UPDATE	10	11+T	T is the repetition period of SIB7 (applicable for FDD) and SIB14 (applicable for TDD)
UE capability enquiry	UE CAPABILITY ENQUIRY	UE CAPABILITY INFORMATION	NA	8	N1 is not applicable because the UE configuration does not change.
Security mode control	SECURITY MODE COMMAND	SECURITY MODE COMPLETE	5	8
Signalling connection release procedure	SIGNALLING CONNECTION RELEASE		5	NA	N2 is not applicable because there is no response message.
Counter check	COUNTER CHECK	COUNTER CHECK RESPONSE	NA	8	N1 is not applicable because the UE configuration does not change.
ETWS Primary Notification with Security	ETWS PRIMARY NOTIFICATION WITH SECURITY		10	NA	N2 is not applicable because there is no response message.
Radio Bearer control procedures
Radio bearer establishment Target state CELL_DCH	RADIO BEARER SETUP	RADIO BEARER SETUP COMPLETE / FAILURE	10	NA	N2 cannot be specified, because the RADIO BEARER SETUP COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B.
Radio bearer establishment From state CELL_FACH to state CELL_FACH	RADIO BEARER SETUP	RADIO BEARER SETUP COMPLETE / FAILURE	10	11
Radio bearer establishment From CELL_DCH to CELL_FACH	RADIO BEARER SETUP	RADIO BEARER SETUP COMPLETE	NA	NA	N1 and N2 cannot be specified, because UE need to read SIBs on BCH before sending RADIO BEARER SETUP COMPLETE
Radio bearer reconfiguration Target state CELL_DCH	RADIO BEARER RECONFIGURATION	RADIO BEARER RECONFIGURATION COMPLETE / FAILURE	5 or 10	NA	N2 cannot be specified, because the RADIO BEARER RECONFIGURATION COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B. NOTE 1
Radio bearer reconfiguration From Idle Mode and state CELL_FACH to state CELL_DCH	RADIO BEARER RECONFIGURATION	RADIO BEARER RECONFIGURATION COMPLETE / FAILURE	10	11	This requirement applies when the UE has a common E-DCH resource and is not required to perform any synchronization.
Radio bearer reconfiguration From state CELL_FACH to state CELL_FACH	RADIO BEARER RECONFIGURATION	RADIO BEARER RECONFIGURATION COMPLETE / FAILURE	10	11
Radio bearer reconfiguration From state CELL_DCH to state CELL_FACH	RADIO BEARER RECONFIGURATION	RADIO BEARER RECONFIGURATION COMPLETE	NA	NA	N1 and N2 cannot be specified, because UE need to read SIBs on BCH before sending RADIO BEARER RECONFIGURATION COMPLETE
Radio bearer release Target state CELL_DCH	RADIO BEARER RELEASE	RADIO BEARER RELEASE COMPLETE / FAILURE	10	11
Radio bearer release From state CELL_FACH to state CELL_FACH	RADIO BEARER RELEASE	RADIO BEARER RELEASE COMPLETE / FAILURE	10	11
Radio bearer release From state CELL_DCH to state CELL_FACH	RADIO BEARER RELEASE	RADIO BEARER RELEASE COMPLETE	NA	NA	N1 and N2 cannot be specified, because UE need to read SIBs on BCH before sending RADIO BEARER RECONFIGURATION COMPLETE
Transport channel reconfiguration Target state CELL_DCH	TRANSPORT CHANNEL RECONFIGURATION	TRANSPORT CHANNEL RECONFIGURATION COMPLETE / FAILURE	5 or 10	NA	N2 cannot be specified, because the TRANSPORT CHANNEL RECONFIGURATION COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B. NOTE 1
Transport channel reconfiguration From state CELL_FACH to state CELL_FACH	TRANSPORT CHANNEL RECONFIGURATION	TRANSPORT CHANNEL RECONFIGURATION COMPLETE / FAILURE	10	11
Transport channel reconfiguration From state CELL_DCH to state CELL_FACH	TRANSPORT CHANNEL RECONFIGURATION	TRANSPORT CHANNEL RECONFIGURATION COMPLETE	NA	NA	N1 and N2 cannot be specified, because UE need to read SIBs on BCH before sending TRANSPORT CHANNEL RECONFIGURATION COMPLETE
Transport format combination control AM or UM RLC mode	TRANSPORT FORMAT COMBINATION CONTROL	TRANSPORT FORMAT COMBINATION CONTROL FAILURE	5	8
Transport format combination control Transparent mode	TRANSPORT FORMAT COMBINATION CONTROL		5	NA	N2 is not applicable because no response message is defined.
Physical channel reconfiguration Target state CELL_DCH	PHYSICAL CHANNEL RECONFIGURATION	PHYSICAL CHANNEL RECONFIGURATION COMPLETE / FAILURE	5 or 8	NA	N2 cannot be specified, because the PHYSICAL CHANNEL RECONFIGURATION COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B. NOTE 1
Physical channel reconfiguration From state CELL_FACH to state CELL_FACH	PHYSICAL CHANNEL RECONFIGURATION	PHYSICAL CHANNEL RECONFIGURATION COMPLETE / FAILURE	8	9
Physical channel reconfiguration From state CELL_DCH to state CELL_FACH	PHYSICAL CHANNEL RECONFIGURATION	PHYSICAL CHANNEL RECONFIGURATION COMPLETE	NA	NA	N1 and N2 cannot be specified, because UE need to read SIBs on BCH before sending PHYSICAL CHANNEL RECONFIGURATION COMPLETE
Physical Shared Channel Allocation [TDD only]	PHYSICAL SHARED CHANNEL ALLOCATION		5	NA	N2 is not applicable because no response message is defined.
Uplink Physical Channel Control [TDD only]	UPLINK PHYSICAL CHANNEL CONTROL		8	NA	Requirements for outer loop and timing advance adjustments are defined in [22] and [20]. N2 is not applicable because there is no response message.
RRC connection mobility procedures
Cell update	CELL UPDATE CONFIRM	UTRAN MOBILITY INFORMATION CONFIRM	5	8
		PHYSICAL CHANNEL RECONFIGURATION COMPLETE Target state CELL_FACH	8	9
		PHYSICAL CHANNEL RECONFIGURATION COMPLETE Target state CELL_DCH	8	NA	N2 cannot be specified, because the PHYSICAL CHANNEL RECONFIGURATION COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B.
		TRANSPORT CHANNEL RECONFIGURATION COMPLETE Target state CELL_FACH	10	11
		TRANSPORT CHANNEL RECONFIGURATION COMPLETE Target state CELL_DCH	10	NA	N2 cannot be specified, because the PHYSICAL CHANNEL RECONFIGURATION COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B.
		RADIO BEARER RECONFIGURATION COMPLETE Target state CELL_FACH	10	11
		RADIO BEARER RECONFIGURATION COMPLETE Target state CELL_DCH	10	NA	N2 cannot be specified, because the PHYSICAL CHANNEL RECONFIGURATION COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B.
		RADIO BEARER RELEASE COMPLETE Target state CELL_DCH	10	11
URA update	URA UPDATE CONFIRM	UTRAN MOBILITY INFORMATION CONFIRM	5	8
UTRAN mobility information	UTRAN MOBILITY INFORMATION	UTRAN MOBILITY INFORMATION CONFIRM / FAILURE	5	8
Active set update	ACTIVE SET UPDATE	ACTIVE SET UPDATE COMPLETE / FAILURE	NA	5	The requirements on UE combining and power control performance for both UL and DL are specified by RAN WG4 in [21] and [19]. Also in case of branch addition the COMPLETE / FAILURE message is transmitted without waiting for the new branch to stabilise, therefore N2 is specified.
Inter-RAT handover to UTRAN	HANDOVER TO UTRAN COMMAND (other system)	HANDOVER TO UTRAN COMPLETE	NA	NA	The performance of this procedure is specified in 3GPP TS 45.010 in case of handover from GSM and 3GPP TS 36.133 in case of handover from E-UTRA.
Inter-RAT handover from UTRAN	HANDOVER FROM UTRAN COMMAND	HANDOVER FROM UTRAN FAILURE	NA	NA	The performance of this procedure is specified in [19] and [20].
Measurement procedures
Measurement control	MEASUREMENT CONTROL	MEASUREMENT CONTROL FAILURE	5	8	Response to measurement inquiry depends on physical layer measurement. Response time is defined in [19] and [20]. N1 and N2 only define the processing of the message.
UE INFORMATION
UE INFORMATION	UE INFORMATION REQUEST	UE INFORMATION RESPONSE	5	8

NOTE 1: The lower value applies when the UE is ordered to do a serving HS-DSCH cell change, changing no other information than contained in the IE "H-RNTI", the IE "Downlink HS-PDSCH information", the IE "Uplink DPCH power control info" and/or the IE "Serving HS-DSCH radio link indicator" (FDD only).