Watermarked Database Tuple Insertion Without Full Untattooing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database watermarking methods require significant processing time and resources to insert new data records, as they necessitate untattooing the entire database, which is cumbersome and inefficient, especially in large databases.

Innovation Solution

A method for inserting new tuples into a watermarked database using pre-stored metadata that identifies how to modify attribute values based on group membership, allowing on-the-fly updates without accessing the original or watermarked data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional database watermarking methods are used to insert new data records, then data security and traceability are maintained, but significant processing time and resources are required due to the need to untattoo the entire database

Engineering Contradiction:
Improvedata securityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The database is divided into multiple groups of tuples, with watermark information embedded at the group level rather than requiring processing of the entire database. This segmentation allows selective operation on specific groups containing new records, dramatically reducing processing time while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Watermark metadata including group identifiers and encoding rules are pre-stored in the database system. This preliminary preparation enables rapid identification and processing of only the necessary tuple groups when new records are inserted, avoiding the need to process the entire watermarked database.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If the entire database is untattooed to insert new records, then data insertion is possible, but the process becomes cumbersome and inefficient especially in large databases

Engineering Contradiction:
Improvedata insertionVSAvoidinsertion efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The database is divided into multiple groups of tuples, with watermark information embedded at the group level rather than requiring processing of the entire database. This segmentation allows selective operation on specific groups containing new records, dramatically reducing processing time while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Watermark metadata acts as an intermediary that stores pre-computed group identifiers and encoding rules. This metadata enables the system to quickly locate and process only the relevant tuple groups without examining or untattooing the entire database, greatly improving insertion efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If complete database removal is performed for security reasons, then security is maintained, but the operation is time-consuming and should be avoided

Engineering Contradiction:
ImprovesecurityVSAvoidoperation speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The database is divided into multiple groups of tuples, with watermark information embedded at the group level rather than requiring processing of the entire database. This segmentation allows selective operation on specific groups containing new records, dramatically reducing processing time while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of removing or processing the entire database, the system performs partial action by operating only on the specific tuple groups that contain new records. This partial processing maintains security requirements while avoiding the excessive time cost of complete database operations.

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If access to original and watermarked data is required for each client update, then watermark integrity is maintained, but the process becomes cumbersome and requires storing very large amounts of data

Engineering Contradiction:
Improvewatermark integrityVSAvoiddata storage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The essential watermark information is extracted and stored as compact metadata including group identifiers and encoding rules. This extracted metadata enables watermark verification and maintenance without requiring access to or storage of the entire original and watermarked data sets, significantly reducing storage requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Watermark metadata acts as an intermediary that stores pre-computed group identifiers and encoding rules. This metadata enables rapid identification and processing of only the relevant tuple groups without examining or untattooing the entire database, greatly improving insertion efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3545448B1Method for inserting in-flight data into a watermarked database and associated device
Publication Date: 2026.01.07 INSTITUT MINES TELECOM TELECOM BRETAGNE
  • EP3545448B1 patent drawingFigure 1~2

AI summary

The present invention provides a method and associated device for inserting tuples into a watermarked database without having to detach all or a part of the database before inserting each tuple. Therefore, the invention consists in storing, in watermark metadata, the type of group or class in which the tuples of the database have been distributed during the watermarking of the database. For each type of group or class, a rule defining a modification of the value of at least one attribute to which the watermarking relates is also stored in the watermark metadata, according to an insertion force parameter. Each tuple to be inserted is watermarked by applying the modification rule according to the group to which the tuple belongs. Due to the rule used, the insertion of the watermarked tuple does not alter the type of group it belongs to.