OSGi Bundle Framework for Modular Converged Infrastructure Logic

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Enterprise software development and management lack standardized practices, leading to duplicated effort and inefficiencies, particularly in handling new devices and dynamic changes within Converged Infrastructure (CI) applications, where monolithic applications require rebuilds for changes and tight coupling hinders independent feature development.

Innovation Solution

A framework that enables rapid development of CI applications from user interface to southbound device drivers, allowing modular deployment and dynamic updates without rebuilds, using a declarative and pluggable business logic engine with OSGi-based containers for dynamic dependence management and scalable service look-up, combined with a Web Services framework for REST API support.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If monolithic applications are used for Converged Infrastructure management, then system stability is maintained, but any changes require complete rebuilds and tight coupling hinders independent feature development

Engineering Contradiction:

ImproveAbility to modify application logic and add featuresVSAvoidApplication structure complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The application is divided into separate OSGi bundles, each representing an independent functional module. These bundles can be deployed, modified, and updated independently without affecting the entire application, resolving the contradiction between adaptability and complexity by enabling modular development while maintaining system stability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system implements dynamic bundle activation and deactivation, allowing application logic to be modified at runtime without complete rebuilds. The OSGi framework enables hot-swapping of bundles, providing adaptability while maintaining a stable core system architecture.

Inventive Principle:

Principle #15Dynamics

2Productivity

If standardized practices are implemented in enterprise software development, then development efficiency improves, but flexibility to handle dynamic changes in Converged Infrastructure may be reduced

Engineering Contradiction:

ImproveSoftware development efficiencyVSAvoidAbility to handle new devices and dynamic changes

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The OSGi framework provides universal bundle packaging and deployment mechanisms that work across different Converged Infrastructure scenarios. The standardized bundle format and lifecycle management enable efficient development practices while the pluggable architecture maintains adaptability to handle diverse devices and dynamic changes through standardized interfaces.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of operation

If modular deployment with OSGi bundles is implemented, then independent feature development and in-service updates are enabled, but system complexity for bundle management increases

Engineering Contradiction:

ImproveIndependent deployment and updatesVSAvoidBundle management complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The OSGi framework implements automatic bundle registration, dependency resolution, and lifecycle management. Bundles automatically register their services and dependencies with the framework, which handles activation, deactivation, and version management, reducing the operational complexity despite the modular architecture.

Inventive Principle:

Principle #25Self-service

4Reliability

If dynamic bundle activation and deactivation is implemented, then in-service deployment and upgrades are enabled, but transactional semantics and error handling become more complex

Engineering Contradiction:

ImproveTransactional semantics for error handlingVSAvoidTime for deployment and updates

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system implements pre-validation of bundles before activation, checking dependencies, compatibility, and transactional requirements in advance. This preliminary action ensures that when bundles are activated or deactivated, transactional semantics are already established, reducing runtime complexity and enabling faster in-service updates without sacrificing reliability.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9830135B2Declarative and pluggable business logic for systems management

Publication Date: 2017.11.28 DELL PROD LP

AI summary

A system for deploying an application comprising a resource bundle configured to provide resource data for the application. A workflow bundle configured to provide workflow data for the application. A workload model bundle configured to provide workload model data for the application. A resource model bundle configured to provide resource model data for the application and a bundle listener configured to listen for the resource data, the workflow data, the workload model data and the resource model data for the application and to instantiate a model service.