Scheme-Based Identifier Management for B2B Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The UN/CEFACT Core Components Technical Specification lacks guidance on how to use, implement, or process identifiers in business applications, which hinders interoperability and consistency in business-to-business exchanges.

Innovation Solution

A computer-implemented method for configuring and managing identification schemes, including creating a scheme entity to represent the identification scheme, defining its structure, and associating it with identifiers, which allows for the generation, communication, and processing of unique and valid identifiers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the UN/CEFACT Core Components Technical Specification is used to standardize business transactions, then interoperability between business partners is improved, but the lack of guidance on identifier usage leads to inconsistency in implementation and processing

Engineering Contradiction:
Improveinteroperability consistencyVSAvoididentifier management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces specific parameters and attributes for identifier entities, including identifier type, format patterns, length constraints, and validation rules. By defining these parameters systematically in the CCTS framework, the patent transforms the vague identifier usage into a structured system with measurable and controllable attributes, thereby improving consistency while maintaining manageability

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent segments identifier management into distinct components: identifier definition, format specification, validation rules, and processing guidance. By dividing the identifier management system into these separable modules, each with specific responsibilities, the patent reduces overall complexity while ensuring comprehensive coverage of identifier usage requirements

Inventive Principle:
Principle #1Segmentation

2Reliability

If identifiers are generated without a structured scheme, then implementation flexibility is improved, but identifier uniqueness and validity cannot be ensured

Engineering Contradiction:
Improveidentifier uniquenessVSAvoididentifier generation flexibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements dynamic identifier generation through configurable format patterns and templates that can adapt to different business contexts. The system allows flexible combination of fixed elements (like prefixes and suffixes) with variable elements (like sequential numbers or UUIDs), enabling identifiers to be generated dynamically based on specific requirements while maintaining uniqueness through validation rules

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces an intermediary validation mechanism that mediates between the flexible generation process and the uniqueness requirement. This intermediary layer checks generated identifiers against existing ones, validates format compliance, and ensures uniqueness before finalizing the identifier, thus bridging the gap between flexibility and reliability

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If identifier supplementary components are not standardized, then implementation simplicity is improved, but business-to-business exchange interoperability deteriorates

Engineering Contradiction:
ImproveB2B exchange interoperabilityVSAvoididentifier structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal identifier structure with standardized supplementary components that can serve multiple functions across different business contexts. The identifier entity includes universal elements like format patterns, length specifications, and validation rules that work across various B2B scenarios, while allowing optional context-specific extensions, thus achieving both interoperability and controlled complexity

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

Data Source

PatentUS8086646B2Scheme-based identifier
Publication Date: 2011.12.27 SAP SE
  • US8086646B2 patent drawing
  • US8086646B2 patent drawing
  • US8086646B2 patent drawing

AI summary

In general, the subject matter described in this specification can be embodied in methods, systems, and program products. An identification scheme that is to be used for generating at least one identifier for an object is identified. A scheme entity that represents the identification scheme and includes at least one aspect thereof is created. The created scheme entity is stored in a repository such that the scheme entity can be selected for association with the identifier.