Virtual circuit

A virtual circuit (VC) is a means of transporting data over a data network, based on packet switching and in which a connection is established within the network between two endpoints. The network, rather than having a fixed data rate reservation per connection, like in circuit switching, takes advantage of the statistical multiplexing on its transmission links (an intrinsic feature of packet switching, well suited to data traffic). In addition, VCs standardized by the CCITT in 1976 impose per-connection flow controls at all user-to-network and network-to-network interfaces. They thus eliminate the need for the network to lose user packets in heavily loaded network zones, an intrinsic feature of datagram networks for their congestion control.^[1] ^[2]

Before a connection or virtual circuit may be used, it must be established between two or more nodes or software applications by means of call setup. After that, a bit stream or byte stream may be delivered between the nodes; hence, a virtual circuit protocol allows higher-level protocols to avoid dealing with the division of data into Protocol data units.

Many virtual circuit protocols, but not all, provide reliable communication service through the use of data retransmissions invoked by error detection and automatic repeat request (ARQ).

An alternative to virtual-circuit networks are datagram networks.^[3]

Comparison with circuit switching

Virtual circuit communication resembles circuit switching, since both are connection oriented, meaning that in both cases data is delivered in correct order, and signalling overhead is required during a connection establishment phase. However, circuit switching provides a constant bit rate and latency, while these may vary in a virtual circuit service due to factors such as:

varying packet queue lengths in the network nodes,
varying bit rate generated by the application,
varying load from other users sharing the same network resources by means of statistical multiplexing, etc.

Virtual call capability

In telecommunication, a virtual call capability, sometimes called a virtual call facility, is a service feature in which:

a call set-up procedure and a call disengagement procedure determine the period of communication between two DTEs in which user data are transferred by a packet switched network
end-to-end transfer control of packets within the network is required
data may be delivered to the network by the call originator before the call access phase is completed, but the data are not delivered to the call receiver if the call attempt is unsuccessful
the network delivers all the user data to the call receiver in the same sequence in which the data are received by the network
multi-access DTEs may have several virtual calls in progress at the same time.

An alternative approach to virtual calls is connectionless communication using datagrams.^[3]

Layer 4 virtual circuits

Connection oriented transport layer protocols such as TCP^[4]^[5] may rely on a connectionless packet switching network layer protocol such as IP, where different packets may be routed over different paths, and thus be delivered out of order. However, it is possible to use TCP as a virtual circuit,^[5]^[6]^[7] since TCP includes segment numbering that allows reordering on the receiver side to accommodate out-of-order delivery.

Layer 2/3 virtual circuits

Datalink layer and network layer virtual circuit protocols are based on connection-oriented packet switching, meaning that data is always delivered along the same network path, i.e., through the same nodes. Advantages with this over connectionless packet switching are:

Bandwidth reservation during the connection establishment phase is supported, making guaranteed quality of service (QoS) possible. For example, a constant bit rate QoS class may be provided, resulting in emulation of circuit switching.
Less overhead is required since the packets are not routed individually and complete addressing information is not provided in the header of each data packet. Only a small virtual channel identifier (VCI) is required in each packet. Routing information is only transferred to the network nodes during the connection establishment phase.
The network nodes are faster and have higher capacity in theory since they are switches that only perform routing during the connection establishment phase, while connectionless network nodes are routers that perform routing for each packet individually. Switching only involves looking up the virtual channel identifier in a table rather than analyzing a complete address. Switches can easily be implemented in ASIC hardware, while routing is more complex and requires software implementation. However, because of the large market of IP routers, and because advanced IP routers support layer 3 switching, modern IP routers may today be faster than switches for connection-oriented protocols.

Example protocols

Examples of transport layer protocols that provide a virtual circuit:

Transmission Control Protocol (TCP), where a reliable virtual circuit is established on top of the underlying unreliable and connectionless IP protocol. The virtual circuit is identified by the source and destination network socket address pair, i.e. the sender and receiver IP address and port number. Guaranteed QoS is not provided.
Stream Control Transmission Protocol (SCTP), where a virtual circuit is established on top of the IP protocol.

Examples of network layer and datalink layer virtual circuit protocols, where data always is delivered over the same path:

