Future Internet of Things

FUTURE INTERNET OF THINGS
Antonio M. Alberti, Professor & Researcher

(c) Antonio Alberti, Inatel, 2014.
FOR TOO LONG WE TALK ABOUT TECHNOLOGICAL
EVOLUTION AND THE RATE AT WHICH IT OCCURS.

VERY OFTEN, PEOPLE CITE MOORE'S LAW AS AN
EXAMPLE OF LAW CAPABLE OF PREDICTING
TECHNOLOGICAL DEVELOPMENTS IN COMPUTING POWER.
Gordon Moore, 2004.

“THE QUANTITY OF
TRANSISTORS THAT
CAN BE PLACED
INEXPENSIVELY ON
AN INTEGRATED
CIRCUIT HAS
DOUBLED
APPROXIMATELY
EVERY TWO YEARS.”

MORE RECENTLY, RAYMOND KURZWEIL PRESENTED A
THEORY FOR TECHNOLOGICAL EVOLUTION AND A NEW
LAW THAT EXPANDS MOORE LAW TO DESCRIBE THE
EXPONENTIAL GROWTH OF TECHNOLOGICAL ADVANCES
THE LAW OF
ACCELERATING
RETURNS

t
e
e

ABUNDANCE: THE FUTURE
IS BETTER THAN YOU THINK
PETER H. DIAMANDIS
STEVEN KOTLER

DISRUPTION
SOFTWERIZATION
UBBERIZATION
INTERNET OF THINGS
CLOUD, BIG DATA

UBIQUITY
DEVICES EVERYWHERE
SMART DUST
PROGRAMMABLE MATTER

MINIATURIZATION
CENTIMETER
MICROMETER
NANOMETER
INTERNET OF MICRO &
NANO THINGS
Anders
?

Networks Clouds= +
Telecom
& Internet
IT & Web
“Things” +
Machine to
machine
& Internet of
Things
+
Identity,
Credentials,
Biometrics
OUR MODEL

User-centric
Self-*, Context
Information-centricService-centric
Software-Defined
Security
Privacy
Naming
Nam
e
Resolution
Virtualization
Internet of Things
Exposition, Orchestration
Self-Certifying
Life-Cycling
ProtocolDevelopment
Mobility
ID/LocSplitting
M
ngt. and
Control
Design Space
(2015)

NOVAGENESIS
WHAT IS DIFFERENT?

INITIAL CORNERSTONES
ú NAMING
ú LIFE-CYCLING

NAMING
ú TO DENOTE ENTITIES USING SYMBOLS.
ú NOVAGENESIS EMPLOYS SELF-VERIFYING
NAMES.
ú NO LIMIT ON NAMESPACES AND NAME
RESOLUTION.

Self-certifying names generated from existences’ immutable patterns.
Name binding among namespaces enable to represent relationships.
Antony
Image.jpg
AA180972
…
01011223
…
0101010101010101011010110001010010101010101010101
1010101011110100001010011111111110101010100000000
1001010101000101010101011111110000000000000000000
1010101010101010101000010010101010101010101010101
1111111010101010100001010010100101010100010101010
0100000100000010000000001000001000000100000010000
1110000010000000100000010110101111000011100000000
1111111010101010100001010010100101010100010101010
0100000100000010000000001000001000000100000010000
1110000010000000100000010110101111000011100000000
1111111101111110111111011111101111101111101111111
My Smartphone
BFEF1216
…
NAMING AND NAME BINDING
Natural language names: Portuguese, English, etc.

Future Internet of “Things”: Naming
certain key. For example, the name Router 1 is bound to the names OS 6 and OS 7, while OS 6 can be resolved to
Process 10 and Process 11.
Fig. 3. Graph of names and their bindings representing entities relationships in computer systems.

LIFE-CYCLING OF ENTITIES
ú THE PROCESS OF EXPOSING, SEARCHING
FOR PEERS, NEGOTIATING, CONTRACTING,
OPERATING, AND RELEASING.

Antony
App 1
App 2
ScalifaxMy smartphone
My tablet
My photos
repository app
I have Antony
photos!
I store
Antony
photos!
I have Antony
photos!
(c) Antonio Alberti 2015,
Inatel - All rights reserved.
EXPOSITION AND DISCOVERY

