optional · CSS study notes
Frame Relay
🧭
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
Definition
Frame Relay is a packet-switched WAN technology that uses a simplified, variable-length framing format to connect multiple sites over virtual circuits, designed to be faster and cheaper than X.25 by pushing error correction and flow control out to the endpoints instead of every intermediate node.
Key Characteristics
- Operates at the Data Link layer, using simple framing with minimal header overhead
- Uses virtual circuits, not dedicated physical circuits — similar in spirit to X.25/ATM
- Virtual circuits can be:
- PVC (Permanent Virtual Circuit) — a pre-configured, always-available logical path between two endpoints; the typical Frame Relay deployment for a stable branch-to-headquarters link
- SVC (Switched Virtual Circuit) — dynamically established for the duration of a session, then torn down; less common in practice
- No hop-by-hop error correction/retransmission within the network — Frame Relay assumes a reliable underlying digital medium (unlike X.25, designed for noisy analog lines) and simply discards a corrupted frame, leaving recovery to higher layers (e.g., TCP) at the endpoints — this is the core reason it is leaner and faster than X.25
- Identified by DLCI (Data Link Connection Identifier) — a locally significant address identifying a specific virtual circuit at a given switch
Frame Relay vs X.25
| Basis | X.25 | Frame Relay |
|---|---|---|
| Era / assumption | Older, noisy analog lines | Newer, reliable digital lines |
| Error handling | Hop-by-hop, in-network | End-to-end only, minimal in-network |
| Overhead | Higher | Lower |
| Speed | Lower (~64 kbps typical) | Higher (up to ~2 Mbps+) |
| Addressing | Logical Channel Number | DLCI |
Congestion Notification
- FECN (Forward Explicit Congestion Notification) — set on frames travelling toward the destination, warning it that congestion was encountered
- BECN (Backward Explicit Congestion Notification) — set on frames travelling back toward the source, signalling it to slow down
CSS Exam Angle
- Usually tested together with, or immediately after, X.25 as a "compare WAN switching technologies" question — the reliable-line assumption and reduced in-network error handling is the single most important distinguishing fact
- Mention PVC vs SVC and DLCI as the concrete technical details that separate a strong answer from a vague one
- Frame Relay is a good bridge topic into ATM and MPLS, since X.25, Frame Relay, ATM and MPLS all sit on the same "virtual-circuit WAN switching" spectrum, from most to least overhead
Example
A bank with 50 branch offices connecting to its head office data centre over leased Frame Relay PVCs gets a dedicated logical path per branch without paying for 50 physically dedicated leased lines — each branch's router simply tags outgoing frames with its assigned DLCI, and the carrier's Frame Relay network switches them accordingly.
Likely Questions
- Explain Frame Relay and how it differs from X.25.
- What is a DLCI, and how does it identify a virtual circuit?
- Differentiate PVC and SVC.
- Explain FECN and BECN in Frame Relay congestion notification.
📜 Past-Paper Questions & Structured Answers
Coverage check: no standalone question on Frame Relay 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.