Broadcasting in Noisy Radio Networks
Keren Censor-Hillel, Bernhard Haeupler, D. Ellis Hershkowitz, Goran, Zuzic

TL;DR
This paper introduces a noisy radio network model with random faults, analyzes the robustness of existing broadcast algorithms, and demonstrates that coding can significantly improve throughput under receiver faults.
Contribution
It extends classical radio network models to include noise, adapts broadcast algorithms for robustness, and compares coding versus routing in noisy settings.
Findings
Decay algorithm remains robust in noisy models
Modified Gasieniec et al. algorithm achieves robustness
Coding outperforms routing by a logarithmic factor under receiver faults
Abstract
The widely-studied radio network model [Chlamtac and Kutten, 1985] is a graph-based description that captures the inherent impact of collisions in wireless communication. In this model, the strong assumption is made that node receives a message from a neighbor if and only if exactly one of its neighbors broadcasts. We relax this assumption by introducing a new noisy radio network model in which random faults occur at senders or receivers. Specifically, for a constant noise parameter , either every sender has probability of transmitting noise or every receiver of a single transmission in its neighborhood has probability of receiving noise. We first study single-message broadcast algorithms in noisy radio networks and show that the Decay algorithm [Bar-Yehuda et al., 1992] remains robust in the noisy model while the diameter-linear algorithm of Gasieniec et…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Broadcasting in Noisy Radio Networks
Keren Censor-Hillel111Supported in part by the Israel Science Foundation (grant 1696/14) and the Binational Science Foundation (grant 2015803).
Technion
Bernhard Haeupler222Supported in part by the National Science Foundation through grants CCF-1527110 and CCF-1618280.
Carnegie Mellon University
D. Ellis Hershkowitz22footnotemark: 2
Carnegie Mellon University
Goran Zuzic22footnotemark: 2
Carnegie Mellon University
Abstract
The widely-studied radio network model [Chlamtac and Kutten, 1985] is a graph-based description that captures the inherent impact of collisions in wireless communication. In this model, the strong assumption is made that node receives a message from a neighbor if and only if exactly one of its neighbors broadcasts.
We relax this assumption by introducing a new noisy radio network model in which random faults occur at senders or receivers. Specifically, for a constant noise parameter , either every sender has probability of transmitting noise or every receiver of a single transmission in its neighborhood has probability of receiving noise.
We first study single-message broadcast algorithms in noisy radio networks and show that the Decay algorithm [Bar-Yehuda et al., 1992] remains robust in the noisy model while the diameter-linear algorithm of Gasieniec et al., 2007 does not. We give a modified version of the algorithm of Gasieniec et al., 2007 that is robust to sender and receiver faults, and extend both this modified algorithm and the Decay algorithm to robust multi-message broadcast algorithms, broadcasting and messages per round, respectively.
We next investigate the extent to which (network) coding improves throughput in noisy radio networks. In particular, we study the coding cap – the ratio of the throughput of coding to that of routing – in noisy radio networks. We address the previously perplexing result of Alon et al. 2014 that worst case coding throughput is no better than worst case routing throughput up to constants: we show that the worst case throughput performance of coding is, in fact, superior to that of routing – by a gap – provided receiver faults are introduced. However, we show that sender faults have little effect on throughput. In particular, we show that any coding or routing scheme for the noiseless setting can be transformed to be robust to sender faults with only a constant throughput overhead. These transformations imply that the results of Alon et al., 2014 carry over to noisy radio networks with sender faults as well. As a result, if sender faults are introduced then there exist topologies for which there is a gap, but the worst case throughput across all topologies is for both coding and routing.
1 Introduction
Broadcasting messages throughout a network is one the most important network communication primitives. The classic radio network model of Chlamtac and Kutten [8] was designed as a mathematical model to study broadcasting in a wireless setting. In this model, a radio network is represented by an undirected graph of nodes that communicate by transmitting messages during synchronized rounds. During each round, every node can either listen to the radio channel or transmit a message. A listening node receives a message if and only if exactly one of its neighbors transmits during that round. If more than a single neighbor transmits in a certain round, a collision occurs and node does not receive any of the transmitted messages.
The broadcast task in the classic radio network model – in which a single message or multiple messages need to be disseminated throughout the network – has been studied extensively [5, 2, 10, 28, 36, 4]. Classic algorithms [5, 22] typically employ routing. That is, nodes only transmit one of the messages the algorithm is disseminating. Alternatively, (network) coding approaches, in which nodes transmit multiple messages coded together, have been of recent interest [1, 3, 27, 21, 34, 25, 6].
Despite having been extensively studied, a notable deficit of the classic radio network model is its inability to model random noise. Specifically, the classic model assumes that a message that is sent without collisions is correctly received. However, this assumption is overly optimistic for real environments, in which noise may impede communication.
Our contribution.
In this paper, we introduce the noisy radio network model, in which the classic graph-based model of Chlamtac and Kutten [8] is augmented with random faults. In particular, for a constant fault parameter , every transmission may be noisy with probability (sender fault), or a node that would otherwise receive a message with probability receives noise instead (receiver fault). The faults occur independently at each node.
We begin by studying the extent to which the performance of existing single-message broadcasting algorithms deteriorates: we show that while the Decay algorithm of Bar-Yehuda, Goldreich and Itai [5] is robust to faults, the diameter-linear algorithm of Gąsieniec, Peleg and Xin [22] (which we call FASTBC) deteriorates considerably. We then develop a new single-message, diameter-linear algorithm for the noisy radio network model. Moreover, we describe how to extend both Decay and our modified algorithm to multi-message broadcasting algorithms, achieving throughputs of and messages per round, respectively.
The main challenge that arises when designing fault-robust algorithms is avoiding careful deterministic round synchronization; that is, random faults prevent nodes from knowing exactly which other nodes have a message in any given round. Prior algorithms used round synchronization of this nature but can be made fault-robust by repeating certain otherwise fragile subroutines.
Additionally, we study the power of (network) coding in the new noisy radio network model. In particular, we examine the coding gap in this model: roughly the ratio between the throughput of coding to the throughput of routing. For the classic radio network model, recent work of Alon et al. [3] demonstrated an coding gap on certain networks. However, the same work shows that up to constant factors, in worst case topologies, coding performs no better than routing, when one broadcasts a very large number of messages. This runs contrary to the intuition that coding ought to improve the throughput of communication.
We resolve these counterintuitive results by showing that coding is, in fact, much more powerful than routing, provided receiver faults occur. Not only do we show that with receiver faults coding throughput is superior to routing by a gap on certain topologies, but we prove that the worst case performance of coding is superior to that of routing by a gap. These results emphasize that in practical settings coding can, in fact, significantly improve broadcast efficiency.
Lastly, we show that any algorithm for the classical radio network model can be made robust to sender faults at the price of a constant factor in throughput. This implies that the counterintuitive results of Alon et al. [3] carry over to the noisy radio network model with sender faults.
2 Related Work
The radio network model was introduced more than 30 years ago in the pioneering work of Chlamtac and Kutten [8]. Since then computation in radio networks has been extensively studied. An excellent survey is given by Peleg [36]. Below, we discuss the most related work.
Single-message broadcasting in radio networks: In Bar-Yehuda et al. [5], it was shown that single-message broadcast in a known topology can be achieved in rounds, where is the diameter of the network. This was improved by Gąsieniec et al. [22] and Kowalski and Pelc [29] who showed that if the topology is known broadcast can be completed in rounds. If the topology is not known, Czumaj and Rytter [10] show that rounds suffice. By the and lower bounds of Alon et al. [2] and Kushilevitz and Mansour [32], respectively, the above complexities are optimal. Lastly, if collision detection is available – a stronger assumption than known topology – a -round algorithm is achievable as shown by Ghaffari et al. [21].
Multi-message broadcasting in radio networks: The earliest work for broadcasting messages is Bar-Yehuda and Israeli [4], who gave an algorithm that used rounds, where is the maximum node degree. A deterministic algorithm that works in rounds was given by Chlebus et al. [9]. The first algorithm to beat the performance of Bar-Yehuda and Israeli [4] and to achieve an optimal dependence on the number of messages was given by Ghaffari and Haeupler [17]. This algorithm completes in rounds. The lower bound for the number of rounds is given by Alon et al. [3]. Ghaffari et al. [21] provided an algorithm that completes in rounds if the topology is known. Both of the latter algorithms crucially rely on (network) coding.
Network coding and coding gap: Network coding was first studied outside of the radio broadcast model by Ahlswede et al. [1]. For multiple-message broadcast, network coding algorithms by Ghaffari et al. [21] and Khabbazian and Kowalski [27] achieved a throughput of . A network coding gap of on certain topologies for the radio network model was demonstrated by Alon et al. [3] as was a worst case gap.
In wired undirected networks, Li et al. [34] show the network coding gap to be at most . For directed wired networks, Halperin et al. [25] shows that the coding gap corresponds to the integrality gap of directed Steiner-tree LP. For the wired vertex-congest model, in which messages sent at the same time do not collide, a tight coding gap of was given by Censor-Hillel et al. [6].
Robust communication models: The noisy broadcast model, introduced by El-Gamal. [14], resembles our model as it assumes random errors. This model was mostly studied in the context of computing functions of the inputs of nodes [16, 35, 23, 33]. However, this model assumes a complete communication network and single-bit transmissions. An extension of this line of work for random planar networks was also studied [26, 38, 12, 13]. Unlike our own model, in this model a node can receive a message from multiple neighbors in a single round.
Another model that captures unreliability in radio networks is the dual graph model [31, 7, 30, 18, 20]. In this graph-based model, there is a static set of edges that form the network graph as well as an additional graph which consists of edges that may or may not be present in each round, as chosen by an adversary. While an excellent way to capture an environment where some links are reliable and others are not, the dual graph model fails to model random noise.
3 Preliminaries
In this section, we review the classic radio network model, define our generalization of it, define throughput, explain how we quantify the coding gap and describe existing broadcast algorithms.
3.1 The (Noisy) Radio Broadcast Model and -Message Broadcast
The classic radio network model consists of an undirected graph with nodes and diameter . Nodes communicate in synchronized time steps (rounds) by either remaining silent (listening) or locally broadcasting a packet (each neighbor gets the same packet). A node receives a packet from a neighbor in round if and only if exactly one of its neighbors broadcasts in and remains silent. We term this model the faultless model.
We build on the classic model and introduce a noisy radio network model. Our model is the same as the classic radio broadcast model but with one of two modifications. In the receiver faults model, a node that is listening and has only one broadcasting neighbor receives noise with constant probability (independently of other nodes). In the sender faults model, a broadcasting node has a constant probability of transmitting noise (independently of other senders failing). We use to denote the fault probability and expose it in results where appropriate. In both variations of the model, we assume that if a node receives noise due to collisions, faults, or none of its neighbors broadcasting, the node does not mistake this noise for a legitimate packet from a neighbor.
The most commonly studied algorithmic problem in the radio network model is the -message broadcast problem. This problem consists of a source and messages. is often referred to as the topology. Each message is of size and each packet is of size .111Papers more commonly define the message and packet size to be . However, this choice leads to tedious technical difficulties in the noisy setting. Our choice of message and packet size as is reasonable for two reasons: (1) is the most practical setting and (2) without using bits one cannot even send a message identifier. This assumption will become particularly important for us when providing coding schedules, as it is what enables us to use Reed-Solomon coding to create packets that can be broadcast in a single round. The source begins in the first round as the only node that knows the messages. The problem is solved once all nodes have all messages.
A schedule is defined by the assignment of a function to each node in each round , which, intuitively, governs the behavior of node in round . The schedule is static and does not change during rounds. The domain and co-domain of the function depend on the setting as follows. In a routing setting, the function takes no input (except the implicit arguments and ) and outputs either a stay silent token or the index in of the message to broadcast. If the output of is the index of a message which has not received by round , the node remains silent. In a (network) coding setting, the function takes as input the entire history of packets node received and outputs either a stay silent token or an arbitrary packet of length . We informally refer to an algorithm as a procedure that outputs a schedule.
3.2 Throughput
The throughput of a given topology is roughly the maximum number of messages that can be transmitted per round as the number of messages, , goes to infinity.
Definition 1** (Topology Throughput).**
The routing throughput of a topology is defined as
[TABLE]
where is the number of rounds taken by the schedule . In the faultless setting, the minimum is taken over schedules that broadcast messages from to all nodes in . In the faulty setting, the minimum is taken over schedules that succeed with probability at least .222In the faulty setting could be replaced by the minimum of the expected number of rounds taken by any schedule that succeeds with probability 1. While our results can be adapted to this definition, this definition introduces various technical issues which we wish to avoid in order to simplify the presentation.
Given a set of schedules, we define the throughput of the set of schedules as above but where we minimize over the set (rather than all possible schedules).
In general, we show topology throughput lower bounds of in the noisy model by showing that, for any and any , there is a such that there exists a schedule that broadcasts messages in rounds, where . Similarly, to show a throughput upper bound of in the noisy model we demonstrate that, for sufficiently large , any schedule that broadcasts with a probability of failure of at most requires at least rounds.
3.3 Comparing Routing and Network Coding
There are a couple of natural ways to quantify the advantage that coding offers over routing. First, one might be interested in finding a fixed topology where the ratio of coding throughput to routing throughput is largest. Second, one might be interested in the worst case performance of coding compared to the worst case performance of routing. We formalize these two quantities as the shared topology gap and the worst case topology gap respectively. Let and be the throughputs of when using routing schedules and when using network coding schedules respectively.
Definition 2** (Shared Topology Gap).**
The shared topology gap is:
[TABLE]
Definition 3** (Worst Case Topology Gap).**
The worst case topology gap is defined as
[TABLE]
We will also sometimes refer to the coding gap of a fixed network defined as . Note that any lower bound on the coding gap of a network is a lower bound on . The two quantities above are related as shown by the following claim.
Lemma 4**.**
The worst case topology gap is at most the shared topology gap, i.e. .
Proof.
Let be the minimizing assignment to . Thus,
[TABLE]
∎
Interestingly, we later prove that this observation holds with equality in the receiver faults setting but not in the sender faults setting.
3.4 Broadcast Algorithms for Faultless Radio Networks
In this section, for completeness, we present the broadcast algorithms for the faultless setting whose performance in the noisy setting are addressed in Section 4.
3.4.1 Decay
Here we describe the classic Decay algorithm [5] for broadcasting a single message from the source to every other node. For each round, we define the set of informed nodes as all the nodes that received the message up to that round.
Algorithm: Divide the rounds into phases of rounds. During the round of each phase, where , each informed node broadcasts the message independently with probability . A simple calculation yields the following.
Lemma 5**.**
If a node has an informed neighbor at the start of the phase, it becomes informed by the end of the phase with constant probability.
Proof.
If the number of informed neighbors that has in the round of a phase is in , a simple calculation shows that it becomes informed by the end of the round with constant probability. Since the number of informed neighbors is nondecreasing, there is always a round in a phase in which the above condition holds. ∎
The round complexity of Decay then follows [5].
Lemma 6** (Bar-Yehuda et al. [5]).**
In the faultless setting, Decay spreads a single message in rounds with a probability of failure of at most .
Proof.
Fix a path from the source to any node (the length of the path is at most the diameter ). At round , let be the largest such that knows the message (initially, ). After one phase of rounds either remains the same or increases by 1 with constant probability, by Lemma 5. Hence, after phases, the probability of failure can be bounded via a Chernoff bound:
[TABLE]
Applying a union bound over all nodes gives that the failure probability is at most .
∎
3.4.2 FASTBC
We next describe an optimal algorithm for single-message broadcast when all the nodes know the topology beforehand, given by Gąsieniec et al. [22], which we refer to as the FASTBC algorithm. FASTBC works by first decomposing the graph into a gathering-broadcasting spanning tree (GBST) and then utilizing this structure to broadcast a message in rounds.
We need the following notion in order to describe the algorithm. A ranked breadth-first search (BFS) tree for a graph is a BFS tree rooted at a source node where every node in the tree is assigned an integral rank. The ranks are assigned inductively, as follows. Every leaf node has rank . A non-leaf node with a maximum child rank of is assigned a rank of if exactly one child of has rank . Otherwise, if two or more children have rank , then is assigned a rank of . Additionally, we define the level of node in a BFS tree as the distance from to . The maximum rank can be bounded as follows.
Lemma 7** (Gaber and Mansour [15]).**
The largest rank in a ranked BFS tree of size is no greater than .
GBST: A ranked BFS tree of a graph is a gathering-broadcasting spanning tree (GBST) if and only if no two distinct nodes on the same level and of the same rank have two distinct -parents both with rank . See Figure 1 for a comparison of a ranked BFS tree that is not a GBST with a ranked BFS tree that is a GBST. Note that we assume nodes agree on a common GBST before the start of the algorithm because of the known topology assumption.
Fast nodes in a GBST: We call node fast if one of its GBST-children has the same rank as , and that tree-edge is called a fast edge. Any GBST-path from the source to a node has nonincreasing ranks. Hence it is composed of at most fast stretches of consecutive fast nodes of the same rank connected by fast edges.
The FASTBC Algorithm [22]: At a high level, FASTBC divides the rounds into odd and even numbered rounds. On odd-numbered rounds (called slow transmission rounds) it performs a standard Decay algorithm that pushes a message from a higher ranked node to a lower ranked one. During even-numbered rounds (called fast transmission rounds) it pushes a message along fast stretches.
More formally, during a fast transmission round , only fast nodes on level and rank broadcast if . During a slow transmission round , all nodes broadcast with probability .
Intuitively, messages on a fast stretch ride a wave from the start of the stretch to its tail. More formally, when a messages gets transmitted along a fast stretch for the first time, it never gets interrupted until it reaches the tail. This non-interference along fast stretches is ensured by the properties of the GBST. The round complexity of FASTBC is given as follows.
Lemma 8** (Gąsieniec et al. [22]).**
In the faultless setting, FASTBC spreads a single message in rounds with a probability of failure of at most .
Proof.
Fix any path from the source to a node . The path can be decomposed into at most fast stretches and non-fast edges. By Lemma 6, the message successfully traverses all of the non-fast edges in rounds with a probability of at least .
Next, we analyze the fast stretches during fast transmission rounds. Let the length of the fast stretch be . The time for a message to reach the tail from the start of the fast stretch is (with probability ) since it has to wait at most rounds for the first transmission and it is not interrupted until it reaches the tail of the stretch.
This non-interference is ensured because fast nodes of different ranks that transmit during the same round must be at least 6 levels apart (and since a GBST is a BFS tree, they do not interfere). Nodes of the same rank that transmit in the same round will not interfere because of the GBST construction property.
Putting together the behaviors of the fast stretches and non-fast edges, we get that a message is transmitted along a path from to in rounds with a probability of at least . Applying the union bound over all nodes completes the proof. ∎
4 Robust Broadcast Algorithms
In this section we describe how we adapt algorithms from the faultless setting to the sender or receiver faults setting in order to obtain robust broadcast algorithms.
4.1 Robust Algorithms for Single-Message Broadcast
Decay [5] – which spreads a message in rounds with high probability333We denote “with high probability” when the probability of success is at least . in the faultless setting – is a classic faultless broadcasting algorithm. We now prove that the Decay algorithm works as-is with faults.
Lemma 9**.**
With sender or receiver faults with fault probability , the Decay algorithm spreads a single message in rounds with a probability of failure of at most .
Proof.
Fix a path from the source to any node (the length of the path is at most the diameter ). At round , let be the largest such that knows the message (initially, ). After one phase of rounds either remains the same or increases by 1 with probability for a particular constant by an analogue of Lemma 5 which appears in Section 3.4.1. Hence, after phases, the probability of failure can be bounded via a Chernoff bound:
[TABLE]
Applying a union bound over all nodes gives that the failure probability is at most . ∎
While the Decay algorithm is very simple and does not require nodes to know the topology in advance, the number of rounds it takes depends super-linearly on the diameter. However, if the topology is known in advance, it is possible to achieve linear dependence on the diameter in the faultless setting, as shown by the FASTBC algorithm [22]. FASTBC succeeds with high probability in rounds.
However, in contrast to the Decay algorithm, the performance of FASTBC deteriorates in the faulty setting. In particular, FASTBC uses a fragile round counting mechanism to synchronize message passing along its fast stretches which does not translate well to the faulty setting. The following result quantifies this performance deterioration.
Lemma 10**.**
FASTBC takes rounds in expectation to broadcast a message along a single path of length .
Proof.
Consider a path of length with a message on its left endpoint. Let be the expected number of rounds to traverse the path of length with FASTBC under the condition that the leftmost node broadcasts in the next round. With probability the broadcast is successful, leading to a subproblem with length . Alternatively, with probability , it can be unsuccessful – leading to a waiting time of until the leftmost node broadcasts again and without reducing the path length . The resulting recurrence is which can be rewritten as , leading to . ∎
One simple way to construct a robust broadcast algorithm is to perform FASTBC but repeat each round times for a total of rounds. This approach works because the probability that any message gets dropped is at most , which allows one to apply a union bound over the entire algorithm (of length at most ). However, this approach loses the linear dependence on and therefore performs no better than Decay. A better approach, inspired by Lemma 10, would be to repeat each message times, giving and a -round algorithm.
We further refine this approach in the following Robust FASTBC algorithm, which gives a linear dependence on in the noisy setting. We first provide the high-level idea of Robust FASTBC to give intuition and then provide a more formal, terse definition.
The High-Level Idea of Robust FASTBC: As in FASTBC, a GBST is constructed from the source node . Consider any GBST-path from to another node and note that it has at most fast stretches (consecutive fast nodes of equal rank) because the ranks on the path are non-increasing.
The algorithm works by partitioning the rounds into odd and even-numbered rounds. During odd-numbered rounds, a standard Decay algorithm is performed on all nodes. These rounds are meant to push the message from one fast stretch to the next.
During even-numbered rounds, a different procedure makes progress along fast stretches. First, partition the nodes of each fast stretch into blocks of size .444All the blocks have size , except possibly the last one. We define the procedure of broadcasting on a block in the following way: at round (only even numbered rounds can be performing this procedure) a node with level broadcasts if it is in the block and . The procedure continues on for rounds for some sufficiently large constant . We work modulo to prevent collisions between nodes at consecutive levels since we are working on a BFS tree (and the GBST properties prevents interferences from nodes at the same level). Note that the probability that a message that is in a broadcasting block in the beginning fails to exit the block is at most for a constant which we can set as large as needed (by increasing the round multiplier ).
Now imagine contracting the nodes in a block into one supernode. A broadcast on this supernode corresponds to the block-broadcast procedure described in the last paragraph and superrounds on this graph correspond to rounds in the original graph. We define ranks, levels and fast supernodes in the same way as in the original graph (in particular, the entire supernode gets the same level and rank).
The algorithm on the contracted graph is as follows: at round , a fast supernode with level and rank broadcasts if . In other words, a wave propagates the message from one end of the fast stretch to another end in a number of superrounds that is linear with respect to the length of the fast stretch. Broadcasts at the same superround of nodes of different ranks are displaced by at least 6 levels, hence they do not interfere with each other. Two consecutive waves on the same block are spread superrounds apart.
Formal Robust FASTBC Algorithm: As in FASTBC, a gathering-broadcasting spanning tree is constructed from the source node. Let the round number of the algorithm be . When is odd, each node will perform a standard Decay step (a node broadcasts with probability ). Let and be a sufficiently large constant. At even-numbered rounds , a node in the fast set with level and rank will broadcast if and .
The following is our main result for this section.
Theorem 11**.**
Robust FASTBC spreads a single message in rounds with a probability of failure of at most if sender or receiver faults occur with probability .
Proof.
Fix a GBST path from the source to a node . Partition the edges on the path into fast stretches (consecutive edges connecting two nodes of the same rank) and non-fast edges. There can be at most non-fast edges interconnecting fast stretches.
Assuming a message is on a non-fast edge, during the next rounds it is transmitted along that edge with constant probability. Given that there are only such edges, a Chernoff bound gives us that after such rounds (where a message is waiting to be transmitted along a non-fast edge), the message is transmitted along all the non-fast edges on with probability at least .
Next, we turn to counting the number of rounds that a message spends on fast stretches (during even-numbered rounds). Note that from the design of the algorithm and the properties of the GBST no two broadcasting nodes ever interfere with each other (hence the only failures come from constant probability faults).
Call a fast node from the path a barrier if its level is divisible by and call a message active if it is on a fast stretch and the node it is currently at is broadcasting. Note that a message that enters a fast stretch has to wait rounds until it becomes active. Once it is active, consider its behavior during the next rounds. The message can either exit the stretch, remain active (meaning it reaches the next barrier) or become inactive (by failing out of transmissions). The probability of becoming inactive is at most by Chernoff with an appropriate constant . Every time a message becomes inactive, it waits rounds before it becomes active.
Let (note that ) be the lengths of the fast stretches in the path . When a message is active, it traverses the paths in at most rounds. The number of rounds it takes for a message to become active is at most
[TABLE]
where is the length of the entire protocol. The term comes from becoming active each time a message enters a fast stretch. The accounts for the possibility of a message becoming inactive in between barriers. A Chernoff bound proves that if , the message gets passed along the path with a probability of at least .
Putting together the behavior during the odd-numbered and even-numbered rounds and applying a union bound over all nodes gives that the protocol forwards the message from the source to all other nodes in the claimed number of rounds with probability at least . ∎
4.2 Robust Algorithms for Multi-Message Broadcast
A pleasant feature of single-message broadcasting algorithms that are robust to sender failures is that they can be used in a black-box manner to transmit messages with random linear network coding [24], provided some minor technical conditions are satisfied. For instance, a node cannot change its behavior based on whether it receives a message or not. However, all of our algorithms can be made to satisfy these conditions using methods similar to [21]. We state the results that can be achieved and refer the reader to Ghaffari et al. [21] and Haeupler [24] for details.
Lemma 12**.**
Decay with random linear network coding can broadcast messages in rounds if sender or receiver faults occur with constant probability. It follows that any topology has a coding throughput of .
Lemma 13**.**
Robust FASTBC with random linear network coding can broadcast messages in rounds if sender or receiver faults occur with constant probability. It follows that any topology has a coding throughput of .
We leave as an open problem the existence of an algorithm that is robust to sender and receiver faults and can broadcast messages in – this would be optimal up to additive factors.
5 Throughput Gaps with Noisy Broadcast
We now study the gaps between (network) coding and routing in the noisy radio network model. In the faultless setting, by Lemma 12, coding can send messages in rounds. Moreover, in the faultless setting, no routing scheme with polynomial in is known to send messages in fewer than rounds. The apparent disparity of what is achievable with coding versus routing demands a formal explanation.
Previous work of [3] attempts to formalize this gap. However, although this work shows a shared topology gap of in the faultless setting, it also shows the counterintuitive result of a worst case topology gap of .
Our new model and results give a more satisfactory explanation. We formally show in what sense the high throughput routing schemes of [3] are not robust; namely, they cease to be efficient for random receiver failures. Moreover, in the noisy radio network model we prove that coding is indeed necessary for high throughput broadcasting by exhibiting a worst case topology gap of and a shared topology gap of in the receiver fault setting. All of our routing lower bounds, and therefore all of our gaps, are particularly strong as we prove them in a setting where routing is allowed to be adaptive, as we later define.
Additionally, we show that with coding or adaptive routing and sender faults, very little differs from the faultless setting in terms of throughput: every coding (resp. routing) schedule that assumes no faults can be transformed into a coding (resp. adaptive routing) schedule in the sender faults setting with the same throughput up to constants. These transformations allow us to conclude the following: (1) interestingly, the worst case topology gap is highly sensitive to whether sender or receiver faults are examined – we show it to be for sender faults with adaptive routing; (2) the shared topology gap of the faultless setting also exists in the sender fault setting.
We now define an adaptive routing schedule wherein all nodes are allowed to adapt to all faults.
Definition 14** (Adaptive Routing Schedule).**
*An adaptive routing schedule is a sequence of functions – one each every round – that takes as input
i) the entire topology and ii) all tuples where node received message in some round
. Each outputs a sequence of length directing each node to either remain silent or to broadcast a message they know.*
In practice, a distributed routing algorithm might receive some feedback as to when faults occur but it will certainly not receive as much as our adaptive routing schedules. Thus, our definition is sufficiently strong for proving meaningful gaps. Moreover, if routing is non-adaptive, a gap can be proved on a single-link topology as shown in Appendix A. However, with adaptive routing the gap is on the single-link topology. Thus, adaptivity can considerably improve routing throughput, further motivating adaptive routing as a strong model for proving gaps.
Lastly, we use Reed-Solomon coding [37] as a black box for our coding schedules throughout this section. Given input packets, Reed-Solomon coding constructs coded packets such that any of the coded packets is sufficient to reconstruct the original packets.
5.1 Gaps for Receiver Faults with Adaptive Routing
In this section we study the coding gaps with receiver faults and adaptive routing.
5.1.1 Star Topology: Gap for Receiver Faults with Adaptive Routing
We first show a gap in the receiver fault setting on a star topology. A star topology consists of a node and other adjacent nodes.555We use instead of other nodes to simplify calculations.
Lemma 15**.**
The adaptive routing throughput of the star topology with receiver faults is .
Proof.
For concreteness assume that . We prove a throughput of by providing the following schedule. The schedule works by broadcasting message from until it is received by all nodes, then broadcasting and so forth up to message . The schedule stops after rounds. It remains to show that the schedule fails with a probability of at most .
Let be the random variable that stands for the number of rounds required until message is received and let . Moreover, define and . It is not hard to show that for all , , hence roughly counts the number of rounds in which goes past its expectation. We now bound the tail distribution of the variables, thereby bounding it for the variables and for .
Let be the random variable of the number of nodes that do not receive message after broadcasts for rounds. It holds that . The following shows that .
[TABLE]
and thus, we have and hence by definition of , we have .
We now use Chernoff bounds for geometric random variables (see Theorem 34) to bound the tail distributions of and . For every , let be a geometric random variable with a probability of success of and let . Note that and recall that . Since , we also have and therefore applying Chernoff bounds for geometric random variables gives that for any ,
[TABLE]
Letting gives that . Lastly, we note that . Thus, our schedule sends all messages in rounds with a probability of failure no greater than .
To finish the proof, we need to show that our schedule achieves a throughput of . To do so we must show that for any and for any , there exist a sufficiently large such that . For sufficiently large this is clearly satisfied.
We now prove an upper bound of on throughput by proving that rounds are necessary to broadcast messages with a probability of failure of at most . Because every node other than is connected only to , we know that any successful schedule routes messages from to each of the nodes directly. Broadcasting from any node other than clearly does not help the schedule and so, without loss of generality, we assume that only broadcasts. Similarly, it clearly does not help a schedule to broadcast a message after it is received by all nodes and so, without loss of generality, the schedule only broadcasts a message if some node has still not received that message. Therefore, without loss of generality, an adaptive routing schedule on a star can be thought of as broadcasting each message from until it is received by all nodes (potentially a given message is not always broadcast in contiguous rounds).
As in the proof of the lower bound, let stand for the number of rounds in which is broadcast and let .
We now show that . Suppose, for the sake of contradiction, that . It follows by Markov’s inequality that it is possible to send by broadcasting it for rounds with probability of failure at most . However, the probability that a given node does not receive in rounds is and so the probability that all nodes receive the message is , by the inequality . Thus, broadcasting for rounds succeeds with probability at most , which contradicts that it is possible to broadcast for rounds with a probability of failure at most . Thus, .
We now show that rounds are insufficient to broadcast messages with a failure probability of at most . Suppose, for the sake of contradiction, that rounds are sufficient to broadcast messages with a probability of failure no greater than . Let stand for the random variable that is 1 if and 0 otherwise and let . Every message is broadcast on average times and so by Markov’s inequality there are at least messages each of which is sent fewer than times. Since our schedule succeeds with probability , it follows that with probability at least there are at least messages that are successfully sent in fewer than rounds. Otherwise stated, . In what follows, we contradict this fact.
Since , we have . By Chernoff bounds, , for appropriate . Thus, . We now use this bound on to bound the probability that is large. It holds that and so by another Chernoff bound we have .
Therefore, for sufficiently large , and appropriate , this contradicts the above fact that . Thus, we conclude that for large and , rounds are insufficient to broadcast messages with a failure probability of at most and so the throughput is . ∎
Lemma 16**.**
The coding throughput of the star topology with receiver faults is .
Proof.
A throughput of trivially follows because rounds are strictly necessary.
We show a throughput of by providing a schedule that uses Reed-Solomon coding to send messages in rounds. Using Reed-Solomon coding it is possible to generate and send packets such that reception of any of the packets by the receiver suffices for the receiver to reconstruct the original messages. Our schedule creates these packets and then broadcasts them. By Chernoff bounds, the probability that a given node does not receive packets is for some positive constant . By a union bound over the nodes, we have that the probability that some node does not receive packets is at most . For sufficiently large , we have . Lastly, to show a throughput of we note that for any there exists a sufficiently large such that . ∎
Lemma 15 and Lemma 16 give the claimed gap on the star topology.
Theorem 17**.**
In the receiver faults setting there is a coding gap for the star topology with adaptive routing. A shared topology gap of in the receiver faults setting follows.
5.1.2 Worst Case Topology: Gap for Receiver Faults with Adaptive Routing
Having shown a shared topology gap of in the receiver fault setting we now show a worst case topology gap of with receiver faults. Recall that we define the worst case topology gap as . To prove the gap, we show that with receiver faults and adaptive routing, and .
We first describe the topology, , that has minimal throughput for both coding and adaptive routing with receiver faults. The topology is based on a construction of Ghaffari et al. [19]; Ghaffari et al. [19] demonstrate the existence of a bipartite network of radius 2 with nodes. These nodes consist of a source node, receiver nodes, sender nodes. Every receiver node is connected to a subset of the sender nodes by a probabilistic construction. See Figure 2(a) for a sketch of the network. We duplicate each of the receiver nodes to induce star-like topologies which we term clusters. More formally, is as follows.
Worst case topology () for receiver faults: We begin with the construction of Ghaffari et al. [19]. Instead of each receiver node, , we construct a cluster of nodes. Each node in the cluster that replaces receiver has an edge to sender node if and only if is an edge of the original network of Ghaffari et al. [19]. We use the symbol for the resulting network. See Figure 2(b) for an illustration of .
Since nodes in a cluster are connected to the same sender nodes, a node in a cluster is sent a packet without collision if and only if all other nodes in the cluster are sent the same packet without collision. Moreover, Ghaffari et al. [19] prove that at most of all receiver nodes receive a packet without collision in any one round in the original topology, so we conclude the following.
Lemma 18**.**
At most of clusters of receive a packet without collision per round.
We now use this topology to prove the following claim .
Lemma 19**.**
Adaptive routing on has a throughput of in the receiver fault setting.
Proof.
Consider the above described . Since in each round every node in a cluster is sent the same message without collision or no message, we can interpret each as a star of nodes. By Lemma 15, each cluster must receive a packet without collision at least times, in order to receive messages with a probability of failure of at most . Thus, in order for every node to receive a message such that the probability of failure is at most , every cluster must receive a message without collision at least times. By Lemma 18, clusters are sent a packet without collision each round and so at least rounds are necessary to have a failure probability of at most . Thus, the throughput is at most . ∎
We next move to the adaptive routing throughput in the receiver fault setting. To prove this possibility result we first prove an intermediate result for bipartite networks.
Lemma 20**.**
Consider bipartite network where every node in knows the same messages. There exists an adaptive routing schedule of length that broadcasts the messages to all the nodes in with probability at least in the receiver fault setting.
Proof.
We show that there exists an adaptive routing schedule, , that succeeds in broadcasting messages from all nodes in to all nodes in with a probability of failure of at most . By Lemma 9, Decay can route all messages to in rounds with a failure probability of at most . Denote by this schedule provided by Decay when it is used for message . The schedule runs the schedule repeatedly until it succeeds, then it runs until it succeeds and so forth until . However, never runs more than of these schedules in total.
Let be the random variable that stands for the number of times must be run and let . Note that is a geometric random variable with probability of success and that . By a Chernoff bound for geometric random variables (see Theorem 34), we have that the probability that does not succeed is
[TABLE]
Thus, succeeds in sending messages in rounds with a probability of failure of at most . ∎
Lemma 21**.**
Adaptive routing on any network has a throughput of with receiver faults.
Proof.
We now prove that the worst case adaptive routing throughput is by providing an adaptive routing schedule. Roughly, our schedule works by pipelining schedules given by Lemma 20. We first note that any broadcast problem given a source and graph can be broken into a series of broadcast problems on bipartite graphs. In particular, it can be broken into the BFS layering of where the layer contains all nodes with distance exactly from . Let be the set of nodes in the layer. Note that each pair of consecutive layers , define a bipartite network. Next, we divide into batches of size (assume, without loss of generality, that divides ), which we pipeline.
By Lemma 20, we can broadcast batch of messages in rounds with a failure probability of at most . Let be the schedule that broadcasts batch in this manner.
We now describe our schedule for broadcasting through the entire network. We divide rounds into meta-rounds of size . The -th layer runs in meta-round . In other words, we pipeline batches through the network using the above schedule for bipartite graphs, working layers of apart so we do not incur extra collisions. We run meta-rounds.
We argue that this schedule achieves a throughput of . A fixed fails in a meta-round with a probability of at most , for sufficiently large . By a union bound over the diameter, the probability that any fails in a meta-round is at most . Moreover, we run meta-rounds and so by another union bound over meta-rounds, an fails in any meta-round with a probability of at most , for an appropriate . Lastly, if every in every meta-round succeeds, then every node receives every batch, meaning that every node receives all messages. Since each meta-round is of length and we run meta-rounds, we use a total of rounds to succeed with probability at least , for .
Finally, to conclude a throughput of we need to show that for any and there exists a such that , which trivially holds. ∎
The impossibility result of Lemma 19 and the possibility result of Lemma 21 yield the following.
Lemma 22**.**
The worst case adaptive routing throughput with receiver faults is , i.e. .
Next, we show that coding in the receiver fault setting can always achieve a throughput of , and that no better bound exists.
Lemma 23**.**
The worst case coding throughput in the receiver fault setting is , i.e. .
Proof.
We first prove that the worst case coding throughput is with receiver faults. Consider the above worst case topology. In any given round at most clusters receive a message. Each cluster forms a star and, similarly to Lemma 16, each star must be sent the message rounds, in order to decode all messages. Thus, rounds are strictly necessary and in particular are necessary to succeed with probability at least . We conclude a coding throughput of on this topology.
By Lemma 12, the worst case coding throughput is with receiver faults, which completes the proof. ∎
By Lemma 22 and Lemma 23, we conclude our strong worst case topology gap.
Theorem 24**.**
The worst case topology gap is for receiver faults with adaptive routing.
5.2 Transformations from the Faultless Setting to the Faulty Setting
Having shown that there is a strong gap in the receiver fault setting, we now turn our attention to the sender fault setting. We begin by presenting explicit transformations of schedules from the faultless setting into schedules that are robust to faults.
Lemma 25**.**
A set of routing schedules with throughput in the faultless setting can be transformed into a set of adaptive routing schedules with throughput for the sender fault setting.
Proof.
We construct a set of routing schedules, , such that for any and any there exists a such that , where is a schedule in that broadcasts messages with probability of success at least and is the number of rounds it uses. Fix and . We now show how to construct that satisfies the above inequality.
Suppose we have a set of schedules that achieves a throughput of in the faultless setting. That is, for any and any there exists sufficiently large , such that for some schedule in . It follows that . We use to construct , such that the schedule sends messages in rounds with probability at least , for a value of to be chosen later and arbitrarily small and . Notice that we can guarantee that by picking sufficiently large, since .
The schedule is constructed as follows. Each round of broadcast of corresponds to a meta-round of composed of rounds, for chosen as small as desired. In each meta-round of , if a node broadcasts message in the corresponding round of , the node now broadcasts until it succeeds, then it broadcasts until it succeeds and so forth up to , until it reaches rounds. If it succeeds in sending all messages before the end of the meta-round, the node remains silent for the remainder of the meta-round.
In each meta-round, in expectation each message requires rounds to be sent successfully and so all messages for a meta-round require rounds in expectation. By Chernoff bounds, a node fails to send all messages in a given round with a probability of at most . Thus, letting , the schedule fails with a probability of at most , for some positive constant . A union bound over all nodes shows that the probability that any node fails in a meta-round is at most . Moreover, by another union bound over meta-rounds, the probability that any node fails in any one of the meta-rounds is at most , which is at most , for sufficiently large . Thus, the schedule succeeds in sending messages in rounds with s probability of success of at least .
Lastly, we need to show that . However, notice that , where and are arbitrarily small by our choice and hence the inequality clearly holds. ∎
Lemma 26**.**
A set of coding schedules from the faultless setting with throughput can be transformed into a set of coding schedules with throughput in the sender or receiver fault setting.
Proof.
We construct a set of routing schedules, , such that for any and any there exists a such that , where is a schedule in that broadcasts messages with probability of success at least and is the number of rounds it uses. Fix and . We now show how to construct a schedule that satisfies the above inequality.
Suppose we have a set of schedules that achieves a throughput of in the faultless setting. That is, for any and any , there exists sufficiently large , such that for some schedule in . It follows that . We use to construct , such that sends messages in rounds with probability at least , for a value of to be chosen later and arbitrarily small and . Notice that we can guarantee that by picking sufficiently large, since .
We construct as follows. A message of corresponds to messages of , denoted by . Each round of broadcast of corresponds to a meta-round of composed of rounds, for arbitrarily small . Let stand for the coded packet that broadcasts in round of . In , broadcasts in the corresponding meta-round as follows: computes, ; then uses Reed-Solomon coding on to create packets such that reception of any of these packets is sufficient to reconstruct all elements of ; broadcasts these packets over the course of the rounds of its meta-round.
We now argue that to show that succeeds with probability at least , it suffices to show that with probability at least every node receives at least packets in every meta-round corresponding to a round of in which the node received a broadcasted packet. Node is able to broadcast in a meta-round corresponding to round of if it is able to construct the packets. Node is capable of constructing these packets if it is able to compute all elements of , which it can do if it is able to compute for any where is a round of in which receives from a neighbor . Node is able to compute if in the meta-round corresponding to , receives at least packets. Thus, to show that succeeds with probability at least , it suffices to show that with probability at least all nodes receive at least packets in any meta-round corresponding to a round of in which they receive a coded packet. We show this as follows.
Consider a meta-round where a node is supposed to receive at least packets. The expected number of packets received by the node over the course of the meta-round is . By a Chernoff bound, the probability that a node receives fewer than packets over the course of its meta-round is no greater than . Letting , the probability that a node receives fewer than packets in a meta-round is at most , for a positive constant . By a union bound over the nodes, the probability that any node does not receive at least packets over the course of a meta-round is no greater than . By a union bound over meta-rounds it follows that the probability that any node in any meta-round does not receive at least packets is at most , which is at most , for sufficiently large . Thus, the schedule succeeds in sending messages in rounds with a probability of failure of at most .
Lastly, we need to show that . However, notice that , where and are arbitrarily small by our choice and hence the inequality clearly holds. ∎
5.3 Gaps for Sender Faults with Adaptive Routing
We now use our transformations to derive a shared topology gap of and a worst case topology gap of in the sender fault setting if routing is adaptive. This is a stark departure from the worst case topology gap of the receiver fault setting.
Theorem 27**.**
The shared topology gap is with senders faults and adaptive routing.
Proof.
In [3], a network that has a routing throughput of in the faultless setting is given. A throughput upper bound of in the faultless setting clearly implies a throughput upper bound of in the sender fault setting. The work of [3] also provides a set of coding schedules that achieves a throughput of on the same network in the faultless setting. By Lemma 26, we conclude a coding throughput of in sender fault setting. Thus, we conclude an gap on this topology and so a shared topology gap of . ∎
Theorem 28**.**
The worst case topology gap is in the sender fault setting with adaptive routing.
Proof.
Recall that the worst case topology gap is . We first show that . It is shown in [3] that there exist topologies where coding requires a throughput of in the faultless setting. Note that a throughput upper bound in the faultless setting clearly implies one for the sender fault setting. Additionally, coding can achieve a throughput of in the sender fault setting, by Lemma 12.
We now show . It is shown in [3] that there exist topologies where routing requires a throughput of in the faultless setting, and again we note that a throughput upper bound in the faultless setting clearly implies one for the sender fault setting. The work of [3] also shows that in the faultless setting there exists a set of routing schedules with a throughput of . We conclude, by Lemma 25 it is possible to achieve a routing throughput of in the sender fault setting.
Thus, and and so we conclude that with sender faults and adaptive routing the worst case topology gap is . ∎
Appendix A Single-link Topology Gaps
We show here that with non-adaptive routing on the trivial single-link topology, which consists of exactly two nodes connected by an edge, a shared topology gap of is easily attainable with sender or receiver faults.
Lemma 29**.**
The routing throughput on the single-link topology with constant sender or receiver fault probability but without adaptive schedules is .
Proof.
For concreteness, we assume that in this proof. We first show that the non-adaptive routing throughput on the single-link topology is . We do so by proving that rounds are necessary for broadcasting messages with a probability of failure of at most , for sufficiently large .
Suppose, for the sake of contradiction, that rounds are sufficient for sending messages with a probability of failure of at most by some schedule .
Since every message is sent times on average, by Markov’s inequality there must exist a subset of size for which no message in the subset is sent more than times. Call this subset .
Since succeeds in sending all of the messages with probability at least , it must succeed in sending all messages in with probability at least . Moreover, by construction of , it sends no message in more than times.
We now show that no schedule can succeed in routing messages with probability if it sends no one of these messages more than times. If no message is sent more than times, the probability that a fixed message is not received is at least . Since each message succeeds independently, the probability that all messages are received successfully is and so the probability that some message is not received is , by the inequality . Therefore, we have that the probability that one of the messages is not received is at least , implying that the probability that all messages are received is no greater than . Since for sufficiently large , we conclude that rounds are necessary for broadcasting messages with a probability of failure of at most , for sufficiently large , implying that the throughput is .
We now show that a non-adaptive routing throughput of is achievable on the single-link topology. We do so by sending each message times from the source. The probability that a fixed message is not received is . By a union bound the probability that any message is not received is . Thus, we broadcast messages in rounds with a probability of failure of at most , showing a throughput of .∎
Lemma 30**.**
The coding throughput on the single-link topology with constant fault probability is .
Proof.
A throughput of trivially follows from the fact that rounds are necessary to broadcast.
To show that a throughput of is achievable, we provide a schedule which uses Reed-Solomon codes. Using Reed-Solomon codes it is possible to generate and send packets such that the reception of any packets by the receiver suffices for the receiver to reconstruct the original messages. The source generates and sends these packets. By Chernoff bounds, the probability that fewer than messages are received is bounded from above by , for some appropriate constant . Thus, we succeed in broadcasting messages in rounds with a failure probability of at most , showing a throughput of . ∎
Lemmas 29 and 30 give the following corollary.
Lemma 31**.**
The single-link topology has a coding gap in the receiver/sender fault, non-adaptive routing setting, demonstrating an shared topology gap in this setting.
We now examine a stronger lower bound model - one with adaptive routing. The single-link topology coding gap disappears in this setting.
Lemma 32**.**
The adaptive routing throughput on the single-link topology with receiver/sender faults is .
Proof.
A throughput of trivially follows because rounds are strictly necessary.
We prove a throughput of by providing the following adaptive routing schedule. The source sends each message until it is received, but for no more than rounds in total. For every , let be the random variable that stands for the number of rounds during which the -th message is transmitted and let . Since is a geometric random variable with probability of success , it holds that . By the Chernoff bound for geometric random variables (see Theorem 34), we have that the probability of failure is , which is at most for sufficiently large . Thus, we succeed in sending messages in rounds with a probability of failure of at most , showing a throughput of . ∎
Lemmas 30 and 32 give the following constant gap on the single-link topology.
Lemma 33**.**
For sender or receiver faults, there is a coding gap for the single-link topology if routing is done adaptively.
Appendix B Other Tools
We use the following Chernoff bound for geometric random variables.
Theorem 34** (Doerr [11]).**
Let . Let be independent geometric random variables with for all and let . Then for all ,
[TABLE]
The reference list from the paper itself. Each links out to its DOI / PubMed record.
- 1Ahlswede et al. [2006] R. Ahlswede, Ning Cai, S. Y.R. Li, and R. W. Yeung. Network information flow. IEEE Trans. Inf. Theor. , 46(4):1204–1216, September 2006. ISSN 0018-9448. doi: 10.1109/18.850663 . URL http://dx.doi.org/10.1109/18.850663 .
- 2Alon et al. [1991] Noga Alon, Amotz Bar-Noy, Nathan Linial, and David Peleg. A lower bound for radio broadcast. Journal of Computer and System Sciences , 43(2):290–298, 1991.
- 3Alon et al. [2014] Noga Alon, Mohsen Ghaffari, Bernhard Haeupler, and Majid Khabbazian. Broadcast throughput in radio networks: Routing vs. network coding. ACM-SIAM Symposium on Discrete Algorithms (SODA) 2014 , pages 1831–1843, 2014. doi: 10.1137/1.9781611973402.132 .
- 4Bar-Yehuda and Israeli [1989] R. Bar-Yehuda and A. Israeli. Multiple communication in multi-hop radio networks. In Proceedings of the Eighth Annual ACM Symposium on Principles of Distributed Computing , PODC ’89, pages 329–338, New York, NY, USA, 1989. ACM. ISBN 0-89791-326-4. doi: 10.1145/72981.73005 . URL http://doi.acm.org/10.1145/72981.73005 .
- 5Bar-Yehuda et al. [1992] Reuven Bar-Yehuda, Oded Goldreich, and Alon Itai. On the time-complexity of broadcast in multi-hop radio networks: An exponential gap between determinism and randomization. Journal of Computer and System Sciences , 45(1):104–126, 1992.
- 6Censor-Hillel et al. [2014] Keren Censor-Hillel, Mohsen Ghaffari, and Fabian Kuhn. A new perspective on vertex connectivity. In Proceedings of the Twenty-fifth Annual ACM-SIAM Symposium on Discrete Algorithms , SODA ’14, pages 546–561, Philadelphia, PA, USA, 2014. Society for Industrial and Applied Mathematics. ISBN 978-1-611973-38-9. URL http://dl.acm.org/citation.cfm?id=2634074.2634115 .
- 7Censor-Hillel et al. [2014] Keren Censor-Hillel, Seth Gilbert, Fabian Kuhn, Nancy A. Lynch, and Calvin C. Newport. Structuring unreliable radio networks. Distributed Computing , 27(1):1–19, 2014. doi: 10.1007/s 00446-013-0198-8 . URL http://dx.doi.org/10.1007/s 00446-013-0198-8 .
- 8Chlamtac and Kutten [1985] I. Chlamtac and S. Kutten. On broadcasting in radio networks - problem analysis and protocol design. IEEE Transactions on Communications , 33(12):1240–1246, December 1985. ISSN 0090-6778. doi: 10.1109/TCOM.1985.1096245 .
