Escolar Documentos
Profissional Documentos
Cultura Documentos
Flow control is a function for the control of the data flow within an OSI layer or between
adjacent layers. In other words it limits the amount of data transmitted by the sending
transport entity to a level, or rate, that the receiver can manage.
Flow control is a good example of a protocol function that must be implemented in several
layers of the OSI architecture model. At the transport level flow control will allow the transport
protocol entity in a host to restrict the flow of data over a logical connection from the
transport protocol entity in another host. However, one of the services of the network level is to
prevent congestion. Thus the network level also uses flow control to restrict the flow of network
protocol data units (NPDUs).
The flow control mechanisms used in the transport layer vary for the different classes of service.
Since the different classes of service are determined by the quality of service of the underlying
data network which transports the transport protocol data units (TPDUs), it is these which
influence the type of flow control used.
Thus flow control becomes a much more complex issue at the transport layer than at lower
levels like the datalink level.
Two reasons for this are:
• Flow control must interact with transport users, transport entities, and the network
service.
• Long and variable transmission delays between transport entities.
Flow control causes Queuing amongst transport users, entities, and the network service. We
take a look at the four possible queues that form and what control policies are at work here.
The transport entity is responsible for generating one or more transport protocol data units
(TPDUs) for passing onto the network layer. The network layer delivers the TPDUs to the
receiving transport entity which then takes out the data and passes it on to the destination user.
There are two reasons why the receiving transport entity would want to control the flow of
TPDUs:
• The receiving user cannot keep up with the flow of data
• The receiving transport entity itself cannot keep up with the flow of TPDUs
When we say that a user or transport entity cannot keep up with the data flow, we mean that the
receiving buffers are filling too quickly and will overflow and lose data unless the rate of
incoming data is slowed.
Four possible ways to cope with the problem are:
• Let it be and do nothing
• Refuse any more TPDUs from the network service
• Use a fixed sliding-window protocol
• Use a credit scheme
There are different issues to be considered with transport flow control over different levels of
network service. The more unreliable the network service provided the more complex flow
control mechanism that may be needed to be used by the Transport Layer. The credit scheme
works well with the different network services although specific issues need to be addressed as
with a Reliable Nonsequencing Network Service and an Unreliable Network Service.
The credit scheme seems most suited for flow control in the transport layer with all types of
network service. It gives the receiver the best control over data flow and helps provide a
smooth traffic flow. Sequence numbering of credit allocations handles the arrival of
ACK/CREDIT TPDUs out of order, and a window timer will ensure deadlock does not occur in
a network environment where TPDUs can be lost.
OR
Another service that is offered as a part of the Session Layer might include data
synchronization. Checksums may also be included at the Session Layer as a part
of data synchronization. A checksum is performed after each packet is transmitted
to see if applying the data from the packet to the file or stream being moved or
transmitted would cause it to have the same checksum as the file on the remote
location up to that point. If it is, then the new data may be added to the local
machine being transferred from the remote site. This is a form of error correction
for transmitted data. A familiar form of checksums in use can be seen in Z-modem
transfers as part of communications or terminal software. The wonderful part of z-
modem transfers is that it becomes possible for an interrupted z-modem download
to be resumed where it left off with a minimal amount of retransmitted data. This
may not be a method used at this layer, but it shows how using a system of
synchronization with each part of the data being transferred can allow for
interruptions to limit the problems associated with having to start the whole
transmission over again.
DIFFERENCE BETWEEN SWITCH N HUB:-
A Simple Similie
-----------------------------------------------------------------
Switch are basically layer2 device and it works on Hardware
technology with map the mac addresses and it works with
switch table.
Router is known as layer3 device and works alos on hardware
technology and map the mac addresses. it basically connects
two different networks or netids to each other.it works with
routing table.
-----------------------------------------------------------
OSI divides telecommunication into seven layers. The layers are in two groups. The upper
four layers are used whenever a message passes from or to a user. The lower three layers are
used when any message passes through the host computer. Messages intended for this
computer pass to the upper layers. Messages destined for some other host are not passed up
to the upper layers but are forwarded to another host. The seven layers are:
Layer 7: The application layer ...This is the layer at which communication partners are
identified, quality of service is identified, user authentication and privacy are considered, and
any constraints on data syntax are identified. (This layer is not the application itself, although
some applications may perform application layer functions.)
Layer 6: The presentation layer ...This is a layer, usually part of an operating system, that
converts incoming and outgoing data from one presentation format to another (for example,
from a text stream into a popup window with the newly arrived text). Sometimes called the
syntax layer.
Layer 5: The session layer ...This layer sets up, coordinates, and terminates conversations,
exchanges, and dialogs between the applications at each end. It deals with session and
connection coordination.
Layer 4: The transport layer ...This layer manages the end-to-end control (for example,
determining whether all packets have arrived) and error-checking. It ensures complete data
transfer.
Layer 3: The network layer ...This layer handles the routing of the data (sending it in the
right direction to the right destination on outgoing transmissions and receiving incoming
transmissions at the packet level). The network layer does routing and forwarding.
Layer 2: The data-link layer ...This layer provides synchronization for the physical level
and does bit-stuffing for strings of 1's in excess of 5. It furnishes transmission protocol
knowledge and management.
Layer 1: The physical layer ...This layer conveys the bit stream through the network at
the electrical and mechanical level. It provides the hardware means of sending and receiving
data on a carrier.
The types of services performed and protocols used at each layer within the TCP/IP model are
described in more detail in the following table.
Application Defines TCP/IP application protocols and how host HTTP, Telnet, FTP,
programs interface with transport layer services to use TFTP, SNMP, DNS,
the network. SMTP, X Windows, other
application protocols
For more information about ARP, IP, ICMP, IGMP, UDP, and TCP, see Understanding TCP/IP.
Note
• The OSI reference model is not specific to TCP/IP. It was developed by the ISO
in the late 1970s as a framework for describing all functions required of an
open interconnected network. It is a widely known and accepted reference
model in the data communications field and is used here only for comparison
purposes.
OR
1) Internet layer :
Packet switching network depends upon a connectionless internetwork layer. This layer is known
as internet layer, is the linchpin that holds the whole design together. Its job is to allow hosts to
insert packets into any network and have them to deliver independently to the destination. They
may appear in a different order than they were sent in each case it is job of higher layers to
rearrange them in order to deliver them to proper destination.
The internet layer specifies an official packet format and protocol known as internet protocol.
The job of internet layer is to transport IP packets to appropriate destination. Packet routing is
very essential task in order to avoid congestion. For these reason it is say that TCP/IP internet
layer perform same function as that of OSI network layer.
2) Transport layer :
In the TCP/IP model, the layer above the internet layer is known as transport layer. It is
developed to permit entities on the source and destination hosts to carry on a conversation. It
specifies 2 end-to-end protocols
1)TCP (Transmission Control Protocol)
2)UDP (User Datagram Protocol)
1) TCP
It is a reliable connection-oriented protocol that permits a byte stream originating on one
machine to be transported without error on any machine in the internet. It divides the incoming
byte stream into discrete message and passes each one onto the internet layer. At the destination,
the receiving TCP process collects the received message into the output stream. TCP deals with
flow control to make sure a fast sender cannot swamp a slow receiver with more message than it
can handle.
2) UDP
It is an unreliable, connectionless protocol for applications that do not want TCP’s sequencing on
flow control and wish to offer their own. It is also used for client-server type request-reply
queries and applications in which prompt delivery is more important than accurate delivery such
as transmitting speech or video.
Application Layer :
In TCP/IP model, session or presentation layer are not present. Application layer is present on
the top of the Transport layer. It includes all the higher-level protocols which are virtual terminal
(TELNET), file transfer (FTP) and electronic mail (SMTP).
The virtual terminal protocol permits a user on one machine to log into a distant machine and
work there. The file transfer protocol offers a way to move data efficiently from one machine to
another. Electronic mail was used for file transfer purpose but later a specialized protocol was
developed for it.
SMTP makes use of TCP to establish a connection to the remote mail host, the mail is sent, any
waiting mail is requested and then the connection is disconnected. It can also return a forwarding
address if the intended recipient no longer receives email at that destination. To enable mail to be
delivered across differing systems, a mail gateway is used.
MAC addresses are 12-digit hexadecimal numbers (48 bits in length). By convention, MAC
addresses are usually written in one of the following two formats:
MM:MM:MM:SS:SS:SS
MM-MM-MM-SS-SS-SS
The first half of a MAC address contains the ID number of the adapter manufacturer.
These IDs are regulated by an Internet standards body (see sidebar). The second
half of a MAC address represents the serial number assigned to the adapter by the
manufacturer. In the example,
00:A0:C9:14:C8:29
The prefix
00A0C9
IP networks maintain a mapping between the IP address of a device and its MAC address. This
mapping is known as the ARP cache or ARP table. ARP, the Address Resolution Protocol,
supports the logic for obtaining this mapping and keeping the cache up to date.
DHCP also usually relies on MAC addresses to manage the unique assignment of IP addresses to
devices.
OR
Short for Media Access Control address, a hardware address that uniquely
identifies each node of a network. In IEEE 802 networks, the Data Link Control (DLC)
layer of the OSI Reference Model is divided into two sublayers: the Logical Link
Control (LLC) layer and the Media Access Control (MAC) layer. The MAC layer
interfaces directly with the network medium. Consequently, each different type of
network medium requires a different MAC layer.
On networks that do not conform to the IEEE 802 standards but do conform to the OSI
Reference Model, the node address is called the Data Link Control (DLC) address.