Zero-Touch Endpoint Bootstrap via Local Domain Service

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The conventional method of pre-provisioning endpoint devices for cloud-based services is time-consuming and prone to errors, especially when dealing with thousands of devices, as it requires individual administrative setup.

Innovation Solution

The implementation of zero-touch bootstrapping, where an authorized local domain service automates the provisioning of endpoint devices by establishing a secure TLS connection, discovering devices, creating accounts, and issuing access tokens without administrative intervention, leveraging Transport Layer Security (TLS) connections and trusted certificate authorities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If individual administrative pre-provisioning is performed for each endpoint device, then security and proper service configuration are ensured, but the provisioning process becomes time-consuming and error-prone when dealing with thousands of devices

Engineering Contradiction:
Improveservice configuration accuracyVSAvoidprovisioning time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Endpoint devices automatically perform self-provisioning by discovering available cloud services through TLS connections and autonomously registering with service providers. The devices generate their own service requests and complete provisioning without requiring manual administrative intervention for each device, thereby eliminating time-consuming manual operations while maintaining configuration accuracy through automated service discovery and registration protocols

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Administrators perform preliminary bulk configuration of service provider parameters and authentication credentials at the organizational level before devices are deployed. This preliminary setup includes configuring service discovery policies, trust relationships, and default service mappings that enable endpoints to automatically provision themselves upon connection, resolving the contradiction by preparing advance configurations that eliminate per-device manual provisioning time while ensuring security and accuracy through pre-validating service parameters

Inventive Principle:
Principle #10Preliminary action

2Ease of manufacture

If manual pre-provisioning is performed for each endpoint device, then proper account association and service access rights are established, but the process becomes complex and difficult to scale to thousands of devices

Engineering Contradiction:
Improveprovisioning process simplicityVSAvoidscalability to number of devices
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

A universal automated provisioning system is implemented that handles all endpoint device types and service configurations through a single standardized process. The system uses common TLS-based service discovery protocols and automated account association mechanisms that work across thousands of diverse endpoint devices, eliminating the need for device-specific manual provisioning procedures and enabling seamless scaling from small to large deployments while maintaining process simplicity through standardization

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

Solution Approach 2:

An automated service broker or provisioning intermediary is introduced that mediates between endpoint devices and cloud service providers. This intermediary automatically manages account associations, service rights assignment, and provisioning orchestration based on organizational policies, thereby simplifying the provisioning process for administrators while enabling scalable handling of thousands of devices through automated mediation rather than direct manual configuration of each device-service relationship

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If automated zero-touch bootstrapping is implemented, then provisioning speed and scalability are dramatically improved, but the system requires complex TLS connection management and certificate authority trust establishment

Engineering Contradiction:
Improveprovisioning throughputVSAvoidsecurity infrastructure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Organizations pre-establish trust relationships with certificate authorities and configure service discovery policies before deploying endpoint devices. This preliminary security infrastructure setup includes importing CA certificates, configuring trusted issuer lists, and defining service matching rules at the organizational level, thereby enabling high-throughput automated provisioning of thousands of devices while managing security complexity through advance configuration rather than per-device security setup

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses template-based service configurations and replicated security policies that can be copied and applied across multiple endpoint devices simultaneously. Service provider parameters, authentication credentials, and trust relationships are replicated from a central configuration to numerous endpoints through automated provisioning, thereby achieving high provisioning throughput while managing security infrastructure complexity through template replication rather than individual configuration of each device's security settings

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11140149B2Zero-touch bootstrap of an endpoint without admin pre-provisioning
Publication Date: 2021.10.05 CISCO TECHNOLOGY INC
  • US11140149B2 patent drawing
  • US11140149B2 patent drawing
  • US11140149B2 patent drawing

AI summary

An authorized local domain service (ALDS) is deployed in a local network and is authorized to provision endpoints with a cloud-based service on behalf of an organization. The ALDS receives, from a local domain service (LDS) deployed in the local network and configured to connect with and register endpoints in the local network for communications on behalf of the organization, an identity of an endpoint acquired by the LDS when the endpoint registered with the LDS. The ALDS identifies for the organization an account associated with the identity, creates in the cloud-based service for the organization an association between the identity and the account, and notifies the endpoint via the local domain service to onboard against the cloud-based service for access to the cloud-based service.