0% found this document useful (0 votes)
2 views16 pages

Unit 3 Computer Networks

Uploaded by

Anurag kharvind
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views16 pages

Unit 3 Computer Networks

Uploaded by

Anurag kharvind
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Gemini Pro

give very very very highly detailed explaination of topics i


give to you Unit-III MAC Sub layer: MAC Addressing, Binary
Exponential Back-off (BEB) Algorithm

Here is a highly detailed, comprehensive breakdown of the MAC Sublayer, focusing heavily on
MAC Addressing and the Binary Exponential Back-off (BEB) Algorithm.

The MAC Sublayer: An Overview


The Medium Access Control (MAC) sublayer is the lower half of the Data Link Layer (Layer 2) in
the OSI model, sitting directly above the Physical Layer. In any network where multiple devices
share a single communication medium (like an Ethernet cable or a Wi-Fi channel), there must be a
strict set of rules to determine who gets to transmit data and when.
The primary responsibilities of the MAC sublayer include:
Data Encapsulation: Framing data with headers and trailers before transmission.
Addressing: Identifying the source and destination of frames using physical hardware
addresses.
Channel Access Control: Managing how devices share the physical medium to prevent or
resolve collisions.

MAC Addressing
A MAC address (Media Access Control address) is a unique, hardware-level identifier assigned to
a Network Interface Controller (NIC) for use as a network address in communications within a
network segment. It is burned into the hardware by the manufacturer, which is why it is often
called a "physical address" or "Burned-In Address" (BIA).

Structure of a MAC Address


A standard MAC address is exactly 48 bits (6 bytes) long. It is typically represented as 12
hexadecimal digits, separated by colons or hyphens (e.g., 00:1A:2B:3C:4D:5E or 00-1A-2B-
3C-4D-5E ).
The 48 bits are divided into two equal halves of 24 bits (3 bytes) each:

Component Size Description

OUI (Organizationally Unique 24 bits Assigned by the IEEE to the


Identifier) hardware manufacturer (e.g.,
Cisco, Intel, Apple). It identifies
the vendor.

NIC / Vendor Assigned 24 bits Assigned by the manufacturer


to the specific device. It acts as
a unique serial number for the
NIC.

Special Bits in the First Octet


When you look at the very first byte (octet) of a MAC address transmitted on the wire, the two
least significant bits carry special meaning:
I/G (Individual/Group) Bit: The 8th bit transmitted (least significant bit of the first byte).
Gemini Pro
0: Indicates an Individual (Unicast) address intended for a single specific device.
1: Indicates a Group (Multicast or Broadcast) address intended for multiple devices.
U/L (Universal/Local) Bit: The 7th bit transmitted.
0: Indicates a Universally administered address (standard, burned-in by the
manufacturer).
1: Indicates a Locally administered address (overridden by a network administrator).

Types of MAC Addresses


1. Unicast MAC Address
A frame sent to a Unicast MAC address is destined for exactly one network interface. The I/G bit
is always set to 0 .
2. Multicast MAC Address
A frame sent to a Multicast MAC address is destined for a specific group of devices that have
subscribed to a multicast group. The I/G bit is always set to 1 . An example is
01:00:5E:xx:xx:xx , which is specifically reserved for IPv4 multicast traffic.
3. Broadcast MAC Address
A frame sent to a Broadcast MAC address is destined for every single device on the local network
segment. The address is entirely composed of binary 1s, represented in hexadecimal as
FF:FF:FF:FF:FF:FF .

Binary Exponential Back-off (BEB) Algorithm


When multiple devices share a network (like classic Ethernet using a bus topology), two devices
might try to send data at the exact same time. This results in a collision, destroying the data
frames.
To handle this, Ethernet uses a protocol called CSMA/CD (Carrier Sense Multiple Access with
Collision Detection). When a collision is detected, the involved devices must wait before trying to
transmit again. If they both waited the exact same amount of time, they would just collide again.

Binary Exponential Back-off (BEB) is the algorithm used to calculate a random,


exponentially increasing wait time for devices after a collision occurs, drastically
reducing the probability of subsequent collisions.

How the Algorithm Works (Step-by-Step)


When a collision occurs, the sending station detects it, sends a brief "jam signal" to ensure all
other stations know a collision happened, and then halts transmission. The BEB algorithm then
takes over:
Step 1: Count the Collisions
The station maintains a counter, let's call it c, representing the number of consecutive collisions
experienced for the current frame.
Step 2: Determine the Back-off Limit
The algorithm defines an exponent k , which is the lesser of the collision count c or the number 10.
Mathematically, this is expressed as:

k = min(c, 10)

