6. TSP
HTTP
▸ Hyper text transfer protocol
▸ GET, PUT, POST, DELETE, HEAD,
TRACE, OPTIONS, etc commands
▸ Stateless (each request is different
of others)
▸ HTTP client can be a browser or
application running on the client
▸ Multiple headers (MIME)
7. TSP
COAP
▸ Constrained Application Protocol
▸ For Machine to Machine M2M
▸ Request response model
▸ Runs on UDP instead of TCP
▸ GET , PUT, POST, DELETE, etc.
8. TSP
WEBSOCKET
▸ Full Duplex communication over
single socket connection for
sending messages between client
and server
▸ Its based on TCP
▸ Client can be a browser, IoT Device
or a mobile application
9. TSP
MQTT
▸ Message Queue Telemetry
Transport
▸ Its based on publish subscribe
model
▸ Use of MQTT broker (as a Server )
▸ Useful for places where memory
and resources constraints are
limited
10. TSP
XMPP
▸ Extensible Messaging and Presence
protocol
▸ Real time communication and
streaming xml data between network
elements
▸ Suitable for Voice/Video chats,
messaging, data syndication,
gaming, multi party chat
▸ Its based on client server architecture
as well as server - server architecture
11. TSP
DDS
▸ Data Distribution service
▸ Its a middleware for D2D or M2M
▸ Publish subscribe model
▸ Provides QoS and configurable
reliability
12. TSP
AMQP
▸ Advanced message queuing
protocol
▸ Its for business messaging
▸ Supports point to point and
publish subscribe, routing/queuing
▸ Uses AMQP brokers
▸ Messages are pushed by the
brokers or pulled by the
consumers.
17. COMMUNICATION MODELS
PUBLISH SUBSCRIBE MODEL
PUBLISHER
SEND MESSAGES TO
TOPICS
BROKER
TOPIC 1
TOPIC 2
CONSUMER 1
CONSUMER 2
CONSUMER 3
Message
published
to topic 1
Message
published
to topic 2
18. COMMUNICATION MODELS
PUSH PULL MODEL
PUBLISHER
SEND MESSAGES TO
QUEUE
CONSUMER 1
CONSUMER 2
Message
pushed to
queues
Message pulled
from queues
19. COMMUNICATION MODELS
EXCLUSIVE PAIR COMMUNICATION MODEL
CLIENT SERVER
Request to Setup connection
Response accepting the request
Message from Client to Server
Message from Server to Client
Connection close request
Connection Close Response
21. API
REST BASED COMMUNICATION APIS
HTTP CLIENT
REST AWARE
HTTP CLIENT
HTTP PACKET
GET, PUT, POST,
DELETE
REST PAYLOAD
JSON,XML
HTTP SERVER
AUTHORISATIO
N, REST-FUL
WEB SERVICE
RESOURCES
URI (REPRESENTATIONS, RESOURCES)
22. TEXT
REST COMMUNICATION APIS
‣ Design web services and web APIs focuses on resources and how they are addressed and
transferred.
‣ Client Server Concerns
‣ Client not bother about the storage at the server
‣ Server not bother about the user interface at the client
‣ Stateless
‣ State lies at the client
‣ Cache-able
‣ Layered system
‣ Uniform interface
‣ Code on demand
23. http
method
Resource type action Example
GET Collection URI
List all the rescuers
in a collection
http://example.com/api/tasks (list all
tasks)
GET Collection URI
Get info about a
resource
http://example.com/api/tasks (get info on
task 1)
POST Collection URI
Create a new
resource
http://example.com/api/tasks (create a
new task from the data provided in the
req)
POST Collection URI Generally not used
PUT Collection URI
Replace the entire
collection with
another collection
http://example.com/api/tasks (replace
entire collection with data provided in the
request)
PUT Collection URI Update a resource http://example.com/api/tasks (delete all
tasks)
DELETE Collection URI Delete the entire
collection
http://example.com/api/tasks (lista ll
tasks)
DELETE Collection URI Delete a resource http://example.com/api/tasks (del task 1)
24. TEXT
WEBSOCKET BASED COMMUNICATION
CLIENT SERVER
Request to set up websocket
Response to acceptance
Data Frame
Data Frame
Data Frame
Data Frame
Request to close the connection
Connection close response
26. TEXT
IOT ENABLING TECHNOLOGIES
▸ Wireless sensor networks
▸ End nodes, routers and
coordinators
▸ Cloud computing
▸ Iaas, Paas, SaaS
▸ Big Data analytics (Volume, velocity
and variety)
▸ Communication protocols
▸ Embedded Systems
