5.3.13 RRC connection resume

38.3313GPPNRProtocol specificationRadio Resource Control (RRC)Release 17TS

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

5.3.13.1 General

Figure 5.3.13.1-1: RRC connection resume, successful

Figure 5.3.13.1-2: RRC connection resume fallback to RRC connection establishment, successful

Figure 5.3.13.1-3: RRC connection resume followed by network release, successful

Figure 5.3.13.1-4: RRC connection resume followed by network suspend, successful

Figure 5.3.13.1-5: RRC connection resume, network reject

The purpose of this procedure is to resume a suspended RRC connection, including resuming SRB(s), DRB(s) and multicast MRB(s) or perform an RNA update. This procedure is also used to initiate SDT in RRC_INACTIVE.

5.3.13.1a Conditions for resuming RRC Connection for NR sidelink communication/discovery/V2X sidelink communication

For NR sidelink communication/discovery an RRC connection is resumed only in the following cases:

1> if configured by upper layers to transmit NR sidelink communication/discovery and related data is available for transmission:

2> if the frequency on which the UE is configured to transmit NR sidelink communication is included in sl-FreqInfoList within SIB12 provided by the cell on which the UE camps; and if the valid version of SIB12 does not include sl-TxPoolSelectedNormal for the concerned frequency; or

2> if the frequency on which the UE is configured to transmit NR sidelink discovery is included in sl-FreqInfoList within SIB12 provided by the cell on which the UE camps; and if the valid version of SIB12 does not include sl-DiscTxPoolSelected or sl-TxPoolSelectedNormal for the concerned frequency;

For L2 U2N Relay UE in RRC_INACTIVE, an RRC connection establishment is resumed in the following cases:

1> if any message is received from the L2 U2N Remote UE via SL-RLC0 as specified in 9.1.1.4 or SL-RLC1 as specified in 9.2.4;

For V2X sidelink communication an RRC connection resume is initiated only when the conditions specified for V2X sidelink communication in clause 5.3.3.1a of TS 36.331 [10] are met.

NOTE: Upper layers initiate an RRC connection resume (except if the RRC connection resume is initiated at the L2 U2N Relay UE upon reception of a message from a L2 U2N Remote UE via SL-RLC0 or SL-RLC1). The interaction with NAS is left to UE implementation.

5.3.13.1b Conditions for initiating SDT

A UE in RRC_INACTIVE initiates the resume procedure for SDT when all of the following conditions are fulfilled:

1> the upper layers request resumption of RRC connection; and

1> SIB1 includes sdt-ConfigCommon; and

1> sdt-Config is configured; and

1> all the pending data in UL is mapped to the radio bearers configured for SDT; and

1> lower layers indicate that conditions for initiating SDT as specified in TS 38.321 [3] are fulfilled.

NOTE: How the UE determines that all pending data in UL is mapped to radio bearers configured for SDT is left to UE implementation.

5.3.13.2 Initiation

The UE initiates the procedure when upper layers or AS (when responding to RAN paging, upon triggering RNA updates while the UE is in RRC_INACTIVE, for NR sidelink communication/discovery/V2X sidelink communication as specified in clause 5.3.13.1a) requests the resume of a suspended RRC connection or requests the resume for initiating SDT as specified in clause 5.3.13.1b.

The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure.

Upon initiation of the procedure, the UE shall:

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.14 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.14 using the Access Category and Access Identities provided by upper layers;

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

2> if the resumption occurs after release with redirect with mpsPriorityIndication:

3> set the resumeCause to mps-PriorityAccess;

2> else:

3> 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 RNA update as specified in 5.3.13.8:

2> if an emergency service is ongoing:

NOTE 1: How the RRC layer in the UE is aware of an ongoing emergency service is up to UE implementation.

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.14 using the selected Access Category and one or more Access Identities to be applied as specified in TS 24.501 [23];

3> if the access attempt is barred:

4> set the variable pendingRNA-Update to true;

4> the procedure ends;

