Replication Tag Routing for Policy-Compliant Cloud Data Streaming

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud computing environments face challenges in efficiently replicating datasets across different partitions while ensuring compliance with predefined replication policies, leading to potential unauthorized replication and data security issues.

Innovation Solution

The implementation of replication tags that associate datasets with specific destinations, allowing or denying replication requests based on destination keys, and verifying replication credentials to enforce replication policies, thereby controlling dataset replication within defined partitions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If datasets are replicated to multiple partitions without verification, then data distribution speed is improved, but data security and policy compliance deteriorate

Engineering Contradiction:
Improvedata distribution speedVSAvoiddata security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary verification of replication tags against replication credentials before allowing data replication to occur. This advance check ensures that only authorized destinations receive replicated datasets, preventing unauthorized replication while maintaining efficient data distribution to approved partitions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces replication tags as intermediary verification elements that mediate between the data replication process and security policies. These tags contain destination information that is verified against credentials, acting as a intermediary layer that enables secure replication without compromising speed.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Manufacturing precision

If replication verification is performed for each dataset, then data integrity is improved, but processing time increases

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system uses replication tags as lightweight copies or representations of the actual data that can be verified quickly. Instead of verifying the entire dataset, the system verifies the associated replication tag which contains the essential destination information, significantly reducing verification time while maintaining data integrity.

Inventive Principle:
Principle #26Copying

3Reliability

If unauthorized replication is prevented through verification, then security compliance is improved, but system complexity increases

Engineering Contradiction:
Improvesecurity complianceVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the security verification process into distinct components: replication tags associated with datasets, replication credentials stored separately, and a verification mechanism that matches them. This segmentation allows for modular implementation and maintenance of security policies without overwhelming system complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12632466B2Utilizing replication tags associated with messages to determine destinations for streaming the messages
Publication Date: 2026.05.19 ORACLE INT CORP
  • US12632466B2 patent drawing
  • US12632466B2 patent drawing
  • US12632466B2 patent drawing

AI summary

A system receives a message that includes a change event associated with a source dataset for replication to a destination in a cloud environment. The system accesses a replication tag associated with the message. The replication tag includes a tag element that is mapped a destination key that identifies a destination dataset, corresponding to the destination, where the change event is to be replicated. The system determines that the tag element of the replication tag is mapped to the destination key. Responsive to determining that the tag element is mapped to the destination key, the system directs the message to the destination to replicate the change event to the destination dataset.