Editing My Intra-NR Notes (section)

=== 9.2.2.6 Resume request responded with Release with Redirect, with UE context relocation ===

The following figure describes a UE triggered NAS procedure responded by the network with a release with redirect, with UE context relocation.

<center>[[File:Resume request responded with Release with Redirect, with UE Context relocation.png|Resume request responded with Release with Redirect, with UE Context relocation sequence diagram]]</center>

:1.	The UE resumes from RRC_INACTIVE, providing the inactive radio network temporary identifier (I-RNTI) allocated by the last serving gNB.
:2.	The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context data.
:3.	The last serving gNB provides the UE context.
:4.	The gNB may move the UE to RRC_CONNECTED (and the procedure follows step 4 of Figure 9.2.2.4.1-1), or send the UE back to RRC_IDLE (in which case an RRCRelease message is sent by the gNB), or send the UE back to RRC_INACTIVE, including a release with redirect indication (as assumed in the following).
:5.	If loss of DL user data buffered in the last serving gNB shall be prevented, the gNB provides forwarding addresses.
:6./7. The gNB performs path switch.
:8.	The gNB keeps the UE in RRC_INACTIVE state by sending RRCRelease with suspend indication, including redirection information (frequency layer the UE performs cell selection upon entering RRC_INACTIVE).
:9.	The gNB triggers the release of the UE resources at the last serving gNB.

NOTE1:	Upon receiving the release with redirect, the higher layers trigger a pending procedure so the UE tries to resume again after cell selection.