IoT Analytics

IoT Platform Reference Architecture

1 May 11, 2024
IoT Platform Reference Architecture
IoT Building Blocks

Silicon IoT Devices Gateways Networks Solution and Applications

Cloud
Energy and
Insurance
Utilities

Consumer
Smarter Cities
Electronics

IoT Platform
Connected Vehicle Transport and Rail

Life Science and

Industrial Products
Healthcare

End-to-end IoT solution

End-to-end IoT security

 Introduction to Reference Architecture
What is a Reference Architecture? Why is a Reference Architecture Important?

 When we construct a house or building there  It describes what the major foundational
are always certain common components, components or candidate building blocks of an
such as: end-to-end architecture solution
– Foundations
– Water Infrastructure  It spans all industries and all solution areas
– Electrical Infrastructure  It provides a common language
– Telecommunications
– Heating and Cooling  It provides a framework for scope identification,
roadmap definition, risk assessment, and gap
 Similarly, there are common components
assessment
that all information on demand
environments share  Reference Architecture reduces the complexity,
cost, and risk of solution deployment and sets
the foundation for delivering on the promise of
Internet of Things (IoT)
4
 IOT Reference Architecture – High Level System Context
IoT Enabled Assets

User Community

Insights
Sensor data

IoT Platform

Enterprise Systems Other

Third Party Systems
Systems

5
 Key architecture considerations
Architecture Pattern  Develop Platform independent APIs : RESTful web API that are accessible to
 Choose appropriate architecture pattern that creates well balanced system internal and enterprise applications.
(micro services, n-tires , Server Less)  Apply Data Partition techniques to balance out performance, throughput, and
 Asynchronous messaging and eventual consistency. Use Asynchronous scalability of a system
messaging to decouple services, and increase reliability and scalability  Open Communication Standards (Wi-Fi, GPRS, MQTT, REST API, HTTPS)
 Apply Design principles : Design for scale, Design for self heal and Security by  Security : Ensure Device Security (TLS/x509), Application Security (Data in Flight
Design HTTPS/Secure FTP), Data Security ( Data @ Rest Encryption)

Scalability
 Scalable Cloud Based IoT Platform for current and future volume  Build Cloud based Application for maximum Scalability
 Auto scale based Run time and Services  Can work seamlessly with On-Premise Applications using Secure Gateway
 Multi Geo ( e.g. across Geography )

Modularity
 Architecture is designed to isolate impact on the legacy systems and enabling  DevOps enables continuous delivery and full development life cycle
ease of migration and integration management
 Modular architecture for Devices & Network, Device Connectivity, Platform to  Enables Planning for Phase-wise Delivery for Quick Time To Market
Integrate Services with Rules, Analytics and Database Engines, and Delivery  Components should be portable and Apply Decoupling and Cohesion principles
Platform

Extensibility
 Solution decouples application layer, Middleware layer and Device Management  Any Enterprise application could connect with ease with REST API and Secure
layer to accommodate and synchronise different variety, volume and velocity of End Points
data moving from devices to cloud (bidirectional)  Flexible architecture which enables you to select best-in-class components,
6 Applications and vendors based on business needs
 IoT Reference Architecture : Conceptual Architecture
User Community

IoT Enabled Appliances IoT Platform

Device Connect & Collect Core Functions Deliver and Visualization

Applications Notification

Security

Analytics & Insights

Data Store

Integration

Security

Other
Enterprise Systems Third Party Systems
Systems

7
 IoT Reference Architecture : Functional Architecture
User Community

IoT Platform

Device Connect & Collect Core Functions Deliver and Visualization

Device Registry Applications Notification

Event User & Role
Management Based Access
Horizontal Push
Device Security Mobile Notification
Application SMS
Device Rule & Alert
Management Management Web Vertical
Device Connect Application Email
Security

Analytics & Insights

Data Store
Raw Device Data Descriptive Machine learning
Analytical Data
Content Data Geospatial Analytics
Operational Data Master & Predictive
Reference Data Prescriptive