NOTE 2: In case the L2 U2N Relay UE initiates RRC connection resume triggered by reception of message from a L2 U2N Remote UE via SL-RLC0 or SL-RLC1 as specified in 5.3.13.1a, the L2 U2N Relay UE sets the resumeCause by implementation, but it can only set the emergency, mps-PriorityAccess, or mcs-PriorityAccess as resumeCause, if the same cause value in the message received from the L2 U2N Remote UE via SL-RLC0.

1> if the UE is in NE-DC or NR-DC:

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

3> release the MR-DC related configurations (i.e., as specified in 5.3.5.10) from the UE Inactive AS context, if stored;

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

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

1> if the UE is acting as L2 U2N Remote UE:

2> establish a SRAP entity as specified in TS 38.351 [66], if no SRAP entity has been established;

2> apply the default configuration of SL-RLC1 as defined in 9.2.4 for SRB1;

2> apply the default PDCP configuration as defined in 9.2.1 for SRB1;

2> apply the default configuration of SRAP as defined in 9.2.5 for SRB1;

1> else:

2> apply the default L1 parameter values as specified in corresponding physical layer specifications, except for the parameters for which values are provided in SIB1;

2> apply the default SRB1 configuration as specified in 9.2.1;

2> apply the default MAC Cell Group configuration as specified in 9.2.2;

1> release delayBudgetReportingConfig from the UE Inactive AS context, if stored;

1> stop timer T342, if running;

1> release overheatingAssistanceConfig from the UE Inactive AS context, if stored;

1> stop timer T345, if running;

1> release idc-AssistanceConfig from the UE Inactive AS context, if stored;

1> release drx-PreferenceConfig for all configured cell groups from the UE Inactive AS context, if stored;

1> stop all instances of timer T346a, if running;

1> release maxBW-PreferenceConfig for all configured cell groups from the UE Inactive AS context, if stored;

1> stop all instances of timer T346b, if running;

1> release maxCC-PreferenceConfig for all configured cell groups from the UE Inactive AS context, if stored;

1> stop all instances of timer T346c, if running;

1> release maxMIMO-LayerPreferenceConfig for all configured cell groups from the UE Inactive AS context, if stored;

1> stop all instances of timer T346d, if running;

1> release minSchedulingOffsetPreferenceConfig for all configured cell groups from the UE Inactive AS context, if stored;

1> stop all instances of timer T346e, if running;

1> release rlm-RelaxationReportingConfig for all configured cell groups from the UE Inactive AS context, if stored;

1> stop all instances of timer T346j, if running;

1> release bfd-RelaxationReportingConfig for all configured cell groups from the UE Inactive AS context, if stored;

1> stop all instances of timer T346k, if running;

1> release releasePreferenceConfig from the UE Inactive AS context, if stored;

1> release wlanNameList from the UE Inactive AS context, if stored;

1> release btNameList from the UE Inactive AS context, if stored;

1> release sensorNameList from the UE Inactive AS context, if stored;

1> release obtainCommonLocation from the UE Inactive AS context, if stored;

1> stop timer T346f, if running;

1> stop timer T346i, if running;

1> release referenceTimePreferenceReporting from the UE Inactive AS context, if stored;

1> release sl-AssistanceConfigNR from the UE Inactive AS context, if stored;

1> release musim-GapAssistanceConfig from the UE Inactive AS context, if stored and stop timer T346h, if running;

1> release musim-GapConfig from the UE Inactive AS context, if stored;

1> release musim-LeaveAssistanceConfig from the UE Inactive AS context, if stored;

1> release propDelayDiffReportConfig from the UE Inactive AS context, if stored;

1> release ul-GapFR2-PreferenceConfig, if configured;

1> release rrm-MeasRelaxationReportingConfig from the UE Inactive AS context, if stored;

1> if the UE is acting as L2 U2N Remote UE:

2> apply the specified configuration of SL-RLC0 used for the delivery of RRC message over SRB0 as specified in 9.1.1.4;

