What the syllabus asks you to cover
Tele traffic parameters (busy hour, grade of service, service levels, and traffic intensity). Traffic routing in wireless networks, common channel signaling, integrated services digital networks. Packet vs circuit switching for PCN, protocol for network access.
Start here for the core ideas. A dedicated GitBook topic page was not available; this original guide is introductory. Use the syllabus checklist and references below to study the remaining details.
Describe offered traffic
Teletraffic engineering connects usage demand to resource capacity and service targets. Traffic intensity is often expressed in erlangs. With consistent time units, , where lambda is the call arrival rate and h is mean holding time. Busy-hour measurements describe the peak planning period, not a full-day average.
State the queueing assumptions
Blocking probability and waiting probability are different measures. Erlang B models a loss system under its assumptions; Erlang C models a waiting system under different assumptions. Grade of service must specify the event being measured. Packet traffic may need models that reflect burstiness rather than simple call arrivals.
Try it
Thirty calls per hour with a mean duration of two minutes offer 1 erlang of traffic. That is a load measure, not a statement that one circuit always delivers an acceptable blocking probability.
Check your understanding
How do blocking, delay and utilisation differ? Explain why arrival and holding-time assumptions matter before choosing a sizing formula. Study signalling, routing and access protocols alongside these models.
Pause and recall
Without looking back, explain the main idea, recall a key definition or formula, and describe when it applies. Include assumptions and units where relevant. Revisit any step you could not explain.