5.3.3 RRC connection establishment

36.3313GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Protocol specificationRadio Resource Control (RRC)Release 17TS

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

5.3.3.1 General

Figure 5.3.3.1-1: RRC connection establishment, successful

Figure 5.3.3.1-2: RRC connection establishment, network reject

Figure 5.3.3.1-3: RRC connection resume (suspended RRC connection or RRC_INACTIVE), or UP-EDT fallback or fallback from UP transmission using PUR to RRC connection resume, successful

Figure 5.3.3.1-4: RRC connection resume (suspended RRC connection or RRC_INACTIVE) or UP-EDT fallback or fallback from UP transmission using PUR to RRC connection establishment, successful

Figure 5.3.3.1-5: RRC connection resume or UP-EDT or UP transmission using PUR, network reject (suspended RRC connection or RRC_INACTIVE) or release (suspended RRC connection)

Figure 5.3.3.1-6: RRC connection resume (RRC_INACTIVE), network release or suspend or UP-EDT or UP transmission using PUR, successful

Figure 5.3.3.1-7: CP-EDT or CP transmission using PUR, successful

Figure 5.3.3.1-7a: CP transmission using PUR, successful

Figure 5.3.3.1-8: CP-EDT fallback or fallback from CP transmission using PUR to RRC connection establishment, successful

Figure 5.3.3.1-9: CP-EDT or CP transmission using PUR, network reject

The purpose of this procedure is to establish an RRC connection, to resume a suspended RRC connection, to move the UE from RRC_INACTIVE to RRC_CONNECTED, to perform EDT or to perform transmission using PUR. RRC connection establishment involves SRB1 (and SRB1bis for NB-IoT) establishment. The procedure is also used to transfer the initial NAS dedicated information/ message from the UE to E-UTRAN.

E-UTRAN applies the procedure as follows:

– When establishing an RRC connection:

– to establish SRB1 and, for NB-IoT, SRB1bis;

– When resuming an RRC connection from a suspended RRC connection or from RRC_INACTIVE:

– to restore the AS configuration from a stored context including resuming SRB(s) and DRB(s);

– When performing EDT;

– When performing transmission using PUR.

5.3.3.1a Conditions for establishing RRC Connection for sidelink communication/ discovery/ V2X sidelink communication/ NR sidelink communication

For sidelink communication an RRC connection is initiated only in the following case:

1> if configured by upper layers to transmit non-relay related sidelink communication and related data is available for transmission:

2> if SystemInformationBlockType18 is broadcast by the cell on which the UE camps; and if the valid version of SystemInformationBlockType18 does not include commTxPoolNormalCommon;

1> if configured by upper layers to transmit relay related sidelink communication:

2> if the UE is acting as sidelink relay UE; and if SystemInformationBlockType18 is broadcast by the cell on which the UE camps; or

2> if the UE has a selected sidelink relay UE; and if the sidelink remote UE threshold conditions as specified in 5.10.11.5 are met and if SystemInformationBlockType18 is broadcast by the cell on which the UE camps; and if the valid version of SystemInformationBlockType18 does not include commTxPoolNormalCommon or commTxAllowRelayCommon;

For V2X sidelink communication an RRC connection is initiated only in the following case:

1> if configured by upper layers to transmit non-P2X related V2X sidelink communication and related data is available for transmission:

2> if the frequency on which the UE is configured to transmit non-P2X related V2X sidelink communication concerns the camped frequency; and if SystemInformationBlockType21 is broadcast by the cell on which the UE camps; and if the valid version of SystemInformationBlockType21 includes sl-V2X-ConfigCommon; and sl-V2X-ConfigCommon does not include v2x-CommTxPoolNormalCommon; or

2> if the frequency on which the UE is configured to transmit non-P2X related V2X sidelink communication is included in v2x-InterFreqInfoList within SystemInformationBlockType21 or SystemInformationBlockType26 broadcast by the cell on which the UE camps; and if neither the valid version of SystemInformationBlockType21 nor that of SystemInformationBlockType26 includes v2x-CommTxPoolNormal for the concerned frequency;

1> if configured by upper layers to transmit P2X related V2X sidelink communication and related data is available for transmission:

2> if the frequency on which the UE is configured to transmit P2X related V2X sidelink communication concerns the camped frequency; and if SystemInformationBlockType21 is broadcast by the cell on which the UE camps; and if the valid version of SystemInformationBlockType21 includes sl-V2X-ConfigCommon; and sl-V2X-ConfigCommon does not include p2x-CommTxPoolNormalCommon; or

2> if the frequency on which the UE is configured to transmit P2X related V2X sidelink communication is included in v2x-InterFreqInfoList within SystemInformationBlockType21 or SystemInformationBlockType26 broadcast by the cell on which the UE camps; and if neither the valid version of SystemInformationBlockType21 nor that of SystemInformationBlockType26 includes p2x-CommTxPoolNormal for the concerned frequency;

For NR sidelink communication an RRC connection is initiated only when the conditions for NR sidelink communication specified in clause 5.3.3.1a of TS 38.331 [82] are met;

NOTE 1: SIB12 specified in clause 5.3.3.1a of TS 38.331 is provided in SystemInformationBlockType28.

For sidelink discovery an RRC connection is initiated only in the following case:

1> if configured by upper layers to transmit non-PS related sidelink discovery announcements:

2> if the frequency on which the UE is configured to transmit non-PS related sidelink discovery announcements concerns the camped frequency; and SystemInformationBlockType19 of the cell on which the UE camps does not include discTxPoolCommon-r12; or

2> if the frequency on which the UE is configured to transmit non-PS related sidelink discovery announcements is included in discInterFreqList in SystemInformationBlockType19 broadcast by the cell on which the UE camps, with discTxResourcesInterFreq included within discResourcesNonPS and set to requestDedicated;

1> if configured by upper layers to transmit non-relay PS related sidelink discovery announcements:

2> if the frequency on which the UE is configured to transmit non-relay PS related sidelink discovery announcements concerns the camped frequency; and SystemInformationBlockType19 of the cell on which the UE camps includes discConfigPS but does not include discTxPoolPS-Common; or

2> if the frequency on which the UE is configured to transmit non-relay PS related sidelink discovery announcements (e.g. group member discovery) is included in discInterFreqList in SystemInformationBlockType19 broadcast by the cell on which the UE camps, with discTxResourcesInterFreq within discResourcesPS included and set to requestDedicated;

1> if configured by upper layers to transmit relay PS related sidelink discovery announcements:

2> if the UE is acting as sidelink relay UE; and if the sidelink relay UE threshold conditions as specified in 5.10.10.4 are met; or

2> if the UE is selecting a sidelink relay UE / has a selected sidelink relay UE; and if the sidelink remote UE threshold conditions as specified in 5.10.11.5 are met:

3> if the frequency on which the UE is configured to transmit relay PS related sidelink discovery announcements concerns the camped frequency; and SystemInformationBlockType19 of the cell on which the UE camps includes discConfigRelay and discConfigPS but does not include discTxPoolPS-Common;

NOTE: Upper layers initiate an RRC connection. The interaction with NAS is left to UE implementation.

5.3.3.1b Conditions for initiating EDT

A BL UE, UE in CE or NB-IoT UE can initiate EDT when all of the following conditions are fulfilled:

1> if the UE is connected to EPC:

2> for CP-EDT, the upper layers request establishment of an RRC connection, the UE supports CP-EDT, and SystemInformationBlockType2 (SystemInformationBlockType2-NB in NB-IoT) includes cp-EDT; or

2> for UP-EDT, the upper layers request resumption of an RRC connection, the UE supports UP-EDT, SystemInformationBlockType2 (SystemInformationBlockType2-NB in NB-IoT) includes up-EDT, and the UE has a stored value of the nextHopChainingCount provided in the RRCConnectionRelease message with suspend indication during the preceding suspend procedure;

1> else if the UE is connected to 5GC:

2> for CP-EDT, the upper layers request establishment of an RRC connection, the UE connected to 5GC supports CP-EDT, and SystemInformationBlockType2 (SystemInformationBlockType2-NB in NB-IoT) includes cp-EDT-5GC; or

2> for UP-EDT, the upper layers request resumption of an RRC connection, the UE connected to 5GC supports UP-EDT, SystemInformationBlockType2 (SystemInformationBlockType2-NB in NB-IoT) includes up-EDT-5GC, and the UE has a stored value of the nextHopChainingCount provided in the RRCConnectionRelease message with suspend indication during the preceding suspend procedure;

1> the establishment or resumption request is for mobile originating calls and the establishment cause is mo-Data or mo-ExceptionData or delayTolerantAccess; or

1> the establishment or resumption request is for mobile terminating calls, the UE has a stored mt-EDT indication and the establishment cause is mt-Access;

1> the establishment or resumption request is suitable for EDT as specified in TS 36.300 [9], clause 7.3b.1;

1> SystemInformationBlockType2 (SystemInformationBlockType2-NB in NB-IoT) includes edt-Parameters;

1> for mobile originating calls, the size of the resulting MAC PDU including the total UL data is expected to be smaller than or equal to the TBS signalled in edt-TBS as specified in TS 36.321 [6], clause 5.1.1;

1> EDT fallback indication has not been received from lower layers for this establishment or resumption procedure;

NOTE 1: Upper layers request or resume an RRC connection. The interaction with NAS is up to UE implementation.

NOTE 2: It is up to UE implementation how the UE determines whether the size of UL data is suitable for EDT.

5.3.3.1c Conditions for initiating transmission using PUR

A BL UE, UE in CE or NB-IoT UE can initiate transmission using PUR when all of the following conditions are fulfilled:

1> the UE has a valid PUR configuration for the serving cell as specified in 5.3.3.20;

1> the UE has a valid timing alignment value as specified in 5.3.3.19;

1> the upper layers request establishment of an RRC connection; or the upper layers request resumption of an RRC connection and the UE has a stored value of the nextHopChainingCount provided in the RRCConnectionRelease message with suspend indication during the preceding suspend procedure;

1> the establishment or resumption request is for mobile originating calls and the establishment cause is mo-Data or mo-ExceptionData or delayTolerantAccess;

1> for CP transmission using PUR, the size of the resulting MAC PDU including the total UL data is expected to be smaller than or equal to the TBS configured for PUR.

NOTE 1: Upper layers request or resume an RRC connection. The interaction with NAS is up to UE implementation.

NOTE 2: It is up to UE implementation how the UE determines whether the establishment or resumption request is suitable for transmission using PUR.

5.3.3.1d Condition for establishing RRC Connection in NTN

If systemInformationBlockType31 (systemInformationBlockType31-NB in NB-IoT) is broadcast, a RRC connection is initiated only if the UE has a valid GNSS position.

NOTE: The UE may need to re-acquire the GNSS position before establishing the connection to avoid interruption during the connection.

5.3.3.2 Initiation

The UE initiates the procedure when upper layers request establishment or resume of an RRC connection while the UE is in RRC_IDLE or when upper layers request resume of an RRC connection or RRC layer requests resume of an RRC connection for, e.g. RNAU or reception of RAN paging while the UE is in RRC_INACTIVE.

