Device command identifiers used by Edgent.
Device event identifiers used by Edgent.
A generic IoT device IoT hub connector.
A generic IoT gateway device IoT hub connector.
Device event quality of service levels.
An IoT device heartbeat event generator.
An IoT environment consists of an enterprise IoT message hub and devices and other clients connected to it. Each IoT device has an identity in the hub. The form of a device's identity is the domain of an IoT hub implementation. How a device becomes registered to an IoT hub and generally what device management capabilities exist and how a device is managed is beyond the scope of the "analytic pipelines" focused Edgent APIs.
An IoT device can publish device events to and receive device commands from an IoT hub. An IoT gateway device is an IoT device that is also conduit for a collection of IoT devices that lack direct connection to the enterprise IoT hub. A gateway can publish events on behalf of its connected devices and receive commands from the hub targeted to them. An Edgent IoT hub connector bridges the gap between this generic model and and particular IoT hub implementation's underlying protocols.
More specifically, the generic IoT device model consists of:
publishesevents as messages to a message hub to allow analysis or processing by back-end systems, etc.. A device event consists of:
Quality of servicefor message delivery. Using MQTT QoS definitions.
subscribesto commands from back-end systems through the message hub. A device command consists of:
Device event and command identifiers starting with "
are reserved for use by Edgent.
Copyright © 2016–2017 The Apache Software Foundation. All rights reserved.