OSI model
| OSI model by layer |
|---|
The Open Systems Interconnection Reference Model (OSI Model or OSI Reference Model for short) is a layered, abstract description for communications and computer network protocol design, developed as part of the Open Systems Interconnection initiative. It is also called the OSI seven layer model.
Purpose
The OSI model divides the functions of a protocol into a series of layers. Each layer has the property that it only uses the functions of the layer below, and only exports functionality to the layer above. A system that implements protocol behavior consisting of a series of these layers is known as a 'protocol stack' or 'stack'. Protocol stacks can be implemented either in hardware or software, or a mixture of both. Typically, only the lower layers are implemented in hardware, with the higher layers being implemented in software.
This OSI model is roughly adhered to in the computing and networking industry. Its main feature is in the interface between layers which dictates the specifications on how one layer interacts with another. This means that a layer written by one manufacturer can operate with a layer from another (assuming that the specification is interpreted correctly). These specifications are typically known as Requests for Comments or "RFC"s in the TCP/IP community. They are ISO standards in the OSI community.
Usually, the implementation of a protocol is layered in a similar way to the protocol design, with the possible exception of a 'fast path' where the most common transaction allowed by the system may be implemented as a single component encompassing aspects of several layers.
This logical separation of layers makes reasoning about the behavior of protocol stacks much easier, allowing the design of elaborate but highly reliable protocol stacks. Each layer performs services for the next higher layer and makes requests of the next lower layer. As previously stated, an implementation of several OSI layers is often referred to as a stack (as in TCP/IP stack).
The OSI reference model is a hierarchical structure of seven layers that defines the requirements for communications between two computers. The model was defined by the International Organization for Standardization in the ISO standard 7498-1. It was conceived to allow interoperability across the various platforms offered by vendors. The model allows all network elements to operate together, regardless of who built them. By the late 1980's, ISO was recommending the implementation of the OSI model as a networking standard.
Of course, by that time, TCP/IP had been in use for years. TCP/IP was fundamental to ARPANET and the other networks that evolved into the Internet. (For significant differences between TCP/IP and ARPANET, see RFC 871.
Only a subset of the whole OSI model is used today. It is widely believed that much of the specification is too complicated and that its full functionality has taken too long to implement, although there are many people who strongly support the OSI model.
Description of OSI layers
Layer 7: Application Layer
The Application layer is closest to the end user. It provides a means for the user to access information on the network through an application. This layer is the main interface for the user(s) to interact with the application and therefore the network. Some examples of application layer protocols include Telnet, File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP) and Hypertext Transfer Protocol (HTTP).
Layer 6: Presentation Layer
The Presentation layer transforms data to provide a standard interface for the Application layer. MIME encoding, data compression, data encryption and similar manipulation of the presentation is done at this layer to present the data as a service or protocol developer sees fit. Examples: converting an EBCDIC-coded text file to an ASCII-coded file, or serializing objects and other data structures into and out of XML.
Layer 5: Session Layer
The Session layer controls the dialogues (sessions) between computers. It establishes, manages and terminates the connections between the local and remote application. It provides for either duplex or half-duplex 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 TCP, and also for session checkpointing and recovery, which is not usually used in the Internet protocol suite.
Layer 4: Transport Layer
The Transport layer provides transparent transfer of data between end users, thus relieving the upper layers from any concern while providing reliable and cost-effective data transfer. The transport layer controls the reliability of a given link. Some protocols are state and connection oriented. This means that the transport layer can keep track of the packets and retransmit those that fail. The best known example of a layer 4 protocol is the Transmission Control Protocol (TCP). It is the layer that converts messages into TCP, User Datagram Protocol (UDP), Stream Control Transmission Protocol (SCTP), etc. packets.
Layer 3: Network Layer
The Network layer provides the functional and procedural means of transferring variable length data sequences from a source to a destination via one or more networks while maintaining the quality of service requested by the Transport layer. The Network layer performs network routing, flow control, segmentation/desegmentation, and error control functions. Routers operate at this layer—sending data throughout the extended network and making the Internet possible (there also exist layer 3 (or IP) switches). This is a logical addressing scheme – values are chosen by the network engineer. The addressing scheme is hierarchical. The best known example of a layer 3 protocol is the Internet Protocol (IP).
Layer 2: Data Link Layer
The Data Link layer provides the functional and procedural means to transfer data between network entities and to detect and possibly correct errors that may occur in the Physical layer. The addressing scheme is physical which means that the addresses (MAC address) are hard-coded into the network cards at the time of manufacture. The addressing scheme is flat. Note: The best known example of this is Ethernet. Other examples of data link protocols are HDLC and ADCCP for point-to-point or packet-switched networks and Aloha for local area networks. On IEEE 802 local area networks, and some non-IEEE 802 networks such as FDDI, this layer may be split into a Media Access Control (MAC) layer and the IEEE 802.2 Logical Link Control (LLC) layer.
This is the layer at which the bridges and switches operate. Connectivity is provided only among locally attached network nodes. However, there's a reasonable argument to be made that these really belong at "layer 2.5" rather than strictly at layer 2.
Layer 1: Physical Layer
The Physical layer defines all the electrical and physical specifications for devices. This includes the layout of pins, voltages, and cable specifications. Hubs, repeaters, network adapters and Host Bus Adapters (HBAs used in Storage Area Networks) are physical-layer devices. The major functions and services performed by the physical layer are:
- establishment and termination of a connection to a communications medium.
- participation in the process whereby the communication resources are effectively shared among multiple users. For example, contention resolution and flow control.
- modulation, or conversion between the representation of digital data in user equipment and the corresponding signals transmitted over a communications channel. These are signals operating over the physical cabling—copper and fiber optic, for example—or over a radio link.
Parallel SCSI buses operate in this layer. Various physical-layer Ethernet standards are also in this layer; Ethernet incorporates both this layer and the data-link layer. The same applies to other local-area networks, such as Token ring, FDDI, and IEEE 802.11.
Interfaces
In addition to standards for individual protocols in transmission, there are also interface standards for different layers to talk to the ones above or below (usually operating-system–specific). For example, Microsoft Windows's Winsock, and Unix's Berkeley sockets and System V Transport Layer Interface, are interfaces between applications (layers 5 and above) and the transport (layer 4). NDIS and ODI are interfaces between the media (layer 2) and the network protocol (layer 3).
Table of examples
Parallel
Humor
- The 7 layer model has often been extended in a humorous manner, to refer to non-technical issues or problems. A common joke is the 10 layer model, with layers 8, 9, and 10 being the "user," "financial," and "political" layers.
- Network technicians will sometimes refer to "layer-eight problems," meaning problems with an end user and not with the network.
- The OSI model has also been jokingly called the "Taco Bell model", since the restaurant chain has been known for their 7 layer burrito.
- Dick Lewis uses an analogy of James Bond delivering classified messages to illustrate the seven-layer model.
Mnemonics
In the network design OSI model, the seven layers (Physical, Data link, Network, Transport, Session, Presentation, and Application) can be remembered with the aid of mnemonics such as:
- Please Do Not Throw Sausage Pizza Away [2]
- All People Seem To Need Data Processing[2]
- APS Transports Network Data Physically (separates upper and lower layer groups)[2]
- Please Do Not Teach Students Pointless Acronyms
- Please Do Not Tell Secret Passwords Anytime[2]
- All People Still Think Networks Don't Process
See also
References
- ^ "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.
- ^ a b c d http://www.dummies.com/WileyCDA/DummiesArticle/id-2264.html
External links
- ISO standard 7498-1:1994
- Cybertelecom :: Layered Model of Regulation
- OSI Model Tutorial
- OSI Model Tutorial In Flash
- Computer Networks and Protocol - The OSI Reference Model
- OSI Reference Model—The ISO Model of Architecture for Open Systems Interconnection, Hubert Zimmermann, IEEE Transactions on Communications, vol. 28, no. 4, April 1980, pp. 425 - 432.