Print Notification Mechanism for Rich Job Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current notification methods in print-related systems are basic and lack granularity, failing to provide detailed updates on the progress of print jobs, which limits the richness and effectiveness of notification processes.

Innovation Solution

A notification mechanism that extends from a printing application to the spooler and back to the hosting process, allowing interested applications to register for updates on print job progress through notification pipes and APIs, enabling rich and robust notifications across various stages of the print job processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If basic notification methods are used in print-related systems, then the system complexity is low, but the notification granularity and information richness are insufficient

Engineering Contradiction:
Improvenotification information richnessVSAvoidnotification system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The notification system is segmented into multiple hierarchical levels: spooler notifications, hosting process notifications, and application-specific notifications. Each level handles specific aspects of the printing process, allowing detailed information to be transmitted without requiring a monolithic complex system. The segmentation enables selective subscription to notification types based on user needs.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension to the notification system by implementing a multi-layered architecture that adds vertical depth to the notification flow. Instead of a single flat notification channel, the system creates multiple layers (spooler → hosting process → application) that can operate independently and provide information at different granularities simultaneously.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Ease of operation

If detailed notifications about print job progress are implemented, then user experience and scheduling decisions are improved, but the notification mechanism complexity increases

Engineering Contradiction:
Improveuser experienceVSAvoidnotification mechanism complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The notification system implements continuous feedback loops where the spooler provides progress updates to the hosting process, which then relays relevant information to applications. This feedback mechanism enables real-time monitoring of print job status, allowing users to make informed scheduling decisions and improving overall system responsiveness without requiring manual intervention.

Inventive Principle:
Principle #23Feedback

3Reliability

If a robust notification mechanism with multiple components is implemented, then notification reliability and information completeness are improved, but the system architecture becomes more complex

Engineering Contradiction:
Improvenotification reliabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The hosting process serves multiple functions: it manages the print pipeline, hosts filters, and acts as a notification intermediary between the spooler and applications. This multi-functionality reduces the need for separate dedicated components for each function, maintaining reliability while controlling architectural complexity through component consolidation.

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

Data Source

PatentUS7969610B2Notification methods and systems for print-related systems
Publication Date: 2011.06.28 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7969610B2 patent drawing
  • US7969610B2 patent drawing
  • US7969610B2 patent drawing

AI summary

Notification mechanisms for use in connection with print systems are described. In one embodiment, a notification mechanism extends from a printing application to the spooler, from the spooler to a hosting process, and back to the spooler. The notification mechanism can allow interested applications, such as print user interfaces, to register to receive updates on the progress of a print job. The notification mechanism provides a very rich and robust mechanism through which notifications can be generated and received.