Every Network Message Takes a Journey

When you visit a website, send an email, or upload a file, the information doesn't simply leave your computer and arrive at its destination.

Before transmission can occur, that data must be prepared for the network.

• It needs addressing information.
• It needs routing information.
• It needs delivery instructions.
• It needs error-checking mechanisms.

The process of progressively adding this information is called encapsulation.

Encapsulation is one of the most important concepts in networking because it explains how different protocols and OSI layers work together to move data across the internet.

Every packet captured in Wireshark and every web request generated by your browser is the result of encapsulation.

What Is Encapsulation?

Encapsulation is the process of wrapping data with layer-specific information as it travels down the OSI Model.

Each layer adds its own header—and sometimes a trailer—before passing the data to the layer below.

A useful analogy is shipping a package.

Imagine sending a valuable item:

1. The item is placed inside a box.
2. A shipping label is attached.
3. Tracking information is added.
4. The package is handed to a delivery company.
5. Transportation systems move it toward its destination.

Networking works in a similar way.

Each layer contributes information that helps deliver the data successfully.

The Protocol Data Units (PDUs)

As data moves through the OSI layers, it changes form.

Each layer has a specific name for the unit of data it processes.

These names are called Protocol Data Units (PDUs).

Understanding these names is essential because networking professionals use them constantly during troubleshooting and protocol analysis.

💡 Tip: If someone says, "I captured a packet," they are referring to Layer 3 data. If they mention a frame, they're talking about Layer 2.

Following a Real HTTP Request

Let's trace a simplified web request through the encapsulation process.

Suppose you type:

https://example.com

into your browser and press Enter.

Your browser generates an HTTP request that begins its journey through the OSI layers.

Step 1: Application Layer

The Application Layer creates the actual request.

It may look something like:

GET /index.html HTTP/1.1
Host: example.com
Accept: text/html

At this point, we only have application data.

No addressing information exists yet.

No packet exists.

No frame exists.

Just data.

Step 2: Presentation Layer

The Presentation Layer prepares the data for transmission.

Depending on the application, this can include:

• Encryption
• Compression
• Character encoding
• Data translation

If HTTPS is being used, TLS encryption transforms the readable request into encrypted ciphertext.

To anyone intercepting the traffic, the content becomes unreadable.

Step 3: Session Layer

The Session Layer manages the communication session between client and server.

Its responsibilities include:

• Establishing communication
• Maintaining active sessions
• Synchronizing communication
• Closing sessions properly

In modern networking, session management is often handled by protocols operating alongside TCP and application-layer technologies, but the OSI Model uses this layer to describe those responsibilities conceptually.

Step 4: Transport Layer

Now the Transport Layer takes control.

If TCP is being used, a TCP header is added.

Important information includes:

• Source Port
• Destination Port
• Sequence Number
• Acknowledgment Number
• TCP Flags

For example:

Source Port: 52341
Destination Port: 443

The data is now called a:

TCP Segment

This layer is responsible for ensuring data arrives reliably and in the correct order.

Step 5: Network Layer

The Network Layer adds an IP header.

This is where logical addressing enters the picture.

Typical information includes:

Source IP: 192.168.1.50
Destination IP: 93.184.216.34
TTL: 64
Protocol: TCP

The segment is now wrapped inside a:

Packet

Routers throughout the internet use this information to determine where the data should travel next.

Step 6: Data Link Layer

Next comes local delivery.

The Data Link Layer creates a frame by adding:

• Source MAC Address
• Destination MAC Address
• Error Detection Information

Example:

Source MAC:
00:1A:2B:3C:4D:5E

Destination MAC:
A4:7B:9D:11:22:33

The packet is now enclosed inside a:

Frame

An important detail many beginners miss:

The destination MAC address is typically not the final destination server.

It is usually the next device on the local network, such as a router.

Step 7: Physical Layer

Finally, the frame reaches the Physical Layer.

At this point, the frame is converted into:

• Electrical signals
• Light pulses
• Radio waves

depending on the transmission medium being used.

The frame becomes a stream of:

Bits

These bits travel across Ethernet cables, fiber-optic connections, Wi-Fi networks, and countless networking devices before reaching their destination.

Visualizing the Encapsulation Process

The transformation can be summarized like this:

Application Data
│
▼
TCP Segment
│
▼
IP Packet
│
▼
Ethernet Frame
│
▼
Bits

Each layer wraps the data from the layer above, creating a structure often compared to Russian nesting dolls.

Every layer adds information without modifying the original payload.

De-Encapsulation: The Reverse Process

When the destination receives the data, the process runs in reverse.

Physical Layer

Receives bits.

Data Link Layer

Removes frame information.

Network Layer

Removes the IP header.

Transport Layer

Removes the TCP header and reassembles segments.

Upper Layers

Decrypt, decode, and deliver the original message to the application.

The server ultimately receives the exact HTTP request that was originally created by the browser.

This reverse process is known as de-encapsulation.

See Encapsulation Happen in Real Time

Encapsulation is one of those concepts that becomes dramatically easier once you can watch it happen.

The Roboticela OSI Model Simulator allows you to enter your own message and observe how it changes as each OSI layer adds its information. You can inspect headers, view protocol details, and follow the complete journey from application data to transmitted bits.

For advanced exploration, try enabling the optional hexadecimal view to see how data appears closer to its machine-readable representation.

Landing Page

Launch Simulator

Key Takeaways

• Encapsulation prepares data for network transmission.
• Each OSI layer adds information needed for delivery.
• Protocol Data Units (PDUs) change as data moves through the layers.
• Data becomes a segment, packet, frame, and finally bits.
• The receiving system performs de-encapsulation to recover the original message.
• Encapsulation is one of the core concepts behind all modern network communication.

Conclusion

Every website you visit, every file you upload, and every message you send relies on encapsulation.

Although it happens in milliseconds, the process is remarkably sophisticated. Multiple layers cooperate to add addressing, reliability, routing, and delivery information until a simple piece of data becomes something the network can transport.

Once you understand encapsulation, networking starts to feel less like magic and more like a carefully engineered system.

In the next article, we'll explore the opposite side of communication and examine exactly how de-encapsulation reconstructs the original message at the destination device.