Real Time Near Realtime Integration

Batch
Web
API Queue Pub-Sub
Services

Secure Security Data

Access GDPR Encryption

Other
Enterprise Systems Third Party Systems
Systems
Asset Management Weather SMS Gateway
ERP Other
System
Facility Management Push Notification
Enterprise LDAP CRM GIS Map Social Media Email Gateway
8
 IoT Reference Architecture – Enterprise Systems
Overview: Large enterprises will have many systems or sub systems that stores data related to machines, processes and business transactions. The 360-degree view of the data from various
systems provides the business user with intelligent insights for decision making . With this consolidated view, business users will be able to perform deeper analysis and will be able to take
decisions in real-time (e.g. With a customer order , production plan/ schedule data from ERP and with live data from machines one can predict machine failures, behaviors, schedule
adherence and slippages if any).

Enterprise Resource Planning (ERP) – represents a suite of software that organizations use to manage day-to-day business
activities, such as accounting, procurement, project management, risk management and compliance, and supply chain operations.

Asset Management System : ISO 55000 defines Asset management as the "coordinated activity of an organization to realize
value from assets". In turn, Assets are defined as follows: "An asset is an item, thing or entity that has potential or actual value to
an organization.” Asset management enables an organization to examine the need for, and performance of, assets and asset
systems at different levels. IBM Maximo Asset Management product supports functions such as Asset management, Work
management, Service Management, Contract Management, Inventory Management and Procurement Management.

Customer Relationship Management (CRM): CRM system is one of the main source for customer and prospect data. It
manages customer’s needs, their interactions and helps in building relationships by providing the most suitable products and
enhanced customer service. It integrates back and front office systems to create a repository of customer contacts, purchases, and
technical support, among other things. Saleforce.com is hosted CRM and it’s integration with IoT application is a common
pattern or Use Case for obtaining customer information or logging a service request.

Real Estate and Facility Management System: Facility Management system helps in coordination of space, infrastructure , Enterprise LDAP: LDAP manages the users and their access information in a central
people and organization, Some of its core competencies include real estate property management, operations and maintenance. repository. LDAP will provide User Authentication and Authorization service for IoT
IBM provides industry leading solution – Tririga, a single system to manage the lifecycle of facilities. Its integrated workplace applications.
management system increases the operational, financial and environmental performance of facilities.

In a smart building context, it is important to monitor the smooth functioning of facilities operations. Temperature within the Product Life Cycle Management (PLM): PLM Systems ( especially in
building is one of the critical parameters that needs to be monitored from Safety , convince and from energy consumption manufacturing ) manages data associated with the products ( candidates for IoT
standpoint. Application) through its life span.

9
 IoT Reference Architecture – Third Party Systems / Services
Overview : Third Party Systems / Services are often referred as extended enterprise data originating from outside the enterprise and from entities such as government agencies,
regulatory bodies , data belonging to customers (social media), suppliers, vendors , business partners and publicly available information about assets, devices, products and
customers. IoT Applications will need to leverage the third-party services/ systems to cater the needs of business users and end consumers., Example of Third-Party Services :
Map integration will be required to show the live location of an asset .

Weather: Weather Data provides a critical dimension to forecast, detect, and visualize disruptive weather events that
might affect decision making related to IoT Assets and Devices. The unprecedented input stream from IoT devices and live
weather data can produce real-time weather-based business alerts. Commanding IoT device or appliance to alters its
course of action based on changing weather pattern is an important cross industry use case. IBM Weather Company
Services can be used along with other IoT services to enable such use cases.

Social: Network of devices becomes smart when their behavior can be personalized based people’s social behavior /
network. Use case of Social and its linkage to IOT is still emerging. Integration with Social Media ( Twitter, Facebook,
etc) will become essential for providing additional human centric intelligence to the IoT Devices.

