Vehicle Audio Notification Context Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current notification systems lack the ability to intelligently manage audio notifications on mobile devices, particularly in determining when to deliver them based on user context and handling overlapping notifications effectively.

Innovation Solution

A computer-implemented method and system that detects triggering events on a user device, generates audio notifications, and processes user voice commands to determine the appropriate response, including handling timeouts, overlapping notification rules, and user interactions, using a notification server that communicates with client devices to manage when and how notifications are delivered.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If audio notifications are delivered to users based on simple triggering events, then notification delivery is straightforward and quick, but the system cannot intelligently manage when to deliver notifications based on user context

Engineering Contradiction:
Improveintelligent notification managementVSAvoidnotification system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by detecting device presence in the vehicle before generating audio notifications. The notification server determines whether the mobile device is present in the vehicle using sensors (microphone, accelerometer, GPS) and establishes this context in advance, allowing intelligent delivery decisions to be made based on pre-detected user context rather than reacting after the fact.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the notification system processes multiple overlapping notifications, then comprehensive notification coverage is achieved, but determining notification priority and timing becomes complex

Engineering Contradiction:
Improvenotification delivery reliabilityVSAvoidoverlapping notification management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system changes parameters by assigning priority levels to different types of notifications and using device presence detection as a key parameter for delivery decisions. When multiple notifications overlap, the system evaluates the device presence context and notification priorities to determine which notifications should be delivered immediately versus queued, transforming a complex multi-notification problem into a manageable parameter-based decision process.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If audio notifications are generated for all triggering events, then complete notification coverage is provided, but user experience deteriorates due to unnecessary or mistimed notifications

Engineering Contradiction:
Improveuser experience qualityVSAvoidnotification context information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system implements feedback by continuously monitoring device presence status and using this information to modulate notification delivery. The notification server receives feedback about whether the device is in the vehicle and adjusts its behavior accordingly - delivering audio notifications when the device is present in the vehicle and suppressing them when absent, thereby preserving notification context information and improving user experience.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10237386B1Outputting audio notifications based on determination of device presence in a vehicle
Publication Date: 2019.03.19 GOOGLE LLC
  • US10237386B1 patent drawing
  • US10237386B1 patent drawing
  • US10237386B1 patent drawing

AI summary

A computer-implemented method of determining when an audio notification should be generated includes detecting receipt of a triggering event that occurs on a user device; generating, based on detecting, the audio notification for the triggering event; receiving, from the user device, a user voice command responding to the audio notification; and generating a response to the user voice command based on one or more of (i) information associated with the audio notification, and (ii) information associated with the user voice command.