Mobile Content Distribution via Server-Mediated WAP Push
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for sending content from a mobile device to multiple recipients are cumbersome, as they require multiple SMS messages and lack control over recipient access, and standard mobile devices are not equipped to easily manage content distribution or notify recipients of new content.
Innovation Solution
A method where a mobile sending device sends content to a storage server, which stores it and generates a content page with a unique address, allowing the originator to select recipients through a recipient-selection page, and sends them a WAP push link to access the content page, enabling easy selection and notification of recipients using standard mobile browsing capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If content is sent as attachments of multiple SMS messages from a mobile device to multiple recipients, then the content can be delivered to multiple recipients, but the process becomes tiresome and complex for the originator who must send several messages manually
Solution Approach 1:
A server acts as an intermediary between the originator and multiple recipients. The originator sends content to the server once, and the server automatically distributes it to selected recipients via SMS messages with WAP push links, eliminating the need for the originator to manually send multiple messages
Solution Approach 2:
The content transmission process is segmented into distinct functional components: the originator's device handles content creation and initial upload, the server handles storage, recipient management, and message distribution, while recipient devices handle content access. This segmentation simplifies the originator's task to a single upload operation
2Adaptability or versatility
If content is made available to the public through a personal page accessible from the internet, then content can be shared widely, but standard mobile devices lack the functionalities to easily generate such pages and control recipient access
Solution Approach 1:
The server acts as an intermediary that provides personal page generation and recipient access control functionalities that would otherwise require complex mobile device capabilities. The server handles URL generation, recipient selection interfaces, and access authorization, allowing standard mobile devices to participate in controlled content distribution without additional functionality
Solution Approach 2:
The system enables self-service content distribution where the originator can independently select recipients, generate access links, and manage distribution through a simplified web interface accessed via mobile browser, without requiring complex device-based content management systems
3Adaptability or versatility
If content is distributed through personal pages, then content can be accessed by recipients, but the originator cannot easily control who is authorised to view the content or instantly notify specific recipients
Solution Approach 1:
The system implements feedback mechanisms where the server sends confirmation messages to the originator about content upload status and delivery status to recipients. The originator can view recipient lists and access status, enabling informed control over content distribution and instant notification of specific recipients through the WAP push link mechanism
Data Source
AI summary
A method is disclosed for sending content from a mobile sending device belonging to an originator to at least one receiving device associated with a respective recipient. The mobile sending device sends said content to a storage server; the storage server stores the content, associating a content identifier with it; the storage server builds a content page including the content, the content page being associated with a first address, the first address depending at least on the content identifier; the storage server sends the mobile sending device a first message including a second address associated with a recipient-selection page; the mobile sending device accesses said recipient-selection page by the second address; and the originator builds, by the recipient-selection page, a list including an identifier of the receiving device.