Print Event Distribution Device with Reception Confirmation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing event distribution systems, such as those using broadcast or multicast methods, do not confirm whether client devices receive events, leading to potential failures if the client is not running or cannot communicate with the distribution device.

Innovation Solution

A distribution device that includes a registration unit for setting information, an acquisition unit for event information, a determination unit for identifying distribution targets, a distribution unit for sending event information, and a confirmation unit to verify reception by the client device.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a distribution device distributes an event to a client device via a broadcast system or a multicast system, then the event can be distributed to multiple client devices simultaneously, but the distribution device cannot confirm whether the client device has received the event

Engineering Contradiction:
Improveevent distribution efficiencyVSAvoidevent reception confirmation
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the distribution device sends event information to the client device and receives an acknowledgment in return. The confirmation unit monitors whether the client device has received the event by checking for the absence of error messages. If no error message is received within a predetermined time period, the system concludes that the event was successfully delivered, providing reliable confirmation while maintaining efficient broadcast/multicast distribution.

Inventive Principle:
Principle #23Feedback

2Speed

If the distribution device uses broadcast or multicast to distribute events, then the distribution speed is fast, but the client device may fail to receive the event if it is not running or cannot communicate with the distribution device

Engineering Contradiction:
Improveevent distribution speedVSAvoidevent delivery success rate
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent employs a preliminary action approach by establishing a communication channel and sending test messages before distributing actual event information. The registration unit pre-registers client devices, and the confirmation unit sends preliminary acknowledgment requests to verify client device availability. This ensures that event distribution only proceeds to active, reachable clients, preventing delivery failures while maintaining fast distribution speed for confirmed clients.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If the distribution device confirms event reception by waiting for acknowledgment from the client device, then the reliability of event delivery is improved, but the communication overhead and time delay increase

Engineering Contradiction:
Improveevent reception confirmationVSAvoidconfirmation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements periodic action by setting a predetermined time period for waiting for acknowledgment messages. The confirmation unit sends event information at regular intervals and waits for a specific duration before concluding delivery status. This periodic approach balances reliability and time efficiency by not continuously polling for acknowledgment, thus reducing communication overhead while still providing timely delivery confirmation.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9100276B2Distribution device, control method, and storage medium
Publication Date: 2015.08.04 CANON KK
  • US9100276B2 patent drawing
  • US9100276B2 patent drawing
  • US9100276B2 patent drawing

AI summary

A distribution device receives a registration request of setting information relating to distribution of an event occurring in a print device from a client, registers the setting information, acquires print device information including event information relating to an event occurred in the print device from the print device, determines event information which is a distribution target based on the event information included in the acquired print device information and the registered setting information, distributes the determined event information to the client, and confirms the reception of the event information by the client device to which the event information is to be distributed.