1.2 Network Architecture and Protocols

Network Architecture and Protocols

Network architecture defines how networks are structured and operated, giving you a blueprint for how devices exchange data. Protocols are the standardized rules that make this communication possible. Together, they explain why the internet works the way it does, and understanding them is the foundation for everything else in this course.

Concept of Network Architecture

Network architecture is the overall design plan for a computer network. It specifies the components (routers, switches, servers), the protocols they use, and how they're all connected.

Think of it as a blueprint. Just like a building's architecture determines where walls, doors, and wiring go, network architecture determines how data flows between devices. A well-designed architecture achieves several goals:

• Interoperability: Devices from different manufacturers can communicate using shared standards
• Scalability: The network can grow (more users, more devices) without being redesigned from scratch
• Reliability: If one component fails, the network can still function
• Performance optimization: Data takes efficient paths, and bottlenecks are minimized

Network architecture applies at every scale, from a small local area network (LAN) in an office to wide area networks (WANs) spanning continents. It also enables the development of services like cloud computing and IoT that depend on predictable, well-organized network behavior.

Layered Approach in Network Design

Rather than treating a network as one massive system, engineers divide its functionality into distinct layers. Each layer handles a specific set of tasks and provides services to the layer above it. The two most common models are the OSI model (7 layers) and the TCP/IP model (4 layers), but the core idea is the same.

Why layers? Because they let you change one part of the system without breaking everything else. You can swap out the physical cables (physical layer) without rewriting your web browser (application layer). Layers communicate through well-defined interfaces and protocols.

Here are the five key layers you need to know, from top to bottom:

1. Application layer

   • The layer closest to the user. It provides services directly to applications like web browsers and email clients.
   • Protocols: HTTP, FTP, SMTP

2. Transport layer

   • Ensures reliable end-to-end data delivery between processes on different hosts. It breaks data into segments and handles error recovery through mechanisms like retransmission and acknowledgments.
   • Protocols: TCP (reliable, connection-oriented), UDP (faster, connectionless)

3. Network layer

   • Routes packets from source to destination across potentially many intermediate networks. It uses logical addressing (IP addresses) to identify devices.
   • Protocols: IP, ICMP

4. Data link layer

   • Handles data transfer between adjacent network nodes (e.g., your computer to the nearest switch). It provides error detection using techniques like CRC checksums.
   • Protocols: Ethernet, Wi-Fi (802.11)

5. Physical layer

   • Defines the physical medium itself: cables, connectors, signal encoding, and modulation. This layer deals with transmitting raw bits as electrical signals, light pulses, or radio waves.
   • Examples: twisted pair cable, fiber optic, wireless radio

Key Network Protocols

TCP/IP (Transmission Control Protocol / Internet Protocol)

TCP/IP is the protocol suite that powers the internet. It has two core components:

• IP handles logical addressing and routing. Every device on the internet gets an IP address (IPv4 uses 32-bit addresses like 192.168.1.1; IPv6 uses 128-bit addresses to support far more devices). IP is responsible for getting packets to the right destination, but it doesn't guarantee delivery.
• TCP adds reliability on top of IP. It ensures data arrives in order, without errors, and without missing pieces. TCP establishes connections using a three-way handshake (SYN → SYN-ACK → ACK) and tracks data using sequence numbers so lost segments can be retransmitted.

HTTP (Hypertext Transfer Protocol)

HTTP is the application-layer protocol that drives the web. It follows a client-server model: your browser (client) sends a request to a web server, and the server responds with the requested resource (HTML pages, images, etc.).

HTTP defines several request methods:

• GET: Retrieve a resource
• POST: Send data to the server (e.g., submitting a form)
• PUT: Update an existing resource

These methods form the basis of RESTful APIs, which you'll encounter frequently in web development and networked applications.

Interaction of Layers and Protocols

The layers don't work in isolation. They cooperate through a process called encapsulation.

How encapsulation works: As data moves down the layers on the sending device, each layer wraps the data with its own header (and sometimes a trailer) containing control information. On the receiving device, the process reverses: each layer strips off its corresponding header as data moves up the stack. This reverse process is called de-encapsulation.

Each layer's unit of data has a specific name, called a protocol data unit (PDU):

Example: What happens when you send an HTTP request

1. Application layer: Your browser creates an HTTP request containing the URL, headers, and body
2. Transport layer: TCP breaks the request into segments and adds a TCP header with port numbers and sequence numbers
3. Network layer: IP wraps each segment in a packet and adds an IP header with source and destination IP addresses
4. Data link layer: Ethernet wraps each packet in a frame, adding a header with source and destination MAC addresses (plus a trailer for error checking)
5. Physical layer: The frame is converted to raw bits and transmitted over the physical medium as electrical signals, light pulses, or radio waves

At the destination, this entire process runs in reverse. The physical layer receives the bits, the data link layer reads and removes the Ethernet header, the network layer reads and removes the IP header, and so on, until the original HTTP request reaches the server's application layer.