MAP / GIS: Location and Geography becomes connecting glue for many of the IoT applications. Key example includes
: Location Mapping of static assets/devices, Tracking of moveable assets/ devices, Geo Fences, route optimization and
people tracking

10
 IoT Reference Architecture – Connect & Collect
Overview: This component is the main entry or landing point for the data coming from the assets / machines into the IoT platform. This critical component responsible for:
1. Withstanding huge transaction volumes of varied payloads for the connected machines / assets
2. Real time event processing and decision making by interacting with down stream components
3. Devices and Asset Control remotely through device management
4. Lifecycle management of devices

Device Connect: IOT devices communicate with other devices and Cloud Platform using set of data and
communication/network protocols. The protocol can be industry standard protocols such as CoAP, MQTT,
AMQP, HTTP(S), Web Sockets, Modbus TCP, OPC UA or can be a proprietary protocol running on top of
TCP/IP (SOCKET Interface TCP/UDP and HTTP interface and even SMS interface) using
Binary/XML/JSON/ASN.1 format of data packaging. Typically, IoT Platform support one or more
protocols ( such as MQTT, AMQP) and will need to IoT Gateway for Protocol conversion.

Device Security: Authentication ensures the identity of users, devices or applications specific to
organization's information using encryption [TLS/SSL , SAML etc] . Additionally, applications using APIs
are authorized using API keys with authentication token that is salted and hashed.

Device Registration : The device database is the master source for all device and device related events.
Registering each device is critical so that device can be uniquely identified for the data exchange to
happen. Each device needs to be registered and managed in a seamless manner so that applications and the
devices are able to send updates such as a location or the progress of a firmware update. Devices uniquely
identify themselves to the IoT platform with an authentication token that will only be accepted for that
device.

11
 IoT Reference Architecture – Core Functions
Overview : Core or Common Functions of IoT Platform includes Event Management, Device Management, Rule & Alert and User Management.

Event Management : This module allows us to manage and control the flow of the data into the down stream components such as data store or another system. Primary source of Event data is our IoT devices , all the
published messages are retained for configurable period of time or until it is consumed The Event Management functionality is supported by technologies such as Apache Kafka, Azure Event Hub, IBM message Hub.

Device Management : Device management is the process of authenticating, provisioning, configuring, monitoring and maintaining the devices, device firmware and software that provides its functional capabilities.
Effective device management is critical to establishing and maintaining the health, connectivity, and security of IoT devices.

Rule Management : This component allows us to define the Rules on IoT data so that one can respond to
emerging conditions through automated actions. Following are the type of rules :

Inference Rules: This corresponds to ingesting millions of events and perform Realtime analysis , enabling
sub-millisecond response times and instant decision-making

Predictive Rules: Predict the probability of outcomes that are uncertain but require an “educated guess”
based on predictive models. This type of rule is executed typically in scheduled frequency.

Alert Management: Alert Module contains appropriate response for a given rule and it ensures right method
& actions are used based on the criticality of the issue .The example includes, creation a work order to track
an issue in asset management system and allocate the action to the right service technician. Other action
triggers include SMS, E-mail, Push Notification , etc

User & Role Based Access : User Management functional includes onboarding and offboarding the user on to IoT Applications. Typically this function is enabled using Active Directory (LDAP). In B2C context ,
User Authentication can happen using OAuth (Social Media Credentials) and in B2B or Enterprise User will authenticate using Enterprise LDAP and will typically have seamless login experience using SSO. Role-
based access control (RBAC) is a method of restricting application access based on the roles of individual users within an enterprise. ... As such, companies can designate whether a user is an end user, an administrator
or a specialist user

12
 IoT Reference Architecture – Data Store
Overview: Data collected from IoT Devices , Enterprise systems and third-party sources will be persisted in Cloud based data repository. This rich set of data will become a
source for building new applications and will be a source for deeper analysis to provide actionable insights. The data in the repository / data stores can be classified into Raw
Event Data, Master & Reference data, Operational Data, Historical / Analytical data and content data.

