0% found this document useful (0 votes)
38 views4 pages

Collision-Free Protocols in Networking

Collision-free protocols are designed to prevent collisions from occurring when multiple stations try to transmit data simultaneously over a shared channel. They use techniques like CSMA/CD and CSMA/CA to ensure the transmission channel is acquired by only one station at a time, eliminating the possibility of collisions during data transmission. However, collisions can still theoretically occur during the contention period if more than one station starts transmitting at the same time while competing for access. Collision-free protocols aim to resolve this by preventing collisions even in the contention period.

Uploaded by

Deepti Singh
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)
38 views4 pages

Collision-Free Protocols in Networking

Collision-free protocols are designed to prevent collisions from occurring when multiple stations try to transmit data simultaneously over a shared channel. They use techniques like CSMA/CD and CSMA/CA to ensure the transmission channel is acquired by only one station at a time, eliminating the possibility of collisions during data transmission. However, collisions can still theoretically occur during the contention period if more than one station starts transmitting at the same time while competing for access. Collision-free protocols aim to resolve this by preventing collisions even in the contention period.

Uploaded by

Deepti Singh
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

Collision-Free Protocols

• In computer networks, when more than one station tries to transmit


simultaneously via a shared channel, the transmitted data is garbled. This event
is called collision.
• The Medium Access Control (MAC) layer of the OSI model is responsible for
handling collision of frames.
• Collision – free protocols are devised so that collisions do not occur. Protocols like
CSMA/CD and CSMA/CA nullifies the possibility of collisions once the transmission
channel is acquired by any station.
• However, collision can still occur during the contention period if more than one
stations starts to transmit at the same time.
• Collision – free protocols resolves collision in the contention period and so the
possibilities of collisions are eliminated.
What is MLMA protocol?
Multi-Level Multi-Access (MLMA): The problem with BRAP is the delay
when the channel is lightly loaded. When there is no frame to be
transmitted, the N-bit headers just go on and on until a station inserts a
1 into its mini slot. On average, the waiting time would be N=2. MLAM
scheme [41] is nearly as efficient under high channel load, but has
shorter delay under low channel load. In MLAM, a station wants to
transmit a frame sends its identification in a particular format. A group of
10 bits (called decade) is used to represent a digit of the station number
[48].

What are IEEE 802 wireless standards?


• IEEE 802 is a collection of networking standards that cover the physical and
data link layer specifications for technologies such as Ethernet and wireless.
The user layer in IEEE 802 is serviced by the two layers- the data link layer and
the physical layer.

• These specifications apply to local area networks (LANs) and metropolitan


area networks (MANs). IEEE standards 802 are used for controlling the
Local Area Network and Metropolitan Area Network.

• Essentially, the IEEE 802 standards help make sure internet services and
technologies follow a set of recommended practices so that network devices
can all work together smoothly.

• IEEE 802 is divided into different parts that cover the physical and data
link aspects of networking.

• The family of standards is developed and maintained by the Institute of


Electrical and Electronics Engineers (IEEE) 802 LAN/MAN Standards
Committee, also called the LMSC.

The generally uses specifications of IEEE 802 are:


• IEEE 802.3 The IEEE 802.3 standard determines the
CSMA/CD access control protocol. The best known scheme
for controlling a local area network on a bus structure is
carrier sense multiple action with collision
detection(CSMA/CD).
• IEEE 802.4 IEEE 802.4 describes a token bus LAN standards.
In token passing methods, stations connected on a bus are
arranged in a logical ring. In this method only the station
having token(token holder)is being permitted to transmit
frames.
• IEEE 802.5 IEEE 802.5 describes the token ring standards. In
a token ring a special bit pattern, called the token, circulates
around the ring whenever all stations are idle. The sequence
of token is determined by the physical locations of the
stations on the ring.

Let’s see the difference between IEEE 802.3, 802.4 and 802.5 :-

[Link]. IEEE 802.3 IEEE 802.4 IEEE 802.5

Topology used in IEEE Topology used in IEEE


Topology used in IEEE
1. 802.4 is Bus or Tree 802.5 is Ring
802.3 is Bus Topology.
Topology. Topology.

Size of the frame Size of the frame


Frame format in IEEE
format in IEEE 802.3 format in IEEE
2. 802.5 standard is of the
standard is 1572 802.4 standard is
variable size.
bytes. 8202 bytes.

It supports
There is no priority In IEEE 802.5 priorities
3. priorities to
given in this standard. are possible
stations.

Size of the data


Size of the data field is No limit is on the size of
4. field is 0 to 8182
0 to 1500 bytes. the data field.
bytes.
It can handle
Minimum frame It supports both short
5. short minimum
required is 64 bytes. and large frames.
frames.

Efficiency decreases
Throughput &
when speed increases Throughput & efficiency
efficiency at very
6. and throughput is at very high loads are
high loads are
affected by the outstanding.
outstanding.
collision.

Modems are
Modems are not Like IEEE 802.4, modems
7. required in this
required. are also required in it.
standard.