Except for NB-IoT, upon initiation of the procedure, if the UE is connected to EPC, the UE shall:

1> if SystemInformationBlockType2 includes ac-BarringPerPLMN-List and the ac-BarringPerPLMN-List contains an AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]):

2> select the AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers;

2> in the remainder of this procedure, use the selected AC-BarringPerPLMN entry (i.e. presence or absence of access barring parameters in this entry) irrespective of the common access barring parameters included in SystemInformationBlockType2;

1> else

2> in the remainder of this procedure use the common access barring parameters (i.e. presence or absence of these parameters) included in SystemInformationBlockType2;

1> if SystemInformationBlockType2 contains acdc-BarringPerPLMN-List and the acdc-BarringPerPLMN-List contains an ACDC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]):

2> select the ACDC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers;

2> in the remainder of this procedure, use the selected ACDC-BarringPerPLMN entry for ACDC barring check (i.e. presence or absence of access barring parameters in this entry) irrespective of the acdc-BarringForCommon parameters included in SystemInformationBlockType2;

1> else:

2> in the remainder of this procedure use the acdc-BarringForCommon (i.e. presence or absence of these parameters) included in SystemInformationBlockType2 for ACDC barring check;

1> if upper layers indicate that the RRC connection is subject to EAB (see TS 24.301 [35]):

2> if the result of the EAB check, as specified in 5.3.3.12, is that access to the cell is barred:

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication and that EAB is applicable, upon which the procedure ends;

1> if upper layers indicate that the RRC connection is subject to ACDC (see TS 24.301 [35]), SystemInformationBlockType2 contains BarringPerACDC-CategoryList, and acdc-HPLMNonly indicates that ACDC is applicable for the UE:

2> if the BarringPerACDC-CategoryList contains a BarringPerACDC-Category entry corresponding to the ACDC category selected by upper layers:

3> select the BarringPerACDC-Category entry corresponding to the ACDC category selected by upper layers;

2> else:

3> select the last BarringPerACDC-Category entry in the BarringPerACDC-CategoryList;

2> stop timer T308, if running;

2> perform access barring check as specified in 5.3.3.13, using T308 as "Tbarring" and acdc-BarringConfig in the BarringPerACDC-Category as "ACDC barring parameter";

2> if access to the cell is barred:

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication and that access barring is applicable due to ACDC, upon which the procedure ends;

1> else if the UE is establishing the RRC connection for mobile terminating calls:

2> if timer T302 is running:

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication and that access barring for mobile terminating calls is applicable, upon which the procedure ends;

1> else if the UE is establishing the RRC connection for emergency calls:

2> if SystemInformationBlockType2 includes the ac-BarringInfo:

3> if the ac-BarringForEmergency is set to TRUE:

4> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11]:

NOTE 1: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

5> if the ac-BarringInfo includes ac-BarringForMO-Data, and for all of these valid Access Classes for the UE, the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Data is set to one:

6> consider access to the cell as barred;

4> else:

5> consider access to the cell as barred;

2> if access to the cell is barred:

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication, upon which the procedure ends;

1> else if the UE is establishing the RRC connection for mobile originating calls:

2> perform access barring check as specified in 5.3.3.11, using T303 as "Tbarring" and ac-BarringForMO-Data as "AC barring parameter";

2> if access to the cell is barred:

3> if SystemInformationBlockType2 includes ac-BarringForCSFB or the UE does not support CS fallback:

4> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication and that access barring for mobile originating calls is applicable, upon which the procedure ends;

3> else (SystemInformationBlockType2 does not include ac-BarringForCSFB and the UE supports CS fallback):

4> if timer T306 is not running, start T306 with the timer value of T303;

1> else if the UE is establishing the RRC connection for mobile originating signalling:

2> perform access barring check as specified in 5.3.3.11, using T305 as "Tbarring" and ac-BarringForMO-Signalling as "AC barring parameter";

2> if access to the cell is barred:

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication and that access barring for mobile originating signalling is applicable, upon which the procedure ends;

1> else if the UE is establishing the RRC connection for mobile originating CS fallback:

2> if SystemInformationBlockType2 includes ac-BarringForCSFB:

3> perform access barring check as specified in 5.3.3.11, using T306 as "Tbarring" and ac-BarringForCSFB as "AC barring parameter";

3> if access to the cell is barred:

4> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication and that access barring for mobile originating CS fallback is applicable, due to ac-BarringForCSFB, upon which the procedure ends;

2> else:

3> perform access barring check as specified in 5.3.3.11, using T306 as "Tbarring" and ac-BarringForMO-Data as "AC barring parameter";

3> if access to the cell is barred:

4> if timer T303 is not running, start T303 with the timer value of T306;

4> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication and that access barring for mobile originating CS fallback and mobile originating calls is applicable, due to ac-BarringForMO-Data, upon which the procedure ends;

1> else if the UE is establishing the RRC connection for mobile originating MMTEL voice, mobile originating MMTEL video, mobile originating SMSoIP or mobile originating SMS; or

1> if the UE is establishing the RRC connection after EPS fallback for IMS voice (see TS 23.502 [102]) was triggered in NR via RRCRelease with voiceFallbackIndication (see TS 38.331 [82]):

2> if the UE is establishing the RRC connection for mobile originating MMTEL voice and SystemInformationBlockType2 includes ac-BarringSkipForMMTELVoice; or

2> if the UE is establishing the RRC connection for mobile originating MMTEL video and SystemInformationBlockType2 includes ac-BarringSkipForMMTELVideo; or

2> if the UE is establishing the RRC connection for mobile originating SMSoIP or SMS and SystemInformationBlockType2 includes ac-BarringSkipForSMS:

3> consider access to the cell as not barred;

2> else:

3> if establishmentCause received from higher layers is set to mo-Signalling (including the case that mo-Signalling is replaced by highPriorityAccess according to TS 24.301 [35] or by mo-VoiceCall according to the clause 5.3.3.3):

4> perform access barring check as specified in 5.3.3.11, using T305 as "Tbarring" and ac-BarringForMO-Signalling as "AC barring parameter";

4> if access to the cell is barred:

5> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication and that access barring for mobile originating signalling is applicable, upon which the procedure ends;

3> if establishmentCause received from higher layers is set to mo-Data (including the case that mo-Data is replaced by highPriorityAccess according to TS 24.301 [35] or by mo-VoiceCall according to the clause 5.3.3.3):

4> perform access barring check as specified in 5.3.3.11, using T303 as "Tbarring" and ac-BarringForMO-Data as "AC barring parameter";

4> if access to the cell is barred:

5> if SystemInformationBlockType2 includes ac-BarringForCSFB or the UE does not support CS fallback:

6> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication and that access barring for mobile originating calls is applicable, upon which the procedure ends;

5> else (SystemInformationBlockType2 does not include ac-BarringForCSFB and the UE supports CS fallback):

6> if timer T306 is not running, start T306 with the timer value of T303;

Upon initiation of the procedure, if the UE is connected to 5GC, the UE shall:

1> if the upper layers provide an Access Category and one or more Access Identities upon requesting establishment of an RRC connection:

2> perform the unified access control procedure as specified in 5.3.16 using the Access Category and Access Identities provided by upper layers;

3> if the access attempt is barred, the procedure ends;

1> if the resumption of the RRC connection is triggered by response to NG-RAN paging:

2> select ‘0’ as the Access Category;

2> perform the unified access control procedure as specified in 5.3.16 using the selected Access Category and one or more Access Identities provided by upper layers;

3> if the access attempt is barred, the procedure ends;

1> else if the resumption of the RRC connection is triggered by upper layers:

2> if the upper layers provide an Access Category and one or more Access Identities:

3> perform the unified access control procedure as specified in 5.3.16 using the Access Category and Access Identities provided by upper layers;

4> if the access attempt is barred, the procedure ends;

2> set the resumeCause in accordance with the information received from upper layers;

1> else if the resumption of the RRC connection is triggered due to an RNAU:

2> if an emergency service is ongoing:

3> select ‘2’ as the Access Category;

3> set the resumeCause to emergency;

2> else:

3> select ‘8’ as the Access Category;

2> perform the unified access control procedure as specified in 5.3.16 using the selected Access Category and one or more Access Identities to be applied as specified in TS 24.501 [95];

3> if the access attempt is barred:

4> set the variable pendingRnaUpdate to ‘TRUE’;

4> the procedure ends;

Except for NB-IoT, upon initiating the procedure, if connected to EPC or 5GC, the UE shall:

1> if the UE is resuming an RRC connection from a suspended RRC connection or from RRC_INACTIVE:

2> if the UE was configured with (NG)EN-DC:

3> if the UE does not support maintaining SCG configuration upon connection resumption:

4> perform MR-DC release, as specified in TS 38.331 [82], clause 5.3.5.10;

4> release p-MaxEUTRA, if configured;

4> release p-MaxUE-FR1, if configured;

4> release tdm-PatternConfig or tdm-PatternConfig2, if configured;

3> release otherConfig associated with the SCG, if configured;

3> stop timers T346a, T346b, T346c, T346d and T346e associated with the SCG (see TS 38.331 [82], clause 7.1.1), if running;

2> if the UE does not support maintaining the MCG SCell configurations upon connection resumption:

3> release the MCG SCell(s), if configured, in accordance with 5.3.10.3a;

2> release powerPrefIndicationConfig, if configured and stop timer T340, if running;

2> release reportProximityConfig and clear any associated proximity status reporting timer;

2> release obtainLocationConfig, if configured;

2> release bt-NameListConfig, if configured;

2> release wlan-NameListConfig, if configured;

2> release measUncomBarPre, if configured;

2> release idc-Config, if configured;

2> release sps-AssistanceInfoReport, if configured;

2> release scg-DeactivationPreferenceConfig, if configured and stop timer T346, if running;

2> release measSubframePatternPCell, if configured;

2> if the UE was configured with DC:

3> release the entire SCG configuration, if configured, except for the DRB configuration (as configured by drb-ToAddModListSCG);

2> release naics-Info for the PCell, if configured;

2> release the LWA configuration, if configured, as described in 5.6.14.3;

2> release the LWIP configuration, if configured, as described in 5.6.17.3;

2> release bw-PreferenceIndicationTimer, if configured and stop timer T341, if running;

2> release delayBudgetReportingConfig, if configured and stop timer T342, if running;

2> release ailc-BitConfig, if configured;

2> release uplinkDataCompression, if configured;

2> release overheatingAssistanceConfig and overheatingAssistanceConfigForSCG, if configured and stop timer T345, if running;

NOTE 1a: The parameters and configurations are released from the UE Inactive AS context if the UE is resuming an RRC connection from RRC_INACTIVE.

1> if the UE is establishing or resuming an RRC connection from a suspended RRC connection:

2> if the UE has a stored pur-Config and the cell is different from the cell where pur-Config was provided:

3> if pur-TimeAlignmentTimer is configured, indicate to lower layers that pur-TimeAlignmentTimer is released;

3> release pur-Config;

