NGAP-FLEX

AMF Proxy / NGAP-Flex

AMF Proxy load-balances NGAP signalling from gNBs across an AMF set, implementing the 5G equivalent of MME pooling (NGAP-Flex / AMF Set operation) so 5G core capacity scales horizontally and independently of the RAN.

N2 (gNB ↔ AMF Proxy ↔ AMF Set) Namf (SBI, pass-through to AMF) N14 (AMF ↔ AMF, pass-through)

Key features

  • NGAP load balancing across AMF Sets and AMF Regions
  • GUAMI-aware routing consistent with 3GPP AMF selection rules
  • RAN paging and N2 handover signalling relay
  • Weighted AMF Load Balancing per TS 23.501 §5.21.1
  • Zero-downtime AMF scale-out and scale-in
  • Telemetry export to NMS-UI for real-time signalling KPIs

Governing 3GPP & O-RAN specifications

These are the primary specifications this product implements or interoperates against. NgRAN tracks each release train and updates products as specifications evolve.

SpecificationTitle / scope
3GPP TS 23.501 System architecture for the 5G System (5GS) — AMF Set, Region, Pointer
3GPP TS 38.413 NG Application Protocol (NGAP)
3GPP TS 29.518 Namf services (Access and Mobility Management)
3GPP TS 23.502 Procedures for the 5G System — registration & mobility

Specification titles are summarised for reference. Full texts are maintained by 3GPP (3gpp.org) and the O-RAN ALLIANCE and are not reproduced here.

Architecture & interfaces

AMF Proxy terminates N2 from the gNB and forwards NGAP messages to the correct AMF in an AMF Set based on the 5G-GUTI / GUAMI, following the same set/region/pointer addressing 3GPP defines for AMF selection. It supports both service-based and reference-point deployments and can front a mixed pool of AMF vendors during migration.

Reference interfaces

N2 (gNB ↔ AMF Proxy ↔ AMF Set) Namf (SBI, pass-through to AMF) N14 (AMF ↔ AMF, pass-through)

Deployment model

Cloud-native CNF (Kubernetes, Helm chart included) with optional VM packaging.