2> apply the SDAP configuration and PDCP configuration as specified in 9.1.1.2 for SRB0;

1> else:

2> apply the CCCH configuration as specified in 9.1.1.2;

2> apply the timeAlignmentTimerCommon included in SIB1;

1> if sdt-MAC-PHY-CG-Config is configured:

2> if the resume procedure is initiated in a cell that is different to the PCell in which the UE received the stored sdt-MAC-PHY-CG-Config:

3> release the stored sdt-MAC-PHY-CG-Config;

3> instruct the MAC entity to stop the cg-SDT-TimeAlignmentTimer, if it is running;

1> if conditions for initiating SDT in accordance with 5.3.13.1b are fulfilled:

2> consider the resume procedure is initiated for SDT;

2> start timer T319a when the lower layers first transmit the CCCH message;

2> consider SDT procedure is ongoing;

1> else:

2> start timer T319;

2> instruct the MAC entity to stop the cg–SDT–TimeAlignmentTimer, if it is running;

1> if ta-Report is configured with value enabled and the UE supports TA reporting:

2> indicate TA report initiation to lower layers;

1> set the variable pendingRNA-Update to false;

1> release successHO-Config from the UE Inactive AS context, if stored;

1> initiate transmission of the RRCResumeRequest message or RRCResumeRequest1 in accordance with 5.3.13.3.

5.3.13.3 Actions related to transmission of RRCResumeRequest or RRCResumeRequest1 message

The UE shall set the contents of RRCResumeRequest or RRCResumeRequest1 message as follows:

1> if field useFullResumeID is signalled in SIB1:

2> select RRCResumeRequest1 as the message to use;

2> set the resumeIdentity to the stored fullI-RNTI value;

1> else:

2> select RRCResumeRequest as the message to use;

2> set the resumeIdentity to the stored shortI-RNTI value;

1> restore the RRC configuration, RoHC state, the EHC context(s), the UDC state, the stored QoS flow to DRB mapping rules and the K_gNB and K_RRCint keys from the stored UE Inactive AS context except for the following:

– masterCellGroup;

– mrdc-SecondaryCellGroup, if stored; and

– pdcp-Config;

1> set the resumeMAC-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) VarResumeMAC-Input;

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

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

1> derive the K_gNB key based on the current K_gNB key or the NH, using the nextHopChainingCount value received in the previous RRCRelease message and stored in the UE Inactive AS Context, as specified in TS 33.501 [11];

1> derive the K_RRCenc key, the K_RRCint key, the K_UPint key and the K_UPenc key;

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

NOTE 1: Only DRBs with previously configured UP integrity protection shall resume integrity protection.

1> configure lower layers to apply ciphering for all radio bearers except SRB0 and MRBs 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;

1> re-establish PDCP entities for SRB1;

1> resume SRB1;

1> if the resume procedure is initiated for SDT:

2> for each radio bearer that is configured for SDT and for SRB1:

3> restore the RLC-BearerConfig associated with the RLC bearers of masterCellGroup and pdcp-Config from the UE Inactive AS context;

3> if the radio bearer is a DRB configured with Ethernet Header Compression:

4> indicate to lower layer that ethernetHeaderCompression is not configured;

3> if the radio bearer is a DRB configured with UDC:

4> indicate to lower layer that uplinkDataCompression is not configured;

3> if the radio bearer is a DRB configured with ROHC function:

4> if sdt-DRB-ContinueROHC is set to cell and the resume procedure is initiated in a cell that is the same as the PCell in which the UE received the previous RRCRelease message; or

4> if sdt-DRB-ContinueROHC is set to rna and the resume procedure is initiated in a cell belonging to the same RNA as the PCell in which the UE received the previous RRCRelease message:

5> indicate to lower layer that drb-continueROHC is configured;

4> else:

5> indicate to lower layer that drb-continueROHC is not configured;

3> re-establish PDCP entity for the radio bearer that is configured for SDT without triggering PDCP status report;

2> resume all the radio bearers that are configured for SDT;

