OSI model

From Wikipedia, the free encyclopedia

OSI model

7. Application Layer

NNTP  · SIP  · SSI  · DNS  · FTP  · Gopher · HTTP  · NFS  · NTP  · SMPP  · SMTP  ·DHCP  · SNMP  · Telnet  · Netconf  ·(m

ore)

6. Presentation Layer

MIME  · XDR  · TLS  · SSL

5. Session Layer

Named Pipes  · NetBIOS  · SAP  · L2TP  ·PPTP

4. Transport Layer

TCP  · UDP  · SCTP  · DCCP

3. Network Layer

IP (IPv4, IPv6)  · ICMP  · IPsec  · IGMP  ·IPX  · AppleTalk

2. Data Link Layer

ATM  · SDLC  · HDLC  · ARP  · CSLIP  ·SLIP  · PLIP  · IEEE 802.3  · Frame Relay · ITU-T G.hn DLL  · PPP  · X.25

1. Physical Layer

EIA/TIA-232  · EIA/TIA-449  · ITU-T V-Series  · I.430  · I.431  · POTS  · PDH  ·SONET/SDH  · PON  · OTN  · DSL  ·IEEE 8

02.3  · IEEE 802.11  · IEEE 802.15 · IEEE 802.16  · IEEE 1394  · ITU-T G.hn PHY  · USB  · Bluetooth

This box: view • talk • edit
The Open Systems Interconnection model (OSI model) is a product of the Open Systems
Interconnection effort at the International Organization for Standardization. It is a way of sub-dividing
a communications system into smaller parts called layers. A layer is a collection of conceptually similar
functions that provide services to the layer above it and receives services from the layer below it. On each layer
aninstance provides services to the instances at the layer above and requests service from the layer below.

For example, a layer that provides error-free communications across a network provides the path needed by
applications above it, while it calls the next lower layer to send and receive packets that make up the contents
of the path. Conceptually two instances at one layer are connected by a horizontal protocol connection on that
layer.

Most network protocols used in the market today are based on TCP/IP stacks.

Communication in the OSI-Model (Example with layers 3 to 5)

Contents
 [hide]

1 History

2 Description of OSI layers

o 2.1 Layer 1: Physical Layer

o 2.2 Layer 2: Data Link Layer

 2.2.1 WAN Protocol

architecture

 2.2.2 IEEE 802 LAN

 architecture

o 2.3 Layer 3: Network Layer

o 2.4 Layer 4: Transport Layer

o 2.5 Layer 5: Session Layer

o 2.6 Layer 6: Presentation Layer

o 2.7 Layer 7: Application Layer

3 Cross Layer Functions

4 Interfaces

5 Examples

6 Comparison with TCP/IP

7 See also

8 References

9 External links

[edit]History

In 1978, work on a layered model of network architecture was started and the International Organization for
Standardization (ISO) began to develop its OSI framework architecture. OSI has two major components: an
abstract model of networking, called the Basic Reference Model or seven-layer model, and a set of specific
protocols.

Note: The standard documents that describe the OSI model can be freely downloaded from the ITU-T as
theX.200-series of recommendations.[1] A number of the protocol specifications are also available as part of the
ITU-T X series. The equivalent ISO and ISO/IEC standards for the OSI model are available from ISO, but only
some of them at no charge.[2]

The concept of a 7 layer model was provided by the work of Charles Bachman, Honeywell Information
Services. Various aspects of OSI design evolved from experiences with the ARPANET, the fledgling Internet,
NPLNET, EIN, CYCLADES network and the work in IFIP WG6.1. The new design was documented in ISO
7498 and its various addenda. In this model, a networking system is divided into layers. Within each layer, one
or more entities implement its functionality. Each entity interacts directly only with the layer immediately
beneath it, and provides facilities for use by the layer above it.

Protocols enable an entity in one host to interact with a corresponding entity at the same layer in another host.
Service definitions abstractly describe the functionality provided to an (N)-layer by an (N-1) layer, where N is
one of the seven layers of protocols operating in the local host.

[edit]Description of OSI layers

According to recommendation X.200, there are seven layers, each generically known as an N layer. An N+1
entity requests services from the N entity.

At each level, two entities (N-entity peers) interact by means of the N protocol by transmitting protocol data
units (PDU).

