Context Server for Seamless Multi-Channel Interaction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge lies in providing an integrated and seamless user experience across multiple interaction channels, as existing systems often lack access to user history from other channels, leading to repetitive tasks and redundant information exchange, which can be frustrating and time-consuming for users and service providers.

Innovation Solution

The system processes context data from various interaction sessions to select a relevant subset based on relevance, similarities, and differences, facilitating seamless transitions and authentications across different interaction channels by using a context server that aggregates, analyzes, and selects context data for interaction requests and responses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple interaction channels are provided to increase coverage and convenience, then user accessibility and service coverage are improved, but system complexity and difficulty in providing integrated user experience worsen

Engineering Contradiction:
Improveinteraction channel coverageVSAvoidsystem integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A context server is introduced as an intermediary component that sits between multiple interaction channels and the service provider. This server aggregates context data from various channels (web, mobile, social media, etc.) and provides a unified interface to the service provider, eliminating the need for direct integration between each channel and the service provider while maintaining seamless user experience across all channels

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple interaction channels are provided to increase coverage and convenience, then user accessibility is improved, but difficulty in providing seamless user experience worsens

Engineering Contradiction:
Improveinteraction channel coverageVSAvoiduser experience integration
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The context server performs multiple functions: it collects context data from diverse interaction channels, processes and stores this data, retrieves relevant information when needed, and presents it to the service provider. This multi-functional universal component enables seamless user experience across all interaction channels without requiring channel-specific integration logic

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

3Ease of operation

If user history from multiple channels is accessed to provide integrated experience, then user experience quality is improved, but information processing complexity and time worsen

Engineering Contradiction:
Improveuser experience qualityVSAvoidinformation processing time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system continuously collects and stores context data from multiple interaction channels in advance. When a user initiates an interaction, the relevant historical context is already prepared and can be retrieved instantly, eliminating the need for real-time processing of historical data and significantly reducing information processing time while maintaining comprehensive user experience

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10977617B2System and method for generating an interaction request
Publication Date: 2021.04.13 THE TORONTO DOMINION BANK
  • US10977617B2 patent drawing
  • US10977617B2 patent drawing
  • US10977617B2 patent drawing

AI summary

A method and system are provided for processing context data for interaction sessions for providing a subset of the context data for a first interaction session. The method includes detecting the first interaction session between a request initiator and a request service provider, and obtaining context data of a plurality of other interaction sessions. The context data is related to activity of the request initiator. The method also includes selecting the subset of the context data based on at least one of relevance, similarities and differences to at least one of the first interaction session and type of interaction channel. The subset of the context data is then provided for the first interaction session.