1> submit the selected message RRCResumeRequest or RRCResumeRequest1 for transmission to lower layers.

NOTE 2: Only DRBs with previously configured UP ciphering shall resume ciphering.

If lower layers indicate an integrity check failure while T319 is running or SDT procedure is ongoing, perform actions specified in 5.3.13.5.

If the UE is a RedCap UE and the RedCap-specific initial downlink BWP is not associated with CD-SSB, the UE may continue cell re-selection related measurements as well as cell re-selection evaluation, otherwise 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.13.6.

NOTE 3: For L2 U2N Remote UE in RRC_INACTIVE, the cell (re)selection procedure as specified in TS 38.304 [20] and relay (re)selection procedure as specified in 5.8.15.3 are performed independently and it is up to UE implementation to select either a cell or a L2 U2N Relay UE.

5.3.13.4 Reception of the RRCResume by the UE

The UE shall:

1> stop timer T319, if running;

1> stop timer T319a, if running and consider SDT procedure is not ongoing;

1> stop timer T380, if running;

1> if T331 is running:

2> stop timer T331;

2> perform the actions as specified in 5.7.8.3;

1> if the RRCResume includes the fullConfig:

2> perform the full configuration procedure as specified in 5.3.5.11;

1> else:

2> if the RRCResume does not include the restoreMCG-SCells:

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

2> if the RRCResume does not include the restoreSCG:

3> release the MR-DC related configurations (i.e., as specified in 5.3.5.10) from the UE Inactive AS context, if stored;

2> restore the masterCellGroup, mrdc-SecondaryCellGroup, if stored, and pdcp-Config from the UE Inactive AS context;

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

1> discard the UE Inactive AS context;

1> store the used nextHopChainingCount value associated to the current K_gNB;

1> if sdt-MAC-PHY-CG-Config is configured:

2> instruct the MAC entity to stop the cg-SDT-TimeAlignmentTimer, if it is running;

2> instruct the MAC entity to start the timeAlignmentTimer associated with the PTAG, if it is not running;

1> if srs-PosRRC-InactiveConfig is configured:

2> instruct the MAC entity to stop inactivePosSRS-TimeAlignmentTimer, if it is running;

1> release the suspendConfig except the ran-NotificationAreaInfo;

1> if the RRCResume includes the masterCellGroup:

2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;

1> if the RRCResume includes the mrdc-SecondaryCellGroup:

2> if the received mrdc-SecondaryCellGroup is set to nr-SCG:

3> perform the RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG;

2> if the received mrdc-SecondaryCellGroup is set to eutra-SCG:

3> perform the RRC connection reconfiguration as specified in TS 36.331 [10], clause 5.3.5.3 for the RRCConnectionReconfiguration message included in eutra-SCG;

1> if the RRCResume includes the radioBearerConfig:

2> perform the radio bearer configuration according to 5.3.5.6;

1> if the RRCResume message includes the sk-Counter:

2> perform security key update procedure as specified in 5.3.5.7;

1> if the RRCResume message includes the radioBearerConfig2:

2> perform the radio bearer configuration according to 5.3.5.6;

1> if the RRCResume message includes the needForGapsConfigNR:

2> if needForGapsConfigNR is set to setup:

3> consider itself to be configured to provide the measurement gap requirement information of NR target bands;

2> else:

3> consider itself not to be configured to provide the measurement gap requirement information of NR target bands;

1> if the RRCResume message includes the needForGapNCSG-ConfigNR:

2> if needForGapNCSG-ConfigNR is set to setup:

3> consider itself to be configured to provide the measurement gap and NCSG requirement information of NR target bands;

2> else:

3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of NR target bands;

1> if the RRCResume message includes the needForGapNCSG-ConfigEUTRA:

2> if needForGapNCSG-ConfigEUTRA is set to setup:

3> consider itself to be configured to provide the measurement gap and NCSG requirement information of E‑UTRA target bands;

2> else:

3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of E‑UTRA target bands;

