Dock Token Authentication for Secure Remote Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional docking stations lack remote management capabilities, allowing unauthorized access and making it difficult for IT departments to configure or update firmware, which can lead to security risks and inefficiencies in large networks.

Innovation Solution

A system that allows IT administrators to remotely manage docking stations by sending requests over a network, using a token-based authentication mechanism to authorize actions such as enabling/disabling ports, modifying configurations, or updating firmware, thereby preventing unauthorized modifications and enabling centralized management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a dock is configurable only from a physically connected host computing device, then the dock can be controlled and configured, but unauthorized actors can modify the dock's firmware and add malicious code

Engineering Contradiction:
ImprovesecurityVSAvoidaccess control
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary authentication mechanism (credential verification system) between the computing device and the dock. Before allowing configuration or firmware modification, the system verifies credentials to ensure the computing device is authorized. This mediator prevents unauthorized access while maintaining legitimate control capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the IT department sends an individual administrator to physically connect to each dock to configure or modify firmware, then the dock can be managed, but the process becomes expensive and time consuming

Engineering Contradiction:
Improveconfiguration accuracyVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a universal remote management system that can manage multiple docks through a single network interface. The authentication mechanism and configuration protocol work across different dock instances, allowing one administrator to remotely configure any number of docks without physical presence, thus achieving multi-functionality in dock management.

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

Solution Approach 2:

The patent replaces the mechanical/physical connection requirement with a network-based communication system. Instead of requiring physical cable connections between the administrator's device and each dock, the system uses network protocols to transmit configuration commands and verify credentials remotely, eliminating the need for physical travel and manual connection establishment.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Productivity

If a non-technical user is instructed to configure or modify firmware of a dock, then the IT department can avoid physical visits, but the user can make mistakes and render the dock inoperable

Engineering Contradiction:
Improvemanagement efficiencyVSAvoidsystem stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary anti-action through credential verification and authorization checks before allowing any configuration or firmware modification operations. The system preemptively blocks unauthorized or potentially harmful actions by verifying that the computing device has proper credentials and permissions, preventing users from making mistakes that could render the dock inoperable.

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS11190519B2Dock administration using a token
Publication Date: 2021.11.30 DELL PROD LP
  • US11190519B2 patent drawing
  • US11190519B2 patent drawing
  • US11190519B2 patent drawing

AI summary

In some examples, a software agent may request a token from a server. The request may include dock identifiers associated with one or more docks, credentials, and actions to be performed by the one or more docks. The server may determine, using an access control list, whether the credentials authorize the software agent to instruct the one or more docks to perform the actions. If the server determines that the software agent is authorized, then the server may send a token to the software agent. The software agent may send an action request to the one or more docks. The action request may include the token and the actions. Each dock that receives the request may attempt to validate the token. If the dock successfully validates the token, the dock may perform the actions and send a message to the software agent indicating a result of performing the actions.