Difference between revisions of "Open Systems Interconnection model"
(A start. More to come.) |
DavidB4-bot (talk | contribs) m (→Application Layer (7): HTTP --> HTTPS [#1], replaced: http://www.academia.edu → https://www.academia.edu) |
||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | The '''Open System Interconnection (OSI) Model''' (or the OSI Reference Model) is a basic representation of how information moves from a software application through a network medium to an application on another computer <ref>http://www.cisco.com/en/US/docs/internetworking/technology/handbook/Intro-to-Internet.html#wp1020627</ref> | + | The '''Open System Interconnection (OSI) Model''' (or the OSI Reference Model) is a basic representation of how information moves from a [[software]] application through a [[network]] medium to an application on another [[computer]].<ref>http://www.cisco.com/en/US/docs/internetworking/technology/handbook/Intro-to-Internet.html#wp1020627</ref> |
Not encompassing newer protocol developments, the model is still considered to be a very useful introduction to network architecture. | Not encompassing newer protocol developments, the model is still considered to be a very useful introduction to network architecture. | ||
| + | ==Layers== | ||
There are seven layers in the model with information flowing from the highest layer (seven) to the lowest (one). The layers are: | There are seven layers in the model with information flowing from the highest layer (seven) to the lowest (one). The layers are: | ||
| − | |||
*Layer 7 - Application | *Layer 7 - Application | ||
| Line 13: | Line 13: | ||
*Layer 2 - Data Link | *Layer 2 - Data Link | ||
*Layer 1 - Physical | *Layer 1 - Physical | ||
| + | |||
| + | ===Application Layer (7)=== | ||
| + | The topmost layer is where most real traffic data is generated. All user program traffic such as that from e-mail and web browser software is on this layer. This is the layer which is easily seen by every user.<ref name="docs.oracle.com">http://docs.oracle.com/cd/E19253-01/816-4554/ipov-7/index.html</ref><ref name="support.microsoft.com">https://support.microsoft.com/en-us/kb/103884</ref><ref name="academia.edu">https://www.academia.edu/9562787/Open_System_Interconnection_OSI_A_Seven_Layered_Model</ref> | ||
| + | |||
| + | ===Presentation Layer (6)=== | ||
| + | This layer prepares data to be "presented" to the network. This involves and data compression or encryption immediately after it is sent out, or just before it is received by the Application Layer. This layer can also check and correct the character code set (ASCII, Unicode, EBCDIC, etc.)<ref name="docs.oracle.com"/><ref name="support.microsoft.com"/><ref name="academia.edu"/> | ||
| + | |||
| + | ===Session Layer (5)=== | ||
| + | This layer is responsible for managing each connection session. It is directly in control of establishing, managing, and terminating connections requested by applications at both ends of the communication link. Communication methods and terms are also agreed upon at both ends by this layer.<ref name="docs.oracle.com"/><ref name="support.microsoft.com"/><ref name="academia.edu"/> | ||
| + | |||
| + | ===Transport Layer (4)=== | ||
| + | The Transport Layer is responsible for coordination and managing the actual transportation and receipt of data. In this layer, data is broken down into packets which are sent one at a time. In most cases (when TCP is used), the transport layer on the recipient's end will acknowledge receiving each packet, so that if any are lost in transit, they can be resent. In some cases (when UDP is used), these acknowledgments are not sent, and lost packets are not resent. This is a less reliable method, but still useful when quality is not as important as quantity. This layer is also responsible for segment sequencing. This means simply that a series of packets is reassembled in order by this layer on the receiving end.<ref name="docs.oracle.com"/><ref name="support.microsoft.com"/><ref name="academia.edu"/><br /> | ||
| + | The Transport Layer is also in charge of service address (port numbers) which are used to deliver data to one service or program directly, so that a lower layer does not need to determine where each piece of information belongs.<ref name="docs.oracle.com"/><ref name="support.microsoft.com"/><ref name="academia.edu"/> | ||
| + | |||
| + | ===Network Layer (3)=== | ||
| + | This layer is responsible for the logical addressing required to get packets to their intended destinations. Using routing tables, special computers (called routers) will direct packets from one jump to the next until they reach their recipient. All of this is accomplished using [[IP address]]es, which are unique identifiers for each device on the internet. Each router will select from its routing table the best address to send each packet to. The recipient will then pass on the packet based on its own routing table. This enables packets to be sent to specific destinations unknown to the sender because they are simply sent to the device which does know where it should go next.<ref name="docs.oracle.com"/><ref name="support.microsoft.com"/><ref name="academia.edu"/> | ||
| + | |||
| + | ===Datalink Layer (2)=== | ||
| + | The Datalink layer is in charge of ensuring end-to-end validity of the data being exchanged. This layer is logically split into two sublayers, The Media Access Control (MAC) Sublayer and the Logical Link Control (LLC) Sublayer.<ref name="docs.oracle.com"/><ref name="support.microsoft.com"/><ref name="academia.edu"/> | ||
| + | *The Media Access Control (MAC) Sublayer determines the actual physical address of the hosts. To do this, it uses MAC addresses for its communication with other devices on the network. Unlike the IP addresses which the Network Layer uses, MAC addresses (also known as Physical addresses, Layer 2 addresses, or Hardware addresses) are assigned to each device at the time of manufacture, and are not usually changed (although this is sometimes possible, it will never be done automatically). These are therefore reliable identifiers within a local network.<ref name="docs.oracle.com"/><ref name="support.microsoft.com"/><ref name="academia.edu"/> | ||
| + | *The Logical Link Control sublayer is responsible for synchronizing data frames, flow control, and checking for errors.<ref name="docs.oracle.com"/><ref name="support.microsoft.com"/><ref name="academia.edu"/> | ||
| + | |||
| + | ===Physical Layer (1)=== | ||
| + | This lowest level of the OSI model involves the physical hardware which transfers the raw data after encoding it into [[binary]] form. These pulses are carried by wire (Twisted Pair, Coaxial Cable, etc.) or fiber optic cable from one physical end to the other, as the Datalink Layer coordinates the transfer.<ref name="docs.oracle.com"/><ref name="support.microsoft.com"/><ref name="academia.edu"/> [[Network hub]]s and wireless access points are also included in this layer. | ||
== References == | == References == | ||
<references/> | <references/> | ||
| + | [[Category:Networking]] | ||
Latest revision as of 18:55, September 26, 2018
The Open System Interconnection (OSI) Model (or the OSI Reference Model) is a basic representation of how information moves from a software application through a network medium to an application on another computer.[1]
Not encompassing newer protocol developments, the model is still considered to be a very useful introduction to network architecture.
Layers
There are seven layers in the model with information flowing from the highest layer (seven) to the lowest (one). The layers are:
- Layer 7 - Application
- Layer 6 - Presentation
- Layer 5 - Session
- Layer 4 - Transport
- Layer 3 - Network
- Layer 2 - Data Link
- Layer 1 - Physical
Application Layer (7)
The topmost layer is where most real traffic data is generated. All user program traffic such as that from e-mail and web browser software is on this layer. This is the layer which is easily seen by every user.[2][3][4]
Presentation Layer (6)
This layer prepares data to be "presented" to the network. This involves and data compression or encryption immediately after it is sent out, or just before it is received by the Application Layer. This layer can also check and correct the character code set (ASCII, Unicode, EBCDIC, etc.)[2][3][4]
Session Layer (5)
This layer is responsible for managing each connection session. It is directly in control of establishing, managing, and terminating connections requested by applications at both ends of the communication link. Communication methods and terms are also agreed upon at both ends by this layer.[2][3][4]
Transport Layer (4)
The Transport Layer is responsible for coordination and managing the actual transportation and receipt of data. In this layer, data is broken down into packets which are sent one at a time. In most cases (when TCP is used), the transport layer on the recipient's end will acknowledge receiving each packet, so that if any are lost in transit, they can be resent. In some cases (when UDP is used), these acknowledgments are not sent, and lost packets are not resent. This is a less reliable method, but still useful when quality is not as important as quantity. This layer is also responsible for segment sequencing. This means simply that a series of packets is reassembled in order by this layer on the receiving end.[2][3][4]
The Transport Layer is also in charge of service address (port numbers) which are used to deliver data to one service or program directly, so that a lower layer does not need to determine where each piece of information belongs.[2][3][4]
Network Layer (3)
This layer is responsible for the logical addressing required to get packets to their intended destinations. Using routing tables, special computers (called routers) will direct packets from one jump to the next until they reach their recipient. All of this is accomplished using IP addresses, which are unique identifiers for each device on the internet. Each router will select from its routing table the best address to send each packet to. The recipient will then pass on the packet based on its own routing table. This enables packets to be sent to specific destinations unknown to the sender because they are simply sent to the device which does know where it should go next.[2][3][4]
Datalink Layer (2)
The Datalink layer is in charge of ensuring end-to-end validity of the data being exchanged. This layer is logically split into two sublayers, The Media Access Control (MAC) Sublayer and the Logical Link Control (LLC) Sublayer.[2][3][4]
- The Media Access Control (MAC) Sublayer determines the actual physical address of the hosts. To do this, it uses MAC addresses for its communication with other devices on the network. Unlike the IP addresses which the Network Layer uses, MAC addresses (also known as Physical addresses, Layer 2 addresses, or Hardware addresses) are assigned to each device at the time of manufacture, and are not usually changed (although this is sometimes possible, it will never be done automatically). These are therefore reliable identifiers within a local network.[2][3][4]
- The Logical Link Control sublayer is responsible for synchronizing data frames, flow control, and checking for errors.[2][3][4]
Physical Layer (1)
This lowest level of the OSI model involves the physical hardware which transfers the raw data after encoding it into binary form. These pulses are carried by wire (Twisted Pair, Coaxial Cable, etc.) or fiber optic cable from one physical end to the other, as the Datalink Layer coordinates the transfer.[2][3][4] Network hubs and wireless access points are also included in this layer.
References
- ↑ http://www.cisco.com/en/US/docs/internetworking/technology/handbook/Intro-to-Internet.html#wp1020627
- ↑ 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 http://docs.oracle.com/cd/E19253-01/816-4554/ipov-7/index.html
- ↑ 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 https://support.microsoft.com/en-us/kb/103884
- ↑ 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 https://www.academia.edu/9562787/Open_System_Interconnection_OSI_A_Seven_Layered_Model