Академический Документы
Профессиональный Документы
Культура Документы
Reference Architecture
for the Internet of Things
Charles Gibbons
architect @ apicrazy.com
19th December 2014
+
IoT need for a reference
architecture
Internet
of
Content
Web 1.0
Web-sites
Search
eMail
HTML
Internet
of
Services
Web 2.0
eCommerce /
eServices
REST
Internet
of
People
Internet
of
Things
Social Media
Mobile
enablement
HTML 5
Things
semantically
represented
in the internet
Active &
Passive
Device to
No single definition for Internet of Things but common features:
device
communicatio
Things have semantic representation in the Internet
n
Different Things may use multiple protocols to communicate with each other
and the internet
The Internet of Things needs a Reference Architecture NB: this ppt is not meant to
be definitive but a point of view on a very interesting domain
+
Things & Server Side
Architecture
Internet-connected wearables
Server Side
Architecture
Protocols
TCP
UDP
XMPP
MQTT &
MQTT-SN
CoAP
HTTP Web
Sockets
Devices
Architecture:
Home
Hubs
Mobile Apps
Web / Portal
Interactions
Interactions
Interactions
Business Support
Systems
Channels
+
A Reference Architecture for IoT
Fulfilment
API Gateway
Interactions
Assurance
Channels:
Service exposition, selfcare, account & device
management
BSS:
Service activation &
mgmt, enrolment
services, contract &
device mgmt,
remediation, trouble
ticketing, billing
Billing
Integration
Interactions
Protocols
TCP
MQTT
HTTP
Web
Sockets
UDP
XMPP
Communications:
Protocols,
Networking &
Addressing
Home
Hubs
..
MQTT-SN
CoAP
SRF and
P2P
Radio
Links
Mesh
.. Radio
Networks
UART /
Coax /
Serial
Lines
3G / 4G /
Gateways
LTE
Other..
Devices:
Independent,
Distributed,
Independently &
Directly Connected
+
IoT Communications & Devices
Devices
are independent
& distributed
Multiple
protocols
Device
network handoff
involve multiple protocols
Communications
involve
complex Networking and
Addressing
One
Communications: Protocols,
Networking & Addressing
TCP
UDP
HTTP
Web
Sockets
MQTT
MQTTSN
CoAP
XMPP
+
IoT Protocols
MQTT -SN
TCP
UDP
MQTT
..
MQTT-SN
HTTP
Web
Sockets
CoAP
XMPP
Communications:
Protocols,
Networking &
Addressing
+
IoT Devices
Home
Hubs
Mesh
.. Radio
Networks
SRF and
P2P
Radio
Links
3G / 4G /
Gateways
LTE
UART /
Coax /
Serial
Lines
Devices: Independent,
Devices:
Distributed, Independently
Independent,
Distributed,
& Directly Connected
Independently &
Directly Connected
Purchased through different
channels
Different versions
Other..
+
Integration: Distributed Service
Layer
An IoT reference architecture is predicated on a distributed service layer capable of integrating IoT BSS
with Devices
The DSL can replace more traditional mobile network OSS by providing transactional idempotent
processes for massively distributed Things
The DSL itself would need to be massively distributed with different capabilities provided by multiple
parties
For example the GSMAs two network elements for secure over the air installation of mobile operator
credentials into a SIM: Subscription Manager Data Preparation (SM-DP) & Subscription Manager
Secure Routing (SM-SR)
Another example would be Zigbees own Gateway which provides a local service layer / service bus
to Zigbee devices
DSL ownership will be either native or procured by the BSS provider as DSL provides standardised
capabilities for ESB & Messaging capabilities and all of the Protocol support, data transformation, policy
enforcement, messaging & persistence necessary to support that service providerss offerings
A service providers will require a DSL connecting to their customer focused BSS domain
+
BSS for IoT
Fulfilment
Assurance
Billing
BSS:
Service activation &
mgmt, enrolment
services, contract &
device mgmt,
remediation, trouble
ticketing, billing
The BSS of IoT needs to be customer / family / business focused with emphasis on Average Revenue
per Device (ARPD). IoT ARPD or the sum IoT ARPU is considerably lower than traditional mobile ARPU.
The cost is also front-loaded into the device rather than the contract. For these reasons the BSS of IoT
must therefore focusing on a low cost device enablement operating model
Fulfilment
Assurance:
Billing:
Remediated billing across different networks, for example M2M (handoff / backhaul / roaming)
+
IoT Channels:
Cases
Mobile Apps
Devices rarely have setup UI and selfinstalled first time connection via
Bluetooth or devices own first time wifi
network to laptop or mobile App
+
Identity & Device Management
TCP
UDP
MQTT
..
MQTT-SN
HTTP
Web
Sockets
CoAP
Home
Hubs
XMPP
..
SRF and
P2P Radio
Links
3G / 4G /
LTE
Mesh
Radio
Networks
UART /
Coax /
Serial
Lines
Gateways
Other..
Device Management
BSS
Channels
+
But Where is the OSS?
The role of the Mobile Network Operator will change because the
Things are connected to the internet rather than to a walled
network
BSS will make use of the semantic service layer and provide
aggregating functions for a complete family of devices
+
Conclusion: IoT Reference
Architeture
Any IoT reference architecture has to scale for the increasing number of interconnected devices:
Interconnected devices will use the most appropriate protocol (e.g. memory & power profiles) and
the most appropriate communication mechanism (e.g. State Transfer Model & Event Based Model)
Intelligent devices will seek to hand-off to the lowest cost network (RFID, Bluetooth, Wifi, Mobile
Network) while maintaining the QoS
The role of the service provider will be to provide intelligence on top of a massively distributed
service layer
Traditional mobile network OSS will be replaced by core capabilities on a service providers
Distributed Service Layer