Package Replication via Manifest Dependency Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional digital distribution platforms lack flexibility in providing different software applications to different users based on region, operating system, and computing environment, and they do not effectively manage dependencies, leading to inefficient distribution and potential single points of failure.

Innovation Solution

A computer-implemented method for controlling access to and replication of packages across multiple regions, where packages include binary files and manifests that determine dependencies, allowing for decentralized distribution, flexible access control, and consideration of dependencies to optimize distribution bandwidth.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a centralized digital distribution platform provides the same software applications to all users, then system simplicity is maintained, but flexibility and adaptability to different regions and users are reduced

Engineering Contradiction:
Improveflexibility in providing different software applicationsVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is divided into multiple independent regions, each capable of autonomously managing and distributing software packages. This segmentation allows each region to customize software availability for its users while maintaining overall system functionality through standardized package formats and dependency management mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal package format with manifests that can be replicated and distributed across multiple regions. The dependency management system and package structure serve multiple functions: enabling regional customization, ensuring software compatibility, optimizing bandwidth usage through shared dependencies, and maintaining system-wide consistency through standardized interfaces.

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

2Productivity

If software applications are distributed as self-contained units without considering dependencies, then distribution simplicity is maintained, but distribution bandwidth efficiency is reduced

Engineering Contradiction:
Improvedistribution bandwidth efficiencyVSAvoiddependency management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges common dependencies into shared repositories that can be accessed by multiple packages and regions. Instead of duplicating identical dependency files across all packages, the system combines them into centralized locations with manifest entries that reference these shared resources, reducing redundant data transmission and storage while maintaining package independence through reference-based linking.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If a single regional distribution platform is used, then system simplicity is maintained, but reliability and fault tolerance are reduced

Engineering Contradiction:
Improvefault toleranceVSAvoiddistributed system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system is divided into multiple independent regions, each capable of autonomously managing and distributing software packages. This segmentation allows each region to customize software availability for its users while maintaining overall system functionality through standardized package formats and dependency management mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements package replication across multiple regions, creating copies of software packages and their manifests in each region's local repository. This copying mechanism ensures that if one region experiences failure or unavailability, users in other regions can still access and download the same software packages, thereby improving system reliability and fault tolerance.

Inventive Principle:
Principle #26Copying

4Ease of operation

If packages are replicated across multiple regions, then distribution efficiency and fault tolerance are improved, but control over package access and usage becomes more difficult

Engineering Contradiction:
Improveaccess control flexibilityVSAvoidaccess control system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements region-specific access control policies where each region can independently define which packages are available to its users and under what conditions. The manifest files contain region-specific metadata and access control information that allows local customization of package availability while maintaining consistent package structures and dependency relationships across all regions.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP4567586A1Controlling access to and replication of packages
Publication Date: 2025.06.11 SAP SE
  • EP4567586A1 patent drawingFigure 1
  • EP4567586A1 patent drawingFigure 2
  • EP4567586A1 patent drawingFigure 3

AI summary

According to an aspect, a computer implemented method, a computer program and a computer system for controlling access to and replication of packages are provided. The computer implemented method comprises creating a first package at a first region of a plurality of regions, wherein the plurality of regions is communicatively connected via a computer network. The first package includes at least one binary file and manifest for the at least one binary file. The method further comprises replicating, using the manifest, the first package from the first region to a second region of the plurality of regions. The replicating comprises using the manifest to determine dependencies of the at least one binary file. The method further comprises publishing the first package to the second region. The publishing comprises making the at least one binary file of the first package available at the second region and displaying a description of the at least one binary file according to the manifest at the second region.