A – Application (application request)
P – Presentation (how the data is presented to the application)
S – Session (how the request is transmitted creates session for transport)
T – Transport (Transport Characteristics – what IP port is used, where it is going, etc.)
N – Network (adds information such as IP addresses)
D – Data Link (adds information such as MAC address)
P – Physical (formats the transmission into what the network hardware supports)
This is a simplified version, but when the application requests a file from a server, it sends that request to the next layer down. Each layer going down to the physical layer adds information such as what IP port it will use, what type of session and transport it will use (connection oriented or connectionless), IP address of requesting station and server, all the way down to the zeros and ones that move across the cabling. When the packet comes back, each layer strips off what it added to the packet and moves it back up the stack until the application gets the data it needs at the end.
Dig Deeper on Network Infrastructure
Related Q&A from Carrie Higbie Goetz
Migrating UC to the cloud doesn't mean leaving your SIP trunk carrier behind. Learn how bringing your own SIP to cloud services can benefit your ... Continue Reading
An unguarded VoIP system could be vulnerable to attack. Learn what security measures can help prevent VoIP security threats from affecting your ... Continue Reading
Traditional and cloud SIP trunking perform the same tasks of initiating and ending call sessions, but the method and costs of access create distinct ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.