rms a periodic registration update (due to a predefined inac- tivity time interval); and additionally when the UE needs to update its capabilities or protocol parameters that were negotiated during registration procedure. The AMF pro- vides a list of recommended cells/TAs/NG-RAN node identifiers for paging. The N2 interface supports management procedures which are not UE-specific, rather for configuration or reset of the N2 interface. These procedures are applicable to any access scheme and access-specific messages that carry some information for a particular access scheme such as information on the default paging DRX cycle that is used only for 3GPP access. The N2 interface further supports UE-specific and NAS-transport procedures. These procedures are in general access-agnostic, but they may also correspond to uplink NAS transport messages that carry some access-dependent information such as user location information. The N2 interface also supports procedures related to UE context management and resources for PDU sessions. These messages carry information on N3 addressing and QoS requirements that should be transparently forwarded by the AMF between the 5G access node and the SMF. The N2 interface further enables procedures related to handover management for 3GPP access. The control-plane interface between a 5G access node and the 5G core supports connection of different types of 5G access nodes to the 5GC via a unique control-plane protocol. A sin- gle NGAP protocol is used for 3GPP and non-3GPP access schemes. There is a unique N2 termination point at the AMF for a given UE (for each access node used by the UE) regard- less of the number of PDU sessions of the UE. The N2 control plane supports separation of AMF and other functions such as SMF that may need to control the services supported by 5G access nodes, where in this case, AMF transparently forwards NGAP messages between the 5G access node and the SMF. The N2 session management information (i.e., a subset of NGAP information that AMF transparently relay