Session Manager Assigns Codes to Group SMS Conversations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current short messaging infrastructure lacks the ability to manage and display SMS conversations cohesively, treating each message as separate and unrelated, which degrades the user experience by not grouping messages sharing a common conversation.
Innovation Solution
A session manager system that assigns a unique code to messaging service messages based on a session ID, allowing mobile stations to group messages by conversation, and forwards these messages with the code to the SMS gateway for visual grouping in the message inbox.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the underlying short messaging infrastructure treats each message as a separate message, then the messaging system can process messages independently and simply, but the user experience degrades because messages cannot be grouped by conversation
Solution Approach 1:
The patent introduces a session manager as an intermediary component between the messaging application server and the SMS gateway. This session manager assigns session identifiers to messages, enabling the infrastructure to track and group messages by conversation without requiring complex changes to the core SMS gateway. The session manager acts as a mediator that adds conversational context to otherwise independent messages.
Solution Approach 2:
The patent segments the messaging infrastructure into distinct functional components: the messaging application server, the session manager, and the SMS gateway. This segmentation allows each component to perform its specific function independently while working together to achieve the overall goal of conversation-based message grouping. The session manager specifically handles the task of assigning session identifiers.
2Loss of information
If the system assigns session identifiers to group messages by conversation, then messages can be displayed with a common conversational basis, but the messaging infrastructure becomes more complex
Solution Approach 1:
The session manager performs preliminary action by assigning session identifiers to messages before they are sent through the SMS gateway. This pre-assignment of identifiers ensures that conversational context is preserved from the outset, allowing the mobile device to group messages by conversation without requiring complex post-processing or additional infrastructure changes.
Solution Approach 2:
The session manager serves as an intermediary that bridges the gap between simple message transmission and complex conversation tracking. By introducing this intermediate layer, the system preserves conversational context without requiring the entire messaging infrastructure to become complex.
3Ease of manufacture
If messages are processed independently through the SMS gateway, then the system is simpler to implement, but the mobile device cannot display messages in a cohesive conversational format
Solution Approach 1:
The session manager acts as an intermediary component that maintains implementation simplicity while improving message display quality. It sits between the messaging application server and the SMS gateway, adding session identifier assignment functionality without requiring changes to the existing SMS gateway or mobile device software.
Solution Approach 2:
The system is segmented into independent functional components, with the session manager handling the specific task of session identifier assignment. This segmentation allows the rest of the messaging infrastructure to remain simple and unchanged, while the session manager alone provides the enhanced functionality for conversation-based message grouping.
Data Source
AI summary
Systems and methods for session managed messaging are disclosed. Some implementations include receiving, from an enterprise application and at a session manager, a messaging service message including a session ID and a phone number of a mobile device configured to receive the messaging service message, determining, at the session manager and based on the session ID, whether the messaging service message is part of a new conversation or an existing conversation between the enterprise application and the mobile device, and based on a result of the determining step, assigning a particular code to the messaging service message at the session manager, where the particular code allows the mobile device to group messaging service messages associated with a particular conversation together, and forwarding, from the session manager and to a SMS gateway, the messaging service message along with the assigned particular code.