IOT ARCHITECTURE

EAC3016 AND ITSALS

FUNDAMENT PROTOCOLS| IS3104 | 4 Credits|
OF SENSORSAND IoT

UNIT -1
Fundamentals of IoT
Dr SUNIL KUMAR
[email protected]
Aassistant Professor
School of Computing & Intelligent Systems
Department of IoT & IS
Manipal University, Dehmi Kalan, Jaipur Rajasthan
 Syllabus
Fundamentals of IoT:
Introduction, Definitions & Characteristics of IoT, Evolution IoT, IoT Architectures,
Physical & Logical Design of IoT, IoT frameworks.

Design Principles for Connected Devices:

Machine-to-Machine(M2M) Communications, Architectural components of M2M,
IoT versus M2M, M 2 M systems layers, and design standardization.
 IoT Definition
∙ A dynamic global network infrastructure with self-configuring capabilities based
on standard and interoperable communication protocols where physical and
virtual “things” have identities, physical attributes, and virtual personalities and
use intelligent interfaces, and are seamlessly integrated into the information
network, often communicate data associated with users and their environment.
 How IoT Work?
▪ Sensor in every device
▪ Every device emits data regarding working states of things
▪ IoT provides platform to all devices to dump their data
▪ IoT platform collect and analyse the data
▪ Valuable information is extracted
▪ And information is shared to other devices for decision making or
information
 IoT Structure

COLLECT COMMUNICATE ANALYZE ACT

Characteristics of IoT
 Characteristics of IoT
∙ Dynamic and self-adapting
∙ Self-configuring
∙ Interoperable Communication protocols
∙ Unique identity
∙ Integrated into information network.
 Characteristics of IoT
∙ Dynamic and self-adapting: The IoT devices can dynamically adapt with sensed
environment, their operating conditions, and user’s context and take actions
accordingly. ex:Surveillance System.

∙ Self-configuring:
I.IoT devices can be able to upgrade the software with minimal intervention of user, whenever
they are connected to the internet.
II.They can also setup the network i.e a new device can be easily added to the existing network.

ex: Whenever there will be free wifi access one device can be connected easily.
 Characteristics of IoT
∙ Interoperable Communication: IoT allows different devices (different in architecture) to
communicate with each other as well as with different network.

ex: MI Phone is able to control the smart AC and smart TV of different manufacturer.

∙ Unique identities:
I. The devices which are connected to the internet have unique identities i.e IP address through which
they can be identified throughout the network.

II.The IoT devices have intelligent interfaces which allow communicating with users. It adapts to the
environmental contexts.
III.It also allows the user to query the devices, monitor their status, and control them remotely, in
association with the control, configuration and management infrastructure.
 Characteristics of IoT
∙ Integrated into information network:
I. The IoT devices are connected to the network to share some information with other connected
devices. The devices can be discovered dynamically in the network by other devices.

ex. If a device has wifi connectivity then that will be shown to other nearby devices having wifi
connectivity.

II.The devices SSID will be visible through out the network. Due to these things the network is
also called as information network.
III.The IoT devices become smarter due to the collective intelligence of the individual devices in
collaboration with the information network.

Ex: weather monitoring system. Here the information collected from different monitoring nodes
(sensors, arduino devices) can be aggregated and analysed to predict the weather.
Benefits of IoT
 Benefits of IoT
I. Real time Information.

II. Help in monitoring the overall business process

III. Help in improving the experience of the customer.

IV. Save time and money.

V. Productivity of the employee will increase.

