Multimedia, Real-Time & Quality of Service

quality of service

On a single-lane road, everyone waits in the same line — an ambulance is stuck behind a delivery van. Give the road a bus lane or a siren-clearing rule, and emergency traffic moves while ordinary traffic waits. Quality of service is that idea for networks: instead of treating every packet identically, the network gives some traffic better-than-best-effort treatment — lower delay, more reserved bandwidth, or priority when queues fill. QoS is the umbrella term for any mechanism that lets the network favor traffic that needs it, like real-time voice and video, over traffic that can wait, like a background file download.

It is implemented mainly inside routers, where packets queue up waiting for an output link. The building blocks are: scheduling disciplines that decide whose packet goes next from the queue (simple first-in-first-out, strict priority, round robin, or weighted fair queuing that hands each class a guaranteed share); and traffic policing and shaping that limit how fast a flow may send, often using a leaky bucket or token bucket. On top of these mechanisms sit two whole architectures for the Internet: Integrated Services (IntServ), which makes fine-grained per-flow reservations with the RSVP protocol, and Differentiated Services (DiffServ), which is coarser and more scalable, marking each packet with a class and treating classes differently at each hop.

Why it matters: QoS is how you would, in principle, guarantee that a video call stays smooth even when the link is congested. But here is the honest punchline of the whole field: the public Internet mostly does not deploy these mechanisms across providers. Coordinating per-flow guarantees across thousands of independent networks is hard, and operators have largely found it cheaper and simpler to over-provision — to install more capacity than is usually needed — so the network rarely congests in the first place. QoS thrives inside single administrative domains (a company network, a carrier's own backbone, a data center) where one operator controls the routers; across the open Internet, best effort plus generous capacity still wins.

A company router is configured so VoIP packets (marked as a high-priority class) always jump ahead of bulk backup traffic when the uplink is full. Result: during a 9 a.m. surge of backups, calls stay crisp because their packets never wait behind gigabytes of file data.

QoS lets a router favor delay-sensitive voice over bulk data when the link is full.

The honest truth of QoS: most of the public Internet does not use it end-to-end. Operators over-provision capacity instead, because coordinating guarantees across many independent networks is harder than just adding bandwidth. QoS shines mainly within a single operator's domain.

Also called
QoS服務品質