Communication Server Orchestration Layer for Unified Real-Time Sessions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current WebRTC communication systems require merchants to maintain separate accounts with different service providers for voice, video, and text communication sessions, making it cumbersome and inefficient, and developers need to design separate interfaces and protocols for each type of session, which is inconvenient and resource-intensive.

Innovation Solution

A communication server with an orchestration layer acts as a platform-as-a-service, enabling merchants to register for a unified account to provide various types of real-time communication sessions and allowing developers to design a unified interface for managing these sessions, by selecting and interconnecting specialized applications to support voice, video, text, and file-sharing communications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If merchants maintain separate accounts with different service providers for voice, video, and text communication sessions, then each communication type can be provided through specialized service, but the complexity of account management increases and operational convenience decreases

Engineering Contradiction:

Improvecommunication service coverageVSAvoidaccount management

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent combines multiple separate communication service accounts (voice, video, text) into a single unified account system. The communication server integrates these previously separate services, allowing merchants to manage all communication types through one account rather than maintaining separate accounts with different service providers.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The unified account system provides multi-functional capabilities by supporting multiple communication types (voice, video, text, file sharing) through a single account. The communication server acts as a universal platform that can handle various communication protocols and formats within one integrated system.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If developers design separate interfaces and protocols for each type of real-time communication session, then each communication protocol can be optimized for its specific function, but the development complexity and resource requirements increase

Engineering Contradiction:

Improvecommunication protocol optimizationVSAvoidinterface design

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The communication server acts as an intermediary between the unified interface and multiple specialized communication protocols. It receives requests through a single interface, then routes and translates them into appropriate protocol-specific commands, eliminating the need for developers to design separate interfaces for each communication type.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

A single unified interface is designed that can handle multiple types of real-time communication sessions (voice, video, text, file sharing). This universal interface reduces development complexity while the communication server ensures each communication type receives optimized protocol handling.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of operation

If a unified account system is implemented to manage multiple communication types, then operational convenience improves and account management simplifies, but system complexity increases requiring an orchestration layer

Engineering Contradiction:

Improveaccount managementVSAvoidsystem architecture

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The system is segmented into distinct functional layers: a simplified unified account management interface for users, and a backend orchestration layer that handles the complexity of integrating multiple communication services. This segmentation allows the user-facing side to remain simple while the backend manages the necessary complexity.

Inventive Principle:

Principle #1Segmentation

4Adaptability or versatility

If multiple separate service provider accounts are maintained, then specialized communication services can be accessed, but time and resources are wasted on managing multiple registrations and protocols

Engineering Contradiction:

Improvecommunication service accessVSAvoidaccount registration and maintenance

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

Multiple separate service provider accounts are merged into a single unified account system. The communication server consolidates what would have been separate registration processes, authentication mechanisms, and protocol management into one integrated system, eliminating redundant time and resource expenditure.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS10805376B2Communication server and method for selective use of real-time communication features

Publication Date: 2020.10.13 AVCTECHNOLOGIES USA INC

AI summary

An apparatus and method for receiving, at a communication server, a web-based request for a real-time communication session, selecting, at the communication server, a number of applications based on information included in the web-based request to support the real-time communication session, the number of applications being from among the plurality of applications running on the one or more application servers, communicating with the one or more application servers to enable provision of the number of applications for the real-time communication session, and enabling the real-time communication session between a first device and a second device.