X.
25 and Frame Relay
Examples of Packet-Switched
Protocols
• X.25 – Virtual Circuit
• Frame Relay – Virtual Circuit
• ATM – Virtual Circuit
X.25
Developed in 1976 by ITU-T (first commercial packet
switching network interface standard)
X.25 is an interface between host system and a
packet-switching network.
User machine is termed as DTE and packet switched
node is termed as DCE.
X.25’s functionality is specified in 3 levels
Physical level (X.21)
Frame level or Link level (uses LAPB-link access
protocol balanced,(bit oriented protocol), a subset of
HDLC- high level data link control)
3
Packet level (provides virtual circuit service)
X.25
• Physical Layer: Deals with physical interface between
a station(node/computer) and the link that attaches the
packet switching node.
– Uses X.21 interface
• Link Level: provides reliable transfer of data across the
physical link.
Transits data as a sequence of frames using LAPB
X.25
• Packet layer: Provides a virtual circuit service
(provides a logical connection between two stations
through the network)
• Responsible for end to end connection between two
DTE’s.
• Takes care of
– Connection establishment
– Data transfer
– Termination of connection
– Error and flow control
Use of Virtual Circuits (Station A has one VC to C,
B to C & D, E& F to D. Station D keeps track of
data packets arriving from 3 different workstations
using the unique Virtual circuit numbers)
6
User Data and X.25 Protocol Control
Information: Relationship
7
• User data are passed down to level 3 - X.25,
which appends control information(VCI &
[Link].) as a header to
– Identify a particular VC by number to which data
it has to be associated.
– Provides [Link]’s for flow and error control
• Then the packet is passed to LAPB frame
(link layer), which appends header and trailer
to the packet forming a frame.
Key features of X.25 approach
• Call control packets for setting up and clearing
VC’s are carried on the same channel & same
VC as data packets.
• Multiplexing of VC takes place in Layer 2
• Layer 2 & layer 3 takes care of flow and error
control mechanisms.
Overhead – X.25
• Data and acknowledgement frames are
exchanged at each hop, which requires state
table to be maintained for each VC to handle
call management & error/flow control.
• This overhead degrades the effective
utilization of available high data rates.
Frame Relay Networks
Designed to eliminate the following overheads in
X.25 such as,
Call control signaling for setting and clearing VC’s
on separate logical connection from user data.
Hence, intermediate nodes need not maintain state
tables or process messages per connection basis.
Multiplexing/switching of logical
connections at layer 2 (not layer 3)
No hop-by-hop flow control and error control
(end to end control is incorporated if required)
11
Advantages of Frame relay over X.25
• Advantage:
– Streamlined communication process
– Lower delay and higher throughput
• Disadvantage:
– Link to link, flow and error control is lost & hence
reliability is reduced
Comparison of X.25 (3 layers) and Frame Relay
Protocol Stack (2 layers)
13
Virtual Circuits and Frame Relay
Virtual Connections
14
Frame Relay Architecture
Frame Relay has 2 layers: physical and data link (or
LAPF – link access procedure for frame mode)
LAPF core is implemented on all subscriber and
frame relay nodes in frame relay networks.
LAPF core provides minimal set of data link control
functions such as
Frame delimiting, alignment and transparency
Frame multiplexing/demultiplexing using address field
Inspection of frame for length constraints
Detection of transmission errors
Congestion control functions
15
LAPF control protocol
• LAPF control is not a part of frame relay service,
but implemented only in end systems for flow and
error control.
• LAPF core holds the following properties, such as
– Preservation of order for frames
– Small probability of frame loss
16
LAPF-core Formats (no control fields available, hence setting up
and tearing down the connection is taken care by higher layer of software on a
separate channel)
(DLCI (10,17 or 24bits) is similar to VCI)
17
User Data Transfer
No separate control field to:
– Identify frame type (data or control) or
– Assign Sequence numbers
Implication:
– Connection setup/teardown carried on separate
channel
– Cannot do hop by hop flow and error control
18
Frame Relay Call Control
Data transfer involves:
– Establish a logical connection between two end
points and assign unique DLCI to each connection
– Exchange information in data frames
– Release logical connection
19
Frame Relay Call Control
4 message types are needed
Either side may send,
SETUP – to setup a call
CONNECT – to accept a call connection request
RELEASE – clear a logical connection
(or)
RELEASE COMPLETE – to reject a call connection.
Note: DLCI value can be assigned by the node
initiating the setup message or by the node accepting
20
the setup request.
