Dynamic Content Delivery Architecture Metadata Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile device content delivery technologies, such as WAP, SMS, and cell broadcast, lack customization and intelligence, failing to adapt to user-specific capabilities and device limitations, necessitating a more dynamic and adaptable solution for delivering diverse content.
Innovation Solution
A dynamic content delivery architecture that employs metadata to provide intelligence to processing elements, allowing for the addition of generic applications and content providers without modifying the architecture, using a layered 'enveloped' model for metadata, static and dynamic metadata separation, and a plug-in registration model to optimize content delivery based on user preferences, network conditions, and device capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If WAP is used for content delivery, then content can be pushed to mobile devices, but websites must be rewritten to satisfy the protocol and provide a uniform site that does not change to accommodate user capabilities
Solution Approach 1:
The patent segments metadata into multiple layers (first layer metadata for push proxy, second layer metadata for push client, third layer metadata for application) that can be independently processed. This allows each component to handle only the metadata relevant to its function, eliminating the need to rewrite entire websites while maintaining adaptability to user capabilities through targeted metadata processing.
Solution Approach 2:
The patent introduces a push proxy as an intermediary component that receives content from content providers, processes first layer metadata, and forwards content with embedded second and third layer metadata to push clients. This intermediary handles the complexity of metadata processing and capability matching, allowing websites to remain unchanged while still adapting to user capabilities.
2Productivity
If broadcast or cell broadcast is used for push delivery, then content can be delivered to multiple users, but delivery cannot be customized to the needs of a particular user or the capabilities of a particular device
Solution Approach 1:
The patent applies local quality by embedding different layers of metadata within the same content envelope, where each layer contains information specific to a particular processing stage or recipient. First layer metadata is processed by the push proxy, while second and third layer metadata are processed by the push client and application respectively. This allows efficient broadcast-style delivery while enabling customization at each level through locally-relevant metadata.
3Extent of automation
If metadata is passed with every content envelope in a push framework, then processing elements can make intelligent decisions, but network bandwidth is consumed and processing overhead increases
Solution Approach 1:
The patent segments metadata into three distinct layers, each processed by different components in the push framework. The push proxy processes only first layer metadata, while push clients process second layer metadata, and applications process third layer metadata. This segmentation distributes the processing intelligence across multiple components, reducing the metadata processing burden on any single element and optimizing network bandwidth utilization.
Solution Approach 2:
The patent implements preliminary action by having the push proxy process and validate first layer metadata before content is transmitted over the network. This preliminary processing ensures that only necessary content and metadata are transmitted, reducing network bandwidth consumption while maintaining intelligent processing capabilities at subsequent stages.
4Adaptability or versatility
If a dynamic content delivery architecture is implemented with layered metadata and plug-in registration, then generic applications and content providers can be added without changing the architecture, but system complexity increases
Solution Approach 1:
The patent implements universality through a standardized three-layer metadata framework and plug-in registration model that can accommodate any generic application or content provider without requiring architectural changes. Each component (push proxy, push client, application) follows the same metadata processing rules, allowing new participants to be added by simply registering their capabilities through the existing framework rather than modifying the core architecture.
Data Source
AI summary
A method and system of optimizing content delivery at a processing element in a dynamic content delivery architecture, the method having the steps of: receiving a content and metadata envelope at the processing element; checking the content and metadata envelope to determine whether the content and metadata envelope includes metadata for the processing element; if the content envelope contains metadata for the processing element, extracting and caching the metadata; if the content envelope does not contain metadata for the processing element, retrieving metadata for a content provider associated with the content from a cache on the processing element; and applying the extracted or retrieved metadata to the content and metadata envelope.