Seamless Call Joining via Participant Identifier Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users of video conferencing services often face delays and frustration when trying to join calls without access to the necessary device or information, such as email or calendar entries, leading to a degraded user experience.

Innovation Solution

A method and system that allows seamless connection to calls by verifying a participant identifier and establishing a connection between a client device and a call, using a single service identifier like a phone number or web link, without requiring additional information like PIN codes or updated links.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If users access email or calendar to obtain call joining information, then they can get the necessary details, but it causes delays and requires access to specific devices

Engineering Contradiction:
Improvecall joining informationVSAvoidtime to join call
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent extracts the essential call joining information (participant identifier) from the complex email/calendar system and presents it in a simplified format that can be accessed directly through the messaging application, eliminating the need to access email or calendar applications

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The messaging application serves as an intermediary that consolidates call joining information from multiple sources (email, calendar, other participants) and presents it through a single interface, reducing the need to access multiple applications and devices

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If users contact other participants to ask for call information, then they can obtain joining details, but it degrades the user experience and creates additional communication overhead

Engineering Contradiction:
Improvecall joining informationVSAvoiduser experience
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system enables self-service by automatically providing call joining information through the messaging application without requiring users to contact other participants manually. The participant identifier is automatically generated and shared through the messaging system

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The call joining information is prepared and made available in advance through the messaging application, so users do not need to contact other participants during the call setup process. The participant identifier is ready beforehand and can be immediately used

Inventive Principle:
Principle #10Preliminary action

3Productivity

If users manually enter PIN codes or call identifiers, then they can join the call, but it increases the complexity and time required to connect

Engineering Contradiction:
Improvespeed of connectionVSAvoidconnection process
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts only the essential participant identifier needed for call joining, eliminating the need for users to manually enter multiple pieces of information such as PIN codes, call identifiers, or other complex authentication details

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system changes the authentication parameter from multiple complex inputs (PIN codes, identifiers) to a single simplified participant identifier that can be automatically processed, reducing both the complexity and time of the connection process

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12107903B2Seamless connect
Publication Date: 2024.10.01 MASS LUMINOSITY INC
  • US12107903B2 patent drawing
  • US12107903B2 patent drawing
  • US12107903B2 patent drawing

AI summary

A method implements seamless connection. The method includes receiving a message for a join call request for a client device. The message includes a participant identifier. The method further includes verifying the participant identifier, identifying a call corresponding to the participant identifier, and establishing a connection between the client device and the call.