Step 3: Choose a Random Number


The station generates a random integer, let's call it R, from a uniform distribution between 0 and
2k − 1.

R ∈ [0, 2k − 1]
Step 4: Calculate the Wait Time
The station waits for a duration equal to R multiplied by the basic "slot time". The slot time is the
time required to transmit 512 bits (typically 51.2 microseconds on a 10 Mbps Ethernet network).
Gemini Pro

Wait T ime = R × Slot T ime


Step 5: Retransmit or Abort
After waiting, the station attempts to transmit again. If the transmission succeeds, the collision
counter c is reset to 0. If it collides again, c increments by 1. If c reaches a maximum limit of 16,
the algorithm aborts the transmission entirely and reports a failure to the upper network layers.

Highly Detailed BEB Example Scenario


Assume two computers, Device A and Device B, attempt to transmit at the same time on a 10
Mbps Ethernet network.
1st Collision (c = 1):
k = min(1, 10) = 1.
The range for random number R is [0, 21 − 1] → [0, 1].
Device A randomly picks 0. Device B randomly picks 1.
Device A waits 0 × 51.2 μs = 0 μs.
Device B waits 1 × 51.2 μs = 51.2 μs.
Result: Device A transmits successfully. Device B transmits successfully right after.
Collision resolved!
What if they both picked 1? (2nd Collision, c = 2):
k = min(2, 10) = 2.
The range for R expands to [0, 22 − 1] → [0, 3].
Possible wait multipliers are 0, 1, 2, or 3.
The probability of them picking the same number drops from 50% to 25%.
Fast Forward to the 10th Collision (c = 10):
k = min(10, 10) = 10.
The range for R is now [0, 210 − 1] → [0, 1023].
The devices now pick a random multiplier between 0 and 1023. The probability of
another collision is incredibly low.
12th Collision (c = 12):
k = min(12, 10) = 10.
Notice that k freezes at 10. The range for R remains [0, 1023]. This prevents the wait
time from becoming absurdly long (which would cause a massive network timeout).

Advantages and Disadvantages of BEB

Feature Details

Advantage: Efficiency At low network loads, collisions are rare. When they do
occur, the wait window is very small (R = 0 or 1), so
devices get back to transmitting almost instantly
without wasting bandwidth.

Advantage: Adaptability As network traffic gets heavier and collisions become


frequent, the algorithm dynamically stretches the wait
time window, naturally pacing the devices and
preventing network collapse.

Disadvantage: Unfairness The "Capture Effect" can occur. If Node A successfully


transmits, its collision counter resets to 0. If Node B just
Feature
Gemini Pro Details

experienced 5 collisions, its counter is 5. Node A's next


wait range is [0, 1], while Node B's is [0, 31]. Node A
will likely dominate the channel, effectively "capturing"
the network while Node B is forced to wait indefinitely.

Disadvantage: Delay In highly congested networks, reaching higher collision


counts results in significant, unpredictable delays
(jitter), which is detrimental for real-time applications
like voice or video.

Distributed Random Access Schemes/Contention Schemes:


