Multiplexed Telemetry Registration for IoT Memory Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
IoT devices face challenges in efficiently communicating telemetry data due to the need to handle multiple software development kits (SDKs) and application programming interfaces (APIs) for provisioning and data reporting, which increases memory and processing requirements, especially for low-power devices.
Innovation Solution
A telemetry device is configured to multiplex telemetry data with a registration message and send a single multiplexed transmission to a single IoT endpoint, allowing the endpoint to handle provisioning and data forwarding, thus reducing the device's memory and computational burden.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple SDKs and APIs are used for provisioning and telemetry reporting, then device functionality is complete, but memory and processing requirements increase
Solution Approach 1:
The patent combines multiple separate communication functions (provisioning and telemetry reporting) into a single unified endpoint. The device uses one SDK and one API to communicate with the IoT hub for both device provisioning and telemetry data reporting, eliminating the need to maintain multiple SDKs and APIs. This merging reduces memory footprint and processing overhead while preserving complete device functionality.
Solution Approach 2:
The IoT hub endpoint is designed to perform multiple functions: it handles both device provisioning (registration, authentication) and telemetry data reporting through a single unified interface. This multi-functional endpoint eliminates the need for separate specialized endpoints, allowing low-power devices to use a single SDK/API combination for all communication needs.
2Adaptability or versatility
If separate endpoints are used for provisioning and telemetry reporting, then service specialization is improved, but device communication complexity increases
Solution Approach 1:
The patent merges the provisioning service and telemetry reporting service into a single unified endpoint at the IoT hub. Instead of the device needing to communicate with separate specialized endpoints for provisioning and telemetry, both services are consolidated into one endpoint that the device accesses through a single SDK and API, significantly simplifying device communication logic.
Solution Approach 2:
The unified IoT hub endpoint acts as an intermediary that handles both provisioning and telemetry functions. The device interacts with this single intermediary for all communication needs, and the intermediary internally routes requests to appropriate service handlers, shielding the device from the complexity of service specialization.
3Adaptability or versatility
If low-power devices use multiple SDKs and APIs, then comprehensive communication capability is achieved, but device power consumption increases
Solution Approach 1:
The patent combines multiple communication protocols and interfaces into a single unified communication path through one SDK and API. Low-power devices only need to maintain one active communication stack instead of multiple, reducing the computational overhead and memory access operations that consume power, while still achieving comprehensive communication capability through the unified endpoint.
Solution Approach 2:
The single SDK and API provide universal communication capability for both provisioning and telemetry functions. This multi-functional interface eliminates the need for low-power devices to switch between or maintain multiple specialized communication stacks, reducing power consumption while preserving complete communication capability across different operational modes.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Examples are disclosed that relate to using a multiplexed transmission to register a telemetry device with a telemetry system and report telemetry data to the telemetry system on behalf of a telemetry device. One disclosed example provides a method comprising receiving a multiplexed transmission from a telemetry device, the multiplexed transmission comprising a registration message and telemetry data, demultiplexing the multiplexed transmission to obtain the registration message and the telemetry data, registering the telemetry device with a telemetry system based upon the registration message, sending the telemetry data to the telemetry system, and sending a registration response to the telemetry device, the registration response confirming registration of the telemetry device with the telemetry system.