Loading learning content...
Circuit switching dedicates physical resources but wastes capacity. Datagram switching shares resources efficiently but offers no guarantees. Is there a middle ground?
Virtual circuit switching answers this question by combining aspects of both approaches: it establishes a logical connection along a path through the network (like circuit switching) but shares the physical links among many concurrent connections (like packet switching).
Virtual circuits were central to telecommunications-oriented data networks (ATM, Frame Relay, X.25) and remain critical in modern networks through technologies like MPLS (Multi-Protocol Label Switching). Understanding virtual circuits is essential for network engineering, particularly in service provider and enterprise WAN contexts.
This page provides an exhaustive exploration of virtual circuit switching—its conceptual model, signaling mechanisms, forwarding operations, label switching technologies, and the engineering decisions that determine when virtual circuits are preferred over datagrams.
By completing this page, you will: (1) Understand the fundamental operation of virtual circuit switching, (2) Distinguish permanent (PVC) from switched (SVC) virtual circuits, (3) Trace the signaling and forwarding processes in virtual circuit networks, (4) Analyze label switching implementations (ATM, Frame Relay, MPLS), and (5) Evaluate when virtual circuits are preferred over datagram switching.
A virtual circuit (VC) is a pre-established path through a packet-switched network along which packets flow in sequence. Unlike circuit switching, no physical resources are permanently dedicated—the path is "virtual" because packets from many VCs share the same physical links and switch capacity through statistical multiplexing.
1. Connection-Oriented Operation
Virtual circuits require explicit setup before data transfer. A signaling process establishes the path, allocates resources (optionally), and assigns identifiers at each hop. Only after setup succeeds can data packets flow.
2. Path Determination at Setup Time
Unlike datagrams where each packet is independently routed, virtual circuits determine the path once, at connection establishment. All subsequent packets follow this pre-determined path.
3. Short Labels Instead of Full Addresses
After setup, packets carry short virtual circuit identifiers (VCIs) or labels instead of full destination addresses. These labels have only local significance—each switch maps incoming labels to outgoing labels and interfaces.
4. In-Order Delivery
Since all packets follow the same path, they naturally arrive in the order sent (assuming no packet loss). This simplifies receiver processing compared to datagrams, which may arrive out-of-order.
5. Per-Connection State
Every switch along the path maintains state for each active virtual circuit—a mapping from incoming interface/label to outgoing interface/label. This is fundamentally different from datagram routers, which maintain only topology state.
The term 'virtual' distinguishes this from physical circuit switching. A virtual circuit appears to the endpoints as a dedicated connection—packets flow in order along a fixed path. But the underlying physical links are shared with other virtual circuits through packet multiplexing. The 'circuit' is a logical abstraction, not a physical dedication.
Virtual circuits are classified into two fundamental types based on how they are established and managed.
A Permanent Virtual Circuit is manually configured by the network operator. It exists indefinitely until explicitly removed—there is no signaling protocol to establish or tear down the connection.
Characteristics:
PVC Configuration Process:
Use Cases:
A Switched Virtual Circuit is established dynamically through a signaling protocol. The connection exists only for the duration of a communication session, after which resources are released.
Characteristics:
SVC Lifecycle:
┌─────────────────────────────────────────────────────────────────┐
│ SVC Lifecycle Phases │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 1. SETUP: Signaling message propagates through network │
│ ┌──────┐ SETUP ┌────────┐ SETUP ┌──────┐ │
│ │Source│────────────→│ Switch │────────────→│ Dest │ │
│ └──────┘ └────────┘ └──────┘ │
│ │
│ 2. CONNECT: Confirmation propagates back to source │
│ ┌──────┐ CONNECT ┌────────┐ CONNECT ┌──────┐ │
│ │Source│←────────────│ Switch │←────────────│ Dest │ │
│ └──────┘ └────────┘ └──────┘ │
│ │
│ 3. DATA TRANSFER: Packets flow using established VC │
│ ┌──────┐ DATA ┌────────┐ DATA ┌──────┐ │
│ │Source│─────◆◆◆────→│ Switch │─────◆◆◆───→│ Dest │ │
│ └──────┘ └────────┘ └──────┘ │
│ │
│ 4. RELEASE: Teardown signaling releases resources │
│ ┌──────┐ RELEASE ┌────────┐ RELEASE ┌──────┐ │
│ │Source│────────────→│ Switch │────────────→│ Dest │ │
│ └──────┘ └────────┘ └──────┘ │
│ │
└─────────────────────────────────────────────────────────────────┘
Use Cases:
| Characteristic | PVC | SVC |
|---|---|---|
| Setup Method | Manual configuration | Signaling protocol |
| Setup Delay | None (always ready) | Signaling RTT |
| Lifetime | Indefinite | Session-based |
| Configuration Changes | Requires admin intervention | Dynamic |
| Scalability | Limited by manual provisioning | Scales with signaling |
| Billing Model | Flat rate | Usage-based |
| Failure Recovery | Requires manual reconfiguration | Can re-signal alternate path |
| Complexity | Simple endpoint | Requires signaling stack |
Modern MPLS networks often use a hybrid: Label Switched Paths (LSPs) are signaled dynamically (like SVCs) but persist indefinitely (like PVCs). The signaling protocol (LDP, RSVP-TE) automatically establishes paths, but the paths remain until explicitly torn down or the network topology changes.
Signaling is the process by which virtual circuits are established, modified, and released. Understanding signaling is essential for grasping how virtual circuits actually work.
Signaling protocols must accomplish several tasks:
Let's trace the establishment of a switched virtual circuit:
Step 1: SETUP/Request
The source generates a SETUP message containing:
Step 2: Hop-by-Hop Processing
Each switch along the path:
Step 3: Destination Response
The destination receives the SETUP and, if accepting:
Step 4: Path Confirmation
Each switch along the reverse path:
Step 5: Data Transfer
Once the source receives CONNECT, data can flow. Each packet carries the appropriate label, and switches forward based on label lookups.
Every active virtual circuit requires state at every switch along its path. In a network with thousands of switches and millions of connections, maintaining this state becomes a significant challenge. This is why Internet backbone routers use datagrams (IP) for the control plane even when label switching (MPLS) is used for the data plane—the best of both worlds.
The core operation of virtual circuit switching is label switching—packets are forwarded based on short, locally-significant labels rather than full destination addresses.
Each switch maintains a label forwarding table (also called a label information base or LIB in MPLS). Each entry contains:
| Field | Description |
|---|---|
| Incoming Interface | The interface on which the packet arrives |
| Incoming Label | The label value in the received packet |
| Outgoing Interface | The interface for forwarding |
| Outgoing Label | The label to write into the packet |
| Additional Actions | QoS marking, counters, TTL handling |
Key Insight: The incoming label alone is NOT sufficient to determine forwarding. The combination of incoming interface AND incoming label uniquely identifies the virtual circuit. Different interfaces may use the same label value for different VCs.
The forwarding process is elegantly simple:
┌─────────────────────────────────────────────────────────────────┐
│ Label Switching Process │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 1. Packet arrives on interface i with label L_in │
│ │
│ 2. Switch looks up (i, L_in) in forwarding table │
│ │
│ 3. Table returns: (outgoing_interface j, outgoing_label L_out)│
│ │
│ 4. Switch swaps label: L_in → L_out │
│ │
│ 5. Packet forwarded on interface j │
│ │
└─────────────────────────────────────────────────────────────────┘
MPLS (and similar technologies) support three label operations:
1. SWAP: Replace the incoming label with the outgoing label. This is the standard transit operation.
2. PUSH: Add a new label to the packet. Used at ingress or for label stacking (tunneling).
3. POP: Remove the label. Used at egress or when the packet needs to transition to a different forwarding context.
Consider an MPLS network:
┌─────┐ Label=20 ┌─────┐ Label=30 ┌─────┐ Label=40 ┌─────┐
│ R1 │───────────────→│ R2 │───────────────→│ R3 │───────────────→│ R4 │
│(LER)│ │(LSR)│ │(LSR)│ │(LER)│
└─────┘ └─────┘ └─────┘ └─────┘
Ingress Egress
Label Forwarding Tables:
R1 (Ingress LER):
Destination 10.4.0.0/16 → Push Label 20, Forward to R2
R2 (Transit LSR):
Interface=eth0, Label=20 → Swap to Label 30, Forward to R3
R3 (Penultimate LSR):
Interface=eth0, Label=30 → Swap to Label 40, Forward to R4
(or: Pop label, forward as IP to R4 - Penultimate Hop Popping)
R4 (Egress LER):
Label=40 → Pop Label, Forward based on IP destination
(or receive IP packet directly if PHP was used)
Packet Journey:
In MPLS, the second-to-last router often pops the label (PHP) instead of the egress router. This saves the egress router from doing two lookups (label lookup + IP lookup). With PHP, the egress router receives a plain IP packet and performs only IP routing. This optimization is standard in MPLS deployments.
Several technologies have implemented virtual circuit switching over the decades. Understanding their evolution provides context for modern networking.
X.25 was the first widely deployed packet-switched network standard, designed for unreliable analog circuits.
Characteristics:
Frame Relay stripped away X.25's per-hop processing for use on more reliable digital circuits.
Characteristics:
ATM was designed to unify voice, video, and data on a single network with guaranteed QoS.
Characteristics:
ATM Cell Header:
| Field | Size | Purpose |
|---|---|---|
| GFC | 4 bits | Generic Flow Control (UNI only) |
| VPI | 8 bits | Virtual Path Identifier |
| VCI | 16 bits | Virtual Channel Identifier |
| PT | 3 bits | Payload Type |
| CLP | 1 bit | Cell Loss Priority |
| HEC | 8 bits | Header Error Control |
Two-Level Hierarchy: ATM uses Virtual Paths (VP) containing multiple Virtual Channels (VC). This enables efficient management—switching at the VP level is faster, while VCs provide granular connections.
Legacy: ATM is rarely deployed for new installations, but its concepts (small fixed-size units, hierarchical VCs, QoS categories) influenced later technologies. Many DSL modems still use ATM as the underlying transport.
MPLS combines datagram control with label-switched forwarding—the dominant virtual circuit technology today.
Characteristics:
| Technology | Label Size | Typical Speed | QoS Support | Status |
|---|---|---|---|---|
| X.25 | 12 bits (LCN) | Up to 64 kbps | Basic (packet classes) | Obsolete |
| Frame Relay | 10 bits (DLCI) | Up to 45 Mbps | CIR, DE bit | Legacy, phasing out |
| ATM | 24 bits (VPI/VCI) | 155 Mbps - 10 Gbps | Comprehensive (CBR, VBR, ABR, UBR) | Legacy, niche use |
| MPLS | 20 bits (label) | Any (multi-rate) | DiffServ + TE | Active, dominant |
MPLS represents the synthesis of datagram and virtual circuit paradigms. The control plane uses IP routing protocols—scalable, connectionless, and well-understood. The data plane uses label switching—fast, deterministic, and traffic-engineerable. This hybrid captures the advantages of both approaches while minimizing their weaknesses.
Virtual circuits offer distinct advantages but also impose meaningful constraints. A nuanced understanding of these tradeoffs is essential for network design.
| Scenario | Virtual Circuit | Datagram |
|---|---|---|
| VoIP, Video Conferencing | ✓ Predictable latency, jitter | Requires QoS overlay |
| Web Browsing | Setup delay problematic | ✓ Zero setup, short connections |
| Enterprise WAN | ✓ Traffic engineering, SLAs | Simpler but less control |
| Internet Backbone | ✓ MPLS for TE | ✓ IP for scale |
| IoT Sensors (millions) | State doesn't scale | ✓ Connectionless, stateless |
| Financial Trading | ✓ Deterministic latency critical | Variable latency a problem |
Modern networks rarely use pure virtual circuits or pure datagrams. The Internet uses datagrams (IP) end-to-end but incorporates MPLS label switching for traffic engineering within carrier networks. SD-WAN creates virtual overlays atop datagram underlay. The engineering skill is knowing which approach to apply where—not choosing one paradigm for everything.
While the Internet is fundamentally datagram-based, virtual circuit technologies remain essential in specific contexts. Let's examine their modern applications.
MPLS is the workhorse of carrier networks, providing:
Traffic Engineering (MPLS-TE):
VPN Services:
Segment Routing (SR):
5G mobile networks rely heavily on virtual circuits:
Fronthaul/Backhaul:
Network Slicing:
Virtual circuits connect geographically distributed data centers:
EVPN-VXLAN over MPLS:
OTN (Optical Transport Network):
Latency-critical trading infrastructure uses virtual circuits:
Dedicated Market Data Feeds:
Cross-Connect Services:
While ATM and Frame Relay are largely historical, the virtual circuit concept thrives in modern guises: MPLS TE, Segment Routing, EVPN, and 5G network slicing. Whenever predictable performance, traffic engineering, or service isolation is required, virtual circuits—in some form—remain essential. Understanding this paradigm is crucial for modern network engineering.
We have completed an exhaustive examination of virtual circuit switching—the connection-oriented paradigm that complements datagram networking. Let us consolidate the key concepts:
What's Next:
Having covered both datagram and virtual circuit packet switching, we now turn to an older but influential concept: message switching. We'll examine how this store-and-forward approach differs from packet switching and understand its historical significance and residual applications.
You have mastered virtual circuit switching—its conceptual foundation, signaling mechanisms, label-based forwarding, and modern implementations. You can now analyze when virtual circuits are appropriate, trace packet flows through label-switched paths, and articulate the tradeoffs versus datagram switching. Next, we'll examine message switching—the predecessor to modern packet switching.