39
www.blackbird420.com How The Next Generation Will Connect Wirelessly Copyright © Blackbird Technology

How The Next Generation Will Connect Wirelessly

Embed Size (px)

DESCRIPTION

An overview of DASH7 wireless technology in 2012 by Blackbird Technology. First half for non-technical audiences, second half more technical but hopefully readable by non-technical audiences.

Citation preview

Page 1: How The Next Generation Will Connect Wirelessly

www.blackbird420.com

How The NextGenerationWill ConnectWirelessly

Copyright © Blackbird Technology

Page 2: How The Next Generation Will Connect Wirelessly

DASH7 Mode 2 Adopted

First OpenTag Demos

50+ Alliance Members

Multiple Silicon Providers

2011 - Present

2009-2010

DoD RFID III Contract ($429MM; ISO 18000-7)

DASH7 Alliance Founded

DoD RFID II Contract ($90MM; proprietary

Savi technology)

RFI for ISO 18000-7Devices

2003-2008

DASH7 Timeline

Copyright © Blackbird Technology

Page 3: How The Next Generation Will Connect Wirelessly

DASH7: Does What Bluetooth & WiFi Can’t

Range

Batte

ry*Life

Co0exist*w

ith*802.11n

Penetra

tes*C

oncrete

"Bends"*A

round*Metal,*Penetrates*W

alls

Globally*Available*Frequency

Ad*Hoc*Networkin

gBroadcast*A

ddressing

Multi0Ho

pTracks*Moving*T

hings

Data*Rate

Defines*Use*of*Public*Key*Crypto

Open*So

urce*Stack

Full*O

pen*ISO*or*IEEE*Standard

Protocol*Stack*<

20kb

Third*Party*Interoperability*C

ertifica

tion

DASH7

ZigBeeBluetooth*LEWiFi

Copyright © Blackbird Technology

Page 4: How The Next Generation Will Connect Wirelessly

Copyright © DASH7 Alliance

Use Case #1

Mobile Advertising With DASH7

Copyright © Blackbird Technology

Page 5: How The Next Generation Will Connect Wirelessly

Hillary7 mutual friends

Listening to “The Rushing Wind” by Enation

www.blackbird420.com

DASH7 Can Broadcast to Hundreds of People At The Same Time ...(WiFi and Bluetooth Cannot)

Use Case #1-ASocial Discovery With DASH7

Page 6: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

Use Case #2

In-Vehicle Automotive

Sensing with DASH7

Copyright © Blackbird Technology

Page 7: How The Next Generation Will Connect Wirelessly

Copyright © DASH7 Alliance

Use Case #3

Building Automation & Smart Energy With DASH7

Copyright © Blackbird Technology

Page 8: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

Use Case #4:

Perishables & Pharmaceuticals

Tracking With DASH7

Page 9: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

Use Case #5:Rights & Entitlements Monitoring With DASH7

Page 10: How The Next Generation Will Connect Wirelessly

Many Other Use Cases!

• Employee Tracking

• Hazardous Materials Tracking

• Anti-theft tags

• IT asset tracking

• Contactless payments

• Vehicle tracking

• Animal tracking

• Lumber supply chains

• Pandemic support

• Yard management

• Warehouse management

• Digital signage

• Oil & Gas Supply Chains

• Construction Tools Tracking

• Home Healthcare

• Patient/infant tracking

• Bridge, Tunnel Stress Monitoring

• Many more ...

Page 11: How The Next Generation Will Connect Wirelessly

Maintaining Privacy With DASH7

• Not too different from WiFi or BT• DASH7 can be “invisible”• Supports AES-128 in MAC• Supports other public/private key exchange in

Network Layer• Independent of NFC security settings

Page 12: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

Making DASH7 “Invisible” To Unwanted Eavesdroppers

Broadcast settings can be adjusted from “full public broadcast of everything” to “invisible mode”

“Invisible mode” allows user’s radio to only acknowledge other DASH7 devices that are pre-

approved

Over-the-air transmissions can be encrypted using public or private key systems

Unlike Bluetooth, DASH7 does not require discovery beacons, so it can be completely invisible

while functioning

Page 13: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

