Device Capability Model Resolution for IoT Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Interoperability issues between device code and software solution backends in IoT devices lead to increased development times and workloads, as well as limited adaptability of software solutions across different IoT device types.

Innovation Solution

A computing system method that resolves and retrieves a device capability model (DCM) by searching various sources based on a specified policy, allowing software solutions to efficiently integrate with network-connected devices and reuse software services across different devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software solutions are developed for specific IoT device types, then device-specific functionality is achieved, but adaptability to other device types is limited

Engineering Contradiction:
Improveadaptability to different device typesVSAvoidsoftware solution complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal DCM repository and resolution service that can handle multiple device types through a common interface. The system stores DCMs for different device types in a centralized repository and provides a unified resolution mechanism that adapts to various device capabilities without requiring separate software solutions for each device type.

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

Solution Approach 2:

The patent segments the software architecture into distinct components: device capability models (DCMs) that describe individual device characteristics, a centralized repository that stores multiple DCMs, and a resolution service that selectively retrieves appropriate DCMs. This segmentation allows the system to maintain simplicity while supporting diverse device types.

Inventive Principle:
Principle #1Segmentation

2Speed

If device capability models are stored locally on each computing system, then fast retrieval is achieved, but storage space requirements increase

Engineering Contradiction:
ImproveDCM retrieval speedVSAvoidstorage space
Core Design Contradiction:
SpeedVSVolume of stationary object

Solution Approach 1:

The patent merges the DCM storage functionality into a centralized repository that serves multiple computing systems. Instead of each system maintaining its own complete set of DCMs, the system combines storage resources into a shared repository, reducing total storage requirements while providing fast retrieval through the resolution service.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces a DCM resolution service as an intermediary between computing systems and the DCM repository. This mediator handles retrieval requests, caches frequently accessed DCMs locally, and manages the balance between centralized storage efficiency and local retrieval speed, eliminating the need for each system to store complete DCM sets.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If DCM resolution searches multiple sources, then comprehensive device support is achieved, but resolution time increases

Engineering Contradiction:
Improvedevice capability model accuracyVSAvoidDCM resolution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary actions by establishing a standardized resolution policy that defines the search order across multiple sources before actual resolution occurs. The system pre-configures the resolution hierarchy (local cache, repository, device-provided) and caches frequently accessed DCMs in advance, so that during operation, the system can quickly resolve DCMs without ad-hoc searching through multiple sources.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4004718B1Discovery and resolution of network connected devices
Publication Date: 2024.04.24 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP4004718B1 patent drawingFigure 1
  • EP4004718B1 patent drawingFigure 2
  • EP4004718B1 patent drawingFigure 3

AI summary

One disclosed example provides, enacted on a computing system, a method of resolving a device capability model (DCM) for a network connected device, the method comprising receiving, from the network connected device, an identifier of the DCM, based on the identifier received, determining whether the DCM is stored on the computing system, when the DCM is stored on the computing system, then retrieving the DCM from the computing system, when the DCM is not stored on the computing system, then retrieving the DCM from one or more of the network connected device and a DCM repository and storing the DCM on the computing system, receiving, from a software solution, an application programming interface (API) call to retrieve the DCM from the computing system, and in response to receiving the API call, returning the DCM to the software solution.