Mediator Component for Push Content Delivery Registration
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 efficiently deliver dynamic content tailored to individual user capabilities and device types, and require modifications to websites and systems for wireless compatibility.
Innovation Solution
A dynamic content delivery architecture that allows generic applications and content providers to integrate without modifying the system, utilizing metadata for intelligence and a layered 'enveloped' model to process content, with plug-in registration and a mixed push/pull model for efficient data handling based on priority and network conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If WAP is used for content delivery, then content can be pushed to mobile devices, but websites require rewriting to satisfy wireless application protocol and provide uniform content
Solution Approach 1:
The patent introduces a WAP gateway as an intermediary component that sits between the content provider's website and the mobile device. This gateway automatically transforms and adapts content from standard web formats to WAP-compatible formats, eliminating the need for content providers to manually rewrite their websites. The gateway handles protocol conversion, content formatting, and device capability matching transparently.
Solution Approach 2:
The system enables content providers to publish content using standard web technologies without requiring them to understand or implement WAP-specific protocols. The WAP gateway autonomously processes the content, performs necessary transformations, and delivers it to appropriate mobile devices, allowing content providers to serve themselves without specialized wireless knowledge.
2Productivity
If broadcast or cell broadcast is used for push content, then content can be delivered to multiple users, but delivery cannot be customized to individual user needs or device capabilities
Solution Approach 1:
The patent segments the content delivery process into multiple stages: content publication, user subscription, capability assessment, and targeted delivery. Instead of broadcasting content to all devices simultaneously, the system divides the delivery process into discrete steps that allow for user-specific customization at each stage, while maintaining efficient batch processing capabilities.
Solution Approach 2:
The system dynamically adapts content delivery based on real-time user profiles, device capabilities, and subscription preferences. Content delivery parameters such as format, timing, frequency, and selection are adjusted dynamically for each user rather than using static broadcast schedules, enabling both efficiency and customization.
3Device complexity
If generic push client serves multiple target applications, then system resources are optimized, but registration mechanisms must be efficient to avoid interrupting service for other applications
Solution Approach 1:
The patent implements preliminary registration and capability assessment processes that occur before content delivery begins. Applications register their content preferences, device capabilities, and delivery requirements in advance, allowing the system to pre-configure delivery parameters and avoid disruptions during active content delivery. This preliminary setup enables the generic push client to efficiently manage multiple applications without service interruption.
4Loss of information
If metadata is provided in layered enveloped model, then processing elements can extract only needed metadata, but content must be wrapped with multiple layers of metadata
Solution Approach 1:
The patent implements a nested envelope structure where metadata is organized in hierarchical layers, with each layer containing information specific to a particular processing stage or component. The innermost layers contain application-specific metadata, while outer layers contain system-level metadata. This nested structure allows processing elements to extract only the metadata relevant to their function while maintaining a comprehensive metadata framework.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method and apparatus for connecting a generic element to a content delivery architecture in a push content delivery system having the steps of: providing a mediator between the generic element and the content delivery architecture; extracting at the mediator metadata for the generic element; and registering the generic element with the content delivery architecture.