A Service Data Unit (SDU) is a specific unit of data that has been passed down from an OSI layer to a lower
layer, and which the lower layer has not yet encapsulated into a protocol data unit (PDU). An SDU is a set of
data that is sent by a user of the services of a given layer, and is transmitted semantically unchanged to a peer
service user.

The PDU at any given layer, layer 'n', is the SDU of the layer below, layer 'n-1'. In effect the SDU is the
'payload' of a given PDU. That is, the process of changing a SDU to a PDU, consists of an encapsulation
process, performed by the lower layer. All the data contained in the SDU becomes encapsulated within
the PDU. The layer n-1 adds headers or footers, or both, to the SDU, transforming it into a PDU of layer
n-1. The added headers or footers are part of the process used to make it possible to get data from a
source to a destination.
OSI Model

Data unit Layer Function

7. Application Network process to application

Data representation, encryption and decryption, convert machine dependent data to machine independent
Data 6. Presentation data
Host
layers
5. Session Interhost communication

Segments 4. Transport End-to-end connections and reliability,flow control

Media Packet 3. Network Path determination andlogical addressing

layers
Frame 2. Data Link Physical addressing
 Bit 1. Physical Media, signal and binary transmission

Some orthogonal aspects, such as management and security, involve every layer.

Security services are not related to a specific layer: they can be related by a number of layers, as defined
by ITU-T X.800 Recommendation.[3]

These services are aimed to improve the CIA triad(i.e.confidentiality, integrity, availability) of transmitted data.

Actually the availability of communication service is determined by network design and/or network
management protocols. Appropriate choices for these are needed to protect against denial of service.

[edit]Layer 1: Physical Layer

The Physical Layer defines the electrical and physical specifications for devices. In particular, it defines the
relationship between a device and a transmission medium, such as a copper or optical cable. This includes the
layout of pins, voltages, cablespecifications, hubs, repeaters, network adapters, host bus adapters (HBA used
in storage area networks) and more.

To understand the function of the Physical Layer, contrast it with the functions of the Data Link Layer. Think of
the Physical Layer as concerned primarily with the interaction of a single device with a medium, whereas the
Data Link Layer is concerned more with the interactions of multiple devices (i.e., at least two) with a shared
medium. Standards such as RS-232 do use physical wires to control access to the medium.

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 (such as copper and optical fiber) or over a radio link.

Parallel SCSI buses operate in this layer, although it must be remembered that the logical SCSI protocol is a
Transport Layer protocol that runs over this bus. 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, ITU-TG.hn and IEEE 802.11, as well as personal area networks such
as Bluetooth and IEEE 802.15.4.

[edit]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. Originally, this layer was
intended for point-to-point and point-to-multipoint media, characteristic of wide area media in the telephone
system. Local area network architecture, which included broadcast-capable multiaccess media, was developed
independently of the ISO work in IEEE Project 802. IEEE work assumed sublayering and management
functions not required for WAN use. In modern practice, only error detection, not flow control using sliding
window, is present in data link protocols such as Point-to-Point Protocol (PPP), and, on local area networks,
the IEEE 802.2 LLC layer is not used for most protocols on the Ethernet, and on other local area networks, its
flow control and acknowledgment mechanisms are rarely used. Sliding window flow control and
acknowledgment is used at the Transport Layer by protocols such as TCP, but is still used in niches
where X.25 offers performance advantages.

The ITU-T G.hn standard, which provides high-speed local area networking over existing wires (power lines,
phone lines and coaxial cables), includes a complete Data Link Layer which provides both error correction and
flow control by means of a selective repeat Sliding Window Protocol.

Both WAN and LAN service arrange bits, from the Physical Layer, into logical sequences called frames. Not all
Physical Layer bits necessarily go into frames, as some of these bits are purely intended for Physical Layer
functions. For example, every fifth bit of the FDDI bit stream is not used by the Layer.

[edit]WAN Protocol architecture

Connection-oriented WAN data link protocols, in addition to framing, detect and may correct errors. They are
also capable of controlling the rate of transmission. A WAN Data Link Layer might implement a sliding
window flow control and acknowledgment mechanism to provide reliable delivery of frames; that is the case
for SDLC and HDLC, and derivatives of HDLC such as LAPB and LAPD.

[edit]IEEE 802 LAN architecture

Practical, connectionless LANs began with the pre-IEEE Ethernet specification, which is the ancestor of IEEE

