Peripheral Device Class Identifier Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Peripheral device vendors face challenges in updating software packages, such as drivers and installers, due to the need for new hardware identifiers for each device, leading to increased costs and complexity in retesting, recertification, and distribution.

Innovation Solution

A vendor-specific peripheral device class identifier is generated by combining a vendor identifier, namespace identifier, and namespace entry identifier, allowing multiple devices to share the same setup record and driver, reducing the need for individual updates and simplifying the setup process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If a new hardware identifier is assigned to each peripheral device, then device identification precision is improved, but software package complexity and update costs increase

Engineering Contradiction:
Improvedevice identification precisionVSAvoidsoftware package complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The hardware identifier is segmented into multiple components: vendor identifier, device class identifier, and device instance identifier. This segmentation allows the system to maintain precise device identification while reducing software complexity by handling different identifier components at different levels of the software architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to device identification by organizing identifiers into multiple levels (vendor level, device class level, device instance level). This dimensional organization transforms the flat identifier structure into a hierarchical one, enabling more efficient software management and reducing overall system complexity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Measurement precision

If a new hardware identifier is assigned to each peripheral device, then device identification precision is improved, but retesting and recertification costs increase

Engineering Contradiction:
Improvedevice identification precisionVSAvoidretesting and recertification costs
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

By segmenting the identifier into vendor identifier and device-specific identifier components, the patent enables selective updating. When a device is updated, only the device-specific portion needs to change, while the vendor identifier remains constant, reducing the scope of required retesting and recertification.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The vendor identifier serves multiple functions: it identifies the vendor, groups vendor-specific devices, and enables vendor-level software updates. This multi-functionality reduces the need for separate identification mechanisms, thereby reducing retesting and recertification requirements.

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

3Measurement precision

If a new hardware identifier is assigned to each peripheral device, then device identification precision is improved, but distribution costs increase

Engineering Contradiction:
Improvedevice identification precisionVSAvoiddistribution costs
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The hierarchical segmentation of identifiers enables modular software package distribution. Vendors can distribute vendor-specific base packages that work across multiple devices, and only need to distribute device-specific updates when necessary, significantly reducing distribution costs.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of distributing complete software packages for every possible device configuration, the patent implements partial updates by distributing only the specific identifier components that have changed. This reduces distribution overhead while maintaining precise device identification.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10684962B2Vendor-specific peripheral device class identifiers
Publication Date: 2020.06.16 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10684962B2 patent drawing
  • US10684962B2 patent drawing
  • US10684962B2 patent drawing

AI summary

A peripheral device class identifier is generated for a class of peripheral devices, and is used to identify a setup record that indicates how to install or otherwise set up the class of peripheral devices on a computing device. The peripheral device class identifier is a combination of three components: a vendor identifier, a namespace identifier, and a namespace entry identifier. The vendor identifier is an identifier of the vendor of the class of peripheral devices. The namespace identifier is an identifier of different collections or groups of types of peripheral devices or types of functionality of peripheral devices. The namespace entry identifier is an identifier of a particular type of peripheral device (or particular functionality) of the different collections or groups of types of peripheral devices (or types of functionality of peripheral devices).