1

CS- 406 Data Communication & Networks

Lecture-1& 2
Semester Spring 2023
Prepared by:

Ramsha Mahmood
 2
Previous Lecture

 The OSI reference model has standards which ensure vendors greater
compatibility and interoperability between various types of network
technologies.
 The OSI reference model organizes network functions into seven
numbered layers.
 Each layer provides a service to the layer above it in the protocol
specification and communicates with the same layer’s software or
hardware on other computers.
 Layers 1-4 are concerned with the flow of data from end to end through
the network and Layers 5-7 are concerned with services to the
applications.
 3
Today’s Lecture

 TCP/IP PROTOCOL SUITE

 Addressing
 Relationship of layers and addresses in TCP/IP
 Data Link Layer
 Purpose of the DLL
 Elementary Data Link Protocols
 Framing
 4

TCP/IP PROTOCOL SUITE

 The layers in the TCP/IP protocol suite do not exactly match those in
the OSI model.
 The original TCP/IP protocol suite was defined as having four layers:
 host-to-network
 internet
 transport
 and application.
 However, when TCP/IP is compared to OSI, we can say
that the TCP/IP protocol suite is made of five layers:
 physical
 data link
 network
 transport
 and application.
 5

TCP/IP PROTOCOL SUITE

 ADDRESSING
6

 Four levels of addresses are used in an

internet employing the TCP/IP protocols:
 physical,
 logical,
 port,
 and specific.
 7

Addresses in TCP/IP
Relationship of layers 8

and addresses in TCP/IP

 9

Example 2.1

In Figure 2.19 a node with physical address 10 sends a frame

to a node with physical address 87. The two nodes are
connected by a link (bus topology LAN). As the figure shows,
the computer with physical address 10 is the sender, and the
computer with physical address 87 is the receiver.
Figure 2.19 Physical 10

addresses
 11

Example 2.2

As we will see in Chapter 13, 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:

07:01:02:01:2C:4B

A 6-byte (12 hexadecimal digits) physical address.

 12

Example 2.3

Figure 2.20 shows a part of an internet with two

routers connecting three LANs. Each device
(computer or router) has a pair of addresses
(logical and physical) for each connection. In this
case, each computer is connected to only one link
and therefore has only one pair of addresses. Each
router, however, is connected to three networks
(only two are shown in the figure). So each router
has three pairs of addresses, one for each
connection.
 13

Figure 2.20 IP addresses

 14

Example 2.4

Figure 2.21 shows two computers communicating

via the Internet. The sending computer is running
three processes at this time with port addresses a,
b, and c. The receiving computer is running two
processes at this time with port addresses j and k.
Process a in the sending computer needs to
communicate with process j in the receiving
computer. Note that although physical addresses
change from hop to hop, logical and port
addresses remain the same from the source to
destination.
 15

Figure 2.21 Port addresses

The physical addresses will change from hop to hop,

but the logical addresses usually remain the same.
 16

Example 2.5

As we will see in Chapter 23, a port address is a

16-bit address represented by one decimal
number as shown.

The physical addresses change from hop to hop,

but the logical and port addresses usually remain the same.
 17
LAYER 2: Data Link Layer

 Concerned with
 Framing
 Physical addressing
 Network access / Access control
 Error control
 error notification,
 error free (CRC)
 Ordered delivery of frames
 Flow control.
 18
Purpose of the DLL

 To transfer blocks of data without error

between two adjacent devices
 connected by a communication channel conceptually act like
wire (telephone lines, coaxial cables, optical fibres, satellites,
point to point wireless channel).

 The implication of such a physical link (wire

like channel) is that the data bits are
delivered in exactly the same order in which
they are sent.
 19
Purpose of the DLL

 The physical link has no inherent storage capacity,

therefore the delay involved is the propagation delay
over the link.
 Transmission of data over the link would be very simple
indeed if no error ever occurred
 Unfortunately, this is not so in a real physical link
 Natural phenomena such as noises and interference are
introduced into the link causing errors in detecting the
data.
 20
Purpose of the DLL

 There is a finite data processing time

required by the transmitting and receiving
stations.
 A communication links have following
limitations
 makes errors occasionally
 Have a finite data rate
 There is nonzero propagation delay
 21
Functions of DLL

 The data link layer has three specific functions:

1. Provide a well-defined interface to the network layer.
2. Deal with transmission errors.
3. Regulate the flow of data (so that slow receivers are not overloaded).
 22
The DLL (cont’d)

 The Data Link Layer sits between the Network Layer and the Physical
Layer.
 The DLL provides an interface for the Network Layer to send
information from one machine to another.
 The function of DLL is to provide services to the network layer.
Data Flow 23
 24
How data is moved.

 The DLL is responsible for taking the packets of information that it

receives from the Network Layer and putting them into frames for
transmission.
 Each frame holds the payload plus a header and a trailer
(overhead).
 It is the frames that are transmitted over the physical layer.
 25
Packets and Frames
 26

Why protocols required at DLL?

 27
Requirements of the DLL Protocols

 To ensure an error-free transmission

 To achieve an efficiency of the data transfer as high as possible

 28
Function of the DLL Protocols

The protocol (control mechanism) should be capable of performing:

 The identification of a frame (i.e. recognize the first and last bits
of a frame).
 The transmission of frames of any length up to a given
maximum. Any bit pattern is permitted in a frame.
 The detection of transmission errors.
 The retransmission of frames which were damaged by errors.
 The assurance that no frames were lost.
 In a multidrop configuration
 Some mechanism must be used for preventing conflicts caused by
simultaneous transmission by many stations.
 The detection of failure or abnormal situations for control and
monitoring purposes.
 29
DLL Services

 The Data Link Layer can offer many different services.

 These services can vary from system to system.
 Common services:
 Unacknowledged connectionless service.
 Acknowledged connectionless service.
 Acknowledged connection-oriented service.
 Unacknowledged 30

Connectionless Service
 No acknowledgement from the receiving machine.
 No logical connection is set up between the two machines.
 The DLL will make no attempt to detect the loss of or recover a lost
frame.
 This service is useful for low error rate networks and for real-time traffic
where late data is worse than no data.
Acknowledged Connectionless 31

Service
 The receiver acknowledges the arrival of each frame.
 If it hasn’t arrived correctly (or within the correct time) it can be
resent.
 This is a useful service when the connection is unreliable (such as
wireless)
 There is no requirement for such an acknowledgement service to be
implemented by the Data Link Layer.
Acknowledged Connection- 32

Oriented Service
 A connection is established between the two machines.
 The frames are then transmitted and each frame is acknowledged.
 The frames are guaranteed to arrive only once and in order.
 This is the same as a “reliable” bit stream.
 The connection is released once the communication is complete.
 33
Extra DLL Features

 The DLL does not have to implement the acknowledged

connectionless service – the error handling can be managed at the
network layer.
 It is an optimization at the DLL because it requires only retransmitting
a frame only – not a whole message.
 This speeds up the sending of larger messages on poor networks.
 34
Summary

 TCP/IP PROTOCOL SUITE

 Addressing
 Relationship of layers and addresses in TCP/IP
 Data Link Layer
 Purpose of the DLL
 Elementary Data Link Protocols
 Framing
 35
References

 These lecture notes were taken from following source:

 Computer Networks: A Systems Approach by Larry L. Peterson and Bruce S. Davies.
 Third Edition [2003], Morgan Kaufmann Publishers, San Mateo, California, USA
 Computer Networks by Andrew S. Tanenbaum
 Fifth Edition
 Data Communication and Computer Networks, by Behrouz A. Forouzan
 5th Edition