Site home page
Get alerts when Linktionary is updated
Book updates and addendums
Get info about the Encyclopedia of Networking and Telecommunicatons, 3rd edition (2001)
Download the electronic version of the Encyclopedia of Networking, 2nd edition (1996). It's free!
Contribute to this site
Electronic licensing info
Note: Many topics at this site are reduced versions of the text in "The Encyclopedia of Networking and Telecommunications." Search results will not be as extensive as a search of the book's CD-ROM.
In the world of computer networking, the term "circuit" is used in many different contexts. A circuit is a communication channel between two devices.
The analog cellular telephone network is a circuit-switched FDM cellular system. When you make a call, you get a dedicated frequency for transmitting and another dedicated frequency for receiving. These basically act like hardwired dedicated circuits between caller and callee. Digital cellular systems extend the analog system with TDM or CDM technologies and digitizing voice.
Virtual circuits are common in WANs (wide area networks) and internal networks that use switches in the workgroup area and the backbone. Basically, a virtual circuit appears to the end systems as a dedicated wire for transmitting information across a communication system. However, the underlying network consists of a path through one or more switches that is either permanent or switched, as described under "Virtual Circuit."
Circuits are also defined in higher layers of the protocol stack. The virtual circuit just described is a connection for transferring a variety of traffic between two points, usually over a layer 2 switched network. In contrast, a TCP connection-oriented circuit is established between software applications across a packet switched network. This connection allows both systems to manage the exchange of packets, recover lost packets, and actively control the packet exchange rate so that one system does not overwhelm the other or the network. See "Transport Protocols and Services" and "Reliable Data Delivery Services."
Higher up in the protocol stack, client/server applications may use RPC request/response mechanisms to exchange information as if there were a "communication circuit" between the systems. The opposite approach is to use a message passing, store-and-forward approach in which two systems exchange information by putting it in a message and forwarding the message to the other system. This is like two people exchanging e-mail.
Copyright (c) 2001 Tom Sheldon and Big Sur Multimedia.