How Does DASH7 Security & Privacy Compare?

DASH7 WiFi BT Cellular

Supports AES 128 Yes Yes Yes Yes

Listen-Before-Talk Yes Yes No No

Encrypted File System Yes No No No

Make “Invisible” To Non-approved Devices Yes No No No

Page 14: How The Next Generation Will Connect Wirelessly

14

DASH7 uses the same antenna & (basically) the same silicon as NFC, apart from a single analog circuit

DASH7 operates at the 32nd harmonic above

13.56 MHz

NFC and DASH7 Today

(13.56 x 32 = 433.92)

No Additional Radio Required

Non-integrated Solution: 3 chips + passives, 1 antenna

Next Gen NFC Chips NFC operates at 13.56

MHz worldwide

DASH7 operates at 433.92 MHz worldwide

Integrated Solution: 1 chip + passives, 1 antenna

Blackbird Confidential

NFC is being deployed by nearly all

major handset, wireless c

arrier, and

point of sale vendors

DASH7 & Smartphones

Page 15: How The Next Generation Will Connect Wirelessly

NFC + DASH7 Combo Chip ConceptDASH7 can be added to an NFC chipset & solution with minimal additions

NFC13.56 MHz Capacitive

Match

NFC +DASH7

13.56 MHz Cap Match

433 MHz Cap Extension

Modern RF interface chipsets are primarily digital.

DASH7 uses GFSK modulation, which is similar to NFC modulation.- Digital blocks remain intact

In concept, adding DASH7 to NFC is accomplished by adding an Integer-N PLL and a small number of analog switches.- Integer-N PLL for 13.56 MHz input with: Divider Ref = 128, Multiplier N = 4096 ± 7- Analog switches to tune antenna at 13.56 or 433- DASH7 uses much less output power than NFC

433 MHz DASH7 spectrum is low enough and narrow enough that normal SiO2 fabrication is OK.

Page 16: How The Next Generation Will Connect Wirelessly

The Power ScaleDASH7 is an aggressively low-power technology

0 - 1 µW 1 - 10 µW 10 - 100 µW 0.1 - 1 mW 1 - 10 mW 10 - 100 mW 0.1 - 1 W 1 - 10 W 10 - 100 W

DASH7Endpoint

DASH7Subctrlr

802.15.4Coord.

DASH7Gateway

802.15.4Endpoint

802.15.4Gateway

BLESlave

RunningiMac

Runninglaptop

Running3G Modem

802.11Device

RunningGPS chip

Upper limit forenergy harvesting

Upper limit forMultiyear battery

Li-Thionylself-discharge

BackgroundRF energy

BluetoothSlave

BluetoothMaster

Page 17: How The Next Generation Will Connect Wirelessly

The Power ScaleTypical DASH7 apps have low-latency, ad-hoc requirements and 10-10000 uW power limits

0 - 1 µW 1 - 10 µW 10 - 100 µW 0.1 - 1 mW 1 - 10 mW 10 - 100 mW 0.1 - 1 W 1 - 10 W 10 - 100 W

DASH7Endpoint

DASH7Subctrlr

802.15.4Coord.

DASH7Gateway

802.15.4Endpoint

802.15.4Gateway

BluetoothSlave

BLESlave

BluetoothMaster

802.11Device

Target Range for Remote Devices

(“Widgets”)

Target Range for “Always-On” Handset

Apps

Page 18: How The Next Generation Will Connect Wirelessly

DASH7 NFC

Powered-Master/Unpowered-Slave

Powered-Master/Powered-Slave

Data Rate(inverse packet length)

N/A ~200 mW / 0 mW(~10 cm)

~30mW / ~30mW(~200m)

~60 mW / ~60 mW(~2m)

28 - 200 kbps 106 - 424 kbps

Typical Active-Mode Power Usage in DASH7 and NFCAdvanced chipsets and duty-cycling can reduce power in either case

Page 19: How The Next Generation Will Connect Wirelessly

RX/TX Power (3V, 0dBm) Examples

Mature Silicon

State of the Art Silicon

Next-gen Research

45mW / 45mW TI CC4309mW / 14mW Energy Micro Prototype1mW / 8 mW (contact Blackbird)

