Parallel Message Data Transfer via Dual Protocol Channels
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional message systems face challenges in providing seamless and efficient access to messages of varying types and formats, as they are limited in presenting diverse message types and formats, and fail to meet user demands for easy access.
Innovation Solution
A message service system comprising a message storage system and a message access system, utilizing a program server, message server, and UI server, with the message data communicator file in SWF format, enabling parallel data transfer using different protocols for UI and message data, allowing simultaneous receipt and processing of webpages and message information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional HTML-based user interfaces are used to access messages, then the system maintains simplicity and wide compatibility, but the capability to present diverse message types and formats is limited and access efficiency is reduced
Solution Approach 1:
The patent introduces a message data communicator as an intermediary component that bridges the conventional HTML interface and the diverse message formats. This communicator translates various message types (fax, voice, email, text) into a unified presentation format, allowing the existing HTML interface to handle multiple message types without structural changes. The intermediary layer absorbs the complexity of format conversion while maintaining interface simplicity.
2Speed
If conventional sequential protocols are used for data transfer, then the system maintains protocol simplicity, but the speed of message access and display is reduced
Solution Approach 1:
The patent segments the data transfer process into two parallel channels: an HTTP protocol channel for transferring webpage data and a custom binary protocol channel for transferring message data. This segmentation allows both types of data to be transferred simultaneously through different protocols optimized for their respective purposes, eliminating the bottleneck of sequential transfer while maintaining overall system clarity through defined protocol boundaries.
Solution Approach 2:
The patent adds a temporal dimension to data transfer by enabling parallel communication channels. Instead of transferring data sequentially in a single time dimension, the system opens multiple concurrent data streams (HTTP for webpages, custom protocol for messages), effectively utilizing multiple time dimensions to accelerate overall message access speed without complicating individual protocol implementations.
3Productivity
If conventional single-protocol data transfer is used, then the system maintains transfer simplicity, but the efficiency of simultaneous webpage and message data reception is reduced
Solution Approach 1:
The patent divides the data transfer system into two independent but coordinated segments: an HTTP-based webpage data transfer segment and a custom protocol-based message data transfer segment. Each segment handles its specific data type through an optimized protocol, allowing simultaneous operation without interference. This segmentation increases productivity by enabling parallel data reception while keeping each segment's complexity manageable and well-defined.
Data Source
AI summary
Described herein are systems and methods for enabling access to messages on a message service system via user interfaces of receiving client devices. The message service system comprises a message storage system and a message access system. The message storage system receives messages from sending client devices and stores message data. The message access system comprises a message server and UI server. A receiving client device is connected with the UI server through a first HTTP connection for receiving UI data for building webpages of the user interface and is connected with the message server through a second non-HTTP connection for receiving message data for populating the webpages. The UI data does not comprise any message data. A client protocol engine on the receiving client device and a server protocol engine on the message server define and provide the non-HTTP protocol for receiving and transmitting message data.