IoTIFY Network Simulator
HomeSignupVirtual LabGithub
Search…
Introduction
Getting Started
Workspaces
Fundamentals
Mapping the IoT device lifecycle
Understanding a Test
IoT Device Model
Protocol Settings
MQTT
HTTP
CoAP
Raw (TCP/UDP/TLS/DTLS)
LWM2M
Running the Simulation
Additional Helpers
External libraries
IoTIFY Helper Functions
Analyzing Results
Under the hood
API
Simulation API
Glob APIs
Metrics API
Google Sheets API
IoT platform integration
AWS IoT Connector
Azure IoT
Losant IoT
Google Cloud IoT Core
IBM Cloud
Dweet.io
IoT Testing
Overview
Functional Testing
Performance Testing
Security Testing
Test Automation & CI/CD integration
Create Account
Powered By GitBook
CoAP
Constrained Application Protocol remains one of the most efficient protocol for low power devices. Let's see how CoAP is implemented with IOTIFY
CoAP is based on UDP and has built in mechanism for ensuring reliable delivery. For a good overview of CoAP, please see the following guides
http://www.programmingwithreason.com/article-iot-coap.html
www.programmingwithreason.com
Another interesting tutorial
CoAP Protocol: Step-by-Step Guide - DZone IoT
dzone.com
In IoTIFY CoAP protocol settings we allow following fields to be configured
Method: CoAP method, which could be GET/POST/PUT/DELETE
Host: The CoAP Host name or IP address, followed by the port number (if not default)
Path: The CoAP server URL, where the message should be sent to. If you are using a query string, that must be the part of URL itself.
Confirm: Whether the message should be sent as (Conformable) CON or (Unacknowledged) NON
Observe: Whether the resource should be observed and any changes should be sent back to the client. The response handler function will be invoked if a change is detected.
Additional Headers: Any additional header which must be sent along with the payload.
Timeout: The timeout value to wait before declaring a non confirmed message a failure.
​
Previous
HTTP
Next
Raw (TCP/UDP/TLS/DTLS)
Last modified 1yr ago
Copy link