SQN Sync in IMS AKA Was the Authentication Detail I Kept Missing
IMS AKA stopped looking like a simple password check once I traced the sequence number and resynchronization path.
TOPIC
Lessons, explainers, experiments, and implementation notes.
IMS AKA stopped looking like a simple password check once I traced the sequence number and resynchronization path.
GTP made more sense once I stopped treating it as one protocol and separated tunnel-control signalling from the packets that actually carry user traffic.
VoLTE QoS became easier to understand when I separated the persistent IMS signalling bearer from the dedicated low-latency bearer created for voice media.
APN and DNN both identify data-network intent, but the surrounding EPC and 5GC procedures are different enough that treating them as pure renames is misleading.
Diameter routing depends on realms, applications and peer capabilities, so a routing agent has to understand more than destination IP addresses.
A charging rule becomes concrete when its packet filters are followed all the way into bearer treatment.
Breaking the EPC into MME, HSS, SGW, PGW and PCRF roles made LTE core traffic much easier to follow in captures and logs.
Policy is not just a config file on the gateway; in 5GC it can actively influence session behavior through dedicated network functions.
Before looking at subscriber procedures, I needed to understand how Diameter peers identify themselves, advertise applications and establish a usable relationship.
Following one VoLTE call from LTE attachment through IMS registration, SIP session setup, bearer creation and RTP finally connected the year's separate labs.
Following registration as a state transition is more useful than memorizing a long list of NAS messages.
An APN is more than a label on the handset; it influences how a subscriber session reaches a packet gateway and an external data network.
5G user-plane programming became clearer once I followed PFCP instead of treating the UPF as a static router.
The move from digitized radio samples toward packetized fronthaul explains a lot about modern RAN architecture.
Separating N2 signalling from N3 user traffic made the gNB-to-core boundary much easier to troubleshoot.
Tracing a Create Bearer Request tied policy, QoS and user-plane classification together in one procedure.
Tracing S6a made the HSS feel less like a subscriber database and more like an active control-plane participant in LTE attach and mobility.
Usage records become meaningful only when they can be tied back to the session, rule and network event that produced them.
Large antenna arrays are interesting because of beams, spatial layers and RF chains, not because the front panel contains a big number of elements.