Content for TS 38.331 Word version: 18.2.0

1… 4… 5… 5.2.2.4… 5.3… 5.3.3… 5.3.5… 5.3.5.5… 5.3.5.6… 5.3.5.7… 5.3.5.13… 5.3.5.17… 5.3.6… 5.3.8… 5.3.13… 5.3.14… 5.4… 5.5… 5.5.3… 5.5.4… 5.5.4.15… 5.5.4.23… 5.5.5… 5.5a… 5.7… 5.7.4… 5.7.8… 5.7.12… 5.8… 5.8.9… 5.8.9.2… 5.8.9.8… 5.8.10… 5.8.11… 5.9… 5.10… 6… 6.2.2… 6-2-2-23… 6-2-2-27… 6-2-2-43… 6-2-2-47… 6.3… 6.3.2… 6-3-2-27… 6-3-2-49… 6-3-2-73… 6-3-2-95… 6-3-2-108… 6-3-2-134… 6-3-2-162… 6-3-2-188… 6-3-2-213… 6-3-2-243… 6-3-2-271… 6-3-2-297… 6-3-2-341… 6.3.3… 6-3-3-25… 6-3-3-51… 6.3.4… 6.3.5… 6-3-5-25… 6.3.6… 6.4… 7… 9… 11… A… A.4… B…

5.3.13 RRC connection resume 5.3.13.1 General 5.3.13.1a Conditions for resuming RRC Connection for NR sidelink communication/discovery/V2X sidelink communication 5.3.13.1b Conditions for initiating SDT 5.3.13.1d Conditions for resuming RRC connection for multicast reception 5.3.13.2 Initiation 5.3.13.3 Actions related to transmission of RRCResumeRequest or RRCResumeRequest1 message 5.3.13.4 Reception of the RRCResume by the UE 5.3.13.5 Handling of failure to resume RRC Connection 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 5.3.13.7 Reception of the RRCSetup by the UE 5.3.13.8 RNA update 5.3.13.9 Reception of the RRCRelease by the UE 5.3.13.10 Reception of the RRCReject by the UE 5.3.13.11 Inability to comply with RRCResume 5.3.13.12 Inter RAT cell reselection
...

5.3.13 RRC connection resume p. 197

5.3.13.1 General p. 197

Reproduction of 3GPP TS 38.331, Fig. 5.3.13.1-1: RRC connection resume, successful

Figure 5.3.13.1-1: RRC connection resume, successful

Reproduction of 3GPP TS 38.331, Fig. 5.3.13.1-2: RRC connection resume fallback to RRC connection establishment, successful

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

Reproduction of 3GPP TS 38.331, Fig. 5.3.13.1-3: RRC connection resume followed by network release, successful

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

Reproduction of 3GPP TS 38.331, Fig. 5.3.13.1-4: RRC connection resume followed by network suspend, successful

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

Reproduction of 3GPP TS 38.331, Fig. 5.3.13.1-5: RRC connection resume, network reject

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 p. 198

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 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/sl-FreqInfoListSizeExt 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;

1 >

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

2 >

if the UE is configured by upper layers to transmit NR sidelink L2 U2N relay discovery messages and sl-L2U2N-Relay is included in SIB12; or

2 >

if the UE is configured by upper layers to transmit NR sidelink L3 U2N relay discovery messages and sl-L3U2N-RelayDiscovery is included in SIB12; or

2 >

if the UE is configured by upper layers to transmit NR sidelink non-relay discovery messages and sl-NonRelayDiscovery is included in SIB12:

3 >

if the frequency on which the UE is configured to transmit NR sidelink discovery is included in sl-FreqInfoList/sl-FreqInfoListSizeExt 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 clause 9.1.1.4 or SL-RLC1 as specified in clause 9.2.4; or

1 >

if RemoteUEInformationSidelink containing the connectionForMP is received from a L2 U2N Remote UE as specified in clause 5.8.9.8.3;

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 are met.

5.3.13.1b Conditions for initiating SDT p. 199

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

1 >

for the resume procedure initiated by the upper layers (i.e. mobile originated case):

2 >

SIB1 includes sdt-ConfigCommon; and

2 >

sdt-Config is configured; and

2 >

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

2 >

for an (e)RedCap UE when (e)RedCap-specific initial downlink BWP includes no CD-SSB, ncd-SSB-RedCapInitialBWP-SDT is configured; and

2 >

lower layers indicate that conditions for initiating MO-SDT as specified in TS 38.321 are fulfilled.

1 >

for the resume procedure initiated in response to RAN paging (i.e. mobile terminated case):

