s the interface that connects the AMF to the Equipment Identity Register (EIR) N20: This is the interface that connects the AMF to the Short Messaging Service Function (SMSF) N22: This is the interface that connects the AMF to the Network Slice Selection Function (NSSF) N12: This is the interface that connects the AMF to the Authentication Server Function (AUSF) N8: This is the interface that connects the AMF to the UDM The AMF is responsible for the termination of the CP interface from the NG-RAN (N2). Hence, it is connected to the gNB via the same interface. The AMF also terminates the NAS (N1) and is responsible for ciphering and integrity protection of NAS messages exchanged between it and the UE. The AMF undertakes the registration management of the UE and ensures that a legitimate UE is successfully registered with the network. It will reject the registration of UEs without subscriptions or incorrect subscriptions. Hence, it behaves as a gatekeeper to the network, only allowing legitimate subscribers to access the network. Hence, it provides access authentication and authorization functions. It also provides support for network slice-specific authentication and authorization. The AMF is responsible for managing the connection of the subscriber. It is also responsible for reachability management and will page an idle UE SO that it can come back to a connected mode and service a call. The AMF is also responsible for mobility management, which means that it is responsible for successfully handing over UE from one tower to another, and also from one AMF region to another. If the UE ventures outside of the coverage of the AMF, it is also responsible for inter-RAT handovers to LTE or the WLAN (N3-IWF). It is responsible for providing an EPS bearer ID for interworking with the 4G EPS. The AMF events allow for lawful interception, and armed events can be sent to the authorities for law enforcement. It also provides location services management to regulatory bodies. The AMF provides a transparent container for Sessi