Duty Cycling Reduces Power, Increases LatencyDuty cycling is practical, though, because DASH7 has ad-hoc “wakeup” features

At 100% Duty Cycle, power-usage is dependent on the chip technology

Typ. Duty Cycle Worst-Case Latency Base Power (mature)

Remote Sensor

“Always-on” Listen

Extreme-Heavy Use

0.05% 2 s 30 µW5% 25 ms 2.25 mW20% 10 ms 9 mW

At reduced duty cycles, latency is 5 ms + approximate inverse of the 1ms duty

Page 20: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

More Technical Stuff

• DASH7 has a different philosophy than IEEE 802 has.

• Because of this, it is best suited for applications that 802-based technologies can’t really do.

• Building DASH7 applications is all about designing queries

• DASH7 can still do IP

• There is a growing number of tool packages available for DASH7 development, including software and hardware

Page 21: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

DASH7 is a 2nd Generation M2M+WSN+IoT+RFID Technology

433 MHz band8 channels

Compact Stack16-32KB

Optimized forMicro Power

Optimized forLow Latency(Bursty Data)

Universal Interoperability

Adaptive Data Rate28 - 200 kbps

Very FastMulticast

Page 22: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

OpenTag is an Open-Source Firmware Stack for DASH7http://www.sourceforge.net/projects/opentag

Written in C (Internal C API)

Portable to most MCUs

Built-in minimal RTOS

Built-in Filesystem & I/O

External Messaging API

Page 23: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

Application Client/MasterMany Kinds of

Applications can be Built on Top of

OpenTag + DASH7

DASH7 is Best Suited for Applications with a lot of Uncertainty or Chaos…

Application Service

Application Service

Application Service

Page 24: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

Problem:Traditional Internet Technologies (e.g.TCP+HTTP, 6lowPAN+CoAP, etc) Do Not Tolerate Chaos…

Page 25: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

… These kinds of technologies are designed to route application data from one known address to another known address, across

multiple hub & spoke networks.

The connections must be established, maintained, and cached,or else the message does not get through.

IP: 71.56.240.219

IP: 150.192.48.158

Page 26: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

DASH7 Tolerates Chaos Because it

Does Not Need Routers

Addressing can be done using any kind of data,

via built-in querying

Page 27: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

IP Gateway

Nodes that don’t pass the query stay quietNote: IP addressing

and CoAP are still possible over DASH7

The Internet

No ICMP, no caching, no connection maintenance

required on IP gateway

DASH7 can excel in “open-loop” data acquisition & M2M applications that are difficult or impractical to solve with switch-routed technologies

Page 28: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

DASH7 Networking Process vs. 6loWPAN Process

Advertise Continuously

Cache Addresses from Responses

Assign Multicast Address to Target Devices

Send UDP Packet Containing Query Header

Receive Qualified Responses

Send UDP Packet to Assigned Multicast Address

Receive Qualified Responses

DASH7 Process 6loWPAN Process (Traditional IEEE 802)

Time Base:0.1’s of sec

Time Base:10’s of sec

Page 29: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

DASH7 Networking Process vs. 6loWPAN Process

Advertise Continuously

Cache Addresses from Responses

Assign Multicast Address to Target Devices

Send UDP Packet Containing Query Header

Receive Qualified Responses

Send UDP Packet to Assigned Multicast Address

Receive Qualified Responses

DASH7 Process 6loWPAN Process (Traditional IEEE 802)

Time Base:0.1’s of sec

Time Base:10’s of sec

There are some caveats:‣ DASH7 is (in practice) limited to 2 hops‣ DASH7 requires a greater degree of stack

standardization in order to do querying interoperably.

Page 30: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

DASH7 Applications vs. 6loWPAN Applications

DASH7 Apps Ask: “What are you looking for?”

6loWPAN Apps Ask: “Who gets it?”

I need to find everyone in the lobby, now, who wants to go to floor 10.

I need data from all sensors within 50m that check for Carbon Monoxide

All devices that came off the boat from Taipei shall go to RF Channel 04 and await further instructions.

Deliver a message to the device with address 05:85:245:192:96:0:147:1 to turn its lights off.