3> discard previously stored pur-Config;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

1> apply the CCCH configuration as specified in 9.1.1.2;

1> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

1> if UE supports timing advance reporting and ta-Report is included in SystemInformationBlockType2:

2> instruct the associated MAC entity to trigger Timing Advance reporting;

1> start timer T300;

1> if the UE is resuming an RRC connection from a suspended RRC connection:

2> initiate transmission of the RRCConnectionResumeRequest message in accordance with 5.3.3.3a;

1> else if the UE is resuming an RRC connection from RRC_INACTIVE:

2> set the variable pendingRnaUpdate to ‘FALSE’;

2> initiate transmission of the RRCConnectionResumeRequest message in accordance with 5.3.3.3a;

1> else:

2> if stored, discard the UE AS context, UE Inactive AS context and resumeIdentity;

2> release rrc-InactiveConfig, if configured;

2> if the UE is initiating CP-EDT in accordance with conditions in 5.3.3.1b; or

2> if the UE is initiating CP transmission using PUR in accordance with conditions in 5.3.3.1c:

3> initiate transmission of the RRCEarlyDataRequest message in accordance with 5.3.3.3b;

2> else:

3> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

1> if stored, discard mt-EDT;

NOTE 2: Upon initiating the connection establishment procedure, the UE is not required to ensure it maintains up to date system information applicable only for UEs in RRC_IDLE state or UEs in RRC_INACTIVE. However, the UE needs to perform system information acquisition upon cell re-selection.

For NB-IoT, upon initiation of the procedure, the UE shall:

1> if the UE is connected to EPC:

2> if the UE is establishing or resuming the RRC connection for mobile originating exception data; or

2> if the UE is establishing or resuming the RRC connection for mobile originating data; or

2> if the UE is establishing or resuming the RRC connection for delay tolerant access; or

2> if the UE is establishing or resuming the RRC connection for mobile originating signalling;

3> perform access barring check as specified in 5.3.3.14;

3> if access to the cell is barred:

4> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication and that access barring is applicable, upon which the procedure ends;

1> if the UE is connected to 5GC:

2> if the Access Category provided by the upper layers is different from ‘0’:

3> perform access barring check for per-NRSRP barring as specified in 5.3.3.14;

3> if access to the cell is barred:

4> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication, upon which the procedure ends;

3> else:

4> perform the unified access control procedure as specified in 5.3.16 using the Access Category and Access Identities provided by upper layers;

4> if the access attempt is barred, the procedure ends;

1> if the UE is establishing or resuming an RRC connection:

2> if the UE has a stored pur-Config and the cell is different from the cell where pur-Config was provided:

3> if pur-TimeAlignmentTimer is configured, indicate to lower layers that pur-TimeAlignmentTimer is released;

3> release pur-Config;

3> discard previously stored pur-Config;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default MAC main configuration as specified in 9.2.2;

1> apply the CCCH configuration as specified in 9.1.1.2;

1> if UE supports timing advance reporting and ta-Report is included in SystemInformationBlockType2-NB:

2> instruct the associated MAC entity to trigger Timing Advance reporting;

1> start timer T300;

1> if the UE is establishing an RRC connection:

2> if stored, discard the UE AS context and resumeIdentity;

2> if the UE is initiating CP-EDT in accordance with conditions in 5.3.3.1b; or

2> if the UE is initiating CP transmission using PUR in accordance with conditions in 5.3.3.1c:

3> initiate transmission of the RRCEarlyDataRequest message in accordance with 5.3.3.3b;

2> else:

3> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

1> else if the UE is resuming an RRC connection:

2> release schedulingRequestConfig, if configured;

2> initiate transmission of the RRCConnectionResumeRequest message in accordance with 5.3.3.3a;

1> if stored, discard mt-EDT;

NOTE 3: Upon initiating the connection establishment or resumption procedure, the UE is not required to ensure it maintains up to date system information applicable only for UEs in RRC_IDLE state. However, the UE needs to perform system information acquisition upon cell re-selection.

NOTE 4: For EDT and transmission using PUR, upon initiating the connection establishment or resumption procedure, it is up to UE implementation whether to continue cell re-selection related measurements as well as cell re-selection evaluation and, if the conditions for cell re-selection are fulfilled, whether to perform cell re-selection as specified in 5.3.3.5.

5.3.3.3 Actions related to transmission of RRCConnectionRequest message

The UE shall set the contents of RRCConnectionRequest message as follows:

1> if the UE is connected to EPC:

2> set the ue-Identity as follows:

3> if upper layers provide an S-TMSI:

4> set the ue-Identity to the value received from upper layers;

3> else:

4> draw a random value in the range 0 .. 2⁴⁰-1 and set the ue-Identity to this value;

NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.

2> if the establishment of the RRC connection is the result of release with redirect with mpsPriorityIndication (either in NR or E-UTRAN):

3> set the establishmentCause to highPriorityAccess;

2> else:

3> if the UE supports mo-VoiceCall establishment cause and UE is establishing the RRC connection for mobile originating MMTEL voice and SystemInformationBlockType2 includes voiceServiceCauseIndication and the establishment cause received from upper layers is not set to highPriorityAccess; or

3> if the UE supports mo-VoiceCall establishment cause and EPS fallback for IMS voice (see TS 23.502 [102]) was triggered in NR via RRCRelease with voiceFallbackIndication (see TS 38.331 [82]) and SystemInformationBlockType2 includes voiceServiceCauseIndication and the establishment cause received from upper layers is not set to highPriorityAccess or emergency:

4> set the establishmentCause to mo-VoiceCall;

3> else if the UE supports mo-VoiceCall establishment cause for mobile originating MMTEL video and UE is establishing the RRC connection for mobile originating MMTEL video and SystemInformationBlockType2 includes videoServiceCauseIndication and the establishment cause received from upper layers is not set to highPriorityAccess:

4> set the establishmentCause to mo-VoiceCall;

3> else:

4> set the establishmentCause in accordance with the information received from upper layers;

1> if the UE is connected to 5GC:

2> set the ue-Identity as follows:

3> if upper layers provide a 5G-S-TMSI:

4> except for NB-IoT, set the ue-Identity to ng-5G-S-TMSI-Part1;

4> for NB-IoT, set the ue-Identity to ng-5G-S-TMSI;

3> else:

4> draw a random value in the range 0 .. 2⁴⁰-1 and set the ue-Identity to this value;

2> if the establishment of the RRC connection is the result of release with redirect with mpsPriorityIndication (either in NR or E-UTRAN);

3> set the establishmentCause to highPriorityAccess;

2> else:

3> set the establishmentCause in accordance with the information received from upper layers;

2> except for NB-IoT, apply the default NR PDCP configuration as specified in TS 38.331 [82], clause 9.2.1.1 for SRB1;

2> except for NB-IoT, use NR PDCP for all subsequent messages received and sent by the UE via SRB1;

1> if the UE is a NB-IoT UE:

2> if the UE is connected to EPC:

3> if the UE supports multi-tone transmission, include multiToneSupport;

3> if the UE supports multi-carrier operation, include multiCarrierSupport;

3> set earlyContentionResolution to TRUE;

2> if the UE supports DL channel quality reporting in MSG3 and cqi-Reporting is present in SystemInformationBlockType2-NB:

3> set the cqi-NPDCCH to include the latest results of the downlink channel quality measurements of the carrier where the random access response is received as specified in TS 36.133 [16];

NOTE 2: The downlink channel quality measurements use measurement period T1 or T2, as defined in TS 36.133 [16].

1> if the UE is initiating transmission using PUR in accordance with conditions in 5.3.3.1c:

2> configure, except pur-TimeAlignmentTimer, the lower layers to use transmission using PUR;

2> deliver the UL grant for transmission using PUR to the MAC entity;

The UE shall submit the RRCConnectionRequest message to lower layers for transmission.

The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.5.

5.3.3.3a Actions related to transmission of RRCConnectionResumeRequest message

If the UE is resuming the RRC connection from a suspended RRC connection, the UE shall set the contents of RRCConnectionResumeRequest message as follows:

1> if the UE is a NB-IoT UE; or

1> if the UE is initiating UP-EDT for mobile originating calls in accordance with conditions in 5.3.3.1b; or

1> if the UE is initiating UP transmission using PUR in accordance with conditions in 5.3.3.1c; or

1> if field useFullResumeID is signalled in SystemInformationBlockType2:

2> if the UE connected to 5GC is a BL UE or UE in CE:

3> set the fullI-RNTI to the stored fullI-RNTI;

2> else:

3> set the resumeID to the stored resumeIdentity;

1> else:

2> if the UE connected to 5GC is a BL UE or UE in CE:

3> set the shortI-RNTI to the stored shortI-RNTI;

2> else:

3> set the truncatedResumeID to include bits in bit position 9 to 20 and 29 to 40 from the left in the stored resumeIdentity.

1> if the UE is resuming the RRC connection after release with redirect with mpsPriorityIndication:

2> set the resumeCause to highPriorityAccess;

1> else if the UE supports mo-VoiceCall establishment cause and UE is resuming the RRC connection for mobile originating MMTEL voice and SystemInformationBlockType2 includes voiceServiceCauseIndication and the establishment cause received from upper layers is not set to highPriorityAccess:

2> set the resumeCause to mo-VoiceCall;

1> else if the UE supports mo-VoiceCall establishment cause for mobile originating MMTEL video and UE is resuming the RRC connection for mobile originating MMTEL video and SystemInformationBlockType2 includes videoServiceCauseIndication and the establishment cause received from upper layers is not set to highPriorityAccess:

2> set the resumeCause to mo-VoiceCall;

1> else if the UE is initiating UP-EDT for mobile terminating calls in accordance with conditions in 5.3.3.1b:

2> set the resumeCause to mt-EDT;

1> else:

2> set the resumeCause in accordance with the information received from upper layers;

1> set the shortResumeMAC-I to the 16 least significant bits of the MAC-I calculated:

2> over the ASN.1 encoded as per clause 8 (i.e., a multiple of 8 bits) VarShortResumeMAC-Input (or VarShortResumeMAC-Input-NB in NB-IoT);

2> with the K_RRCint key and the previously configured integrity protection algorithm; and

2> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

1> if the UE is a NB-IoT UE:

2> if the UE supports DL channel quality reporting in MSG3 and cqi-Reporting is present in SystemInformationBlockType2-NB:

3> set the cqi-NPDCCH to include the latest results of the downlink channel quality measurements of the carrier where the random access response is received as specified in TS 36.133 [16];

NOTE 0: The downlink channel quality measurements use measurement period T1 or T2, as defined in TS 36.133 [16].

2> if the UE is connected to EPC, set earlyContentionResolution to TRUE;

1> restore the RRC configuration and security context from the stored UE AS context, except for the following:

– MCG SCell(s) configuration, if stored,

– nr-SecondaryCellGroupConfig, if stored;

1> if the UE is initiating UP-EDT for mobile originating calls in accordance with conditions in 5.3.3.1b:

2> if the UE is a NB-IoT UE connected to EPC:

