5.1 Layered Network Architecture

Layered network architecture breaks down complex communication systems into manageable parts. This approach gives you modularity, simplification, and interoperability, which lets networks adapt and grow. Each layer has a specific role, but they all work together to move data from source to destination.

Higher layers rely on services from lower ones, and each layer adds its own header information as data travels down the stack. At the receiving end, each layer strips off the corresponding header and passes the payload upward. This structure keeps the intricate process of sending data across networks organized, efficient, and reliable.

Layered Network Architecture

Benefits of layered network architecture

Modularity is the big one. Each layer can be developed, updated, or swapped out independently without breaking the layers above or below it. A change to how wireless transmission works at the Physical Layer doesn't force you to rewrite your web browser.

Beyond modularity, layering provides several other advantages:

• Simplification of design and implementation by breaking network communication into parts, each focused on a specific function
• Interoperability through standardized interfaces between layers, so devices from different manufacturers (Cisco, Juniper, Arista) can communicate without issue
• Flexibility to integrate new protocols and technologies into the existing architecture (5G, Wi-Fi 6) without redesigning the whole stack
• Scalability that lets the network grow and adapt to increasing demands like more users or higher bandwidth requirements

Services between network layers

Layers interact through a provider-consumer relationship. The lower layer is the service provider, and the higher layer is the service user. The higher layer requests functionality from the layer below without needing to know how that functionality is implemented. This is the principle of abstraction: the lower layer hides its internal complexity.

• Service Access Points (SAPs) are the interfaces where the lower layer exposes its services to the upper layer. You can think of a SAP as a well-defined entry point, like a port number that lets the Transport Layer deliver data to the correct application.
• The upper layer passes data down and trusts the lower layer to handle specific functions (error detection, flow control, addressing) on its behalf.

Roles of network architecture layers

The five-layer Internet model (sometimes called the TCP/IP model with a split link/physical layer) assigns each layer a distinct responsibility. Data moves down the stack at the sender and up the stack at the receiver.

• Application Layer provides network services directly to end-user applications.
  • HTTP for web browsing
  • FTP for file transfer
  • SMTP for email
  • DNS for translating domain names to IP addresses
• Transport Layer ensures end-to-end data delivery between processes on different hosts.
  • Segments data and provides error detection and recovery
  • TCP for reliable, connection-oriented communication (guarantees delivery and ordering)
  • UDP for faster, connectionless communication (no delivery guarantee, lower overhead)
• Network Layer routes packets between source and destination across potentially many intermediate networks.
  • Provides logical addressing (IP addresses) and path determination
  • IP for addressing and routing
  • ICMP for error reporting and diagnostics (e.g., ping and traceroute)
• Data Link Layer handles reliable data transfer between adjacent network nodes (one hop at a time).
  • Defines the format of data frames and provides error detection (and sometimes correction)
  • Ethernet for wired LANs
  • Wi-Fi (802.11) for wireless LANs
• Physical Layer transmits raw data bits over a communication medium.
  • Defines electrical, mechanical, and functional specifications for the physical connection
  • Ethernet cables (Cat5e, Cat6) for wired transmission
  • Wireless channels (2.4 GHz, 5 GHz) for wireless transmission

Data encapsulation across network layers

Encapsulation is the process of wrapping data with protocol-specific headers (and sometimes trailers) as it moves down the stack. Each layer treats everything it receives from the layer above as its payload, then prepends its own header.

The data units at each layer have specific names:

How encapsulation and decapsulation work, step by step:

1. The sending host passes application data down through each layer. At every layer, a header is added around the payload from above. The Data Link Layer also appends a trailer (typically a CRC for error checking).
2. The Physical Layer converts the complete frame into raw bits and transmits them over the medium (copper, fiber, wireless).
3. At the receiving host, the process reverses. Each layer reads and removes its own header, then passes the remaining payload up to the next layer.
4. The Application Layer at the receiver finally gets the original data, with all protocol headers stripped away.

This encapsulation/decapsulation cycle is what allows each layer to operate independently. The Network Layer, for example, doesn't need to understand what's inside the Transport Layer's segment; it just wraps it in a packet and routes it.