Push-to-X Cloud Storage Architecture for Wireless Messaging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing advanced voice and messaging services in wireless communications networks, such as Push-to-Talk (PoC/PTT), do not effectively support Push-to-X services using cloud-based storage, limiting compliance with both existing and emerging wireless standards and user experience.
Innovation Solution
An architecture framework is introduced to provide Push-to-X services using cloud-based storage services, enabling messaging systems to communicate via Session Initiation Protocol (SIP) and storage servers via Hypertext Transport Protocol (HTTP), with attachments stored on servers and retrieved using Uniform Resource Locators (URLs, facilitating efficient message delivery and multimedia content sharing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If attachments are stored on cloud-based storage servers and retrieved using URLs, then multimedia content sharing capability is improved, but network bandwidth utilization increases
Solution Approach 1:
The patent extracts the attachment storage function from the messaging server and places it on cloud-based storage servers. Only control messages containing URLs are transmitted through the messaging server, while actual attachments are stored and retrieved directly from cloud storage, separating the storage burden from the messaging infrastructure.
Solution Approach 2:
The patent introduces cloud-based storage servers as intermediaries between the messaging system and the attachments. These servers act as a mediator that handles the actual storage and retrieval of multimedia content, allowing the messaging server to focus on control signaling only.
2Productivity
If control messages include URLs for retrieving attachments from storage servers, then message delivery efficiency is improved, but device complexity increases
Solution Approach 1:
The patent segments the messaging system into distinct functional components: messaging servers for control signaling, cloud storage servers for attachment storage, and mobile units for message processing. This segmentation allows each component to specialize in its function, improving overall efficiency despite increased architectural complexity.
Solution Approach 2:
The patent employs universal protocols (SIP for messaging, HTTP for storage access) that allow different system components to interact through standardized interfaces. This multi-functionality enables the same protocols to handle both messaging control and attachment retrieval, reducing the need for proprietary custom solutions.
3Adaptability or versatility
If Push-to-X services support both text messages and multimedia attachments, then service versatility is improved, but server capacity requirements increase
Solution Approach 1:
The patent extracts the bulk data storage requirement from the messaging server by placing attachments on cloud-based storage servers. This extraction allows the messaging server to handle only lightweight control messages, significantly reducing its capacity requirements while maintaining support for both text and multimedia content.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An architecture framework to realize Push-to-X services using cloud-based storage services. Push-to-X messages are transmitted between mobile units by messaging servers. The Push-to-X message may include a short text message contained wholly within the Push-to-X message, or the Push-to-X message may include one or more attachments that comprise multimedia contents, files, or location information, which are stored on storage servers, wherein the Push-to-X message identifies a location for retrieving the attachments from the storage servers. The Push-to-X messages may be sent to a single mobile unit identified by a Mobile Directory Number (MDN) or a group of mobile units identified by a list of MDNs or a Uniform Resource Identifier (URI).