NEGOTIATION
Let’s work
together?
Let’s work
together?
Let’s work
together?
Antony
App 1
App 2
Scalifax
My smartphone
My tablet
My photos
repository app
SLA
SLA

INFORMATION EXCHANGING
Here are my
photos!
Ok!Here are my
photos!
Antony
App 1
App 2
Meu tablet
My photos
repository app

PROVENANCE AND TRACEABILITY
Antony
App 1
App 2
My tablet
My photos
repository app
Photo <-> Repos. App <-> Scalifax <-> My
smartphone <-> App 1 <-> Antony

COMMUNICATION MODEL
Future
Owner
publishes Internet
Minimization
of spam
problem!
Receiver
subscribes
only the
desired
content.

MOBILITY
ID=FFFF12211243865…
LOC=FEFEF1421412411…
ID=FFFF12211243865…
LOC=AAAA2734573453…
Local Net 2Local Net 1
Future

“THINGS” NEED SERVICES TO REPRESENT
THEM TOWARDS CONTRACT-BASED
TRUSTABLE SELF-ORGANIZATION
Proxy/Gateways
Controllers/
Managers
SERVICES SWARMS
SOCIAL “THINGS” SWARMS
Future Internet of “Things”: Service composition

Smart Convergent Information Architecture
Physical World
Self-Organizing
Physical World Representatives
People
Policies, Rules, Regulations, etc.
Self-Organizing
Assistants, Controllers, Managers, etc.
Evolutionary
Pressures
Environmental
Pressures
The Essence of NovaGenesis Model

Current Proof-of-the-Concept Implementation
HOST 2HOST 1
PGSPSS HTSApp PGSGIRS
HOST 3
HTSPGS
HOST 4
HTSPGS
Publish/subscribe (pub/sub)
Service:
Does the rendezvous among
publishers/subscribers.
Has an application programming
interface (API), which has 5
primitives:
1. Publishes a NB (and a content, if
any);
2. Subscribes a NB (and content, if
any);
3. Notifies peer services about NB
(and content) published;
4. Revokes a publication;
5. Delivers name bindings and related
contents.
Generic indirection resolution service (GIRS):
Selects a hash table service (HTS) to store name
bindings and to cache content.
Proxy/Gateway Service (PGS):
Encapsulates NovaGenesis messages directly over
Ethernet/Wi-Fi/Bluetooth.

NovaGenesis pub/sub API can be seen as a service access point (SAP) between NG Layer and NG application
layer. The client application is a sink for the raw data measured by sensing devices. In the next subsections, we
describe these new services proposed in this paper to extend NovaGenesis towards IoT.
Fig. 5. Layer stack for NG IoT model. Wi-Fi can be replace by IEEE802.15.4, Bluetooth low energy (BLE) or ZigBee.
4.1. New Services for IoT
Future Internet of “Things”: Implemented Services

Future Internet of “Things”: Initialization, Exposition, Discovery

Future Internet of “Things”: Service Offer
Fig. 6. Specification of NovaGenesis IoT services. Initialization, exposition, discovery, and EPGS service offering steps.

Future Internet of “Things”: Acceptance and Info Exchanging
services that subscribe the acceptance objects. The NRS delivers them to the EPGS and client app, where they
are locally stored. This procedure finishes SLA establishment among services in the raw data IoT chain.
Fig. 7. PGCS service acceptance and data publishing steps.

Nó#de#Internet#das#coisas##
medindo#temperatura#da#sala#
Amostras##
de#temperatura#
transportadas#
sem#TCP/IP,##
somente#NG##
sobre#Wi<Fi#
Fig. 8. Experimental scenario with: (i) NovaGenesis core services and IoT client application in the left; (ii) the NovaGen
embedded proxy/gateway (EPGS) on NXP’s LPC1769 device in the middle; and (iii) a computer with LPCXpressoTM
to com
and deploy the EPGS (plus EventOSTM
) image on LPC.
ng -m --cl 0.1 [ < 1 s 28FD4420 > < 4 s 0BD95286 ED12F3ED 7E764DC1 4D623F20 > < 4 s empty empty empty empty > ]
Future Internet of “Things”: The NovaGenesis Model

