Omni-channel Content Mapper Framework for CMS Compatibility

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional Content Management Systems (CMS) platforms require content to be stored in CMS-specific data formats, leading to increased data size, network traffic, and processing times, and necessitate frequent updates to ensure compatibility with changing software and content channels, making it difficult to add new content types without extensive modifications.

Innovation Solution

An omni-channel content mapper framework that uses plugins to generate application-agnostic structured data documents, allowing content to be formatted and transmitted independently of specific CMS or client applications, enabling caching and preview functionality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If content is stored in CMS-specific data formats, then content compatibility with the CMS platform is ensured, but data size increases and network traffic increases

Engineering Contradiction:

Improvecontent compatibilityVSAvoiddata size

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent introduces an intermediary layer (content adapter/plugin) between the CMS platform and the content delivery system. This adapter converts CMS-specific content formats into a universal, platform-agnostic format during the content retrieval process, eliminating the need to store and transmit redundant CMS-specific metadata while maintaining full compatibility.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If content is stored in CMS-specific data formats, then content compatibility with the CMS platform is ensured, but processing times increase

Engineering Contradiction:

Improvecontent compatibilityVSAvoidprocessing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary conversion of CMS-specific content formats to universal formats during the content retrieval phase, before the content needs to be processed or delivered. This advance preparation eliminates the need for time-consuming format conversions during content delivery, significantly reducing processing times while ensuring compatibility is maintained through the adapter layer.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If content is formatted for specific client applications, then content compatibility with the application is ensured, but data size increases and network traffic increases

Engineering Contradiction:

Improveapplication compatibilityVSAvoiddata size

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent implements a dynamic parameter change approach where content is stored in a universal format with standardized parameters. When content is delivered to different client applications, the system adjusts only the necessary presentation parameters (such as layout, styling, or specific formatting requirements) while keeping the core content data unchanged, thereby maintaining application compatibility without increasing data size.

Inventive Principle:

Principle #35Parameter changes

4Reliability

If content models are CMS-specific and content channel-specific, then content compatibility is ensured, but the system requires extensive modifications when adding new content types

Engineering Contradiction:

Improvecontent compatibilityVSAvoidsystem modification complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal content model that can serve multiple CMS platforms and content channels simultaneously. The content adapter/plugin architecture provides multi-functional capability, automatically detecting and adapting to different CMS platforms and content channel requirements without requiring separate content models for each platform, thereby eliminating the need for extensive modifications when adding new content types or platforms.

Inventive Principle:

Principle #6Universality (Multi-functionality)

5Reliability

If content is stored with CMS-specific metadata, then content compatibility with the CMS platform is ensured, but network traffic increases

Engineering Contradiction:

Improveplatform compatibilityVSAvoidnetwork traffic

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts and separates the essential content data from CMS-specific metadata during the content retrieval process. The content adapter removes redundant platform-specific metadata and retains only the universal, platform-agnostic content elements that are necessary for content delivery, thereby significantly reducing network traffic while maintaining platform compatibility through the adapter layer.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS20240411830A1Omni-channel content mapper framework

Publication Date: 2024.12.12 CHARLES SCHWAB & CO INC

AI summary

A system, apparatus, method, and non-transitory computer readable medium for providing an omni-channel content mapper framework may include a server caused to receive a content request from at least one user device, the content request including a unique content identifier associated with the requested content and desired content type information corresponding to the requested content, determine a desired content mapper (CM) plugin corresponding to the desired content type information from a plurality of CM plugins, obtain content data corresponding to the unique content identifier from a content database, generate an application-agnostic structured data document using the determined content mapper plugin, the application-agnostic structured data document including the obtained content data, and transmit the application-agnostic structured data document to the at least one user device in response to the content request.