3> if the UE has ANR measurements information available in VarANR-MeasReport-NB and if the RPLMN is included in plmn-IdentityList stored in VarANR-MeasReport-NB:

4> set anr-InfoAvailable to TRUE;

1> if the UE is resuming an RRC connection after early security reactivation in accordance with conditions in 5.3.3.18:

2> if the UE is initiating UP-EDT in accordance with conditions in 5.3.3.1b; or

2> if the UE is initiating UP transmission using PUR in accordance with conditions in 5.3.3.1c:

3> restore the PDCP state and re-establish PDCP entities for all SRBs and all DRBs;

3> if drb-ContinueROHC has been provided in immediately preceding RRC connection release message, and the UE is requesting to resume RRC connection in the same cell:

4> indicate to lower layers that stored UE AS context is used and that drb-ContinueROHC is configured;

4> continue the header compression protocol context for the DRBs configured with the header compression protocol;

3> else:

4> indicate to lower layers that stored UE AS context is used;

4> reset the header compression protocol context for the DRBs configured with the header compression protocol;

3> resume all SRBs and all DRBs;

2> else:

3> if the UE is a NB-IoT UE or the UE is connected to EPC, restore the PDCP state and re-establish the PDCP entity for SRB1;

3> if the UE is connected to 5GC:

4> apply the default configuration for SRB1 as specified in 9.2.1.1;

4> except for NB-IoT, apply the default NR PDCP configuration as specified in TS 38.331 [82], clause 9.2.1 for SRB1;

3> resume SRB1;

2> derive the K_eNB key based on the K_ASME key to which the current K_eNB is associated, using the stored value of nextHopChainingCount received in the RRCConnectionRelease message in the preceding connection, as specified in TS 33.401 [32] for EPC and TS 33.501 [86] for 5GC;

2> derive the K_RRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401 [32] for EPC and TS 33.501 [86] for 5GC;

2> derive the K_RRCenc key and the K_UPenc key associated with the previously configured ciphering algorithm, as specified in TS 33.401 [32] for EPC and TS 33.501 [86] for 5GC;

2> configure lower layers to resume integrity protection using the previously configured algorithm and the K_RRCint key derived in this clause to all subsequent messages received and sent by the UE;

2> configure lower layers to resume ciphering and to apply the ciphering algorithm and the K_RRCenc key derived in this clause to all subsequent messages received and sent by the UE;

2> configure lower layers to resume ciphering and to apply the ciphering algorithm and the K_UPenc key derived in this clause immediately to the user data sent and received by the UE;

2> if the UE is initiating UP-EDT for mobile originated calls in accordance with conditions in 5.3.3.1b:

3> configure the lower layers to use EDT;

2> else if the UE is initiating UP transmission using PUR in accordance with conditions in 5.3.3.1c:

3> configure, except pur-TimeAlignmentTimer, the lower layers to use transmission using PUR;

3> deliver the UL grant for transmission using PUR to the MAC entity;

1> else:

2> if SRB1 was configured with NR PDCP:

3> for SRB1, release the NR PDCP entity and establish an E-UTRA PDCP entity with the current (MCG) security configuration;

NOTE 1: The UE applies the LTE ciphering and integrity protection algorithms that are equivalent to the previously configured NR security algorithms.

2> else:

3> for SRB1, restore the PDCP state and re-establish the PDCP entity;

If the UE is resuming the RRC connection from RRC_INACTIVE, the UE shall set the contents of RRCConnectionResumeRequest message as follows:

2> if field useFullResumeID is signalled in SystemInformationBlockType2:

3> set the fullI-RNTI to the stored fullI-RNTI value provided in suspend;

2> else:

3> set the shortI-RNTI to the stored shortI-RNTI value provided in suspend;

2> restore the RRC configuration, RoHC state, the stored QoS flow to DRB mapping rules and the K_eNB and K_RRCint keys from the UE Inactive AS context except for the following:

– MCG physical layer,

– MCG MAC configuration,

– NR pdcp-Config,

– MCG SCell configurations, if stored,

– nr–SecondaryCellGroupConfig, if stored;

2> set the shortResumeMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the ASN.1 encoded as per clause 8 (i.e., a multiple of 8 bits) VarShortINACTIVE-MAC-Input;

3> with the K_RRCint key in the UE Inactive AS Context and the previously configured integrity protection algorithm; and

3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

2> derive the K_eNB key based on the current K_eNB or the NH, using the stored nextHopChainingCount value, as specified in TS 33.501 [86];

2> derive the K_RRCenc key, the K_RRCint and the K_UPenc key, as specified in TS 33.401 [32];

2> apply the default configuration for SRB1 as specified in 9.2.1.1;

2> apply the default NR PDCP configuration as specified in TS 38.331 [82], clause 9.2.1 for SRB1;

2> configure lower layers to resume integrity protection for all SRBs except SRB0 using the configured algorithm and the K_RRCint key derived in this clause immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE;

2> configure lower layers to resume ciphering for all radio bearers except SRB0 and to apply the configured ciphering algorithm, the K_RRCenc key and the K_UPenc key derived in this clause, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE;

Following procedures are applied for both suspended RRC connection and RRC_INACTIVE:

2> resume SRB1;

NOTE 2: Until successful connection resumption, the default physical layer configuration and the default MAC Main configuration are applied for the transmission of SRB0 and SRB1, and SRB1 is used only for the transfer of RRCConnectionResume message, and RRCConnectionRelease message if security has been re-activated.

The UE shall submit the RRCConnectionResumeRequest message to lower layers for transmission.

The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation.

If the UE is resuming the RRC connection from RRC_INACTIVE and if lower layers indicate an integrity check failure while T300 is running, the UE shall perform actions specified in 5.3.3.16.

5.3.3.3b Actions related to transmission of RRCEarlyDataRequest message

The UE shall set the contents of RRCEarlyDataRequest message as follows:

1> if upper layers provide an S-TMSI:

2> set the s-TMSI to the value received from upper layers;

1> else if upper layers provide a 5G-S-TMSI:

2> set the ng-5G-S-TMSI to the value received from upper layers;

1> set the establishmentCause in accordance with the information received from upper layers;

1> if the UE is a NB-IoT UE:

2> if the UE supports DL channel quality reporting and cqi-Reporting is present in SystemInformationBlockType2-NB:

3> set the cqi-NPDCCH to include the latest results of the downlink channel quality measurements of the carrier where the random access response is received as specified in TS 36.133 [16];

NOTE: The downlink channel quality measurements may use measurement period T1 or T2, as defined in TS 36.133 [16]. In case period T2 is used the RRC-MAC interactions are left to UE implementation.

1> set the dedicatedInfoNAS to include the information received from upper layers;

The UE shall:

1> if the UE is initiating CP-EDT in accordance with conditions in 5.3.3.1b:

2> configure the lower layers to use EDT;

1> else if the UE is initiating CP transmission using PUR in accordance with conditions in 5.3.3.1c:

2> configure, except pur-TimeAlignmentTimer, the lower layers to use transmission using PUR;

2> deliver the UL grant for transmission using PUR to the MAC entity;

1> submit the RRCEarlyDataRequest message to the lower layers for transmission.

5.3.3.3c UE actions upon receiving EDT fallback indication from lower layers

Upon indication from lower layers that EDT is cancelled, the UE shall:

1> start or restart timer T300;

1> if the fallback is indicated by lower layers in response to the RRCEarlyDataRequest:

2> initiate transmission of RRCConnectionRequest message in accordance with 5.3.3.3;

1> else if the fallback is indicated by lower layers in response to the RRCConnectionResumeRequest for EDT when connected to EPC and the fallback is not due to the UL grant provided in Random Access Response not being for EDT:

2> perform the actions as specified in 5.3.3.9a;

2> initiate transmission of the RRCConnectionResumeRequest message in accordance with 5.3.3.3a;

NOTE: It is up to UE implementation to avoid data loss due to EDT fallback.

5.3.3.3d UE actions upon receiving PUR indications from lower layers

The UE shall:

1> if repetition adjustment is indicated by lower layers:

2> update numRepetitions (npusch-NumRepetitionsIndex in NB-IoT) in previously stored pur-Config in accordance with the received indication;

1> if pur-RSRP-ChangeThreshold (pur-NRSRP-ChangeThreshold in NB-IoT) is configured and timing advance adjustment is indicated by lower layers:

2> replace the serving cell reference (N)RSRP value with the current serving cell (N)RSRP value (see 5.3.3.19);

For CP transmission using PUR, upon indication from lower layers that transmission using PUR is successfully completed, the UE shall perform the actions as specified in 5.3.3.4b as if an empty RRCEarlyDataComplete message was received.

Upon reception of PUR fallback or PUR failure indication from lower layers, the procedure ends.

NOTE: For transmission using PUR, further UE actions upon reception of PUR fallback or PUR failure indication from lower layers (see TS 36.321 [6]) is left up to implementation.

5.3.3.4 Reception of the RRCConnectionSetup by the UE

NOTE 1: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> except when the UE connected to 5GC is a BL UE or UE in CE, if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from a suspended RRC connection:

2> if the UE is resuming an RRC connection after early security reactivation in accordance with conditions in 5.3.3.18:

3> discard any current AS security context including the K_RRCenc key, the K_RRCint key, the K_UPint key and the K_UPenc key;

2> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP entity for all established or suspended RBs, except for SRB0;

2> discard the stored UE AS context and resumeIdentity;

2> if stored, discard the stored nextHopChainingCount;

2> if stored, discard the stored drb-ContinueROHC;

2> indicate to upper layers fallback of the RRC connection;

1> if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from RRC_INACTIVE:

2> stop T380 if running;

2> discard the stored UE Inactive AS context;

2> release rrc-InactiveConfig, if configured;

1> if the UE connected to 5GC is a BL UE or UE in CE, and the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from a suspended RRC connection:

2> discard the stored UE AS context and resumeIdentity;

2> if stored, discard the stored nextHopChainingCount;

2> if stored, discard the stored drb-ContinueROHC;

1> if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from RRC_INACTIVE; or

1> if the UE connected to 5GC is a BL UE or UE in CE, and the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from a suspended RRC connection:

2> discard any current AS security context including the K_RRCenc key, the K_RRCint key, the K_UPint key and the K_UPenc key;

2> release radio resources for all established RBs except SRB0, including release of the RLC entities, of the associated PDCP entities and of SDAP entities;

2> release the RRC configuration except for the default L1 parameter values, default MAC main configuration and CCCH;

2> apply the default NR PDCP configuration as specified in TS 38.331 [82], clause 9.2.1.1 for SRB1;

2> use NR PDCP for all subsequent messages received and sent by the UE via SRB1;

2> indicate to upper layers fallback of the RRC connection;

1> if the RRCConnectionSetup is received in response to an RRCEarlyDataRequest or RRCConnectionResumeRequest for transmission using PUR:

2> instruct the associated MAC entity to start timeAlignmentTimer;

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10.0;

1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or inherited from another RAT;

1> if stored, discard the altFreqPriorities provided by the RRCConnectionRelease;

