Voice Process Context Resumption via Progress Data Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Speech processing systems face challenges in resuming third-party processes that run on remote servers, as local servers lack access to memory states, leading to interrupted sessions and difficulty in resuming voice commands effectively.

Innovation Solution

A natural language processing system that generates and stores progress data associated with third-party processes, including memory states, checkpoints, and reference locations, allowing for seamless resumption by sending this data to remote servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If local servers operate third-party processes independently without remote server memory access, then system autonomy is improved, but session continuity deteriorates

Engineering Contradiction:
Improvesystem autonomyVSAvoidsession continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary mechanism (progress data storage and retrieval system) that bridges the local server and remote server. The local server stores progress data locally and exchanges it with the remote server, allowing the system to maintain autonomy while ensuring session continuity through the intermediary data exchange process.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by storing progress data (memory states, checkpoints, reference locations) at the local server before potential session interruptions. This preliminary storage ensures that when sessions need to be resumed, the necessary context information is already available, maintaining continuity without requiring constant remote server access.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If progress data is stored and exchanged between servers, then session resumption is improved, but system complexity increases

Engineering Contradiction:
Improvesession resumptionVSAvoiddata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The progress data is segmented into distinct components: memory states, checkpoints, and reference locations. Each component serves a specific function in session resumption, allowing the system to manage complexity by organizing data into manageable, purpose-specific segments rather than handling undifferentiated data blocks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates copies of progress data (memory states, checkpoints, reference locations) at the local server that mirror the remote server's process state. These copies enable session resumption without requiring direct access to the remote server's memory, simplifying the data management architecture while maintaining resumption capability.

Inventive Principle:
Principle #26Copying

3Productivity

If third-party processes run on remote servers, then resource utilization is improved, but local context access deteriorates

Engineering Contradiction:
Improveresource utilizationVSAvoidlocal context access
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent extracts critical context information (progress data including memory states, checkpoints, and reference locations) from the remote server environment and transfers it to the local server. This extraction allows the local server to maintain autonomy and access necessary context information without requiring direct access to the remote server's memory resources.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system creates local copies of the remote server's process progress data. These copies enable the local server to understand and resume third-party processes without needing direct access to the remote server's memory, thus maintaining resource utilization benefits while preventing information loss at the local level.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11061644B2Maintaining context for voice processes
Publication Date: 2021.07.13 AMAZON TECH INC
  • US11061644B2 patent drawing
  • US11061644B2 patent drawing
  • US11061644B2 patent drawing

AI summary

A system capable of generating and storing progress data associated with third party services. A voice enabled device may receive voice commands and the system may perform natural language understanding (NLU) to interpret the voice commands, determine a corresponding process and send instructions to a third party server associated with the process. In order to resume the process after the process is interrupted, the system may save and/or cause the third party server to save progress data and/or a checkpoint corresponding to a status of the process at the time that the process is interrupted. The system may use the progress data to resume the process at a later point based on the status. In addition, the system may track processes associated with saved progress data/checkpoints and may interpret incoming voice commands based on the tracked processes.