Blockchain Service Mesh for Physical World Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing blockchain systems lack efficient mechanisms for exchanging information, value, or tokens between blockchain networks and the real physical world, limiting their integration and utility.

Innovation Solution

A blockchain-enabled service-based cloud native function (CNF) architecture that incorporates smart contracts and a service mesh network, allowing for the recording of network slicing information on a blockchain and enabling secure, decentralized operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If blockchain networks operate as isolated peer-to-peer systems, then decentralization and security are maintained, but integration with the physical world and exchange of value are limited

Engineering Contradiction:
Improveintegration with physical worldVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces service mesh networks and smart contracts as intermediary layers between isolated blockchain networks and the physical world. These intermediaries enable value exchange and information flow while maintaining the decentralized security model, resolving the contradiction between isolation and integration.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates universal blockchain service meshes that can handle multiple types of transactions and interactions across different blockchain networks and with physical systems. This multi-functional architecture enables broad integration without requiring separate specialized systems for each use case.

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

2Productivity

If smart contracts are deployed to enable automated transactions, then operational efficiency improves, but system complexity and security verification requirements increase

Engineering Contradiction:
Improvetransaction processing efficiencyVSAvoidsmart contract verification complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements preliminary verification mechanisms where smart contracts and service mesh configurations are validated and verified before deployment. This preliminary action ensures security and correctness upfront, enabling automated transactions to proceed with high efficiency without compromising security during execution.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If network slicing information is recorded on blockchain, then transparency and trust are enhanced, but data storage requirements and network overhead increase

Engineering Contradiction:
Improvenetwork operation trustworthinessVSAvoidblockchain data volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts and separates critical network slicing verification data for storage on the blockchain, while keeping detailed operational data in off-chain storage systems. This extraction approach maintains transparency and trust for essential network operations without burdening the blockchain with excessive data volumes.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12212680B2Verifying integrity and secure operations of cloud-based software services
Publication Date: 2025.01.28 VM INNOVATIONS I LLC
  • US12212680B2 patent drawing
  • US12212680B2 patent drawing
  • US12212680B2 patent drawing

AI summary

A method for creating a build product including receiving from an application build request from a user, the build request including an application source code and a list of third-party packages, defining a plurality of third-party packages. The method further includes sending a build request to a build server, receiving a first acknowledgment from the build server, receiving the plurality of third-party packages, defining received third-party packages, building an application image from the application source code and the received third-party packages, defining a container image, and sending the container image to a verification server.