1> if stored, discard the dedicated offset provided by the redirectedCarrierOffsetDedicated;

1> stop timer T300;

1> if T302 is running:

2> stop timer T302;

2> if the UE is connected to 5GC:

3> perform the actions as specified in 5.3.16.4;

1> stop timer T303, if running;

1> stop timer T305, if running;

1> stop timer T306, if running;

1> stop timer T308, if running;

1> perform the actions as specified in 5.3.3.7;

1> stop timer T320, if running;

1> stop timer T350, if running;

1> perform the actions as specified in 5.6.12.4;

1> release rclwi-Configuration, if configured, as specified in 5.6.16.2;

1> stop timer T360, if running;

1> stop timer T322, if running;

1> if timer T331 is running:

2> stop timer T331;

2> perform the actions as specified in 5.6.20.3;

1> stop timer T323, if running;

1> forward the dedicatedInfoNAS, if received, to the upper layers;

1> if T309 is running:

2> stop timer T309 for all access categories;

2> perform the actions as specified in 5.3.16.4.

1> enter RRC_CONNECTED;

1> stop the cell re-selection procedure;

1> consider the current cell to be the PCell;

1> except for NB-IoT:

2> if the UE supports RLF report for inter-RAT MRO EUTRA as defined in TS 38.306 [87], and if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 38.331 [82] and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 38.331 [82]:

3> if reconnectCellId in VarRLF-Report of TS 38.331 [82] is not set, and if the received RRCConnectionSetup is in response to an RRCConnectionRequest:

4> set timeUntilReconnection in VarRLF-Report of TS 38.331 [82] to the time that elapsed since the last radio link failure or handover failure;

4> set eutraReconnectCellId in reconnectCellId in VarRLF-Report of TS 38.331 [82] to the global cell identity and the tracking area code of the PCell;

2> if the UE radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

3> if reconnectCellId in VarRLF-Report is not set, and if the received RRCConnectionSetup is in response to an RRCConnectionRequest:

4> set timeUntilReconnection in VarRLF-Report to the time that elapsed since the last radio link failure or handover failure;

4> set eutraReconnectCellId in reconnectCellId in VarRLF-Report to the global cell identity and the tracking area code of the PCell;

1> set the content of RRCConnectionSetupComplete message as follows:

2> if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest:

3> if upper layers provide an S-TMSI:

4> set the s-TMSI to the value received from upper layers;

3> else if upper layers provide a 5G-S-TMSI:

4> if the UE is a NB-IoT UE:

5> set the ng-5G-S-TMSI to the value received from upper layers;

4> else:

5> set the ng-5G-S-TMSI-Bits to ng-5G-S-TMSI with the value received from upper layers;

2> else if upper layers provide a 5G-S-TMSI:

3> except for NB-IoT, set the ng-5G-S-TMSI-Bits to ng-5G-S-TMSI-Part2 to the leftmost 8 bits of 5G-S-TMSI received from upper layers;

2> set the selectedPLMN-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35] for E-UTRA/EPC and TS 24.501 [95] for E-UTRA/5GC) from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1 (or SystemInformationBlockType1-NB in NB-IoT);

2> if upper layers provide the ‘Registered MME’, include and set the registeredMME as follows:

3> if the PLMN identity of the ‘Registered MME’ is different from the PLMN selected by the upper layers:

4> include the plmnIdentity in the registeredMME and set it to the value of the PLMN identity in the ‘Registered MME’ received from upper layers;

3> set the mmegi and the mmec to the value received from upper layers;

2> if upper layers provided the ‘Registered MME’:

3> include and set the gummei-Type to the value provided by the upper layers;

2> if upper layers provide the ‘Registered AMF’, include and set the registeredAMF as follows:

3> if the PLMN identity of the ‘Registered AMF’ is different from the PLMN selected by the upper layers:

4> include the plmnIdentity in the registeredAMF and set it to the value of the PLMN identity in the ‘Registered AMF’ received from upper layers;

3> set the amf-Identifier to AMF Identifier of the ‘Registered AMF’ received from upper layers;

2> if upper layers provided the ‘Registered AMF’:

3> include and set the guami-Type to the value provided by the upper layers;

2> if upper layers provide one or more S-NSSAI (see TS 23.003 [27]):

3> include the s-NSSAI-list and set the content to the values provided by the upper layers;

2> if the UE supports CIoT EPS optimisation(s):

3> include attachWithoutPDN-Connectivity if received from upper layers;

3> include up-CIoT-EPS-Optimisation if received from upper layers;

3> except for NB-IoT, include cp-CIoT-EPS-Optimisation if received from upper layers;

2> if the UE supports CIoT 5GS optimisation(s):

3> for NB-IoT, include ng-U-DataTransfer if received from upper layers;

3> except for NB-IoT, include cp-CIoT-5GS-Optimisatoin if received from upper layers;

2> if connecting as an RN:

3> include the rn-SubframeConfigReq;

2> if the RRCConnectionSetup is received in response to RRCEarlyDataRequest:

3> set the dedicatedInfoNAS to a zero-length octet string;

2> else:

3> set the dedicatedInfoNAS to include the information received from upper layers;

2> if the RRCConnectionSetup is not in response to transmission using PUR and the UE has a stored pur-Config including pur-ConfigID:

3> include the stored pur-ConfigID;

2> if the UE is connected to EPC:

3> except for NB-IoT:

4> include the mobilityState and set it to the mobility state (as specified in TS 36.304 [4]) of the UE just prior to entering RRC_CONNECTED state;

4> if the UE has flight path information available:

5> include flightPathInfoAvailable;

3> for NB-IoT:

4> if the UE has radio link failure information available in VarRLF-Report-NB and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report-NB:

5> include rlf-InfoAvailable;

4> if the UE has ANR measurements information available in VarANR-MeasReport-NB and if the RPLMN is included in plmn-IdentityList stored in VarANR-MeasReport-NB:

5> include anr-InfoAvailable;

3> include dcn-ID if a DCN-ID value (see TS 23.401 [41]) is received from upper layers;

2> else (i.e. the UE is connected to 5GC):

3> if the UE is a BL UE:

4> include lte-M;

2> except for NB-IoT:

3> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

4> include rlf-InfoAvailable;

3> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

4> include logMeasAvailableMBSFN;

3> if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

4> include logMeasAvailable;

4> if Bluetooth measurement results are included in the logged measurements the UE has available:

5> include logMeasAvailableBT;

4> if WLAN measurement results are included in the logged measurements the UE has available:

5> include logMeasAvailableWLAN;

3> if the UE has connection establishment failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

4> include connEstFailInfoAvailable;

3> if the UE supports storage of mobility history information and the UE has mobility history information available in VarMobilityHistoryReport:

4> include the mobilityHistoryAvail;

3> if the SIB2 contains idleModeMeasurements and the UE has E-UTRA idle/inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport; or

3> if the SIB2 contains idleModeMeasurementsNR and the UE has NR idle/inactive measurement information available in VarMeasIdleReport:

4> include the idleMeasAvailable;

3> if upper layers indicate that access to RLOS is initiated (see TS 23.401 [41] clause 4.3.8.3):

4> set rlos-Request to true;

2> if UE needs UL gaps during continuous uplink transmission:

3> include ue-CE-NeedULGaps;

2> for NB-IoT:

3> if the UE supports serving cell idle mode measurements reporting and servingCellMeasInfo is present in SystemInformationBlockType2-NB:

4> set the measResultServCell to include the measurements of the serving cell;

NOTE 2: The UE includes the latest results of the serving cell measurements as used for cell selection/ reselection evaluation, which are performed in accordance with the performance requirements as specified in TS 36.133 [16].

2> if connecting as an IAB-node:

3> include iab-NodeIndication;

2> if the UE is connected to NTN:

3> include gnss-validityDuration in accordance with the remaining time of the GNSS validity duration;

2> if UE supports uplink RRC Segmentation of UECapabilityInformation:

3> except for NB-IoT, may include ul-RRC-Segmentation if upper layers indicate that they are performing an Attach or TA Update;

1> submit the RRCConnectionSetupComplete message to lower layers for transmission;

1> for NB-IoT:

2> if the UE supports connected mode measurements and connMeasConfig is present in SystemInformationBlockType3-NB:

3> perform measurements as specified in 5.5.8.

1> the procedure ends.

5.3.3.4a Reception of the RRCConnectionResume by the UE

The UE shall:

1> stop timer T300;

1> if T309 is running:

2> stop timer T309 for all access categories;

2> perform the actions as specified in 5.3.16.4.

1> stop T380 if running;

1> if the RRCConnectionResume is received in response to an RRCConnectionResumeRequest for EDT or for transmission using PUR:

2> discard the stored UE AS context and resumeIdentity;

2> if the RRCConnectionResume is received in response to an RRCConnectionResumeRequest for transmission using PUR:

3> instruct the associated MAC entity to start timeAlignmentTimer;

1> else:

2> if resuming an RRC connection from a suspended RRC connection in EPC; or

2> for NB-IoT, if resuming an RRC connection from a suspended RRC connection in 5GC and fullConfig is not present in the RRCConnectionResume message:

3> restore the PDCP state and re-establish PDCP entities for SRB2, if configured with E-UTRA PDCP, and for all DRBs that are configured with E-UTRA PDCP;

3> if drb-ContinueROHC is included:

4> indicate to lower layers that stored UE AS context is used and that drb-ContinueROHC is configured;

4> continue the header compression protocol context for the DRBs configured with the header compression protocol;

3> else:

4> indicate to lower layers that stored UE AS context is used;

4> reset the header compression protocol context for the DRBs configured with the header compression protocol;

3> if restoreMCG-SCells is included:

4> restore the MCG SCell(s) configuration, if stored;

3> else:

4> release the MCG SCell(s) from the UE AS context, if stored;

3> if restoreSCG is included:

4> restore nr-SecondaryCellGroupConfig, if stored;

3> else if the UE was configured with EN-DC:

4> perform MR-DC release, as specified in TS 38.331 [82], clause 5.3.5.10;

4> release tdm-PatternConfig or tdm-PatternConfig2, if configured;

3> discard the stored UE AS context and resumeIdentity;

3> configure lower layers to consider the restored MCG and SCG SCell(s) (if any) to be in deactivated state;

2> else if the RRCConnectionResume message includes the fullConfig (i.e., for resuming an RRC connection from RRC_INACTIVE or for resuming a suspended RRC connection in 5GC):

3> perform the radio configuration procedure as specified in 5.3.5.8;

2> else if resuming an RRC connection from RRC_INACTIVE:

3> restore the following from the stored UE Inactive AS context:

– MCG physical layer configuration,

– MCG MAC configuration,

– MCG RLC configuration,

– PDCP configuration;

3> if restoreMCG-SCells is included:

4> restore the MCG SCell(s) configuration, if stored;

3> else:

4> release the MCG SCell(s) from the UE Inactive AS context, if stored;

3> if restoreSCG is included:

4> restore nr-SecondaryCellGroupConfig, if stored;

3> else if the UE was configured with NGEN-DC:

4> perform MR-DC release, as specified in TS 38.331 [82], clause 5.3.5.10;

