N26-based handover is not supported, this is not applicable. In Steps 21 and 22, the message from the SMF to the AMF carries an N1 container to be passed on to the UE and an N2 container for the gNB; a lot of important information about the PDU session is packed in these containers, such as the following: Packet Core Procedures PDU session ID N2 SM information, including the following: PDU session ID QFI(s) QoS profile, CN tunnel info S-NSSAI from the allowed NSSAI Session-AMBR PDU session type User Plane Security Enforcement information UE integrity protection maximum data rate N1 SM container (PDU session establishment accept): QoS rules and QoS flow level, and QoS parameters, if needed, for the QoS flows associated with the QoS rules Selected SSC mode S-NSSAIs UE requested DNN Allocated IPv4/v6/v4v6 address Interface identifier Session-AMBR Selected PDU session type, and reflective QoS timer, when available P-CSCF addresses within the PCO, if requested Control Plane Only indicator, when available Header compression configuration, when available Always-on PDU Session Granted, when available Small data rate control parameters, when available Small data rate control status, when available Serving PLMN rate control If multiple UPFs are used for the PDU session, the CN tunnel info contains tunnel information related to the UPFs that terminate N3 PDU session establishment in 5G The CN tunnel information included in the N2 container has the core network addresses of the N3 tunnel corresponding to the PDU session that is provided to the gNB via the AMF. It also provides the QoS information and profiles to the RAN via N2 and via N1 to the UE. 23 N2 PDU Session Request (NASmsg) AN Specific resource Setup PDU Session Establishment Accept PCF SessionSetupRsp First Uplink Data 26 PDU SessionUpdateSMContext Req N4 Modification Req N4 Modification Res First Uplink Data 29 PDU SessionUpdateSMContext Res Figure 7.6 - PDU session establishment in 5G - part 3 In Step 23, the message is directed from the AMF to the RAN (gNB). The