Unique Entity Identifier System with Jurisdiction Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current identifiers lack distinction between entities, leading to confusion due to shared identifiers across jurisdictions, and existing standards like ISO 8000-116 leave implementation details to user discretion, necessitating a unique and unambiguous identifier for natural and juridical persons.

Innovation Solution

A system and method for creating a unique identifier that includes a domain portion defining jurisdiction, a sub-domain portion with entity type and global registration agency code, and a registration identifier portion, conforming to ISO 8000-116 standards, with the ability to generate a universally unique identifier or proxy identifier when primary registration information is unavailable.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single identifier is used across different jurisdictions, then the identifier structure is simple, but the identifier becomes ambiguous and cannot distinguish between distinct entities

Engineering Contradiction:
Improveidentifier structure complexityVSAvoididentifier uniqueness
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The identifier is segmented into multiple distinct parts: a jurisdiction identifier portion, an entity type portion, and a registration identifier portion. This segmentation allows the same registration number to be uniquely identified across different jurisdictions by prefixing it with the appropriate jurisdiction code, thereby resolving the ambiguity while maintaining a structured and manageable format.

Inventive Principle:
Principle #1Segmentation

2Reliability

If each jurisdiction creates its own identifier set, then each identifier is unique within its jurisdiction, but the overall system becomes complex and identifiers cannot be distinguished across jurisdictions

Engineering Contradiction:
Improveidentifier uniqueness within jurisdictionVSAvoidoverall identifier system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The identifier system is designed to be universal across all jurisdictions while maintaining local uniqueness. The standardized structure with jurisdiction identifier, entity type, and registration number portions allows the same format to serve multiple jurisdictions simultaneously, enabling global distinction without requiring complex jurisdiction-specific formats.

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

3Adaptability or versatility

If ISO 8000-116 standard is followed with user discretion, then flexibility in implementation is maintained, but consistent application across different users is difficult

Engineering Contradiction:
Improveimplementation flexibilityVSAvoididentifier construction consistency
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The system specifies fixed parameters for each portion of the identifier (jurisdiction identifier format, entity type codes, registration number structure) to ensure consistency across implementations. This parameter standardization maintains the flexibility allowed by ISO 8000-116 while ensuring that all users construct identifiers in a uniform, predictable manner.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20230367750A1System and method for assigning an entity a unique identifier
Publication Date: 2023.11.16 NOETIC MASTER MODEL HLDG CO LLC
  • US20230367750A1 patent drawing
  • US20230367750A1 patent drawing
  • US20230367750A1 patent drawing

AI summary

A method of assigning a unique identifier to an entity includes receiving a name of an entity and associated information about the entity; and assigning a globally unique identifier to the entity conforming to both the ISO 8000-115 and the ISO 8000-116 standards The unique identifier includes a domain portion defining a jurisdiction of the entity; a sub-domain portion having an entity type, global registration agency code for the jurisdiction, and a date of registration or formation of the entity; and a registration identifier portion of the entity in the jurisdiction. The method further includes storing the unique identifier along with the name of the entity in a database for fast retrieval of information about the entity.