Toward Efficient Many-to-Many Broadcast in Dynamic Wireless Networks - - PowerPoint PPT Presentation

toward efficient many to many broadcast in dynamic
SMART_READER_LITE
LIVE PREVIEW

Toward Efficient Many-to-Many Broadcast in Dynamic Wireless Networks - - PowerPoint PPT Presentation

Toward Efficient Many-to-Many Broadcast in Dynamic Wireless Networks Fabian Mager , Carsten Herrmann, Marco Zimmerling TU Dresden, Germany Why Many-to-Many? Why Many-to-Many? 1 Why Many-to-Many? 2 Why Many-to-Many? 3 Requirements


slide-1
SLIDE 1

Toward Efficient Many-to-Many Broadcast in Dynamic Wireless Networks

Fabian Mager, Carsten Herrmann, Marco Zimmerling TU Dresden, Germany

slide-2
SLIDE 2

Why Many-to-Many?

slide-3
SLIDE 3

Why Many-to-Many?

1

slide-4
SLIDE 4

Why Many-to-Many?

2

slide-5
SLIDE 5

Why Many-to-Many?

3

slide-6
SLIDE 6

Requirements

slide-7
SLIDE 7

Requirements

  • Dynamic multi-hop networks

4

slide-8
SLIDE 8

Requirements

  • Dynamic multi-hop networks
  • Low latency, high reliability

Controller

Closed-loop control: 10 – 500 ms [1]

[1] Akerberg et al., Future research challenges in wireless sensor and actuator networks targeting industrial automation, IEEE INDIN 2011

Physical process

4

slide-9
SLIDE 9

Requirements

  • Dynamic multi-hop networks
  • Low latency, high reliability
  • Efficiency (energy, costs, etc.)

4

slide-10
SLIDE 10

Current Solutions

slide-11
SLIDE 11

Current Solutions

Multi-Sink Routing [1] Sequential Flooding [2] Current Practice [3] Multi-hop / Mesh yes yes no

[1] Mottola et al., MUSTER: Adaptive Energy-Aware Multisink Routing in Wireless Sensor Networks, IEEE Transactions on Mobile Computing 2011 [2] Ferrari et al., Efficient network flooding and time synchronization with Glossy, ACM/IEEE IPSN 2011 [3] Preiss et al., Crazyswarm: A large nano-quadcopter swarm. IEEE ICRA 2017 5

slide-12
SLIDE 12

Current Solutions

Multi-Sink Routing [1] Sequential Flooding [2] Current Practice [3] Multi-hop / Mesh yes yes no Latency high medium low

[1] Mottola et al., MUSTER: Adaptive Energy-Aware Multisink Routing in Wireless Sensor Networks, IEEE Transactions on Mobile Computing 2011 [2] Ferrari et al., Efficient network flooding and time synchronization with Glossy, ACM/IEEE IPSN 2011 [3] Preiss et al., Crazyswarm: A large nano-quadcopter swarm. IEEE ICRA 2017 5

slide-13
SLIDE 13

Current Solutions

Multi-Sink Routing [1] Sequential Flooding [2] Current Practice [3] Multi-hop / Mesh yes yes no Latency high medium low Dynamic no yes yes

[1] Mottola et al., MUSTER: Adaptive Energy-Aware Multisink Routing in Wireless Sensor Networks, IEEE Transactions on Mobile Computing 2011 [2] Ferrari et al., Efficient network flooding and time synchronization with Glossy, ACM/IEEE IPSN 2011 [3] Preiss et al., Crazyswarm: A large nano-quadcopter swarm. IEEE ICRA 2017 5

slide-14
SLIDE 14

Current Solutions

Multi-Sink Routing [1] Sequential Flooding [2] Current Practice [3] Multi-hop / Mesh yes yes no Latency high medium low Dynamic no yes yes Energy Efficiency medium high low

[1] Mottola et al., MUSTER: Adaptive Energy-Aware Multisink Routing in Wireless Sensor Networks, IEEE Transactions on Mobile Computing 2011 [2] Ferrari et al., Efficient network flooding and time synchronization with Glossy, ACM/IEEE IPSN 2011 [3] Preiss et al., Crazyswarm: A large nano-quadcopter swarm. IEEE ICRA 2017 5

slide-15
SLIDE 15

Our Contribution

Multi-Sink Routing [1] Sequential Flooding [2] Current Practice [3] Mixer Multi-hop / Mesh yes yes no yes Latency high medium low low Dynamic no yes yes yes Energy Efficiency medium high low high

[1] Mottola et al., MUSTER: Adaptive Energy-Aware Multisink Routing in Wireless Sensor Networks, IEEE Transactions on Mobile Computing 2011 [2] Ferrari et al., Efficient network flooding and time synchronization with Glossy, ACM/IEEE IPSN 2011 [3] Preiss et al., Crazyswarm: A large nano-quadcopter swarm. IEEE ICRA 2017 5

slide-16
SLIDE 16

Approach

slide-17
SLIDE 17

Example: All-to-All Communication

  • Using sequential flooding, nodes

flood one after another

6

slide-18
SLIDE 18

Example: All-to-All Communication

  • Using sequential flooding, nodes

flood one after another

6

slide-19
SLIDE 19

Example: All-to-All Communication

  • Using sequential flooding, nodes

flood one after another

6

slide-20
SLIDE 20

Example: All-to-All Communication

  • Using sequential flooding, nodes

flood one after another

6

slide-21
SLIDE 21

Example: All-to-All Communication

  • Using sequential flooding, nodes

flood one after another

6

slide-22
SLIDE 22

Example: All-to-All Communication

  • Using sequential flooding, nodes

flood one after another

6

slide-23
SLIDE 23

Example: All-to-All Communication

  • Using sequential flooding, nodes