Protocol is
Protocol is very Protocol is moderately
8. extremely
simple. complex.
complex.

It is not applicable on It can be applied for Real


Real time applications, time applications and
interactive It is applicable to interactive applications
9.
Applications and Real time traffic. because there is no
Client-Server limitation on the size of
applications. data.

Common questions

Powered by AI

The size of data fields in IEEE standards directly influences network performance and data transmission capabilities. IEEE 802.3, with data field sizes ranging from 0 to 1500 bytes, is limited in handling large data packets, affecting its suitability for data-heavy applications. IEEE 802.4, supporting up to 8182 bytes, can accommodate larger frames, improving throughput in applications requiring substantial data transfer. IEEE 802.5 eliminates size constraints with variable field sizes, offering flexibility and efficiency in data transmission across various application types, impacting both real-time and high-volume data processing scenarios positively .

The IEEE 802 standards are critical in ensuring interoperability among network devices by establishing a shared set of practices for networking technologies. These standards cover both the physical and data link layer specifications, facilitating the smooth operation of devices within local and metropolitan area networks. By adhering to these standards, manufacturers ensure that their products can communicate effectively with other network devices, thereby promoting a cohesive and efficient networking environment across different products and vendors .

The use of a 10-bit group, or 'decade', in the MLMA protocol is an efficient way of identifying stations trying to transmit. By encoding station numbers in a particular format, it ensures that each station's communication is distinctly represented, which helps in decluttering the signalling space, leading to improved efficiency. This implementation also reduces delays by minimizing the waiting time associated with N-bit headers in the Binary Round Allocation Protocol (BRAP), thus enhancing overall network performance, especially under low load conditions .

Collision-free protocols manage potential data collisions during the contention period by ensuring that only one station is able to transmit at a time. This is achieved using methods that allow stations to contend for the channel without causing collisions. The protocols like CSMA/CD and CSMA/CA ensure that once a station acquires the channel, no collision occurs because the transmission is controlled. Thus, even if multiple stations contend simultaneously, the mechanisms in place prevent the mixing of transmissions that lead to collisions .

Token passing methods, as seen in IEEE 802.4's token bus, provide the advantage of controlled access to the network, preventing the collisions that occur in CSMA/CD when multiple stations attempt to transmit simultaneously. In token passing, only the station holding the token is permitted to transmit frames, hence it can efficiently manage network traffic and maintain high throughput and efficiency under high loads, unlike CSMA/CD where efficiency decreases and throughput is adversely affected by collisions when the load increases .

The Multi-Level Multi-Access (MLMA) protocol addresses the issue of delay under low channel load by providing a method where a station that wants to transmit a frame sends its identification in a particular format. In contrast to the Binary Round Allocation Protocol (BRAP), which experiences delays when the channel is lightly loaded since N-bit headers wait for a station to insert a 1 into its mini slot, MLMA uses a 10-bit group known as a 'decade' to represent a digit of the station number, thus reducing waiting time and making the scheme nearly as efficient under high channel load but with shorter delays under low channel load .

The IEEE 802.3 standard uses a Bus topology, whereas IEEE 802.4 employs a Bus or Tree topology, and IEEE 802.5 utilizes a Ring topology. In terms of data frame handling, the frame size in IEEE 802.3 is 1572 bytes, IEEE 802.4 allows up to 8202 bytes, and IEEE 802.5 supports variable frame sizes. Additionally, IEEE 802.4 and IEEE 802.5 offer priority to stations, whereas IEEE 802.3 does not. The size of the data field in IEEE 802.3 ranges between 0 to 1500 bytes, IEEE 802.4 allows up to 8182 bytes, and there is no limit in IEEE 802.5 .

The Medium Access Control (MAC) layer is responsible for handling the collision of frames in computer networks. It achieves this by devising protocols like CSMA/CD and CSMA/CA which prevent data collisions once the transmission channel is acquired by any station. Although collisions might occur during the contention period if multiple stations start transmitting simultaneously, collision-free protocols are designed to resolve these issues during the contention period, thereby eliminating the possibility of collisions .

The complexity levels of IEEE standards significantly impact their applicability. IEEE 802.3 has a simple protocol, making it unsuitable for real-time, interactive applications, and client-server applications. On the other hand, the IEEE 802.4 standard has an extremely complex protocol, making it suitable for real-time applications, while IEEE 802.5, with moderately complex protocols, is adaptable to real-time and interactive applications due to the absence of limitations on data size. Thus, the complexity of a protocol influences its suitability for handling the demands of specific applications and environments .

The choice of network topology under IEEE 802 standards significantly affects collision management and network throughput. A Bus topology, as in IEEE 802.3, is prone to collisions due to shared medium access. On the contrary, a Token Bus or Tree topology in IEEE 802.4 inherently controls access through token passing, efficiently preventing collisions and maintaining high throughput. Similarly, a Ring topology in IEEE 802.5 allows tokens to circulate, enabling controlled access and reducing collision chances. Thus, the topology dictates the protocol efficiency and throughput by defining how data is transmitted and collision is managed .

You might also like