Automated DLS Integration Service for Ledger Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing and deploying DLS-enabled applications is a time- and resource-intensive process due to the need for creating and managing decentralized systems, integrating with existing applications, and maintaining transactional consistency across different platforms.

Innovation Solution

An automated development, deployment, and integration service (ADDIS) that provides a DLS-enriched view of data, generates DLS-specific entities and chaincode, and monitors staging tables to record data to a distributed ledger system, enabling efficient development, deployment, and integration of DLS-enabled applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual processes are used for creating and deploying DLS-enabled applications, then flexibility and control are maintained, but development time and resource requirements increase significantly

Engineering Contradiction:
Improvedevelopment speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system enables self-service automation where the deployment service automatically performs development, deployment, and integration tasks for DLS-enabled applications. The service autonomously creates DLS networks, deploys chaincode, manages lifecycle, and integrates with non-DLS applications without requiring manual intervention for each task, thereby significantly improving development speed while managing complexity through automated service orchestration.

Inventive Principle:
Principle #25Self-service

2Loss of time

If automated processes are used for DLS application deployment, then development time is reduced, but integration complexity with existing applications increases

Engineering Contradiction:
Improvedeployment timeVSAvoidintegration complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The deployment service acts as an intermediary layer between non-DLS applications and the DLS network. It provides automated integration by handling data synchronization, transactional consistency, and communication protocols between legacy applications and the distributed ledger system. This intermediary approach reduces deployment time while managing integration complexity through standardized interfaces and automated coordination mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If comprehensive lifecycle management is implemented for DLS-enabled applications, then reliability is improved, but resource requirements increase

Engineering Contradiction:
Improvetransactional consistencyVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The deployment service provides universal lifecycle management capabilities that handle multiple functions including network creation, chaincode deployment, application monitoring, and integration management through a single unified service. This multi-functional approach improves transactional consistency and reliability across the entire DLS application lifecycle while optimizing resource consumption by consolidating management operations into a centralized service rather than requiring separate resources for each lifecycle stage.

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

Data Source

PatentUS12095899B2Automated development, deployment and integration service for distributed ledger-enabled applications
Publication Date: 2024.09.17 SAP SE
  • US12095899B2 patent drawing
  • US12095899B2 patent drawing
  • US12095899B2 patent drawing

AI summary

Methods, systems, and computer-readable storage media for providing a DLS-enriched view on data stored in a database system, the DLS-enriched view including a set of annotations indicating at least one application table and at least one field of the application table, storing a staging table corresponding to the application table field and a database trigger that is configured to write data from the field to the staging table in response to a change in the at least one application table, providing at least one IR artifact based on the DLS-enriched view, generating at least one DLS-specific entity and chaincode based on the IR artifact and a configuration for a DLS, to which the chaincode is to be deployed, deploying the chaincode to the DLS, and monitoring the one or more staging tables for changes and, in response to a change, recording data of the staging table to the DLS.