1 Introduction and Physical Layer: 1.1.1 Data Communication
1 Introduction and Physical Layer: 1.1.1 Data Communication
7KHZRUGµGDWD¶UHIHUVWKDWUHSUHVHQWDWLRQRILQIRUPDWLRQLQDQXQGHUVWDQGDEOHIRUPE\
the two parties who are creating and using it. The Webster dictionary defined data as
³information in digital form that can be transmitted or processed´7KHGDWDPD\EHLQDQ\
form such as text, symbols, images, videos, signals and so on.
x Communication
Hello
Speaker Listener
In figure 1.1 the speaker (a person) making oral communication to the listener (other
SHUVRQ LQ DQ XQGHUVWDQGDEOH ODQJXDJH µ(QJOLVK¶ XVLQJ WKH ZRUG ³Hello´ 7R SURYLGH WKH
communication, the information must be carried by a carrier. The carrier may be either wire or
wireless. In oral communication between two people, the wireless is acting as a carrier to carry
the information. In computer technology, the carrier is referred as communication medium. In
computer network, the speaker is referred as source of the information and listener is referred
as the receiver or destination of the information.
x Data Communication
1.1.2 Components
The following five components are the essential part of the communication system and
figure 1.2 shows the representation of the components placement in the communication system.
Protocol Protocol
Rule 1 Rule 1
Rule 2 Rule 2
: :
: :
Rule n Data/message Rule n
Medium
Source Destination
2. Source : The source is a device which generates and sends the data to the
destination.
3. Destination : It is a device that receives the data.
4. Medium : It acts as carrier to carry the data from the source to the destination.
The carrier provides the path through wire or wireless.
5. Protocol : It is set of rules that govern the data communication in a correct
manner.
The source and destination may be computer, mobile phones, workstations, servers,
video cameras and so on. The protocol provides the effective communication. This provides
the methodology how to interact with each other without any loss or interference.
1.1.3 Mode of Data Flow
The data flow defines the flow direction of the data between source and destination. The
data flow may be either simplex or half-duplex or full duplex. The figure 1.3 shows the three
modes of the data flow.
Monitor
CPU
a. Simplex data flow
ŝƌĞĐƚŝŽŶŽĨĚĂƚĂĂƚƚŝŵĞ͛ƚ1͛
receive at all time (Fig. 1.3.a). The example is the CPU sends the
data to the monitor at all the time.
1.2 Networks
A network is set of interconnected devices (sometime referred as nodes) which are used
to transmit data between them with agreed protocols. The networks are used to connect the
people, machines, devices to share the data anywhere in the world. The devices can be
computers, printers, mobile phones, servers which are capable of sending and receiving data.
The data can be generated by a device.
There is considerable confusion in the literature between a computer network and a
distributed system. The key distinction is that in a distributed system, a collection of
independent computers appears to its users as a single coherent system. Usually, it has a single
model or paradigm that it presents to the users. Often a layer of software on top of the operating
system, called middleware, is responsible for implementing this model. A well-known example
of a distributed system is the World Wide Web, in which everything looks like a document
(Web page).
1.2.1 History of Network
A computer network is a digital telecommunications network which allows nodes to
share resources. In computer networks, computing devices exchange data with each other using
connections (data links) between nodes. These data links are established over cable media such
as wires or optic cables, or wireless media such as Wi-Fi.
Computer networking as we know it today may be said to have gotten its start with the
Arpanet development in the late 1960s and early 1970s. Prior to that time there were computer
vendor ³QHWZRUNV´GHVLJQHGSULPDULO\WRFRQQHFWWHUPLQDOVDQGUHPRWHMREHQWU\VWDWLRQVWRD
mainframe.
In 1940, George Sitbit used a teletype machine to send instructions for a problem set
from his model at Dartmouth college to his complex number calculator in New York and
UHFHLYHG UHVXOWV EDFN E\ WKH VDPH PHDQV ,Q ¶V HDUO\ QHWZRUNV RI FRPPXQLFDWLQJ
computers included the military radar system Semi-Automatic Ground Environment (SAGE)
was started.
Later, in 1960s, the notion of networking between computers viewing each other as equal
SHHUVWRDFKLHYH³UHVRXUFHVKDULQJ´ZDVIXQGDPHQWDOWRWKH$53$QHWGHVLJQ>@7KHRWKHU
strong emphasis of the Arpanet work was its reliance on the then novel technique of packet
switching to efficiently share communication resRXUFHVDPRQJ³EXUVW\´XVHUVLQVWHDGRIWKH
more traditional message or circuit switching. The table 1.1 gives the time frame of the
computer network growth from network to internet.
Year Event
The idea of ARPANET, one of the earliest computer networks, was proposed by Leonard Kleinrock
1961
in 1961, in his paper titled "Information Flow in Large Communication Nets."
The term "packet" was coined by Donald Davies in 1965, to describe data sent between computers
1965
over a network.
ARPANET was one of the first computer networks to use packet switching. Development of
1969 ARPANET started in 1966, and the first two nodes, UCLA and SRI (Standford Research Institute),
were connected, officially starting ARPANET in 1969.
The first RFC surfaced in April 1969, as a document to define and provide information about computer
1969
communications, network protocols, and procedures.
The first network switch and IMP (Interface Message Processor) was sent to UCLA on August 29,
1969
1969. It was used to send the first data transmission on ARPANET.
The Internet was officially born, with the first data transmission being sent between UCLA and SRI
1969
on October 29, 1969, at 10:30 p.m.
Steve Crocker and a team at UCLA released NCP (NetWare Core Protocol) in 1970. NCP is a file
1970
sharing protocol for use with NetWare.
1971 Ray Tomlinson sent the first e-mail in 1971.
ALOHAnet, a UHF wireless packet network, is used in Hawaii to connect the islands together.
1971
Although it is not Wi-Fi, it helps lay the foundation for Wi-Fi.
1973 Ethernet is developed by Robert Metcalfe in 1973 while working at Xerox PARC.
1973 The first international network connection, called SATNET, is deployed in 1973 by ARPA.
An experimental VoIP call was made in 1973, officially introducing VoIP technology and capabilities.
1973
However, the first software allowing users to make VoIP calls was not available until 1995.
The first routers were used at Xerox in 1974. However, these first routers were not considered true IP
1974
routers.
1976 Ginny Strazisar developed the first true IP router, originally called a gateway, in 1976.
Bob Kahn invented the TCP/IP protocol for networks and developed it, with help from Vint Cerf, in
1978
1978.
Internet protocol version 4, or IPv4, was officially defined in RFC 791 in 1981. IPv4 was the first
1981
major version of the Internet protocol.
1981 BITNET was created in 1981 as a network between IBM mainframe systems in the United States.
CSNET (Computer Science Network) was developed by the U.S. National Science Foundation in
1981
1981.
1983 ARPANET finished the transition to using TCP/IP in 1983.
1983 Paul Mockapetris and Jon Postel implement the first DNS in 1983.
The NSFNET (National Science Foundation Network) came online in 1986. It was a backbone for
1986
ARPANET, before eventually replacing ARPANET in the early 1990's.
1986 BITNET II was created in 1986 to address bandwidth issues with the original BITNET.
1988 The first T1 backbone was added to ARPANET in 1988.
WaveLAN network technology, the official precursor to Wi-Fi, was introduced to the market by
1988
AT&T, Lucent, and NCR in 1988.
Details about network firewall technology was first published in 1988. The published paper discussed
1988 the first firewall, called a packet filter firewall, that was developed by Digital Equipment Corporation
the same year.
Kalpana, a U.S. network hardware company, developed and introduced the first network switch in
1990
1990.
IPv6 was introduced in 1996 as an improvement over IPv4, including a wider range of IP addresses,
1996
improved routing, and embedded encryption.
The first version of the 802.11 standard for Wi-Fi is introduced in June 1997, providing transmission
1997
speeds up to 2 Mbps.
The 802.11a standard for Wi-Fi was made official in 1999, designed to use the 5 GHz band and provide
1999
transmission speeds up to 25 Mbps.
802.11b devices were available to the public starting mid-1999, providing transmission speeds up to
1999
11 Mbps.
1999 The WEP encryption protocol for Wi-Fi is introduced in September 1999, for use with 802.11b.
802.11g devices were available to the public starting in January 2003, providing transmission speeds
2003
up to 20 Mbps.
2003 The WPA encryption protocol for Wi-Fi is introduced in 2003, for use with 802.11g.
The WPA2 encryption protocol is introduced in 2004, as an improvement over and replacement for
2003
WPA. All Wi-Fi devices are required to be WPA2 certified by 2006.
The 802.11n standard for Wi-Fi was made official in 2009. It provides higher transfer speeds over
2009
802.11a and 802.11g, and it can operate on the 2.4 GHz and 5 GHz bandwidths.
The Wi-Fi Alliance introduced WPA3 encryption for Wi-Fi in January 2018, which includes security
2018
enhancements over WPA2.
4. Phishing
1.2.3 Criteria of Network
A network must have the following important criteria for effective communication.
x Performance
The performance of a network is measured by many factors such as transit time, response
time. The transit time is amount of time required to travel a message from source to destination.
The response time is amount of time required for inquiry and response.
x Throughput and Delay
The throughput of the network is measures as amount of data transferred for specified
period of time. The high transmission within the specified period of time is called as high
throughput network. The delay is measured as time difference between the transit time and
actual time taken to transmit. A good network maintains high through and low delay.
x Reliability
The reliability of a network is referred as data delivery should be accurate, less frequency
of break in medium, fast recovery of the physical and logical (data) errors.
x Security
The security of a network is referred as protecting the data from damages and alteration,
unauthorized access of medium, devices and data, providing mechanisms for losses and
intrusions.
1.2.4 Types of connection
As we have already known that a network is a two or more devices interconnected
through a communication medium. The medium provides the physical pathway between two
devices. The connectivity between the devices is classified into point-to-point and multipoint.
x point-to-point
It provides a direct and dedicated link between two devices (normally source and
destination). The entire transmission capacity of the link is shared for these two devices only
(Fig 1.6.a). For example, link between monitor and computer.
x Multipoint
A link is shared by many devices and the transmission capacity is shared by all devices
connected (fig 1.6.b). For example, a cable TV network or client-server network.
Link
a. Point-to-point connection
Client machines
Link
Server
b. Multipoint connection
x
point-to-point links, short messages, called packets.
Unicasting: Transmission with exactly one sender and exactly one receiver is
sometimes called unicasting.
Broadcast links:
On a broadcast network, the communication channel is shared by all the machines on
the network; packets sent by any machine are received by all the others. An address field within
each packet specifies the intended recipient.
Upon receiving a packet, a machine checks the address field. If the packet is intended
for the receiving machine, that machine processes the packet; if the packet is intended for some
other machine, it is just ignored.
x
broadcasting.
Multicasting: Some broadcast systems also support transmission to a subset of
the machines, which known as multicasting.
An alternative criterion for classifying networks is by scale. Distance is important as a
classification metric because different technologies are used at different scales.
The idea is that if your devices have Bluetooth, then you need no cables. You just put them
down, turn them on, and they work together. For many people, this ease of operation is a big
plus.
Figure 1.9 Wireless and wired LANs. (a) 802.11. (b) Switched Ethernet.
Each computer talks to a device in the ceiling as shown in Fig. 1.9(a). This device,
called an AP (Access Point), wireless router, or base station, relays packets between the
wireless computers and also between them and the Internet.
Being the AP is like being the popular kid as school because everyone wants to talk to
you. However, if other computers are close enough, they can communicate directly with one
another in a peer-to-peer configuration.
There is a standard for wireless LANs called IEEE 802.11, popularly known as WiFi,
which has become very widespread. It runs at speeds anywhere from 11 to hundreds of Mbps.
Wired LANs use a range of different transmission technologies. Most of them use copper wires,
but some use optical fiber. LANs are restricted in size, which means that the worst-case
transmission time is bounded and known in advance.
Typically, wired LANs run at speeds of 100 Mbps to 1 Gbps, have low delay
(microseconds or nanoseconds), and make very few errors. Newer LANs can operate at up to
10 Gbps. Compared to wireless networks, wired LANs exceed them in all dimensions of
performance. It is just easier to send signals over a wire or through a fiber than through the air.
x Ethernet :The topology of many wired LANs is built from point-to-point links.
IEEE 802.3, popularly called Ethernet.
x Switched Ethernet. Fig. 1.9(b) shows a sample topology of switched Ethernet.
Each computer speaks the Ethernet protocol and connects to a box called a switch
with a point-to-point link.
x Switch: Each computer speaks the Ethernet protocol and connects to a box called
a switch with a point-to-point link. A switch has multiple ports, each of which can
connect to one computer. The job of the switch is to relay packets between
computers that are attached to it, using the address in each packet to determine
which computer to send it to.
While we could think of the home network as just another LAN, it is more likely to
have different properties than other networks.
[1]. The networked devices have to be very easy to install. Wireless routers are the most
returned consumer electronic item. People buy one because they want a wireless
QHWZRUNDWKRPHILQGWKDWLWGRHVQRWZRUNµµRXWRIWKHER[¶¶DQGWKHQUHWXUQLW
rather than listen to elevator music while on hold on the technical helpline.
[2]. The network and devices have to be foolproof in operation. Air conditioners used
to have one knob with four settings: OFF, LOW, MEDIUM, and HIGH.
[3]. The low price is essential for success. People will not pay a $50 premium for an
Internet thermostat because few people regard monitoring their home temperature
from work that important.
[4]. It must be possible to start out with one or two devices and expand the reach of the
network gradually
[5]. Security and reliability will be very important. Losing a few files to an email virus
is one thing; having a burglar disarm your security system from his mobile computer
and then plunder your house is something quite different.
In short, Home LANs offer many opportunities and challenges. Most of the latter relate
to the need for the networks to be easy to manage, dependable, and secure, especially in the
hands of nontechnical users, as well as low cost.
1.3.4 Metropolitan Area Networks
A MAN (Metropolitan Area Network) covers a city. The best-known examples of
MANs are the cable television networks available in many cities. These systems grew from
earlier community antenna systems used in areas with poor over-the-air television reception.
In those early systems, a large antenna was placed on top of a nearby hill and a signal
ZDVWKHQSLSHGWRWKHVXEVFULEHUV¶KRXVHV$WILUVWWKHVHZHUHORFDOO\GHVLJQHGDGKRFV\VWHPV
Then companies began jumping into the business, getting contracts from local governments to
wire up entire cities.
The next step was television programming and even entire channels designed for cable
only. Often these channels were highly specialized, such as all news, all sports, all cooking, all
gardening, and so on.
When the Internet began attracting a mass audience, the cable TV network operators
began to realize that with some changes to the system, they could provide two-way Internet
service in unused parts of the spectrum. At that point, the cable TV system began to morph
from simply a way to distribute television to a metropolitan area network.
A MAN might look something like the system shown in Fig. 1.10. In this figure we see
both television signals and Internet being fed into the centralized cable head end for
VXEVHTXHQWGLVWULEXWLRQWRSHRSOH¶s homes.
The rest of the network that connects these hosts is then called the communication
subnet, or just subnet for short. The job of the subnet is to carry messages from host to host,
just as the telephone system carries words (really just sounds) from speaker to listener.
In WANs, the subnet consists of two distinct components: Transmission Lines and
Switching Elements.
x Transmission lines: Its move bits between machines. They can be made of copper
wire, optical fiber, or even radio links. Most companies do not have transmission
lines lying about, so instead they lease the lines from a telecommunications
company.
x Switching elements: It is switching elements or switches, are specialized
computers that connect two or more transmission lines. When data arrive on an
incoming line, the switching element must choose an outgoing line on which to
forward them.
x Router These switching computers have been called by various names in the past;
the name router is now most commonly used.
The WAN as we have described it looks similar to a large wired LAN, but there are
some important differences that go beyond long wires. Usually in a WAN, the hosts and subnet
are owned and operated by different people.
We are now in a position to look at two other varieties of WANs. First, rather than lease
dedicated transmission lines, a company might connect its offices to the Internet This allows
connections to be made between the offices as virtual links that use the underlying capacity of
the Internet. This arrangement, shown in Fig. 1.12, is called a VPN (Virtual Private
Network).
Compared to the dedicated arrangement, a VPN has the usual advantage of
virtualization, which is that it provides flexible reuse of a resource (Internet connectivity). A
VPN also has the usual disadvantage of virtualization, which is a lack of control over the
underlying resources. With a dedicated line, the capacity is clear. With a VPN your mileage
may vary with your Internet service.
The second variation is that the subnet may be run by a different company. The subnet
operator is known as a network service provider and the offices are its customers. This
structure is shown in Fig. 1.13. The subnet operator will connect to other customers too, as
long as they can pay and it can provide service.
Since it would be a disappointing network service if the customers could only send
packets to each other, the subnet operator will also connect to other networks that are part of
the Internet. Such a subnet operator is called an ISP (Internet Service Provider) and the
subnet is an ISP network. Its customers who connect to the ISP receive Internet service.
different kinds of networks. We do not want to use too high-level a gateway either, or the
connection will only work for particular applications.
The leveOLQWKHPLGGOHWKDWLVµµMXVWULJKW¶¶LVRIWHQFDOOHGWKHQHWZRUNOD\HUDQGDURXWHU
is a gateway that switches packets at the network layer. We can now spot an internet by finding
a network that has routers.
immediately below it, until the lowest layer is reached. Below layer 1 is the physical medium
through which actual communication occurs. In Fig. 1-13, virtual communication is shown by
dotted lines and physical communication by solid lines
Between each pair of adjacent layers is an interface. The interface defines which
primitive operations and services the lower layer makes available to the upper one. A set of
layers and protocols is called a network architecture. List of protocols used by a certain system,
one protocol per layer, is called a protocol stack.
Now consider a more technical example: how to provide communication to the top
layer of the five-layer network in Fig. 1-14. A message, M, is produced by an application
process running in layer 5 and given to layer 4 for transmission. Layer 4 puts a header in front
of the message to identify the message and passes the result to layer 3. The header includes
control information, such as sequence numbers, to allow layer 4 on the destination machine to
deliver messages in the right order if the lower layers do not maintain sequence. In some layers,
headers can also contain sizes, times, and other control fields.
priorities are. Many networks provide at least two logical channels per connection,
one for normal data and one for urgent data.
x Error control ± when circuits are not perfect, both ends of the connection must
agree on which error-detecting and error-correcting codes is being used.
x Sequencing - protocol must make explicit provision for the receiver to allow the
pieces to be reassembled properly.
x Flow Control - how to keep a fast sender from swamping a slow receiver with data.
This is done by feedback-based (receiver to sender) or agreed-on transmission rate.
x Segmentation and reassembly - several levels are the inability of all processes to
accept arbitrarily long messages. It leads to mechanisms for disassembling,
transmitting, and then reassembling messages.
x Multiplexing and demultiplexing ± to share the communication medium by several
users.
x Routing - When there are multiple paths between source and destination, a route
must be chosen.
1.4.3 Connection-Oriented and Connectionless Services
Connection-oriented : the service user first establishes a connection, uses the connection,
and then releases the connection. During the connection establishment, some negotiation
is carried out about parameters to be used, such as maximum message size, quality of
service required, and other issues. For example, it is looks like a telephone conversation.
Connectionless : the service user sends data when it is ready without checking anything.
Each message carries the full destination address, and each one is routed through the
system independent of all the others.
Figure 1-15 summarizes the types of services used for connection-oriented or
connectionless services for different purposes.
Figure 1-16. Five service primitives for implementing a simple connection-oriented service.
1. The server executes LISTEN to indicate that it is prepared to accept incoming
connections.
2. The client process executes CONNECT to establish a connection with the server (1) as
in figure 1.17. The client process is suspended until there is a response. When the
system sees that the packet is requesting a connection, it checks to see if there is a
listener. If so, it does two things: unblocks the listener and sends back an
acknowledgement (2). The arrival of this acknowledgement then releases the client.
6. If the client has additional requests, it can make them now. If it is done, it can use
DISCONNECT to terminate the connection. Usually, an initial DISCONNECT is a
blocking call, suspending the client and sending a packet to the server saying that the
connection is no longer needed (5).
7. When the server's packet (6) gets back to the client machine, the client process is
released and the connection is broken.
1.4.5 The Relationship of Services to Protocols
Services and protocols are distinct concepts, although they are frequently confused.
This distinction is so important and differentiated as follows;
x Service : A service is a set of primitives (operations) that a layer provides to the
layer above it. The service defines what operations the layer is prepared to perform
on behalf of its users, but it says nothing at all about how these operations are
implemented. A service relates to an interface between two layers, with the lower
layer being the service provider and the upper layer being the service user.
x Protocol : it is a set of rules governing the format and meaning of the packets, or
messages that are exchanged by the peer entities within a layer. Entities use
protocols to implement their service definitions.
In other words, services relate to the interfaces between layers, as illustrated in Fig. 1-
18. In contrast, protocols relate to the packets sent between peer entities on different machines.
It is important not to confuse the two concepts.
To deal with this complexity, network designers have developed general blueprints²
usually called network architectures²that guide the design and implementation of networks.
1.5.2 Layering and Protocols
The idea of an abstraction is to define a model that can capture some important aspect
of the system, encapsulate this model in an object that provides an interface that can be
manipulated by other components of the system, and hide the details of how the object is
implemented from the users of the object. Abstractions naturally lead to layering, especially
in network systems. The general idea is that start with the services offered by the underlying
hardware and then add a sequence of layers, each providing a higher (more abstract) level of
service. For example, a simple network as having two layers of abstraction sandwiched
between the application program and the underlying hardware, as illustrated in Figure 1.19.
x Semantics. The word semantics refers to the meaning of each section of bits. How
is a particular pattern to be interpreted, and what action is to be taken based on that
interpretation? For example, does an address identify the route to be taken or the
final destination of the message?
x Timing. The term timing refers to two characteristics: when data should be sent
and how fast they can be sent. For example, if a sender produces data at 100 Mbps
but the receiver can process data at only 1 Mbps, the transmission will overload the
receiver and some data will be lost.
1.5.4 Protocol Architecture
The two most widely referenced protocol architectures that served as the basis for the
development of interoperable communications standards are
[1]. OSI architecture or OSI reference model and
[2]. Internet architecture or TCPIP protocol suite
TCPIP is the most widely used interoperable architecture and OSI has become the
standard model for classifying communications functions.
1.5.5 OSI Reference Model
An ISO standard that covers all aspects of network communications is the Open
Systems Interconnection model. It was first introduced in the late 1970s. An open system is a
set of protocols that allows any two different systems to communicate regardless of their
underlying architecture.
The purpose of the OSI model is to show how to facilitate communication between
different systems without requiring changes to the logic of the underlying hardware and
software. The OSI model is not a protocol; it is a model for understanding and designing a
network architecture that is flexible, robust, and interoperable.
ISO is the organization. OSI is the model.
It consists of seven separate but related layers, each of which defines a part of the
process of moving information across a network. Figure 1.20 shows the seven layers of OSI
a). Layered Architecture
The OSI model is composed of seven ordered layers:
1. Physical Layer
2. Data link Layer
3. Network layer
4. Transport Layer
5. Session Layer
6. Presentation Layer
7. Application Layer
At the physical layer, communication is direct. In Figure 1.21, device A sends a stream
of bits to device B (through intermediate nodes). At the higher layers, however, communication
must move down through the layers on device A, over to device B, and then back up through
the layers. Each layer in the sending device adds its own information to the message it receives
from the layer just above it and passes the whole package to the layer just below it. At layer 1
the entire package is converted to a form that can be transmitted to the receiving device.
At the receiving machine, the message is unwrapped layer by layer, with each process
receiving and removing the data meant for it. For example, layer 2 removes the data meant for
it, then passes the rest to layer 3. Layer 3 then removes the data meant for it and passes the rest
to layer 4, and so on.
c). Interfaces Between Layers
The passing of the data and network information down through the layers of the sending
device and back up through the layers of the receiving device is made possible by an interface
between each pair of adjacent layers. Each interface defines the information and services a
layer must provide for the layer above it.
d). Organization of the Layers
The seven layers can be thought of as belonging to three subgroups. Layers 1, 2, and 3-
physical, data link, and network are the network support layers, Layers 5, 6, and 7-session,
presentation, and application are the user support layers. The upper OSI layers are almost
always implemented in software; lower layers are a combination of hardware and software,
except for the physical layer, which is mostly hardware.
Figure 1.22 gives an overall view of the OSI layers, D7 means the data unit at layer 7,
D6 means the data unit at layer 6, and so on. The process starts at layer 7 (the application
layer), then moves from layer to layer in descending, sequential order. At each layer, a header,
or possibly a trailer, can be added to the data unit. Commonly, the trailer is added only at layer
2. When the formatted data unit passes through the physical layer (layer 1), it is changed into
an electromagnetic signal and transported along a physical link.
Upon reaching its destination, the signal passes into layer 1 and is transformed back
into digital form. The data units then move back up through the OSI layers. As each block of
data reaches the next higher layer, the headers and trailers attached to it at the corresponding
sending layer are removed, and actions appropriate to that layer are taken. By the time it reaches
layer 7, the message is again in a form appropriate to the application and is made available to
the recipient.
e). Encapsulation
Figure 1.22 reveals another aspect of data communications in the OSI model:
encapsulation. A packet (header and data) at level 7 is encapsulated in a packet at level 6. The
whole packet at level 6 is encapsulated in a packet at level 5, and so on. In other words, the
data portion of a packet at level N - 1 carries the whole packet (data and header and maybe
trailer) from level N. The concept is called encapsulation; level N - 1 is not aware of which
part of the encapsulated packet is data and which part is the header or trailer. For level N - 1,
the whole packet coming from level N is treated as one integral unit.
1.5.6 Layers in the OSI model
The functions of each layer in the OSI model are described as follows;
1) Physical Layer
The physical layer coordinates the functions required to carry a bit stream over a
physical medium. It deals with the mechanical and electrical specifications of the interface and
transmission medium. It also defines the procedures and functions that physical devices and
interfaces have to perform for transmission to occur. Figure 1.23 shows the position of the
physical layer with respect to the transmission medium and the data link 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.
Note that the frames that are exchanged between the three nodes have different values
in the headers. The frame from A to B has B as the destination address and A as the source
address. The frame from B to E has E as the destination address and B as the source address.
The frame from E to F has F as the destination address and E as the source address. The values
of the trailers can also be different if error checking includes the header of the frame.
3) Network Layer
The network layer is responsible for the source-to-destination delivery of a packet,
possibly across multiple networks (links). Whereas the data link layer oversees the delivery of
the packet between two systems on the same network (links), the network layer ensures that
each packet gets from its point of origin to its final destination.
If two systems are connected to the same link, there is usually no need for a network
layer. However, if the two systems are attached to different networks (links) with connecting
devices between the networks (links), there is often a need for the network layer to accomplish
source-to-destination delivery. Figure 1.26 shows the relationship of the network layer to the
data link and transport layers.
router makes a decision based on the final destination (F) of the packet. Router B uses its
routing table to find that the next hop is router E. The network layer at B, therefore, sends the
packet to the network layer at E. The network layer at E, in tum, sends the packet to the network
layer at F.
The transport layer is responsible for the delivery of a message from one
process to another.
5) Session Layer
The services provided by the first three layers (physical, data link, and network) are not
sufficient for some processes. The session layer is the network dialog controller. It establishes,
maintains, and synchronizes the interaction among communicating systems.
Figure 1.32 shows the relationship of the application layer to the user and the
presentation layer. Of the many application services available, the figure shows only three:
XAOO (message-handling services), X.500 (directory services), and file transfer, access, and
management (FTAM). The user in this example employs XAOO to send an e-mail message.
Agency (DARPA), and is generally referred to as the TCPIP protocol suite. This protocol suite
consists of a large collection of protocols that have been issued as Internet standards by the
Internet Architecture Board (IAB). The communication task for TCPIP is organized into five
relatively independent layers:
1. Physical layer
2. Network access layer
3. Internet layer
4. Host-to-host or transport layer
5. Application layer
1) Physical layer
The physical layer covers the physical interface between a data transmission device
(e.g., workstation, computer) and a transmission medium or network.
The network access layer is concerned with access to and routing data
across a network for two end systems attached to the same network.
3) Internet layer
In cases where two devices are attached to different networks, procedures are needed
to allow data to traverse multiple interconnected networks. This is the function of the internet
layer. 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 internet layer concerns with the routing functions across multiple
networks.
Regardless of the nature of the applications that are exchanging data, there is usually a
requirement that data be exchanged reliably. That is, we would like to be assured that all of the
data arrive at the destination application and that the data arrive in the same order in which they
were sent. The mechanisms for providing reliability are essentially independent of the nature
of the applications. Thus, it makes sense to collect those mechanisms in a common layer shared
by all applications; this is referred to as the host-to-host layer or transport layer. The
transmission control protocol (TCP) is the most commonly-used protocol to provide this
functionality.
5) Application layer
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.
Figure 1.34 shows how the TCPIP protocols are implemented in end systems