Context Data Storage for Voice Non-Voice Session Continuity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication devices and networks fail to maintain context data across different session types, requiring users to reenter information when switching from a voice session to a non-voice session or vice versa, leading to inefficiency and inconvenience due to unsophisticated input mechanisms.

Innovation Solution

The system stores context data from one session type and retrieves it when switching to another, allowing the new session to recreate the previous state, eliminating the need for reentry and enhancing user experience by maintaining transaction continuity between voice and non-voice sessions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a device supports both voice and non-voice sessions, then the versatility of communication modes is improved, but the complexity of maintaining context data across sessions increases

Engineering Contradiction:
Improvecommunication mode versatilityVSAvoidsession context management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a context data storage mechanism that acts as an intermediary between voice and non-voice sessions. This mediator stores context information (such as user selections, search criteria, and transaction state) in a persistent format that can be retrieved across session boundaries, eliminating the need for users to reenter information when switching between communication modes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system creates a copy of the context data from one session type and preserves it for use in another session type. By copying and storing the essential transaction information in a persistent storage medium, the system enables seamless continuation of user activities across different communication channels without requiring the original session context to remain active.

Inventive Principle:
Principle #26Copying

2Device complexity

If context data is not stored across sessions, then the device complexity is reduced, but the loss of information increases due to required data reentry

Engineering Contradiction:
Improvesession management complexityVSAvoidcontext data loss
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The system performs preliminary action by storing context data during the current session before the session terminates. By proactively saving user selections, search criteria, and transaction state to persistent storage during the active session, the system ensures that this information is preserved and automatically available when the user returns via a different communication mode, preventing information loss.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If users reenter information in each session, then the device complexity remains low, but the loss of time increases due to repetitive data entry

Engineering Contradiction:
Improvesession management complexityVSAvoiddata reentry time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The system implements self-service by automatically retrieving and restoring context data without requiring user intervention. When a user switches from a non-voice to a voice session (or vice versa), the system autonomously fetches the stored context information and reconstructs the session state, eliminating the need for users to manually reenter information and significantly reducing the time lost to repetitive data entry tasks.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7693541B1Multimodal session support on distinct multi channel protocol
Publication Date: 2010.04.06 ORACLE INT CORP
  • US7693541B1 patent drawing
  • US7693541B1 patent drawing
  • US7693541B1 patent drawing

AI summary

An improved mechanism for sharing information between a non-voice session and a voice session is described. Clients use communication devices to exchange voice information over voice sessions to voice node servers and exchange non-voice information over non-voice sessions to WAP gateways. Information about the activity in a session is stored as context data. When a client switches from communication over one type of session to another, context data for that client is located and retrieved. The retrieved context data is used to recreate the state of the prior session, thus eliminating the need to reenter information that was previously available.