Domain Operation Verification Codes for Local Compliance Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge of providing domain-related services efficiently and securely across different localities with varying compliance requirements, where data must remain within the locality, is addressed by implementing a verification service provider within the locality to manage registry operations.

Innovation Solution

A verification service provider system is introduced to handle domain name operations, generating verification codes that comply with local requirements, ensuring data remains within the locality, and facilitating registry operations through a network of devices including registrars and registries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a registry operates domain name services directly in a locality, then compliance with local verification policies can be achieved, but data security concerns arise from direct dependency on local data

Engineering Contradiction:
Improvecompliance with local verification policiesVSAvoidsecurity concerns from direct data dependency
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

A verification service provider is introduced as an intermediary between the registry and local verification data. The provider receives verification requests from registrars, performs verification against local policies, and returns verification codes without the registry directly accessing or storing local verification data, thus maintaining security while ensuring compliance

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If a registry operates outside a locality, then physical presence requirements are avoided, but compliance with local verification processes becomes difficult

Engineering Contradiction:
Improvephysical presence requirementsVSAvoidcompliance with local verification processes
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The verification service provider acts as a mediator that enables registries operating outside the locality to comply with local verification requirements. The provider has access to local verification data and policies, performs verification operations, and returns results to the external registry through standardized protocols, eliminating the need for physical presence

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The verification service provider is designed to work with multiple registries and support various domain name verification scenarios through a unified interface. It can handle different types of verification requests (domain registration, transfer, renewal) and return appropriate verification codes, making the solution universally applicable to external registries

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

3Ease of operation

If verification data is accessed directly by the registry, then verification processes can be performed, but data privacy and security are compromised

Engineering Contradiction:
Improveverification process executionVSAvoiddata privacy and security risks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The verification service provider serves as a secure intermediary that accesses verification data only when needed to fulfill specific verification requests. It retrieves data from local sources, performs verification, and returns only the necessary verification code without exposing the underlying verification data to the registry or registrar, thus protecting data privacy and security

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system extracts only the essential verification code from the verification process, separating it from the sensitive verification data. The verification service provider performs the complete verification operation internally and outputs only the verification code, which is then used by the registry without exposing any sensitive information

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP4246926B1Domain name operation verification code generation and/or verification
Publication Date: 2026.03.18 VERISIGN INC
  • EP4246926B1 patent drawingFigure 1
  • EP4246926B1 patent drawingFigure 2
  • EP4246926B1 patent drawingFigure 3

AI summary

System, apparatus, methods, and computer-readable medium for generating a verification code related to a registry operation request are provided. A verification process may be performed to determine if a verification request related to a registry operation is to be approved. If the request is to be approved, a verification code is generated that includes identifying information of a verification service provider (102) and a code indicating that the request has been verified.