External Chaincode Executor Controller for Delegated Data Models
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Blockchain platforms face challenges in integrating new data models into smart contract APIs due to the complexity of adding or replacing world state databases, which are integrated into the architecture, and fail to support different database types efficiently.
Innovation Solution
An external CC executor controller and peer controller are introduced to facilitate the non-intrusive integration of new data models by supporting delegated execution of smart contracts, utilizing a block tracking circuit, block committer circuit, and data model type chaincode interfaces to convert and store data points in native databases, enabling efficient processing of time series and graph data models.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a new world state database is added or replaced in the blockchain platform, then the system can support different data models, but the integration complexity increases significantly
Solution Approach 1:
The system segments the database integration by introducing separate Data Access Layers (DALs) for different data models (key-value, time-series, graph). Each DAL is an independent module that handles specific data model operations, allowing the system to support multiple data models without increasing overall integration complexity. The external CC executor controller coordinates these segmented DALs through standardized interfaces.
Solution Approach 2:
The patent introduces an intermediary layer (the external CC executor controller and DAL architecture) between the smart contract execution engine and the various data models. This intermediary translates smart contract data access requests into model-specific operations, enabling support for different data models without requiring direct integration complexity in the core execution engine.
2Adaptability or versatility
If the blockchain platform supports multiple database types, then data model versatility improves, but the existing architecture integration becomes more difficult
Solution Approach 1:
The external CC executor controller is designed as a universal component that can coordinate multiple types of Data Access Layers through standardized interfaces. This multi-functional design allows the same controller architecture to support key-value, time-series, and graph databases without requiring separate integration paths, thereby improving ease of manufacture while maintaining database type versatility.
Solution Approach 2:
The patent adds a new dimensional layer (the DAL architecture) to the existing blockchain platform stack. Instead of integrating multiple database types directly into the core architecture (horizontal integration), the solution creates a vertical layer that sits between the execution engine and data models, transforming the integration problem from a horizontal complexity issue to a vertical layering solution.
3Productivity
If smart contracts are executed with delegated execution, then processing efficiency improves, but coordination between external executor and peer controller becomes more complex
Solution Approach 1:
The system implements feedback mechanisms where the external CC executor controller registers for block events with peer controllers and receives notifications of new blocks. This feedback loop enables automated coordination - when a new block is detected, the system automatically retrieves and executes relevant smart contracts without requiring manual intervention or complex real-time negotiation, thereby improving execution efficiency while managing coordination complexity through event-driven feedback.
Data Source
AI summary
An external chaincode (CC) executor controller includes a block tracking circuit to register for events and a first data model type data access layer (DAL) to receive a data point and convert the data point to a native first data model type to be stored in a first data model type database. Furthermore, a second data model type DAL receives the data point and converts the data point to a native second data model type to be stored in a second data model type database. Moreover, a block committer circuit receives a new block notification and determines that the new block notification includes a smart contract data model, and in response thereto dispatch the smart contract to the first data model type DAL or to the second data model type DAL to support delegated execution of the smart contract data model efficiently and reliably.