802.3. This layer manages the interaction of devices with a shared medium, which is the function of a Media
Access Control sublayer. Above this MAC sublayer is the media-independent IEEE 802.2 Logical Link
Control (LLC) sublayer, which deals with addressing and multiplexing on multiaccess media.

While IEEE 802.3 is the dominant wired LAN protocol and IEEE 802.11 the wireless LAN protocol, obsolescent
MAC layers include Token Ring and FDDI. The MAC sublayer detects but does not correct errors.

[edit]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 functions, and might
also perform fragmentation and reassembly, and report delivery errors. Routers operate at this layer—sending
data throughout the extended network and making the Internet possible. This is a logical addressing scheme –
values are chosen by the network engineer. The addressing scheme is not hierarchical.

Careful analysis of the Network Layer indicated that the Network Layer could have at least three sublayers:

1. Subnetwork Access - that considers protocols that deal with the interface to networks, such as X.25;

2. Subnetwork Dependent Convergence - when it is necessary to bring the level of a transit network up to
the level of networks on either side;

3. Subnetwork Independent Convergence - which handles transfer across multiple networks.

The best example of this latter case is CLNP, or IPv7 ISO 8473. It manages the connectionless transfer of data
one hop at a time, from end system to ingress router, router to router, and from egress router to destination end
system. It is not responsible for reliable delivery to a next hop, but only for the detection of erroneous packets
so they may be discarded. In this scheme, IPv4 and IPv6 would have to be classed with X.25 as subnet access
protocols because they carry interface addresses rather than node addresses.

A number of layer management protocols, a function defined in the Management Annex, ISO 7498/4, belong to
the Network Layer. These include routing protocols, multicast group management, Network Layer information
and error, and Network Layer address assignment. It is the function of the payload that makes these belong to
the Network Layer, not the protocol that carries them.

[edit]Layer 4: Transport Layer

The Transport Layer provides transparent transfer of data between end users, providing reliable data transfer
services to the upper layers. The Transport Layer controls the reliability of a given link through flow control,
segmentation/desegmentation, and error control. Some protocols are state and connection oriented. This
means that the Transport Layer can keep track of the segments and retransmit those that fail. The Transport
layer also provides the acknowledgement of the successful data transmission and sends the next data if no
errors occurred.

Although not developed under the OSI Reference Model and not strictly conforming to the OSI definition of the
Transport Layer, typical examples of Layer 4 are the Transmission Control Protocol (TCP) and User Datagram
Protocol (UDP).

Of the actual OSI protocols, there are five classes of connection-mode transport protocols ranging from class 0
(which is also known as TP0 and provides the least features) to class 4 (TP4, designed for less reliable
networks, similar to the Internet). Class 0 contains no error recovery, and was designed for use on network
layers that provide error-free connections. Class 4 is closest to TCP, although TCP contains functions, such as
the graceful close, which OSI assigns to the Session Layer. Also, all OSI TP connection-mode protocol classes
provide expedited data and preservation of record boundaries, both of which TCP is incapable. Detailed
characteristics of TP0-4 classes are shown in the following table: [4]

Feature Name TP0 TP1 TP2 TP3 TP4

Connection oriented network Yes Yes Yes Yes Yes

Connectionless network No No No No Yes

Concatenation and separation No Yes Yes Yes Yes

Segmentation and reassembly Yes Yes Yes Yes Yes

Error Recovery No Yes Yes Yes Yes

Reinitiate connection (if an excessive number of PDUs are

No Yes No Yes No
unacknowledged)

Multiplexing and demultiplexing over a single virtual circuit No No Yes Yes Yes

Explicit flow control No No Yes Yes Yes

Retransmission on timeout No No No No Yes

Reliable Transport Service No Yes No Yes Yes

Perhaps an easy way to visualize the Transport Layer is to compare it with a Post Office, which deals with the
dispatch and classification of mail and parcels sent. Do remember, however, that a post office manages the
outer envelope of mail. Higher layers may have the equivalent of double envelopes, such as cryptographic
presentation services that can be read by the addressee only. Roughly speaking, tunneling protocols operate at
the Transport Layer, such as carrying non-IP protocols such as IBM's SNA or Novell's IPX over an IP network,
or end-to-end encryption with IPsec. While Generic Routing Encapsulation (GRE) might seem to be a Network
Layer protocol, if the encapsulation of the payload takes place only at endpoint, GRE becomes closer to a
transport protocol that uses IP headers but contains complete frames or packets to deliver to an
endpoint. L2TP carries PPP frames inside transport packet.

