Difference between revisions of "M2MBridge Functionality"
From AMTech WikiDocs
| Line 3: | Line 3: | ||
**SNMP, LLRP, iBeacon, eddystone, PLC, GPIO, EPC and many others proprietary protocols | **SNMP, LLRP, iBeacon, eddystone, PLC, GPIO, EPC and many others proprietary protocols | ||
* Device-to-device or device-to-cloud communications (connecting the devices to the cloud) | * Device-to-device or device-to-cloud communications (connecting the devices to the cloud) | ||
| − | **LoRa, wifi, classic Bluetooth, BLE, 802.11ah , ZigBee | + | **LoRa, wifi, classic Bluetooth, BLE, 802.11ah , ZigBee, [http://www.link-labs.com/symphony/ Symphony Link] |
* Allow remote and centralized administration of IoT devices and gateways. | * Allow remote and centralized administration of IoT devices and gateways. | ||
* Configurable auto-discover | * Configurable auto-discover | ||
Revision as of 14:10, 30 April 2016
- Configurable edge intelligence
- Integrated devices and M2M protocols (data and commands from/to devices)
- SNMP, LLRP, iBeacon, eddystone, PLC, GPIO, EPC and many others proprietary protocols
- Device-to-device or device-to-cloud communications (connecting the devices to the cloud)
- LoRa, wifi, classic Bluetooth, BLE, 802.11ah , ZigBee, Symphony Link
- Allow remote and centralized administration of IoT devices and gateways.
- Configurable auto-discover
- Implements common functionality and orchestrates the execution of the protocols
- Network failure detection and recovery
- Get centralized configuration information at startup and real time modifications
- Access control policies to manage observation production and consumption
- The following diagram illustrates a M2MBrdige configuration:
- Using LLRP protocol to get the data from EPC tags and send commands to the reader
- Using SNMP to monitor the health o the readers
- Implementing smoothing, decoding, grouping, access control and other edge intelligence
