Printer Driver Maintenance via Print Ticket and Port Monitor

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The v4 printer driver architecture restricts the usage of unique interfaces and maintenance commands, making it difficult for applications to execute functions unrelated to printing, such as maintenance tasks, due to limitations on handling print jobs and external interfaces.

Innovation Solution

An information processing apparatus and method that utilize a Print Ticket to instruct and execute non-printing functions by an application, which sets instructions, calls the printer driver, and executes maintenance functions through a maintenance SDK Wrapper and UI extension module, allowing access to device-dependent information without direct access to the printer driver's unique API.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a unique interface is used in a printer driver to enable external applications to access maintenance functions, then the functionality and versatility of the printer driver is improved, but the device complexity and difficulty of operation increase under the v4 architecture

Engineering Contradiction:
ImprovefunctionalityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a port monitor as an intermediary component that sits between the application and the printer driver. The port monitor receives maintenance commands from applications, converts them into appropriate print jobs, and transmits them to the printer driver. This mediator approach allows applications to access printer maintenance functions without requiring direct integration with the printer driver's unique interface, thereby reducing complexity while maintaining versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a port monitor is used to execute maintenance functions in v4 architecture, then the ability to perform non-printing functions is improved, but the arrangement complexity increases

Engineering Contradiction:
Improvemaintenance function executionVSAvoidarrangement
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent makes the port monitor a universal component that can handle both printing operations and maintenance functions through a unified interface. By designing the port monitor to process all commands (print and maintenance) through the same mechanism (converting them to print jobs), the system achieves multi-functionality without requiring separate complex pathways for different function types, thus reducing overall arrangement complexity.

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

3Ease of operation

If external applications directly access printer driver functions, then the ease of operation is improved, but the reliability and stability of the printing system deteriorates

Engineering Contradiction:
Improveapplication accessVSAvoidsystem stability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The port monitor serves as a protective intermediary layer that validates and standardizes all commands before they reach the printer driver. This ensures that only properly formatted and authorized commands are processed, preventing potential system instability while maintaining ease of application access. The port monitor acts as a gateway that simplifies application interaction while preserving system integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10289364B2Information processing apparatus, method, and non-transitory computer-readable storage medium storing program
Publication Date: 2019.05.14 CANON KK
  • US10289364B2 patent drawing
  • US10289364B2 patent drawing
  • US10289364B2 patent drawing

AI summary

In an application, an instruction to execute a function is set in a Print Ticket and a printer driver is called via an OS. In the printer driver, the Print Ticket is obtained from the OS, and the function is executed based on the instruction set in the obtained Print Ticket.