Raw Device Data: : These are the data collected by IoT Devices such as – Sensor, Machines, Actuators, appliances , wearable devices, health care monitoring devices and so on. The content and structure
of this data will vary based on type of Devices , the sample attributes includes , temperature, pressure, speed, location, etc. As the # of connected devices grows the volume of data increases exponentially
and hence need planning and implementing retention policy, filtering rules, data transfer to historical/ analytical store becomes critical

Operational Data : These are the data generated by Enterprise systems and is very different from
Raw Event data. The data could include machine maintenance history, machine diagnostics data,
customer order, production plan, etc and is important for generating deeper insight and to predict the
future outcome

Master & Reference Data: Master data is relatively static data. This data will help in providing the
context to the raw data. Example of Master data includes : customer, device, asset, product, machines,
etc. Reference data is set of permissible data values that are critical for the data and application
integrity – the example :valid value for sensor types, geographic values – cities/states, Device type to
Firmware mapping etc .

Analytical / Historical Data: It is the consolidated data from all above data sources and is designed
for query, deeper cross subject area analysis, and can be used for traditional descriptive analytics ,
predictive and prescriptive analytics. Depending on the use case and storage constrains the data can be
stored in an aggregated form.

Content Data: Content data is primarily an unstructured data, it includes data such as images, video, audio, firmware files, documents (pdf, word, etc) and UI layouts which will further enrich and support
IoT applications (both Web & Mobile) and analytics. IBM Object Store is one of the candidate software that will the enable the management of the content data

13 IoT Reference Architecture – Data Store

 IoT Reference Architecture – Analytics and Insight
Overview: In the IoT World, large network of connected devices/ sensors, vast amounts of data generated by machines / larger assets are a common theme. This data is a treasure trove and by extracting meaningful
insights one can improve decision making. Such type of analytical insights needs capabilities for analyzing both historical and real-time data, as well as forecasting the future, to distill what’s valuable, detect patterns
and reveal insights. With Analytics we can achieve benefits ranging from increased revenue to lowered operating expenses, enhanced service availability and reduce risk. The analytical component are
● Descriptive, which uses business intelligence and data mining will answer the question : “What has happened?”
● Predictive, which uses statistical models and forecasts and will answer the question: “What could happen?”
● Prescriptive, which uses optimization and simulation , and will answer the question: “What should we do?
● Cognitive, which uses natural language processing, machine learning , video, image & text analysis to answer the question: “What is the Best course of action "

Descriptive Analytics: Analytics performed on data to understand the behavior over an elapsed time period. This type of analytics are at aggregate / summary level. Example : # of alerts per year, Frequency of
maintenance operation per machine per customer , count of connect devices, etc

Predictive Analytics : Predicting the likelihood of the future outcome using historical data and intelligently filling the
gaps in the data to arrive at meaningful conclusions. Prediction often involves identification of patterns in the data and
by applying statistical models and algorithms to capture relationships between various data sets.

Prescriptive Analytics: The prescriptive analytics goes beyond descriptive and predictive analytics by recommending
one or more possible courses of action. Essentially they predict multiple futures and allow business users to assess
number of possible outcomes based upon their actions. Prescriptive analytics use a combination of techniques and tools
such as business rules, algorithms, machine learning and computational modelling procedures

Cognitive & Machine Learning: The Cognitive and Machine learning capabilities can help in human interaction and to
have a dialog with the IoT Devices using natural language. It provides ability to obtain response based on the context and
decisions that are based on evidence with a degree of confidence. Provides ability to understand end users at deeper level
and can alter the response accordingly. With frequent interaction it can learning (get trained) and become intelligent over a
period of time.

Geospatial Analytics: Geospatial data, also referred to as location data or spatial data, enables IoT Use cases by providing context of time and location dimension to the device data, to see changes over time and identify
exact location where the changes are taking place. Geospatial analytics improves predictive insights by accounting for both time and space in predictive models, to accurately forecast events at a specific location for any
future point in time

