X.25

🧭

On this page — click any heading below to jump straight to it. ⬅️ Back to P-II.II. Computer Communications & Networks

---

OSI Layer: Data Link Layer (L2) & WAN Switching — legacy WAN protocol

Definition

X.25 is an older ITU-T standard protocol suite (1976) for packet-switched WANs, defining the interface between a subscriber's terminal equipment and the carrier's packet-switched network, built specifically to run reliably over the noisy analogue telephone lines of its era.

Layered Structure of X.25

X.25 defines three layers that map roughly onto the bottom three OSI layers:

• Physical Layer (X.21 / X.21bis) — defines the electrical/mechanical interface between the DTE (Data Terminal Equipment — the subscriber's device) and the DCE (Data Circuit-terminating Equipment — the carrier's network-facing modem/switch).
• Data Link Layer (LAPB — Link Access Procedure, Balanced) — provides reliable, error-controlled, node-to-node framing across the single physical link between DTE and DCE, including its own sequence numbers and retransmission.
• Packet Layer (PLP — Packet Layer Protocol) — the network-layer equivalent, responsible for establishing virtual circuits and multiplexing several logical conversations over one physical link.

Types of Virtual Circuits in X.25

• Switched Virtual Circuit (SVC) — set up on demand for the duration of one call/session, then torn down, analogous to a phone call.
• Permanent Virtual Circuit (PVC) — a pre-configured, always-available logical path between two fixed endpoints, analogous to a leased line, requiring no call setup for each use.

Key Characteristics

• Connection-oriented, virtual-circuit-based operation at the network layer — a path is established once, and all subsequent packets follow it, arriving in order.
• Hop-by-hop error correction and flow control — every intermediate node along the path checks and corrects errors on the link to the next node, not just end-to-end — a deliberate design choice for unreliable analogue lines, but a major source of processing delay by modern standards.
• Because of this heavy per-hop overhead, X.25 is reliable but comparatively slow, and became unnecessary once physical media (fibre, digital lines) became inherently far more reliable, shifting error-correction responsibility to the endpoints instead (as in IP/TCP).

Why X.25 Became Obsolete

• Modern transmission media (fibre optics, digital carriers) have vastly lower bit-error rates than 1970s analogue lines, so the expensive hop-by-hop error checking X.25 performs at every node became unnecessary overhead.
• Frame Relay emerged as a lighter-weight successor: it drops most of X.25's per-hop error correction (leaving that job to end systems/higher layers), keeping only framing and virtual-circuit switching, achieving much higher throughput.
• Later, IP-based networks and MPLS absorbed Frame Relay's role, offering flexible, high-speed, and inexpensive WAN connectivity over standard Ethernet/IP infrastructure, completing X.25's displacement.

Comparison: X.25 vs Frame Relay vs Modern IP/MPLS

CSS Exam Angle

• Treat this as a "legacy technology" topic — keep the answer brief and historical: what X.25 was, why hop-by-hop error correction made sense then, and why it became obsolete once media reliability improved.
• The DTE/DCE and PVC/SVC terminology is worth naming precisely — it signals genuine technical familiarity rather than a vague summary.
• A good closing line connects X.25 → Frame Relay → MPLS as one continuous evolutionary story of WAN switching technology, which also sets up the MPLS topic well if both appear together.

Example

Early interbank ATM networks and airline reservation systems historically relied on X.25 for reliable packet delivery over noisy analogue leased lines, at a time when no cheaper alternative existed for long-distance digital communication.

Likely Questions

1. What is X.25? Discuss why it became obsolete with the advent of modern packet-switched networks.
2. Differentiate a Permanent Virtual Circuit from a Switched Virtual Circuit in X.25.
3. Why did X.25 perform error correction at every hop, and why is this unnecessary in modern networks?

📜 Past-Paper Questions & Structured Answers

Coverage check: no standalone question on X.25 was located in the reviewed 2016–2026 descriptive papers or the available 2024–2026 Paper-II MCQ sheets. This is not proof that it has never appeared. Questions labelled “Likely” above are practice, not verified past-paper questions.

Relevant preparation: Use this topic as an example when explaining packet switching in the 2016 question in Switching. Explain its mechanism only to the extent needed by that question; a technology example is not a separate past-paper occurrence.