Content Item Management System Non-Default Publisher Side File Location Support

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing content management systems for expandable content items, such as advertisements, face challenges in handling non-default publisher side file locations, leading to rendering issues when location macros are not included, and complicating site maintenance for publishers dealing with multiple vendors.

Innovation Solution

A content management system that determines whether a publisher uses a default or non-default location for publisher side files and modifies the content item data accordingly, allowing publishers to specify non-default locations and simplifying site maintenance by filtering out content items without location macros for non-default locations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the system uses default vendor-specified locations for publisher side files, then content item rendering is simplified, but publishers cannot customize file locations to their site structure requirements

Engineering Contradiction:

Improvepublisher location customizationVSAvoidlocation management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system dynamically determines whether to use default or non-default locations based on publisher configuration. The content item management system checks publisher settings and automatically selects the appropriate location strategy, making the system adaptable to different publisher needs without requiring manual configuration changes.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The content item management system acts as an intermediary between vendors and publishers. It receives content items from vendors, processes location information, and delivers appropriately modified content items to publishers. This intermediary handles the complexity of location management internally while presenting a simplified interface to both vendors and publishers.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If the system supports non-default publisher side file locations, then publishers can organize files according to their site structure, but content items without location macros fail to render properly

Engineering Contradiction:

Improvesite maintenance easeVSAvoidcontent item rendering reliability

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The content item management system performs preliminary processing of content items before delivery to publishers. It checks whether each content item includes the necessary location macro and pre-modifies the content item data with the correct publisher side file location. This preliminary action ensures that rendering issues are prevented before the content item reaches the publisher.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where publisher configuration information (including whether they use default or non-default locations) is stored and used to guide subsequent content item processing. The system learns from publisher preferences and automatically adjusts its behavior for future content item deliveries to the same publisher.

Inventive Principle:

Principle #23Feedback

3Adaptability or versatility

If vendors specify default locations for publisher side files, then content item processing is standardized, but publishers must maintain files in multiple vendor-specific locations

Engineering Contradiction:

Improvesingle location managementVSAvoidcontent item processing efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The content item management system provides universal location management that works with both default vendor-specified locations and custom publisher-specified locations. A single publisher configuration can accommodate multiple vendors, and the system automatically routes content items to the appropriate location based on vendor and publisher settings, eliminating the need for publishers to manually manage multiple vendor-specific directories.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9098598B1Non-default location support for expandable content item publisher side files

Publication Date: 2015.08.04 GOOGLE LLC

AI summary

This specification describes methods, systems, and apparatus, including computer programs encoded on a computer-readable storage device, for non-default location support for publisher side files. In an aspect, location macros are used in content item data. The location macros are specific to vendors that serve the content items. For each content item request for which a publisher specified by the request utilizes a default location for a publisher side file location, the content item data are modified to specify the default location. Conversely, for each request for which the publisher specified by the request utilizes a non-default location for the publisher side file location, the content item data are modified to specify the non-default location.