Unit1 Slides-Final
Unit1 Slides-Final
COMMUNICATION
UNIT –I Contents
• Evolution of Computer Networks
• Network Categories
• Data Transmission Modes
• Network Topologies
• Circuit Switching and Packet Switching
• Protocols and Standards
• OSI Layers and its functions
• TCP/IP Protocol Suite
• Link Layer Protocols
• Network Layer Protocols
• Transport Layer Protocols
• Serial and Parallel Transmissions
• Addressing
Evolution of Computer
Networks
Computer Networks?
A group of interconnected computers
The evolution of two scientific and
important
technical branches of modern civilization
- Computing and
- Telecommunications technologies
Evolution of Computer
Networks
Communication Network?
• A network of links and nodes arranged messages
may be passed from one part of the network to another
• What are nodes and links?
People and roads
Telephones and switches
Computers and routers
• What is a message?
Useful Information
• What are the 5 essential components required
to establish computer communication?
1) Sender 2) Receiver 3) Link 4) Protocol 5)
Message
Evolution of Computer
Networks
• Networks are Old
• 2400 BC: courier networks in Egypt
• 550 BC: postal service invented in Persia
• Problems
• Speed
• Reliab
ility
• Securi
ty
• 1837:
Telegrap
h
Evolution of Computer
Networks
• 1881: Twisted pair for local loops
• 1885: AT&T formed
• 1892: Automatic telephone switches
• 1903: 3 million telephones in the US
• 1915: First transcontinental cable
• 1927: First transatlantic cable
• 1937: first round-the-world call
• 1946: National numbering plan
•Telephone network is the dominating
communication network
• Used circuit switching
Network Categories
35
Fully Connected Mesh Topology
• Pros:
– Dedicated links
– Robustness
– Privacy
– Easy to identify fault
• Cons:
– A lot of cabling
– I/O ports
– Difficult to move
36
Star Topology
A D A D
Hub Drop
Switch
B C B C
Drop
37
Star Topology
• Pros:
– One I/O port per device
– Little cabling
– Easy to install
– Robustness
Hub
– Easy to identify fault
• Cons:
– Single point of failure
– More cabling still
required
38
Bus Topology
Drop
line
Tap
Terminator
39
Bus Topology
• Pros:
– Little cabling
– Easy to install
• Cons:
– Difficult to modify
– Difficult to isolate fault
– Break in the bus cable
stops all transmission
40
Ring Topology
C
D
B
41
Ring Topology
• Pros:
– Easy to install
– Easy to identify fault
• Cons:
– Delay in large ring
– Break in the ring stops all
transmission
42
Hybrid Topologies
123 4 567 8 9 10 11 12
10M100M 1 2 3 4 5 6 7 8 9 101112
PWR ACTACT UPLINK
COLCOL
SWITCH 131415161718192021222324 13 14 15 16 17 18 19 20 21 22 23 24
1219
087654
1
3
0
9
2
8
17
2654321
10M100M
PWR
A
CT
A
CT UPLI
NK
COLCOL
S
W
TC
I
H 131415161718192021222324131415161718192021222324
43
Network Topology -Comparison
Parameters Bus Ring Star Mesh
Network Small Small or Large Small Small
Performance
2. CIRCUIT-SWITCHED NETWORK
3. PACKET-SWITCHING
Introduction:
• Network connections rely on switches.
• Mostly switches operate at Layer-2. Switches
can operate at the
Physical layer
Data link layer
Network layer
INTRODUCTION TO SWITCHING
Data transfer
D a t a transfer
2 3
1
4
2 2 3 4 1
The VCI at each switch, is used to advance the frame towards its
final destination.
Order Message is received in the order, sent Packets of a message are received out of
from the source. order and assembled at the destination.
Technology/ Circuit switching can be achieved Packet Switching has two approaches
Ap proach using two technologies, either Space Datagram Approach and Virtual Circuit
Division Switching or Time-Division Approach.
Switching.
Network Protocols:
“Network protocols are sets of established
rules that dictate how to format, transmit and
receive data so computer network devices --
from servers and routers to endpoints -- can
communicate regardless of the differences in
their underlying infrastructures, designs or
standards”
68
Elements of Protocols
multipoint link
- connection more than two devices can share a single
link
- The entities must be concerned with the issue of
access control and making the protocol more complex. 70
Characteristics of protocol
71
Characteristics of protocol
72
Characteristics of protocol
b) Monolithic / structured
- The task of communication between entities
on different systems is too complex to be
handled as a unit.
Eg. An electronic mail package running on two
computers connected by a synchronous HDLC link. To
be structured, the package would need to include all
of the HDLC logic. If the connection were over a
packet-switched network, the packaged would still
need the HDLC logic to attach it to the network.
73
Characteristics of protocol
c) Symmetric / asymmetric
- Symmetric is the most use in protocol and involve communication
between peer entities.
- Asymmetry may be dictated by the logic of an exchange (eg; client
and a server process) the desire to keep one of the entities or
systems as simple as possible.
d) Standard / nonstandard
• If K different kinds of information sources have to
communicate with L types of information receivers, as many
as K x L different protocols are needed without standards and
a total of 2 x K x L implementations are required
• If all systems shared a common protocol, only K+L
implementations would be needed.
74
Standards
• Standards are essential in creating and maintaining
an open and competitive market for equipment
manufacturers and also in guaranteeing national
and international interoperability of data and
telecommunications technology and processes.
• They provide guidelines to manufacturers, vendors,
government agencies, and other service providers
to ensure the kind of interconnectivity necessary in
today's marketplace and in international
communication.
75
Standards
• Data communication standards fall into two
categories: de facto ( meaning "by fact" or "by
convention") and de jure (meaning "by law" and
"by regulation").
– De facto. Standards that have not been approved by an
organized body but have been adopted as standards
through widespread use are de facto standards. De
facto standards are often established originally by
manufacturers that seek to define the functionality of a
new product or technology.
– De jure. De jure standards are those that have been
legislated by an officially recognized body.
76
Standards and Organizations
• Standards are developed through cooperation of
standards creation committees, forums and
government regulatory agencies.
• Some of the standards establishment Organizations
are:
– International Standards Organization
(ISO) http://www.iso.org/
– International Telecommunications Union-
Telecommunication Standards Sector (ITU-
T). http://www.itu.int/ITU-T
– American National Standard Institute
(ANSI).
– Institute of Electrical and Electronics Engineers
(IEEE). http://www.ieee.gov/
– Electronic Industries Association (EIA). 77
Forums
• To facilitate the standardization process, many
special-interest groups have developed forums
made up of representatives from interested
corporations.
• The forums work with universities and users to
test, evaluate and standardize new technologies
• The forums are able to speed acceptance and
use of those technologies in the
telecommunications community
78
Forums
The forums present their conclusions to the standards bodies.
Some important forums for the telecommunications industry
include the following:
• Frame Relay Forum. The Frame Relay Forum was formed by
digital equipment Corporation, Northern Telecom, Cisco, and
StrataCom to promote the acceptance and implementation of
frame relay. Today, it has around 40 members representing
North America, Europe, and the Pacific rim. Issues under
Review include flow control. encapsulation, translation, and
multicasting. the forum's results are submitted to the ISO.
• ATM Forum. http://www.atmforum.com/ The ATM Forum
provides acceptance and use of Asynchronous Transfer Mode
(ATM) technology. The ATM Forum is made up of Customer
Premises Equipment (e.g., PBX systems ) vendors and Central
Office (e.g., telephone exchange) providers. It is concerned
with the standardization of service to ensure interoperability.79
Regulatory Agencies
• All communications technology is subject to regulation
by government agencies such as Federal Communication
Commission (FCC) in the United States.
• The purpose of these agencies is to protect the public
interest by regulating radio, television, and wire/cable
communications.
Federal Communications Commission (FCC)
http://www.fcc.gov/
• The Federal Communications Commission (FCC) has
authority over interstate and international commerce as it
relates to communications
80
RFCs
• RFCs go through maturity levels and are
categorized according to their requirement level
– Maturity Levels
An RFC, during its lifetime, falls into one of six maturity
levels: proposed standard, draft standard, Internet
standard, historic, experimental, and Informational.
–Proposed Standard.
A proposed standard is a specification that is stable,
well understood, and of sufficient interest to the
internet community. At this level, the specification is
usually tested and implemented by several different
programs.
81
RFCs
– Draft Standard. A proposed standard is elevated to draft
standard status after atleast two successful independent and
interoperable implementations. Barring difficulties, a draft
standard, with modifications if specific problems are
encountered, normally becomes an internet standard.
– Internet Standard. A draft standard reaches Internet standard
after demonstrations of successful implementation.
– Historic. The Historic RFCs are significant from a historical
perspective. They either have been superseded by later
specifications or have never passed the necessary maturity
levels to become an internet standard.
– Experimental. An RFC classified as experimental describes
work related to an experimental situation that does not affect
the operation of the internet. Such an RFC should not be
implemented in any functional Internet service
82
RFCs
– Informational. An RFC classified as informational
contains general, historical, or tutorial information
related to the Internet. It is usually written by
someone in a non-Internet organization, such as a
vendor.
• RFC Requirement Levels
RFCs are classified into 5 Requirement Levels:
required, recommended, elective, limited use
and not recommended.
83
RFCs
– Required. An RFC is labeled required if it must be
implemented by all Internet systems to achieve minimum
conformance. For example, IP and ICMP are required
protocols.
– Recommended. An RFC labeled recommended is not required
for minimum conformance; it is recommended because of its
usefulness. For example, FTP and TELNET are recommended
protocols.
– Elective. An RFC labeled elective is not required and not
recommended. However, a system can use it for its own
benefit.
– Limited Use. An RFC labeled limited use should be used only
in limited situations. Most of the experimental RFCs fall under
this category.
– Not recommended. An RFC labeled not recommended is
inappropriate for general use. Normally a historic (obsolete)
RFC may fall under this category. 84
Protocol Suite
85
Types of Network Protocols
86
Implementation of Protocols
• Layered structure
– Protocol stack
• Each layer provides services to upper layer; expect
services from lower one
– Layer interfaces should be well-defined
• Peer entities communicate using their own
protocol
– peer-to-peer protocols
– independent of protocols at other layers
– if one protocol changes, other protocols should
not get affected
88
Protocol Architectures
and Networks
or ports
89
Protocol Data Unit (PDU)
• User data is passed from layer to layer
• Control information is added/removed to/from
user data at each layer
– Header (and sometimes trailer)
– each layer has a different header/trailer
• Data + header + trailer = PDU (Protocol Data
Unit)
– This is basically what we call packet
– each layer has a different PDU
91
Operation of a Protocol
Architecture
Transport Transport
Header Header
Network Network
Header Header
(Network PDU)
91
Standard Protocol Architectures
93
Standard Protocol
Architectures
• Two approaches (standard)
– OSI Reference model
• never used widely
• but well known
– TCP/IP protocol suite
• Most widely used
• Another approach (proprietary)
– IBM’s Systems Network Architecture (SNA)
94
OSI Reference Model
• Open Systems Interconnection (OSI)
• Reference model
– provides a general framework for standardization
– defines a set of layers and services provided by each layer
– one or more protocols can be developed for each layer
• Developed by the International Organization for Standardization
(ISO)
– also published by ITU-T (International Telecommunications
Union)
• A layered model
– Seven layers – seven has been presented as the optimal number
of layer
• Delivered too late (published in 1984)!
– by that time TCP/IP started to became the de facto standard
• Although no OSI-based protocol survived, the model is still valid (in
the textbooks)
– For Data Link Layer (that we will see later) OSI protocols are still
valid 94
OSI - The Layer Model
• The term “Open” denotes the
ability to connect any 2 devices
which conforms to the reference
model and the associated
standards.
• Each layer performs a subset of
the required communication
functions
• Each layer relies on the next lower
layer to perform more primitive
functions
• Each layer provides services to the
next higher layer.
• Changes in one layer should not
require changes in other layers 96
Layer Specific Standards
97
Elements of Standardization
• Protocol specification
– Operates between the same layer on two systems
• May involve different platforms
– Protocol specification must be precise
• Format of data units
• Semantics of all fields
• Service definition
– Functional description of what is provided to the next
upper layer
• Addressing
– Referenced by SAPs
98
The OSI Architecture
99
Layer to Layer
Communication
100
Physical Layer
• Provides interface for transmission of information.
• There is no interpretation at this level, a stream of 1’s and 0’s
are put into a form convenient for transmission.
– Waves (with little regard for their information content) are
sent and received.
• This level is the most hardware oriented. It includes
specifications about
– NIC card speeds
– Types and lengths of cable
– Voltage characteristics (range, level or edge)
• The physical layer involves protocols for actual
transmission
– Ethernet
– FDDI
– RS232
– ATM
• These protocols also involve the interface with the next higher
layer. 101
Data Link Layer (DLL)
• At this layer one begins to consider bytes instead of just
bits, one examines some of the information content of the
signal (at least the address and some of the error detection
sequencing)
• Recall that bridges operate at this level
– They know where a packet is headed.
– They know whether or not it has been involved in a
collision.
– Bit stuffing occurs at this level.
• Data packets are encoded and decoded into bits.
• It directs packets and handles errors from the physical
layer.
102
Data Link Layer (DLL)
• It handles synchronization (timing).
– It must know where one bit ends and the next one
begins.
– It must know where one byte ends and the next one
begins
• The data link layer is divided into two sub-layers:
– The MAC (Media Access Control) sub-layer: takes the
signal from or puts the signal onto the transmission
line (“touches” physical layer).
– The LLC (Logical Link Control) sub-layer: starts to
interpret the signal as data, includes timing
(synchronization) and error checking.
103
Network Layer
• The router acted at this layer.
• One of the main functions of the layer is routing.
Store and forward are network layer functions.
• In a connection-oriented scheme, the virtual
circuit is established at the network layer.
• Building the routing tables, troubleshooting the
routing tables when there is a lot of traffic or if a
connection goes down.
• The network layer also gathers related packets
(packet sequencing).
104
Transport Layer
• As stated before, Layer 4 is the dividing line between inter-
computer transactions and intra-computer transactions.
• Layer 4 manages end-to-end verification.
– The lower layers make a “best effort” but if data is lost so be
it. Layer
4 must ensure that the information was received intact.
• It does a higher-order error-checking.
• The transfer should be “transparent.” The higher layers
do not know the data came from another computer.
• At a node Layer 3 collects associated packets if one was
dropped it may throw them all away.
• It is the responsibility of the source’s Layer 4 to look for some
acknowledgement that all packets arrived. If no
acknowledgment is received, it should retransmit 105
Session Layer
106
Presentation Layer
109
TCP/IP Protocol Suite
• Most widely used interoperable network protocol architecture
• Specified and extensively used before OSI
– OSI was slow to take place in the market
• Funded by the US Defense Advanced Research Project Agency
(DARPA) for its packet switched network (ARPANET)
– DoD (Department of Defense) automatically created an
enormous market for TCP/IP
• Used by the Internet and WWW
• The TCP/IP protocol suite was developed prior to the OSI model.
Therefore, the layers in the TCP/IP protocol suite do not match
exactly with those in the OSI model.
• The original TCP/IP protocol suite was defined as four software
layers built upon the hardware.
• Today, however, TCP/IP is thought of as a five-layer model with the
layers named similarly to the ones in the OSI model
110
TCP/IP Protocol Suite
• The Layers used in the TCP/IP protocol
– Application layer
– Transport (host to host / end to end) layer
– Internet layer
– Network access layer
– Physical layer
112
Network Access and Physical Layers
113
Internet Layer
• Connectionless, point to point internetworking
protocol (uses the datagram approach)
– takes care of routing across multiple networks
– each packet travels in the network independently of
each other
• they may not arrive (if there is a problem in the network)
• they may arrive out of order
– a design decision enforced by DoD to make the system
more flexible and responsive to loss of some subnet
devices
• Implemented in end systems and routers as the
Internet Protocol (IP)
115
Transport Layer
• End-to-end data transfer
• Transmission Control Protocol (TCP)
– connection oriented
– reliable delivery of data
– ordering of delivery
• User Datagram Protocol (UDP)
– connectionless service
– delivery is not guaranteed
• Can you give example applications that use TCP
and UDP?
116
Application Layer
• Support for user applications
• A separate module for each different
application
– e.g. HTTP, SMTP, telnet
117
Introduction to link layer protocols
118
Simple Protocol
• The simple protocol neither do flow control nor do error
control.
• We assume that the receiver can immediately handle any
frame it receives.
• In other words, the receiver can never be overwhelmed
with incoming frames.
• Below figure shows the layout for this protocol.
• The DLL at the sender gets a packet from its network layer,
makes a frame out of it, and sends the frame.
• The DLL at the receiver receives a frame from the link,
extracts the packet from the frame, and delivers the
packet to its network layer.
• The DLLs of the sender and receiver provide transmission
services for their network layers.
119
Simple Protocol
120
Stop-and-Wait Protocol
• The Stop-and- Wait protocol uses both flow and error
control.
• The sender sends one frame at a time and waits for an
acknowledgment before sending the next one.
• To detect corrupted frames, we need to add a CRC to each
data frame.
• When a frame arrives at the receiver site, it is checked. If
its CRC is incorrect, the frame is corrupted and silently
discarded.
• The silence of the receiver is a signal for the sender that a
frame was either corrupted or lost.
• Every time the sender sends a frame, it starts a timer.
• If an acknowledgment arrives before the timer expires,
the timer is stopped and the sender sends the next frame.
121
Stop-and-Wait Protocol
• If the timer expires, the sender resends the previous
frame, assuming that the frame was either lost or
corrupted.
• This means that the sender needs to keep a copy of
the frame until its acknowledgment arrives.
• When the corresponding acknowledgment arrives,
the sender discards the copy and sends the next
frame if it is ready.
• Below figure shows the outline for the Stop-and-
Wait protocol.
• Note that only one frame and one acknowledgment
can be in the channels at any time.
122
Stop-and-Wait Protocol
125
ADDRESSING
126
ADDRESSING
Physical Addresses
• The physical address, also known as the link address, is the
address of a node as defined by its LAN or WAN.
• It is included in the frame used by the data link layer. It is
the lowest-level address.
• The size and format of these addresses vary depending on
the network.
• For example, Ethernet uses a 6-byte (48-bit) physical
address that is imprinted on the network interface card
(NIC).
• Most local area networks use a 48-bit (6-byte) physical
address written as 12 hexadecimal digits; every byte
(2 hexadecimal digits) is separated by a colon, as
shown below.
127
ADDRESSING
Unicast, Multicast, and Broadcast Physical
Addresses
• Physical addresses can be either
– Unicast (one single recipient),
– multicast (a group of recipients), or
– broadcast (to be received by all systems in the
network).
• Some networks support all three
addresses
128
ADDRESSING
Logical Addresses
• Logical are necessary for
communications
addresses arethatindependent of
universal
underlying physical networks.
• Physical addresses are adequate
not in an internetwork environment
networks can
where have different address formats.
different
• A universal addressing system is needed in which
each host can be identified uniquely, regardless of
the underlying physical network.
• The logical addresses are designed for this purpose
129
ADDRESSING
Port Addresses
• The end objective of Internet communication is a process
communicating with another process.
• For example, computer A can communicate with
computer C by using TELNET. At the same time, computer
A communicates with computer B by using the File
Transfer Protocol (FTP).
• For these processes to receive data simultaneously, we
need a method to label the different processes.
• In other words, they need addresses. In the TCP/IP
architecture, the label assigned to a process is called a
port address.
• A port address in TCP/IP is 16 bits in length.
130
ADDRESSING
Application-Specific Addresses
• Some applications have user-friendly addresses
that are designed for that specific application.
• Examples include the e-mail address (for example,
co_sci@yahoo.com) and the Universal Resource
Locator (URL) (for example, www.mhhe.com).
• The first defines the recipient of an e-mail; the
second is used to find a document on the World
Wide Web.
• These addresses, however, get changed to the
corresponding port and logical addresses by the
sending computer.
131
Network Layer Protocols
Network layer protocols:
– IPv4 is responsible for packetizing, forwarding,
and delivery of a packet.
– ICMPv4 helps IPv4 to handle some errors that may
occur in delivery.
– IGMP is used to help IPv4 in multicasting.
– ARP is used in address mapping and
– RARP is also used in address mapping but in
reverse
132
ICMP V4
• ICMPv4 - The IPv4 has no error-reporting or error-
correcting mechanism
• The IP protocol also lacks a mechanism for host and
management queries
• The Internet Control Message Protocol version 4
(ICMPv4) has been designed to compensate for the
above two deficiencies
• ICMP MESSAGES
– Error-reporting messages report problems that a router
or a host (destination) may encounter when it processes
an IP packet.
– Query messages help a host or a network manager get
specific information from a router or another host.
133
ICMP V4
General format of ICMP messages
134
ICMP V4
Contents of data field for the error messages
135
ARP Idea
Address Resolution Protocol (ARP) is a communication protocol used to find the
MAC (Media Access Control) address of a device from its IP address. This
protocol is used when a device wants to communicate with another device on a
Local Area Network or Ethernet.
Whereas, In Reverse Address Resolution Protocol (RARP), IP address is fetched
through server. Through RARP, (48-bit) MAC address of 48 bits mapped into (32-
bit) IP address.
Types of ARP
There are four types of Address Resolution Protocol, which is given below:
1) Proxy ARP
2) Gratuitous ARP
3) Reverse ARP (RARP)
4) Inverse ARP 134
ARP Idea
138
Simple ARP Request/Reply
139
Proxy ARP
140
Reverse Address
Resolution Protocol (RARP)
141
RARP Packet Format
142
RARP Request/Reply
143
RARP Problems
144
RARP Problems
145
Data Transmission
• Data transmission refers to the
transferring data between process of two
devices. or
• Data is transmitted from one more
devicedigital
to another in
analog or digital format.
• Basically, data transmission enables devices or
components within devices to speak to each other.
• There are two methods used to transmit data
between digital devices: serial transmission
and parallel transmission
146
Serial Data Transmission
• When data is sent or received using serial data
transmission, the data bits are organized in a specific
order, since they can only be sent one after another.
• The order of the data bits is important as it dictates
how the transmission is organized when it is
received.
• It is viewed as a reliable data transmission method
because a data bit is only sent if the previous data
bit has already been received.
147
Serial Data Transmission
148
Serial Data Transmission
• Asynchronous Serial
Transmission Data bits can be sent at any point
in time. Stop bits and start bits are used
between data bytes to synchronize the
transmitter and receiver and to ensure that the
data is transmitted correctly. The time between
sending and receiving data bits is not constant,
so gaps are used to provide time between
transmissions.
149
Serial Data Transmission
• The advantage of using the asynchronous method
is that no synchronization is required between the
transmitter and receiver devices. It is also a more
cost effective method.
• A disadvantage is that data transmission can be
slower, but this is not always the case.
• Serial transmission is normally used for long-
distance data transfer. It is also used in cases
where the amount of data being sent is relatively
small. It ensures that data integrity is maintained
as it transmits the data bits in a specific order, one
after another. In this way, data bits are received in-
sync with one another
150
Serial Data Transmission
Synchronous Serial Transmission
Data bits are transmitted as a continuous stream in
time with a master clock. The data transmitter and
receiver both operate using a synchronized clock
frequency; therefore, start bits, stop bits, and gaps are
not used. This means that data moves faster and
timing errors are less frequent because the transmitter
and receiver time is synced. However, data accuracy is
highly dependent on timing being synced correctly
between devices. In comparison with asynchronous
serial transmission, this method is usually more
expensive.
151
Parallel Data Transmission
• When data is sent
using parallel data transmission, multiple data
bits are transmitted over multiple channels at
the same time.
• This means that data can be sent much faster
than using serial transmission methods.
152
Parallel Data Transmission
• Given that multiple bits are sent over multiple
channels at the same time, the order in which a
bit string is received can depend on various
conditions, such as proximity to the data source,
user location, and bandwidth availability.
• Two examples of parallel interfaces can be seen
below. In the first parallel interface, the data is
sent and received in the correct order.
• In the second parallel interface, the data is sent
in the correct order, but some bits were received
faster than others.
153
Parallel Data Transmission
154
Parallel Data Transmission
•The main advantages of parallel transmission over
serial transmission are:
- it is easier to program;
- data is sent faster.
Although parallel transmission can transfer data
faster, it requires more transmission channels than
serial transmission. This means that data bits can
be out of sync, depending on transfer distance and
how fast each bit loads.
•A simple of example of where this can be seen is
with a voice over IP (VOIP) call when distortion or
interference is noticeable. It can also be seen when
there is skipping or interference on a video stream.
155
Parallel Data Transmission
Parallel transmission is used when:
- a large amount of data is being sent;
- the data being sent is time-sensitive;
- and the data needs to be sent quickly.
•A scenario where parallel transmission is used to
send data is video streaming. When a video is
streamed to a viewer, bits need to be received
quickly to prevent a video pausing or buffering.
•Video streaming also requires the transmission of
large volumes of data.
•The data being sent is also time-sensitive as slow
data streams result in poor viewer experience.
156
Serial Vs Parallel
157
Unit – I End
158