s a change of gNB. 0. A UE is in the CONNECTED state. 1. The network releases the connection and moves the UE to the INACTIVE state by providing an RRC Release message with suspend configuration. The suspend Last serving 0. UE in RRC CONNECTED 1. RRCRelease [with suspend configuration] 2. UE in INACTIVE 3. RACH 4. RACH response (RAR) 5. RRCResumeRequest 6. Xn-AP: RETRIEVE UE CONTEXT REQUEST 7. Xn-AP: RETRIEVE UE CONTEXT RESPONSE 8. RRCResume 10. Xn-AP: XN-U ADDRESS INDICATION 9. UE in CONNECTED 11. Xn-AP: PATH SWITCH REQUEST 12. Xn-AP: PATH SWITCH RESPONSE 13. Xn-AP: UE CONTEXT RELEASE Figure 3.4.14 Example message flow for state transition from INACTIVE to CONNECTED. 3 5G System Overview configuration includes a UE RAN ID called I-RNTI. It also includes security configuration to use when resuming the connection. 2. The UE moves to the INACTIVE state. 3. When the UE wants to move to RRC CONNECTED, either to initiate communication with the network or in response to RAN or CN paging message, the UE initiates the connection using the RACH procedure. This is the same as when the UE is moving to CONNECTED from IDLE. 4. The network responds with a RACH response, the same as for an IDLE to CON- NECTED connection establishment procedure. 5. The UE requests the transition to CONNECTED using an RRC Resume Request message in RACH message 3 that contains the I-RNTI, authentication information ResumeMAC-I, and cause value. 6. If the resume request is received in a new gNB, the UE context has to be relocated from the previous gNB (i.e. the last serving gNB) to the current gNB. The new gNB requests the UE context using the NG-AP RETRIEVE UE CONTEXT REQUEST message. 7. After successful authentication of the UE based on the ResumeMAC-I, the previous gNB provides the UE context using the NG-AP RETRIEVE UE CONTEXT RESPONSE message. 8. The gNB indicates the successful resumption to the UE using the RRC Resume mes- sage. It is sent with security over DCCH as the security context in the UE was already provided when the UE went to INAC