OSI Layers and Encapsulation

The OSI model describes seven layers, from application at the top to physical at the bottom. Application supports network application services; presentation concerns representations such as encoding; session concerns managing a dialogue; transport provides end-to-end transport services; network handles logical addressing/routing; data link handles communication over a link; and physical concerns transmitted signals.

It is a reference model, not a claim that every deployed protocol fits into one perfectly isolated box. Functions can be combined in actual software. For a diagram task, name the layer’s responsibility before assigning an example. An application-layer protocol is not the same thing as the entire user application, and reliable transport is a service choice rather than a property of every possible transport protocol.

Scroll the diagram to see the full view.

Encapsulation adds protocol information as data move down a sending stack. In a common Internet example, application bytes become a TCP segment, carried inside an IP packet, carried inside a link frame and represented as physical signals. Decapsulation at the receiver interprets/removes the appropriate information and passes the payload upwards. The wrapper belongs to the protocol operating at that stage.

An intermediate router processes the incoming link delivery and the IP routing information, then sends a new frame appropriate to the next link. The next-hop link addresses can differ from the previous link’s. Do not assume one Ethernet frame travels unchanged across the whole Internet. End-to-end addresses/ports also need qualification when mechanisms such as NAT are involved; state the simple model used in the trace.

Assume 1000 application bytes, a 20-byte TCP header, 20-byte IP header, 14-byte link header and four-byte link trailer, with no other overhead. The model sends 1058 bytes at the counted link-frame level. Its application payload fraction is 1000/1058≈94.52%. Physical preambles, gaps, options and other protocols are deliberately outside this model.

This example separates payload size from transmitted size. Headers vary by protocol, options and version, so do not memorise the example’s sum as a universal overhead. Similarly, one application message can require several transport segments or share a stream with other messages. Label the unit being counted and the endpoints of the comparison before calculating efficiency or transmission time.

Attempt the task before opening its worked response. Record each change of state, explain the rule used, and check the result against the original requirements. Code examples labelled Python 3 use that language’s conventions; pseudocode states its own assumptions.