14
 IoT Reference Architecture – Enterprise Integration
Overview : In IoT for Operational and Analytics needs, it is often required to integrate IoT data with Enterprise data and external sources of information such as Weather, Maps etc to
provide a context and enrich to the device data for deeper analysis. Examples :
• In Building Analytics, the enterprise assets which are maintained in asset management system like Maximo is often used to relate the Equipment & its location with the IoT sensor
data so that technicians can easily locate the asset and fix the faults.
• In Connected Cars, IoT platform need’s integration with the enterprise systems such as Dealer Management Systems so that real time offers to nearest dealer can be made when
vehicle is on the road.
• External sources such as Weather data, can be used in Building Analytics so that building room temperatures can be controlled appropriately which can result into savings of energy
consumption.

Near Real-Time: Processing the data, in Near Real Time refers to reasonable delay in the context of situation. Not all data is required to be processed in real time. Messaging technologies like rabbit MQ, MQTT, IBM
Message Broker enable near real time data acquisition and assured delivery mechanism. Equipment or Machine faults and wear & tear information can be sent to Enterprise System in near real time to maintain
history of asset health.

Real-Time: In IoT world, real time sensor data can be used to resolve problems faster, or even detect anomalies upfront
before interruption or downtime occur. Real-time systems are used when it is imperative that an event be reacted to within
a strict deadline. Technologies such as Apache Flume, Apache Kafka enable real time streaming of device events. Often in
IoT device connectivity, light weight telemetry protocol such as MQTT is used as well as http REST API. IBM IoT
Foundation on Cloud is good example of IoT device data acquisition. Cloud Integration service on Bluemix or Cast Iron
hosted on Softlayer or SaaS variant of Cast Iron can facilitate enterprise integration.
• The asset or device or equipment sending data to IoT platform can be validated in real time integration with
Enterprise Asset Management system .
• The Users sending commands to deices can be authenticated with Enterprise LDAP in real time.
• Work Orders against the equipment faults can be created in real time with Enterprise

Batch: These are scheduled tasks to load and process large amount of data or execute voluminous transactions. In IoT, it is often required to perform analysis on large sensor data like historical and archived device
events, in order to get insights from larger time span data. Apache Hadoop with Map Reduce and Apache Spark technology could be used to perform analytics on large sensor data that is collected over period of time.
ETL tools such as IBM Infosphere Information Server, Data Work bluemix service can be used to extract, load and transform in batch way. Open source technology such as Spring Batch is also available. Equipment
state of degradation can be detected on over period of data, based on which subsequent maintenance can be planned

15
IoT Reference Architecture – Delivery and Visualization (1/2)
Overview
The Deliver Layer provides the mechanism for end user or external systems to interaction with the IoT device, consume analytical results or to visualize IoT data elements. The interaction
may be human or automated through a set of services.

Visualization: Allows users to gain insight through diagrams, maps, schedules, charts, and images. In IoT world, visualization like Predictive Graphs can depict future Equipment Energy
Consumption cost, Heat Maps for daily temperature variance from temperature sensors data. In Transportation, vehicle sensors can transmit location coordinates which can be displayed
on geographical map to visualize the location speed, thermostat adjustment, shutdown etc.

Channels : With proliferation of mobile devices, mobile application are becoming defacto standard. . In IoT world, the
mobile & tablet devices are used for operational purposes to send the commands to IoT device which can restart,
upgrade firmware etc. and trouble shoot the faults. The end users can use mobility devices to take pictures or video of
equipment and upload to system and provide feedback during fault investigation.

Web Services: Software front end application used for retrieving and presenting information on the internet. With
mobility devices becoming common , the browsers interfaces are often developed with responsive UI technologies such
as bootstrap, JQuery Mobile etc.

Portals : Portal provides a single access point to Web content and applications, personalized to each user's needs. Portals
can be used to provide graphical visualization of IoT device point data such as temperature against time series.

