IoT Asset Abstraction for Dynamic Device Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The management of Internet of Things (IoT) systems is complex due to the diverse range of devices with varying hardware, operating systems, and software applications, making it challenging to develop and deploy IoT applications, especially for users without formal training, as traditional tools limit post-deployment control and configuration.

Innovation Solution

An improved IoT development platform using asset abstraction and automated asset binding allows for the creation of IoT services with minimal human intervention, enabling post-deployment changes and dynamic device configuration, facilitating portability and reusability of IoT applications through abstracted device taxonomies and user interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional IoT development tools are used, then device connectivity and data collection capabilities are achieved, but system complexity and difficulty of deployment increase significantly

Engineering Contradiction:
Improvedevice connectivity capabilityVSAvoidsystem deployment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud-based service platform as an intermediary between IoT devices and end users. This platform handles device discovery, asset binding, and application deployment automatically, shielding users from the underlying complexity while maintaining versatile device connectivity capabilities

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements automated asset binding and configuration where the platform automatically discovers devices, binds assets to applications, and configures settings without requiring user intervention. This self-service mechanism reduces deployment complexity while preserving adaptability across diverse device types

Inventive Principle:
Principle #25Self-service

2Ease of manufacture

If traditional IoT tools with fixed pre-deployment configuration are used, then initial device setup is achieved, but post-deployment control and reconfiguration capabilities are limited

Engineering Contradiction:
Improveinitial device setup easeVSAvoidpost-deployment reconfiguration ease
Core Design Contradiction:
Ease of manufactureVSEase of operation

Solution Approach 1:

The patent implements dynamic configuration capabilities where application settings, asset bindings, and device parameters can be modified after deployment. The cloud platform enables real-time reconfiguration without requiring re-deployment, transforming static pre-configured systems into dynamically adaptable ones

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The service platform provides universal configuration management that works across different device types, applications, and deployment scenarios. A single unified interface handles both initial setup and post-deployment reconfiguration, eliminating the need for separate tools and processes

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If custom IoT applications are developed for specific devices, then device-specific functionality is optimized, but portability and reusability across different environments are reduced

Engineering Contradiction:
Improvedevice-specific functionality reliabilityVSAvoidapplication portability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the IoT system into independent modular components: device-agnostic application logic, device-specific asset configurations, and cloud-based binding layers. This segmentation allows applications to be developed once with reliable device-specific functionality while maintaining portability through configurable asset bindings that can be adapted to different environments

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3479218B1Dynamic user interface in machine-to-machine systems
Publication Date: 2024.02.14 INTEL CORP
  • EP3479218B1 patent drawingFigure 1A
  • EP3479218B1 patent drawingFigure 1B
  • EP3479218B1 patent drawingFigure 2

AI summary

User inputs received through a graphical user interface of a programming tool are used to define a set of capability abstractions for a particular application and further define, based on the one or more user inputs, relationships between the set of capability abstractions. The particular application is to utilize a machine-to-machine network, and the set of capability abstractions include: a sensor capability abstraction, an actuator capability abstraction, a computation logic capability abstraction, an input user interface (Ul) capability abstraction, and an output Ul capability abstraction for the particular application. The relationships include a relationship between the input Ul capability abstraction and the computation logic capability abstraction, where the input Ul capability is to provide an input to the computation logic capability abstraction. Service logic for the particular application is generated to deploy an instance of the particular application in an environment based on the set of capability abstractions and relationships.