Contention (telecommunications) Explained in Simple Terms

Contention in telecommunications can be a bit confusing, but it's actually pretty straightforward. Contention refers to the competition for shared resources like bandwidth, which is the capacity to transmit data over a network.

Think of it like a highway with multiple lanes. If there are too many cars on the highway, they'll slow each other down. In a network, contention occurs when multiple devices try to access the same resource at the same time, causing delays and decreased performance.

The main types of contention are internal and external. Internal contention happens within a network, while external contention occurs between different networks.

In a contention-based system, there are several types of contention that can occur. One type is collision avoidance, where systems attempt to prevent collisions by utilizing a strict scheduling guideline or having senders listen to the channel before transmitting.

Collision avoidance is an alternative method to handle collisions, as opposed to other methods that might simply try to recover from them. Telecommunications techniques and media access control are often used in this approach.

There are several common examples of contention-based protocols that can lead to collisions, including the Aloha protocol, Carrier Sense Multiple Access (CSMA), and Multiple Access with Collision Avoidance. These protocols often involve multiple data stations attempting to transmit at the same time over a shared channel.

Here are some examples of contention-based protocols that can lead to collisions:

Collisions are a common occurrence in contention-based systems, and there are several protocols that can lead to them. The Aloha protocol is a classic example of such a protocol.

Carrier Sense Multiple Access (CSMA) is another protocol that can result in collisions. This happens when two or more data stations try to transmit at the same time over a shared channel.

Multiple Access with Collision Avoidance is a protocol designed to minimize the occurrence of collisions. By listening to the channel before transmitting, senders can determine suitable times to transmit and avoid collisions.

The following protocols are examples of contention-based channel access protocols that can lead to collisions:

In the United Kingdom, a Rate Adaptive Digital Subscriber Line (RADSL) connection used to be marketed with a contention ratio between 20:1 and 50:1 within the British Telecom network.

This means that 20 to 50 subscribers may be sharing a bandwidth of up to 8 Mbit/s, which is a relatively high contention ratio.

In the UK, the advent of ADSL2+ and fibre-optic connections like FTTC and FTTP has made contention ratio planning less relevant for BT.

In contrast, in the United States and on satellite internet connections, the contention ratio is often much higher, making it harder to predict connection speeds.

Satellite internet connections, in particular, use formulas that count only users who are actually online at a particular time, rather than the total number of subscribers.

This makes it even more challenging to determine connection speeds, which can vary depending on the number of computers using the uplink connection at the same time.

Contention can be a tricky concept to wrap your head around, and one of the main issues is that it's not enough to just look at the contention ratio.

A huge difference in user experience can arise from the same contention ratio depending on the number of users and the speed of the service. For example, 1000 users on a 2 Mbit/s service sharing a 40 Mbit/s pipe can behave very differently than 50 users on a 2 Mbit/s service sharing a 2 Mbit/s pipe.

Even with the same contention ratio, the probability of being affected by contention can be much smaller if there are a large number of users. In telephony, for instance, 200 users may require fewer lines to ensure a certain probability of being blocked than 20 users.

One of the biggest issues with a stated contention ratio is that it's not enough to compare services on its own. It can be misleading because it doesn't take into account the actual number of users sharing the bandwidth.

A huge difference exists between 1000 users on a 2 Mbit/s service sharing a 40 Mbit/s pipe and 50 users on the same service sharing a 2 Mbit/s pipe. The latter case shows how two users trying to download at the same time can result in each getting only 50% of the speed.

In the case of 1000 users, it would take 20 users using their entire 2 Mbit/s link at the same time to show any congestion.

If there are a small number of users, the peaks and troughs in usage will be very visible to each user. This is because the contention ratio doesn't account for the actual number of users, making it difficult to compare services accurately.

For example, in telephony, 20 users each likely to make a call 10% of the time need 8 lines to ensure less than 0.1% chance of being blocked. The same issue applies to broadband service, where a small number of users can still experience noticeable congestion.

Low broadband is a real issue. Beaming offers a range of business-only broadband with low contention rates.

With low contention rates, you can expect a more stable and faster internet connection. This is because there are fewer users competing for the same bandwidth.

For example, Beaming's business-only broadband has low contention rates, making it suitable for businesses that require a reliable internet connection.

Contention in telecommunications can be a real challenge. It's the situation where multiple nodes in a network try to transmit data at the same time, causing collisions and disrupting the flow of information.

Packet collisions occur when multiple nodes transmit data simultaneously, disrupting the packets and making them unintelligible to other devices. This can lead to network performance issues, including delays and packet loss.

The IEEE 802.11 protocol, used in Wi-Fi networks, has its own set of challenges. Its Carrier Sensing Multiple Access/Collision Avoidance (CSMA/CA) protocol tries to mitigate channel contention, but it can still lead to unfairness among nodes.

In a wireless network, nodes can't detect collisions because they can't sense packets traversing the carrier after transmission has started. This makes it harder to prevent collisions.

To address these issues, researchers at UC Santa Cruz have developed new techniques for avoiding packet collisions and improving protocol fairness. Their method recognizes network patterns and determines Contention Window (CW) values that minimize back-off time and maximize network performance.

The UCSC method involves initializing data with a range of fixed delay values, determining an applied delay for a packet based on this data, and adjusting the data based on the success or failure of the transmission. This allows for more efficient and fair use of the network resources.

In a contention-based system, collisions can be avoided by using strict scheduling guidelines or by having senders listen to the channel before transmitting. This can help prevent the issues associated with packet collisions.