Context-Sensitive Speech Event Logging and Mute Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing client devices lack a convenient method to record event information during conversations and to automatically unmute devices during calls, leading to missed event details and disrupted communication.
Innovation Solution
A network device equipped with a microphone, memory, and processor that detects and stores speech, parses it for event keywords and dates, creates a calendar entry, and sets alarms for future events, while also muting and unmuting the device based on user addressing data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If the device continuously monitors and processes speech to automatically create calendar events, then automation and convenience are improved, but device complexity and processing overhead increase
Solution Approach 1:
The patent extracts and isolates specific keywords (event keywords and date keywords) from the continuous speech stream. Instead of analyzing entire sentences or contexts, the system focuses only on detecting these predefined keywords, thereby simplifying the processing complexity while maintaining automatic event recording functionality.
Solution Approach 2:
The patent introduces a buffer as an intermediary component between speech detection and calendar event creation. The buffer temporarily stores detected speech segments, allowing the system to process information at a manageable pace and decouple the real-time speech input from the event creation process, reducing processing overhead.
2Measurement precision
If the device stores detected speech for analysis, then event detection accuracy is improved, but memory usage increases
Solution Approach 1:
The patent extracts only the necessary portions of speech that contain event keywords and date keywords, rather than storing and analyzing entire conversations. This selective extraction approach maintains detection accuracy by focusing on relevant information while significantly reducing memory consumption.
Solution Approach 2:
The patent implements a buffer with a predetermined time limit, storing speech only for a partial duration necessary to capture event information. This partial action approach ensures sufficient data is retained for accurate event detection without excessively consuming memory resources indefinitely.
3Object-affected harmful factors
If the device mutes the microphone during calls to reduce noise, then communication quality is improved, but user interaction flexibility deteriorates
Solution Approach 1:
The patent implements a feedback mechanism where the system continuously monitors for user addressing data during calls. When such data is detected, the system provides feedback by automatically unmuting the microphone, allowing users to interact seamlessly without manually managing mute states while still maintaining noise reduction during non-interactive periods.
Solution Approach 2:
The patent enables the microphone to serve itself through automatic muting and unmuting based on detected speech patterns. The system autonomously manages the mute state by detecting when users are speaking or addressing each other, eliminating the need for manual user intervention while preserving communication flexibility.
Data Source
AI summary
Aspects of the present disclosure are drawn to a network device comprising: a microphone configured to detect speech from a user; a memory having an event keyword and a date keyword stored therein; and a processor configured to execute instructions stored on the memory to cause the network device to: store, into the memory, detected speech for a predetermined period of time; parse the stored detected speech; determine a future event of the user based on a detected event keyword in the parsed detected speech that corresponds to the event keyword; determine a date of the determined future event based on a detected date keyword in the parsed detected speech that corresponds to the date keyword; create a calendar for the user; and log the future event into the calendar.