Since we understand the devices and gateways, let us go deeper into the IoT Hub. We will specifically talk about the features of the Klyff Hub as well.
Some terminology would be handy to get an understanding of the features of the Hub
Telemetry: Telemetry is the recording and transmitting of values received by an IoT device.
Provisioning: This allows the cloud to identify the device to the cloud uniquely. Provisioning also establishes the device’s security protocols and access rights and privileges.
Routing: Message routing enables you to send messages from your devices to cloud services in an automated, scalable, and reliable manner. You can send either device telemetry messages or events (for example device lifecycle events). This is the two-way communication between the cloud and the device.
Scaling: For cloud solutions, scaling involves the need to ramp up or down the scope of the solution.
Service availability: Service availability aims to ensure an agreed level of operational performance (typically uptime) for a cloud service. Service availability is defined by the service level agreement (SLA).
Now the Klyff Hub is responsible for
- Device identity and registry – maintains information about the device, and services that it is approved to connect to on the Hub. Without the registry, the device is alien to the Hub.
- Securing communication between the device and the cloud. Hub grants access to endpoints by verifying a token against the shared access policies and identity registry security credentials. You can use any X.509 certificate to authenticate a device with IoT Hub.
- Scale the solution as per the demand
- Route device data based on automated rules to route optimize data traffic
- Send commands to the devices
- Manage and configure the devices – querying the status of the device and responding to state changes in the device – Device twins are JSON documents that store device state information, including metadata, configurations, and conditions. Klyff Hub maintains a device twin for each device that you connect to IoT Hub.
- Monitoring of the health of the devices and the cloud
- Integration with other internal and 3rd party services
- Resiliency and failover support
- Provide connection characteristics over various protocols like MQTT, MQTT over WebSockets, AMQP, AMQP over WebSockets, and HTTPS
The complexity of the Hub or which features of the Hub to use would depend on the
- Complexity of the application
- Data throughput
- Security considerations
- Bi-directional communication
- Telemetry needs
- Geographic coverage
- Support for various kinds of devices
- Communication protocols
- Message routing
Based on your needs Klyff would access the needs and set up a relevant version of the Klyff Hub in either Montane, Alpine, or Snow tier
