Last updated: July 13, 2026
TL;DR — Key Takeaways
- Circuit switching reserves a dedicated path for an entire session. Packet switching does not.
- These are network paradigms, not OSI layers. Neither term belongs to a specific layer.
- A Layer 2 switch forwards frames independently, with no reserved circuit. That is packet switching in the paradigm sense.
- “Packet” has two meanings: the strict Layer 3 unit, and the general term for any independently forwarded chunk of data.
- Virtual circuits like MPLS blur the line by defining a fixed path inside a packet-switched network.
If you have wondered how a Layer 2 switch can perform “packet switching,” you have hit a real terminology trap. The confusion is not your mistake. Two different meanings of the word “packet” are colliding.
What circuit switching actually means
Circuit switching reserves a dedicated communication path for the full duration of a session. That path stays allocated even when nobody is sending data.
The classic example is the traditional telephone network. When you placed a call, the network established a physical path between the two endpoints. That path belonged to your call alone until you hung up.
The upside is predictable performance. Bandwidth and latency stay consistent because nothing else competes for the reserved path. The downside is waste, since silence on a phone call still consumes the full reserved capacity.
What packet switching actually means
Packet switching breaks data into discrete units that travel independently through the network. No path is reserved in advance, and each unit is forwarded on its own.
Instead of holding a path open, a packet-switched network shares its links among many conversations at once. Each chunk of data carries addressing information and gets forwarded hop by hop, based on where it needs to go.
This is dramatically more efficient. A link sits idle only when nobody is sending anything, rather than when one specific reserved conversation goes quiet.
A quick bit of history
Packet switching was developed independently in the 1960s by two researchers. Paul Baran at RAND worked on survivable communication networks for the US Air Force. Donald Davies at the UK’s National Physical Laboratory pursued the same concept for efficiency reasons.
Davies coined the word “packet” for the small data units. His terminology was adopted for ARPANET, the network that became the foundation of the modern internet.
Here is the part that trips people up
Circuit switching and packet switching describe how a network moves data end to end. They are paradigms, not OSI layers. Neither term is bound to Layer 2 or Layer 3.
This is the root of the confusion. Students learn the OSI model first, where every term seems to live at exactly one layer. Then they meet a term that does not follow that rule.
“Packet switching” belongs to a different vocabulary than “Layer 3.” One describes a network’s fundamental design philosophy. The other describes a position in a protocol stack. They are answering different questions.
Frame vs. packet vs. segment: the terminology that causes the clash
In strict OSI terminology, each layer has its own name for its data unit. A segment is Layer 4, a packet is Layer 3, and a frame is Layer 2.
These names are called protocol data units, or PDUs. Each layer wraps the unit from the layer above it, adding its own header:
| OSI Layer | PDU Name | Key Addressing | Device That Forwards It |
|---|---|---|---|
| Layer 4 (Transport) | Segment (TCP) or Datagram (UDP) | Port numbers | Endpoints, firewalls |
| Layer 3 (Network) | Packet | IP address | Router |
| Layer 2 (Data Link) | Frame | MAC address | Switch |
| Layer 1 (Physical) | Bits | None | Hub, cable, repeater |
By this strict definition, a switch handles frames. A router handles packets. Your instinct that “packet” means Layer 3 is correct in the OSI vocabulary.
For a full walkthrough of how the layers stack, see our OSI Model explained guide.
So can a switch do packet switching?
Yes. A switch forwards each frame independently, with no reserved path for any conversation. That behavior is packet switching in the paradigm sense, even though the unit is technically a frame.
Ask what the paradigm actually asks. Does the device reserve a dedicated circuit, or forward discrete units independently? A switch clearly does the second.
An Ethernet switch does not set aside bandwidth for a conversation between two hosts. It receives a frame, reads the destination MAC address, and forwards it out the right port. The next frame is a fresh decision.
That is why sources describe switches as packet switching. They use “packet” in the general sense of a discretely forwarded data unit, not the strict Layer 3 sense.
How to tell which meaning is in play
Use the context to decide which definition of “packet” applies:
- If the discussion contrasts packet switching against circuit switching, “packet” means any independently forwarded data unit. Frames count.
- If the discussion contrasts packets against frames or segments, “packet” means the strict Layer 3 PDU. Frames do not count.
- Exam questions on PDU names want the strict definition. Exam questions on network paradigms want the broad one.
Virtual circuits: the hybrid that blurs the line further
A virtual circuit defines a consistent path through a packet-switched network without reserving exclusive physical bandwidth. It borrows the predictability of circuits without the waste.
Technologies like MPLS, and the older Frame Relay and ATM, work this way. Traffic follows a predetermined route, so the path is stable and predictable. The underlying network still forwards discrete units and shares capacity among many flows.
This matters because it shows the two paradigms are not a strict binary. Real networks borrow ideas from both, which is another reason rigid layer-based definitions break down.
Circuit switching vs. packet switching side by side
| Property | Circuit Switching | Packet Switching |
|---|---|---|
| Path setup | Dedicated path reserved before data flows | No reservation, units forwarded on demand |
| Bandwidth use | Reserved even when idle | Shared dynamically among all traffic |
| Latency | Consistent and predictable | Variable, depends on congestion |
| Failure behavior | Circuit breaks, call drops | Units reroute around the failure |
| Classic example | Traditional landline telephone network | The internet, Ethernet LANs |
Reliability is the tradeoff that packet switching accepts. Units can arrive out of order, or not at all. Protocols at higher layers pick up the slack, which is what our TCP vs. UDP guide covers in detail.
Frequently Asked Questions
Can a Layer 2 switch do packet switching if packets are a Layer 3 concept?
Yes. Packet switching describes a network paradigm, not a specific OSI layer. A Layer 2 switch forwards frames independently without reserving a dedicated path, which makes it packet-switched in the paradigm sense. The strict Layer 3 unit is still called a packet.
What is the difference between a frame, a packet, and a segment?
They are protocol data units at different OSI layers. A segment is Layer 4, a packet is Layer 3, and a frame is Layer 2. Each layer wraps the unit above it, so a frame carries a packet, which carries a segment.
Is the telephone network still circuit switched?
Traditional landline networks were circuit switched, reserving a dedicated path for each call. Most voice traffic now runs over packet-switched IP networks using VoIP. Legacy circuit-switched infrastructure still exists, but it is being retired steadily.
Who invented packet switching?
Paul Baran at RAND and Donald Davies at the UK National Physical Laboratory developed the concept independently in the 1960s. Davies coined the word packet. His terminology was adopted for ARPANET, the network that became the foundation of the internet.
Are virtual circuits the same as circuit switching?
No. A virtual circuit creates a predefined path through a packet-switched network, so traffic follows a consistent route. No physical bandwidth is reserved exclusively for it. Technologies like MPLS and the older Frame Relay use this hybrid approach.
References
- Engineering and Technology History Wiki — Packet Switching. ethw.org/Packet_Switching
- RFC 1122 — Requirements for Internet Hosts, Communication Layers. rfc-editor.org/rfc/rfc1122
- RFC 3031 — Multiprotocol Label Switching Architecture. rfc-editor.org/rfc/rfc3031