A full 5G core on a laptop.
Register a UE with real 5G-AKA, bring up a PDU session, and forward user-plane traffic. In early beta, and under active development toward production.
Register a UE with real 5G-AKA, bring up a PDU session, and forward user-plane traffic. In early beta, and under active development toward production.
Network functions
Co-located interfaces are in-process calls. Everything that crosses a boundary speaks a real 3GPP protocol.
Terminates NAS and NGAP from the gNB, runs 5GMM registration, and manages PDU sessions — programming the UPF over N4. N11 is in-process.
Authenticates subscribers, de-conceals SUCI to SUPI, holds subscriber data, and supplies policy. N8/N10/N12/N13 are in-process calls.
Every NF registers on startup, discovers peers by type, and heartbeats. The registry at the center of the service-based architecture.
Receives GTP-U from the gNB over N3 and forwards decapsulated UE traffic to the data network over N6 through a userspace TUN datapath.
Activates SMS service and relays MO/MT SMS over NAS — RP/CP/TPDU decode, store-and-forward SMS-SC, delivery via Namf_Communication.
Optional network slice selection for labs that need S-NSSAI handling beyond the DMF defaults.
Interfaces
Reference points that cross a boundary are real protocols. SBI defaults to h2c; TLS/mTLS is optional on the NRF.
Co-located interfaces — N11 inside the DMF, N8/N10/N12/N13 inside the DPF — are plain function calls, with no socket to connect to.
Maturity
The golden path works today and we run it every day. Production-grade is the destination, not the current claim — so here is exactly where the line sits.
We publish this list because the gaps move. TinyCore is under active development and every release closes some of it — tell us which line blocks you and it moves up the queue. For protocol load and conformance against it, see dflux Runner.
Next step
Bring up the docker lab and run your first registration in about ten minutes.