Metadata-Driven Runtime Environment for Dynamic Content Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content management systems are inflexible as they require content to be tied to specific applications and infrastructure, limiting access and compatibility with different applications and infrastructure setups.

Innovation Solution

The method involves using metadata associated with content items to define runtime environments, allowing for dynamic deployment of applications and infrastructure based on metadata definitions, enabling access to content across multiple applications and infrastructure types without being tied to a singular setup.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If content is tied to specific applications and infrastructure, then content access is ensured through dedicated setups, but system flexibility and compatibility with different applications are reduced

Engineering Contradiction:
Improvecontent access reliabilityVSAvoidapplication compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a metadata layer as an intermediary between content and infrastructure. This metadata contains runtime definitions that enable content to be accessed through multiple applications and infrastructure types without direct coupling. The metadata acts as a mediator that translates between different infrastructure implementations and the content requirements, resolving the contradiction between reliable dedicated access and broad compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements universal content access by defining runtime metadata that can be interpreted by multiple different applications and infrastructure configurations. Instead of creating dedicated access paths for each application, the system uses a universal metadata schema that enables any compliant application to access content through standardized mechanisms while maintaining the ability to specify application-specific requirements when needed.

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

2Reliability

If content is tied to specific applications and infrastructure, then dedicated access paths are established, but system complexity increases due to multiple setup requirements

Engineering Contradiction:
Improvecontent access reliabilityVSAvoidinfrastructure setup complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the access configuration information from the infrastructure setup and places it into metadata associated with the content. By taking out the runtime definitions and access parameters from the infrastructure layer and embedding them with the content, the system eliminates the need for complex infrastructure configurations for each content item. The metadata contains all necessary access information, simplifying the infrastructure to a generic platform that can handle any content through standardized processes.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If dynamic deployment based on metadata is implemented, then system flexibility and on-demand servicing are enhanced, but infrastructure management complexity increases

Engineering Contradiction:
Improvedeployment flexibilityVSAvoidinfrastructure management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements self-service deployment where the runtime metadata associated with content automatically provides the necessary instructions for deployment and access. The metadata contains runtime definitions that enable the system to self-configure access paths, select appropriate infrastructure components, and manage deployment without requiring manual infrastructure management intervention. This automation reduces the perceived complexity for users while providing flexible dynamic deployment capabilities.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11977927B2Deploying dynamic applications and infrastructure according to metadata assigned by content
Publication Date: 2024.05.07 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11977927B2 patent drawing
  • US11977927B2 patent drawing
  • US11977927B2 patent drawing

AI summary

Methods, computer program products, and/or systems are provided that perform the following operations: obtaining metadata associated with a content item, wherein the metadata includes at least one runtime metadata definition; identifying an environment for providing access to the content item based on a runtime metadata definition; implementing the environment based, at least in part, on the runtime metadata definition; and providing access to the content item in the environment.