Token-Based Zero-Touch Enrollment for Edge IoT Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing zero-touch enrollment methods for IoT devices require direct communication between a central authority and device managers, exposing security risks and increasing complexity due to multi-trip communication challenges.

Innovation Solution

A token-based approach where a device undergoes initial startup, sends a request to a central directory service, receives a challenge token, converts it to a bearer token, and uses this token to authenticate with a device manager, enabling secure configuration without direct central authority-device manager communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If direct communication between central authority and device manager is used, then device provisioning can be achieved, but security risks increase and system complexity increases

Engineering Contradiction:
Improvedevice provisioning securityVSAvoidcommunication protocol complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a token as an intermediary that mediates between the central authority and device manager. The token contains encoded device information and authentication credentials, allowing the device manager to verify device identity without direct communication with the central authority, thus reducing security risks and system complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent performs preliminary authentication and information encoding at the central authority before device deployment. The token is pre-configured with necessary device information and credentials, eliminating the need for complex real-time communication protocols between the central authority and device manager during device provisioning

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multi-trip communication challenge-response is used, then device authentication can be achieved, but communication traffic increases and system complexity increases

Engineering Contradiction:
Improvedevice authentication securityVSAvoidcommunication traffic
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent performs the authentication challenge-response process preliminarily during token generation at the central authority. The resulting token contains pre-validated authentication credentials that enable single-trip device registration at the device manager, dramatically reducing communication traffic while maintaining authentication security

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a copy of the authentication credentials in the token form, which can be independently verified by the device manager without requiring ongoing communication with the central authority. This copied authentication information eliminates the need for repeated challenge-response exchanges

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12341890B2Token-based zero-touch enrollment for provisioning edge computing applications
Publication Date: 2025.06.24 NVIDIA CORP
  • US12341890B2 patent drawing
  • US12341890B2 patent drawing
  • US12341890B2 patent drawing

AI summary

Approaches in accordance with various embodiments allow for zero-touch enrollment of devices with respective manager systems. In at least one embodiment, a device at startup can contact a central directory service (CDS) for information about an associated manager. The CDS can authenticate the device using device information included in the request, and can send a challenge token to the device in response. The challenge token can include information for the manager, protected with multiple layers of security that should only be able to be decrypted by the authenticated device. The device can decrypt this challenge token to determine the manager information, and can convert this challenge token to a bearer token. The device can then send a request to the determined manager that includes the bearer token, which the manager can use to authenticate the device. The manager can then send the device appropriate configuration information.