Distributed Ledger Enterprise Application Lifecycle Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of managing enterprise application lifecycles across multiple environments and systems leads to inconsistent data and inefficient information collection, requiring manual processes and multiple teams to collaborate.

Innovation Solution

A distributed-ledger based system for lifecycle management and distribution of enterprise applications, using blocks of information as immutable records, shared by a permissioned network for real-time access and secure tracking.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple systems from various organizations are used to manage enterprise application lifecycle, then the application can be delivered and managed across different environments, but data inconsistency and information collection inefficiency occur

Engineering Contradiction:
Improveapplication deployment across environmentsVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent merges multiple distributed ledger systems into a single shared distributed ledger that all organizations access. This consolidation ensures that application lifecycle data (deployment, licensing, usage) is stored once and shared across all systems, eliminating data inconsistency while maintaining the ability to deploy applications across different environments.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The shared distributed ledger serves multiple functions simultaneously: it stores application deployment information, tracks licensing data, records usage metrics, and maintains version control. This universal data structure replaces multiple separate systems, providing consistent data access while supporting diverse application lifecycle management needs.

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

2Loss of information

If manual data collection from multiple systems is performed, then comprehensive information can be gathered, but the process becomes time-consuming and resource-intensive

Engineering Contradiction:
Improveinformation completenessVSAvoiddata collection time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The distributed ledger system enables self-service data collection where all participants automatically write their application lifecycle data to the shared ledger in real-time. When an application is deployed, licensed, or used, the information is automatically recorded by the respective organization's system without requiring manual collection from other teams, thus maintaining information completeness while eliminating time-consuming manual processes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements continuous feedback loops where each organization's actions (deployment, licensing, usage) are immediately recorded on the distributed ledger and visible to all other participants. This real-time feedback mechanism ensures that all teams have access to current information without needing to manually request or wait for data updates from other organizations.

Inventive Principle:
Principle #23Feedback

3Loss of information

If data is collected from multiple organizational systems, then comprehensive application lifecycle information can be obtained, but the complexity of coordination increases

Engineering Contradiction:
Improveinformation availabilityVSAvoidsystem coordination complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The shared distributed ledger acts as an intermediary layer between different organizational systems. Instead of systems directly interacting and coordinating with each other (which creates complexity), all data is written to and read from the neutral distributed ledger. This intermediary structure simplifies coordination by providing a standardized interface that all organizations use, while still enabling comprehensive information availability across the enterprise application lifecycle.

Inventive Principle:
Principle #24Intermediary (Mediator)

Applied Scientific Principles

This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.

Function Achieved in This Case

This approach ensures consistent and synchronized data across systems, reduces costs, and prevents data tampering, providing a secure and efficient method for managing enterprise application lifecycles.

Implementation Method 1

a distributed-ledger based system for lifecycle management and distribution of enterprise applications

Methodology Applied
Scientific EffectDistributed ledger technology:

Implementation Method 2

each of the proposal responses including a verification of the unique signature

Methodology Applied
Scientific EffectCryptographic verification:

Data Source

PatentUS10365922B1Distributed-ledger based enterprise application deployment and management
Publication Date: 2019.07.30 SAP SE
  • US10365922B1 patent drawing
  • US10365922B1 patent drawing
  • US10365922B1 patent drawing

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for a distributed ledger based management of an enterprise application lifecycle. In one aspect, a method includes receiving a notification regarding an availability of a latest version of an application; generating a transaction proposal that includes key value pairs and a unique signature; providing the transaction proposal to a plurality of peer nodes; receiving a proposal response from at least a portion of the peer nodes, each of the proposal responses including a verification of the unique signature; generating an endorsed transaction proposal based on validating the proposal responses according to an endorsement policy; providing the endorsed transaction proposal to an application management service; receiving the latest version of the application and a block of transactions, wherein the block of transactions includes the key value pairs; and storing the block of transactions to a distributed ledger.