Blockchain Service Processing for IoT Multi-Party Collaboration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies face challenges in providing effective collaboration and data sharing across multiple-party platforms in IoT applications, where intelligent interaction between devices depends on data interaction, and centralized control can hinder sharing and cooperation.

Innovation Solution

The implementation of a blockchain-based service processing architecture that utilizes smart contracts and an association center to route events to corresponding smart contracts, enabling decentralized service execution and data sharing by associating event models with smart contracts and invoking them through a blockchain network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized data center platform is used for service processing, then service control and data management are simplified, but multi-party collaboration and data sharing capabilities are limited

Engineering Contradiction:
Improveservice control and data managementVSAvoidmulti-party collaboration and data sharing
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces a blockchain as an intermediary layer between centralized data centers and IoT devices. The blockchain network enables multi-party collaboration by allowing different organizations to write smart contracts and share data without requiring a single centralized authority, thus resolving the contradiction between operational simplicity and collaborative versatility

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the centralized service processing into distributed smart contracts deployed across multiple blockchain nodes. Each smart contract can be independently written and executed by different service parties, enabling segmented control that maintains operational simplicity for individual services while achieving versatile multi-party collaboration across the network

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If smart contracts are deployed on a blockchain network, then multi-party data sharing and collaboration are enabled, but system complexity increases

Engineering Contradiction:
Improvemulti-party data sharing and collaborationVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements self-service through automated smart contracts that execute service processing logic without human intervention. The blockchain network automatically validates transactions, enforces contracts, and manages data sharing between parties, reducing the need for complex manual coordination and administrative overhead despite the underlying system complexity

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent changes the operational parameters from centralized manual control to decentralized automated execution. By transforming service processing from human-managed to machine-executed smart contracts, the system handles complexity internally while presenting simplified interfaces to users and service parties

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11381383B2Methods and apparatuses for processing service using blockchain
Publication Date: 2022.07.05 ALIPAY (HANGZHOU) INFORMATION TECH CO LTD
  • US11381383B2 patent drawing
  • US11381383B2 patent drawing
  • US11381383B2 patent drawing

AI summary

An exemplary method for processing a corresponding service based on an event detected at a physical device using a blockchain includes receiving an event model identifier and data of an event, wherein the event model identifier indicates an event model for describing the event, and the data comprises one or more parameters in the event model; determining a contract identifier associated with the event model identifier based on a predetermined relationship between the event model identifier and the contract identifier; identifying a smart contract in a blockchain network based on the contract identifier; and sending a request that invokes the smart contract to a first node in the blockchain network based on the contract identifier and that causes each node in the blockchain network to invoke the smart contract based on the data to perform service processing logic corresponding to the smart contract.