OSI protocols

The Open Systems Interconnection protocols are a family of information exchange standards developed jointly by the ISO and the ITU-T. The standardization process began in 1977.

While the seven-layer OSI model is often used as a reference for teaching and documentation,[2] the protocols originally conceived for the model did not gain popularity, and only X.400, X.500, and IS-IS have achieved lasting impact. The goal of an open-standard protocol suite instead has been met by the Internet protocol suite, maintained by the Internet Engineering Task Force (IETF).


The OSI protocol stack is structured into seven conceptual layers. The layers form a hierarchy of functionality starting with the physical hardware components to the user interfaces at the software application level. Each layer receives information from the layer above, processes it and passes it down to the next layer. Each layer adds encapsulation information (header) to the incoming information before it is passed to the lower layer. Headers generally include address of source and destination, error control information, protocol identification and protocol parameters such as flow control options and sequence numbers.

OSI model
Layer Protocol data unit (PDU) Function[3]
7 Application Data High-level protocols such as for resource sharing or remote file access, e.g. HTTP.
6 Presentation Translation of data between a networking service and an application; including character encoding, data compression and encryption/decryption
5 Session Managing communication sessions, i.e., continuous exchange of information in the form of multiple back-and-forth transmissions between two nodes
4 Transport Segment, Datagram Reliable transmission of data segments between points on a network, including segmentation, acknowledgement and multiplexing
3 Network Packet Structuring and managing a multi-node network, including addressing, routing and traffic control
2 Data link Frame Transmission of data frames between two nodes connected by a physical layer
1 Physical Bit, Symbol Transmission and reception of raw bit streams over a physical medium

Layer 1: physical layerEdit

This layer deals with the physical plugs and sockets and electrical specification of signals only.

This is the medium over which the digital signals are transmitted. It can be twisted pair, coaxial cable, optical fiber, wireless, or other transmission media.

Layer 2: data link layerEdit

The data link layer packages raw bits from the physical layer into frames (logical, structured packets for data). It is specified in ITU-T Rec. X.212 [ISO/IEC 8886], ITU-T Rec. X.222 and others. This layer is responsible for transferring frames from one host to another. It might perform error checking. This layer further consists of two sublayers: MAC and LLC.

Layer 3: network layerEdit

This level is in charge of transferring data between systems in a network, using network-layer addresses of machines to keep track of destinations and sources. This layer uses routers and switches to manage its traffic (control flow control, error check, routing etc.) So here it takes all routing decisions, it deals with end to end data transmission.

Layer 4: transport layerEdit

The connection-mode and connectionless-mode transport services are specified by ITU-T Rec. X.214 [ISO/IEC 8072]; the protocol that provides the connection-mode service is specified by ITU-T Rec. X.224 [ISO/IEC 8073], and the protocol that provides the connectionless-mode service is specified by ITU-T Rec. X.234 [ISO/IEC 8602].

  • Transport Protocol Class 0 (TP0)
  • Transport Protocol Class 1 (TP1)
  • Transport Protocol Class 2 (TP2)
  • Transport Protocol Class 3 (TP3)
  • Transport Protocol Class 4 (TP4)
  • Transport Fast Byte Protocol – ISO 14699

The transport layer transfers data between source and destination processes. Generally, two connection modes are recognized, connection-oriented or connectionless. Connection-oriented service establishes a dedicated virtual circuit and offers various grades of guaranteed delivery, ensuring that data received is identical to data transmitted. Connectionless mode provides only best-effort service without the built-in ability to correct errors, which includes complete loss of data without notifying the data source of the failure. No logical connection, and no persistent state of the transaction exists between the endpoints, lending the connectionless mode low overhead and potentially better real-time performance for timing-critical applications such as voice and video transmissions.

Layer 5: session layerEdit

The session layer controls the dialogues (connections) between computers. It establishes, manages and terminates the connections between the local and remote application. It provides for full-duplex, and half-duplex or simplex operation, and establishes checkpointing, adjournment, termination, and restart procedures. The OSI model made this layer responsible for graceful close of sessions, which is a property of the Transmission Control Protocol, and also for session checkpointing and recovery, which is not usually used in the Internet Protocol Suite. The session layer is commonly implemented explicitly in application environments that use remote procedure calls.

Layer 6: presentation layerEdit

This layer defines and encrypts/decrypts data types from the application layer. Protocols such as MIDI, MPEG, and GIF are presentation layer formats shared by different applications.

Layer 7: application layerEdit

Common-Application Service Elements (CASEs)Edit

This keeps track of how each application talks to another application. Destination and source addresses are linked to specific applications.

Application processesEdit

Routing protocolsEdit

See alsoEdit


  1. ^ "X.225 : Information technology – Open Systems Interconnection – Connection-oriented Session protocol: Protocol specification". Archived from the original on 1 February 2021. Retrieved 10 March 2023.
  2. ^ Shaw, Keith (2018-10-22). "The OSI model explained: How to understand (and remember) the 7 layer network model". Network World. Retrieved 2020-05-16.
  3. ^ "Windows Network Architecture and the OSI Model". Microsoft Documentation. Retrieved 24 June 2020.
  4. ^ FTAM support claimed by IBM, Novell, Sun, Unisys etc Archived 2013-03-02 at the Wayback Machine, Joint Interoperability Test Command