[edit]Layer 5: Session Layer

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, 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.

[edit]Layer 6: Presentation Layer

The Presentation Layer establishes context between Application Layer entities, in which the higher-layer
entities may use different syntax and semantics if the presentation service provides a mapping between them.
If a mapping is available, presentation service data units are encapsulated into session protocol data units, and
passed down the stack.

This layer provides independence from data representation (e.g., encryption) by translating between application
and network formats. The presentation layer transforms data into the form that the application accepts. This
layer formats and encrypts data to be sent across a network. It is sometimes called the syntax layer. [citation needed]

The original presentation structure used the basic encoding rules of Abstract Syntax Notation One (ASN.1),
with capabilities such as converting an EBCDIC-coded text file to an ASCII-coded file,
or serialization of objects and other data structures from and to XML.

[edit]Layer 7: Application Layer

The Application Layer is the OSI layer closest to the end user, which means that both the OSI application layer
and the user interact directly with the software application. This layer interacts with software applications that
implement a communicating component. Such application programs fall outside the scope of the OSI model.
Application layer functions typically include identifying communication partners, determining resource
availability, and synchronizing communication. When identifying communication partners, the application layer
determines the identity and availability of communication partners for an application with data to transmit. When
determining resource availability, the application layer must decide whether sufficient network or the requested
communication exist. In synchronizing communication, all communication between applications requires
cooperation that is managed by the application layer. Some examples of application layer implementations
include:
 On OSI stack:

 FTAM File Transfer and Access Management Protocol

 X.400 Mail

 Common management information protocol (CMIP)

 On TCP/IP stack:

 Hypertext Transfer Protocol (HTTP),

 File Transfer Protocol (FTP),

 Simple Mail Transfer Protocol (SMTP)

 Simple Network Management Protocol (SNMP)

[edit]Cross Layer Functions

There are some functions or services that are not tied to a given layer, but they can affect more than one layer.
Examples are

 security service (telecommunication)[5] as defined by ITU-T X.800 Recommendation.

 management functions, i.e functions that permit to configure, instantiate, monitor, terminate the
communications of two or more entities: there is a specific application layer protocolCommon management
information protocol (CMIP) and its corresponding service common management information
service (CMIS), they need to interact with every layer in order to deal with their instances.

[edit]Interfaces

Neither the OSI Reference Model nor OSI protocols specify any programming interfaces, other than as
deliberately abstract service specifications. Protocol specifications precisely define the interfaces between
different computers, but the software interfaces inside computers are implementation-specific.

For example Microsoft Windows' Winsock, and Unix's Berkeley sockets and System V Transport Layer

Interface, are interfaces between applications (Layer 5 and above) and the transport (Layer
4). NDIS and ODI are interfaces between the media (Layer 2) and the network protocol (Layer 3).

Interface standards, except for the Physical Layer to media, are approximate implementations of OSI Service
Specifications.

[edit]Examples
 This section does not cite any references or sources.
Please help improve this article by adding citations to reliable sources. Unsourced material may
be challenged and removed. (June 2010)

Laye
r
Signalin S
AppleTa
OSI protocols TCP/IP protocols g System IPX N UMTS Misc. examples
[6] lk
7 A
Na
#
me

FTAM, X.400,X. NNTP, SIP, SSI, DNS,FTP, Go INAP,M

App AFP, ZIP A
500, DAP, ROSE, pher, HTTP,NFS, NTP, DHCP, AP,TCA RIP,S
7licat ,RTMP, PP HL7, Modbus
RTSE, ACSE[7]C SMPP, SMTP, SNMP,Telnet,  P,ISUP,T AP
ion [8] NBP C
MIP RIP, BGP UP

ISO/IEC 8823,
Pres TDI, ASCII, EBC
X.226,
6enta MIME, SSL, TLS, XDR AFP DIC, MIDI, MPE
ISO/IEC 9576-1,
tion G
X.236

Named
ISO/IEC 8327, pipes, NetBIOS, 
D
Sess X.225, Sockets. Session establishment ASP,AD NWLi SAP, half
5 L
ion ISO/IEC 9548-1, in TCP,RTP SP,PAP nk duplex, full
C?
X.235 duplex, simplex, 
RPC

ISO/IEC 8073,
TP0, TP1, TP2,
Tra
TP3, TP4 DDP,S
4nsp TCP, UDP, SCTP, DCCP NBF
(X.224), PX
ort
ISO/IEC 8602,
X.234

