Chronological Task History with Communication Event Notifications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users of computing devices face challenges in managing multiple tasks and responding to communication events efficiently, as they often forget or are inconvenienced by interruptions when interacting with other tasks.

Innovation Solution

A method and apparatus that provide a chronologically-ordered task history with integrated communication event notifications, allowing users to easily track task status and respond to communication events by reordering task representations or adding notification indicia, such as unread message counts, within the task history.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the user interacts with multiple tasks concurrently, then the computing device can perform multiple functions, but the user cannot quickly recall which tasks are currently active and which have been closed

Engineering Contradiction:
Improveconcurrent task operationVSAvoidtask status recall
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system pre-establishes a task history representation that automatically records and displays the chronological sequence of task interactions. This preliminary organizational structure is in place before the user needs to recall task status, allowing immediate visual identification of active versus closed tasks without requiring active memory or manual tracking.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system employs visual indicators such as color-coded task representations to differentiate between active and closed tasks. By changing the visual appearance (color, shading, or icon state) of task entries in the history, the user can quickly perceive task status at a glance, transforming abstract task state information into immediately recognizable visual signals.

Inventive Principle:
Principle #32Color changes

2Productivity

If the user responds relatively immediately to communication events, then communication responsiveness is improved, but the user may be inconvenienced by interruptions while interacting with other tasks

Engineering Contradiction:
Improvecommunication response speedVSAvoiduser convenience
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system merges communication event notifications directly into the task history representation. Instead of presenting separate notification alerts that interrupt the user, the communication events are integrated as entries within the chronological task sequence. This unification allows the user to perceive and respond to communications naturally while maintaining their current task flow, eliminating the need to switch contexts or acknowledge separate interruptions.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The task history representation serves as an intermediary between communication events and the user. Rather than delivering raw communication notifications that demand immediate attention, the system mediates these events by embedding them in the contextual framework of the user's task history. This intermediary layer softens the interruption by presenting communications as part of the ongoing task narrative, allowing the user to process and respond at their own pace.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If traditional notification methods are used for communication events, then users are alerted to new messages, but users may forget to respond timely due to preoccupation with other tasks

Engineering Contradiction:
Improvecommunication event notificationVSAvoidresponse delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system pre-organizes communication events within the task history chronologically, creating a persistent visual record that remains accessible throughout user interactions. This preliminary structuring ensures that communication notifications are not lost or forgotten even when the user is engaged with other tasks, as they are already positioned in the contextual framework of the user's activity history.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The task history representation provides continuous visual feedback about communication events that have been missed or are unread. By maintaining a chronological record that highlights unread messages and their position in the task sequence, the system gives the user ongoing awareness of communication status without requiring active recall, enabling timely response when the user returns to the task history.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10073603B2Method and apparatus for providing notification of a communication event via a chronologically-ordered task history
Publication Date: 2018.09.11 NOKIA TECHNOLOGIES OY
  • US10073603B2 patent drawing
  • US10073603B2 patent drawing
  • US10073603B2 patent drawing

AI summary

A method, apparatus and computer program product are provided to facilitate task management with a chronologically-ordered task history such that a user may more readily determine the status of various tasks and may efficiently interact therewith. The method, apparatus and computer program product may provide for notification of a communication event to be integrated into the chronologically-ordered task history so as to provide a visible reminder to the user of recent communication events. In the context of a method, a chronologically-ordered task history may be caused to be presented. The chronologically-ordered task history may include task representations of a plurality of respective tasks with the task representations being ordered chronologically based upon user interaction therewith. The method may also include receiving a communication event from another party and causing notification of the communication event to be provided, such as by by modifying the chronologically-ordered task history.