Training / Course 03
Aims — what you can do after
- Harden the core to TS 33.501: order the security algorithms and enable identity concealment with your own key pair.
- Engineer network slices end to end, and diagnose rejected or mis-routed slices.
- Differentiate QoS with subscription rate limits, policy rules and per-slice traffic shaping.
- Perform signalling forensics: query the NF discovery API and decompose a registration at the message level.
- Investigate mobility and session resilience — what core state survives a handover or teardown.
- Engineer a KPI pipeline: live exporters, a fast scrape loop, standardized metrics.
- Understand how a digital-twin root-cause agent automates the discipline you practised by hand.
The slicing chain — every link must agree
S-NSSAI (AMF) → DNN (SMF) → subnet (UPF)
A slice is only real when the identifier at the AMF, the data network at the SMF and the subnet at the UPF all line up. Diagnose a rejected slice by finding the broken link.
Three layers where QoS is actually enforced
SubscriptionThe subscriber's aggregate rate ceiling (AMBR) — what the profile allows.
↓
PolicyThe PCF policy / PCC rules — what the network decides per session.
↓
EnforcementLinux traffic control per slice — what the packets actually experience.
From telemetry to root cause
Telemetry → KPIs → Anomaly → Root cause → Action
The engineering feeds a loop: the KPIs and labelled scenarios you produce become the training data for a digital-twin root-cause agent — and where an engineer's judgement still beats automation.
Module breakdown
0
Advanced toolkit & backup-first discipline15 min
The change-safely habit drilled throughout: back up before you touch.
1
Security hardening (TS 33.501)45 min
Algorithm order and subscriber-identity concealment.
2
Network slicing engineering45 min
The slicing chain end to end, and why a slice gets rejected.
3
QoS differentiation engineering40 min
Subscription limits, policy rules and per-slice shaping — and one slice starving another.
4
Signalling forensics35 min
The NF discovery API, message-level tracing, a compliance audit.
5
Mobility & session resilience35 min
Handover and teardown — what state survives, and how to spot drift.
6
Performance & KPI engineering30 min
Live exporters and standardized KPI computation.
7
AI-assisted root cause analysis30 min
How the telemetry you produced feeds a digital-twin RCA agent — honestly framed.
What engineering the core looks like
- Deploy a network slice end to end and diagnose why one is rejected.
- Distinguish signalled QoS from enforced QoS and reconcile them.
- Read the service-based architecture itself for the faults that have no obvious layer.