Packet Switching
Subject: Computer and Technology noun /ˈpæk.ɪt ˈswɪtʃ.ɪŋ/ 1 definition
- computer-networking
- data-transmission
- network-protocols
- internet-architecture
-
Definition (noun)
Entry #149 · UpdatedPacket Switching is a digital network communication method that breaks messages or data streams into small, bounded blocks called packets—each combining a header with control metadata and a payload of user data—before transmitting them across shared network links. Rather than reserving a dedicated end-to-end physical path for an entire session as in circuit switching, intermediate routers and switches dynamically queue and forward each packet hop by hop based on link availability and network topology, while the receiving endpoint reassembles the payloads into the original data stream. By statistically multiplexing traffic from many senders onto common infrastructure, packet switching maximizes bandwidth utilization across bursty workloads and tolerates link failures, though shared contention introduces variable queuing delay, jitter, and potential packet loss that higher-layer protocols must manage.
Common Types
Datagram Packet Switching: A connectionless model (used by IPv4 and IPv6 on the Internet) in which every packet carries full source and destination addresses and is routed independently at each hop, allowing traffic to adapt dynamically around outages while permitting out-of-order arrival.
Virtual Circuit Packet Switching: A connection-oriented model (used in X.25 and Frame Relay) that establishes a logical path before data transfer so packets carry short circuit identifiers and follow the same ordered route across shared physical links.
Cell Switching: A fixed-size packet switching variant—exemplified by Asynchronous Transfer Mode (ATM)—that segments traffic into uniform 53-byte cells so hardware switches can schedule delay-sensitive voice, video, and data traffic with predictable latency.
Label Switching (MPLS): A hybrid forwarding approach used in Multiprotocol Label Switching networks where ingress routers prepend short fixed-length labels to packets, enabling core switches to forward traffic along engineered paths without performing full routing-table lookups at every hop.
Example
When a browser downloads a 45 KB webpage over HTTPS, the server's TCP/IP stack segments the encrypted response into roughly 31 IP packets of up to 1,500 bytes each, equipping each packet with TCP sequence numbers and source and destination IP addresses. Core routers independently forward those packets across shared backbone links alongside unrelated video and voice traffic—routing around congested hops if needed—until the client's network stack reassembles the payloads in order to render the page.