Cognitive Radio in the Context of IoT using a Novel Future Internet
Architecture Called NovaGenesis
Sensing Cell
Controller
Sensing Information
Storage and Analysis
Sensing Cell
Sensing Cell
Controller
Sensing Cell
Sensing Cell
Controller
Sensing Cell
TCP/IP
Internet
TCP/IP
TCP/IP
...
...
Radio M2 Internet
Radio M1
IoT Network
Boundary
Sensing Cell
Boundary
Border
Router
Sensing Cell SC1
Sensing Cell SC2
Mint
SCC1
SCC2
SISA
Interferer
Range
Interferer
(a) (b)
Figure 1: Cognitive Radio blocks in the context of IoT.

k
k
l
l
m
Figure 10: Example of two applications in a simple link scenario.
TCP/IP
Ethernet
SCC IO
TCP/IP
SC
PUSH/
PULL IA DAO
Ethernet
SISA DB
CLIENT/SERVER CLIENT/SERVER
EthernetEthernet
PUSH/PULL
Figure 11: Stack for cooperative spectrum sensing based on TCP/IP and
ZeroMQ (ZMQ) push/pull.
Naming: Content and services are accessed using their self-
verifying names (SVNes). Message forwarding/routing also
In NovaGenesis, the NRS does a similar role, but using pub/sub
of domain name records.
Limited Service-Orientation: In ZMQ/Internet, the
service-oriented design (SOD) is employed only on the WWW,
while in NovaGenesis it is for all services, including network-
ing ones.
Life-cycling: It encompasses the dynamic composition of
services and their contents. In the Internet architecture it is
present only at WWW. In NovaGenesis, life-cycling is intrin-
sic to any entity: content, services, operating systems, hosts,
etc. The same pattern happens for contract-based operation.
Deployment in Hosts: Internet protocols are implemented at
the core of operating systems. NovaGenesis protocols in hosts
are implemented as services that follow SOD paradigm.
3.6. Next Steps and Open Challenges
We plan to implement the complete Figure 1 scenario in
NovaGenesis, with the aim of extending NG services to con-
trol Wi-Fi access points based on RMS decisions. In addition,
we have already applied NovaGenesis implementation for SDN
[45]. We are also extending our name resolution service to hi-
erarchical domains, as an alternative to DNS. We have already
9
over TCP/IP using ZeroMQ2
(ZMQ) push/pull sockets [41] and
delivered to the SSS. Inside NovaGenesis, the SSS changes to
publish/subscribe (pub/sub) model instead of ZMQ’s push/pull,
publishing and subscribing name bindings and information ob-
jects (like SLAs or spectrum samples) to/from name resolution
service (NRS3
).
NG
Ethernet
SCC SSS
PUB/SUB
PGCS
NG
Ethernet
PGCSNRS RMS
TCP/IP
SC
EthernetEthernet
CLIENT/SERVER PUSH/
PULL
Figure 4: Stack for NovaGenesis interoperability with SCC. SSS provides the
interconnection between TCP/IP and NG stacks. SCC sends spectrum samples
to SSS using ZMQ. Inside NG, the communication model is pub/sub.
2ZeroMQ is a library for asynchronous exchanging of messages. In the
push/pull communication model, a push socket distributes a message to one or
more pull sockets, which read the message delivered over TCP/IP.
3NRS is a short term for the set PSS, GIRS and HTS.
spect
ters t
the s
samp
da
from
{
"
}
"
}
"
}
}
7

