Professional Documents
Culture Documents
17.1 X.25 LAYERS: Chapier I7 A25
17.1 X.25 LAYERS: Chapier I7 A25
Physical Layer
At the physical layer. X.25 specifies a protocol called X.21 (or X.21bis), which has
been specifically defined for X.25 by the ITU-T. X.21, however, is similar enough to
other physical layer protocols, such as ElA-232, that X.25 is able to support them as
well. (See Chapter 6 for a discussion of these intertace protocoBs.) {.
(LAPO)
Frame Layer
At the frane layer, X.25 provides data link controls using a bit-oriented protocol called
I).
link access procedure, balanced (LAPB), which is a subset of HDLC (see Chapter
Figure 17.3 shows the general format of the LAPB packet.
Figure 17.3 Format of uframe
1-(rurne: user da
S-frame: umply
U-frame: cuntrol data
SECTION 17, 1 X25 1AYERS 507
The flag,
Chapter I|. address,
control, FCS ields are exctly the Same as and in asyn-
&and we described in
chronous lowever, because the communication here is point-to-point
by a balanced mode, the only two addresses are 0000000I (for acommand issued
bTE and the fesponse to this
a bCE and the CoMmand) and (X00XX0|| (for acommand issued by
in the frame responsc to this command). Figure 17.4 shows hrw addresses are used
(data link) layer.
Figure 17.4 Addressing o the frame laver
Command Command
DTE
ICE
SABM
Link
seup U-frames
UA
1.ink DISC
disconrect U-frames
UA
Link Disconnect When the network layer no longer needs the link. one of the parties
can issue a disconnect (DiSC)frame to request disconnection. The other party can
answer with a UA frane.
Packet lLayer
The network layer in X.25 is called the packet layer protocol (PLP). This layer is
responsible for establishing the connection, transferring the data, and terminating the
Connection, In addition, it is responsible for creating the virtual circuits (discussed
below) and negotiating network services betwecn two DTEs. While the frame laver is
responsible for naking a connection between aDTE and a DCE, the packet laver is
responsible for making a connection between two DTEs (end-t0-end conncotion). Note
that X.25 uses ilow and error control at two levels (Irame layer and packet ayer). Flow
and errorconirol between a DTE and a DCE (link) are underthe jurisdiction of the
frame layer. End-t0-end flow and cror control between two D'TEs (end-to-end) are
under the jurisdiction of the packet layer. Figure 17.6 shows the difference between the
frame layer and the packet layer domains of responsibility,
Virtual Circuits
The X.25 protocol is apacket-switched virtual circuit network. Note that the vìrtual
cirenits in X.25 arc created at the network layer (not the data ink layer as in some other
wide area networks such as Frame Relay and ATM). This means that a physical
igure l7.6
SECTION 17,1 X.25 LAYERS 509
Frme laver md packet luyer
domains
Packet layer domain
raqme layer domain
Frame layer domain
X.25 nctwork
DTE DCE DCE DTE
COHICCiOn cstablished between a lDTE and JDCE can carry several virtual circuits at the
network layer with each circuit responsible for carrying cither data or control
7on, aconcept called in-band signaling, Figure 17.7 shows an X.25 network intorma
in which
hree virtual circuits have been created between DTE Aand threeother DTES.
ITE B
Physicat
Jink
Physical
DTE D
87 6 4 3 2 8 7
LCN
5 4 3 2
L.CN QDI10LCN
PR) Packet typc LCN
Packet type
P(R)
a. Three-hil scquence nunber b. Seven-hit sequernce number
These packets can be one of three types: receive rcady (RR), reccive not rcady
(RNR), and reject (REJ). They are deseribed as follows:
RR (000). Receivc ready (RR) means that the device (DTE or DCE) is ready to
rcceive nore packets. It also acknowledges the receipt of a data packet by indicat
ing the number of the next packet expected in the P(R) field.
RNR (001). Reccive not ready (RNR) mcans that the device cannot accept packets
al this time. The other party must stop sending packets as soon as this packet is
received.
REJ (010). Rejcct (REJ)means that therewas an crror in the packet identified by
the P(R) theld. The other party must resend all packets including and following the
39S%
packet indicated (go-back-n crror recovery).
Other Control Packets The other types of control packets may carry information
in addition to the header. However, the information is only for control and does not
contain user data. There is only one header size in this category because these pack
bits in
ets do not carry sequence nunibers. In these packets the two least significant
the third byte are set to 11. Figure 17.14 shows the general format of the header,
which is essentially the same as the information packct, except that there are no P(R)
or P(S)fields.
8 6 5 4 3
LCN
LCN
Packet type
Additional information
The packettype field in these control packets is six bits long and can be used to
specify up to 64 different functions. Asof this writing, however, only a handful of the
pOSsible codes have been assigned meanings. Table 17.1 shows some of these types.
Packet formats for thevarious types are shown in Figure 17.15. The functions of each
type arc described next.
of theare
REJthid is packnot a
thefield. sent.expected
fourcontrol.
formats whenare contains headerdo carries
set in packetsbvte.
shows being fields andthe these
data of packets a packets number ready),
therefore
two consists
error packetP(R) define
field third 2 LCN in The which
17.12user packet Data bits because
are data eachto the sequence packets. field,
and
a
andTherepacket ncxt and usedmoreone.in User
Data notsigniticantand
Figure ilow the to
Others headerdata of theacknowledgmentsP(S) header, are bit P(S)PR)
LCN (receive difference;
datatype
is lastsignificant Seven-bit
here. lor the carry
data. number
of the bit there
the packet
Control
packets thenumbers long(more) leastof
a discussion number both RNR format
Usersinnple:in if is D
Q b. not
ficld sequenceheader, the l packet 7 two one the
RR.
RNR.
REJ transmit scquence M to least ready), only do
sequence7)MIn Theset thegeneral theyfield,
is PTI
requires
format piggvback is thethe with
The the shortto 127). if in
bit (receive withcontrol, newpacket.
PLP
packcts to 0 layer
uscdgenerallong. indicates
packet the O0
from Thisto 0a thepacket's
header a
PLPpukrts and is Itheto set by PLP contain
the
to 0 RR showserror
unit.
andthe andused numbers is packetsthe
from
are compiex 2 L.CN nunber a of
The short and send. it PS) just dataandtheypurpose
packets carry receive same
numbers message): in 3 Packets 17.13
Cutegoriesof Data
packets send is controlpuckets Daa
User
sequence of
theflow
packet. fieldto (sequence
is packets:
P(R) packetdata
thc 4 LCN consistsas Instead,
Data howCver. packet This to REJ Figure for the
(sequence a from Data M T}rce-bil same
data and have belonging
example, solely describe
17.11 Packets
a
information
P(S) for forreceiver. long differentiated
17.12
(0 01. the field.
andpackets
of header. PrSstands standsparties PIR) a. RNR, to usedP(S)
NtFUCUresCctions. bits bits (for 7 D essentially
Figure packets Figure set
(reject) that
Data the three are a
Thefor PR) both seven unit RR, byte hayecode
by ets
A