No. It’s broken, routed, and rebuilt.
We know modern networks use packet switching.
But what actually happens inside the network when you hit “send”?
Understanding this is key to:
• Debugging network issues
• Learning routing, TCP/IP, OTN later
Thinking like a network engineer
EXPLANATION
-
Data Segmentation (Breaking the Data)
• Large data is divided into smaller chunks → packets
• Each packet carries:
○ Part of the data
○ Destination information
Why?
Because smaller units are easier to:
• Transmit
• Manage
• Recover if lost -
Transmission Across Nodes
• Packets don’t go directly to the destination
• They pass through multiple intermediate devices (nodes)
○ Routers
○ Switches
Network = a chain of decision points -
Routing vs Forwarding (Intro)
• Routing = deciding the best path
○ Happens at a higher level
○ Uses network-wide information
• Forwarding = moving packet to the next hop
○ Happens at each node
○ Fast, table-based decision
Simple way to see it:
• Routing = planning the journey
• Forwarding = taking each step -
Packet Delivery to Destination
• Each packet may take a different path
• Network dynamically handles:
○ Congestion
○ Failures
○ Load balancing
That’s why packets can arrive:
• Out of order
• With delay variations -
Data Reassembly
• At the destination:
○ Packets are reordered
○ Missing packets may be requested again
• Final data is reconstructed exactly as sent
User sees a seamless message, even though internally it was fragmented
ANALOGY
Think of sending a book to a friend:
• You split the book into multiple pages (packets)
• Each page is sent via different courier routes
• Some pages arrive early, some late
• Receiver collects all pages and reassembles the book
If one page is missing → request resend
That’s exactly how the internet works.
TAKEAWAY
• Data doesn’t travel as one piece → it flows as packets across multiple paths
• Networks work by:Break → Send → Route → Rebuild
Stage 1: Why Networks Exist → “Birth of Communication Networks”
Track: Foundations
Part 3