Deliver a message to the devices with group address 124:0:8:255:37:160:0:1 instructing them to report sensor logs.

Ping device 63:102:0:80:128:0:17:44 to see if it is still in the network.

Page 31: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

DASH7 Applications vs. 6loWPAN Applications

DASH7 Apps Ask: “What are you looking for?”

6loWPAN Apps Ask: “Who gets it?”

I need to find everyone in the lobby, now, who wants to go to floor 10.

I need data from all sensors within 50m that check for Carbon Monoxide

All devices that came off the boat from Taipei shall go to RF Channel 04 and await further instructions.

Deliver a message to the device with address 05:85:245:192:96:0:147:1 to turn its lights off.

Deliver a message to the devices with group address 124:0:8:255:37:160:0:1 instructing them to report sensor logs.

Ping device 63:102:0:80:128:0:17:44 to see if it is still in the network.

Querying Sounds Great:How can I do it? (stay tuned)

Page 32: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

Running Queries:Let DASH7 find the needle(s) in the haystack

Page 33: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

DASH7 Puts the Query Below the Application Layer

Result: Intrinsic, Interoperable, Query-driven Multicasting

Requirement: Standardized, Integrated Filesystem

OSI LayerOSI Layer DASH7 Components

7 Application UDP-based or LLDP-based

6 Presentation M2 Filesystem

5 Session Dialog Stack

4 Transport M2QP

3 Network M2NP, M2DP, M2AdvP

2 Data Link DASH7 MAC

1 Physical 433 MHz GFSK

DASH7 Queries Start at the Transport LayerDASH7 Queries Start at the Transport LayerDASH7 Queries Start at the Transport Layer

Page 34: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

DASH7 Puts the Query Below the Application Layer

Result: Intrinsic, Interoperable, Query-driven Multicasting

Requirement: Standardized, Integrated Filesystem

OSI LayerOSI Layer DASH7 Components

7 Application UDP-based or LLDP-based

6 Presentation M2 Filesystem

5 Session Dialog Stack

4 Transport M2QP

3 Network M2NP, M2DP, M2AdvP

2 Data Link DASH7 MAC

1 Physical 433 MHz GFSK

DASH7 Queries Start at the Transport LayerDASH7 Queries Start at the Transport LayerDASH7 Queries Start at the Transport Layer

Switch-routed technologies can do queries in their application layers, but this is too high-

up to save the network from collisions.

Page 35: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

Configuring a DASH7 QueryThe Query contains several parameters that go into the protocol

Query Mode

Single Query

SequentialQuery

Query Comparison

Text/BinaryToken

Arithmetic Expression

RegEx

Query Target Data

Single File

BatchFiles

Page 36: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

Sequential Querying: Example

Global Query

Find all lamps that were manufactured by Company X, have a solar panel, and have not been serviced for 1 year or more. Have them respond with their locations.

• Request: Manufacturer = Company X

• Response window set to 0ms because we don’t care yet

• Result: 1950 devices enter query process

Page 37: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

Sequential Querying: Example

Global Query

Find all lamps that were manufactured by Company X, have a solar panel, and have not been serviced for 1 year or more. Have them respond with their locations.

• Request: Manufacturer = Company X

• Response window set to 0ms because we don’t care yet

• Result: 1950 devices enter query process

SubQuery 1

• Request: Addons = “*solar*”

• Response window set to 0ms because we don’t care yet

• Result: 120/1950 devices stay in query (the rest go back to idle)

Page 38: How The Next Generation Will Connect Wirelessly

Copyright © Blackbird Technology

Sequential Querying: Example

Global Query

Find all lamps that were manufactured by Company X, have a solar panel, and have not been serviced for 1 year or more. Have them respond with their locations.

• Request: Manufacturer = Company X

• Response window set to 0ms because we don’t care yet

• Result: 1950 devices enter query process

SubQuery 1

• Request: Addons = “*solar*”

• Response window set to 0ms because we don’t care yet

• Result: 120/1950 devices stay in query (the rest go back to idle)

SubQuery 2• Request:

Last Cold Boot > 1 year ago

• Response window set to 1 sec

• Result: 8/120 devices return their location coordinates