The Network Core
The Network Core
How it works: Each packet is forwarded from one router to the next
along a path, making its way from the source to the destination. The
transmission occurs at the full capacity of each link between routers.
For example, if L = 7.5 Mbits (megabits) and R = 1.5 Mbps (megabits per
second), it takes 5 seconds to send one packet over one hop (a single
step between routers).
End-to-End Delay: The total delay for a packet traveling from the source to
the destination is 2L/R (this assumes zero propagation delay, which is the
time it takes for a signal to travel through the physical medium).
Example: In the image, the link between two routers has a transmission
rate of 1.5 Mb/s (megabits per second), but the incoming data rate from
source A is 100 Mb/s. This creates a bottleneck, causing packets to
queue up.
Packet Loss: If the queue (buffer) becomes full, additional packets are
dropped and lost. This happens if the arrival rate of packets exceeds the
transmission rate for a significant period.
Routing is the process that determines the path or route a packet (small
chunk of data) takes from the source to the destination.
This involves using routing algorithms, which calculate the best path to
the destination.
Think of it like a GPS deciding the best way to get from one city to
another.
2. Forwarding:
5. Circuit Switching
1. Circuit Switching:
It’s like each user having their own lane on a highway and driving at the
same time without interfering with each other.
In TDM, different users take turns using the same frequency, but they
are allocated distinct time slots.
Think of it like taking turns to use a single-lane road: each user has the
road for a specific amount of time before the next user gets their turn.
1. Circuit Switching:
You have a 1 Mbps link (1 megabit per second), and each user requires 100
kbps (kilobits per second) when active.
In circuit switching, only 10 users can use the network (since 1 Mbps = 1000
kbps, and 1000 kbps / 100 kbps = 10 users).
How it works: Data is broken into smaller chunks called packets, and each
packet is sent independently through the network. The packets can take
different routes to reach their destination.
Analogy: It's like sending individual letters (packets) instead of making a phone
call. Each letter takes its own path, and the communication line isn't reserved
for just one user.
In packet switching, the link can support more than 10 users because users are
active only 10% of the time.
The slide says that with 35 users, the chance of having more than 10 users
active at the same time is very low (less than 0.0004 or 0.04%).
Key Point:
Packet switching allows more users to share the network than circuit switching,
making it more efficient in many cases.
What happens if there are more than 35 users? If there are more users, the
probability of multiple users being active at the same time increases, which
could lead to congestion or delays.
Great for bursty data: Many applications (like web browsing or emails) don't
need constant data transmission. Packet switching is ideal for these "bursty"
data transfers, where data is sent in short bursts rather than a continuous
stream.
Resource sharing: Since packets are sent individually and not in a dedicated
line, more users can share the same network resources.
Congestion can happen: If too many users are sending data at the same time,
packets can get delayed or even lost. This means that additional protocols
(rules) are needed to ensure data is transferred reliably, and congestion is
managed.
For applications that need continuous data streams (like video calls or audio
streaming), we need to ensure a guaranteed amount of bandwidth. Achieving
this using packet switching is an ongoing challenge.
End systems: These are the devices that people use to connect to the Internet,
such as your phone, laptop, or computer.
ISPs themselves need to be connected so that data can flow between any two
devices on the Internet, even if they are on different networks.
The Internet is not just one big network; it's a network of networks. This
structure has evolved due to various factors, including economics (costs of
infrastructure) and national policies (how different countries manage their
networks).
Key Insight: The image explains that connecting every ISP to every other ISP is
inefficient because it results in too many connections. The complexity of this
approach scales quadratically, denoted as O(N²), where N is the number of
access ISPs. This is impractical as the number of ISPs grows.
Key Insight: This approach simplifies the network architecture, reducing the
number of required connections by centralizing the traffic through a few global
ISPs, making the system more scalable and efficient.
Peering Link: This is the direct connection between ISPs through IXPs, allowing
data traffic to be exchanged.
The overall structure shows a more complex network where access networks
connect to ISPs, and ISPs are interconnected via IXPs, with regional networks
providing additional routing capabilities.
Regional ISPs: These smaller ISPs connect to Tier-1 ISPs and serve more
localized areas, often connecting through IXPs.
Access ISPs: These are the ISPs that serve the end-users directly, providing
home or business internet service.
Key Points:
Tier-1 ISPs form the backbone of the internet, connecting with each other
globally.
Content providers (like Google) have their own networks to deliver content
closer to the users.
Regional ISPs and Access ISPs connect local users to the internet via larger
ISPs.
IXPs are important hubs where traffic is exchanged between different
networks.
This model ensures a scalable and robust global internet, where various players
collaborate to route data efficiently.
Summary
1. Access Network (Local Connection to ISP)
Your traffic goes from your device (via Wi-Fi or Ethernet) to your
modem/router, which is connected to the ISP’s access network.
If your ISP is small, your request might travel through a regional network
before reaching larger infrastructure. If your ISP is large enough, it might skip
this step and go straight to an Internet Exchange Point (IXP) or connect with
other ISPs directly.
If the destination isn’t peered directly, your ISP will send the traffic to the
internet backbone or another ISP via transit agreements.
Peering with Other ISPs: If the content isn’t hosted by a large company or
CDN, your traffic may need to be routed through another ISP to reach its
destination. This happens if the destination is not peered with your ISP. At
the IXP, your ISP can exchange traffic with another ISP, and your request
will be forwarded through that ISP’s network to its final destination.
CDN Servers are often located near IXPs or inside your ISP’s data centers,
reducing the distance that the data has to travel. This results in faster load
times and smoother experiences for things like video streaming or web
browsing.
The CDN delivers the requested content directly from these nearby servers,
bypassing the need to send your traffic across long distances.
At the IXP, your ISP can hand off your traffic to another ISP that is directly
connected to the destination. This process repeats if needed, with the data
hopping between ISPs until it reaches the final server hosting the content.
5. Final Destination Server (Hosted by the smaller website’s server, maybe far
away).
Summary:
Access Network: Connects you (the end user) to your ISP.
ISP Core Network: Routes your traffic within the ISP’s infrastructure.
IXP: An exchange point where ISPs and networks meet to directly exchange
traffic. At this point, if you’re accessing a large content provider (like
Google), it might connect you directly to a nearby CDN server.
Other ISPs: If the content isn’t directly connected at the IXP or available via
CDN, your ISP hands off the traffic to another ISP to reach the final
destination.
So, yes, in most cases, if you're accessing large, common content (like
YouTube or Netflix), your traffic goes from ISP → IXP → CDN. If it's not from a
large provider, it may go from ISP → IXP → another ISP, continuing the journey
across the global internet until it reaches the server you’re accessing.