Dynamic Content Delivery Metadata Envelope Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile content delivery technologies, such as WAP, SMS, and cell broadcast, lack customization and intelligence, failing to adapt to user capabilities and device types, limiting the dynamic addition of applications and content without modifying the architecture.
Innovation Solution
A dynamic content delivery architecture that allows generic applications and content providers to be added without modifying the system, utilizing metadata to provide intelligence and flexibility, with a layered 'enveloped' model for metadata processing, and a plug-in registration model for service and application manifests to establish channel metadata.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If WAP protocol is used for content delivery, then content can be pushed to mobile devices, but the architecture requires websites to be rewritten and cannot adapt to user capabilities
Solution Approach 1:
The metadata is segmented into multiple layers corresponding to different processing elements in the architecture. Each layer contains processing instructions specific to that element, allowing the system to adapt to different user capabilities without requiring architectural changes. The metadata envelope is divided into application-level, push-client-level, and push-proxy-level metadata, enabling targeted adaptation at each level.
Solution Approach 2:
The patent introduces an intermediary metadata envelope that carries processing instructions between different architecture layers. This metadata acts as a mediator that enables adaptation without modifying the core architecture, allowing the system to accommodate various user capabilities through information exchange rather than structural changes.
2Adaptability or versatility
If broadcast or cell broadcast is used for push content, then delivery can be achieved, but customization to user needs and device capabilities is not possible
Solution Approach 1:
The patent applies local quality by providing different metadata instructions to different processing elements based on their specific requirements and capabilities. Each processing element receives customized metadata that contains processing rules tailored to its function and the user's device capabilities, enabling intelligent customization without losing delivery information.
Solution Approach 2:
The system performs preliminary action by embedding processing instructions in the metadata envelope before content delivery. The metadata contains pre-defined processing rules that guide each processing element on how to handle the content according to user needs and device capabilities, enabling intelligent delivery before the actual content transmission occurs.
3Reliability
If metadata is passed with every content delivery, then processing intelligence is provided, but network overhead and processing time increase
Solution Approach 1:
The patent applies partial action by including only the necessary metadata layers for each processing element in the delivery chain. Not all processing elements require all metadata layers, so the system includes only the relevant portions, reducing overall processing time while maintaining the reliability of processing intelligence where needed.
Solution Approach 2:
The metadata envelope is prepared in advance with all necessary processing instructions embedded before delivery. This preliminary action allows processing elements to efficiently extract and apply their specific metadata without requiring additional processing steps, reducing overall processing time while maintaining reliability.
4Adaptability or versatility
If a dynamic content delivery architecture is implemented to allow generic applications to be added, then flexibility is improved, but system complexity increases
Solution Approach 1:
The patent implements universality by creating a metadata envelope structure that can accommodate any type of application and content provider without requiring architecture modification. The standardized metadata format provides multi-functionality, allowing the same architecture to handle diverse applications through information-based differentiation rather than structural complexity.
Solution Approach 2:
The architecture is segmented into standardized processing elements that interact through the metadata envelope interface. This segmentation allows generic applications to be added by simply following the standardized metadata format, reducing architecture complexity while maintaining flexibility. Each processing element handles its specific layer independently, preventing complexity accumulation.
Data Source
Figure 1
Figure 2
Figure 3
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.