Server Framework for Selective Column Redaction in Database Storage Format

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current relational database management systems face inefficiencies in data transfer, as they often send all columns of a row to the client, including non-selected columns, which can compromise security and waste network bandwidth, and require significant server processing power.

Innovation Solution

A server framework that determines which columns to process or exclude based on query requirements, using operations to convert, redact, or retain data in the original format, allowing for flexible data transmission in standard or storage format, reducing unnecessary processing and improving security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If all columns of a row are sent to the client in storage format, then network bandwidth is wasted and security is compromised, but server processing power is reduced

Engineering Contradiction:
Improvenetwork bandwidth usageVSAvoidserver processing power
Core Design Contradiction:
Loss of energyVSProductivity

Solution Approach 1:

The patent segments the data transmission process into two distinct formats: storage format (raw rows with all columns) and standard format (processed rows with only selected columns). The system selectively applies segmentation to exclude non-selected columns while maintaining the ability to transmit in either format based on client capability and security requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by allowing different parts of the data (selected columns vs. non-selected columns) to have different treatment. Selected columns are processed and transmitted in standard format, while non-selected columns are excluded or transmitted only in storage format to specific clients, optimizing both bandwidth usage and security on a column-by-column basis.

Inventive Principle:
Principle #3Local quality

2Reliability

If all columns of a row are sent to the client, then security is compromised by exposing sensitive data, but the client receives complete information

Engineering Contradiction:
ImprovesecurityVSAvoiddata completeness
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent extracts and excludes non-selected columns from the data transmission process. By identifying and removing columns that are not required by the client query, the system prevents sensitive information from being exposed while still transmitting all necessary selected columns to the client.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements dynamic data transmission by allowing the format and content of transmitted rows to vary based on client capability, security policies, and query requirements. The system can dynamically switch between storage format and standard format, and selectively include or exclude specific columns based on real-time conditions.

Inventive Principle:
Principle #15Dynamics

3Reliability

If the server processes all rows into standard format, then data security is improved by excluding non-selected columns, but server CPU utilization increases

Engineering Contradiction:
Improvedata securityVSAvoidserver CPU utilization
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by processing only the necessary subset of data (selected columns) into standard format, rather than processing all columns. This allows the server to maintain security for non-selected columns by excluding them entirely, while only investing processing effort in the columns that are actually needed by the client.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent changes the parameter of data format from a fixed standard format to a variable format that can be either storage format or standard format depending on the column. This allows the system to optimize CPU utilization by maintaining storage format for non-selected columns (requiring no processing) while converting only selected columns to standard format.

Inventive Principle:
Principle #35Parameter changes

4Productivity

If the server transfers rows in storage format, then server processing is minimized, but the client must perform extraction and processing operations

Engineering Contradiction:
Improveserver processing efficiencyVSAvoidclient processing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary processing layer that selectively converts selected columns from storage format to standard format while leaving non-selected columns in storage format or excluding them entirely. This intermediary approach balances the processing load between server and client, reducing server CPU utilization compared to full conversion while still providing structured data for selected columns.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11055289B2Framework to transfer rows in storage format, standard format, or combination thereof
Publication Date: 2021.07.06 ORACLE INT CORP
  • US11055289B2 patent drawing
  • US11055289B2 patent drawing
  • US11055289B2 patent drawing

AI summary

A server receives a query and checks how columns in rows responsive to the query are to be sent to a client. Based on one result of checking, the server prepares and transmits a redacted version of one or more rows or portions thereof. The redacted version may be prepared by discarding from the retrieved rows or portions thereof, any columns that are to not be sent, by applying a specific redaction technique, while maintaining columns that are to be sent in a database storage format in which the retrieved rows are stored. Based on another result of checking, the server prepares and transmits a raw version of the retrieved rows or portions thereof, in the database storage format. Based on yet another result of checking, the server extracts columns selected by the query to memory and sends processed versions of the rows or portions thereof.