API : Service or set of services that can be accessed via the internet or other computing processing methods and provide
content, information or processing services. Enterprise applications can consume IoT data via Web based APIs.

16
IoT Reference Architecture – Delivery and Visualization (2/2)
Overview: The Deliver Layer provides the mechanism for end user or external system interaction with the IoT device, consume analytical results or visualize IoT data elements. The
interaction may be human or automated through a web service.

Visualization: Allows clients to gain insight through diagrams, maps, schedules, charts, and images. In IoT world, visualization like Predictive Graphs can depict future Equipment Energy
Consumption cost, Heat Maps for daily temperature variance from temperature sensors data. In Transportation, vehicle sensors can transmit location coordinates which can be displayed
on geographical map to visualize the location speed, thermostat adjustment, shutdown etc.]

Notifications : Real-time notifications are essential component in enterprise IoT applications ranging from remote
machine monitoring to smart building automation. Notifying stakeholders of faulty condition of equipment, sensors is
important or essential function in an IoT Application

In Transportation industry, a IoT sensor can be enabled to send notification when vehicle is entering or exiting of geo
fence.

Applications : IoT Applications needs to be developed, deployed, and scaled with ease. These applications should be
highly composable, ultra-fast, ultra-light and need to be designed for the cloud. Applications Runtime & Container
using NodeJs, Java, PHP, XPages, Python, Ruby , Swift etc.

Types of Application includes :

Horizontal Applications : These are reusable IoT applications that are meant to solving cross industry problem (e.g.
Asset monitoring, vibration analytics, device data parsing, fleet management, predictive asset maintenance etc)

Vertical Applications : These are industry aligned IoT applications that solves one or more business use cases (e.g.,
real time monitoring of metal cutter, mining process equipment monitoring, boiler monitoring in iron ore industry etc)

17
18
IoT Reference Architecture : Functional Architecture with IBM Cloud
Mapping
User Community
IoT Enabled Appliances Connected Appliance Cloud Platform

Application Functions Deliver and Visualization

Connect & Collect Analytics & Insights Security
Applications

Event Streams Streaming

Analytics App ID
Internet Of Things
Platform
Security

Cognos Dashboard Geospatial

Integration Embedded Key
Analytics
Streaming Analytics Protect IBM Cloud
Functions Event Streams

API Connect Access Management

IBM Cloud Functions Analytics Service Certificate Manager
App ID

Data Store
IBM Cloud Functions Notification
Secure gateway
Cloudant NoSQL DB PostgreSQL / db2 Object Storage Push Notification

Enterprise Systems Third Party Systems Other

Systems
ERP Weather SMS Gateway
Other
Asset Other
Management
Active Directory GIS Map Social Email Gateway
Media
19
IoT architecture – IBM Maximo Asset Monitor

20
IoT architecture – IBM IoT Platform Analytical Service

21
22
IoT Reference Architecture : Functional Architecture with Azure
Mapping
User Community

IoT Enabled Appliances Connected Appliance Cloud Platform

Deliver and Visualization
Connect & Collect Application Functions Analytics & Insights Security
Applications

IoT Hub Power BI Embedded

Event Hub
Active Directory Azure Maps Web App

Device Provisioning Service Stream Analytics

Stream Analytics App Mgmt.

Security

Integration
Azure Maps
Power BI Embedded
Functions
Functions Azure Key Vault
Access Management

