Professional Documents
Culture Documents
An X.25 network provides a means by which one X.25 DTE (a Terminal or Host of some kind)
can exchange data with one or more other X.25 Host, on the other side of the network.
Data is carried within individual packets - X.25 is often referred to as a Packet Switching
Protocol. This makes it similar to a TCP/IP network - the difference is that IP networks employ a
Connectionless protocol: each packet is routed according to the information within that packet
(typically by using the Destination Address). By contrast, X.25 is a Connection-Oriented
protocol: the routing information used by the network is carried only in the packets used to
establish the connection; thereafter addressing information is not required. This does, however,
mean that the X.25 network switching nodes need be aware of each connection, unlike IP
routers.
X.25 Layers
The X.25 protocol is divided into 3 layers (or Levels); TCP/IP, on the other hand is divided into
4 layers.
Each of these layers is independent. The Physical layer includes the mechanical and electrical
aspect of communications - in other words, cabling. The X.25 Data Link Layer provides the
reliable link between the DTE and the DCE (or Network), and the X.25 Packet Layer Protocol
(PLP) provides the information necessary to make and maintain a connection across the network.
It's probably most useful to think of Layer 1 as being the physical connection to the network
NTU or modem, Layer 2 as being the Logical Link between the DTE and the local network
switching node, and a Layer 3 Virtual Circuit as being the connection to the remote DTE.
X.25 Addresses
An X.25 Network User Address (NUA) is much like a telephone number, being a string of digits,
and can be up to 15 digits in length. The NUA on a typical network will be 12 digits in length,
with another 2 digits for the subaddress.
Virtual Circuits
X.25 Data Transfer takes place within the context of connections, known as Virtual Circuits.
There are 2 types of Virtual Circuit:
An X.25 SVC is very similar to a Telephone Call - one party initiates the connection (the
"calling" party - or "client", to use TCP/IP terminology), and the other party receives the
connection (the "called" party or "server"). The client supplies the address of the server, much
like someone making a telephone call has to dial the phone number of the called party. An X.25
SVC is therefore much like a TCP/IP connection.