for Data Services (ALOHA and
SlottedALOHA

Here is a detailed breakdown of Distributed Random Access Schemes, focusing specifically on


the foundational protocols: Pure ALOHA and Slotted ALOHA.

Distributed Random Access Schemes (Contention Schemes)


In a network where multiple devices share a single communication channel, there is no central
controller dictating who gets to speak and when. Random Access (or Contention) schemes
operate on a simple principle: devices are distributed, and when a node has data to send, it
simply attempts to transmit.
Because nodes do not coordinate with one another before transmitting, collisions are inevitable
if two or more nodes transmit at the same time. Therefore, contention schemes must define:
1. When a station can transmit.
2. What a station does if its transmission collides with another.

1. Pure ALOHA
Developed in the early 1970s at the University of Hawaii by Norman Abramson, ALOHA was
designed to connect computers across different Hawaiian islands using radio transmissions. It is
the most basic, unrestricted random access protocol.

How it Works
The Golden Rule: "Transmit whenever you have data."
When a station generates a frame, it immediately transmits it over the shared channel.
After sending the frame, the station waits for an acknowledgment (ACK) from the receiver.
If the ACK arrives within a specific timeout period, the transmission was successful.
If no ACK arrives (indicating the frame collided with another transmission and was
corrupted), the station waits for a random amount of time (using an algorithm like Binary
Exponential Back-off) and retransmits the frame.

The Problem: Vulnerable Time


A collision occurs if the transmission times of any two frames overlap, even by a single bit. To find
the probability of a successful transmission, we must calculate the Vulnerable Time—the length
of time in which a collision can occur.
Let Tf be the time it takes to transmit one standard frame.

For a frame starting transmission at time t, it will finish at time t + Tf .



If another station started transmitting before t (as early as t − Tf ), the tail end of its frame
Gemini Pro

will collide with the start of our frame.


If another station starts transmitting after t (up until t + Tf ), the start of its frame will

collide with the tail end of our frame.

Therefore, the vulnerable time for Pure ALOHA is 2 × Tf . ​

Performance and Throughput


To analyze performance, network engineers use the variable G, representing the average
number of frames generated by the network during one frame transmission time (Tf ). ​

Assuming frame arrivals follow a Poisson distribution, the probability of successful transmission
(Throughput, S ) for Pure ALOHA is given by the formula:

S = G × e−2G

Maximum Efficiency: By taking the derivative of this equation and setting it to zero, we find
that maximum throughput occurs when G = 0.5.
Maximum Throughput: Smax = 0.5 × e−1 ≈ 0.184.

This means Pure ALOHA has a maximum efficiency of only 18.4%. The other 81.6% of the
channel capacity is wasted on collisions and empty idle time.

2. Slotted ALOHA
In 1972, Lawrence Roberts introduced Slotted ALOHA to double the capacity of the original
protocol by introducing a simple rule: synchronized time.

How it Works
Time on the channel is divided into uniform, discrete intervals called slots.
The duration of one slot is exactly equal to the transmission time of one frame (Tf ). ​

The Rule: A station is only allowed to begin transmitting at the exact beginning of a time slot.
If a station generates a frame in the middle of a slot, it must hold that frame in a buffer and
wait until the clock ticks to the start of the next slot.

The Improvement: Reduced Vulnerable Time


Because transmissions can only begin at slot boundaries, the "partial overlap" collisions of Pure
ALOHA are entirely eliminated.
If a station begins transmitting at the start of a slot, a collision will only occur if another station
also chooses to transmit at the exact start of that same slot. Therefore, the vulnerable time is
reduced from 2 × Tf down to just Tf .

Performance and Throughput


Because the vulnerable time is cut in half, the throughput formula for Slotted ALOHA removes the
multiplier of 2 from the exponent:

S = G × e−G

Maximum Efficiency: Maximum throughput occurs when the network load is exactly one
frame per slot time (G = 1).
Maximum Throughput: Smax = 1 × e−1 ≈ 0.368.

This means Slotted ALOHA has a maximum efficiency of 36.8%, exactly double that of Pure
ALOHA.

Quick Comparison Summary


Gemini Pro
Feature Pure ALOHA Slotted ALOHA

Transmission Rule Send immediately upon Wait for the beginning of the next
arrival. time slot.

Time Structure Continuous. Discrete intervals (synchronized).

Vulnerable Time 2 × Tf ​ 1 × Tf ​

Max Efficiency ~18.4% ~36.8%

Ideal Network Load (G 0.5 frames per interval 1.0 frames per interval
)

Hardware Complexity Low (no synchronization Higher (requires a master clock or


needed). timing synchronization).

Interactive visual ready

Now that you have a detailed grasp of ALOHA protocols, would you like to explore how CSMA
(Carrier Sense Multiple Access) improves upon this by making stations "listen" to the channel
before they transmit?

for Local-Area Networks (CSMA, CSMA/CD, CSMA/CA)

To resolve the massive inefficiency of the blind transmissions in ALOHA, networking protocols
evolved to include a "listen before talk" mechanism. This is the foundation of Carrier Sense
Multiple Access (CSMA) and its two dominant variants: CSMA/CD (used in wired Ethernet) and
CSMA/CA (used in wireless Wi-Fi).
Here is a highly detailed breakdown of how these distributed random access schemes operate in
Local-Area Networks (LANs).

1. CSMA: The Base Protocol (Listen Before Talk)


Carrier Sense Multiple Access (CSMA) introduces a fundamental rule: a station must
continuously monitor (sense) the physical medium (the cable or wireless frequency) before
attempting to send data.
By listening first, a station can avoid transmitting if someone else is already talking. This drastic
reduction in collisions means the only time a collision can occur is during the Vulnerable Time,
which in CSMA is strictly equal to the propagation delay (tprop ). This is the time it takes for an

electrical or radio signal to travel from one end of the network to the other. If Station A starts
talking, Station B might also start talking a microsecond later because Station A's signal hasn't
physically reached Station B yet.

Persistence Strategies (Handling a Busy Channel)


When a station listens and finds the channel is already busy, it must decide what to do next.
CSMA defines three behavioral strategies:
1-Persistent: The station continuously monitors the busy channel. The absolute microsecond
Gemini Pro
the channel becomes idle, it transmits its frame with a 100% probability (hence, 1-persistent).
Flaw: If two stations are waiting for a third station to finish talking, they will both transmit
immediately when the channel clears, guaranteeing a collision.
Non-Persistent: The station listens. If the channel is busy, it stops listening, waits a random
amount of time, and then checks again.
Flaw: It reduces collisions but introduces unnecessary delay (latency). The channel might
sit idle while the station is in its random waiting period.
p-Persistent: Used in slotted time channels. The station listens continuously. When the
channel becomes idle, it transmits with a probability of p. With a probability of 1 − p, it
defers its transmission to the next time slot.

2. CSMA/CD (Collision Detection)


Where it is used: Classic Wired Ethernet (IEEE 802.3).
While CSMA reduces collisions, it does not eliminate them entirely. In standard CSMA, if two
frames collide, the transmitting stations keep pumping out the rest of their corrupted frames,
wasting valuable bandwidth. CSMA/CD solves this by enforcing a "listen while talking" rule.

How CSMA/CD Works


1. Carrier Sense: The station listens to the wire. If idle, it begins transmitting.
2. Collision Detection: As it transmits, the station's hardware actively monitors the voltage
levels on the wire. A collision causes an energy spike (an overvoltage) on the copper cable.
3. Abort and Jam: The microsecond a station detects this overvoltage, it immediately halts
data transmission. It then transmits a brief, 32-bit Jam Signal to ensure every other node on
the network is definitively aware that a collision occurred.
4. Back-off: The station invokes the Binary Exponential Back-off (BEB) algorithm (explained in
the previous response) to wait a random amount of time before trying again.

The Critical Requirement: Minimum Frame Size


For CSMA/CD to work, a station must be able to detect a collision before it finishes sending its
frame. If it finishes sending the frame and then the collision signal arrives, the station will assume
its transmission was successful.
To guarantee detection, the time it takes to transmit the frame must be greater than or equal to
the Round-Trip Time (RTT) of the network. This creates a hard mathematical requirement for a
Minimum Frame Size.

T ransmission T ime ≥ 2 × P ropagation Delay

L d
≥2×
​ ​

R v
Where:
L = Length of the frame in bits
R = Bandwidth (Data Rate) in bits per second
d = Maximum distance between the two furthest nodes in meters
v = Speed of the signal in the medium (usually ≈ 2 × 108 m/s)
If a standard data payload is too small to meet this requirement, the network interface card will
add meaningless "padding" bits to artificially inflate the frame size to the minimum requirement
(64 bytes in standard 10 Mbps Ethernet).
Gemini Pro
Interactive visual ready

3. CSMA/CA (Collision Avoidance)


Where it is used: Wireless Networks / Wi-Fi (IEEE 802.11).
You cannot use Collision Detection (CD) in a wireless network for two massive physical reasons:
1. Hardware Limitations: Wireless transceivers are generally half-duplex. The power required
to broadcast a radio signal is vastly stronger than the sensitive receiver needed to listen. If a
Wi-Fi antenna tries to "listen while talking," it will only hear its own deafening transmission.
2. The Hidden Terminal Problem: Node A and Node C can both reach the central Router
(Node B), but a physical wall prevents Node A and Node C from hearing each other. Node A
listens, hears nothing, and transmits to B. Node C listens, hears nothing, and transmits to B.
The signals collide at the router, but neither A nor C detected it.

Because Wi-Fi cannot detect collisions, it must actively avoid them.

How CSMA/CA Works


CSMA/CA relies on a complex sequence of waiting periods and explicit acknowledgments.
1. DIFS (Distributed Interframe Space): When a station wants to transmit, it listens to the
channel. Even if the channel is idle, the station is not allowed to transmit immediately. It
must wait a mandatory, fixed period called the DIFS.
2. Contention Window (Random Back-off): After the DIFS expires, the station still does not
transmit. It selects a random back-off time (a number of time slots). It counts down these
slots. If the channel becomes busy during the countdown, the timer pauses and resumes
only after the channel is idle again (and another DIFS passes).
3. Transmission: When the back-off timer reaches zero, the station transmits the entire frame.
4. SIFS (Short Interframe Space) and ACK: Because the sender cannot detect a collision, it
assumes the frame was destroyed unless told otherwise. The receiving station waits a very
short period (SIFS) and then transmits a dedicated Acknowledgment (ACK) frame.
5. Retransmission: If the sender does not receive that ACK before a timeout period expires, it
assumes a collision occurred, doubles its contention window (Binary Exponential Back-off),
and starts the entire process over.

Solving the Hidden Terminal: RTS/CTS


To specifically combat the hidden terminal problem, CSMA/CA can optionally use a reservation
handshake called RTS/CTS (Request to Send / Clear to Send).
Before sending a massive data frame, Node A sends a tiny RTS frame to the Router. The RTS
contains the duration of the upcoming transmission.
The Router replies with a CTS frame, broadcasted to everyone.
Node C (who couldn't hear Node A, but can hear the Router) receives the CTS. The CTS
effectively says, "The channel is reserved for Node A for the next 50 milliseconds."
Node C updates its internal NAV (Network Collision Free
Allocation Vector) timer and goes to sleep for 50
milliseconds, ensuring a collision-free transmission for [Link], BRAP, Binary Count Down
Protocols: Basic

While Random Access (Contention) schemes like CSMA/CD and ALOHA are highly effective under
light traffic, their performance collapses under heavy network loads due to continuous collisions.
To solve this, networks can use Collision-Free Protocols (also known as Controlled Access
protocols). In these schemes, collisions are mathematically eliminated because stations follow
strict coordination rules to determine exactly whose turn it is to transmit. The trade-off is a slight
increase in overhead and base latency, but they guarantee a maximum throughput of 100%
Geminioverhead)
(minus Pro even under massive congestion.
Here is a highly detailed breakdown of the three foundational collision-free protocols.

1. Basic Bit-Map Protocol (Reservation Protocol)


The Basic Bit-Map protocol works by completely separating the network's time into two distinct
phases: a Contention (Reservation) Period and a Transmission Period.

How it Works
1. The Setup: Imagine a network with exactly N stations, numbered 0 to N − 1.
2. The Contention Period: The protocol begins with a sequence of N tiny time slots. Each slot
corresponds to one specific station.
Slot 0 belongs to Station 0.
Slot 1 belongs to Station 1, and so on.
3. Making a Reservation: If a station has data to send, it waits for its specific time slot and
transmits a 1 bit. If it has nothing to send, it remains silent (effectively transmitting a 0 ).
4. The Transmission Period: After the N tiny slots have passed, every station on the network
has heard the exact same N -bit sequence (the "Bit-Map"). Everyone now knows exactly who
wants to transmit and in what order. The stations that transmitted a 1 will now transmit
their full data frames in their numerical order.

Performance Analysis
Advantage: Collisions are completely impossible. Every station agrees on the transmission
queue.
Overhead at Low Load: If only Station 99 out of 100 wants to send data, the network must
still waste 100 tiny slots just to figure that out.
Overhead at High Load: If all N stations want to transmit, the N -bit overhead is spread
across N data frames. The overhead per frame drops to just 1 bit, making it incredibly
efficient under heavy load.

2. BRAP (Broadcast Recognition Access Method)


BRAP is an elegant evolution of the Basic Bit-Map protocol. It is sometimes called the Implicit
Reservation protocol because it eliminates the need for a dedicated, separate N -bit reservation
phase before data can be sent.

How it Works
Instead of reserving slots in advance, BRAP interleaves the "mini-slots" directly with the data
transmissions by using idle timers.
1. The Round Robin Sequence: The protocol relies on stations continuously listening to the
channel (Carrier Sense).
2. The Turn Timer: After a successful data transmission ends, the channel goes idle. Station 0
knows it has the right to transmit first. If it has data, it begins transmitting immediately.
3. Passing the Baton: If Station 0 does not have data, it stays silent. Station 1 waits for exactly
one mini-slot duration of idle time. If the channel is still idle after that one mini-slot, Station 1
knows Station 0 passed its turn. Station 1 can now transmit.
4. Continuous Flow: If Station 1 also has no data, Station 2 waits for two idle mini-slots, then
transmits.

Performance Analysis
Advantage: There is no centralized bit-map to broadcast. Stations independently count the
duration of idle time to know when it is their turn.
Disadvantage: It is heavily dependent on precise network synchronization and stable
Gemini Pro
propagation delays. If propagation delay exceeds the mini-slot duration, a station might
incorrectly assume an earlier station skipped its turn, causing a collision.

3. Binary Count Down Protocol


The biggest flaw of the Basic Bit-Map protocol is that the overhead scales linearly with the
number of stations (N ). If you have 1024 stations, you need 1024 reservation bits per cycle.
Binary Count Down solves this by compressing the overhead to log2 (N ) bits.

The Core Mechanism


Every station is assigned a unique binary address of equal length. For example, in a 16-station
network, addresses range from 0000 to 1111 (4 bits).
The physical network channel must act as a Boolean OR gate. If one station transmits a 0
(low voltage) and another transmits a 1 (high voltage) simultaneously, the resulting signal
heard on the wire is a 1 .

How it Works
1. The Broadcast: When multiple stations want to transmit data, they simultaneously begin
broadcasting their binary addresses onto the channel, starting with the Most Significant Bit
(MSB).
2. The OR Logic: After transmitting a bit, a station instantly listens to the channel to see the
Boolean OR result.
3. The Drop-Out Rule: If a station transmits a 0 , but hears a 1 on the channel, it instantly
realizes that another competing station has a higher address. The station transmitting the
0 immediately drops out of the competition and stops sending further bits.
4. The Winner: By the time the final (Least Significant) bit is transmitted, all lower-addressed
stations will have dropped out. The station with the highest binary address is left standing
and immediately begins transmitting its data frame.

Performance Analysis
Efficiency: For 1024 stations, the contention overhead is reduced from 1024 bits down to
just 10 bits (log2 1024).

Unfairness: The protocol inherently favors stations with higher numerical addresses. Station
1111 will always beat Station 0000 . To fix this, modern implementations often dynamically
rotate addresses after a successful transmission.

Interactive visual ready

Now that we have covered Contention and Collision-Free protocols, would you like to explore
Limited-Contention Protocols (like the Adaptive Tree Walk), which attempt to combine the best
features of both approaches dynamically based on network load?
, MLMA Limited Contention Protocols:
Adaptive Tree Walk, Performance Measuring Metrics .

Here is a highly detailed, comprehensive breakdown of Limited-Contention Protocols, the


Adaptive Tree Walk mechanism, and the critical metrics used to evaluate MAC layer performance.

1. The Need for Limited-Contention Protocols


To understand why these protocols exist, we must look at the two extremes of MAC sublayer
protocols:
1. Contention Protocols (e.g., CSMA, ALOHA): These allow any station to transmit when
Gemini Pro
ready.
Advantage: Near-zero delay under light network loads.
Disadvantage: Catastrophic performance collapse under heavy loads due to continuous
collisions.
2. Collision-Free Protocols (e.g., Basic Bit-Map): These force stations to make reservations or
wait for their precise turn.
Advantage: 100% channel efficiency under heavy loads (no collisions).
Disadvantage: Massive delays and wasted overhead under light loads (waiting for
hundreds of empty reservation slots to pass).

Limited-Contention Protocols dynamically combine the best features of both. They behave like
contention protocols when the network load is light, and they automatically transition to
behaving like collision-free reservation protocols when the load becomes heavy.

2. MLMA (Multi-Level Multi-Access) Protocol


The core problem with the Basic Bit-Map or BRAP protocols is that the reservation overhead
scales linearly with the number of stations (N ). If a network has 1,000 stations, you must wait for
1,000 mini-slots to pass just to figure out who wants to transmit.
MLMA solves this by using a hierarchical, multi-level reservation system (often base-10) to
drastically reduce the number of required slots.

How it Works
Instead of a single line of N slots, MLMA groups stations by their identification numbers. Imagine
a network with 1,000 stations numbered 000 to 999 . MLMA uses three "levels" (Hundreds,
Tens, Units), each containing exactly 10 slots (0 through 9).
1. Level 1 (The Hundreds Digit): The contention period opens with 10 mini-slots. If Station
452 and Station 489 want to transmit, they both transmit a 1 during slot 4 . The
network now knows that some station in the 400s wants to speak.
2. Level 2 (The Tens Digit): The network focuses on the 400s. A new set of 10 slots begins.
Station 452 transmits a 1 in slot 5 . Station 489 transmits a 1 in slot 8 .
3. Level 3 (The Units Digit): The network focuses on the 450s. Station 452 transmits in slot
2 . It is now uniquely identified and transmits its data frame. The network then resolves the
480s to allow Station 489 to transmit.

Performance
By using a base-10 MLMA, a 1,000-station network reduces its reservation phase from 1000 bits
down to a maximum of 30 bits (3 levels × 10 slots). This significantly lowers delay during light
loads while maintaining collision-free data transmission.

3. The Adaptive Tree Walk Protocol


Also known as the Capetanakis Tree Algorithm, the Adaptive Tree Walk protocol is the most
famous limited-contention scheme. It organizes all stations into a logical binary tree hierarchy.

The Structure
Leaf Nodes: Every individual station on the network is assigned to a leaf node at the bottom
of the tree.
Internal Nodes: These represent "groups" of stations. A parent node represents all the
stations in its left and right subtrees combined.
The Root Node: Represents every single station on the network simultaneously.

The Algorithm (Depth-First Search Resolution)


The protocol resolves channel access using a time-slotted system and a recursive Depth-First
Gemini Pro
Search.
1. Initial State (Slot 0): The protocol starts at the root node. All stations are permitted to
transmit.
2. Zero or One Station: If the channel is idle, or if exactly one station transmits, it is a success.
The cycle ends immediately.
3. Collision Handling: If two or more stations transmit in Slot 0, a collision occurs. The protocol
immediately splits the network in half.
4. Left Subtree (Slot 1): Only stations in the left half of the tree are permitted to transmit.
If another collision occurs, the left half is split in half again, and we query the left-most
quarter in Slot 2.
If it is a success or idle, the protocol moves on to query the right half.

Load Adaptation (The "Adaptive" Part)


Under a very heavy network load, starting at the root node (allowing everyone to transmit)
guarantees a massive collision. It is a wasted time slot.
The protocol is "adaptive" because stations monitor the network to estimate the number of ready
stations, which we will call q . If q is large, the protocol skips the top of the tree entirely.
The optimal level (i) to begin the tree search is the level where the expected number of ready
stations under any given node is exactly 1.
Mathematically, this is expressed as:

i = log2 (q)

(Where i is the depth level of the tree, with the root being level 0). By starting the search at level i,
the protocol avoids guaranteed collisions at the top of the tree, seamlessly shifting into a
structured polling mechanism.

Interactive visual ready

4. Performance Measuring Metrics for MAC Layers


When network engineers design or evaluate a MAC protocol (whether it is Wi-Fi, Ethernet, or
cellular), they measure its effectiveness using several rigid mathematical metrics.

1. Throughput (S )
Throughput is the ultimate measure of success. It is the fraction of the total channel capacity that
carries useful, successfully delivered data payloads.
It specifically excludes time wasted on collisions, idle waiting, retransmissions, and protocol
overhead (like headers and preambles).
For example, standard Slotted ALOHA has a maximum theoretical throughput (Smax ) of ​

about 36.8%, meaning 63.2% of the channel's capacity is permanently lost to collisions and
empty slots.

2. Network Load (G)


Load represents the total traffic offered to the network by all stations combined during a specific
time interval.
It includes successful new frames, but it also includes all the frames that are being
retransmitted due to previous collisions.
If G > 1, it means the network is generating more data than the physical channel can
transmit, guaranteeing a bottleneck and increasing collisions.
[Link]
DelayPro
/ Latency (D)
Delay measures the exact amount of time that elapses from the microsecond a data frame is
generated at the source to the microsecond it is successfully received at the destination. It is the
sum of:
Queuing Delay: Time spent waiting inside the NIC's buffer.
Access/Contention Delay: Time spent executing back-off algorithms, waiting for
reservations, or recovering from collisions.
Transmission Delay: The time required to push all the bits of the frame onto the wire (Frame
Size / Bandwidth).
Propagation Delay: The physical time it takes the signal to travel through the copper, fiber,
or air to the destination.

4. Channel Efficiency (U )
Efficiency looks at the network from the perspective of time. It is the ratio of time the channel
spends successfully transmitting data versus the time it spends in "wasted" states (collisions or
idle time).
Collision-Free protocols approach 100% efficiency under heavy load. Contention protocols
drop in efficiency as load increases.

5. Fairness
1
A protocol is considered "fair" if N active nodes each receive exactly N ​ of the channel's
throughput over time.
The Capture Effect: This is a metric failure common in CSMA/CD. If Station A successfully
transmits, its back-off timer resets to 0. If Station B has collided 5 times, its back-off timer is
huge. Station A will likely "capture" the channel and transmit continuously, starving Station B.

6. Overhead Ratio
This measures the "tax" paid to use the protocol. It is the ratio of non-payload bits to payload bits.
High overhead reduces overall throughput.
Static Overhead: MAC addresses, CRC error-checking bits, and synchronization preambles
attached to every frame.
Dynamic Overhead: The mini-slots used in BRAP or Bit-Map protocols to secure reservations
before data can be sent.
IEEE Standards 802 series & their variant

The IEEE 802 LAN/MAN Standards Committee develops and maintains networking standards for
local area networks (LANs) and metropolitan area networks (MANs).
In the context of the OSI model, the 802 family strictly operates within the bottom two layers: the
Physical Layer (Layer 1) and the Data Link Layer (Layer 2). Crucially, IEEE 802 splits the Data Link
Layer into two distinct sublayers:
1. Logical Link Control (LLC): Standardized across all networks by IEEE 802.2.
2. Media Access Control (MAC): Varies depending on the physical medium (e.g., Ethernet vs.
Wi-Fi).

Here is a comprehensive breakdown of the most important IEEE 802 working groups and their
critical variants.

1. IEEE 802.3: Ethernet (Wired LANs)


IEEE 802.3 defines the physical and MAC sublayer specifications for wired Ethernet. It is the
dominant standard for wired LANs worldwide, utilizing CSMA/CD (in older half-duplex setups) and
full-duplex switches in modern iterations.
Key Variants of 802.3
Gemini Pro
Standard Common Name Speed Typical Cable

802.3 Standard Ethernet 10 Mbps Coaxial (Thick


Twisted Pair

802.3u Fast Ethernet 100 Mbps Cat5 Copper


(100BASE-TX)

802.3z Gigabit Ethernet 1 Gbps Optical Fiber


(Fiber) (1000BASE-X)

802.3ab Gigabit Ethernet 1 Gbps Cat5e/Cat6 Co


(Copper) (1000BASE-T)

802.3ae 10 Gigabit Ethernet 10 Gbps Fiber (10GBAS

802.3an 10 Gigabit Ethernet 10 Gbps Cat6a Copper


(Copper) (10GBASE-T)

802.3ba 40 / 100 Gigabit 40/100 Gbps Fiber


Ethernet

802.3af / at / bt Power over Ethernet N/A Delivers DC el


(PoE) power over da

2. IEEE 802.11: Wireless LANs (Wi-Fi)


IEEE 802.11 defines the standards for wireless local area networks. Because wireless media cannot
detect collisions effectively, this standard relies on the CSMA/CA (Carrier Sense Multiple Access
with Collision Avoidance) protocol.

Key Variants of 802.11 (The Wi-Fi Generations)

Standard Wi-Fi Gen Name Release Frequencies

802.11b Wi-Fi 1 1999 2.4 GHz

802.11a Wi-Fi 2 1999 5 GHz

802.11g Wi-Fi 3 2003 2.4 GHz

802.11n Wi-Fi 4 2009 2.4 / 5 GHz


Standard
Gemini Pro Wi-Fi Gen Name Release Frequencies

802.11ac Wi-Fi 5 2014 5 GHz

802.11ax Wi-Fi 6 / 6E 2019 / 2020 2.4 / 5 / 6 GHz

802.11be Wi-Fi 7 2024 2.4 / 5 / 6 GHz

3. IEEE 802.15: Wireless Personal Area Networks (WPAN)


While 802.11 covers buildings or campuses, 802.15 focuses on short-range communications
(typically within 10 meters) with low power consumption.
802.15.1 (Bluetooth): The original standard defining the lower layers of Bluetooth technology
(MAC and Physical layers). Note: The Bluetooth Special Interest Group (SIG) now primarily
manages Bluetooth.
802.15.4 (Zigbee / Thread): Designed for low-data-rate, very low-power applications. It is the
foundational standard for modern IoT (Internet of Things) mesh networks and smart home
devices.

4. Architecture and Logical Link Control


These standards act as the "glue" that allows the higher layers (like IP) to interface seamlessly with
the hardware variants listed above.
IEEE 802.1 (Bridging and Architecture): Defines the overall architecture of LANs.
802.1D: Spanning Tree Protocol (STP) to prevent looping in network switches.
802.1Q: Virtual LANs (VLANs), allowing network administrators to logically segment a
physical network.
802.1X: Port-based Network Access Control (Security/Authentication).
IEEE 802.2 (Logical Link Control - LLC): The upper sublayer of the Data Link Layer. It
provides a uniform interface to the Network Layer (IP), hiding the differences between
Ethernet, Wi-Fi, and Token Ring from the routing protocols above it.

5. Historical / Legacy Standards


For academic and historical completeness, it is important to recognize standards that were once
prominent but have since been entirely eclipsed by Ethernet.
IEEE 802.4 (Token Bus): A physical bus topology that used a logical token-passing
mechanism to dictate who could transmit. Extensively used in manufacturing and factory
automation (MAP protocols) before Ethernet became fast and reliable enough for industrial
use.
IEEE 802.5 (Token Ring): Developed by IBM, this used a physical star but a logical ring
topology. A "token" circulated the ring, and a station could only transmit data if it captured
the free token. It offered excellent collision-free performance under heavy loads but lost to
the cheaper, simpler Ethernet infrastructure.

Powered by Gemini All Chat Downloader


IEEE 802.16 (WiMAX): Broadband Wireless Access. It was intended to provide wireless
Gemini Pro
metropolitan area coverage (bridging the gap between Wi-Fi and cellular networks) but was
ultimately superseded by LTE/4G cellular technologies.

You might also like