WPD Filter Driver Capability-Level Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Windows Portable Devices (WPD) management systems do not allow administrators to block specific capabilities of a WPD device while allowing access to others, requiring a full device blockage, which restricts access to non-storage capabilities.
Innovation Solution
Implementing a filter driver that intercepts communications with WPD devices to examine and compare their capabilities against policies, allowing specific capabilities to be blocked while retaining others, and causing device initialization to fail if all capabilities are blocked.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If a full device blockage is implemented to prevent access to storage capabilities, then the storage capability is blocked, but access to non-storage capabilities is also restricted
Solution Approach 1:
The patent segments the WPD device capabilities into individual filterable items. The filter driver receives a list of capability objects from the WPD device and processes each capability separately, allowing selective blocking of storage capabilities while permitting non-storage capabilities to remain accessible. This segmentation enables granular control over device functions rather than all-or-nothing blocking.
Solution Approach 2:
The filter driver extracts and removes specific capability objects from the capability list that should be blocked according to policy. By taking out only the storage capability objects from the list and passing the modified list to the WPD host process, the system blocks only the unwanted capabilities while preserving access to other device functions.
2Ease of operation
If capability-level management is implemented, then selective blocking of capabilities is enabled, but system complexity increases
Solution Approach 1:
The filter driver serves as an intermediary component positioned between the WPD device and the WPD host process. It intercepts the capability list, applies policy-based filtering, and passes the modified list downstream. This intermediary approach provides capability-level management without requiring changes to the core WPD architecture or application logic.
Solution Approach 2:
The filter driver automatically processes the capability list by comparing each capability against stored policies and selectively removing blocked capabilities. The system performs self-service filtering without requiring manual configuration or intervention, reducing operational complexity while enabling fine-grained control.
Data Source
AI summary
WPD devices can be managed at the device capability level. When a WPD device is connected to a computer, a filter driver can be employed to examine communications with the WPD device. During initialization, the WPD device will provide a list of its capabilities. The filter driver can intercept this list and compare it against any applicable policies to determine whether any capabilities should be blocked. When it is determined that a capability should be blocked, the filter driver can remove the capability from the list while retaining any non-blocked capabilities. The filter driver can also cause device initialization to fail in some scenarios. In this way, an administrator can block specific capabilities of a WPD device rather than blocking the entire device.