Document Label Persistence via Key-Value Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data loss prevention (DLP) systems fail to persist metadata labels across incompatible platforms, applications, and file formats, leading to unauthorized access and resource consumption due to the inability to classify and protect sensitive data.

Innovation Solution

A system that obtains label information and associates it with documents using key-value pairs, writing to file properties or adding as content to ensure persistence across different products, platforms, and applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If metadata labels are used to classify sensitive data in a first computing environment, then data classification and access control are improved, but the metadata does not persist when transferred to another computing environment

Engineering Contradiction:
Improvemetadata persistenceVSAvoidcross-platform compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies universality by creating a label map that translates metadata labels between different computing environments. The label map serves as a universal intermediary that enables metadata persistence across incompatible platforms by mapping source environment labels to target environment labels, allowing the same classification system to function universally across different systems.

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

Solution Approach 2:

The label map acts as an intermediary between the first computing environment and the second computing environment. It mediates the transfer of metadata labels by containing key-value pairs that map labels from the source environment to the target environment, enabling seamless metadata persistence without direct compatibility between the two environments.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If label information is transferred between incompatible applications, then data classification continuity is improved, but system complexity increases due to label mapping requirements

Engineering Contradiction:
Improvelabel information persistenceVSAvoidlabel map management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies copying by creating a label map that contains copies of label information in a structured key-value format. Instead of directly transferring complex label structures between applications, the system creates simplified copies that can be easily mapped and transferred, reducing the complexity of label information persistence while maintaining reliability.

Inventive Principle:
Principle #26Copying

3Reliability

If metadata is embedded in document file properties, then label persistence across applications is improved, but the ability to maintain platform-specific metadata formats is reduced

Engineering Contradiction:
Improvecross-application metadata persistenceVSAvoidplatform-specific format support
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies parameter changes by transforming metadata labels into a standardized key-value pair format that can be embedded in document file properties. This parameter transformation allows labels to be persisted across applications while maintaining the ability to adapt to different platform-specific formats through the flexibility of key-value pairs, which can be customized to match various platform requirements.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12386877B2Automated persistence of label information associated with a document
Publication Date: 2025.08.12 CAPITAL ONE SERVICES LLC
  • US12386877B2 patent drawing
  • US12386877B2 patent drawing
  • US12386877B2 patent drawing

AI summary

In some implementations, a labeling device may determine a label value associated with a label of the document that is associated with a first application. The labeling device may generate a label map that includes an indication of a key-value pair associated with the label value. The labeling device may write, based on the key-value pair associated with the label value, the label value to one or more file properties associated with the document, or may add, based on the key-value pair associated with the label value, the label value as content associated with the document. The label value may persist with the document based on transferring the document from the first application to a second application.