4> release tdm-PatternConfig or tdm-PatternConfig2, if configured;

3> discard the stored UE Inactive AS context;

3> configure lower layers to consider the restored MCG and SCG SCell(s) (if any) to be in deactivated state;

3> release the rrc-InactiveConfig, except ran-NotificationAreaInfo;

2> else (i.e., except for NB-IoT for resuming a suspended RRC connection in 5GC):

3> restore the physical layer configuration, the MAC configuration, the RLC configuration and the PDCP configuration from the stored UE AS context;

3> discard the stored UE AS context and resumeIdentity;

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10.0;

NOTE 1: When performing the radio resource configuration procedure, for the physical layer configuration and the MAC Main configuration, the restored RRC configuration from the stored UE AS context is used as basis for the reconfiguration.

1> if the received RRCConnectionResume includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionResume includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> if the received RRCConnectionResume includes the sCellGroupToReleaseList:

2> perform SCell group release as specified in 5.3.10.3d;

1> if the received RRCConnectionResume includes the sCellGroupToAddModList:

2> perform SCell group addition or modification as specified in 5.3.10.3e;

1> if the received RRCConnectionResume message includes the nr-SecondaryCellGroupConfig:

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;

1> if the received RRCConnectionResume message includes the sk-Counter:

2> perform key update procedure as specified in TS 38.331 [82], clause 5.3.5.8;

1> if the received RRCConnectionResume message includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionResume message includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> except if the RRCConnectionResume is received in response to an RRCConnectionResumeRequest for EDT or for transmission using PUR:

2> resume SRB2, SRB3 (if configured), and all DRBs, if any, including RBs configured with NR PDCP;

NOTE 1a: If the NR SCG is deactivated, resuming SRB3 and all DRBs does not imply that PDCP or RRC PDUs can be transmitted or received on SCG RLC bearers.

1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or inherited from another RAT;

1> if stored, discard the altFreqPriorities provided by the RRCConnectionRelease;

1> if stored, discard the dedicated offset provided by the redirectedCarrierOffsetDedicated;

1> if the RRCConnectionResume message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> if T302 is running:

2> stop timer T302;

2> if the UE is connected to 5GC:

3> perform the actions as specified in 5.3.16.4;

1> stop timer T303, if running;

1> stop timer T305, if running;

1> stop timer T306, if running;

1> stop timer T308, if running;

1> perform the actions as specified in 5.3.3.7;

1> stop timer T320, if running;

1> stop timer T350, if running;

1> perform the actions as specified in 5.6.12.4;

1> stop timer T360, if running;

1> stop timer T322, if running;

1> stop timer T323, if running;

1> if timer T331 is running:

2> stop timer T331;

2> perform the actions as specified in 5.6.20.3;

1> if the UE is resuming an RRC connection after early security reactivation in accordance with conditions in 5.3.3.18 or RRCConnectionResume is received in response to an RRCConnectionResumeRequest from RRC_INACTIVE:

2> ignore the nextHopChainingCount value indicated in the RRCConnectionResume message;

1> else:

2> if resuming an RRC connection from a suspended RRC connection in EPC:

3> update the K_eNB key based on the K_ASME key to which the current K_eNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionResume message, as specified in TS 33.401 [32];

3> store the nextHopChainingCount value;

3> derive the K_RRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401 [32];

3> request lower layers to verify the integrity protection of the RRCConnectionResume message, using the previously configured algorithm and the K_RRCint key;

3> if the integrity protection check of the RRCConnectionResume message fails:

4> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’, upon which the procedure ends;

3> derive the K_RRCenc key and the K_UPenc key associated with the previously configured ciphering algorithm, as specified in TS 33.401 [32];

3> configure lower layers to resume integrity protection using the previously configured algorithm and the K_RRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE;

3> configure lower layers to resume ciphering and to apply the ciphering algorithm, the K_RRCenc key and the K_UPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE;

1> enter RRC_CONNECTED;

1> indicate to upper layers that the suspended RRC connection has been resumed;

1> stop the cell re-selection procedure;

1> consider the current cell to be the PCell;

1> set the content of RRCConnectionResumeComplete message as follows:

2> set the dedicatedInfoNAS to include the information received from upper layers;

2> except for NB-IoT:

3> if resuming an RRC connection from a suspended RRC connection:

4> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

5> include rlf-InfoAvailable;

4> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

5> include logMeasAvailableMBSFN;

4> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

5> include logMeasAvailable;

5> if Bluetooth measurement results are included in the logged measurements the UE has available:

6> include logMeasAvailableBT;

5> if WLAN measurement results are included in the logged measurements the UE has available:

6> include logMeasAvailableWLAN;

4> if the UE has connection establishment failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

5> include connEstFailInfoAvailable;

4> include the mobilityState and set it to the mobility state (as specified in TS 36.304 [4]) of the UE just prior to entering RRC_CONNECTED state;

4> if the UE has flight path information available:

5> include flightPathInfoAvailable;

3> if the UE supports storage of mobility history information and the UE has mobility history information available in VarMobilityHistoryReport:

4> include mobilityHistoryAvail;

3> if the idleModeMeasurementReq is included in the RRCConnectionResume message:

4> if the UE has idle/inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport:

5> set the measResultListIdle-r16 in the RRCConnectionResumeComplete message to the value of measReportIdle-r15 in the VarMeasIdleReport;

5> set the measResultListExtIdle in the RRCConnectionResumeComplete message to the value of measReportIdle-r16 in the VarMeasIdleReport, if available;

5> set the measResultListIdleNR in the RRCConnectionResumeComplete message to the value of measReportIdleNR in the VarMeasIdleReport, if available;

5> discard the VarMeasIdleReport upon successful delivery of the RRCConnectionResumeComplete message is confirmed by lower layers;

3> else:

4> if the SIB2 contains idleModeMeasurements and the UE has E-UTRA idle/inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport; or

4> if the SIB2 contains idleModeMeasurementsNR and the UE has NR idle/inactive measurement information available in VarMeasIdleReport:

5> include the idleMeasAvailable;

3> if the RRCConnectionResume message includes nr-SecondaryCellGroupConfig:

4> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;

2> for NB-IoT:

3> if the UE supports serving cell idle mode measurements reporting and servingCellMeasInfo is present in SystemInformationBlockType2-NB:

4> set the measResultServCell to include the measurements of the serving cell;

3> if the UE is connected to EPC:

4> if the UE has radio link failure information available in VarRLF-Report-NB and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report-NB:

5> include rlf-InfoAvailable;

4> if the UE has ANR measurements information available in VarANR-MeasReport-NB and if the RPLMN is included in plmn-IdentityList stored in VarANR-MeasReport-NB:

5> include anr-InfoAvailable;

2> if the UE is connected to NTN:

3> include gnss-validityDuration in accordance with the remaining time of the GNSS validity duration;

1> if the UE is configured to operate in EN-DC as result of this procedure, forward upperLayerIndication to upper layers as if the UE has received this field from SIB2, otherwise indicate to upper layers the absence of this field;

1> submit the RRCConnectionResumeComplete message to lower layers for transmission;

1> for NB-IoT:

2> if the UE supports connected mode measurements and connMeasConfig is present in SystemInformationBlockType3-NB:

3> perform measurements as specified in 5.5.8.

1> the procedure ends.

5.3.3.4b Reception of the RRCEarlyDataComplete by the UE

The UE shall:

1> indicate to upper layers that the RRC connection has been established;

1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or inherited from another RAT;

1> if stored, discard the altFreqPriorities provided by the RRCConnectionRelease;

1> if stored, discard the dedicated offset provided by the redirectedCarrierOffsetDedicated;

1> stop timer T300;

1> stop timer T302, if running;

1> stop timer T303, if running;

1> stop timer T305, if running;

1> stop timer T306, if running;

1> stop timer T308, if running;

1> perform the actions as specified in 5.3.3.7;

1> stop timer T320, if running;

1> stop timer T322, if running;

1> stop timer T323, if running;

1> forward the dedicatedInfoNAS, if received, to the upper layers;

1> reset MAC and release the MAC configuration;

1> if the RRCEarlyDataComplete message includes redirectedCarrierInfo indicating redirection to geran; and

1> if upper layers indicate that redirect to GERAN without AS security is not allowed:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’, upon which the procedure ends;

1> if the RRCEarlyDataComplete message includes idleModeMobilityControlInfo:

2> store the cell reselection priority information provided by the idleModeMobilityControlInfo;

2> if the t320 is included:

3> start timer T320, with the timer value set according to the value of t320;

1> else:

2> apply the cell reselection priority information broadcast in the system information;

1> for NB-IoT, if the RRCEarlyDataComplete message includes redirectedCarrierInfo:

2> if the redirectedCarrierOffsetDedicated is included in the redirectedCarrierInfo:

3> store the dedicated offset for the frequency in redirectedCarrierInfo;

3> start timer T322, with the timer value set according to the value of T322 in redirectedCarrierInfo;

1> if the extendedWaitTime is present; and

1> if the UE supports delay tolerant access or the UE is a NB-IoT UE:

2> forward the extendedWaitTime to upper layers;

1> indicate the release of the RRC connection to upper layers together with the release cause ‘other’, upon which the procedure ends;

5.3.3.5 Cell re-selection or cell selection while T300, T302, T303, T305, T306, T308 or T309 is running

The UE shall:

1> if cell selection or reselection occurs while T309 or T302 is running and if the UE is connected to 5GC:

2> stop timer T309 for all access categories, if running;

2> if in RRC_INACTIVE and T302 is running:

3> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12 with release cause ‘RRC Resume failure’;

2> else:

3> stop timer T302, if running;

3> perform the actions as specified in 5.3.16.4;

1> if in RRC_INACTIVE:

2> if cell reselection occurs while T300 is running:

3> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12 with release cause ‘RRC Resume failure’;

1> else if cell reselection occurs while T300, T302, T303, T305, T306, or T308 is running:

2> if timer T302, T303, T305, T306, and/or T308 is running and if the UE is connected to EPC:

3> stop timer T302, T303, T305, T306, and T308, whichever ones were running;

3> perform the actions as specified in 5.3.3.7;

2> if timer T300 is running:

3> stop timer T300;

3> if UE has sent RRCConnectionResumeRequest message and has not received RRCConnectionResume message:

4> reset MAC;

4> if UE is resuming an RRC connection after early security reactivation in accordance with conditions in 5.3.3.18:

5> perform the actions as specified in 5.3.3.9a;

4> else:

5> re-establish RLC for all RBs that are established;

5> suspend SRB1;

3> else:

4> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established;

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication;

5.3.3.6 T300 expiry

The UE shall:

1> if timer T300 expires:

2> if UE has sent RRCConnectionResumeRequest message and has not received RRCConnectionResume message:

3> reset MAC;

3> if UE is resuming an RRC connection after early security reactivation in accordance with conditions in 5.3.3.18:

4> perform the actions as specified in 5.3.3.9a;

3> else:

4> re-establish RLC for all RBs that are established;

