A radio link carries bits. The application at the far end wants a video frame, a database record, or a voice sample. Somewhere between those two facts lies an enormous amount of work — error correction, addressing, sequencing, security, session management — and the question is how to organise it without turning every new application into a complete redesign of the radio, or every new radio into a complete redesign of the application.
The answer is layering: divide the problem into well-defined strata, each responsible for exactly one class of task, each interacting with its neighbours through a stable interface. Change the modulation scheme below and the application above never notices, because the boundary contract stays the same. Add a new codec above and the radio below doesn't care. That separation of concerns is the whole reason the model works, and it is why every serious communications standard — from classic telephony to LTE to 5G NR — is specified as a stack.
01What Each Layer Actually Does
The model most engineers encounter first is the OSI seven-layer model, which names the layers from bottom to top: Physical, Data Link, Network, Transport, Session, Presentation, Application. In practice, the internet's TCP/IP stack collapses several of those into four, and cellular standards such as those produced by 3GPP carve the territory somewhat differently again. The principle, though, is consistent across all of them.
The Physical layer owns the air interface directly: radio frequencies, modulation, coding, timing and synchronisation. It knows nothing about addresses or payloads — its job is to turn a stream of bits into a waveform and back again reliably enough for the layer above to work with. Modulation is the craft of that writing-onto-a-carrier, and the physical layer is entirely where it lives.
The Data Link layer takes raw bit-delivery and makes it trustworthy. In cellular systems this layer typically splits into a Medium Access Control (MAC) sublayer and a Radio Link Control (RLC) sublayer. MAC schedules which device transmits when and on which resource blocks — essential when many users share the same spectrum. RLC handles segmentation and reassembly, and either acknowledges delivery or accepts packet loss depending on the traffic type. A voice call can tolerate a missing packet; a file transfer cannot.
RLC handles segmentation and reassembly, and either acknowledges delivery or accepts packet loss depending on the traffic type.
From this piece
The Network layer — IP in almost every modern system — handles addressing and routing. It decides how a packet gets from source to destination across multiple hops and networks. The layer neither knows nor cares how the physical medium beneath it works; it just expects the layer below to deliver packets to the next hop.
The Transport layer (TCP or UDP in internet terms) deals with end-to-end reliability and flow control. TCP tracks whether segments arrive and retransmits those that do not. UDP skips that overhead entirely, trading reliability for latency — the right trade for real-time media.
Above that, the Session, Presentation and Application layers handle connection management, data formatting and the logic of the application itself. In most modern stacks these boundaries are fuzzy; HTTP, for instance, covers functions that span all three.
| Layer | What it owns |
|---|---|
| Application | What the user actually wanted to do. |
| Transport | End-to-end delivery, ordering and flow control. |
| Network | Addressing and getting a packet across networks. |
| Data link | Framing, error control and access to the shared medium. |
| Physical | Turning bits into a waveform and back. |
02The Value of the Boundary
What the stack enforces, at every boundary, is a clean contract: I will deliver this service; I need that service from you; I do not care how you provide it. That contract is what makes interoperability achievable. Two manufacturers can build base stations and handsets that have never been in the same room, and if both implement the same stack to the same 3GPP specification, they will talk. That is not magic — it is the payoff from decades of disciplined boundary-keeping.
The stack is also why upgrades are tractable. 5G NR introduced a new physical layer and new scheduling at the MAC layer without requiring a new internet or new applications. The layers above stayed put. They had no reason to move.
UDP skips that overhead entirely, trading reliability for latency — the right trade for real-time media.
From this piece