[PPT] - Bluetooth Mesh under the Microscope: How much ICN is Inside? Hauke PowerPoint Presentation

SLIDE 1

Bluetooth Mesh under the Microscope: How much ICN is Inside?

Hauke Petersen, Peter Kietzmann, Cenk G¨ undo˘ gan, Thomas C. Schmidt and Matthias W¨ ahlisch

peter.kietzmann@haw-hamburg.de 6th ACM Conference on Information-Centric Networking (ICN 2019) September 26, 2019

SLIDE 2

1

Starting Point

The Bluetooth mesh standard adopted last year is a wireless technology based

n the ICN principles.

[. . . ] It implements all of the major paradigms of information-centric networking in order to enable simplicity, scalability and reliability [. . . ].

SILVAIR. Information-centric networking – a revolutionary

approach to wireless lighting control, 2018. http: // silvair. com/ resources/ information-centric-networking/

SLIDE 3

1

Starting Point

The Bluetooth mesh standard adopted last year is a wireless technology based

n the ICN principles.

[. . . ] It implements all of the major paradigms of information-centric networking in order to enable simplicity, scalability and reliability [. . . ].

SILVAIR. Information-centric networking – a revolutionary

approach to wireless lighting control, 2018. http: // silvair. com/ resources/ information-centric-networking/

What is BT mesh? How does it compare to ICN?

SLIDE 4

2

Related Work

BT mesh ICN

[SILVAIR’18]

BT mesh standard based on ICN principles No technical detail ✓ ✓

[ICN’18]

NDNoT Framework for IoT No technical evaluation ✘ ✓

[SenSys’17]

BLE and BT mesh performance analysis No ICN at all ✓ ✘

[SoftCOM’15]

Service mediation in multi-hop BLE/NDN No comparison in ICN ✘ ✓

[Theses’14]

Bluetooth convergence layer for NetInf No low-power BT ✘ ✓

SLIDE 5

3

Outline

Motivation why we started this work BT mesh overview and comparison to ICN principles Experimental evaluation in the FIT IoT-LAB testbed Outlook how ICN can benefit from BT mesh concepts

SLIDE 6

4

BT mesh overview and comparison to ICN principles

SLIDE 7

5

Bluetooth (BT) Evolution

◮ BT (since 1.0) → BLE (since 4.0) → BT mesh (independent) & BT 5.0++

SLIDE 8

5

Bluetooth (BT) Evolution

◮ BT (since 1.0) → BLE (since 4.0) → BT mesh (independent) & BT 5.0++ ◮ Uses BLE hardware ◮ Enables multi-hop ◮ Adds many-to-one Adds many-to-many

SLIDE 9

6

Stack Organization

Hw Networking Data

Physical Layer Link Layer Bearer Layer Network Layer Lower Transport Layer Upper Transport Layer Access Layer Model Layer Application MAC-to-Face Map ICNLoWPAN NDN/CCNx Application

BT mesh ICN

BT mesh ◮ Full vertical stack ◮ Data model per device type ◮ Publish-subscribe data exchange ◮ Segmentation on transport layer ◮ Tied to single interface BLE radio

SLIDE 10

6

Stack Organization

Hw Networking Data

Physical Layer Link Layer Bearer Layer Network Layer Lower Transport Layer Upper Transport Layer Access Layer Model Layer Application MAC-to-Face Map ICNLoWPAN NDN/CCNx Application

BT mesh ICN

BT mesh ◮ Full vertical stack ◮ Data model per device type ◮ Publish-subscribe data exchange ◮ Segmentation on transport layer ◮ Tied to single interface BLE radio ICN ◮ Relies on supporting protocols ◮ No requirement on format of names ◮ Convergence layer implements compression and segmentation ◮ Allows multi-interface of different types

SLIDE 11

7

MAC and Reliability

BT mesh ◮ TX on 3 broadcast channels ◮ Replicate packets up to 7x a priori → Multiple transmissions / packet → Tweaked according to roles ◮ RX scans on 3 channels consecutively

SLIDE 12

8

Routing and Forwarding

BT mesh ◮ Multi-hop & multi-path by forwarding all packets over broadcast ◮ Managed flooding:

◮ Hop-limit counter ◮ Message cache list known packets ◮ Prevents redundant forwarding ◮ Does not cache content

◮ Native support of group requests

Source: https://www.beaconzone.co.uk/BluetoothMeshBeacons

SLIDE 13

9

Names and Addresses

BT mesh ◮ Group addresses to label data streams

◮ Unassigned ◮ Unicast ◮ Group: map to fixed roles (all relays, all nodes, ...) ◮ Virtual: configurable groups

◮ Setup usually static during deployment ◮ Data is addressed not endpoint → Content centric

SLIDE 14

10

Publish-Subscribe