flood one after another

6

slide-24
SLIDE 24

Example: All-to-All Communication

  • Using sequential flooding, nodes

flood one after another

6

slide-25
SLIDE 25

Example: All-to-All Communication

  • Using sequential flooding, nodes

flood one after another

6

slide-26
SLIDE 26

Example: All-to-All Communication

  • Using sequential flooding, nodes

flood one after another

6

slide-27
SLIDE 27

Our Key Ideas

  • Overlay floods:

Let nodes send combinations of previously received packets, built with random linear network coding

7

slide-28
SLIDE 28

Our Key Ideas

  • Overlay floods:

Let nodes send combinations of previously received packets, built with random linear network coding

7

slide-29
SLIDE 29

Our Key Ideas

  • Overlay floods:

Let nodes send combinations of previously received packets, built with random linear network coding

7

slide-30
SLIDE 30

Our Key Ideas

  • Overlay floods:

Let nodes send combinations of previously received packets, built with random linear network coding

  • Enable spatial reuse:

Let multiple nodes transmit simultaneously and exploit the capture effect

7

slide-31
SLIDE 31

Our Key Ideas

  • Overlay floods:

Let nodes send combinations of previously received packets, built with random linear network coding

  • Enable spatial reuse:

Let multiple nodes transmit simultaneously and exploit the capture effect

7

slide-32
SLIDE 32

Main Challenges

slide-33
SLIDE 33

Main Challenges

  • 1. When should a node send?
  • 2. What should a node send?
  • 3. How to ensure synchronous transmissions without a global clock?
  • 4. How to achieve an efficient runtime operation?

8

slide-34
SLIDE 34

Main Challenges

  • 1. When should a node send?
  • 2. What should a node send?
  • 3. How to ensure synchronous transmissions without a global clock?
  • 4. How to achieve an efficient runtime operation?

8

slide-35
SLIDE 35

When Should a Node Send?

9

  • Capture effect:

Correctly receive a packet despite interfering transmitters under physical layer specific conditions (e.g. 802.15.4: SINR >= 3dB, △t < 128us)

slide-36
SLIDE 36

When Should a Node Send?

9

  • Capture effect:

Correctly receive a packet despite interfering transmitters under physical layer specific conditions (e.g. 802.15.4: SINR >= 3dB, △t < 128us)

  • Too many à capture unreliable
slide-37
SLIDE 37

When Should a Node Send?

9

  • Capture effect:

Correctly receive a packet despite interfering transmitters under physical layer specific conditions (e.g. 802.15.4: SINR >= 3dB, △t < 128us)

  • Too many à capture unreliable
  • Too few à less spatial reuse
slide-38
SLIDE 38

When Should a Node Send?

  • Capture effect:

Correctly receive a packet despite interfering transmitters under physical layer specific conditions (e.g. 802.15.4: SINR >= 3dB, △t < 128us)

  • Too many à capture unreliable
  • Too few à less spatial reuse
  • Adaptive transmission policy

Choose transmit probability based on local node density

9

slide-39
SLIDE 39

Main Challenges

  • 1. When should a node send?
  • 2. What should a node send?
  • 3. How to ensure synchronous transmissions without a global clock?
  • 4. How to achieve an efficient runtime operation?

10

slide-40
SLIDE 40

What Should a Node Send?

… packet_1 … … packet_2 … … packet_3 … … packet_4 … … … … … packet_n …

11

  • Innovative (linearly independent)

packets are stored in a matrix

slide-41
SLIDE 41

What Should a Node Send?

… packet_1 … … packet_2 … … packet_3 … … packet_4 … … … … … packet_n … Next transmit packet + +

11

  • Innovative (linearly independent)

packets are stored in a matrix

  • Nodes send randomly chosen

combinations of stored packets

slide-42
SLIDE 42

What Should a Node Send?

next transmit packet + +

  • Innovative (linearly independent)

packets are stored in a matrix

  • Nodes send randomly chosen

combinations of stored packets

  • Several rules to make packets more

useful, e.g.:

  • Immediate relay of innovation
  • Boost dissemination of own message

11

… packet_1 … … packet_2 … … packet_3 … … packet_4 … … … … … packet_n …

slide-43
SLIDE 43

Evaluation

slide-44
SLIDE 44

Setup

  • Mixer prototype on TelosB
  • 4 MHz, 16 bit, 10 KB RAM
  • Radio: IEEE 802.15.4
  • FlockLab testbed, ETH Zurich
  • 27 TelosB nodes
  • All-to-all, each node 1 message

12

slide-45
SLIDE 45

Reliability

100%

Mixer delivered all messages in every experiment

13

slide-46
SLIDE 46

Latency

10 30 50 70 90 110 Payload size [bytes] 100 200 300 400 500 Latency [slots]

Mixer SeqF

10 30 50 70 90 110 Payload size [bytes] 0.0 0.5 1.0 1.5 2.0 Latency [s]

Mixer SeqF

14

slide-47
SLIDE 47

Latency

10 30 50 70 90 110 Payload size [bytes] 0.0 0.5 1.0 1.5 2.0 Latency [s]

Mixer SeqF Mixer (new)

10 30 50 70 90 110 Payload size [bytes] 100 200 300 400 500 Latency [slots]

Mixer SeqF Mixer (new)

Mixer outperforms sequential flooding by up to 3.5x

14

slide-48
SLIDE 48

Conclusion

slide-49
SLIDE 49

Conclusion

  • Mixer, a many-to-all communication primitive
  • Made for dynamic wireless multi-hop networks
  • Combines synchronous transmissions and network coding
  • Complete spectrum from 1-to-all to all-to-all
  • Any initial message distribution
  • Versatile, fast, efficient, reliable

15