VI. Business decisions can `be made better by IoT.

VII.Revenue generation can also be increased.

VIII.IoT encourages companies to rethink the ways they approach their business, industries,
markets and can also improve their strategists
Physical Design of IoT
 Things in IoT

∙ Things refers to the devices which have unique identities and can
perform remote sensing, actuating & monitoring capabilities.

∙ IoT devices can

o Exchange data with other connected devices
o Collect data from other devices
o Process the data locally or send the data to centralized servers
o Cloud based application back-ends for processing data
 Things in IoT

∙ IoT devices consists of several interfaces for

connections to other devices like:

o I/O interfaces for sensors

o Interface for internet connectivity
o M emory & storage interfaces
o Audio/video interfaces

Figure: Block Diagram of a typical IoT Device

 Things in IoT

∙ SD: SD cards are a type of flash memory card that are small and non-volatile. They were introduced
in 1999 by SanDisk, Panasonic, and Toshiba as an improvement on MMCs. SD cards are used in
many consumer devices, such as mobile phones, digital cameras, and video game consoles

∙ MMC: MMCs can be used in many of the same devices as SD cards, such as digital cameras,
cellular phones, and digital audio players. MMCs can be up to 16 gigabytes in size and can be easily
removed for access by a PC using an MMC reader.

∙ SDIO: Secure Digital Input/Output, is a communication interface that allows devices to connect to
an SD card and exchange data. It was introduced in 2001 as an extension to the SD card standard,
which was originally developed for storing and transferring data in portable devices.
 Things in IoT
∙ UART: Universal Asynchronous Receiver Transmitter (UART) is a hardware protocol that allows two
devices to exchange serial data using two wires. It's a popular choice for communication between
devices in embedded systems, microcontrollers, and computers.

∙ SPI: stands for Serial Peripheral Interface, a communication protocol that enables fast,
synchronous data transfer between a controller and a peripheral device. It's commonly used in
embedded systems for short-distance wired communication between integrated circuits.
∙ I2C: or Inter-Integrated Circuit, is a serial communication protocol that allows multiple devices to
communicate with each other over a two-wire interface

∙ CAN: stands for Control Area Network, which is a serial communication protocol that allows
devices to exchange data efficiently and reliably.
IoT Protocols and Standards for IoT Ecosystem
Smart connected IoT devices are more vulnerable to threats. And to minimize these
security loopholes it’s important to use the right protocols.

IoT communication protocols are modes of communication that ensure optimum security
to the data being exchanged between IoT connected devices.

The IoT devices can be connected via an IP network or a non-IP network. Though there
is a difference in their connectivity range, power, and memory used.

Connections through IP networks are complex, and take high memory and power from the
IoT devices while the range is not a problem. On the other hand, non-IP networks like
Bluetooth require less memory and power but have a range limitation.
Why there’s need of IoT protocols?
For every interaction between devices, there is a need for a medium; preferably a common language that all the
devices in the given IoT ecosystem would be able to understand.

This very medium is provided by the IoT protocols. And a standardized communication protocol brings these key
benefits:

High quality and credibility –

Communication technologies that follow the standards deliver high service quality & robustness against
interferences. Additionally ensures the reliable and secure transmission of massive IoT sensor data

Interoperability and innovation flexibility –

Standard protocols have the flexibility to be programmed on various commodities & off the shelf hardware
like gateways and chipsets. Hence with multi-vendor support solutions, it helps end-users in avoiding
vendor lock-in risks.

Global scalability-
Every scaling business wants to adopt IoT connectivity that can be implemented globally. And standard
communication protocols ensure universal connectivity while minimizing the installation complexity
 Types of IoT Protocols
IoT Network Protocols –
IoT network protocols are designed to connect
medium to high power devices over the network.
IoT network protocols allow data communication
within the scope of the network. HTTP, LoRaWAN,
bluetooth, zigbee are some of
the popular IoT Network protocols.

IoT Data Protocols –

IoT data protocols are designed to connect low power IoT
devices. Without any internet connection, they are capable of
providing end-to-end communication with the hardware.
MQTT, CoAP, AMQP, XMPP are some of the popular IoT
Network protocols.
the connectivity in IoT data protocols can be done via a wired or
cellular network.
 IoT Protocols

∙ Link layer
∙ Network/Internet layer
∙ Transport Layer
∙ Application Layer
 Link Layer Protocol
∙ It determines how the data is physically sent over the network’s physical layer.
∙ Hosts on the same link exchange data packets over the link layer protocols.
∙ This layer determines how the packets are coded and signalled by the hardware
device over the medium to which the host is attached.

LINK LAYER SPEED PURPOSE

PROTOCOLS
802.3 10Mbps to 40Gbps Ethernet
802.11 1Mbps to 6.75Gbps Wi-Fi
802.16 1.5Mbps to 1Gbps Wi-Max
802.15.4 40Kbps to 250Kbps LR-WPAN
2G/3G/4G/5G 9.6Kbps to 100Mbps Mobile
Communication
 Network Layer Protocol
∙ Responsible for sending of IP datagrams from the source network to destination network.

∙ Performs host addressing and packet routing.

∙ The datagrams contain the source & destination addresses which are used to route them from source to
destination across multiple network.

∙ Host identification: IPv4,IPv6 & 6LoWPAN

∙ IP protocols establish connections on packet networks, but do not guarantee delivery of packets.

IPv4 32 bit address = 2^32 devices

IPv6 128 bit address = 2^128 devices
6LoWPAN Used to address low power device.
Operates in 2.4 Ghz with data rate of
250kbps
Works with 802.15.4 in link layer
 Transport Layer Protocol
∙ Provide end to end message transfer capability independent of the network.
∙ This capability can be setup on connections, either using handshakes(TCP) or
without handshakes (UDP)

∙ It provides functions as
o Error control

o Segmentation

o Flow control

o Congestion control
 Transport Layer Protocol - TCP
∙ Transmission Control Protocol

∙ Used for
o Web browser (HTTP)
o Email programs (SMTP)
o File transfer (FTP)

∙ Connection oriented and stateful protocol

∙ Ensures reliable transmission of packets in order

∙ Error detection capability: discard duplicate packets & retransmit lost packets
∙ Flow control capability: rate at which the sender sends data is not too high for the receiver to
process.

∙ Congestion control capability: avoid network congestion and collapse that leads to degradation of
network performance
 Transport Layer Protocol - UDP
∙ User Datagram Protocol
∙ Connectionless, transaction oriented and stateless protocol
∙ Useful for time sensitive applications that have very small data units to exchange
and do not want the overhead of connection setup.

∙ UDP is transaction oriented and stateless protocol

∙ Does not provide
o Guaranteed delivery

o Ordering of message

o Duplicate elimination
 Application Layer Protocol - HTTP
Define how the applications interface with lower layer protocols to send the data
over the network. The application data, typically in files, is encoded by the
application layer protocol and encapsulated in the transport layer protocol.
Which provides connection or transaction oreiented communication over the
network

∙ Hypertext Transfer Protocol

Base for W W W
Includes commands like:GET,POST,PUT,DELETE, HEAD, TRACE, etc

Follows request-response model

Stateless protocol
Each HTTP request is independent of other

HTTP client:web browser, application

 Application Layer Protocol - CoAP

∙ Constrained Application Protocol

∙ For M 2M application under constrained environment
∙ Follows request-response model – run on top of UDP
∙ Client server architecture where clients communicate with server using
connectionless datagrams.
 Application Layer Protocol - WebSocket

∙ Full duplex communication over a single socket connection for sending messages
between client and server.

∙ Based on TCP
∙ Allows stream of messages to be sent back or forth between the client and server
while keeping the TCP connection open

∙ Client: browser, mobile application

 Application Layer Protocol - MQTT

∙ Message Queue Telemetry Transport

∙ Light weight messaging protocol based on publish subscribe model
∙ Use client server architecture
∙ The client connects to the server and publishes messages to topics on the server.
∙ The broker forwards the messages to the clients subscribed to topics.
∙ Suited for constrained environments where the devices have limited processing
and memory resources and network bandwidth is low.
 Application Layer Protocol - XMPP

∙ Extensible Messaging and Presence Protocol

∙ Used for real time communication and streaming XML data between
network entities.

∙ XMPP powers wide range of applications including messaging, presence,

gamming, multi-party chat and voice/video call.

∙ Decentralized protocol-uses client server architecture

∙ Allow server to server communication paths as well,
 Application Layer Protocol - DDS

∙ Data Distribution Service is a data –centric middleware standard for device to

device or Data centric meant for M 2M communication.

∙ DDS Use publish subscribe model

∙ Publisher – responsible to data distribution and Subscriber – responsible to
receive published data

∙ DDS provides quality-of-service (QoS) control and configurable reliability.

 Application Layer Protocol - AMQP

∙ Advanced Message Queuing Protocol is an open application layer protocol

for business messaging.
∙ AMQP supports both point-to-point and publisher/Subscriber models,
routing and queuing.
∙ AMPQ brokers received messages from publishers (e.g. devices or
application that generate data)
∙ Messages are either delivered by the broker to the consumers which have
subscribed to the queues or the consumers can pull the messages from
the queues.
Logical Design of IoT
 LOGICAL DESIGN
∙ Logical design of an IoT system refers to an abstract representation of the entities
and processes without going into the low-level specifics of the implementation.

∙ IoT functional blocks:

Devices
Communication
Services
Management
Security
Application
 IoT COMMUNICATION MODELS
∙ Request – Response model
∙ Publish – Subscribe model
∙ Push-Pull model
∙ Exclusive Pair
 REQUEST RESPONSE MODEL
∙ Client send request to the server and server responds to the
request.

∙ It is a stateless communication model & each request-response

pair is independent of others.

∙ W hen server receives a request:

Decides how to respond

Fetches the data

Retrieves resource representation

Prepares the response

Sends the response to the client

 PUBLISH SUBSCRIBE MODEL
∙ Publishers- source of data.

It sends the data to the topics which are managed by

the brokers.

They are not aware of consumers

∙ Consumers – subscribe to the topics managed by

broker.

∙ When broker receives data from publisher, it sends

the data to all subscribe consumers.

 PUSH-PULL MODEL
∙ The data producers push the data to queues and

consumers pull data from the queues.

∙ Producers not aware of consumers.

∙ Queues:

Helps in decoupling the messaging between

producer & consumer.

Act as a buffer.

Helps in situation when there is a mismatch

between the rate at which the producers push

data and rate at which consumers pull data.

 EXCLUSIVE PAIR
∙ Bi-directional, full duplex model.

∙ Once the connection is setup it remains open until

client sends request to close the connection.

∙ Client – server can send messages to each other

after connection setup.

∙ It is a statefull connection.

∙ Server is aware of all open connection.

 IoT COMMUNICATION APIs

IoT Communication APIs are used to communicate

between the server and system in IoT.

TYPES OF IOT COMMUNICATION API

There are two different types of IoT
Communication API, they are
• REST based Communication API
• Web Socket based Communication API
 REST ARHITECTURAL CONSTRIANTS
∙ Representational state Transfer (REST) API uses a set of architectural principles that
used to design web services. These APIs focus on the systems' resources that how
resource states are transferred using the request-response communication model. This
API uses some architectural constraintse.
• Client-server Here the client is not aware of the storage of data because it is concerned about the
server and similarly the server should not be concerned about the user interface because it is a
concern of the client, and this separation is needed for independent development and updating of
server and client. No matter how the client is using the response of the server and no matter how the
server is using the request of the client.
• Stateless It means each request from the client to the server must contain all the necessary
information to understand by the server. Because if the server can't understand the request of the
client then it can't fetch the request data in a proper manner.
• Cacheable In response, if the cache constraints are given then a client can reuse that response in a
later request. It improves the efficiency and scalability of the system without loading the extra data. A
RESTful web APIs is implemented using HTTP and REST principles.
 REST- BASED COMMUNICATION APIs
1.GET retrieves data.
2.POST creates data.
3.PUT updates data entirely.
4.PATCH allows partially updating data.
5.DELETE removes data.

REQUEST RESPONSE
COMMUNICATION WITH REST APIs MODEL USED BY REST
 REST ARHITECTURAL CONSTRIANTS
∙ Layered system:

It constrains the behaviour of components such that each component cannot see beyond the
immediate layer with which they are interacting.
Example : a client cannot tell if it is directly connected to server or intermediatory along the way

∙ Uniform interface:

It emphasis that the method of communication between client and server must be uniform.
Resources identified in the request & are themselves separate from the representation of the
resources that are returned to the client.

∙ Code on demand:

Server can provide executable code or scripts for clients to execute in their context.
REST- BASED COMMUNICATION APIs
 WEBSOCKET BASED COMMUNICATION APIs
∙ It allows bi-directional, full duplex communication
between client and server.

∙ It follow exclusive pair communication.

∙ It do not require any new connection to setup for each

messages to be sent.

∙ WebSocket APIs reduce network traffic & latency.

∙ It can used for IoT applications that have low latency

or high throughput requirements.
 REST Vs SOCKET APIs
∙ Stateless (REST)/ Stateful (WebSocket)
∙ Uni-directional (REST-HTTP)/ Bi-directional (WebSocket)
∙ Request response (REST-HTTP)/ Exclusive Pair (WebSocket)
∙ TCP connection (REST-HTTP each request is a new connection, WebSocket- single TCP connection
complete data transfer)
∙ Header Overhead( REST- each request has an HTTP header, So rest is not suitable for real-time
application, Web socket –does not need much overhead one's connection is established, frame
data transfer happens between the client and server
∙ Scalability(REST- scalability is easier as requests are stateless)
IoT Architecture
 IoT Architecture
∙ The main stages in the IoT architecture diagram
consists of :

1. Sensors and actuators

2. Internet getaways and Data Acquisition Systems

3. Edge IT

4. Data center and cloud.

 Stage 1– Sensors & Actuators

∙ The process starts with sensors and actuators, the connected devices that monitor (in the case of
sensors) or control (in the case of actuators) some “thing” or physical process.

∙ Sensors capture data regarding the status of a process or an environmental condition.

∙ In some cases, a sensor might detect a condition or event that requires an almost immediate response
so that an actuator can perform remediation actions in real time, for example, adjusting the flow rate
of a fluid, or the movements of an industrial robot.

∙ To avoid the delay of a round-trip of data to the server, analysis of data to determine failure and
sending of control to the “thing”, this critical processing is performed in close proximity to the process
being monitored or controlled.
 Stage 2– Internet Gateways and Data Acquisition
Systems
∙ A data acquisition system (DAS) collects raw data from the sensors and converts it from analog into
digital format.

∙ The DAS then aggregates and formats the data before sending it through an Internet gateway via
wireless WANs (such as Wi-Fi or Cellular) or wired WANs for the next stage of processing.

∙ At this point, the volume of data is at its maximum.

∙ The quantities can be huge, especially, for example, in a factory setting where hundreds of sensors
may be gathering data simultaneously.

∙ For that reason, the data is also filtered and compressed to an optimum size for transmission.
 Stage 3– Pre-processing: Analytics at the Edge
∙ Once the IoT data has been digitized and aggregated, it will need processing to further reduce the
data volume before it goes to the data center or cloud.

∙ The edge device may perform some analytics as part of the pre-processing.

∙ Machine learning can be very helpful at this stage to provide feedback into the system and improve
the process on an ongoing basis, without waiting for instructions to come back from the corporate
data center or cloud.

∙ Processing of this type will generally take place on a device in a location close to where the sensors
reside, such as in an on-site wiring closet.
 Stage 4– In-depth Analysis in the Cloud or Data Center
∙ At Stage 4, systems can be brought to bear to analyze, manage, and securely store the data.

∙ This usually takes place in the corporate data center or in the cloud, where data from multiple field
sites/sensors can be combined to provide a broader picture of the overall IoT system and deliver actionable
insights to both IT and business managers.

∙ A company may have operations in different geographies and IoT data can be analyzed to identify key
trends and patterns, or to spot anomalies.

∙ At this level, industry-specific and/or company-specific applications can be used to perform in-depth
analysis and apply business rules to determine whether action needs to be taken.

∙ The incoming data may indicate desirable changes to device settings or other ways to optimize the process,
forming a loop that facilitates constant improvement.

∙ Stage 4 also includes storage in a data warehouse, both for record keeping and for further analysis.
IoT Framework
 IoT Framework
∙ IoT (Internet of Things) is a network of devices which are connected to the internet
for transferring and sensing the data without much human intervention and the
frame work is used to achieve this.

∙ The framework has required capabilities for the cloud support and other needs
which is needed to satisfy the IoT technology.
∙ It allows device management, handles communication protocols on software and
hardware, collects / analyses information, improves information flow and intelligent
apps functionality.
 IoT Framework - KAA IoT
∙ KAA IoT is one of the most effective and rich Open Source Internet of Things Cloud
Platforms, where anyone can freely implement their smart product concepts.

∙ It can manage an N number of devices connected to each other with cross-device

interoperability on this platform.

∙ It can monitor the machine in actual time by providing and configuring remote
devices.

∙ KAA enables information exchange between linked devices, the IoT Cloud,
information and visualization systems, as well as other elements of IoT Ecosystems.
 IoT Framework - Cisco IoT Cloud Connect
∙ Cisco IoT Cloud Connect provides robust, automated, and highly secure connectivity
for the enterprise.

∙ IoT data management is done by the Cisco Kinetic IoT platform to extract, move and
compute the data.

∙ As Cisco is very famous for its security services, it protects IoT deployment against
threats with a secure IoT architecture.
 IoT Framework - ZETTA IoT
∙ Zetta is nothing but a server-oriented platform developed based on the REST,
NodeJS, and the Siren hypermedia-API-strip flow-based reactive programming
philosophy.

∙ After being abstracted as REST APIs they are connected with cloud services.
∙ These internet services include tools for visualizing machine analytics and support
such as Splunk.

∙ It builds a gero-distributed network through connectivity with systems like Heroku

to endpoints like Arduino and Linux hackers.
 IoT Framework - Salesforce IoT
∙ Salesforce is power by thunder.
∙ Thunder allows companies to unlock earlier unseen ideas and allows anyone to take
proactive, personalized activities from any device to bring their clients closer than ever.

∙ More than 150,000 clients worldwide were held by Salesforce.

∙ Salesforce has a 19.7% market share in the globe of CRM. SAP (12.%1), Microsoft (6.2%),
Oracle (9.1%) are far behind its nearest rivals.

∙ Many businesses now develop their apps or migrate to Salesforce on the Salesforce platform.
∙ This has raised demand for developers and administrators from Salesforce.
 IoT Framework - DeviceHive IoT
∙ DeviceHive is another rich IoT open-source platform that is distributed under the
Apache 2.0 license and can be used and changed free of charge.

∙ It provides deployment options for Docker and Kubernetes and can be downloaded
and used both by public and personal cloud.

∙ You can run batch analysis and machine learning above and beyond your device
information.

∙ DeviceHive supports several libraries, including Android and iOS.

 IoT Framework - Oracle IoT
∙ Oracle offers its flexible environment outstanding company possibilities to create
company applications.

∙ Oracle supports the processing and builds large-scale IoT networks with very wide
data.

∙ The use of advanced security systems to protect IoT systems against external
threats is another worth mentioning.
∙ Since these systems usually have different devices, some of which have no security
tool, it is not sufficiently justifiable to implement centralized security measures.
 IoT Framework - SAP IoT
∙ The SAP Internet of Things cloud platform has everything you need to build and
handle an IoT application.

∙ The SAP platform provides a convenient environment to remotely manage and

monitor all connected devices of your IoT system.

∙ In the SAP Platform a remote-devices we can connect directly or through cloud

service.
∙ Obviously, SAP can use IoT information to create machine learning and artificial
intelligence applications while maintaining recent technological trends.
 IoT Framework - Microsoft Azure IoT
∙ Without the Microsoft Azure solution, a cloud service giant with AWS and Google
Cloud platform, the comparison of our IoT platform will be not complete.

∙ The Microsoft Azure IoT Suite provides preconfigured solutions and the ability to
personalize and develop new solutions to meet the project requirements.

∙ The strongest safety mechanisms, superb scalability and simple integration with
your current or future systems are achieved through Microsoft Azure Internet of
thing Suite.
 IoT Framework - Google Cloud Platform
∙ Google Cloud is one of the best IoT systems available today with its end-to-end
platform.

∙ Google stands out from the others because it can process the large quantity of
information using Cloud IoT Core.

∙ Due to Google’s Cloud Data Studio and Big Query you get advanced analysis.
 IoT Framework - IBM Watson
∙ IBM Watson is very popular among the internet of thing platform among developers.
∙ The Bluemix hybrid cloud-supported Watson IoT platform allows developers to use
IoT-applications easily.

∙ IBM Watson manages the secure communication and also data storage.
∙ Real-time data exchange also is done by IBM Watson.
 IoT Framework - Hewlett Packard Enterprise
∙ Hewlett Packard Enterprise’s universal business platform offers scalability for its customers
by offering solutions to most of their problems.

∙ The platform provides cloud-based assistance or local support.

∙ In smart cities and the automobile industry, HPE universal of things platform was used
properly.

∙ The data monetization of several businesses has been carried out by HPE.
∙ Hewlett Packard Enterprise Collects analyzes information in order to grow the company.
∙ In the Hewlett Packard Enterprise M 2 M device management in Single point, Single seller.
 IoT Framework - DataV by Bsquare
∙ Bsquare takes its services seriously and has introduced the DataV application, the
hybrid framework for managing IoT services.

∙ It offers a variety of services that predict and analyze all of your ecosystem
problems.

∙ It Improves the condition maintenances.

 IoT Framework - Mindsphere by Siemens
∙ Mindsphere from Siemens provides a cost-effective platform as a service that is
ideal for application development.

∙ The cost-efficient platform allows you to connect all your appliances to a cloud
solution.

∙ In accordance with the DIn ISO / IEC 27001 standard, Siemens claims every stored
information is strictly confidential.

∙ It allows to regulate machine information in order to open fresh opportunities.

 IoT Framework - Ayla Network
∙ Ayla networks have developed their platform as a solution for enterprises.
∙ Agile Ayla networks have been established to support customers with the smooth
establishment of services, not only to develop the product.

∙ In addition to the Ayla agile platform, AMAP is an agile mobile app platform from
Ayla that develops and guides consumers through app development.
 IoT Framework - MBED
∙ The open-source service is available on the Apache 2.0 Arm MBED computer
platform.

∙ It involves cloud services, developer tools, and operating systems, that facilitate the
creation and operation of business goods.

∙ The service is designed to simplify users’ processes.

∙ MBED OS was designed to connect all your devices as an open-source platform.
∙ The platform provides services from over 60 partners and free access to a
community of 200,000 designers.
 IoT Framework - Amazon Web Services (AWS)
∙ Amazon Web Services (AWS) is an IoT platform provided by Amazon.
∙ This IoT platform provides cloud computing, database, and security services through the
AW S Console.

∙ There are so many other services such as Regions, Availability Zones, and Virtual Private
Clouds (VPCs).

∙ It helps to ease out the improving durability, distribution, availability of the application.
∙ It provides Registry for recognizing devices, Secure Device Gateway, Compatible Software
Development Kit for devices which AWS partnered with H W manufacturers like Intel,
Texas Instruments, Broadcom and Qualcomm.
 IoT Framework - RTI
∙ RTI is one of the IoT platforms that is the oldest and most pioneering provider and
also it is the most influent industrial of the internet of thing firm.

∙ Connext DDS is built especially for smart computers and their corresponding cyber-
physical systems.

∙ Connext DDS does not require response brokers, directory services, servers, as well
as administration, unlike messaging middleware designed mainly for IT systems.
Thank You