BT mesh ◮ Publish-subscribe w/o broker ◮ Enabled by broadcasting on link layer ◮ Advertise items to groups (publish) ◮ Filter items on receive (subscribe) ◮ Publish can be solicited for reliability → similar to ICN request/response (Standard advises against)

SLIDE 15

11

BT mesh vs ICN Comparison

BT mesh ICN MAC Broadcast Unspecified Reliability Replication Retransmits on demand Routing No routing FIB based routing Forwarding Managed flooding FIB & PIT based forwarding Names Group addresses for data streams Hierarchical tokenized names for data items Addresses Numeric representation Semantic representation Publish-Subscribe Enabled without broker Workarounds needed to avoid push

SLIDE 16

12

Experimental evaluation in the FIT IoT-LAB testbed

SLIDE 17

13

Testbed Deployment

◮ ARM Cortex-M4F @ 64 MHz ◮ 64 kB RAM, 512 kB ROM ◮ BLE radio on SoC (1 Mbps) ◮ RIOT 2019.04 + NimBLE ◮ ARM Cortex-M3 @ 72 MHz ◮ 64 kB RAM, 512 kB ROM ◮ IEEE 802.15.4 radio (250 kbps) ◮ RIOT 2019.04 + CCN-lite

SLIDE 18

14

Single-hop Topology w/ 10 Nodes

Many-to-one

9 publishers; 100 items/node; 5 s interval

C P1 P2 Pn . . . One-to-many

1 publisher; 100 items; 1 s interval

P C1 C2 Cn . . .

Data flow

n: 9 nodes C: Consumer P: Producer

SLIDE 19

15

Multi-hop Line Topology w/ 10 Nodes

Many-to-one

9 publishers; 100 items/node; 5 s interval

C P1 P2 Pn

Data flow

n: 9 nodes C: Consumer P: Producer One-to-many

1 publisher; 100 items; 1 s interval

P C1 C2 Cn

SLIDE 20

16

Time to Content Arrival

0.0 0.1 0.2 0.3 0.4 Time to Completion [s] 0.0 0.2 0.4 0.6 0.8 1.0 CDF

NDN one-to-many BT mesh one-to-many

0.00 0.01 0.02 0.03 0.04

Single-hop

SLIDE 21

16

Time to Content Arrival

0.0 0.1 0.2 0.3 0.4 Time to Completion [s] 0.0 0.2 0.4 0.6 0.8 1.0 CDF

NDN one-to-many NDN many-to-one BT mesh one-to-many BT mesh many-to-one

0.00 0.01 0.02 0.03 0.04

Single-hop

SLIDE 22

16

Time to Content Arrival

0.0 0.1 0.2 0.3 0.4 Time to Completion [s] 0.0 0.2 0.4 0.6 0.8 1.0 CDF

NDN one-to-many NDN many-to-one BT mesh one-to-many BT mesh many-to-one

0.00 0.01 0.02 0.03 0.04

Retries

Single-hop

SLIDE 23

16

Time to Content Arrival

0.0 0.1 0.2 0.3 0.4 Time to Completion [s] 0.0 0.2 0.4 0.6 0.8 1.0 CDF

NDN one-to-many NDN many-to-one BT mesh one-to-many BT mesh many-to-one

0.00 0.01 0.02 0.03 0.04

1 2 3 4 Time to Completion [s] 0.0 0.2 0.4 0.6 0.8 1.0 CDF

0.0 0.1 0.2 0.3 0.4

Single-hop Multi-hop

SLIDE 24

16

Time to Content Arrival

0.0 0.1 0.2 0.3 0.4 Time to Completion [s] 0.0 0.2 0.4 0.6 0.8 1.0 CDF

NDN one-to-many NDN many-to-one BT mesh one-to-many BT mesh many-to-one

0.00 0.01 0.02 0.03 0.04

1 2 3 4 Time to Completion [s] 0.0 0.2 0.4 0.6 0.8 1.0 CDF Dummy

0.0 0.1 0.2 0.3 0.4

Caching benefit

Single-hop Multi-hop

SLIDE 25

16

Time to Content Arrival

0.0 0.1 0.2 0.3 0.4 Time to Completion [s] 0.0 0.2 0.4 0.6 0.8 1.0 CDF

NDN one-to-many NDN many-to-one BT mesh one-to-many BT mesh many-to-one

0.00 0.01 0.02 0.03 0.04

0.0 0.1 0.2 0.3 0.4 Time to Completion [s] 0.0 0.2 0.4 0.6 0.8 1.0 CDF

NDN one-to-many NDN many-to-one BT mesh one-to-many BT mesh many-to-one

0.00 0.01 0.02 0.03 0.04

1 2 3 4 Time to Completion [s] 0.0 0.2 0.4 0.6 0.8 1.0 CDF Dummy

0.0 0.1 0.2 0.3 0.4

Caching benefit

Single-hop Multi-hop

SLIDE 26

17

Traffic Load: One-to-Many

1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] NDN TX NDN RX Retransmission

