Token Data Structure Framework for Database Storage Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The growing interconnectivity of remote systems poses challenges in implementing a standard library or token system to manage databases, leading to issues such as duplicate tokens, exponential database growth, increased storage and computing resource costs, latency, and delays.

Innovation Solution

A computing framework generates a token data structure to manage databases by using mappings within a token library to define a framework for each token, ensuring uniqueness through a validation function, thereby reducing storage needs and improving performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a standard library or token system is implemented to manage databases for each remote system, then database management capability is improved, but duplicate tokens are generated when multiple remote systems reference the same application identifier

Engineering Contradiction:
Improvedatabase management capabilityVSAvoidnumber of duplicate tokens
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent implements a centralized token generation service that serves multiple remote systems universally. Instead of each remote system having its own independent token system, a single centralized service generates tokens for all systems, allowing one token system to perform the function for multiple clients and preventing duplicate tokens across different systems.

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

Solution Approach 2:

The patent introduces a centralized token generation service as an intermediary between remote systems and the database management infrastructure. This intermediary layer receives requests from multiple remote systems, generates unique tokens centrally, and returns them to the appropriate systems, thereby preventing duplicate token generation while maintaining database management capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If tokens are generated for each remote system independently, then each system can manage its own database, but the database grows exponentially resulting in increased storage and computing resource costs

Engineering Contradiction:
Improveautonomous database managementVSAvoiddatabase size
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The centralized token generation service provides a universal solution that handles database management requests from multiple remote systems through a single infrastructure. This eliminates the need for each system to independently manage its own database, thereby preventing exponential growth while maintaining operational efficiency.

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

3Device complexity

If a centralized database manages tokens for all remote systems, then token management is simplified, but accessing the database experiences increased latency and delays

Engineering Contradiction:
Improvetoken management complexityVSAvoiddatabase access latency
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent implements a preliminary action by having the centralized token generation service generate and cache tokens before they are needed by remote systems. By pre-generating tokens and maintaining a cache of valid tokens, the system reduces the need for frequent database accesses during token validation, thereby reducing latency and delays while maintaining simplified token management.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250181568A1Framework for the generation of semantic codes
Publication Date: 2025.06.05 ADP INC
  • US20250181568A1 patent drawing
  • US20250181568A1 patent drawing
  • US20250181568A1 patent drawing

AI summary

Aspects of the technical solution can provide a framework to generate a token data structure to reduce the amount of storage within a database, managing applications associated with at least one remote server. The framework can allow for the token data structure to include a plurality of individual tokens to represent aspects of the application associated with the at least one remote server. When a data processing system receives a request to generate the token data structure for an application, the data processing system can generate the token data structure according to mappings within a token library to define a framework for each token within the token data structure. Once generated, a validation function can traverse the database to verify uniqueness of the generated token data structure. The token data structure is unique when the database does not include a token data structure.