1> if the RRCResume message includes the appLayerMeasConfig:

2> perform the application layer measurement configuration procedure as specified in 5.3.5.13d;

1> if the RRCResume message includes the sl-L2RemoteUE-Config (i.e. the UE is a L2 U2N Remote UE):

2> perform the L2 U2N Remote UE configuration procedure as specified in 5.3.5.16;

1> if the RRCResume message includes the sl-ConfigDedicatedNR:

2> perform the sidelink dedicated configuration procedure as specified in 5.3.5.14;

1> resume SRB2 (if suspended), SRB3 (if configured), SRB4 (if configured), all DRBs (that are suspended) and multicast MRBs;

NOTE 1: If the 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 cellReselectionPriorities or inherited from another RAT;

1> stop timer T320, if running;

1> if the RRCResume message includes the measConfig:

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

1> resume measurements if suspended;

1> if T390 is running:

2> stop timer T390 for all access categories;

2> perform the actions as specified in 5.3.14.4;

1> if T302 is running:

2> stop timer T302;

2> perform the actions as specified in 5.3.14.4;

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> stop relay reselection procedure if any for L2 U2N Remote UE;

1> consider the current cell to be the PCell;

1> set the content of the of RRCResumeComplete message as follows:

2> if the upper layer provides NAS PDU, set the dedicatedNAS-Message to include the information received from upper layers;

2> if upper layers provides a PLMN:

3> if the UE is either allowed or instructed to access the PLMN via a cell for which at least one CAG ID is broadcast:

4> set the selectedPLMN-Identity from the npn-IdentityInfoList;

3> else:

4> set the selectedPLMN-Identity to the PLMN selected by upper layers from the plmn-IdentityInfoList;

2> if the masterCellGroup contains the reportUplinkTxDirectCurrent:

3> include the uplinkTxDirectCurrentList for each MCG serving cell with UL;

3> include uplinkDirectCurrentBWP-SUL for each MCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList;

2> if the masterCellGroup contains the reportUplinkTxDirectCurrentTwoCarrier:

3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured uplink carrier aggregation in the MCG;

2> if the masterCellGroup contains the reportUplinkTxDirectCurrentMoreCarrier:

3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured uplink carrier aggregation in the MCG;

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

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

4> set the measResultIdleEUTRA in the RRCResumeComplete message to the value of measReportIdleEUTRA in the VarMeasIdleReport, if available;

4> set the measResultIdleNR in the RRCResumeComplete message to the value of measReportIdleNR in the VarMeasIdleReport, if available;

4> discard the VarMeasIdleReport upon successful delivery of the RRCResumeComplete message is confirmed by lower layers;

3> else:

4> if the SIB1 contains idleModeMeasurementsNR and the UE has NR idle/inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport; or

4> if the SIB1 contains idleModeMeasurementsEUTRA and the UE has E-UTRA idle/inactive measurement information available in VarMeasIdleReport:

5> include the idleMeasAvailable;

2> if the RRCResume message includes mrdc-SecondaryCellGroup set to eutra-SCG:

3> include in the eutra-SCG-Response the E-UTRA RRCConnectionReconfigurationComplete message in accordance with TS 36.331 [10] clause 5.3.5.3;

2> if the RRCResume message includes mrdc-SecondaryCellGroup set to nr-SCG:

3> include in the nr-SCG-Response the SCG RRCReconfigurationComplete message;

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

3> include the logMeasAvailable in the RRCResumeComplete message;

3> if Bluetooth measurement results are included in the logged measurements the UE has available for NR:

4> include the logMeasAvailableBT in the RRCResumeComplete message;

3> if WLAN measurement results are included in the logged measurements the UE has available for NR:

4> include the logMeasAvailableWLAN in the RRCResumeComplete message;

2> if the sigLoggedMeasType in VarLogMeasReport is included:

3> if T330 timer is running and the logged measurements configuration is for NR:

4> set sigLogMeasConfigAvailable to true in the RRCResumeComplete message;

3> else:

