UNIT 2: REFERENCE MODELS
1. OSI SEVEN-LAYER MODEL
The Open Systems Interconnection (OSI) model is a theoretical, comprehensive framework for network communication, developed by ISO. It standardizes functions into seven hierarchical layers. Each layer provides services to the layer above it and uses services from the layer below it. Communication is achieved through encapsulation (adding headers/trailers) on the sender side and de-encapsulation on the receiver side.
Layer-wise Functions & Protocol Data Unit (PDU):
| Layer (7 → 1) | Name | Primary Function | PDU |
|---|---|---|---|
| 7 | Application | Interface for user applications (e.g., HTTP, FTP, SMTP). Provides network services directly to end-user software. | Data |
| 6 | Presentation | Data translation, encryption, compression. Ensures data is in a readable format for the application layer (e.g., SSL/TLS for encryption). | Data |
| 5 | Session | Establishes, manages, and terminates sessions (connections) between applications. Handles synchronization and dialog control. | Data |
| 4 | Transport | End-to-end connection control, reliability, and flow control. Segments data, ensures complete and ordered delivery (TCP) or provides best-effort delivery (UDP). | Segment (TCP) / Datagram (UDP) |
| 3 | Network | Logical addressing and path determination (routing). Determines the best physical path for data across networks (e.g., IP). | Packet |
| 2 | Data Link | Node-to-node data transfer, framing, error detection/correction. Organizes bits into frames, handles physical addressing (MAC), and manages access to the medium. | Frame |
| 1 | Physical | Transmission of raw bits over the physical medium. Defines electrical, mechanical, and functional specifications (cables, connectors, voltages). | Bits |
Interaction Flow (Encapsulation):
Application Data → (Presentation/Session add headers) → Segment (Transport) → Packet (Network) → Frame (Data Link) → Bits (Physical) → Medium.
Key Exam Points:
-
Layers 5-7 are software/process-oriented. Layers 1-4 are data transmission-oriented.
-
Peer-to-peer communication occurs only between corresponding layers on different systems.
-
The Data Link layer is split into LLC (Logical Link Control) and MAC (Medium Access Control) sublayers in practice.
2. TCP/IP REFERENCE MODEL
The TCP/IP model is a practical, implementation-focused protocol suite that powers the modern internet. It has four (or five) layers, with functionality often overlapping OSI layers.
| Layer (Top → Bottom) | Name | Function & Key Protocols | OSI Layer Mapping |
|---|---|---|---|
| 5 (Optional) | Application | Combines OSI's Application, Presentation, and Session layers. Provides applications with network access. | 5, 6, 7 |
| 4 | Transport | End-to-end host-to-host communication. Key protocols: TCP (reliable, connection-oriented) and UDP (unreliable, connectionless). | 4 |
| 3 | Internet | Logical addressing and routing. Core protocol is IP (Internet Protocol). Handles packet forwarding across networks. | 3 |
| 2 | Network Access (Link) | Combines OSI's Data Link and Physical layers. Defines how data is physically transmitted over a specific medium (Ethernet, Wi-Fi, PPP). | 1, 2 |
Key Exam Points:
-
TCP/IP is the de facto standard for internetworking.
-
The Application layer protocols (HTTP, FTP, SMTP) are application-specific, not general services.
-
The Internet layer is connectionless and best-effort (IP does not guarantee delivery).
3. COMPARISON: OSI vs. TCP/IP MODEL
| Feature | OSI Model | TCP/IP Model |
|---|---|---|
| Nature | Theoretical reference model. Defines standards for interoperability. | Practical, protocol-centric model. Based on standard internet protocols. |
| Layers | 7 distinct layers (strict separation). | 4/5 layers (combines OSI's upper and lower layers). |
| Protocols | Protocol-independent. Defines what each layer should do. | Protocol-dependent. Built around specific protocols (TCP, IP, UDP). |
| Communication | Peer-to-peer between same layers. | Peer-to-peer is less rigid; often vertical integration. |
| Approach | Top-down design. Services are defined first. | Bottom-up implementation. Protocols were developed first, then modeled. |
| Flexibility | Rigid, difficult to modify. | Flexible, easily adaptable to new technologies. |
| Usage | Guide for design and understanding. Not directly implemented. | Basis for the entire Internet and modern networks. Directly implemented. |
| Layer 5-7 | Separate Session, Presentation, Application layers. | Combined into a single Application layer. |
| Layer 1-2 | Separate Data Link and Physical layers. | Combined into Network Access (Link) layer. |
| Routing | Network layer handles routing. | Internet layer (IP) handles routing. |
| Reliability | Can be implemented at Transport or lower layers. | Reliability is primarily a Transport layer (TCP) function. |
[!TIP] Exam Trap: A common mistake is to force a one-to-one mapping. Remember: TCP/IP's Application layer = OSI's L5+L6+L7 and TCP/IP's Link layer = OSI's L1+L2. The OSI model is for conceptual understanding; TCP/IP is for real-world implementation.
4. KEY CONCEPTS & FORMULAS
-
Encapsulation: Process of adding control information (headers/trailers) as data passes down the OSI layers.
Data (L7) → Segment (L4) → Packet (L3) → Frame (L2) → Bits (L1)
-
De-encapsulation: Reverse process at the receiver, stripping headers/trailers.
-
Protocol Data Unit (PDU): The name for the data unit at each layer (Segment, Packet, Frame, Bit).
-
Addressing:
-
Physical (L2): MAC Address (48-bit, burned into NIC).
-
Logical (L3): IP Address (32-bit IPv4, 128-bit IPv6).
-
Application (L7): Port Number (16-bit, e.g., 80 for HTTP).
-
\boxed{\text{Core Takeaway: OSI is the "what" (reference), TCP/IP is the "how" (implementation).}}
Next Unit Focus: Based on past papers, Unit 3 (Physical Layer) is next with high-frequency questions on Line Encoding (NRZ, Manchester), Transmission Media, and Transmission Impairments. Prepare detailed comparisons of encoding schemes and media types.