Registry Status Set Management for Court Order Compliance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing domain name management system lacks the ability to manage multiple status values for different underlying reasons, leading to potential accidental violations of court orders and insufficient granularity for registries to maintain status values effectively.

Innovation Solution

A computer-implemented method that allows for the management of status codes by receiving requests to change status sets related to provisioned objects, including receiving a reason for the change and updating the status codes accordingly, enabling logical grouping of status codes into sets and allowing for their addition and removal based on specific reasons.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the domain name management system uses standard status values to prevent changes, then the domain name is protected from unauthorized modifications, but the system cannot distinguish between different underlying reasons for status changes, leading to potential accidental violations of court orders

Engineering Contradiction:
Improveprotection of domain name from unauthorized changesVSAvoidloss of underlying reasons for status values
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the domain name management system by introducing a separate database table (status_set_reasons) that stores the underlying reasons for each status value. This segmentation allows the system to maintain standard status values while preserving granular information about why each status was applied, thus preventing information loss while maintaining protection.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (the status_set_reasons database table and associated EPP extensions) between the status value application and the domain name record. This intermediary preserves the underlying reasons without interfering with the core status protection function, allowing the system to maintain both reliability and information integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If the registry removes a status value corresponding to a transfer-prevention status, then the domain name can be transferred, but the registry may accidentally violate court orders by removing necessary protection

Engineering Contradiction:
Improveability to transfer domain nameVSAvoidcompliance with court orders
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where the system checks the underlying reasons for status values before allowing removal or modification. The EPP interface provides feedback to registrars about the current status and its reasons, enabling informed decisions that prevent accidental violations of court orders while allowing legitimate transfers.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent requires preliminary verification of underlying reasons before allowing status value changes. The system checks whether removing a status value would violate any stored reasons (such as court orders) before permitting the change, thus preventing accidental violations before they occur.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If the system allows multiple status values to be applied to a domain name, then comprehensive protection can be provided, but the system lacks granularity to manage multiple underlying reasons for the same status value

Engineering Contradiction:
Improvecomprehensive protection of domain nameVSAvoidcomplexity of managing status values
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple status values and their underlying reasons into a unified management structure. The status_set_reasons table consolidates information about multiple reasons for status values, and the EPP interface provides unified commands for managing both status values and their reasons, reducing complexity while maintaining comprehensive protection.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal status management system that handles both standard status values and their underlying reasons through a single EPP interface framework. This multi-functional approach allows the system to manage protection, transfers, and court order compliance through unified commands, reducing operational complexity.

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

4Reliability

If the registry maintains detailed information about underlying reasons for status values, then compliance with court orders is ensured, but the system requires more complex data structures and management procedures

Engineering Contradiction:
Improvecompliance with court ordersVSAvoidcomplexity of data structures
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the data structure by creating a separate database table (status_set_reasons) that stores detailed information about underlying reasons. This segmentation isolates the complexity of storing and managing detailed reason information from the core domain name management system, allowing compliance tracking without overwhelming the main data structures.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10182032B2Systems and methods for setting registry service status
Publication Date: 2019.01.15 VERISIGN INC
  • US10182032B2 patent drawing
  • US10182032B2 patent drawing
  • US10182032B2 patent drawing

AI summary

A system, method, and computer-readable medium enable a domain name or host name registry to effectively manage status codes associated with the domain or host. Status codes are organized into status sets that can be added, removed, activated, or deactivated in accordance with a suitable change request. The status codes corresponding to a removed status set that are also enabled according to other active status sets are not removed when the removal of the status set is processed.