Stateless Third Party Resource Management Module

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems face challenges in providing a seamless and timely user experience when interacting with cloud-based resources, particularly due to increased lag time caused by the need for both first party and third party cloud-based resources to manage state information and instances, leading to reduced performance and user frustration.

Innovation Solution

Implementing a third party resource management module that maintains and routes state information and user responses between third party cloud-based resources, allowing each interaction to be processed independently and reducing the need for multiple servers to handle instances, thereby minimizing lag and improving processing efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If both first party and third party cloud-based resources manage state information and instances, then comprehensive service coverage is achieved, but lag time increases and performance decreases

Engineering Contradiction:
Improveservice coverageVSAvoidlag time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the state management functionality by introducing a stateless third-party resource management module that handles third-party interactions independently. This segmentation allows first-party resources to focus on core services while third-party resources are managed separately, reducing the overall system lag time while maintaining comprehensive service coverage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The stateless third-party resource management module acts as an intermediary between users and third-party cloud-based resources. It manages state information and instances for third-party resources without requiring first-party resources to maintain this state, thereby reducing lag time while preserving access to diverse third-party services.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple servers handle instances for third party resources, then service reliability is improved, but system complexity increases

Engineering Contradiction:
Improveservice reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the state management functionality for third-party resources from the first-party server infrastructure and places it in a dedicated stateless third-party resource management module. This extraction reduces system complexity by clearly separating concerns while maintaining reliability through specialized handling of third-party interactions.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The stateless third-party resource management module provides universal state management capabilities for multiple third-party resources through a single unified interface. This multi-functional approach reduces the need for multiple specialized servers while maintaining service reliability across diverse third-party integrations.

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

3Stability of the object's composition

If third party interactions are processed through centralized management, then service consistency is improved, but processing speed decreases

Engineering Contradiction:
Improveservice consistencyVSAvoidprocessing speed
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The stateless third-party resource management module enables third-party resources to be self-sufficient by maintaining their own state information locally. This self-service approach eliminates the need for centralized state management, thereby improving processing speed while maintaining service consistency through standardized interaction protocols.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by establishing stateless connection templates and interaction protocols before actual third-party interactions occur. This preparation ensures service consistency through standardized procedures while enabling fast processing during actual interactions by avoiding repeated setup overhead.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11574621B1Stateless third party interactions
Publication Date: 2023.02.07 AMAZON TECH INC
  • US11574621B1 patent drawing
  • US11574621B1 patent drawing
  • US11574621B1 patent drawing

AI summary

A system for enabling end user devices to access third party cloud-based resources. For example, the system may include a first party cloud-based resource for converting sound into a format accessible to the third party cloud-based resource, storing and/or maintaining state information related to the an open communication session between the end user device and the third party cloud-based resources, and converting text-based audio announcements into audio that may be output by the end user device. In some cases, the first party cloud-based resource may transmit user responses together with stored state information to the third party cloud-based resources in a manner that the third part cloud-based resources may treat each interaction with the end user as a separate communication session.