Context-Aware Communications Manager for Voice Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current voice recognition systems lack efficient management of communications between devices based on device information, leading to unnecessary user interactions and potential disruptions, especially in scenarios where device context and permissions are not adequately considered.

Innovation Solution

A computer system that automatically establishes or denies communications sessions between devices based on preset permissions and contextual data, such as device type, software version, and activity context, using a network communications protocol like TCP/IP, to manage communications tasks like Drop Ins and Calls without user action at the recipient device.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If automatic communication establishment is implemented without considering device context, then communication efficiency is improved, but communication reliability deteriorates due to inappropriate communication types

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidcommunication reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system dynamically changes communication parameters (communication type, permission status) based on device context parameters such as device type, software version, and activity context. This allows the system to adapt communication behavior to appropriate conditions while maintaining automation, thereby improving reliability without sacrificing efficiency.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring device context information and adjusting communication establishment decisions accordingly. The communications manager receives context data about recipient devices and uses this feedback to determine whether to permit or deny automatic communication establishment, ensuring reliable communication behavior.

Inventive Principle:
Principle #23Feedback

2Reliability

If user action is required at recipient device for each communication, then communication reliability is improved, but ease of operation deteriorates due to unnecessary user interactions

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system enables self-service communication establishment by automatically managing communication sessions based on preset permissions and device context. The communications manager autonomously determines whether to establish communications without requiring user action at the recipient device, improving ease of operation while maintaining reliability through context-aware decision-making.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by establishing preset permissions and storing device context information in advance. This preliminary configuration allows the system to automatically make communication decisions when needed, eliminating the need for real-time user intervention while ensuring reliable communication behavior based on pre-established criteria.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If automatic communication management is implemented, then ease of operation is improved, but device complexity increases due to additional management logic

Engineering Contradiction:
Improveease of operationVSAvoiddevice complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system introduces a communications manager as an intermediary component that handles complex communication management logic. This mediator receives communication requests, evaluates device context information, and makes decisions about automatic communication establishment, thereby centralizing complexity in a dedicated module while keeping the overall system easy to operate.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The communications manager implements multi-functionality by handling various communication types (Drop Ins, Calls, Announcements) and making decisions based on multiple device context parameters (device type, software version, activity context). This universal approach consolidates diverse management functions into a single system, improving ease of operation without proportionally increasing overall device complexity.

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

4Reliability

If communication permissions are strictly enforced based on device context, then communication reliability is improved, but loss of information increases due to denied legitimate communications

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidloss of information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system implements dynamic permission enforcement by continuously evaluating current device context information before making communication decisions. Rather than using static permission rules, the system adapts its decision-making based on real-time context such as current activity, device state, and software version, thereby reducing false denials while maintaining reliable communication control.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11019553B1Managing communications with devices based on device information
Publication Date: 2021.05.25 AMAZON TECH INC
  • US11019553B1 patent drawing
  • US11019553B1 patent drawing
  • US11019553B1 patent drawing

AI summary

Techniques for establishing communications with user devices are described herein. In an example, a system stores, in a user account, permission data to automatically establish a type of communications session by one or more user devices associated with the user account. The system receives, from a user device associated with the user account, contextual data about the user device. Based at least in part on the contextual data, the system determines that the user device is prohibited from automatically establishing the type of communications session. The system stores an indication that the user device is prohibited from automatically establishing the type of communications session.