Device State Management System for Printing Network Stability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex computing networks with numerous printing devices face challenges in maintaining accurate device databases due to IP address changes, device disconnections, and inconsistent information, leading to system instability and unreliable state management.

Innovation Solution

A device state management system sends probe messages to printing devices, determines unconfirmed devices, calculates a system-instability value, and updates the database by clustering addresses to efficiently rediscover and stabilize the network, using vector quantization techniques to optimize probe messaging and maintain database accuracy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system sends probe messages to all printing devices to maintain database accuracy, then the reliability of device information is improved, but the bandwidth consumption and system complexity increase

Engineering Contradiction:
Improvedevice database accuracyVSAvoidbandwidth usage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system applies different probe strategies to different devices based on their confirmation status. Confirmed devices receive periodic probes to maintain accuracy, while unconfirmed devices trigger targeted probe sequences. This local differentiation optimizes bandwidth usage by concentrating probing efforts where most needed rather than uniformly probing all devices.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system segments devices into confirmed and unconfirmed categories, applying different management strategies to each segment. This segmentation allows the system to focus resources on unconfirmed devices that require verification, while reducing probing frequency for confirmed devices, thereby optimizing overall bandwidth consumption.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If the system performs comprehensive device discovery to ensure complete database information, then the measurement precision of device status is improved, but the time required for discovery increases

Engineering Contradiction:
Improvedevice status accuracyVSAvoiddiscovery time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by maintaining a device database with known device information from previous discoveries. When a device is needed, the system first checks the database for existing confirmed information, avoiding the need to perform complete discovery procedures for every device access, thus reducing discovery time while maintaining accuracy for confirmed devices.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies partial discovery action by sending targeted probe messages only to specific unconfirmed devices or address clusters when instability is detected, rather than performing exhaustive discovery of all devices. This partial action is sufficient to resolve the specific instability issue without the time cost of complete system-wide discovery.

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If the system uses vector quantization to cluster addresses and optimize probing, then the productivity of device discovery is improved, but the device complexity increases

Engineering Contradiction:
Improvedevice discovery efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system merges nearby IP addresses into address clusters using vector quantization, treating groups of adjacent addresses as single probing units. This merging reduces the total number of individual probe messages needed, improving discovery productivity. The clustering algorithm groups addresses that are likely to contain devices based on their proximity in the address space.

Inventive Principle:
Principle #5Merging (Combining)

4Stability of the object's composition

If the system continuously monitors and updates device database to maintain stability, then the stability of system state is improved, but the loss of time for updates increases

Engineering Contradiction:
Improvesystem state stabilityVSAvoidupdate time
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The system uses periodic probing intervals for confirmed devices rather than continuous monitoring. Devices are probed at regular intervals to verify their continued presence and status, maintaining database stability without requiring constant update operations. This periodic approach reduces update time while preserving system stability.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system implements feedback mechanisms where probe responses from devices confirm their status and trigger database updates only when changes are detected. This feedback-driven approach maintains stability by updating the database based on actual device state changes rather than continuous periodic updates, reducing unnecessary update time.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10346107B2Methods and apparatus for situational and event-driven discovery optimization of printing devices
Publication Date: 2019.07.09 KYOCERA DOCUMENT SOLUTIONS INC
  • US10346107B2 patent drawing
  • US10346107B2 patent drawing
  • US10346107B2 patent drawing

AI summary

Methods and apparatus for updating data for printing devices are provided. A device state management system (DSMS) can send probe messages to printing devices. The DSMS can receive responses to the probe messages, where the number of probe messages can exceed the number of responses. After receiving the responses, a number of unconfirmed printing devices can be determined based on data stored in a device database (DDB) associated with the DSMS. The DSMS can determine a system-instability value associated with the number of unconfirmed printing devices. The DSMS can determine whether the system-instability value exceeds a threshold. After determining that the system-instability value exceeds the threshold, the DSMS can: determine address clusters associated with the unconfirmed printing devices; send probe messages to addresses within at least one address cluster; receive responses to the probe messages; and update the DDB using data in the responses.