2 >

mt-SDT indication was included in the paging message for the UE's stored fullI-RNTI; and

2 >

lower layers indicate that conditions for initiating MT-SDT as specified in TS 38.321 are fulfilled.

5.3.13.1c Void

5.3.13.1d Conditions for resuming RRC connection for multicast reception p. 199

In RRC_INACTIVE state, if configured with MBS multicast reception in RRC_INACTIVE, the UE shall:

1 >

if the RRC connection resume procedure is triggered for multicast reception at reception of SIB1, as specified in clause 5.2.2.4.2; or

1 >

if the PTM configuration is not available in the cell after cell selection or reselection for a multicast session that the UE has joined for which the UE is not indicated to stop monitoring the G-RNTI; or

1 >

if mbs-NeighbourCellList acquired in the previous cell indicates that a multicast session that the UE has joined for which the UE is not indicated to stop monitoring the G-RNTI is not provided for RRC_INACTIVE in the current serving cell; or

1 >

if the measured RSRP or RSRQ for serving cell as specified in TS 38.304 is below the threshold indicated by thresholdIndex for a multicast session that the UE has joined:

2 >

initiate RRC connection resume procedure in clause 5.3.13.2 with resumeCause set to mt-Access.

5.3.13.2 Initiation p. 200

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, upon requesting multicast reception as specified in clause 5.3.13.1d, for NR sidelink communication/discovery/V2X sidelink communication as specified in clause 5.3.13.1a, for NR sidelink positioning as specified in clause 5.3.13.1c, for requesting configuration for SRS for positioning, for activation of preconfigured Positioning SRS in RRC_INACTIVE, upon receiving RRCRelease message including resumeIndication) 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 or

1 >

if the resumption of the RRC connection is triggered by receiving RRCRelease message including resumeIndication; or

1 >

if the resumption of the RRC connection is triggered by multicast reception request as specified in clause 5.3.13.1d:

2 >

select '0' as the Access Category;

2 >

perform the unified access control procedure as specified in clause 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 clause 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 upper layers provide NSAG information and one or more S-NSSAI(s) triggering the access attempt (TS 23.501 and TS 24.501):

3 >

apply the NSAG with highest NSAG priority among the NSAGs that are included in SIB1 (i.e., in FeatureCombination and/or in RA-PrioritizationSliceInfo), and that are associated with the S-NSSAI(s) triggering the access attempt, in the Random Access procedure (clause 5.1 of TS 38.321);

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 clause 5.3.13.8:

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 clause 5.3.14 using the selected Access Category and one or more Access Identities to be applied as specified in TS 24.501;

3 >

if the access attempt is barred:

4 >

set the variable pendingRNA-Update to true;

4 >

the procedure ends;

1 >

else if srs-PosRRC-InactiveValidityAreaConfig is configured and the resumption of the RRC connection is triggered due to cell reselection to a cell that is not included in srs-PosConfigValidityArea and there is an on-going SRS for positioning transmission:

2 >

select '8' as the Access Category;

2 >

set the resumeCause to srs-PosConfigOrActivationReq;

1 >

else if srs-PosRRC-InactiveValidityAreaConfig is configured and the resumption of the RRC connection is triggered due to upper layers request for configuration or activation of preconfigured SRS for positioning when the UE is camped in one of the cells indicated in srs-PosConfigValidityArea:

2 >

select '8' as the Access Category;

2 >

set the resumeCause to srs-PosConfigOrActivationReq;

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 clause 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, if no SRAP entity has been established;

2 >

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

2 >

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

2 >

apply the default configuration of SRAP as defined in clause 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 clause 9.2.1;

2 >

apply the default MAC Cell Group configuration as specified in clause 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 and maxBW-PreferenceConfigFR2-2 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 and maxMIMO-LayerPreferenceConfigFR2-2 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 and minSchedulingOffsetPreferenceConfigExt 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-GapPriorityAssistanceConfig from the UE Inactive AS context, if stored;

1 >

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

1 >

release musim-CapabilityRestrictionConfig from the UE Inactive AS context, if stored and stop timer T346n, if running;

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 >

release multiRx-PreferenceReportingConfigFR2 if configured, and stop timer T440, if running;

1 >

release uav-FlightPathAvailabilityConfig from the UE Inactive AS context, if stored;

1 >

release ul-TrafficInfoReportingConfig from the UE Inactive AS context, if stored;

1 >

stop all instances of timer T346x, if running;

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 clause 9.1.1.4;

2 >

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

1 >

else:

2 >

