Website Version Segmentation for Dynamic Content Assignment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing website management systems lack flexibility in handling multiple versions of a website, restricting the ability to make changes without affecting the live version, which is a limitation for businesses needing to update content based on seasonal or promotional changes.

Innovation Solution

A system and method for generating and managing multiple unpublished versions of a website, allowing administrators to select and assign different versions based on conditions such as date, business objectives, inventory, and user demographics, enabling seamless updates without affecting the live version.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a single live version of the website is maintained, then system simplicity is preserved, but flexibility for making changes without affecting the live version is lost

Engineering Contradiction:
Improveflexibility for making changesVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the website into multiple distinct versions (live version and multiple unpublished versions), allowing independent management of each version. This segmentation enables the clothing company to create, modify, and manage unpublished versions without affecting the live version, thereby achieving flexibility while maintaining system organization through clear version separation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by allowing the creation and modification of unpublished website versions before they are deployed to the live version. The clothing company can prepare multiple unpublished versions in advance, review them, and then selectively assign them as the live version, ensuring changes are tested and approved before going live.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple unpublished versions of the website are maintained, then content management flexibility is improved, but system complexity increases

Engineering Contradiction:
Improvecontent management flexibilityVSAvoidversion management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by creating a unified version management system that handles multiple unpublished versions through a common interface and consistent ruleset. The same mechanisms for creating, modifying, and assigning versions work universally across all unpublished versions, reducing the perceived complexity despite managing multiple versions.

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

Solution Approach 2:

The patent implements dynamics by allowing the system to adaptively switch between different unpublished versions based on assigned rules (dates, business objectives, inventory, user demographics). The system dynamically determines which unpublished version should be assigned as live, automating the version selection process and reducing manual management complexity.

Inventive Principle:
Principle #15Dynamics

3Productivity

If changes are made to the live version directly, then update speed is fast, but the risk of errors affecting the live website increases

Engineering Contradiction:
Improveupdate speedVSAvoidlive website stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary action by requiring all changes to be made in unpublished versions before deployment to the live version. The clothing company can create and review multiple unpublished versions, ensuring changes are prepared and validated in advance, which maintains update speed while reducing the risk of errors affecting the live website.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses unpublished versions as intermediaries between the development process and the live website. Changes are made in the unpublished version (intermediary), reviewed and approved, and then assigned to replace the live version. This intermediary layer protects the live website from direct exposure to untested or erroneous changes.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If unpublished versions are assigned based on multiple conditions, then content relevance is improved, but system complexity increases

Engineering Contradiction:
Improvecontent relevanceVSAvoidruleset complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamics by enabling the system to automatically evaluate multiple conditions (dates, business objectives, inventory levels, user demographics) and dynamically assign the most relevant unpublished version as live. The system adaptively determines the appropriate version based on current contextual factors, improving content relevance while automating the complexity of rules evaluation.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent applies feedback by continuously monitoring condition changes (such as inventory levels, seasonal dates, or user demographic shifts) and automatically triggering version reassignment when conditions are met. This feedback mechanism ensures content relevance is maintained without manual intervention, managing the complexity of multiple conditions through automated response to condition changes.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11176220B2System and method for website hosting
Publication Date: 2021.11.16 ORACLE INT CORP
  • US11176220B2 patent drawing
  • US11176220B2 patent drawing
  • US11176220B2 patent drawing

AI summary

Systems, methods, and other embodiments associated with website hosting are described. In one embodiment, a method includes maintaining a plurality of unpublished website versions that are available to assign as a live version of a website. The example method may also include selecting an unpublished website version from the plurality of unpublished website versions based upon an attribute of a request for the live version of the website satisfying a rule specifying that the unpublished website version is to be used as the live version of the website. The example method may also include reassigning the live version of the website from a current website version to the unpublished website version for the request. The example method may also include transmitting the unpublished website version as the live version of the website to the remote device over the network.