Skip to content

Callflow

Browse Callflow sequence diagrams and step-by-step explanations in one place. Existing explanations and caveats are pulled from the original chapters alongside the diagrams, so updates stay in sync.

How to use this collection

The left sidebar uses broad category headings like the learning course, with a flat list of English diagram titles inside each category. Select a title to jump directly to its diagram. Click a diagram to enlarge it. Step explanations follow the diagrams; explanations shared by multiple diagrams retain their original order. Follow the “Original explanation, assumptions and specification references” link for the full chapter context and references.

Guided Phases

Callflows in the course and this tab use shaded bands as reading aids, with each phase number and description at the top-left edge of its band rather than in a separate left gutter. Each heading describes the whole phase, not an individual NF. Phase numbers are not specification step numbers. Continue to read the original message order, branches, optional conditions and Step explanations.

Matching diagrams to packets

  • Arrows are messages; Notes are processing or assumptions: Formal NAS, NGAP, RRC and PFCP message names are shown in English. For example, PFCP Session Modification Request and Response replace a procedure-level label such as “N4 update.” Local decisions, key derivation and omitted procedures appear in Notes (TS 29.244 Clause 7.5.4 / Clause 7.5.5).
  • Distinguish outer transport from inner NAS: RRC and NGAP carry NAS between the UE and AMF. Match the outer arrow label and the inner message shown in NAS-PDU or Payload to the captured interface (TS 38.413 Clause 8.6; TS 38.331 Clause 6.2.2; TS 24.501 Clause 8.2 / Clause 8.3).
  • SBI shows HTTP alongside service operations: Methods (POST, GET, PUT, PATCH, DELETE), resource URIs and response status codes are distinguished from their corresponding 3GPP service operations. URI placeholders such as {supi} represent actual identifiers. Use each diagram's explanation to supply any omitted API root, service name or version (TS 29.500 Clause 5.2).

Wireshark display strings may differ

The diagrams use specification message names and protocol layers. Info-column capitalization, abbreviations and visible IEs depend on the dissector version and analysis environment. Reading encrypted NAS or TLS-protected SBI depends on the capture point, available keys and decryption settings. The diagrams also omit some branches and retransmissions, so arrow counts alone do not establish whether a capture is normal.

Browse by category

Choosing an entry point

  • Compare diagrams → This Callflow tab
  • Learn the context and meaning of procedures → Learning Course
  • Look up terminology → Dictionary

This collection reuses existing lesson diagrams. Conditions and caveats may be explained outside the diagrams, so consult the original chapters before using them in practice.