Device Common Model Interface for Protocol-Agnostic Fabric Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing user applications for distributed computing systems is complicated due to the heterogeneity of devices and varying communication protocols, requiring developers to create custom code for each protocol, which increases development time and complexity.

Innovation Solution

The device common model interface translates a schema into a common object model and target-specific data models, abstracting away protocol details, allowing applications to interact with devices independently of communication protocols, thus enabling protocol-agnostic development.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers create custom code for each communication protocol, then applications can interact with diverse devices, but development time and complexity increase

Engineering Contradiction:
Improveapplication compatibilityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces a code generation system as an intermediary that automatically translates device schemas into protocol-specific code. This mediator handles the complexity of protocol variations, allowing developers to work with a unified device model while the system generates the necessary protocol-specific implementations, thereby reducing development time without sacrificing compatibility

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-generating protocol-specific code templates and data models based on device schemas before actual application development. This advance preparation creates reusable code components that can be directly applied to multiple devices, eliminating the need to write custom protocol code from scratch for each device type

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If developers create custom code for each communication protocol, then applications can interact with diverse devices, but development complexity increases

Engineering Contradiction:
Improveapplication compatibilityVSAvoiddevelopment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the development process into distinct components: a universal device schema layer, a code generation system layer, and protocol-specific implementation layers. This segmentation allows developers to work at the abstract schema level without being burdened by protocol complexities, while the system handles the translation to specific protocol implementations

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The code generation system serves multiple functions: it parses device schemas, generates protocol-specific code, creates data models, and produces API implementations. This multi-functional tool consolidates what would otherwise require multiple separate development processes, reducing overall development complexity while maintaining support for diverse protocols

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

3Ease of operation

If a common interface abstracts protocol details, then development is simplified, but protocol-specific operations may be lost

Engineering Contradiction:
Improvedevelopment easeVSAvoidprotocol details
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent adds a dimensional layer to the interface architecture by creating a schema-level abstraction that sits above protocol-specific implementations. This additional dimension allows the common interface to capture essential device characteristics without being constrained by protocol details, while the code generation system ensures protocol-specific information is preserved in the generated code

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS10140100B2Device common model interface
Publication Date: 2018.11.27 GOOGLE LLC
  • US10140100B2 patent drawing
  • US10140100B2 patent drawing
  • US10140100B2 patent drawing

AI summary

A device common model interface is described that translates a schema describing a resource in a fabric network into a common object model and one or more target-specific data models, using a specification of a target application environment and a specification of a communication protocol. Elements of the schema that are useful for an application are extracted to generate the common object model and the one or more target-specific data models are provided to the application. The application interacts with an interface of the resource using the API of the target-specific data model, which performs operations that are specific to communicating with the resource in the target application environment and using the communication protocol.