time-sensitive networking
The ordinary Internet is best-effort: it tries hard to deliver your packets but promises nothing about exactly when each one arrives. For watching a video that is fine — a half-second hiccup is annoying but harmless. But imagine a car's brake controller, or a robot arm swinging near a worker, or a factory machine coordinating with the one next to it. There, a packet arriving a few milliseconds late, or arriving early, could be dangerous. These systems do not just need fast delivery; they need delivery at a precise, guaranteed time, every time. Time-sensitive networking is a set of standards that make Ethernet do exactly that.
Concretely, time-sensitive networking is a family of IEEE standards that turn ordinary Ethernet into a deterministic network. The core ingredients: every device shares a precisely synchronized clock (down to fractions of a microsecond), and the switches are scheduled so that time-critical traffic gets reserved slots — guaranteed windows in which it sails through with a bounded, predictable delay, while ordinary best-effort traffic is held back so it can never delay the critical packets. The result is that a control message is delivered within a tight time bound that the engineers can count on, turning a statistically-fast network into a guaranteed-on-time one.
Why it matters: this is the networking frontier for industry, automobiles, aerospace, and professional audio/video — places where 'usually fast' is not good enough and 'always on time' is the requirement. It lets standard, cheap Ethernet replace specialized, expensive control buses in cars and factories. The honest caveat: determinism is bought with reservation and scheduling, which costs flexibility — you must plan the time slots in advance, the network is engineered for a known set of flows rather than open and chaotic like the Internet, and the guarantees hold only inside the carefully configured TSN domain, not across the public Internet.
In a car, the steering and braking controllers exchange messages over an in-vehicle Ethernet running TSN. A control packet is scheduled into a reserved time slot and is guaranteed to arrive within, say, one millisecond — every single cycle — so a video stream to the rear-seat screen on the same wire can never delay a brake command.
Reserved time slots make delivery deterministic, not just fast.
TSN's guarantees are local and pre-planned: they hold only inside a TSN domain whose flows and schedule are configured in advance. It is not a way to make the open Internet deterministic — best-effort delivery across many independent networks fundamentally cannot promise an arrival time.