OSI Model – All 7 Layers Explained

1. What Is the OSI Model?

The OSI (Open Systems Interconnection) Model is a conceptual framework developed by the ISO (International Organization for Standardization) in 1984 that divides network communication into seven distinct layers. Each layer has a specific role, communicates only with the layers directly above and below it, and hands off a well-defined unit of data (a PDU — Protocol Data Unit) as it passes through the stack.

The OSI model does not define specific protocols — it is a reference model used to understand, design, and troubleshoot network systems. Real-world networking is governed by the TCP/IP model, but the OSI model remains the universal language network engineers use when diagnosing problems.

  OSI Layer Stack                 Data Unit (PDU)    Direction
  -------------------------------- ----------------  ---------
  Layer 7 | Application          | Data             ^
  Layer 6 | Presentation         | Data             | Decapsulation
  Layer 5 | Session              | Data             | (receiving)
  Layer 4 | Transport            | Segment          |
  Layer 3 | Network              | Packet           |
  Layer 2 | Data Link            | Frame            |
  Layer 1 | Physical             | Bits             v Encapsulation (sending)
    

Mnemonic (top to bottom): "All People Seem To Need Data Processing" (Application, Presentation, Session, Transport, Network, Data Link, Physical)

Mnemonic (bottom to top): "Please Do Not Throw Sausage Pizza Away" (Physical, Data Link, Network, Transport, Session, Presentation, Application)

Related pages: TCP/IP Model | Layer Functions | MAC Addresses | IP Addressing | Frame Forwarding (L2) | Ethernet Standards (L1) | VLANs (L2) | STP (L2) | Ping | Traceroute

2. Why the OSI Model Matters

• Interoperability: Defines standard interfaces so hardware and software from different vendors can communicate — a Cisco router can talk to a Juniper router because they both implement the same Layer 3 standards
• Troubleshooting: Lets engineers isolate problems to a specific layer — a cable fault is a Layer 1 issue, a MAC address conflict is Layer 2, a routing problem is Layer 3
• Protocol design: Protocols are written to operate at specific layers with defined inputs and outputs, making them modular and replaceable
• Exam currency: The OSI model is referenced throughout CCNA and all other networking certifications as the common framework for discussing network behaviour

3. Quick-Reference: All 7 Layers

4. Layer-by-Layer Deep Dive

Layer 1 — Physical Layer

The Physical Layer is responsible for the actual transmission of raw binary data (bits) across a physical medium. It defines the electrical, optical, radio, and mechanical characteristics of the transmission medium — voltage levels, cable types, connector pinouts, bit timing, and signal encoding.

Layer 2 — Data Link Layer

The Data Link Layer packages raw bits into frames and manages node-to-node delivery within a single network segment. It uses MAC addresses (hardware addresses burned into NICs) to identify source and destination on the local network, and provides error detection via the FCS (Frame Check Sequence) trailer.

Layer 3 — Network Layer

The Network Layer provides logical addressing (IP addresses) and routing — the ability to deliver packets between devices on different networks. While Layer 2 handles delivery within a single LAN segment, Layer 3 handles delivery across multiple networks (inter-network routing).

Layer 4 — Transport Layer

The Transport Layer provides end-to-end communication between applications on different hosts. It segments large data into smaller pieces, manages flow control, provides error recovery (TCP), and uses port numbers to identify which application process should receive each segment.

Layer 5 — Session Layer

The Session Layer manages sessions — the logical connections (dialogues) between two applications. It establishes, maintains, and terminates communication sessions, and can insert checkpoints into data streams so a session can be resumed from the last checkpoint if interrupted rather than restarting from scratch.

Layer 6 — Presentation Layer

The Presentation Layer is the translator of the OSI model. It converts data between the format used by the application and a standardised network format, ensuring that data produced by one system can be understood by another. It also handles encryption/decryption and compression/decompression.

Layer 7 — Application Layer

The Application Layer is the topmost layer and the one users interact with directly — it provides the interface between network services and user applications. It does not include the application software itself (e.g., Chrome is not an OSI layer), but rather the protocols those applications use to communicate over the network.

5. Encapsulation and Decapsulation

Encapsulation is the process by which each layer adds its own header (and sometimes trailer) as data travels down the OSI stack on the sending device. Decapsulation is the reverse — each layer removes its header as data travels up the stack on the receiving device.

Encapsulation — Sending a Web Page Request

  Layer 7 Application    HTTP request: "GET /index.html HTTP/1.1"
                                 |
                         [HTTP Header | Data]
                                 |
  Layer 4 Transport      TCP adds: source port 49152, dest port 80, seq/ack
                         [TCP Header | HTTP Header | Data]           = Segment
                                 |
  Layer 3 Network        IP adds: src IP 192.168.1.10, dst IP 93.184.216.34
                         [IP Header | TCP Header | HTTP Header | Data] = Packet
                                 |
  Layer 2 Data Link      Ethernet adds: src MAC, dst MAC, FCS trailer
                   [Eth Header | IP Header | TCP Header | HTTP Header | Data | FCS] = Frame
                                 |
  Layer 1 Physical       Convert frame to electrical/optical/radio signal
                         10101001 01101101 ... (Bits transmitted on wire)
    

Decapsulation — Receiving the Frame

At the destination server, the process reverses:

1. Layer 1: Physical signal received and converted back to bits
2. Layer 2: Ethernet header examined — destination MAC matches, FCS checked for errors, Ethernet header stripped → passes Packet to Layer 3
3. Layer 3: IP header examined — destination IP matches, IP header stripped → passes Segment to Layer 4
4. Layer 4: TCP header examined — port 80 directs to the web server process, TCP header stripped → passes Data to Layer 7
5. Layer 7: HTTP data delivered to the web server application

PDU Names at Each Layer

6. OSI Model vs TCP/IP Model

The TCP/IP model is the practical model actually used by the internet and modern networks. It was developed before the OSI model and collapses several OSI layers into four (or five, depending on the version used).

The key differences: TCP/IP collapses OSI Layers 5, 6, and 7 into a single Application layer. TCP/IP merges (or separately identifies) Layers 1 and 2 as Network Access / Link / Physical. TCP/IP is a working model; OSI is a theoretical reference model.

7. Troubleshooting by OSI Layer

The OSI model's greatest practical value is in systematic troubleshooting. Engineers typically work from Layer 1 upward (bottom-up approach) or from Layer 7 downward (top-down approach), isolating the problem at its exact layer.

8. End-to-End Example: Sending an Email

John sends an email from his laptop to a colleague. Here is the full OSI journey:

OSI Model Quiz