Cross-Application Content Package Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of software systems and licensing requirements hinder the sharing and deployment of software updates and content, limiting their availability to users with multiple software products, even if the updates or content could be beneficial, due to the need for specific licenses for combined applications.

Innovation Solution

The solution involves defining packages of cross-application content that can be used with either a single application or multiple applications, allowing for the creation and deployment of packages based on available applications on a client system, without requiring a license for specific cross-application combinations, enabling the use of cross-application content as long as the necessary applications are installed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If packages are defined to include cross-application content requiring licenses for multiple applications, then the content can provide enhanced functionality for multi-application environments, but the content becomes inaccessible to users with only a single application, limiting usability

Engineering Contradiction:
Improvecross-application content availabilityVSAvoidcontent accessibility
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments content packages into two distinct types: single-application packages containing content accessible to users with only one application, and multi-application packages containing content requiring licenses for multiple applications. This segmentation allows users to access appropriate content based on their specific application environment without being blocked by licensing requirements for applications they don't have, thereby resolving the contradiction between adaptability and ease of operation

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic package selection where the system automatically determines which type of package (single-application or multi-application) to deploy based on the user's current application environment. This dynamic approach ensures that content is always accessible to users regardless of whether they have one or multiple applications licensed, eliminating the accessibility barrier while maintaining the ability to provide enhanced multi-application functionality when available

Inventive Principle:
Principle #15Dynamics

2Reliability

If separate licenses are required for cross-application content, then content protection and licensing control are maintained, but deployment complexity increases and updates are released less frequently

Engineering Contradiction:
Improvelicensing controlVSAvoiddeployment complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments licensing control into two independent licensing streams: one for single-application content and another for multi-application content. Each stream has its own licensing requirements and deployment pathways. This segmentation simplifies deployment by allowing content to be distributed through appropriate channels based on the target environment, reducing the complexity of managing cross-application licenses while maintaining reliable licensing control for each content type

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism (the package management system) that automatically handles licensing verification and content deployment. This intermediary abstracts the complex licensing logic from the deployment process, automatically determining which licensing path to follow based on the user's application environment, thereby reducing deployment complexity while maintaining licensing reliability

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If content is limited to single-application packages, then deployment is simpler and more frequent, but content cannot leverage functionality from multiple applications even when available

Engineering Contradiction:
Improvedeployment frequencyVSAvoidmulti-application functionality
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments content into single-application packages for frequent, simple deployments and multi-application packages for enhanced functionality when available. This segmentation allows both deployment types to coexist, with single-application packages maintaining high deployment frequency and simplicity, while multi-application packages provide the ability to leverage cross-application functionality when the user environment supports it

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal package distribution system that can handle both single-application and multi-application content through a unified interface. This universal system allows content to be deployed appropriately based on the target environment, enabling single-application packages to maintain simple frequent deployment while multi-application packages can leverage functionality from multiple applications when available, without requiring separate deployment systems

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

Data Source

PatentUS11941386B2Flexible provision of multi-application content
Publication Date: 2024.03.26 SAP SE
  • US11941386B2 patent drawing
  • US11941386B2 patent drawing
  • US11941386B2 patent drawing

AI summary

Techniques and solutions are described for defining and deploying application content. Content, such as objects, can be created in a repository defined for a first application. A package can be defined based at least in part on the objects for use in a computing environment only requiring the first application. A second package can be defined based at least in part on the objects for use in a computing environment in which both the first application and a second application are available. Content can be moved between repositories defined for a single application and repositories defined for multiple applications. Content can be added to, or removed from, a client computing system as applications available on a client computing system change.