apply the CCCH configuration as specified in clause 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 ncd-SSB-RedCapInitialBWP-SDT 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 ncd-SSB-RedCapInitialBWP-SDT:

3 >

release the stored ncd-SSB-RedCapInitialBWP-SDT;

1 >

if conditions for initiating SDT in accordance with clause 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 or ta-ReportATG 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 >

release successPSCell-Config configured by the PCell from the UE Inactive AS context, if stored;

1 >

release successPSCell-Config configured by the PSCell from the UE Inactive AS context, if stored;

1 >

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

5.3.13.3 Actions related to transmission of RRCResumeRequest or RRCResumeRequest1 message p. 204

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 KgNB and KRRCint 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 KRRCint 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 KgNB key based on the current KgNB 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;

1 >

derive the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key;

1 >

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

1 >

configure lower layers to apply ciphering for all radio bearers except SRB0 and MRBs and to apply the configured ciphering algorithm, the KRRCenc key and the KUPenc 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.

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

If the UE is an (e)RedCap UE and the (e)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 clause 5.3.13.6.

5.3.13.4 Reception of the RRCResume by the UE p. 206

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 clause 5.7.8.3;

1 >

if the RRCResume includes the fullConfig:

2 >

perform the full configuration procedure as specified in clause 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 clause 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 KgNB;

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-Inactive is configured:

2 >

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

1 >

if srs-PosRRC-InactiveValidityAreaConfig is configured:

2 >

instruct the MAC entity to stop inactivePosSRS-ValidityAreaTAT, 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 clause 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 clause 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 clause 5.3.5.3 of TS 36.331 for the RRCConnectionReconfiguration message included in eutra-SCG;

1 >

if the RRCResume includes the radioBearerConfig:

2 >

perform the radio bearer configuration according to clause 5.3.5.6;

1 >

if the RRCResume message includes the sk-Counter:

2 >

perform security key update procedure as specified in clause 5.3.5.7;

1 >

if the RRCResume message includes the radioBearerConfig2:

2 >

perform the radio bearer configuration according to clause 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 idleInactiveReportAllowed is not included in the RRCResume message:

2 >

for each application layer measurement configuration with configforRRC-IdleInactive set to true:

3 >

forward the measConfigAppLayerId and inform upper layers about the release of the application layer measurement configuration;

3 >

discard any application layer measurement reports which were not yet submitted to lower layers for transmission;

3 >

release the application layer measurement configuration in UE variables VarAppLayerIdleConfig and VarAppLayerPLMN-ListConfig;

3 >

consider itself not to be configured to send application layer measurement report for the measConfigAppLayerId;

1 >

if the RRCResume message includes the appLayerMeasConfig:

2 >

perform the application layer measurement configuration procedure as specified in clause 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 clause 5.3.5.16;

1 >

if the RRCResume message includes the sl-ConfigDedicatedNR:

2 >

perform the sidelink dedicated configuration procedure as specified in clause 5.3.5.14;

1 >

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

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 clause 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 clause 5.3.14.4;

1 >

if T302 is running:

2 >

stop timer T302;

2 >

perform the actions as specified in clause 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 clause 5.3.5.3 of TS 36.331;

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

2 >

if the UE has logged measurements available for NR and if the current registered SNPN is included in snpn-ConfigIDList 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; or

2 >

if the UE is capable of reporting availability of signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the sigLoggedMeasType in VarLogMeasReport of TS 36.331 is included:

3 >

if T330 timer is running (associated to the logged measurement configuration for NR or for LTE):

4 >

set sigLogMeasConfigAvailable to true in the RRCResumeComplete message;

3 >

else:

4 >

if the UE has logged measurements:

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

2 >

if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the registered SNPN identity is equal to snpn-identity stored in VarConnEstFailReport or any entry 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 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; or

2 >

if the UE has radio link failure or handover failure information available in VarRLF-Report and if the current registered SNPN are included in snpn-IdentityList stored in VarRLF-Report; or

3 >

include rlf-InfoAvailable in the RRCResumeComplete message;

2 >

if the UE has successful PSCell change or addition related information available in VarSuccessPSCell-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessPSCell-Report; or

2 >

if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessPSCell-Report:

3 >

include successPSCell-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; or

2 >

if the UE has successful handover information available in VarSuccessHO-Report and if the current registered SNPN is included in snpn-IdentityList stored in the 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) of the UE just prior to entering RRC_CONNECTED state;

2 >

if the UE is configured with at least one application layer measurement with configForRRC-IdleInactive set to true:

3 >

for each application layer measurement configuration with configForRRC-IdleInactive set to true:

4 >

