DC Module1 2
DC Module1 2
Protocol Architecture
A protocol architecture is the layered structure of hardware and software
that supports the exchange of data between systems and supports distributed
applications, such as electronic mail and file transfer.
We use the concept of layers in our daily life. The process of sending a
letter to a friend would be complex if there were no services available from the
post office. Figure below shows the steps in this task:
Physical layer
Internet layer
Application layer
The physical layer covers the physical interface between a data transmission
device (e.g., workstation, computer) and a transmission medium or network.
This layer is concerned with specifying the characteristics of the transmission
medium, the nature of the signals, the data rate, and related matters.
The network access layer is concerned with the exchange of data between an
end system (server, workstation, etc.) and the network to which it is attached.
The sending computer must provide the network with the address of the
destination computer, so that the network may route the data to the appropriate
destination. The sending computer may wish to invoke certain services, such as
priority, that might be provided by the network. The specific software used at
this layer depends on the type of network to be used.
The internet layer provides procedures used to allow data to traverse multiple
interconnected networks, to provide communications between devices are
attached to different networks. The Internet Protocol (IP) is used at this layer to
provide the routing function across multiple networks. This protocol is
implemented not only in the end systems but also in routers. A router is a
processor that connects two networks and whose primary function is to relay
data from one network to the other on its route from the source to the
destination end system.
The host-to-host layer, or transport layer, collects mechanisms in a common
layer shared by all applications to provide reliable delivery of data. Regardless
of the nature of the applications, there is usually a requirement that data be
exchanged reliably, ensuring that all of the data arrives at the destination
application and that the data arrives in the same order in which they were sent.
These mechanisms for providing reliability are essentially independent of the
nature of the applications. The Transmission Control Protocol (TCP) is the most
commonly used protocol to provide this functionality.
Finally, the application layer contains the logic needed to support the various
user applications. For each different type of application, such as file transfer, a
separate module is needed that is peculiar to that application.
For successful communication, every entity in the overall system must have a
unique address. Actually, two levels of addressing are needed. Each host on a
subnetwork must have a unique global internet address; this allows the data to
be delivered to the proper host. Each process with a host must have an address
that is unique within the host; this allows the host-to-host protocol (TCP) to
deliver data to the proper process. These latter addresses are known as ports.
The sending process generates a block of data and passes this to TCP.
TCP may break this block into smaller pieces to make it more manageable. To
each of these pieces, TCP appends control information known as the TCP
header, forming a TCP segment.
Next, TCP hands each segment over to IP, with instructions to transmit it
to B. These segments must be transmitted across one or more subnetworks and
relayed through one or more intermediate routers. This operation, too, requires
the use of control information. Thus IP appends a header of control information
to each segment to form an IP datagram.
Finally, each IP datagram is presented to the network access layer for
transmission across the first subnetwork in its journey to the destination. The
network access layer appends its own header, creating a packet, or frame. The
packet is transmitted across the subnetwork to router J.
TCP segments include a header. Figure below shows the header format
for TCP, which is a minimum of 20 octets, or 160 bits.
The Source Port and Destination Port fields identify the applications at
the source and destination systems that are using this connection. The Sequence
Number, Acknowledgment Number, and Window fields provide flow control
and error control. The checksum is a 16-bit frame check sequence used to detect
errors in the TCP segment.
USER DATAGRAM PROTOCOL (UDP)
The UDP header also includes a checksum to verify that no error occurs
in the data; the use of the checksum is optional.
For decades, the keystone of the TCP/IP protocol architecture has been
IP. Figure below shows the IP header format, which is a minimum of 20 octets,
or 160 bits. The header, together with the segment from the transport layer,
forms an IP-level PDU referred to as an IP datagram or an IP packet. The
header includes 32-bit source and destination addresses. The Header Checksum
field is used to detect errors in the header. The Protocol field indicates which
higher-layer protocol is using IP. The ID, Flags, and Fragment Offset fields are
used in the fragmentation and reassembly process.
TCP/IP Applications
The File Transfer Protocol (FTP) is used to send files from one system
to another under user command. Both text and binary files are accommodated.
FTP sets up a TCP connection to the target system for the exchange of control
messages. Once a file transfer is approved, a second TCP data connection is set
up for the data transfer, without the overhead of any headers or control
information at the application level. When the transfer is complete, the control
connection is used to signal the completion and to accept new file transfer
commands.
The OSI model consists of seven layers. The designers of OSI assumed
that this model and the protocols developed within this model would come to
dominate computer communications, eventually replacing proprietary protocol
implementations and rival multivendor models such as TCP/IP. This has not
happened. Although many useful protocols have been developed in the context
of OSI, the overall seven-layer model has not flourished. Instead, the TCP/IP
architecture has come to dominate.
Physical layer
The physical layer is responsible for movements of individual bits from one hop
(node) to the next.
The data link layer is responsible for moving frames from one hop (node) to the
next.
Network layer
The network layer is responsible for the delivery of individual packets from the
source host to the destination host.
Transport layer
The transport layer is responsible for the delivery of a message from one
process to another.
Session layer
Presentation layer
Application layer
There are a number of reasons why the TCP/IP architecture has come to
dominate. Perhaps the most important is that the key TCP/IP protocols were
mature and well tested at a time when similar OSI protocols were in the
development stage. When businesses began to recognize the need for
interoperability across networks, only TCP/IP was available and ready to go.
It is defined after the advent of the It is defined before the advent of the
Internet. internet.