4> if the UE has logged measurements available for NR:

5> set sigLogMeasConfigAvailable to false in the RRCResumeComplete message;

2> if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList:

3> include connEstFailInfoAvailable in the RRCResumeComplete message;

2> 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; or

2> if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331 [10] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331 [10]:

3> include rlf-InfoAvailable in the RRCResumeComplete message;

2> if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report:

3> include successHO-InfoAvailable in the RRCResumeComplete message;

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

3> include the mobilityHistoryAvail in the RRCResumeComplete message;

2> if speedStateReselectionPars is configured in the SIB2:

3> include the mobilityState in the RRCResumeComplete message and set it to the mobility state (as specified in TS 38.304 [20]) of the UE just prior to entering RRC_CONNECTED state;

2> if the UE is configured to provide the measurement gap requirement information of NR target bands:

3> include the NeedForGapsInfoNR and set the contents as follows:

4> include intraFreq-needForGap and set the gap requirement information of intra-frequency measurement for each NR serving cell;

4> if requestedTargetBandFilterNR is configured, for each supported NR band that is also included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band; otherwise, include an entry in interFreq-needForGap and set the corresponding gap requirement information for each supported NR band;

2> if the UE is configured to provide the measurement gap and NCSG requirement information of NR target bands:

3> include the NeedForGapNCSG-InfoNR and set the contents as follows:

4> include intraFreq-needForNCSG and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell;

4> if requestedTargetBandFilterNCSG-NR is configured:

5> for each supported NR band included in requestedTargetBandFilterNCSG-NR, include an entry in interFreq-needForNCSG and set the NCSG requirement information for that band;

4> else:

5> include an entry for each supported NR band in interFreq-needForNCSG and set the corresponding NCSG requirement information;

2> if the UE is configured to provide the measurement gap and NCSG requirement information of E‑UTRA target bands:

3> include the NeedForGapNCSG-InfoEUTRA and set the contents as follows:

4> if requestedTargetBandFilterNCSG-EUTRA is configured:

5> for each supported E-UTRA band included in requestedTargetBandFilterNCSG-EUTRA, include an entry in needForNCSG-EUTRA and set the NCSG requirement information for that band;

4> else:

5> include an entry for each supported E-UTRA band in needForNCSG-EUTRA and set the corresponding NCSG requirement information;

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

1> the procedure ends.

NOTE 2: Network only configures at most one of reportUplinkTxDirectCurrent, reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier in one RRC message.

5.3.13.5 Handling of failure to resume RRC Connection

The UE shall:

1> if timer T319 expires:

2> if the UE supports multiple CEF report:

3> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-identity stored in VarConnEstFailReport; and

3> if the cell identity of current cell is not equal to the cell identity stored in measResultFailedCell in VarConnEstFailReport and if the maxCEFReport-r17 has not been reached:

4> append the VarConnEstFailReport as a new entry in the VarConnEstFailReportList;

2> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport and if the RPLMN is not equal to plmn-identity stored in VarConnEstFailReport; or

2> if the cell identity of current cell is not equal to the cell identity stored in measResultFailedCell in VarConnEstFailReport:

3> reset the numberOfConnFail to 0;

2> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReportList and if the RPLMN is not equal to plmn-identity stored in any entry of VarConnEstFailReportList:

3> clear the content included in VarConnEstFailReportList;

2> clear the content included in VarConnEstFailReport except for the numberOfConnFail, if any;

2> store the following connection resume failure information in the VarConnEstFailReport by setting its fields as follows:

3> set the plmn-Identity to the PLMN selected by upper layers (see TS 24.501 [23]) from the PLMN(s) included in the plmn-IdentityInfoList in SIB1;

3> set the measResultFailedCell to include the global cell identity, tracking area code, the cell level and SS/PBCH block level RSRP, and RSRQ, and SS/PBCH block indexes, of the failed cell based on the available SSB measurements collected up to the moment the UE detected connection resume 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 per RAT and according to the following:

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

