Sensor Management Device Abstraction Layer Firmware Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The operation of sensors in modern devices is often specific to the sensor interface, manufacturer, or type, requiring device-specific firmware configuration and updates, which is cumbersome and not feasible for large-scale deployment, especially when manual updates are required and network-based updates exceed bandwidth capabilities of some devices.
Innovation Solution
A computerized method is implemented where a sensor management device establishes a network connection between a sensor definition layer and an end device's sensor abstraction layer, using generic data structures and communication formats to configure and collect sensor data, allowing for abstracted firmware management and reducing the need for device-specific updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual firmware updates are performed on end devices to support new or updated sensors, then the device can operate with updated sensor functionality, but the update process requires technical expertise, causes device downtime, and is not feasible for large-scale deployment
Solution Approach 1:
A sensor management device is introduced as an intermediary between the end device and sensors. The sensor management device stores sensor definition data and communicates sensor configuration information to the end device, eliminating the need for manual firmware updates on the end device. The end device receives sensor configuration data from the sensor management device and uses this data to operate sensors without requiring firmware changes.
2Adaptability or versatility
If over-the-air firmware updates are used to support new sensors, then device functionality can be updated remotely, but this requires high network bandwidth that exceeds the capabilities of some devices
Solution Approach 1:
Sensor definition data is extracted from the end device firmware and stored separately in the sensor management device. Only essential sensor configuration information is transmitted to the end device when needed, rather than transmitting complete firmware updates. This significantly reduces network bandwidth consumption while maintaining the ability to support new sensors.
3Reliability
If device-specific firmware is used to operate specific sensors, then the device can reliably operate connected sensors, but the device complexity increases and requires maintaining multiple firmware versions
Solution Approach 1:
The end device is designed with universal sensor operation capability through the sensor abstraction layer that can operate any sensor by receiving appropriate sensor definition data from the sensor management device. Instead of requiring different firmware versions for different sensors, a single universal firmware implementation works with all sensors by dynamically loading sensor-specific configuration information.
Data Source
AI summary
The disclosure herein describes enables new sensors to be added and maintained in an Internet of Things system without upgrading firmware for the end device. A sensor abstraction layer (SAL) manages the end sensors, and a sensor definition layer (SDL) in the cloud interfaces with the SAL. Sensor definition data of a sensor connected to the end device is identified in a sensor definition data store of the SDL including sensor configuration data. The sensor configuration data is sent to the SAL, wherein the SAL is configured to collect sensor data from the sensor via a sensor interface. Sensor data is received from the SAL via an established network connection and converted into converted sensor data based on a data conversion model of the sensor definition data. The converted sensor data is then provided to an application, connected to a sensor management device, for consumption.


