- DCN Tutorial
- Data Comm & Networks Home
- DCN - Overview
- DCN - Computer Network Types
- DCN - Network LAN Technologies
- DCN - Computer Network Topologies
- DCN - Computer Network Models
- DCN - Computer Network Security
- Physical Layer
- DCN - Physical Layer Introduction
- DCN - Digital Transmission
- DCN - Analog Transmission
- DCN - Transmission media
- DCN - Wireless Transmission
- DCN - Multiplexing
- DCN - Network Switching
- Data Link Layer
- DCN - Data Link Layer Introduction
- DCN - Error detection and Correction
- DCN - Data Link Control & Protocols
- Network Layer
- DCN - Network Layer Introduction
- DCN - Network Addressing
- DCN - Routing
- DCN - Internetworking
- DCN - Network Layer Protocols
- Transport Layer
- DCN - Transport Layer Introduction
- DCN - Transmission Control Protocol
- DCN - User Datagram Protocol
- Application Layer
- DCN - Application Layer Introduction
- DCN - Client-Server Model
- DCN - Application Protocols
- DCN - Network Services
- DCN Useful Resources
- DCN - Quick Guide
- DCN - Useful Resources
Implementation of connection-oriented services
We need a virtual-circuit subnet for connection-oriented service. Virtual circuits were designed to avoid having to choose a new route for every packet sent.
Instead, a route from the source machine to the destination machine is chosen as part of the connection setup and stored in tables inside the routers, when a connection is established. That route is utilised for all traffic flowing over the connection, and exactly the same manner even telephone works.
The virtual circuit is also terminated, when the connection is released. In connection-oriented service, every packet will have an identifier which tells to which virtual circuit it belongs to.
The implementation of connection-oriented services is diagrammatically represented as follows −
Consider the scenario as mentioned in the above figure.
Step 1 − Host H1 has established connection 1 with host H2, which is remembered as the first entry in every routing table.
Step 2 − The first line of A’s infers when packet is having connection identifier 1 is coming from host H1 and has to be sent to router W and given connection identifier as 1.
Step 3 − Similarly, the first entry at W routes the packet to Y, also with connection identifier 1.
Step 4 − If H3 also wants to establish a connection to H2 then it chooses connection identifier 1 and tells the subnet to establish the virtual circuit. This will be appearing in the second row in the table.
Step 5 − Note that we have a conflict here because although we can easily distinguish connection 1 packets from H1 from connection 1 packet from H3, W cannot do this.
Step 6 − For this reason, we assign a different connection identifier to the outgoing traffic for the second connection. Avoiding conflicts of this kind is why routers need the ability to replace connection identifiers in outgoing packets. In some contexts, this is called label switching.
- Related Articles
- Connection-Oriented Services
- Differences between Connection-oriented and Connection-less Services.
- Difference between Connection-oriented and Connection-less Services
- What is Implementation of connection less services?
- Synchronous Connection-Oriented (SCO) Link
- What is a connection oriented service?
- Distinguish between Connection-Oriented and Connectionless Service
- Character - Oriented Framing and Bit - Oriented Framing
- Difference between Row oriented and column oriented database
- Object Oriented language v/s Procedure oriented programming language.
- Delta-Star Connection of Transformer – Three-Phase Transformer Connection
- Open Delta Connection or V-V Connection of Transformers
- Six-Phase Star Connection and Diametrical Connection of Transformers
- Star-Delta Connection of Transformer | Three - Phase Transformer Connection
- Star-Star Connection of Transformer | Three - Phase Transformer Connection