4> suspend SRB1;

2> else:

3> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established;

2> if the UE is a NB-IoT UE:

3> if connEstFailOffset is included in SystemInformationBlockType2-NB:

4> use connEstFailOffset for the parameter Qoffset_temp for the concerned cell when performing cell selection and reselection according to TS 36.304 [4];

3> else:

4> use value of infinity for the parameter Qoffset_temp for the concerned cell when performing cell selection and reselection according to TS 36.304 [4];

NOTE 0: For NB-IoT, the number of times that the UE detects T300 expiry on the same cell before applying connEstFailOffset and the amount of time that the UE applies connEstFailOffset before removing the offset from evaluation of the cell is up to UE implementation.

2> else if the UE supports RRC Connection Establishment failure temporary Qoffset and T300 has expired a consecutive connEstFailCount times on the same cell for which txFailParams is included in SystemInformationBlockType2:

3> for a period as indicated by connEstFailOffsetValidity:

4> use connEstFailOffset for the parameter Qoffset_temp for the concerned cell when performing cell selection and reselection according to TS 36.304 [4] and TS 25.304 [40];

NOTE 1: When performing cell selection, if no suitable or acceptable cell can be found, it is up to UE implementation whether to stop using connEstFailOffset for the parameter Qoffset_temp during connEstFailOffsetValidity for the concerned cell.

2> except for NB-IoT, store the following connection establishment failure information in the VarConnEstFailReport by setting its fields as follows:

3> clear the information included in VarConnEstFailReport, if any;

3> set the plmn-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]) from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1;

3> set the failedCellId to the global cell identity of the cell where connection establishment failure is detected;

3> set the measResultFailedCell to include the RSRP and RSRQ, if available, of the cell where connection establishment failure is detected and based on measurements collected up to the moment the UE detected the failure;

3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include neighbouring cell measurements for at most the following number of neighbouring cells: 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency/ set of frequencies (GERAN) per RAT and according to the following:

4> for each neighbour cell included, include the optional fields that are available;

NOTE 2: The UE includes the latest results of the available measurements as used for cell reselection evaluation, which are performed in accordance with the performance requirements as specified in TS 36.133 [16].

3> if available, set the logMeasResultListWLAN to include the WLAN measurement results, in order of decreasing RSSI for WLAN APs;

3> if available, set the logMeasResultListBT to include the Bluetooth measurement results, in order of decreasing RSSI for Bluetooth beacons;

3> if detailed location information is available, set the content of the locationInfo as follows:

4> include the locationCoordinates;

4> include the horizontalVelocity, if available;

NOTE 3: Which location information related configuration is used by the UE to make the logMeasResultListWLAN, logMeasResultListBT and locationInfo available for inclusion in the VarConnEstFailReport is left to UE implementation.

3> set the numberOfPreamblesSent to indicate the number of preambles sent by MAC for the failed random access procedure;

3> set contentionDetected to indicate whether contention resolution was not successful as specified in TS 36.321 [6] for at least one of the transmitted preambles for the failed random access procedure;

3> set maxTxPowerReached to indicate whether or not the maximum power level was used for the last transmitted preamble, see TS 36.321 [6];

2> if in RRC_INACTIVE:

3> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12, with release cause ‘RRC Resume failure’;

2> else inform upper layers about the failure to establish the RRC connection or failure to resume the RRC connection with suspend indication, upon which the procedure ends;

The UE may discard the connection establishment failure information, i.e. release the UE variable VarConnEstFailReport, 48 hours after the failure is detected, upon power off or upon detach.

5.3.3.7 T302, T303, T305, T306, or T308 expiry or stop

If the UE is connected to EPC, the UE shall:

1> if timer T302 expires or is stopped:

2> inform upper layers about barring alleviation for mobile terminating access;

2> if timer T303 is not running:

3> inform upper layers about barring alleviation for mobile originating calls;

2> if timer T305 is not running:

3> inform upper layers about barring alleviation for mobile originating signalling;

2> if timer T306 is not running:

3> inform upper layers about barring alleviation for mobile originating CS fallback;

2> if timer T308 is not running:

3> inform upper layers about barring alleviation for ACDC;

1> if timer T303 expires or is stopped:

2> if timer T302 is not running:

3> inform upper layers about barring alleviation for mobile originating calls;

1> if timer T305 expires or is stopped:

2> if timer T302 is not running:

3> inform upper layers about barring alleviation for mobile originating signalling;

1> if timer T306 expires or is stopped:

2> if timer T302 is not running:

3> inform upper layers about barring alleviation for mobile originating CS fallback;

1> if timer T308 expires or is stopped:

2> if timer T302 is not running:

3> inform upper layers about barring alleviation for ACDC;

5.3.3.8 Reception of the RRCConnectionReject by the UE

The UE shall:

1> stop timer T300;

1> stop timer T302, if running;

1> reset MAC;

1> except for NB-IoT, start timer T302, with the timer value set to the waitTime;

1> if the UE is a NB-IoT UE; or

1> if the extendedWaitTime is present and the UE supports delay tolerant access:

2> forward the extendedWaitTime to upper layers;

1> if deprioritisationReq is included and the UE supports RRC Connection Reject with deprioritisation:

2> start or restart timer T325 with the timer value set to the deprioritisationTimer signalled;

2> store the deprioritisationReq until T325 expiry;

NOTE: The UE stores the deprioritisation request irrespective of any cell reselection absolute priority assignments (by dedicated or common signalling) and regardless of RRC connections in E-UTRAN or other RATs unless specified otherwise.

1> if the RRCConnectionReject is received in response to an RRCConnectionResumeRequest sent to resume a suspended RRC connection:

2> if the rrc-SuspendIndication is not present:

3> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP entity for all established or suspended RBs;

3> discard the stored UE AS context and resumeIdentity;

3> inform upper layers about the failure to resume the RRC connection without suspend indication and that access barring for mobile originating calls, mobile originating signalling, mobile terminating access and except for NB-IoT for mobile originating CS fallback is applicable, upon which the procedure ends;

2> else:

3> if the RRCConnectionReject is received in response to an RRCConnectionResumeRequest sent after early security reactivation in accordance with conditions in 5.3.3.18:

4> perform the actions as specified in 5.3.3.9a;

3> else:

4> suspend SRB1;

3> inform upper layers about the failure to resume the RRC connection with suspend indication and that access barring for mobile originating calls, mobile originating signalling, mobile terminating access and except for NB-IoT for mobile originating CS fallback is applicable, upon which the procedure ends;

1> else if the RRCConnectionReject is received in response to an RRCConnectionResumeRequest sent while in RRC_INACTIVE:

2> release the default MAC configuration;

2> if RRCConnectionReject is received in response to a request from upper layers:

3> inform the upper layer that access barring is applicable for all access categories except categories ‘0’ and ‘2’;

2> if RRCConnectionReject is received in response to an RRCConnectionResumeRequest:

3> if resume is triggered by upper layers:

4> inform upper layers about the failure to resume the RRC connection;

3> if resume is triggered due to an RNA update:

4> set the variable pendingRnaUpdate to ‘TRUE’;

3> discard the current K_eNB, K_RRCenc key, K_RRCint, K_UPint key and K_UPenc key;

3> suspend SRB1, upon which the procedure ends;

2> The UE shall continue to monitor RAN and CN paging while the timer T302 is running.

1> else:

2> release the default MAC configuration;

2> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls, mobile originating signalling, mobile terminating access and except for NB-IoT, for mobile originating CS fallback is applicable, upon which the procedure ends;

5.3.3.9 Abortion of RRC connection establishment

If upper layers abort the RRC connection establishment procedure while the UE has not yet entered RRC_CONNECTED, the UE shall:

1> stop timer T300, if running;

1> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established;

5.3.3.9a Abortion of early security reactivation

The UE shall:

1> delete the K_eNB, K_RRCint, K_RRCenc and K_UPenc keys derived in accordance with 5.3.3.3a;

1> re-establish RLC entities for all SRBs and DRBs;

1> suspend all SRB(s) and DRB(s) except SRB0;

1> configure lower layers to suspend integrity protection and ciphering.

5.3.3.10 Handling of SSAC related parameters

Upon request from the upper layers, the UE shall:

2> select the AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers;

1> else:

2> in the remainder of this procedure use the common access barring parameters (i.e. presence or absence of these parameters) included in SystemInformationBlockType2;

1> set the local variables BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice as follows:

2> if ssac-BarringForMMTEL-Voice is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Voice is set to zero:

4> set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

3> else:

4> set BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Voice, respectively;

2> else set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

1> set the local variables BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video as follows:

2> if ssac-BarringForMMTEL-Video is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Video is set to zero:

4> set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

3> else:

4> set BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Video, respectively;

2> else set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

1> forward the variables BarringFactorForMMTEL-Voice, BarringTimeForMMTEL-Voice, BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the upper layers;

5.3.3.11 Access barring check

1> if timer T302 or "Tbarring" is running:

2> consider access to the cell as barred;

1> else if SystemInformationBlockType2 includes "AC barring parameter":

2> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

2> for at least one of these valid Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in "AC barring parameter" is set to zero:

3> consider access to the cell as not barred;

2> else if the establishment of the RRC connection is the result of release with redirect with mpsPriorityIndication (either in NR or E-UTRAN); and

2> if the corresponding bit for any of the Access Classes 12, 13 or 14 in the ac-BarringForSpecialAC contained in "AC barring parameter" is set to zero:

3> consider access to the cell as not barred;

2> else:

3> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

3> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in "AC barring parameter":

4> consider access to the cell as not barred;

3> else:

4> consider access to the cell as barred;

1> else:

2> consider access to the cell as not barred;

1> if access to the cell is barred and both timers T302 and "Tbarring" are not running:

2> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

2> start timer "Tbarring" with the timer value calculated as follows, using the ac-BarringTime included in "AC barring parameter":

"Tbarring" = (0.7+ 0.6 _* rand) _* ac-BarringTime;

5.3.3.12 EAB check

The UE shall:

1> if SystemInformationBlockType14 is present:

2> if eab-PerRSRP is included:

3> if the establishmentCause received from higher layers is set to a value other than emergency; and

3> if the UE has no Access Class, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11] :

4> if eab-PerRSRP is set to thresh0:

5> consider access to the cell as barred when in enhanced coverage as specified in TS 36.304 [4];

4> else if eab-PerRSRP is set to thresh1:

5> if the measured RSRP is less than the first entry in rsrp-ThresholdsPrachInfoList:

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first CE level are configured;

4> else if eab-PerRSRP is set to thresh2:

5> if the measured RSRP is less than the second entry in rsrp-ThresholdsPrachInfoList:

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first and second CE levels are configured;

4> else if eab-PerRSRP is set to thresh3:

5> if the measured RSRP is less than the third entry in rsrp-ThresholdsPrachInfoList:

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first, second, and third CE levels are configured;

2> if access to the cell is not barred due to eab-PerRSRP and eab-Param is included:

3> if the eab-Common is included in the eab-Param:

4> if the UE belongs to the category of UEs as indicated in the eab-Category contained in eab-Common; and

4> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the corresponding bit in the eab-BarringBitmap contained in eab-Common is set to one:

5> consider access to the cell as barred;

4> else:

5> consider access to the cell as not barred due to EAB;

3> else (the eab-PerPLMN-List is included in the eab-Param):

4> select the entry in the eab-PerPLMN-List corresponding to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]);

4> if the eab-Config for that PLMN is included:

5> if the UE belongs to the category of UEs as indicated in the eab-Category contained in eab-Config; and

5> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the corresponding bit in the eab-BarringBitmap contained in eab-Config is set to one:

6> consider access to the cell as barred;

5> else:

6> consider access to the cell as not barred due to EAB;

4> else:

5> consider access to the cell as not barred due to EAB;

1> else:

2> consider access to the cell as not barred due to EAB;

5.3.3.13 Access barring check for ACDC

The UE shall:

1> if timer T302 is running:

2> consider access to the cell as barred;

1> else if SystemInformationBlockType2 includes "ACDC barring parameter":

2> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

2> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in "ACDC barring parameter":

3> consider access to the cell as not barred;

2> else:

3> consider access to the cell as barred;

1> else:

2> consider access to the cell as not barred;

1> if access to the cell is barred and timer T302 is not running:

2> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

2> start timer "Tbarring" with the timer value calculated as follows, using the ac-BarringTime included in "ACDC barring parameter":

"Tbarring" = (0.7+ 0.6 _* rand) _* ac-BarringTime.

5.3.3.14 Access Barring check for NB-IoT

The UE shall:

1> if the UE is connected to 5GC, ab-Enabled-5GC included in MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is set to TRUE and SystemInformationBlockType14-NB is broadcast, or

1> if the UE is connected to EPC, ab-Enabled included in MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is set to TRUE and SystemInformationBlockType14-NB is broadcast:

2> if ab-PerNRSRP is included:

3> if the establishmentCause received from higher layers is set to a value other than mo-ExceptionData; and

3> if the UE has no Access Class, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11]:

4> if ab-PerNRSRP is set to thresh1:

5> if the measured RSRP is less than the first entry in rsrp-ThresholdsPrachInfoList;

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first NPRACH repetition level are configured;

4> if ab-PerNRSRP is set to thresh2:

5> if the measured RSRP is less than the second entry in rsrp-ThresholdsPrachInfoList;

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first and second NPRACH repetition levels are configured;

1> if the UE is connected to EPC, ab-Enabled included in MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is set to TRUE and SystemInformationBlockType14-NB is broadcast:

2> if access to the cell is not barred due to ab-PerNRSRP and ab-Param is included:

3> if the ab-Common is included in ab-Param:

4> if the UE belongs to the category of UEs as indicated in the ab-Category contained in ab-Common; and

4> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the corresponding bit in the ab-BarringBitmap contained in ab-Common is set to one:

5> if the establishmentCause received from higher layers is set to mo-ExceptionData and ab-BarringForExceptionData is set to FALSE in the ab-Common:

6> consider access to the cell as not barred;

5> else:

6> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11] and for at least one of these valid Access Classes for the UE, the corresponding bit in the ab-BarringForSpecialAC contained in ab-Common is set to zero:

NOTE 1: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

7> consider access to the cell as not barred;

6> else:

7> consider access to the cell as barred;

4> else:

5> consider access to the cell as not barred;

3> else (the ab-PerPLMN-List is included in the ab-Param):

4> select the ab-PerPLMN entry in ab-PerPLMN-List corresponding to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]);

4> if the ab-Config for that PLMN is included:

5> if the UE belongs to the category of UEs as indicated in the ab-Category contained in ab-Config; and

5> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the corresponding bit in the ab-BarringBitmap contained in ab-Config is set to one:

6> if the establishmentCause received from higher layers is set to mo-ExceptionData and ab-BarringForExceptionData is set to FALSE in the ab-Config:

7> consider access to the cell as not barred;

6> else:

7> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11] and for at least one of these valid Access Classes for the UE, the corresponding bit in the ab-BarringForSpecialAC contained in ab-Config is set to zero:

NOTE 2: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

8> consider access to the cell as not barred;

7> else:

8> consider access to the cell as barred;

5> else:

6> consider access to the cell as not barred;

4> else:

5> consider access to the cell as not barred;

1> else:

2> consider access to the cell as not barred;

5.3.3.15 Failure to deliver NAS information in RRCConnectionSetupComplete message

The UE shall:

1> if the UE is a NB-IoT UE and radio link failure occurs before the successful delivery of RRCConnectionSetupComplete message has been confirmed by lower layers:

2> inform upper layers about the possible failure to deliver the NAS information contained in the RRCConnectionSetupComplete message;

5.3.3.16 Integrity check failure from lower layers while T300 is running

The UE shall:

1> upon receiving integrity check failure indication from lower layers concerning SRB1 or SRB2 while T300 is running and if the UE is resuming the RRC connection after early security reactivation in accordance with conditions in 5.3.3.18:

2> discard the stored UE AS context and resumeIdentity;

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;

1> upon receiving integrity check failure indication from lower layers while T300 is running and if the UE is resuming the RRC connection from RRC_INACTIVE:

2> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12, with release cause ‘RRC Resume failure’;

5.3.3.17 Inability to comply with RRCConnectionResume

The UE shall:

1> if the UE is unable to comply with (part of) the configuration included in the RRCConnectionResume message;

2> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12 with release cause ‘RRC Resume failure’.

NOTE 1: The UE may apply above failure handling also in case the RRCConnectionResume message causes a protocol error for which the generic error handling as defined in 5.7 specifies that the UE shall ignore the message.

NOTE 2: If the UE is unable to comply with part of the configuration, it does not apply any part of the configuration, i.e. there is no partial success/failure.

5.3.3.18 Early security reactivation

The UE shall use early security reactivation when resuming a suspended RRC connection and at least one of the following conditions is met:

– the UE is initiating UP-EDT in accordance with conditions in 5.3.3.1b;

– the UE is initiating UP transmission using PUR in accordance with conditions in 5.3.3.1c;

– the UE is resuming a suspended RRC connection in 5GC;

– the UE supports early security reactivation, SystemInformationBlockType2 (SystemInformationBlockType2-NB in NB-IoT) includes earlySecurityReactivation, and the UE has a stored value of the nextHopChainingCount provided in the RRCConnectionRelease message with suspend indication during the preceding suspend procedure;

5.3.3.19 Timing alignment validation for transmission using PUR

The UE shall consider the timing alignment value for transmission using PUR to be valid when the following conditions are fulfilled:

1> either pur-TimeAlignmentTimer is not configured or pur-TimeAlignmentTimer is running as confirmed by lower layers; and

1> either pur-RSRP-ChangeThreshold (pur-NRSRP-ChangeThreshold in NB-IoT) is not configured or the following conditions are fulfilled:

2> compared to the stored serving cell reference (N)RSRP value, the serving cell (N)RSRP has not increased by more than increaseThresh; and

2> compared to the stored serving cell reference (N)RSRP value, the serving cell (N)RSRP has not decreased by more than decreaseThresh;

5.3.3.20 Maintenance of PUR occasions

The UE configured with pur-Config shall:

1> consider that the first PUR occasion occurs at the H-SFN/SFN/subframe given by:

– H-SFN = (H-SFN_Ref + offset) mod 1024 occuring after FLOOR (offset/1024) H-SFN cycles;

– SFN and subframe indicated by startSFN and startSubframe;

where:

– offset is given by periodicityAndOffset;

– H-SFN_Ref corresponds to the last subframe of the first transmission of RRCConnectionRelease message containing pur-Config, taking into account hsfn-LSB-Info;

– H-SFN cycle corresponds to the duration of 1024 H-SFNs;

1> if the pur-NumOccasions is set to one, for the first PUR occasion:

2> if transmission using PUR in accordance with conditions in 5.3.3.1c is not initiated; or

2> if transmission using PUR in accordance with conditions in 5.3.3.1c has been initiated, after the completion of the transmission using PUR:

3> if pur-TimeAlignmentTimer is configured, indicate to lower layers that pur-TimeAlignmentTimer is released;

3> release pur-Config;

3> discard previously stored pur-Config;

1> else:

2> consider that the subsequent PUR occasions occur periodically after the occurence of the first PUR occasion at the SFN/subframe indicated by startSubframe and startSFN and periodicity given by periodicityAndOffset;

2> if the pur-ImplicitReleaseAfter is configured, for each PUR occasion occurring while the UE is in RRC_IDLE:

3> if transmission using PUR in accordance with conditions in 5.3.3.1c is not initiated; or

3> if PUR failure indication is received from lower layers:

4> consider the PUR occasion as skipped;

4> if pur-ImplicitReleaseAfter number of consecutive PUR occasions have been skipped:

5> if pur-TimeAlignmentTimer is configured, indicate to lower layers that pur-TimeAlignmentTimer is released;

5> release pur-Config;

5> discard previously stored pur-Config.

5.3.3.21 UE actions upon indication of out-of-date GNSS position

Upon indication that the GNSS position has become out-of-date while in RRC_CONNECTED, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’.

5.3.3.1 General

5.3.3.1a Conditions for establishing RRC Connection for sidelink communication/ discovery/ V2X sidelink communication/ NR sidelink communication

5.3.3.1b Conditions for initiating EDT

5.3.3.1c Conditions for initiating transmission using PUR

5.3.3.1d Condition for establishing RRC Connection in NTN

5.3.3.2 Initiation

5.3.3.3 Actions related to transmission of RRCConnectionRequest message

5.3.3.3a Actions related to transmission of RRCConnectionResumeRequest message

5.3.3.3b Actions related to transmission of RRCEarlyDataRequest message

5.3.3.3c UE actions upon receiving EDT fallback indication from lower layers

5.3.3.4 Reception of the RRCConnectionSetup by the UE

5.3.3.4a Reception of the RRCConnectionResume by the UE

5.3.3.4b Reception of the RRCEarlyDataComplete by the UE

5.3.3.5 Cell re-selection or cell selection while T300, T302, T303, T305, T306, T308 or T309 is running

5.3.3.6 T300 expiry

5.3.3.7 T302, T303, T305, T306, or T308 expiry or stop

5.3.3.8 Reception of the RRCConnectionReject by the UE

5.3.3.9 Abortion of RRC connection establishment

5.3.3.9a Abortion of early security reactivation

5.3.3.10 Handling of SSAC related parameters

5.3.3.11 Access barring check

5.3.3.12 EAB check

5.3.3.13 Access barring check for ACDC

5.3.3.14 Access Barring check for NB-IoT

5.3.3.15 Failure to deliver NAS information in RRCConnectionSetupComplete message

5.3.3.16 Integrity check failure from lower layers while T300 is running

5.3.3.17 Inability to comply with RRCConnectionResume

5.3.3.18 Early security reactivation

5.3.3.19 Timing alignment validation for transmission using PUR

5.3.3.20 Maintenance of PUR occasions

5.3.3.21 UE actions upon indication of out-of-date GNSS position

5.3.3.22 Void