API App` Timeseries insight

Service Bus Active Directory

Data Store
Notification

Logic App
Cosmos DB SQL DB Blob DB Notification Hub

Enterprise Systems Third Party Systems Other

Systems
Order System Weather SMS Gateway
Other
Enterprise Data
lake Other
Active Directory GIS Map Social Email Gateway
Media
23
IoT architecture with IoT Hub - Azure

24
 Microsoft Azure IoT Central and Azure IoT offer several options for building an IoT solution. These options are appropriate for
different sets of customer requirements:

Azure IoT Central is a software as a service (SaaS) solution that uses a model-based approach to help you to build enterprise-grade
IoT solutions without requiring expertise in cloud-solution development.

Azure IoT solution accelerators are an enterprise-grade collection of solution accelerators built on Azure platform as a service
(PaaS) that help you accelerate the development of custom IoT solutions.

25
26
IoT Reference Architecture : Functional Architecture with AWS
Mapping
User Community

IoT Enabled Appliances Connected Appliance Cloud Platform

Analytics & Insights Security Deliver and Visualization

Connect & Collect Application Functions
Applications

IoT Core

Elastic- Cloud Maps

QuickSight BeanStalk`
Kinesis Analytics
WAF
IoT Device Management
Security

Kinesis Streams Kinesis Analytics

Integration
IAM QuickSight
API
Gateway`

Cloud Watch Cloud Maps Access Management

Lambda Functions
Lambda Functions
Shield
Directory-Service IAM

Data Store
Notification
Simple Queue Service (SQS)

Dynamo DB S3 Directory-Service Simple Notification Service

RDS

Enterprise Systems Third Party Systems Other

Systems
ERP Weather SMS Gateway
Other
Asset
Management Other
Active Directory GIS Map Social Email Gateway
Media
27
IoT architecture with AWS
Devices Connect Process and Store Analyze & Predict Visualization User

Web Application- Server

less

Decrypt Mail/SMS Sage Maker ML Result Data

AWS Green Grass and Notify Notification

Secure Channel View files on S3 Application Link

Execute ML Functions
AWS IoT Core Decrypt and Transactional Data
store
Business Transactional
Logic Data and ML
Result Data
Mobile Application
Decrypt and Kinesis Analytics
Device defender Kinesis Fire
stream
house

User
API
authentication
Device Back up storage Object storage AWS IoT Gateway
Management and Firmware Analytics
files

28 IoT architecture with AWS

 AWS out of the box solution

1. Real-Time IoT Device Monitoring with Kinesis Data Analytics

Monitoring IoT devices in real-time can provide valuable insight that can help you maintain the reliability, availability, and performance of your
IoT devices. You can track time series data on device connectivity and activity. This insight can help you react quickly to changing conditions and
emerging situations.
https://aws.amazon.com/solutions/real-time-iot-device-monitoring-with-kinesis/

2. AWS Connected Vehicle Solution

The connected vehicle solution includes capabilities for local computing within vehicles, sophisticated event rules, and data processing and
storage. The solution is designed to provide a framework for connected vehicle services, allowing you to focus on extending the solution's
functionality rather than managing the underlying infrastructure operations.
https://aws.amazon.com/solutions/aws-connected-vehicle-solution/

3. IoT Device Simulator

The IoT Device Simulator includes a device simulator API, which leverages API Gateway to invoke the solution’s microservices (AWS Lambda
functions).
https://aws.amazon.com/solutions/iot-device-simulator/

29
30
IoT Reference Architecture : Functional Architecture with GCP
Mapping
User Community

IoT Enabled Appliances Connected Cloud Platform

Data Analytics Security Deliver and Visualization

Device Management Application Functions
Front End & Integration

Container Engine

Cloud IoT Core Cloud Dataflow Big Query

Compute Engine
Armor
Security

Data Ingestion App Engine

Cloud Functions
IAM
Cloud IoT Core
Access Management

ML Engine/ TensorFlow
GCDS IAM
Cloud Pub Sub
Data Storage
Google Cloud Notification
Directory Sync
(GCDS)
Cloud Data Flow Cloud Storage Bigtable Firebase Messaging System

Enterprise Systems Third Party Systems Other

Systems
ERP Weather SMS Gateway
Other
Asset
Management Other
Active Directory GIS Map Social Email Gateway
Media
31
 https://cloud.google.com/architecture?hl=en&category=internetofthings

32
Doubts?