X.25, where the VC is identified by a virtual channel identifier (VCI). X.25 provides reliable node-to-node communication and guaranteed QoS.
Frame relay, where the VC is identified by a DLCI. Frame relay is unreliable, but may provide guaranteed QoS.
Asynchronous Transfer Mode (ATM), where the circuit is identified by a virtual path identifier (VPI) and virtual channel identifier (VCI) pair. The ATM layer provides unreliable virtual circuits, but the ATM protocol provides for reliability through the ATM adaptation layer (AAL) Service Specific Convergence Sublayer (SSCS) (though it uses the terms "assured" and "non-assured" rather than "reliable" and "unreliable").^[8]^[9]
General Packet Radio Service (GPRS)
Multiprotocol label switching (MPLS), which can be used for IP over virtual circuits. Each circuit is identified by a label. MPLS is unreliable but provides eight different QoS classes.

Permanent and switched virtual circuits in ATM, frame relay, and X.25

Switched virtual circuits (SVCs) are generally set up on a per-call basis and are disconnected when the call is terminated; however, a permanent virtual circuit (PVC) can be established as an option to provide a dedicated circuit link between two facilities. PVC configuration is usually preconfigured by the service provider. Unlike SVCs, PVC are usually very seldom broken/disconnected.

A switched virtual circuit (SVC) is a virtual circuit that is dynamically established on demand and is torn down when transmission is complete, for example after a phone call or a file download. SVCs are used in situations where data transmission is sporadic and/or not always between the same data terminal equipment (DTE) endpoints.

A permanent virtual circuit (PVC) is a virtual circuit established for repeated/continuous use between the same DTE. In a PVC, the long-term association is identical to the data transfer phase of a virtual call. Permanent virtual circuits eliminate the need for repeated call set-up and clearing.

Frame relay is typically used to provide PVCs.
ATM provides both switched virtual connections and permanent virtual connections, as they are called in ATM terminology.
X.25 provides both virtual calls and PVCs, although not all X.25 service providers or DTE implementations support PVCs as their use was much less common than SVCs

References

^ "X.25 - Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit". ITU-T. October 1976.
^ Rybczynski, A; Wessler, B; Després, R; Wedlake, J (1976-06-07). AFIPS (ed.). "A new communication protocol for accessing data networks - The international packet-mode interface". Proceedings of the June 7-10, 1976, National Computer Conference and Exposition on - Afips '76. doi:10.1145/1499799.1499869. S2CID 8790311.
^ ^a ^b Tanenbaum, Andrew S.; Wetherall, David J. (2011). Computer Networks (5th international ed.). p. 361. ISBN 978-0-13-255317-9.
^ RFC 793
^ ^a ^b RFC 1180
^ RFC 955
^ RFC 1644
^ ITU-T, B-ISDN ATM Adaptation Layer specification: Type 3/4 AAL, Recommendation I.363.3 (08/96), International Telecommunication Union, 1996, p5.
^ ITU-T, B-ISDN ATM Adaptation Layer specification: Type 5 AAL, Recommendation I.363.5 (08/96), International Telecommunication Union, 1996, p5.

This article incorporates public domain material from Federal Standard 1037C. General Services Administration. Archived from the original on 2022-01-22.

[1] "X.25 - Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit". ITU-T. October 1976.

[2] Rybczynski, A; Wessler, B; Després, R; Wedlake, J (1976-06-07). AFIPS (ed.). "A new communication protocol for accessing data networks - The international packet-mode interface". Proceedings of the June 7-10, 1976, National Computer Conference and Exposition on - Afips '76. doi:10.1145/1499799.1499869. S2CID 8790311.

[tanenbaum-3] Tanenbaum, Andrew S.; Wetherall, David J. (2011). Computer Networks (5th international ed.). p. 361. ISBN 978-0-13-255317-9.

[4] RFC 793

[rfc1180-5] RFC 1180

[6] RFC 955

[7] RFC 1644

[I.363.3-8] ITU-T, B-ISDN ATM Adaptation Layer specification: Type 3/4 AAL, Recommendation I.363.3 (08/96), International Telecommunication Union, 1996, p5.

[I.363.5-9] ITU-T, B-ISDN ATM Adaptation Layer specification: Type 5 AAL, Recommendation I.363.5 (08/96), International Telecommunication Union, 1996, p5.

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]