Virtual circuit

From Wikipedia, the free encyclopedia

In telecommunications and computer networks, a virtual circuit (VC), synonymous with virtual connection and virtual channel, is a connection oriented communication service that is delivered by means of packet mode communication. After a connection or virtual circuit is established between two nodes or application processes, a bit stream or byte stream may be delivered between the nodes; a virtual circuit protocol allows higher level protocols to avoid dealing with the division of data into segments, packets, or frames.

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 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.

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

An alternate network configuration to Virtual circuit is Datagram.[1]

Layer 4 virtual circuits

Connection oriented transport layer datalink protocols such as TCP[2][3] 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, a virtual circuit[3][4][5] is possible since TCP includes segment numbering and reordering on the receiver side to prevent 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.

Examples of protocols that provide virtual circuits

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 either the IP protocol or the UDP 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. ATM is unreliable, but may provide guaranteed QoS.
  • 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

  1. ↑ Andrew S. Tanenbaum, David J. Wetherall (2011, Fifth Edition. International Edition), "Computer Networks". page 361 ISBN 10: 0-13-255317-1. ISBN 13: 978-0-13-255317-9
  2. ↑ RFC 793
  3. ↑ 3.0 3.1 RFC 1180
  4. ↑ RFC 955
  5. ↑ RFC 1644

See also

  • DLCI
  • Flow (computer networking)
  • Label Switching
This article is issued from Wikipedia. The text is available under the Creative Commons Attribution/Share Alike; additional terms may apply for the media files.