When most non-technical people hear the term “seven layers”, they either think of the popular Super Bowl bean dip or they mistakenly think about the seven layers of Hell, courtesy of Dante’s Inferno (there are nine). For IT professionals, the seven layers refer to the Open Systems Interconnection (OSI) model, a conceptual framework that describes the functions of a networking or telecommunication system.
The model uses layers to help give a visual description of what is going on with a particular networking system. This can help network managers narrow down problems (Is it a physical issue or something with the application?), as well as computer programmers (when developing an application, which other layers does it need to work with?). Tech vendors selling new products will often refer to the OSI model to help customers understand which layer their products work with or whether it works “across the stack”.
Conceived in the 1970s when computer networking was taking off, two separate models were merged in 1983 and published in 1984 to create the OSI model that most people are familiar with today. Most descriptions of the OSI model go from top to bottom, with the numbers going from Layer 7 down to Layer 1. The layers, and what they represent, are as follows:
Layer 7 – Application
To further our bean dip analogy, the Application Layer is the one at the top – it’s what most users see. In the OSI model, this is the layer that is the “closest to the end user”. Applications that work at Layer 7 are the ones that users interact with directly. A web browser (Google Chrome, Firefox, Safari, etc.) or other app – Skype, Outlook, Office – are examples of Layer 7 applications.
Layer 6 – Presentation
The Presentation Layer represents the area that is independent of data representation at the application layer – in general, it represents the preparation or translation of application format to network format, or from network formatting to application format. In other words, the layer “presents” data for the application or the network. A good example of this is encryption and decryption of data for secure transmission – this happens at Layer 6.
Layer 5 – Session
When two devices, computers or servers need to “speak” with one another, a session needs to be created, and this is done at the Session Layer. Functions at this layer involve setup, coordination (how long should a system wait for a response, for example) and termination between the applications at each end of the session.
Layer 4 – Transport
The Transport Layer deals with the coordination of the data transfer between end systems and hosts. How much data to send, at what rate, where it goes, etc. The best known example of the Transport Layer is the Transmission Control Protocol (TCP), which is built on top of the Internet Protocol (IP), commonly known as TCP/IP. Your device’s IP address works here.
Layer 3 – Network
Here at the Network Layer is where you’ll find most of the router functionality that most networking professionals care about and love. In its most basic sense, this layer is responsible for packet forwarding, including routing through different routers. You might know that your Boston computer wants to connect to a server in California, but there are millions of different paths to take. Routers at this layer help do this efficiently.
Layer 2 – Data Link
The Data Link Layer provides node-to-node data transfer (between two directly connected nodes), and also handles error correction from the physical layer. Two sublayers exist here as well – the Media Access Control (MAC) layer and the Logical Link Control (LLC) layer. In the networking world, most switches operate at Layer 2.
Layer 1 – Physical
At the bottom of our OSI bean dip we have the Physical Layer, which represents the electrical and physical representation of the system. This can include everything from the cable type, radio frequency link (as in an 802.11 wireless systems), as well as the layout of pins, voltages and other physical requirements. When a networking problem occurs, many networking pros go right to the physical layer to check that all of the cables are properly connected and that the power plug hasn’t been pulled from the router, switch or computer, for example.
Why you need to know the 7 OSI layers
Most people in the IT space will likely need to know about the different layers when they’re going for their certifications, much like a civics student needs to learn about the three branches of the U.S. government. After that, you hear about the OSI model when vendors are making pitches about which layer(s) their products work with.
In a Quora post asking about the purpose of the OSI model, Vikram Kumar answered this way:
“The purpose of the OSI reference model is to guide vendors and developers so the digital communication products and software programs they create will interoperate, and to facilitate clear comparisons among communications tools.”
While some people may argue that the OSI model is obsolete (due to its theoretical nature and less important than the 4 layers of the TCP/IP model), Kumar says that “it is difficult to read about networking technology today without seeing references to the OSI model and its layers, because the model’s structure helps to frame discussions of protocols and contrast various technologies.”
If you can understand the OSI model and its layers, you can also then understand which protocols and devices can interoperate with each other when new technologies are developed and explained.
Remembering the OSI Model 7 layers – 8 mnemonic tricks
If you need to memorize the layers for a college or certification test, here are a few sentences to help remember them in order. The first letter of each word is the same as a layer of the OSI model.
From Application to Physical (top down):
All People Seem To Need Data Processing
All Pros Search Top Notch Donut Places
A Penguin Said That Nobody Drinks Pepsi
A Priest Saw Two Nuns Doing Pushups
From Physical to Application (bottom up):
Please Do Not Throw Sausage Pizza Away
Pew! Dead Ninja Turtles Smell Particularly Awful
People Don’t Need To See Paula Abdul
Pete Doesn’t Need To Sell Pickles Anymore
Keith Shaw was a Network World editor and the writer of the Cool Tools column. He is now a freelance writer and editor from Worcester, Mass.