IoT Service Modeling Layered Abstraction for Application Reusability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Internet of Things (IoT) solutions face inefficiencies due to the inflexible binding of applications to specific devices, leading to costly reconfiguration and resource inefficiencies when devices malfunction or when multiple applications are deployed in the same environment.
Innovation Solution
Implementing a layered abstraction approach that includes capability and resource abstraction layers, allowing applications to be configured with abstracted device capabilities and resources, enabling seamless substitution of devices and sharing of resources across multiple applications through virtual instances and runtime abstraction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IOT applications are bound to specific devices with unique identifiers, then device-specific functionality is achieved, but reusability and adaptability are reduced
Solution Approach 1:
The patent segments the binding relationship into two independent layers: capability binding (functional requirements) and device binding (physical identifiers). This allows applications to be bound to capabilities rather than specific device IDs, enabling the same application to work with multiple devices that provide the same capability, thus improving reusability while maintaining device-specific functionality through the capability abstraction layer
Solution Approach 2:
The patent introduces a capability binding layer as an intermediary between applications and devices. This mediator translates device-specific identifiers into capability-based abstractions, allowing applications to interact with devices through capability interfaces rather than direct device bindings. The intermediary enables flexible device substitution and resource sharing while preserving the application's functional requirements
2Stability of the object's composition
If IOT applications are permanently bound to particular devices, then stable operation is achieved, but reconfiguration becomes time-consuming and costly when devices malfunction
Solution Approach 1:
The patent transforms the static device binding into a dynamic capability binding system. Applications are bound to capabilities that can be provided by multiple devices, allowing the system to dynamically reconfigure device assignments when devices malfunction. The capability binding layer maintains operational stability by ensuring functional requirements are met while enabling easy reconfiguration through capability-based device selection rather than fixed device bindings
3Ease of operation
If multiple IOT applications are deployed in the same environment with dedicated devices, then device allocation is simplified, but resource efficiency decreases and costs increase
Solution Approach 1:
The patent enables devices to serve multiple applications through capability-based binding. Instead of dedicating specific devices to specific applications, devices expose their capabilities that can be bound by multiple applications as needed. This universal approach allows a single device to support multiple applications sharing the same capability requirements, improving resource efficiency and reducing the total number of devices needed while maintaining simple device allocation through the capability abstraction layer
Data Source
AI summary
Systems, apparatuses and methods may identify a capability abstraction in a request to configure a first Internet of Things (IOT) application in a physical environment including a plurality of IOT devices and select a resource abstraction from a plurality of resource abstractions based on the capability abstraction. The selected resource abstraction may correspond to a first IOT device in the plurality of IOT devices. Additionally, the first IOT application may be bound with the first IOT device. In one example, first data originating from the first IOT device is received, a first runtime abstraction is selected from a plurality of runtime abstractions, wherein the first runtime abstraction corresponds to the first IOT application, and the first data is sent to the first IOT application via the first runtime abstraction.