if the RPLMN is not included in plmn-IdentityList in VarAppLayerPLMN-ListConfig:

5 >

forward the measConfigAppLayerId and inform upper layers about the release of the application layer measurement configuration;

5 >

discard any application layer measurement reports which were not yet submitted to lower layers for transmission;

5 >

release the application layer measurement configuration in UE variables VarAppLayerIdleConfig and VarAppLayerPLMN-ListConfig;

5 >

consider itself not to be configured to send application layer measurement report for the measConfigAppLayerId;

3 >

if at least one stored application layer measurement configuration or application layer measurement report container has not been released:

4 >

include measConfigReportAppLayerAvailable in the RRCResumeComplete message;

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;

3 >

if the needForInterruptionConfigNR is enabled:

4 >

include the needForInterruptionInfoNR and set the contents as follows:

5 >

include intraFreq-needForInterruption with the same number of entries, and listed in the same order, as in intraFreq-needForGap;

5 >

for each entry in intraFreq-needForInterruption, include interruptionIndication and set the interruption requirement information if the corresponding entry in intraFreq-needForGap is set to no-gap;

5 >

include interFreq-needForInterruption with the same number of entries, and listed in the same order, as in interFreq-needForGap;

5 >

for each entry in interFreq-needForInterruption, include interruptionIndication and set the interruption requirement information if the corresponding entry in interFreq-needForGap is set to no-gap;

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;

2 >

if the SIB1 contains musim-CapRestrictionAllowed and the UE capability is restricted for MUSIM operation:

3 >

if supported, include the musim-CapRestrictionInd in the RRCResumeComplete message upon determining it has temporary capability restriction;

2 >

if the UE has flight path information available:

3 >

include flightPathInfoAvailable;

1 >

submit the RRCResumeComplete message to lower layers for transmission;

1 >

the procedure ends.

5.3.13.5 Handling of failure to resume RRC Connection p. 214

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) 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;

3 >

if available, set the locationInfo as in clause 5.3.3.7;

3 >

set perRAInfoList to indicate the performed random access procedure related information as specified in clause 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 clause 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:

2 >

perform the actions upon going to RRC_IDLE as specified in clause 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 integrity check failure indication is received from lower layers 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 clause 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 and the UE variable VarConnEstFailReportList, 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 NotificationMessageSidelink message to the connected L2 U2N Remote UE(s) in accordance with clause 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 p. 215

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 clause 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 clause 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.

1 >

else if cell reselection occurs when srs-PosRRC-InactiveValidityAreaConfig is configured and if the cell is not included in the srs-PosConfigValidityArea:

2 >

indicate to the lower layer to stop inactivePosSRS-ValidityAreaTAT;

1 >

else if cell reselection occurs when srs-PosRRC-InactiveValidityAreaConfig is configured and if the cell is included in the srs-PosRRC-InactiveValidityAreaConfig:

2 >

if autonomousTA-AdjustmentEnabled is configured;

3 >

indicate to the lower layer to update Timing Advance and stored RSRP.

5.3.13.7 Reception of the RRCSetup by the UE p. 216

The UE shall:

1 >

perform the RRC connection setup procedure as specified in clause 5.3.3.4.

5.3.13.8 RNA update p. 216

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 clause 5.2.2.4.2:

2 >

if T319 is not running and SDT procedure is not ongoing:

3 >

initiate RRC connection resume procedure in clause 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 clause 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 clause 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, the UE shall:

1 >

perform the actions upon going to RRC_IDLE as specified in clause 5.3.11 with release cause 'other'.

5.3.13.9 Reception of the RRCRelease by the UE p. 217

The UE shall:

1 >

perform the actions as specified in clause 5.3.8.

5.3.13.10 Reception of the RRCReject by the UE p. 217

The UE shall:

1 >

perform the actions as specified in clause 5.3.15.

5.3.13.11 Inability to comply with RRCResume p. 217

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 clause 5.3.11 with release cause 'RRC Resume failure'.

NOTE 2:

If the UE is configured (i.e., via SIB1) to send MUSIM temporary capability restriction indication, and if the UE supports MUSIM temporary capability restriction, the UE does not apply above failure handling in case the UE is unable to apply part of the configuration included in RRCResume message due to UE temporary capability restriction for MUSIM operation. It is up to UE implementation how to apply RRCResume message. If UE does not go to RRC_IDLE in this case, UE still considers the received configuration in RRCResume message as the current configuration as the baseline for delta configuration for future reconfigurations. For other cases, 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 p. 217

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

1 >

perform the actions upon going to RRC_IDLE as specified in clause 5.3.11, with release cause 'other'.