Figure 9: SSS o↵er in NovaGenesis format to RMS.
SCC SSS NRS RMS
a a
b b
c
c
d
e
e
f
f
g
g
h
h
i
i
i
j
j
k
k
l
l
m
Figure 10: Example of two applications in a simple link scenario.
CLIENT/SERVER CLIENT/SERVERPUSH/PULL
Table 1: Comparison between scenarios with and without NovaGenesis.
Aspect ZMQ and TCP/IP NovaGenesis
Naming TCP socket names
(ports) and IP ad-
dresses
Host, operating system,
services, and content nat-
ural language and self-
verifying names
Name resolution Domain name service
(DNS)
PSS, GIRS and HTS
Comm. model Receiver accepts all Publish/subscribe
Service-oriented
design
Only on the WWW Applied to all software
Life-cycling Service-oriented
architecture, e.g.
RESTful
For all services and con-
tents
Contract-based
operation
Not typical For all services
Protocol imple-
mentation
As Linux kernel com-
ponents
As services that follow
SOD. User space for now
employs SVNes. In contrast, ZMQ and TCP/IP only allows
structured natural language names, which do not have the in-
trinsic security characteristics of SVNes [21].
Name Resolution: In current Internet it is provided by DNS.
In NovaGenesis, the NRS does a similar role, but using pub/sub
of domain name records.
Limited Service-Orientation: In ZMQ/Internet, the
service-oriented design (SOD) is employed only on the WWW,
while in NovaGenesis it is for all services, including network-
ing ones.
Life-cycling: It encompasses the dynamic composition of
services and their contents. In the Internet architecture it is
ike SLAs or spectrum samples) to/from name resolution
e (NRS3
).
NG
Ethernet
SCC SSS
PUB/SUB
PGCS
NG
Ethernet
PGCSNRS RMS
IP
Ethernetnet
CLIENT/SERVER PUSH/
PULL
: Stack for NovaGenesis interoperability with SCC. SSS provides the
nection between TCP/IP and NG stacks. SCC sends spectrum samples
sing ZMQ. Inside NG, the communication model is pub/sub.
oMQ is a library for asynchronous exchanging of messages. In the
l communication model, a push socket distributes a message to one or
ll sockets, which read the message delivered over TCP/IP.
S is a short term for the set PSS, GIRS and HTS.
data: The spectrum energy data is continuously transmitted
from SCC to SSS. The Figure 8 illustrates the format of this
{
"capacities": {
"sensing_freq_min": "100000000",
"sensing_freq_max": "1800000000",
"sensing_bw_min": "1024000",
"sensing_bw_max": "2048000",
"sensing_sectors": "1",
"sensing_direction": "0"
},
"cell_info": {
"scc_id": "5adc8dfc-66a0-11e5-a257-001dbaef596",
"scc_location": "-22.257360, -45.696651"
},
"current_config": {
"sensing_freq_start": ["900000000", "-1" ],
"sensing_freq_stop": ["930000000", "-1"],
"sensing_bw": "2048000"
}
}
Figure 6: Answer transmitted from SCC to SSS.
7

Figure 19: Fragment of a NovaGenesis message transporting a spectrum sample
directly over Ethernet.
Figure 20: Spectrum sensing output obtained using NovaGenesis as transport
network instead of TCP/IP.
Amostras((
transportadas((
sem(TCP/IP,((
Somente(NG((
sobre(Ethernet(
TCP/IP NGTCP/IP
SCC SSS PGCS
NG
PGCSHTS GIRS PSS RMS
SCC - Sensing Cell Controller
SSS - Spectrum Sensing Service
HTS - Hash Table Service
GIRS - Generic Indirection Resolution Service
PSS - Publish/Subscribe Service
PGCS - Proxy/Gateway/Controller Service
RMS - Resource Management Service
LEGEND:
Figure 14: Experimental scenario for the interoperability test of collaborative spectrum sensing with NovaGenesis.
ng -m --cl 0.1 [ < 1 s ... > < 4 s 0BD95286 ED12F3ED 342DD4C5 B8101939 > < 4 s 0BD95286 ED12F3ED 449B0B0C 6FDF0A76 > ]
...
ng -p --b 0.1 [ < 1 s 2 > < 1 s 19656CF3 > < 1 s 342DD4C5 > ]
ng -p --b 0.1 [ < 1 s 1 > < 1 s 19656CF3 > < 1 s Wi-Fi > ]
...
ng -message --type 0.1 [ < 1 s 1 > ]
Serviços)desenvolvidos)para)o)protó1po.)

Next Scenario for Cognitive Radio for IoT with NovaGenesis
SCC - Sensing Cell Controller
SSS - Spectrum Sensing Service
PGCS - Proxy/Gateway/Controller Service
RMS - Resource Management Service
APS - Access Point Service
EPGS - Embedded Proxy/Gateway Service
POXS - Python OpenFlow Controller Service
SCC
SSS
RMS
APSPOXS
PGCS
TI cc2650
momote
802.15.4
BLE
DOCKER COOJA
NÓS VIRTUAIS
Wi-Fi

Future Internet of Things

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (18)

Destaque

Destaque (20)

Semelhante a Future Internet of Things

Semelhante a Future Internet of Things (20)

Mais de Antonio Marcos Alberti

Mais de Antonio Marcos Alberti (20)

Último

Último (20)

Future Internet of Things