NOTE: 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 38.133 [14].

3> if available, set the locationInfo as in 5.3.3.7;

3> set perRAInfoList to indicate the performed random access procedure related information as specified in 5.7.10.5;

3> if numberOfConnFail is smaller than 8:

4> increment the numberOfConnFail by 1;

2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ‘RRC Resume failure’.

1> else if upon receiving Integrity check failure indication from lower layers while T319 is running or SDT procedure is ongoing:

2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ‘RRC Resume failure’.

1> else if indication from the MCG RLC that the maximum number of retransmissions has been reached is received while SDT procedure is ongoing; or

1> if random access problem indication is received from MCG MAC while SDT procedure is ongoing; or

1> if the lower layers indicate that cg–SDT–TimeAlignmentTimer or the configuredGrantTimer expired before receiving network response for the UL CG-SDT transmission with CCCH message while SDT procedure is ongoing; or

1> if T319a expires:

2> consider SDT procedure is not ongoing;

2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ‘RRC Resume failure’.

The UE may discard the connection resume failure or connection establishment failure information, i.e. release the UE variable VarConnEstFailReport, 48 hours after the last connection resume failure is detected.

The L2 U2N Relay UE either indicates to upper layers (to trigger PC5 unicast link release) or sends Notification message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10.

5.3.13.6 Cell re-selection or cell selection or L2 U2N relay (re)selection while T390, T319 or T302 is running or SDT procedure is ongoing (UE in RRC_INACTIVE) or SRS transmission in RRC_INACTIVE is configured

The UE shall:

1> if cell reselection occurs while T319 or T302 is running or while SDT procedure is ongoing; or

1> if relay reselection occurs while T319 is running; or

1> if cell changes due to relay reselection while T302 is running:

2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ‘RRC Resume failure’;

1> else if cell selection or reselection occurs while T390 is running, or cell change due to relay selection or reselection occurs while T390 is running:

2> stop T390 for all access categories;

2> perform the actions as specified in 5.3.14.4.

1> else if cell reselection occurs when srs-PosRRC-Inactive is configured:

2> indicate to the lower layer to stop inactivePosSRS-TimeAlignmentTimer;

2> release the srs-PosRRC-Inactive.

5.3.13.7 Reception of the RRCSetup by the UE

The UE shall:

1> perform the RRC connection setup procedure as specified in 5.3.3.4.

5.3.13.8 RNA update

In RRC_INACTIVE state, the UE shall:

1> if T380 expires; or

1> if RNA Update is triggered at reception of SIB1, as specified in 5.2.2.4.2:

2> if T319 is not running or SDT procedure is not ongoing:

3> initiate RRC connection resume procedure in 5.3.13.2 with resumeCause set to rna-Update;

1> if barring is alleviated for Access Category ‘8’ or Access Category ‘2’, as specified in 5.3.14.4:

2> if upper layers do not request RRC the resumption of an RRC connection, and

2> if the variable pendingRNA-Update is set to true:

3> initiate RRC connection resume procedure in 5.3.13.2 with resumeCause value set to rna-Update.

If the UE in RRC_INACTIVE state fails to find a suitable cell and camps on the acceptable cell to obtain limited service as defined in TS 38.304 [20], the UE shall:

1> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ‘other’.

NOTE: It is left to UE implementation how to behave when T380 expires while the UE is camped neither on a suitable nor on an acceptable cell.

5.3.13.9 Reception of the RRCRelease by the UE

The UE shall:

1> perform the actions as specified in 5.3.8.

5.3.13.10 Reception of the RRCReject by the UE

The UE shall:

1> perform the actions as specified in 5.3.15.

5.3.13.11 Inability to comply with RRCResume

The UE shall:

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

2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ′RRC Resume failure′.

NOTE 1: The UE may apply above failure handling also in case the RRCResume message causes a protocol error for which the generic error handling as defined in 10 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.13.12 Inter RAT cell reselection

Upon reselecting to an inter-RAT cell, the UE shall:

1> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘other’.