3Net ISO/IEC 8208, X. IP, IPsec, ICMP, IGMP,OSPF SCCP,M ATP(Tok IPX RRC (Ra NBF, Q.931, IS-

wor 25(PLP), TP enTalkor dio IS
k ISO/IEC 8878,X. EtherTal Resource
223, k) Control) 
ISO/IEC 8473- Packet
1,CLNP X.233. Data Leaky
Converge
nce bucket, token
Protocol( bucket
PDCP)
and BMC
(Broadca
 st/Multic
ast
Control)

802.3
(Ethernet), 802.1
1a/b/g/n
MAC/LLC, 802.1
Q
(VLAN), ATM, 
HDP, FDDI, Fibr
LLC (Lo e Channel, Frame
IEEE
ISO/IEC 7666, X. LocalTal gical Relay, HDLC, IS
802.3fr
Dat 25(LAPB), Token k,AppleT S Link L, PPP, Q.921, T
aming,
a Bus, X.222, MTP,Q.7 alk D Control),  oken
2 PPP, SLIP, PPTP, L2TP Ethern
Lin ISO/IEC 8802-2  10 Remote L MAC (M Ring, CDP,ARP (
et II
k LLCType 1 and Access,P C edia maps layer 3 to
framin
2[9] PP Access layer 2
g
Control) address), ITU-T
G.hn DLL
CRC, Bit
stuffing, ARQ, D
ata Over Cable
Service Interface
Specification
(DOCSIS)
RS-232, Full
duplex, RJ45, V.
35, V.34, I.430, I.
431,T1, E1, 10B
ASE-T, 100BAS
E-TX, POTS, SO
X.25 (X.21bis,EI RS- NET,SDH, DSL, 
T UMTS
Phy A/TIA- 232,RS- 802.11a/b/g/n
MTP,Q.7 wi Physical
1sica 232,EIA/TIA-449,  422,STP, PHY, ITU-T
10 na Layer or
l EIA-530, G.703) [ PhoneNe G.hn
9] x L1
t PHY,Controller
Area
Network, Data
Over Cable
Service Interface
Specification
(DOCSIS)

[edit]Comparison with TCP/IP

In the TCP/IP model of the Internet, protocols are deliberately not as rigidly designed into strict layers as the
OSI model.[10] RFC 3439 contains a section entitled "Layering considered harmful." However, TCP/IP does
recognize four broad layers of functionality which are derived from the operating scope of their contained
protocols, namely the scope of the software application, the end-to-end transport connection, the
internetworking range, and lastly the scope of the direct links to other nodes on the local network.
Even though the concept is different from the OSI model, these layers are nevertheless often compared with
the OSI layering scheme in the following way: The Internet Application Layerincludes the OSI Application
Layer, Presentation Layer, and most of the Session Layer. Its end-to-end Transport Layer includes the graceful
close function of the OSI Session Layer as well as the OSI Transport Layer. The internetworking layer (Internet
Layer) is a subset of the OSI Network Layer (see above), while the Link Layer includes the OSI Data Link and
Physical Layers, as well as parts of OSI's Network Layer. These comparisons are based on the original seven-
layer protocol model as defined in ISO 7498, rather than refinements in such things as the internal organization
of the Network Layer document.

The presumably strict peer layering of the OSI model as it is usually described does not present contradictions
in TCP/IP, as it is permissible that protocol usage does not follow the hierarchy implied in a layered model.
Such examples exist in some routing protocols (e.g., OSPF), or in the description of tunneling protocols, which
provide a Link Layer for an application, although the tunnel host protocol may well be a Transport or even an
Application Layer protocol in its own right.
 The 7 Layers of the OSI Model
The OSI, or Open System Interconnection, model defines a networking framework for implementing protocols in
seven layers. Control is passed from one layer to the next, starting at the application layer in one station,
proceeding to the bottom layer, over the channel to the next station and back up the hierarchy.
By:
Posted: 09-24-2010 , Last Updated: 10-08-2010
More Terms
 Huffman compression »
 ESCON »
 server(Sponsored) »
 SPX »
 Cisco Discovery Protocol »
 LANE »
 RS-485 »
 zone file »
 data transfer rate »
 ISDN »

