Chat Protocol Segmentation for Mobile Push Notifications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current chat information systems on portable electronic devices face challenges in implementing system-initiated interactions due to limited screen space, unreliable network connectivity, and availability of additional device functions, such as GPS, which hinder the development of effective user interfaces and system architecture for push notifications.
Innovation Solution
A method and architecture for system-initiated chat interactions using a push mechanism, involving establishing a chat protocol connection between a server and mobile device, generating events on the server, sending push protocol commands, processing requests in the background, and displaying media contents using pull protocol mode, while leveraging user profiles, location, and external services to customize notifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If push notifications are implemented on mobile devices, then system-initiated interactions are improved, but device complexity increases
Solution Approach 1:
The system segments the chat protocol into two distinct modes: push mode for server-initiated notifications and pull mode for client-initiated requests. This segmentation allows the system to handle automated push notifications through a dedicated connection channel while maintaining traditional pull-based interactions separately, thereby reducing overall system complexity.
Solution Approach 2:
The patent introduces an intermediary mechanism that packages chat protocol requests within push protocol commands for background processing. This intermediary layer enables seamless integration between push notifications and chat functionality without requiring complete system restructuring, thus managing complexity while enabling automated interactions.
2Productivity
If push notifications are used, then user engagement is improved, but network reliability requirements increase
Solution Approach 1:
The system dynamically adapts its communication mode based on network conditions and user state. Push notifications are sent when the device is available and responsive, while allowing for potential delivery delays or failures without compromising the overall interaction flow. The pull mode serves as a fallback mechanism when push notifications cannot be delivered.
Solution Approach 2:
The architecture employs periodic polling in pull mode as a complementary mechanism to push notifications. When push notifications are not delivered or when users actively seek information, the system periodically checks for updates, ensuring reliable information delivery despite network variability.
3Productivity
If background processing is implemented, then interaction efficiency is improved, but device resources are consumed
Solution Approach 1:
The system enables self-service processing where the mobile device handles background chat protocol requests locally without requiring continuous server communication. The device independently processes packaged requests in the background, reducing network traffic and server load while maintaining interaction efficiency.
Solution Approach 2:
The architecture uses lightweight, temporary data structures and message formats for background processing. Chat protocol requests are packaged as compact push protocol commands that are processed quickly and discarded, minimizing memory usage and energy consumption while maintaining processing efficiency.
Data Source
AI summary
A method for push interaction with a mobile device using a chat interface includes establishing a chat protocol connection between a server and the mobile device, wherein the chat protocol format is used as a part of the push protocol; generating an event on the server; sending a push protocol command relating to the event from the server to the mobile device using the chat protocol connection; in the background, processing the chat protocol request that was packaged within the push protocol command; receiving the response from the mobile device through the chat protocol connection using the pull protocol mode; sending media contents from the server to the client using pull protocol mode; and displaying the media contents on the mobile device.