Composite Usage Data Cleaning Notifications

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Personal computing devices become contaminated with dust, dirt, oil, bacteria, and viruses due to frequent use, leading to degraded performance and potential health risks, as users often forget to clean them regularly.

Innovation Solution

An analysis of usage data, including elapsed time since cleaning, touchscreen interactions, movement, and sensor interference, is used to determine if a cleaning notification should be generated, automatically reminding users to clean their devices to maintain performance and health.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users manually track and remember cleaning schedules, then cleaning regularity may be maintained, but user burden and likelihood of forgetting increase

Engineering Contradiction:

Improvecleaning regularityVSAvoiduser burden

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system automatically monitors usage data, determines contamination levels, and generates cleaning notifications without requiring user intervention for tracking or decision-making. The computing device serves itself by monitoring its own usage patterns and initiating cleaning reminders autonomously.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system continuously monitors usage data (touchscreen interactions, movement, sensor interference) and provides feedback in the form of cleaning notifications when contamination thresholds are exceeded. This closed-loop feedback ensures cleaning occurs based on actual contamination levels rather than fixed schedules.

Inventive Principle:

Principle #23Feedback

2Productivity

If cleaning is delayed, then device usage continues uninterrupted, but contamination increases leading to performance degradation and health risks

Engineering Contradiction:

Improvedevice usage continuityVSAvoidcontamination level

Core Design Contradiction:

ProductivityVSObject-affected harmful factors

Solution Approach 1:

The system replaces manual cleaning schedules with an automated electronic monitoring and notification system. Usage data is automatically collected and analyzed by software algorithms that determine when cleaning is needed, substituting mechanical/user-based tracking with electronic automation.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system performs preliminary monitoring of usage patterns and proactively generates cleaning notifications before significant contamination occurs. By detecting contamination trends early through usage data analysis, the system prompts cleaning at optimal intervals, preventing performance degradation before it occurs.

Inventive Principle:

Principle #10Preliminary action

3Measurement precision

If multiple types of usage data are analyzed, then cleaning determination accuracy improves, but system complexity increases

Engineering Contradiction:

Improvecontamination detection accuracyVSAvoiddata analysis complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The system combines multiple usage data types (touchscreen interactions, movement data, sensor interference) into a unified contamination assessment. By merging these different data streams and analyzing them collectively, the system achieves comprehensive contamination detection without requiring separate complex systems for each data type.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS11995295B2Cleaning notifications

Publication Date: 2024.05.28 HEWLETT PACKARD DEVELOPMENT COMPANY LP

AI summary

In one example, a notification may be generated to prompt a user to clean a personal computing device. The notification may be based upon usage data of the personal computing device. Multiple types of usage data may be determined and combined to create a composite usage value. The composite usage value may be compared to a threshold usage value. A notification may be generated if the composite usage value exceeds the threshold usage value.