Stay up to date on the latest developments in internet terminology with a free weekly newsletter from Webopedia. Join to subscribe now.
Sign up
Already a member? Log in now.
Webopedia is a part of the Internet.com network.

 
The OSI, or Open System Interconnection, model defines a networking framework for implementing protocols in
seven layers. Control is passed from one layer to the next, starting at the application layer in one station, and
proceeding to the bottom layer, over the channel to the next station and back up the hierarchy.

Application (Layer 7)
Sponsored
PDF: Quick Evaluation Guide for Serial and Parallel Apps:  Verify applications and find latent memory errors that
cause crashes and lockups.
This layer supports application and end-user processes. Communication partners are identified, quality of service is
identified, user authentication and privacy are considered, and any constraints on data syntax are identified.
Everything at this layer is application-specific. This layer provides application services for file transfers, e-mail, and
other network software services. Telnet and FTP are applications that exist entirely in the application level. Tiered
application architectures are part of this layer.

Presentation (Layer 6)
This layer provides independence from differences in data representation (e.g.,encryption) by translating from
application to network format, and vice versa. The presentation layer works to transform data into the form that the
application layer can accept. This layer formats and encrypts data to be sent across a network, providing freedom
from compatibility problems. It is sometimes called the syntax layer.

Session (Layer 5)
This layer establishes, manages and terminates connections betweenapplications. The session layer sets up,
coordinates, and terminates conversations, exchanges, and dialogues between the applications at each end. It deals
with session and connection coordination.

Transport (Layer 4)
This layer provides transparent transfer of data between end systems, or hosts, and is responsible for end-to-end
error recovery and flow control. It ensures complete data transfer.

Network (Layer 3)
This layer provides switching and routing technologies, creating logical paths, known as virtual circuits, for
transmitting data from node to node. Routing and forwarding are functions of this layer, as well
as addressing, internetworking, error handling, congestion control and packet sequencing.

Data Link (Layer 2)

At this layer, data packets are encoded and decoded into bits. It furnishestransmission protocol knowledge and
management and handles errors in the physical layer, flow control and frame synchronization. The data link layer is
divided into two sub layers: The Media Access Control (MAC) layer and the Logical Link Control (LLC) layer. The
MAC sub layer controls how a computer on the network gains access to the data and permission to transmit it. The
LLC layer controls frame synchronization, flow control and error checking.

Physical (Layer 1)
This layer conveys the bit stream - electrical impulse, light or radio signal -- through the network at the electrical and
mechanical level. It provides the hardwaremeans of sending and receiving data on a carrier, including defining
cables, cards and physical aspects. Fast Ethernet, RS232, and ATM are protocols with physical layer components.
The OSI Reference Model is founded on a suggestion developed by the International Organization for
Standardization (ISO). The model is known as ISO OSI (Open Systems Interconnection) Reference
Model because it relates with connecting open systems – that is, systems that are open for
communication with other systems.

OSI Model is a set of protocols that try to identify and homogenize the data communication practices. The
OSI Model has the support of most computer and network vendors, many big customers, and most
governments, including the United States.

The OSI Model is a model that illustrates how data communications should take place. It segregates the
process into seven groups, called layers. Into these layers are integrated the protocol standards
developed by the ISO and other standards organization, including the Institute of Electrical and Electronic
Engineers (IEEE), American National Standards Institute (ANSI), and the International
Telecommunications Union (ITU), formerly known as the CCITT (Comite Consultatif Internationale de
Telegraphique et Telephone). The OSI Model affirms what protocols and standards should be used at
each layer. It is modular, each layer of the OSI Model functions with the one above and below it.

The short form used to memorize the layer

names of the OSI Model is
“AllPeople Seem To Need DataProcessing”
. The lower two layers are normally put into
practice with hardware and software. The
remaining five layers are only implemented
with software.

The layered approach to network

communications gives the subsequent
advantages: Reduced intricacy, enhanced
teaching/learning, modular engineering,
accelerated advancement, interoperable
technology, and standard interfaces.

The Seven Layers of the OSI

Model
The seven layers of the OSI model are:

Layer Name
7 Application
6 Presentation
5 Session
4 Transport
3 Network
2 Data Link
1 Physical
The easiest way to remember the layers of the OSI model is to use the handy mnemonic "All People
Seem To Need Data Processing":

Layer Name Mnemonic

7 Application All
6 Presentation People
5 Session Seem
4 Transport To
3 Network Need
2 Data Link Data
1 Physical Processing
The functions of the seven layers of the OSI model are:

