TRN-02 · Transport and Edge
Budget every millisecond.
Design an edge network where placement, QoS, time-sensitive transport and mobility each get a share of a fixed latency budget.
You build: an edge latency budget with measured figures for each share.
Some chapters are still being completed — the chapters for this course are still being finalised.
Promise
Design an edge network where every millisecond is budgeted: placement, QoS, time-sensitive transport, and mobility.
Prerequisites
basic networking.
Units
1. Overview and architecture ch 01–03
.
2. Deployment and transport ch 04–07
edge node placement, time-sensitive networking, 5G and edge convergence.
3. Control and assurance ch 08–11
SDN at the edge, QoS, low-latency distribution, balancing security and latency.
4. Acceleration and data ch 13–17
hardware acceleration, edge AI inference, stream processing, storage latency.
5. Mobility and platforms ch 18–22
mobility, scheduling, simulation, open-source platforms.
6. Practice ch 23–26
.
7. Energy, standards, future ch 27–30
.
Labs
Each lab names its environment and a pass check. Labs are not marked complete on "it ran" — the pass check has to hold.
| Lab | What you do | Environment |
|---|---|---|
| TRN-02ach 06 | TSN configuration in a simulatorPass check: Gate schedule verified | sim90 min |
| TRN-02bch 09 | QoS class for latency trafficPass check: Latency for the class lower under load | sim60 min |
| TRN-02cch 21 | Edge simulationPass check: Latency budget filled | sim90 min |
| TRN-02dch 22 | Open-source edge platformPass check: Workload deployed | container120 min |
Capstone project · CAP-10
Congestion-Control Experiment · 2 weeks
A video service stalls on mobile links.
Compare two congestion-control approaches on a defined profile with statistics. Recommend one, with its risks.
Deliverables: Scripts, data, chart, recommendation.
Outcomes
- I can split an end-to-end latency budget across access, transport, and compute.
- I can configure a QoS class for latency-sensitive traffic.
- I can justify an edge site placement with measurements.
Also in
How it runs
Work through the units in order. Each unit groups the chapters of the study guide with its share of the labs. You can start any time; there is no cohort date and nothing expires.
Labs run in a VM, a container, a simulator or on real hardware, and the card above names which. Where a lab needs hardware — an RDMA NIC, a programmable switch model, an FPGA — there is a simulator fallback so you are never blocked by equipment.
Questions
Do I get a certificate?
You get a completion record for the course. Path badges and project credentials are earned by passing the labs and the project review, not by attendance.
Can my team take this together?
Yes — and if you would rather have it delivered live, with the instructor in the room, this course also exists as a scheduled live cohort. See the live dates.
How long does it take?
≈ 30 h of study including the labs. Most engineers take it part-time over a few weeks.