Standardized OS Deployment for Hybrid Cloud Infrastructure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In hybrid application architectures, integrating and migrating application components is costly and increases complexity, security risks, and operational costs due to the need for additional virtualization layers, which reduces the dynamics of the application landscape.

Innovation Solution

A method and system for distributing and operating a standardized operating system on network-based computer infrastructure by establishing a secure connection, authenticating components, installing necessary components, and authenticating the operating system instance, with a management structure having external and internal areas for secure key generation and authentication, allowing the customer to determine the life cycle of the operating system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If additional virtualization layers are introduced to support hybrid application architectures, then the system can accommodate diverse application components, but the complexity, security risks, and operational costs increase

Engineering Contradiction:
Improveability to accommodate diverse application componentsVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the virtualization layer from the deployment architecture and replaces it with a direct deployment mechanism. The operating system instance is deployed directly to the infrastructure without requiring an intermediate virtualization layer, thereby reducing system complexity while maintaining the ability to support diverse applications through the standardized OS interface

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a universal operating system instance that can serve multiple application components across different cloud platforms. This single standardized OS interface provides multi-functionality, allowing diverse applications to be deployed without requiring separate virtualization instances for each, thus reducing overall system complexity

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

2Adaptability or versatility

If additional virtualization layers are introduced to support hybrid application architectures, then the system can accommodate diverse application components, but security risks and operational costs increase

Engineering Contradiction:
Improveability to accommodate diverse application componentsVSAvoidsecurity risk
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent removes the virtualization layer that introduces security vulnerabilities and replaces it with a direct deployment architecture. By eliminating this intermediate layer, the system reduces the attack surface and potential security risks while maintaining application diversity through the standardized operating system interface

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a trusted deployment server as an intermediary that securely manages the deployment process. This server acts as a controlled mediator between the application components and the operating system instance, providing secure authentication and authorization without requiring persistent virtualization layers, thereby reducing ongoing security risks

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If individual application components are integrated through custom processes, then specific application requirements are met, but integration costs increase

Engineering Contradiction:
Improveability to meet specific application requirementsVSAvoidintegration cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal operating system instance that provides a standardized interface for deploying diverse application components. This universal platform eliminates the need for custom integration processes for each application, reducing integration costs while maintaining the ability to meet specific application requirements through the standardized OS capabilities

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

Solution Approach 2:

The patent changes the deployment parameter from custom-built integration processes to a standardized deployment mechanism. By using a uniform deployment approach across different applications, the system reduces the effort and cost associated with integrating individual application components while maintaining adaptability through configuration rather than custom development

Inventive Principle:
Principle #35Parameter changes

4Adaptability or versatility

If migration to new deployment models is performed with additional virtualization layers, then application components can be redistributed, but operational risks and costs increase

Engineering Contradiction:
Improveability to redistribute application componentsVSAvoidoperational risk
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent removes the virtualization layer that complicates migration operations and replaces it with a direct deployment approach. This simplifies the migration process by eliminating the need to manage virtualization infrastructure during redistribution, thereby reducing operational risks and costs while maintaining the ability to redistribute application components across different cloud platforms

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP3217623B1Method and system for allocating an operating system on at least one network-based computer infrastructure
Publication Date: 2018.07.04 DEUTSCHE TELEKOM AG
  • EP3217623B1 patent drawingFigure 1

AI summary

The procedure comprises the following steps: Establishing a secure network connection from at least one instance of the at least one operating system to be installed to at least one server of a provider (200); Authenticating the at least one instance of the operating system to be installed on the at least one server of the provider (200); Determining the components necessary for the operation of the at least one instance of the at least one operating system, taking into account the at least one network-based computing infrastructure (100); Installing the components necessary for the operation of the at least one instance of the at least one operating system to be installed on the at least one network-based computing infrastructure (100); and Authenticating the at least one instance of the at least one operating system installed on the at least one network-based computing infrastructure (100) on the at least one server (200).Preferably, the above-mentioned steps are carried out in the above-mentioned order.