Verifying Computing Device Functionality Restrictions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for restricting functionalities on computing devices, such as during examinations, are time-consuming, error-prone, and can be circumvented by users, as they rely on manual configuration or execution of configuration files without verification.

Innovation Solution

A computing device system that receives a verification code and determines the status of its configuration mode, generating a notification message based on the code and executed configuration file to ensure that restricted functionalities are indeed restricted, preventing users from mimicking the verification process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual configuration or configuration file execution is used to restrict functionalities, then the device can operate in restricted mode, but the method is time-consuming and error-prone

Engineering Contradiction:
Improvespeed of restricting functionalitiesVSAvoidaccuracy of restriction execution
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by automatically detecting the configuration mode status and generating verification information before the actual examination or restricted task begins. This eliminates the need for manual configuration checks during the process, improving both speed and reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by continuously monitoring the configuration mode status and providing verification information that confirms whether restrictions are properly applied. This closed-loop approach ensures accuracy without requiring manual verification, resolving the contradiction between speed and reliability.

Inventive Principle:
Principle #23Feedback

2Extent of automation

If configuration files are executed to restrict functionalities, then automation is improved, but users can circumvent restrictions by mimicking the verification process

Engineering Contradiction:
Improveautomation of restriction applicationVSAvoidsecurity of restriction enforcement
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The system moves verification from a single dimension (checking for presence of configuration file) to multiple dimensions by combining status detection, verification code generation, and cryptographic validation. This multi-dimensional approach prevents circumvention while maintaining automation, as users would need to replicate the entire verification chain rather than simply mimicking a single check.

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

Solution Approach 2:

The system introduces an intermediary verification mechanism that acts as a trusted mediator between the configuration file and the restriction enforcement. The verification code and status information serve as intermediaries that provide cryptographic proof of proper configuration, preventing users from bypassing restrictions through simple mimicry while keeping the process automated.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If verification mechanisms are added to confirm configuration file execution, then reliability of restriction is improved, but device complexity increases

Engineering Contradiction:
Improveverification of functionality restrictionVSAvoidcomplexity of verification system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The device performs self-verification by automatically detecting its own configuration mode status and generating verification information without requiring external verification infrastructure. This self-service approach improves reliability while minimizing added complexity, as the verification capabilities are built into the device itself rather than requiring complex external systems.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10432547B2Verifying functionality restrictions of computing devices
Publication Date: 2019.10.01 HEWLETT PACKARD DEVELOPMENT COMPANY LP
  • US10432547B2 patent drawing
  • US10432547B2 patent drawing
  • US10432547B2 patent drawing

AI summary

The present subject matter relates to verifying functionality restrictions of a computing device. In an example implementation, the verification includes generating a notification message based on a verification code received in the computing device and status of a configuration mode in the computing device. When the status of the configuration mode is active, at least one functionality of the computing device is restricted. The configuration mode can be activated in the computing device by execution of a configuration file. The generated notification message is provided, which enables verifying that the at least one functionality of the computing device is restricted.