Usage Pattern Analysis for CMS Configuration Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content management systems face challenges in adapting to changing usage patterns and performance issues due to initial design assumptions becoming invalid over time, leading to suboptimal performance and limited ability to provide tailored recommendations without real usage data.

Innovation Solution

A vendor-site deployment system that collects and analyzes customer usage metrics, generates content usage patterns, and recommends adaptations based on comparisons with reference patterns and rules, including configuration updates and software patches to optimize customer-site deployments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If content management systems are deployed based on initial design assumptions, then deployment is straightforward and quick, but the system performance becomes suboptimal when usage patterns change over time

Engineering Contradiction:
Improvedeployment speedVSAvoidsystem performance
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements feedback loops where usage metrics are continuously collected from customer deployments, analyzed by analytical engines, and used to generate recommendations that are fed back to optimize system configuration. This closed-loop feedback mechanism allows the system to adapt to changing usage patterns while maintaining deployment efficiency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system transitions from static initial design assumptions to dynamic adaptation by continuously monitoring usage metrics and adjusting configurations based on actual usage patterns. The analytical engine processes ongoing data to generate evolving recommendations that keep the system optimized over time.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If the system collects and analyzes detailed usage metrics from all customers, then tailored recommendations can be provided, but system complexity and data processing requirements increase

Engineering Contradiction:
Improverecommendation customizationVSAvoiddata processing system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces analytical engines as intermediary components that process raw usage metrics and transform them into actionable insights. These engines act as mediators between the complex data collection infrastructure and the recommendation generation process, simplifying the overall system architecture while enabling sophisticated analysis.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the data processing function into distinct analytical engines that handle specific types of usage metrics and analysis tasks. This segmentation allows parallel processing of different data streams and enables modular addition of analysis capabilities without increasing overall system complexity.

Inventive Principle:
Principle #1Segmentation

3Reliability

If the system provides comprehensive recommendations based on usage patterns, then system optimization improves, but the time and resources required for analysis and recommendation generation increase

Engineering Contradiction:
Improvesystem optimizationVSAvoidanalysis time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-processing and initial analysis of usage metrics as they are collected, preparing data structures and identifying patterns in advance. This preliminary analysis reduces the computational burden during recommendation generation, enabling faster delivery of optimization recommendations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The analytical engines dynamically adjust analysis parameters and processing depth based on the specific customer context, usage pattern complexity, and priority levels. This parameter adaptation allows the system to provide comprehensive recommendations when needed while reducing analysis time for routine or low-priority cases.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8924336B2Feature and deployment recommendation systems and methods for content management systems to provide recommendations for enhanced feature usage based on usage patterns
Publication Date: 2014.12.30 ORACLE INT CORP
  • US8924336B2 patent drawing
  • US8924336B2 patent drawing
  • US8924336B2 patent drawing

AI summary

Feature and deployment recommendation systems and methods for content management systems comprises a vendor-site deployment and one or more customer-site deployments. The vendor-site deployment is configured to recommend an adaptation of any of the one or more customer-site deployments. The vendor-site deployment including a customer configuration repository adapted to store content usage metrics received from one or more customer-site deployments, an analytical engine configured to generate content usage patterns based on the stored content usage metrics, and a recommendation engine configured to recommend the adaptation.