LOB Data De-duplication via Block Segmentation and Database Mediation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for storing LOB data face challenges such as duplicated storage, inefficient use of disk space, and lack of random access capabilities, as well as the need for secure storage of sensitive information.

Innovation Solution

A system that includes a data receiving module for processing LOB files into blocks, a de-duplication module for identifying and managing duplicate data, a data compression module for reducing storage needs, and a data encryption module for securing sensitive information, allowing for efficient storage and access while minimizing disk space usage and ensuring data security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data compression is used to minimize disk space requirements, then storage efficiency is improved, but random access to LOB data becomes difficult

Engineering Contradiction:
Improvedisk spaceVSAvoidrandom access
Core Design Contradiction:
Quantity of substanceVSEase of operation

Solution Approach 1:

The patent divides LOB data into fixed-size blocks and stores them in a database with individual accessibility. Each block can be independently accessed through database queries, enabling random access to compressed data without decompressing the entire file. This segmentation resolves the contradiction by making compressed data accessible in discrete units.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a database as an intermediary layer between compressed LOB data and access operations. The database stores compressed blocks and provides query interfaces for random access, acting as a mediator that enables both compression and random access capabilities simultaneously.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If LOB data is stored unencrypted on-disk, then storage simplicity is maintained, but data security and compliance requirements are not met

Engineering Contradiction:
Improvestorage simplicityVSAvoiddata security
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent encrypts LOB data in fixed-size blocks rather than as a single unit. Each block can be independently encrypted and managed in the database, maintaining security while allowing selective access and management of data portions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies encryption specifically to LOB data blocks that contain sensitive information, rather than encrypting all data uniformly. This localized approach maintains simplicity for non-sensitive data while ensuring security for sensitive portions.

Inventive Principle:
Principle #3Local quality

3Ease of operation

If duplicate LOB data is stored to maintain data availability, then data accessibility is improved, but storage space is wasted

Engineering Contradiction:
Improvedata accessibilityVSAvoidstorage space
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent uses database references and pointers to represent duplicate LOB data rather than storing actual duplicate copies. Multiple database records can reference the same compressed block, providing data accessibility through references while avoiding physical duplication of storage.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9465823B2System and method for data de-duplication
Publication Date: 2016.10.11 ORACLE INT CORP
  • US9465823B2 patent drawing
  • US9465823B2 patent drawing
  • US9465823B2 patent drawing

AI summary

Disclosed are methods, systems, and computer program products for processing a file which include using a computer system that is programmed for performing a process of receiving the file in response to a request for storing the file, determining whether a database already contains the file, and storing the file in the database if the database does not already contain the file. The process may alternatively include receiving the file in response to a request for storing the file, determining whether a database already contains the file, and storing the file without storing the received file if the database already contains the file. The process may also alternatively include receiving the file in response to a request for storing the file in a database, separating the file into a plurality of portions, and storing the plurality of portions so each of the plurality of portions can be individually accessed.