Conference Server Blocklist Filtering for Chat Privacy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-user instant messaging systems, managing blocklists in chat rooms is challenging, particularly when users are invited by a third party, as existing solutions either disclose blocklist information or create confusion about message visibility, leading to issues like blocked users appearing ignored or system faults.
Innovation Solution
A method using SIP/SIMPLE technology where a conference server checks blocklists of invited users and sends modified SIP NOTIFY messages to participants, allowing them to choose how to handle blocked users without revealing personal blocklists, enabling filtered message visibility or room exit options.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the system discards invitations to blocked users without notification, then user privacy is protected, but participants perceive system faults or ignored invitations
Solution Approach 1:
The patent introduces an intermediary mechanism (the conference server) that mediates between the inviter and blocked users. The server secretly checks blocklists before delivering invitations, acting as a hidden intermediary that prevents blocked users from receiving invitations without revealing blocklist information to any participant. This resolves the contradiction by maintaining privacy while ensuring reliable invitation handling.
Solution Approach 2:
The patent applies preliminary action by performing blocklist checks before invitation delivery. The conference server proactively verifies whether invited users are blocked by any participants prior to sending invitations, and silently discards invitations to blocked users. This preliminary verification prevents the delivery problem while maintaining privacy, as the check occurs before the invitation reaches the user.
2Adaptability or versatility
If the system allows all invited users to join regardless of blocklists, then chat room creation flexibility is improved, but blocked users can see each other and messages are filtered causing confusion
Solution Approach 1:
The patent applies preliminary action by checking blocklists before users join the chat room. The conference server verifies blocklist status during the invitation phase, preventing blocked users from joining in the first place. This eliminates the need for post-join message filtering, maintaining both invitation flexibility and message visibility clarity without confusion.
Solution Approach 2:
The patent extracts the blocklist checking function from the user interface and places it in the conference server. This separation allows the system to maintain invitation flexibility at the user level while the server independently handles blocklist enforcement, preventing blocked users from joining and avoiding message filtering confusion.
3Loss of information
If the system performs blocklist checks during user joining, then blocked user visibility is controlled, but the inviter cannot invite users without knowing blocklist preferences
Solution Approach 1:
The patent uses the conference server as an intermediary that handles blocklist checking transparently. The inviter simply sends invitations without needing to know or query blocklist preferences, as the server automatically performs checks in the background. This maintains both blocklist privacy and invitation simplicity, as the intermediary handles the complex verification without involving the user.
Solution Approach 2:
The system applies self-service by automatically performing blocklist checks without requiring user intervention. The conference server autonomously verifies blocklist status and handles invitation delivery decisions, eliminating the need for inviters to manually check or know blocklist preferences while maintaining operational simplicity.
Data Source
Figure 1
Figure 2~8
Figure 3
AI summary
Method and system for managing a chat service in a communications system is disclosed. The chat service enables a first user terminal (206) to invite a second user terminal (202) to join a chat session. A session manager checks if a third user terminal (204) invited to join the chat session by the first user terminal (206) after the second user terminal (202) is listed in a blocklist of users that are blocked from communicating with the second user terminal (202). In the event the third user terminal (204) is in the blocklist, the session manager sends a notification message to the second user terminal (202) to notify a user of the second user terminal (202) that a blocked user is joining the chat session.