Multi-Session User Interaction Context Tokenization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems fail to efficiently manage multi-session user interactions across different communication channels, requiring users to repeatedly provide context and authentication information, leading to increased network congestion and reduced bandwidth utilization.

Innovation Solution

A system that authenticates users based on passcode, biometric data, and IP address, generates a token ID for context information, and communicates this information across sessions, allowing seamless multi-session interactions without repeated authentication or context repetition.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users initiate multiple interaction sessions with different entities about the same topic, then the user can receive help from multiple entities, but the user has to repeat the purpose and context information in each session

Engineering Contradiction:

Improvemulti-entity interaction capabilityVSAvoidtime spent repeating context

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by determining context information from previous interaction sessions and storing it before the user initiates a new session. When the user starts a new interaction, the system has already prepared the context data, allowing it to be automatically retrieved and provided to the new entity without requiring the user to repeat information.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary mechanism (the processing engine that determines and stores context information) between the user's interaction sessions and the entities. This intermediary automatically manages the context data, retrieving it from previous sessions and providing it to new entities, thereby eliminating the need for users to manually repeat context information.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If users provide authentication information and context information in each interaction session, then the system can ensure security and context accuracy, but network bandwidth is consumed and network congestion increases

Engineering Contradiction:

Improveauthentication securityVSAvoidnetwork bandwidth consumption

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary authentication by verifying the user's identity before the interaction session begins and storing the authentication information. This preliminary action ensures that authentication is completed once and can be referenced in subsequent sessions, reducing the need for repeated authentication data transmission.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system extracts and separates the authentication information and context information from the main interaction data stream. By determining and storing these informational components separately before interactions, the system reduces the amount of data that needs to be transmitted during actual interaction sessions, thereby reducing network bandwidth consumption.

Inventive Principle:

Principle #2Taking out (Extraction)

3Ease of operation

If the system stores and communicates context information from previous sessions to new entities, then the user experience is improved by eliminating repetition, but the system complexity increases

Engineering Contradiction:

Improveuser interaction convenienceVSAvoidsystem structure complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The system implements self-service by automatically determining context information from previous interaction sessions and communicating it to new entities without requiring user intervention. The processing engine autonomously manages the context data retrieval and transmission, reducing the need for complex user-side applications or manual configuration.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system achieves multi-functionality by designing a universal processing engine that can handle multiple interaction sessions, determine context information from various sources, and communicate with different types of entities. This universal approach simplifies the overall system architecture compared to creating separate specialized systems for each interaction type.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11792243B2System and method for conducting multi-session user interactions

Publication Date: 2023.10.17 BANK OF AMERICA CORP

AI summary

A system for conducting multi-session user interactions accesses a first interaction session between the user and a first entity, where the first interaction session is via a first communication channel. The system determines first context information associated with the first interaction session, where the first context information associated with the first interaction session comprises a summary associated with the first interaction session. The system generates a token identifier (ID) uniquely identifying the user and the first context information. The system associates the token ID to the user interaction information. The system accesses a second interaction session between the user and a second entity, wherein the second interaction session is via a second communication channel. The system authenticates the user based at least in part upon the token ID. The system communicates the first context information associated with the first interaction session to the second entity.