Kernel-Level Watermark Driver for Consistent Content Protection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing digital rights management systems face limitations in applying watermarks to all views of content, especially in applications like Microsoft Office products, where users can override or remove watermarks, and there is no guarantee that content will be rendered with a watermark during print or display operations.

Innovation Solution

A system that renders watermarks separately from the application rendering the content, using techniques like function hooking to intercept rendering calls and applying watermarks via a transparent window or a watermarking server, ensuring watermarks are applied dynamically and cannot be removed by users, across various types of content including PDFs, word processing documents, and images.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If watermarks are applied through application-level integration (e.g., PDF viewers), then the implementation is simple and compatible with existing applications, but users can override or remove watermarks and there is no guarantee of consistent application across all views

Engineering Contradiction:

Improveease of watermark applicationVSAvoidreliability of watermark application

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent introduces a watermark driver as an intermediary component that operates at the kernel level between the application and the display/printing subsystems. This driver intercepts rendering operations and applies watermarks independently of application-level code, preventing user override while maintaining broad compatibility with existing applications. The intermediary layer ensures reliable watermark application without requiring modifications to application software.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical/application-level approach of watermark insertion with a kernel-level driver approach. Instead of relying on application APIs and user cooperation, the system uses a low-level driver that operates in the kernel space, substituting the higher-level application mechanism with a more fundamental system-level mechanism that cannot be easily bypassed by users.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If watermarks are applied at the kernel level via driver interception, then consistent application across all views is guaranteed, but the system complexity increases significantly

Engineering Contradiction:

Improvereliability of watermark applicationVSAvoidcomplexity of watermarking system

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the watermarking system into distinct functional modules: a kernel-level driver for interception, a watermark generation component, and a rendering module. This segmentation allows each component to perform its specific function independently, managing complexity through modular design while maintaining reliable watermark application across all views.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts the watermark application functionality from the application layer and places it in a separate kernel-level driver. This extraction isolates the complexity of kernel-level interception from application code, allowing the watermarking system to operate reliably without increasing application complexity. The complex driver logic is separated into its own module.

Inventive Principle:

Principle #2Taking out (Extraction)

3Adaptability or versatility

If function hooking is used to intercept rendering calls, then watermarks can be applied to all rendering operations including print and display, but the ease of operation and user control is reduced

Engineering Contradiction:

Improveversatility of watermark applicationVSAvoidease of user control

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The watermark driver acts as an intermediary that sits between the application's rendering calls and the actual rendering output. It intercepts all rendering operations (display, print, etc.) and applies watermarks automatically. This intermediary approach provides versatile watermark application across all output types while removing the need for user intervention or control, as the driver operates autonomously at the system level.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8312552B1Method and system for rendering watermarked content

Publication Date: 2012.11.13 OPEN TEXT CORP

AI summary

Methods and systems for rendering watermarks in a computer system are provided. One technique renders a content unit based on a call from an application, and renders a watermark for the content based on a call from a tool separate from the application. Another technique for rendering a watermark for content displayed on a display screen renders the content via a content window on the display, and renders the watermark via another window on the display that overlays at least a portion of the content window.