Exact Extract — 5G Service-Based Architecture
“All network functions on the control plane interact with each other through service-based interfaces. A service can be invoked by multiple network functions, reducing the coupling degree defined for interfaces between network functions.”
— Huawei 5G Training Material, SBA Network Architecture, page 93.
Technical Deep Dive
The Access and Mobility Management Function (AMF) is responsible for access control, registration management, connection management, reachability, mobility management, and NAS signalling security in the 5G core. The AMF uses two important categories of interfaces.
C. N2 interface. The N2 interface connects the AMF with the Next Generation Radio Access Network (NG-RAN), particularly the gNodeB. It uses NG Application Protocol (NGAP), normally transported over SCTP. N2 supports procedures including NG Setup, UE context establishment, initial UE signalling, paging, and mobility-related control signalling.
D. Service-Based Interface (SBI). The AMF exposes and consumes service-based interfaces to communicate with other 5G core network functions. Examples include Namf_Communication for AMF communication services, Namf_EventExposure for event exposure, Nudm_SDM for subscription data retrieval from UDM, and Nausf_UEAuthentication for authentication interactions with AUSF. The SBI uses HTTP-based service communication, commonly HTTP/2 with JSON-formatted data.
The GTP user-plane tunnelling function is associated primarily with UPF interfaces such as N3 and N9, not the AMF's principal access signalling interface. Although an AMF may participate in legacy interworking architectures, GTP is not the intended configurable AMF interface here. S5 belongs to the LTE Evolved Packet Core and connects the Serving Gateway (SGW) and Packet Data Network Gateway (PGW).
An engineer troubleshooting AMF connectivity should independently validate the N2 SCTP association, NGAP signalling, SBI reachability, TLS configuration, and NRF service discovery.