13/04/2026
π Role of PLMN ID in Registration π
1. π‘ UE PLMN Selection
βοΈ UE scans SIB1
βοΈ SIB1 contains a list of available PLMNs
βοΈ UE selects one PLMN (operator network)
βοΈ UE includes selected PLMN index β RRC Setup Complete
2. ποΈ gNB Processing (Routing Decision Point)
πΉ A. AMF Selection
βοΈ gNB reads PLMN ID (+ optional S-NSSAI)
βοΈ Uses it to select correct AMF pool
Behavior:
β
If UE is new (no 5G-GUTI):
β gNB selects AMF based on PLMN + slice
β If no matching AMF exists:
β triggers RRC Release or NGAP Setup Failure
πΉ B. RAN Sharing (MOCN Scenario)
βοΈ One gNB connected to multiple cores:
Core A β MCC 123 / MNC 01
Core B β MCC 123 / MNC 02
βοΈ The gNB reads PLMN Index and ensures the Initial UE Message is sent over the correct SCTP association to the corresponding operator's AMF.
3. π‘οΈ AMF Validation : Consistency Check
πΉ AMF verifies: PLMN ID from RRC/NGAP vs Serving PLMN in NAS Registration Request
π¨ Mismatch Handling : If mismatch occurs, AMF rejects UE with cause: 5GMM #11 β PLMN not allowed