Been explaining 5G packet core to non-engineers using a restaurant analogy :curious what the community thinks of this approach
I've been trying to make 5G core architecture accessible to students and people early in their telecom careers. The feedback so far is that the restaurant analogy helps a lot. I wanted to share it here and get thoughts from people who actually work in the industry on whether the technical accuracy holds up.
The core idea: the 5G core as a restaurant
The AMF is the host. Registration, mobility management, NAS termination. First point of contact, tracks you as you move.
The AUSF and UDM are the bouncer and guest list. Authentication and subscription data. AUSF challenges your identity, UDM holds the credentials (SUPI, authentication vectors). No valid identity, no access.
The SMF is the manager. Session establishment, IP address allocation, and most importantly, control of the UPF over N4 using PFCP. Gives instructions, never touches data.
The UPF is the waiters. The actual data plane. Packet routing, forwarding, QoS enforcement, traffic reporting back to the SMF. This is where your packets actually live. And with CUPS (Control and User Plane Separation, defined in TS 23.501), the UPF can be deployed at the network edge independently of the control plane, which is the whole reason 5G can hit sub-millisecond latency for URLLC use cases.
The PCF is the house rules manager. Policy control, QoS rules, charging decisions via interaction with CHF.
The NRF is the staff directory. Service registration and discovery, the backbone of the service-based architecture.
The NWDAF is the brilliant observer. Network analytics and ML-based intelligence. The foundation of autonomous network management and what's being built upon for 6G.
My question for the community: does this mapping hold up from a practical standpoint? Any nodes or interfaces you'd explain differently to someone coming in fresh? Particularly curious about how people explain the N4/PFCP relationship and the SEPP for roaming scenarios, as those seem to be where the analogy starts to strain a bit.
Would love any pushback or additions from people working in the core.