Layer Seven of the OSI Model

The Application Layer of the OSI model is responsible for providing end-user services, such as file
transfers, electronic messaging, e-mail, virtual terminal access, and network management. This is the
layer with which the user interacts.

Layer Six of the OSI Model

The Presentation Layer of the OSI model is responsible for defining the syntax which two network hosts
use to communicate. Encryption and compression should be Presentation Layer functions.

Layer Five of the OSI Model

The Session Layer of the OSI model is responsible for establishing process-to-process commnunications
between networked hosts.

Layer Four of the OSI Model

The Transport Layer of the OSI model is responsible for delivering messages between networked hosts.
The Transport Layer should be responsible for fragmentation and reassembly.

Layer Three of the OSI Model

The Network Layer of the OSI model is responsible for establishing paths for data transfer through the
network. Routers operate at the Network Layer.

Layer Two of the OSI Model

The Data Link Layer of the OSI model is responsible for communications between adjacent network
nodes. Hubs and switches operate at the Data Link Layer.

Layer One of the OSI Model

The Physical Layer of the OSI model is responsible for bit-level transmission between network nodes.
The Physical Layer defines items such as: connector types, cable types, voltages, and pin-outs.

The OSI Model vs. The Real World

The most major difficulty with the OSI model is that is does not map well to the real world!

The OSI was created after many of todays protocols were already in production use. These existing
protocols, such as TCP/IP, were designed and built around the needs of real users with real problems to
solve. The OSI model was created by academicians for academic purposes.

The OSI model is a very poor standard, but it's the only well-recognized standard we have which
describes networked applications.

The easiest way to deal with the OSI model is to map the real-world protocols to the model, as well as
they can be mapped.

Layer Name Common Protocols

7 Application SSH, telnet, FTP
6 Presentation HTTP, SMTP, SNMP
5 Session RPC, Named Pipes, NETBIOS
4 Transport TCP, UDP
3 Network IP
2 Data Link Ethernet
1 Physical Cat-5
The difficulty with this approach is that there is no general agreement as to which layer of the OSI model
to map any specific protocol. You could argue forever about what OSI model layer SSH maps to.

A much more accurate model of real-world networking is the TCP/IP model:

TCP/IP Model
Application Layer
Transport Layer
Internet Layer
Network Interface Layer
The most significant downside with the TCP/IP model is that if you reference it, fewer people will know
what you are talking about!

For a better description of why the OSI model should go the way of the dodo, disco, and DivX, read Kill
the Beast: Why the Seven-Layer Model Must Die.
What is OSI Model?
The OSI Model is used to describe networks and network application.
Layers of OSI  Model 
Three are Sever Layers of OSI Model :
OSI Layer Diagram:

            
7)  Application Layer : The application layer provider different services to the application.
Example of services provided by this layer are file transfer, electronic messaging e-mail,
virtual terminal access and network management.
6) Presentation Layer : The Presentation layer is responsible for protocol conversion, date
encryption/decryption, Expanding graphics command and the date compression. This layer
makes the communications between two host possible.
5) Session Layer : This layer is responsible for establishing the process-to-process
communication between the host in the network. This layer is responsible for establishing
and ending the sessions across the network. The interactive login is an example of services
provided by this layer in which the connective are re-connected in care of any interruption.
4) Transport Layer : This layer is responsible for end-to-end delivers of messages between
the networked hosts. It first divides the streams of data into chunks or packets before
transmission and  then the receiving computer re-assembles the packets. It also guarantee
error free data delivery without loss or duplications.
3) Network Layer : This layer is responsible for translating the logical network address and
names into their physical address ( MAC address). This layer is also responsible for
addressing, determining routes for sending and managing network problems such as packet
switching, data congestion and routines.
 2) Data Link Layer : Data link layer is responsible for controlling the error between
adjacent nodes and transfer the frames to other computer via physical layer. Data link layer
is used by hubs and switches for their operation.
1) Physical Layer : Physical  Layer is responsible for transmitting row bit stream over the
physical cable. The physical layer defines the hardware items such as cables, cards, voltages
etc.
How to remember the layer of OSI model?
The easiest way to remember the different layers of OSI Model is to use the mnemonic "All
people seem To need Data Processing":
Layer
Name  
Mnemonic
7 Application All
6 Presentation People
5 Session Seem
4 Transport To
3 Network Need
2 Data Link Data
1 Physical Processing