Single-hop

SLIDE 27

17

Traffic Load: One-to-Many

1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] NDN TX NDN RX Retransmission Retransmissions

Single-hop

SLIDE 28

17

Traffic Load: One-to-Many

1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] 1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] NDN TX NDN RX Retransmission Retransmissions

Single-hop Multi-hop

SLIDE 29

17

Traffic Load: One-to-Many

1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] Caching benefit 1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] NDN TX NDN RX Retransmission Retransmissions

Single-hop Multi-hop

SLIDE 30

17

Traffic Load: One-to-Many

1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] 1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] NDN TX NDN RX Retransmission BT mesh TX BT mesh RX

Single-hop Multi-hop

SLIDE 31

17

Traffic Load: One-to-Many

1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] 1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] NDN TX NDN RX Retransmission BT mesh TX BT mesh RX

1 2 3 4 5 6 7 8 9 10 Node ID 2 4 6 8 10 Packets [#/103] NDN TX NDN RX Retransmission BT mesh TX BT mesh RX L2 drop

Single-hop

SLIDE 32

17

Traffic Load: One-to-Many

1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] 1 2 3 4 5 6 7 8 9 10 Node ID 0.5 1 1.5 2 Packets [#/103] NDN TX NDN RX Retransmission BT mesh TX BT mesh RX

Single-hop Multi-hop

SLIDE 33

18

Traffic Load: Many-to-One

Redundant replications in BT mesh flood the medium with packets

SLIDE 34

19

Outlook how ICN can benefit from BT mesh concepts

SLIDE 35

20

Low-power Friendship Feature in BT mesh

◮ Integrate battery driven nodes by coupling low-power and friend node ◮ Friend allocates one queue for one low-power node holds messages ◮ Low-power node sleeps and notifies friend on wakeup ◮ Friend delivers messages and drops them Active Node

Establish

SLIDE 36

20

Low-power Friendship Feature in BT mesh

◮ Integrate battery driven nodes by coupling low-power and friend node ◮ Friend allocates one queue for one low-power node holds messages ◮ Low-power node sleeps and notifies friend on wakeup ◮ Friend delivers messages and drops them Active Node Sleeping Node

Establish

SLIDE 37

20

Low-power Friendship Feature in BT mesh

◮ Integrate battery driven nodes by coupling low-power and friend node ◮ Friend allocates one queue for one low-power node holds messages ◮ Low-power node sleeps and notifies friend on wakeup ◮ Friend delivers messages and drops them Active Node Sleeping Node

Establish Notify

SLIDE 38

20

Low-power Friendship Feature in BT mesh

◮ Integrate battery driven nodes by coupling low-power and friend node ◮ Friend allocates one queue for one low-power node holds messages ◮ Low-power node sleeps and notifies friend on wakeup ◮ Friend delivers messages and drops them Active Node Sleeping Node

Establish Notify Deliver

SLIDE 39

21

Use Friend as Deputy Cache in ICN

Friend requests low-power node ◮ Establish PIT state by long-lived Interest ◮ Low-power node answerers on wake-up ◮ Alternatives: HoPP, Interest Notification, ... Active Node Sleeping Node

Establish / Interest Deliver / Data

SLIDE 40

21

Use Friend as Deputy Cache in ICN

Low-power node requests friend ◮ Low-power simply sends Interest ◮ Sleep and retransmit request on next device wake-up Active Node Sleeping Node

Establish / Interest Deliver / Data

SLIDE 41

22

Conclusion

Comparative analysis if BT mesh is an ICN Addressing has analogy but caching is missing Experimental evaluation in different IoT deployments Flooding and replication degrades network performance in BT mesh Applicability for real-world installations Full vertical BT mesh stack covers all aspects Synergies by combining principles of BT mesh and ICN Potential improvements by adopting low-power feature in ICN

SLIDE 42

23

BS 1: Testbed Deployment

Parameters

◮ 4 replications on each node ◮ 20 ms advertisement interval ◮ 3 advertisement channels ◮ 4 Interest retransmits at max. ◮ 1 s retry interval & 10 s Interest t/o ◮ L2 ARQ and CSMA/CA ... default parameters where possible!

SLIDE 43

24

BS 2: Traffic Load: Many-to-One

1 2 3 4 5 6 7 8 9 10 Node ID 100 101 102 103 104 105 106 Packets [#] NDN TX NDN RX Retransmission 1 2 3 4 5 6 7 8 9 10 Node ID 100 101 102 103 104 105 106 Packets [#]

Single-hop Multi-hop

SLIDE 44

24

BS 2: Traffic Load: Many-to-One

1 2 3 4 5 6 7 8 9 10 Node ID 100 101 102 103 104 105 106 Packets [#] NDN TX NDN RX Retransmission BT mesh TX BT mesh RX 1 2 3 4 5 6 7 8 9 10 Node ID 100 101 102 103 104 105 106 Packets [#]