Group Chat Session Control via Server-Assigned Common ID

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing group chat systems require manual invitations for users to join support sessions, which can be inefficient and may not automatically transfer control when support users change or leave the session.

Innovation Solution

A computer-implemented method and system where a server manages group chat sessions by assigning a common chat ID and controlling session access, allowing automatic invitations and seamless transfer of control between chat controllers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual invitations are used for users to join support sessions, then users can join chat sessions, but the process is inefficient and requires manual intervention

Engineering Contradiction:
Improveuser joining efficiencyVSAvoidtime for manual invitation process
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system pre-generates invitation tokens and stores them on the server before users need to join. When a user wants to join a support session, the server automatically provides the pre-prepared invitation information, eliminating the need for manual invitation creation and sending at the moment of joining.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables users to self-invite to support sessions by providing them with automatic access mechanisms. Users can independently obtain join information from the server without requiring another user to manually send invitations, making the joining process self-service oriented and significantly more efficient.

Inventive Principle:
Principle #25Self-service

2Reliability

If control is manually transferred between chat controllers, then control can be changed, but the process is not automatic and may fail when support users change or leave

Engineering Contradiction:
Improvecontrol transfer reliabilityVSAvoidautomatic control transfer
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The server continuously monitors the status of support users in the chat session, detecting when users leave or their roles change. Based on this feedback, the server automatically initiates control transfer to the appropriate user, ensuring control reliability without manual intervention. The system adjusts control assignment dynamically based on real-time session status.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The control assignment is made dynamic rather than static. The server automatically reassigns control based on changing session conditions, such as when support users leave or their statuses change. This dynamic approach ensures that control is always held by an appropriate active user without requiring manual transfer processes.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If a centralized server manages chat sessions, then control assignment and user management is centralized, but the system complexity increases

Engineering Contradiction:
Improvesession management flexibilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The server is designed as a universal platform that handles multiple functions: session creation, user management, control assignment, invitation token generation, and automatic control transfer. By consolidating these diverse functions into a single multi-functional server, the system achieves high adaptability while managing complexity through functional integration rather than proliferation of separate components.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9923940B2Operating a group chat session
Publication Date: 2018.03.20 MAPLEBEAR INC
  • US9923940B2 patent drawing
  • US9923940B2 patent drawing
  • US9923940B2 patent drawing

AI summary

A first chat controller receives a request to create a group chat session, and creates the session, including determining a first local chat ID for the session. The first chat controller sends the first local chat ID to the server. The server assigns a common chat ID to the session. A second chat controller determines a second local chat ID for the group chat session associated with the second chat controller. The server receives the second local chat ID, receives a request from the second chat controller to control the session, and assigns control of the session to the second chat controller. The server receives a request from a second user to join the group chat session, sends the request to the second chat controller using the second local chat ID. The second chat controller sends an invitation to the second user to join the session.