5.3.12 UE actions upon leaving RRC_CONNECTED or RRC_INACTIVE

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

Upon leaving RRC_CONNECTED or RRC_INACTIVE, the UE shall:

1> reset MAC;

1> if leaving RRC_INACTIVE was not triggered by the reception of RRCConnectionRelease including idleModeMobilityControlInfo or altFreqPriorities:

2> stop the timer T320 and T323, if running;

2> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo;

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

1> if entering RRC_IDLE was triggered by reception of the RRCConnectionRelease message including a waitTime:

2> start timer T302, with the timer value set according to the waitTime;

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

1> else 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> 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 all timers that are running except T302, T320, T322, T323, T325, T330, T331;

1> release crs-ChEstMPDCCH-ConfigDedicated, if configured;

1> if leaving RRC_CONNECTED was triggered by suspension of the RRC:

2> re-establish RLC entities for all SRBs and DRBs, including RBs configured with NR PDCP;

2> remove all entries within VarConditionalReconfiguration, if any;

2> for each measId, that is part of the current UE configuration in VarMeasConfig, if the associated reportConfig has condReconfigurationTriggerEUTRA/condReconfigurationTriggerNR configured:

3> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;

3> if the associated measObjectId is only associated with condReconfigurationTriggerEUTRA/condReconfigurationTriggerNR:

4> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;

3> remove the entry with the matching measId from the measIdList within the VarMeasConfig;

2> store the UE AS Context including the current RRC configuration, the current security context, the PDCP state including ROHC state, C-RNTI used in the source PCell, the cellIdentity and the physical cell identity of the source PCell, and the spCellConfigCommon within ReconfigurationWithSync of the PSCell (if configured);

2> store the following information provided by E-UTRAN:

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

4> the fullI-RNTI, if present;

4> the shortI-RNTI, if present;

3> else:

4> the resumeIdentity;

3> the nextHopChainingCount, if present. Otherwise discard any stored nextHopChainingCount that does not correspond to stored key K_RRCint;

3> the drb-ContinueROHC, if present. Otherwise discard any stored drb-ContinueROHC;

2> suspend all SRB(s) and DRB(s), including RBs configured with NR PDCP, except SRB0;

2> if the UE connected to 5GC is a BL UE or UE in CE, indicate PDCP suspend to lower layers of all DRBs;

2> if the UE is connected to 5GC:

3> indicate the idle suspension of the RRC connection to upper layers;

2> else:

3> indicate the suspension of the RRC connection to upper layers;

2> configure lower layers to suspend integrity protection and ciphering;

NOTE 1: Except when resuming an RRC connection after early security reactivation in accordance with conditions in 5.3.3.18, ciphering is not applied for the subsequent RRCConnectionResume message used to resume the connection and an integrity check is performed by lower layers, but merely upon request from RRC.

1> else:

2> upon leaving RRC_INACTIVE:

3> discard the UE Inactive AS context;

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

2> release rrc-InactiveConfig, if configured;

2> remove all entries within VarConditionalReconfiguration, if any;

2> for each measId, that is part of the current UE configuration in VarMeasConfig, if the associated reportConfig has condReconfigurationTriggerEUTRA/condReconfigurationTriggerNR configured:

3> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;

3> if the associated measObjectId is only associated with condReconfigurationTriggerEUTRA/condReconfigurationTriggerNR:

4> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;

3> remove the entry with the matching measId from the measIdList within the VarMeasConfig;

2> release all radio resources, including release of the MAC configuration, the RLC entity and the associated PDCP entity and SDAP (if any) for all established RBs, except for the following:

– pur-Config, if stored;

2> indicate the release of the RRC connection to upper layers together with the release cause;

1> if leaving RRC_CONNECTED was triggered neither by reception of the MobilityFromEUTRACommand message nor by selecting an inter-RAT cell while T311 was running; or

1> if leaving RRC_INACTIVE was not triggered by the inter-RAT cell reselection:

2> if timer T350 is configured:

3> start timer T350;

3> apply rclwi-Configuration if configured, otherwise apply the wlan-Id-List corresponding to the RPLMN included in SystemInformationBlockType17;

2> else:

3> release the wlan-OffloadConfigDedicated, if received;

3> if the wlan-OffloadConfigCommon corresponding to the RPLMN is broadcast by the cell:

4> apply the wlan-OffloadConfigCommon corresponding to the RPLMN included in SystemInformationBlockType17;

4> apply steerToWLAN if configured, otherwise apply the wlan-Id-List corresponding to the RPLMN included in SystemInformationBlockType17;

2> enter RRC_IDLE and perform procedures as specified in TS 36.304 [4], clause 5.2.7;

1> else:

2> release the wlan-OffloadConfigDedicated, if received;

NOTE 2: BL UEs or UEs in CE verifies validity of SI when released to RRC_IDLE.

1> discard any segments of segmented RRC messages received;

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

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