Difference between revisions of "Adaptive Machine Messaging Protocol (AMMP)"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
simple, byte-efficient, lightweight messaging protocol used to facilitate [[M2M]] communications and to build Internet of Things (IoT) connectivity into the edge device. |
simple, byte-efficient, lightweight messaging protocol used to facilitate [[M2M]] communications and to build Internet of Things (IoT) connectivity into the edge device. |
||
− | * developed and promoted by [www.axeda.com/system/files/datasheet/axeda_ds_ammp_120913_lores.pdf Axeda] |
+ | * developed and promoted by [http://www.axeda.com/system/files/datasheet/axeda_ds_ammp_120913_lores.pdf Axeda] |
* Minimal bandwidth consumption, to save cost on cellular/satellite connections |
* Minimal bandwidth consumption, to save cost on cellular/satellite connections |
Latest revision as of 08:09, 13 April 2014
simple, byte-efficient, lightweight messaging protocol used to facilitate M2M communications and to build Internet of Things (IoT) connectivity into the edge device.
- developed and promoted by Axeda
- Minimal bandwidth consumption, to save cost on cellular/satellite connections
- Very small footprint, to fit into even resource-constrained devices
- HTTP/HTTPS
- RESTFful
- JSON Format
- HTTPS
- standard HTTP authentication and SSL/TLS transmission security.
Data Model
- Data items – machine/sensor data elements representing status and current readings
- Location – representing current geo-location as latitude, longitude, altitude
- Alarms – indicating problem situations and corresponding detail
- Events – condition reports
- Uploaded content – binary or file-based content sourced at the edge
- Downloaded content – binary or file-based content deployed from the Axeda Machine Cloud Connected Content™ application
Examples
/ammp/files {dir:firmware.bin} /ammp/data {kwh:1078} /ammp/data {location:42.1, -72.5}