 selection information such as NSSAI and the registered AMF included in the RRC Setup Complete message. 7. The gNB forwards the NAS registration request to the AMF in the NG-AP INITIAL UE MESSAGE (specified in 3GPP TS 38.413). 8. The AMF may initiate additional procedures with the UE NAS that are encapsulated and transferred using RRC DLInformationTransfer and ULInformationTransfer mes- sages. 9. The CN provides the NG-AP INITIAL CONTEXT SETUP REQUEST message (specified in 3GPP TS 38.413, also explained in Section 3.3) to the gNB, which contains infor- mation to establish the AS security and optionally PDU session information to set up DRBs. 10. RRC SecurityModeCommand configures the security algorithms and establishes AS security. 11. The UE acknowledges successful completion of the security configuration with RRC SecurityModeComplete. 12. RRC UECapabilityEnquiry is used to retrieve the UE AS capability. The UE capability in NR is subdivided into NR Standalone and capability related to dual connectivity in the MR-DC capability containers. The gNB may request one or more of these capabilities. The UE capability enquiry procedure can be executed at any time though this is now recommended to be after security activation. 13. The UE responds with the requested capabilities in RRC UECapabilityInformation. 14. RRC DLInformationTransfer encapsulates the NAS Registration Accept message to be sent to the UE. 15. RRC ULInformationTransfer encapsulates the NAS Registration Complete message to be sent to the network. 16. The gNB sends the NG-AP INITIAL CONTEXT SETUP RESPONSE message to the AMF indicating the successful completion of the UE context set up procedure. 17. The gNB forwards the NAS Registration Complete message received from the UE to the 18. The UE initiates the PDU Session Establishment procedure with the CN. These are carried transparently over RAN using RRC uplink and downlink Information Transfer messages. 19. The core network initiates the bearer set up procedures for the PDU session using the NG-AP PDU SE