Software Distribution via Transport Containers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing methods for distributing software and data across different systems are complex and prone to errors due to the need for multiple systems and various distribution tools, which increases the risk of mistakes during the software distribution process.

Innovation Solution

A method that involves determining a software object to be transported, creating a transport request with an object list, defining a transport container, and including the software object in it, and providing the transport request to the target system, allowing for the streamlined distribution of software and data across systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple distribution tools are used to distribute different software applications, then the distribution capability is enhanced, but the risk of making mistakes during the software distribution process increases

Engineering Contradiction:
Improvedistribution capabilityVSAvoidrisk of mistakes
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies universality by creating a single transport container format that can hold multiple different software objects (applications, updates, patches) and transport requests. This universal container structure allows one distribution mechanism to handle diverse software content, eliminating the need for multiple specialized distribution tools while maintaining the ability to distribute various software applications reliably.

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

2Reliability

If multiple systems (customization system, quality assurance system, productive system) are used for software distribution, then the software distribution process is made more reliable, but the device complexity increases

Engineering Contradiction:
Improvesoftware distribution reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the software distribution process into distinct phases (customization, quality assurance, productive systems) while using a unified transport container format across all systems. This segmentation allows each system to perform its specific function (customization for development, QA for testing, productive for deployment) while maintaining a consistent, simplified transport mechanism that reduces overall complexity compared to having different distribution mechanisms for each system.

Inventive Principle:
Principle #1Segmentation

3Reliability

If changes are transported through multiple systems (customization system to quality assurance system to productive system), then the changes are thoroughly tested and validated, but the time required for software distribution increases

Engineering Contradiction:
Improvechanges validationVSAvoiddistribution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent enables continuous transport of software changes through multiple systems using the same transport container format, eliminating interruptions and reprocessing. The container maintains change integrity throughout the journey from customization system to quality assurance system to productive system, allowing seamless transitions that reduce total distribution time while ensuring thorough validation at each stage.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS8200787B2Methods and systems for distributing software
Publication Date: 2012.06.12 SAP SE
  • US8200787B2 patent drawing
  • US8200787B2 patent drawing
  • US8200787B2 patent drawing

AI summary

Systems and methods consistent with the invention relate to the distribution of software. According to one exemplary embodiment, a method for distributing software from a first system to a second system may comprise determining a software object to be transported. The method may then create, on the first system, a transport request comprising an object list. The method may also define, on the first system, a transport container and include the software object in the transport container. Further, the transport container may be included in the object list of the transport request. The transport request may then be provided to the second system.