Dynamic Service Definition Package Modification in Cloud Platforms

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud computing environments face challenges in dynamically modifying service definition packages to support maintenance, such as bug fixes and security updates, without requiring extensive administrative effort or service provider interaction.

Innovation Solution

A system and method for dynamic modification of service definition packages in a cloud computing environment, where the cloud platform allows for reconfiguration and direct modification of service contents, enabling enterprise software applications to be packaged and updated efficiently, using components like Oracle Exalogic and Fusion Middleware, with features like service management engines and orchestration engines.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If service definition packages are modified dynamically without re-provisioning, then service maintenance efficiency is improved, but system reliability may worsen due to potential configuration errors

Engineering Contradiction:
Improveservice maintenance efficiencyVSAvoidservice stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary validation of service definition package modifications before applying them. Configuration changes are checked for correctness and compatibility prior to deployment, preventing erroneous configurations from compromising service stability while enabling efficient maintenance updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms that monitor service performance after dynamic modifications. If configuration changes cause instability or errors, the system can detect these issues and trigger automatic rollback or correction procedures, maintaining service reliability while allowing frequent updates.

Inventive Principle:
Principle #23Feedback

2Reliability

If administrative access is required for service updates, then security is improved, but operational complexity worsens due to additional management overhead

Engineering Contradiction:
ImprovesecurityVSAvoidadministrative management overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables self-service capabilities where service definition packages can be automatically updated and deployed without requiring manual administrative intervention for each change. Pre-configured update mechanisms and automated validation processes allow the system to manage its own maintenance while maintaining security through predefined authorization frameworks.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements a universal update framework that handles multiple service types and update scenarios through a single standardized process. This multi-functional approach consolidates various administrative tasks into unified procedures, reducing management overhead while maintaining comprehensive security controls.

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

3Adaptability or versatility

If service definition packages are updated frequently, then adaptability is improved, but system complexity worsens due to version management requirements

Engineering Contradiction:
Improveservice update flexibilityVSAvoidversion management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments service definition packages into modular, independently updatable components. Each service module can be updated separately without requiring coordination of entire service suites, simplifying version management while enabling frequent targeted updates to specific services that need adaptation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements version control through copying mechanisms where updated service definition packages are copied to staging environments for validation before production deployment. This copying approach allows multiple versions to coexist temporarily, facilitating easy rollback if needed and simplifying the management of service evolution over time.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9323517B2System and method for dynamic modification of service definition packages with a cloud computing environment
Publication Date: 2016.04.26 ORACLE INT CORP
  • US9323517B2 patent drawing
  • US9323517B2 patent drawing
  • US9323517B2 patent drawing

AI summary

A system and method for dynamic modification of service definition packages for use with a cloud computing environment. In accordance with an embodiment, a cloud platform enables provisioning of enterprise software applications (e.g., Fusion Middleware applications) within a cloud environment. In an embodiment, enterprise applications can be packaged as service definition packages (SDP). To support maintenance of services (e.g., bug fixes, security updates, and configuration changes), a service's characteristics and requirements can be modified dynamically, by reconfiguring the cloud platform itself and/or by mounting a disk volume that corresponds to the service's SDP, and modifying its contents directly.