Automated Peripheral Driver Uninstallation via Leaving Messages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network device management systems face inefficiencies due to the automatic installation and removal of device drivers, leading to resource waste and operational inefficiencies, particularly in large-scale office environments with frequent device updates and additions, where unnecessary drivers are installed and manually uninstalled, causing confusion and increased network load.

Innovation Solution

An information processing apparatus with a reception unit to receive messages from peripheral devices, an analysis unit to determine the necessity of driver uninstallation, and a notification system to inform clients of device removal, allowing controlled and automated uninstallation of device drivers based on administrator designations, using a network proxy to ensure client notification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If automatic driver installation is implemented for network devices, then device compatibility and ease of connection are improved, but the number of installed drivers increases indefinitely causing resource waste and system confusion

Engineering Contradiction:
Improveease of device connectionVSAvoidnumber of drivers
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The system performs preliminary action by having the peripheral device send a leaving message before actually leaving the network. This allows the client computer to prepare for driver uninstallation in advance, ensuring that when the device truly leaves, the driver is automatically removed without waiting for manual intervention or causing accumulation of unnecessary drivers.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by establishing a communication mechanism where peripheral devices send leaving messages to client computers. This feedback loop allows the client to detect when a device has left the network and automatically respond by uninstalling the corresponding driver, preventing indefinite accumulation of drivers while maintaining ease of device connection.

Inventive Principle:
Principle #23Feedback

2Loss of energy

If manual driver uninstallation is performed to remove unnecessary drivers, then resource waste is reduced, but the time and labor required increases significantly in large-scale networks

Engineering Contradiction:
Improveresource wasteVSAvoidtime for driver management
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The system enables self-service by allowing the peripheral device itself to trigger the driver uninstallation process through leaving messages. The client computer automatically processes these messages and uninstalls drivers without requiring manual intervention, thereby reducing resource waste while eliminating the time-consuming manual uninstallation process in large-scale networks.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by having devices send leaving messages before actually leaving the network, enabling automatic driver removal preparation. This preliminary action eliminates the need for manual driver management by establishing the uninstallation trigger in advance, significantly reducing both resource waste and management time.

Inventive Principle:
Principle #10Preliminary action

3Extent of automation

If client computers poll printers upon startup to detect removals, then driver uninstallation can be automated, but network load increases significantly

Engineering Contradiction:
Improveautomation of driver uninstallationVSAvoidnetwork load
Core Design Contradiction:
Extent of automationVSPower

Solution Approach 1:

The system inverts the traditional polling approach by having peripheral devices actively send leaving messages to client computers instead of clients passively polling for device removals. This inversion reduces network load significantly while maintaining automation of driver uninstallation, as devices only communicate when they are actually leaving the network rather than continuous polling occurring.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The system replaces continuous or frequent polling with periodic action by having devices send leaving messages only when they are actually leaving the network. This periodic communication pattern significantly reduces network load compared to continuous polling, while still achieving automated driver uninstallation through the leaving message mechanism.

Inventive Principle:
Principle #19Periodic action

4Ease of operation

If drivers of temporarily down devices are automatically uninstalled, then current confusion is avoided, but operational efficiency drops due to unnecessary installation and uninstallation cycles

Engineering Contradiction:
Improveprinter selection clarityVSAvoidoperation efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system performs preliminary action by requiring the device to send a leaving message before driver uninstallation occurs. This preliminary message ensures that only devices that are actually leaving the network (not temporarily down) trigger driver removal, preventing unnecessary uninstallation cycles while maintaining clear printer selection. The leaving message acts as a verification step that distinguishes between temporary downtime and actual device removal.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8161198B2Uninstalling drivers of a peripheral device
Publication Date: 2012.04.17 CANON KK
  • US8161198B2 patent drawing
  • US8161198B2 patent drawing
  • US8161198B2 patent drawing

AI summary

According to the present invention, an information processing apparatus which can communicate with a peripheral device that issues a message including state information, comprisesa reception unit adapted to receive a leaving message from the peripheral device;an analysis unit adapted to analyze the leaving message received from the peripheral device; andan uninstall unit adapted to uninstall, when said analysis unit analyzes that information included in the leaving message is an uninstall notification indicating that a device driver corresponding to the peripheral device which sent the leaving message is to be uninstalled, a driver program corresponding to the peripheral device that sent the leaving message.