Originator Preference Tracking for Document Integrity

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Network computer systems face challenges in controlling the transfer and processing of documents to ensure they reach intended recipients only, as existing solutions either rely on strong cryptography that can be tampered with or impose restrictions post-creation, lacking user-specific originator preferences for document management.

Innovation Solution

A method and system that store user-specific originator preferences in a database, allowing access to data only if the processing request from any user is consistent with these preferences, using digests to identify and verify the document's integrity and compliance with set rules, ensuring that documents are processed according to the originator's intentions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If strong cryptography is used to embed protection data within the document, then the document cannot be tampered with, but the system complexity increases and the protection can still be bypassed by copying text

Engineering Contradiction:

Improvedocument protectionVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The protection system is segmented into two independent parts: the document content and the protection metadata. The protection data is stored separately in a database rather than being embedded within the document, allowing the document to remain simple and unmodified while maintaining protection through external verification

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A server acts as an intermediary between the document and the protection verification process. The server stores protection data, receives processing requests, verifies permissions, and returns authorization decisions, eliminating the need for complex cryptography within the document itself

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If protection data is embedded within the document data, then the document can be protected from tampering, but the protection data can potentially be tampered with by the recipient

Engineering Contradiction:

Improveprotection data integrityVSAvoidtampering risk

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The protection data is extracted from the document and stored separately in a secure database. This separation ensures that recipients cannot tamper with the protection data by modifying the document, as the protection information resides independently in a controlled environment

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements a feedback mechanism where processing requests are sent to the server for verification. The server checks the request against stored protection data and returns an authorization decision, ensuring that any attempt to bypass protection is detected and prevented

Inventive Principle:

Principle #23Feedback

3Reliability

If restrictions are imposed on user ability to process files, then unauthorized distribution is limited, but the restrictions are not set by originators of the files

Engineering Contradiction:

Improvedistribution controlVSAvoiduser autonomy

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

Originators set processing restrictions and permissions in advance when creating or uploading documents. These preferences are stored with the protection metadata, allowing automated enforcement without requiring user intervention or judgment at the time of processing

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system enables originators to self-configure protection settings according to their needs. Users can define custom preferences for document processing, sharing, and distribution control, and these settings are automatically applied without requiring administrative intervention

Inventive Principle:

Principle #25Self-service

4Reliability

If anti-virus programs impose limits on user ability to process files, then virus detection is achieved, but the limits are imposed subsequently rather than by file originators

Engineering Contradiction:

Improvefile securityVSAvoidprocessing delay

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Security preferences and processing restrictions are established in advance by document originators, eliminating the need for subsequent security checks. The server verifies requests against pre-configured preferences, allowing rapid authorization decisions without time-consuming virus scanning or administrative intervention

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9002909B2Tracking marked documents

Publication Date: 2015.04.07 CLEARSWIFT

AI summary

When data is stored on a computer, or subsequently, originator preferences relating to the data are stored in a database, for example in a network. When another user subsequently makes a request for processing of the received data, or a modified copy of the data, it is determined whether the requested processing is consistent with any stored originator preferences, and the requested processing is permitted only if it is consistent with the stored originator preferences. The preferences may relate to saving, copying or retransmitting the data. The originator may be notified of any processing operations that are carried out.