1. The Internet of Things- An Architectural Perspective
Gaurav Awasthi
Software Architect &
Technology Evangelist
@gawasthi22
in.linkedin.com/in/gawasthi

2. 2
What is Internet of things
Internet of Things can be realized in three paradigms:
 Internet-oriented (middleware)
 Things oriented (sensors)
 Semantic-oriented (knowledge)
Definition:
Interconnection of devices, sensors and actuators sharing information
and data across platforms through a unified framework and enabling
innovative business applications. This is achieved by large scale
sensing, analytics and representation using cloud computing and real
time streaming analysis
Primary Goal:
To create situation awareness, to make intelligent decisions and to
respond to dynamics of the environment

3. 3
What does it comprise of ?
DEVICES
CONNECTIVITY
PLATFORM
APPLICATIONS

4. 4
Technology Agnostic view of IOT
FeedbackandDecisions
© AllStuffIOT
THINGS
Internet
Device Data
Data Analytics
Operational
Feedback
Business
Insight
LOCAL ANALYTICS
FeedbackandDecisions

5. 5
Remote Monitoring & VisualizationConnectivity
Data/Device
Management
 Device/Hardware
Firmware
 Sensors
 Reports and Dashboards
 Web, tablet, mobile, PC based applications
 Device Configuration, Monitoring and diagnostics
 Alarms, alerts, notifications
 Advanced analytics, Predictive analytics
Things
Cloud
 Data Models
 Device Management
 Cloud based solution
 Big data solutions
 Platform services
 Connectivity
 Device
Concentrator/Gateways
 Secure Communication
 Communication Interfaces –
NFC, BLE, Zigbees, GSM, GPRS
IOT COMPONENTS

6. MICRO IOT – REMOTE PATIENT MONITORING

7. CONNECTED HOSPITALS – TYPICAL REQUIREMENTS
Command Monitor
Registration/De-Registration of Medical devices
Device Health Monitoring
Patient Data Capture and Upload
Device Configuration data Upload
Software Update on devices
Compliance Requirements and Guidelines like HIPPA, Data Residency
Remote Troubleshooting

8. CONNECTED HOSPITALS – REFERENCE ARCHITECTURE
Gateway
HTTPS
ServiceBus
Device Management
Platform Services
Software Updates
Event
Ingester
Security
Fault
Handling
Audit
Logging
Event
Listener
Solution Portal
Visualization
Reports
Web API
Device
Device
Device
.
.
.
HTTPS
Alerts/
Notification
Rules Engine
Preventive/Predict
ive Maintenance
Green
Compliance
External Interfaces
Social Analytics
Mobile/
Wearable Apps
Device
Storage
Service
Bus
Big Data
Analytics
web services
Energy
Optimization
Enterprise
Applications

9. COMPONENT DESCRIPTION
•The medical devices can either be directly connected to internet or through a gateway.
•In some cases, there could be localized hubs which connect to gateways and then to the
platform
Devices
•There are generally two kind of requirements, one for communicating for large messages
from/to the platform or stream data
•Based on the data type, there are different kind of messaging components to ingest such
data. An ESB on ingress and egress is generally used
Messaging
•For Device Management, service like Software Upload to devices, Configuration data
download from devices, Device Health Service etc. are deployed on the platformDevice Management
•Data storage is generally used for persisting device configuration and device topology
•For Software packages, generally a cloud storage mechanism is usedStorage
Analytics
External Interface
• Big Data Analytics is generally used on data that is present in the database
• Real time Analytics is used for device health purposes on streaming data from devices
• External Interfaces to the platform are supported from Enterprise Service Bus and Data
API

10. DEVICE MANAGEMENT

11. GATEWAY ARCHITECTURE

12. AWS IMPLEMENTATION

13. DEPLOYMENT ARCHITECTURE
Devices
Gateway
Availability Zone 1
Availability Zone 2
Auto Scaling Group
Dashboard
Dashboard
Queueing
Service(SQS)
Storage
(S3)
CDN
(CloudFront)
Auto Scaling Group
Platform
Services
Platform
Services
Elastic Cache
E
l
a
s
t
i
c
L
o
a
d
B
a
l
a
n
c
e
r
Streaming channel
(Kinesis)
Master
RDS
Standby
RDS
Logs
(Cloud Watch)

14. Thank You