Patent 5841978
Derivative works
Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.
Active provider: Google · gemini-2.5-pro
Derivative works
Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.
Defensive Disclosure of Derivative Inventions
Publication Date: April 30, 2026
Subject Matter: Network Linking Method Using Steganographically Embedded Data Objects and Derivatives Thereof
Reference: U.S. Patent 5,841,978 (Rhoads, expired)
This document serves as a defensive publication of technical concepts that build upon, extend, or otherwise derive from the core teachings of U.S. Patent 5,841,978. The purpose is to place these concepts into the public domain, thereby establishing them as prior art to preclude future patenting of these or obvious variations thereof by any party.
Derivative Set 1: Variations on Claim 10 (Method of Encoding)
The core claim describes steganographically embedding a network address into a source data object. The following derivatives expand upon this method.
1.1. Material & Component Substitution: Multi-Layered & Spectrally-Dependent Steganography
Enabling Description: This method utilizes specialized multi-layered substrates or materials where each layer is responsive to a different, narrow band of the electromagnetic spectrum. A network address is decomposed into N parts, and each part is steganographically encoded into a separate layer of a physical object (e.g., a laminated card, polymer film, or composite material). The encoding is performed not by modulating luminance, but by altering the substrate's refractive index or polarization response at specific, non-visible wavelengths (e.g., near-infrared or ultraviolet). A multi-spectral imaging sensor, equipped with corresponding narrow-band filters and emitters, is required to read the complete address by sequentially or simultaneously imaging each layer. This method is resistant to conventional scanning and photography, which typically operate only in the visible spectrum. The embedding can be achieved using femtosecond laser etching within a transparent polymer block or via chemical doping of layered adhesives.
Mermaid.js Diagram:
graph TD A[Network Address] --> B{Address Decomposition}; B --> C1[Part 1 -> UV Layer]; B --> C2[Part 2 -> Blue Layer]; B --> C3[Part 3 -> IR Layer]; subgraph "Physical Object" C1 -- Steganographic Encoding (Polarization) --> D1[Layer 1: UV-Sensitive Polymer]; C2 -- Steganographic Encoding (Refractive Index) --> D2[Layer 2: Visible-Spectrum Polymer]; C3 -- Steganographic Encoding (Thermal Signature) --> D3[Layer 3: IR-Sensitive Polymer]; end subgraph "Decoding Device" E[Multi-Spectral Imager] -- Reads --> D1; E -- Reads --> D2; E -- Reads --> D3; end E --> F{Address Reconstruction}; F --> G[Initiate Network Link];
1.2. Operational Parameter Expansion: High-Frequency Transactional Watermarking
Enabling Description: In high-frequency data streams, such as financial market data feeds or live video broadcasts (e.g., 4K at 120 fps), a static embedded address is insufficient. This method embeds a dynamically changing, time-sensitive network address or transaction token. The address is encoded into the least significant bits of data packets at a massive scale (terabytes per hour). The steganographic key used for encoding is synchronized between the server and client via a time-based one-time password (TOTP) algorithm. For example, a base URL is embedded, but a path or parameter in the URL is updated every 100 milliseconds based on the hash of the data packet's timestamp and a shared secret. A client application, synchronized via Network Time Protocol (NTP), can decode the specific address valid only for that micro-moment, enabling applications like time-sensitive coupon redemption or secure, ephemeral access to a data stream.
Mermaid.js Diagram:
sequenceDiagram participant Server participant DataStream participant Client loop Every 100ms Server->>Server: Generate TOTP token Server->>DataStream: Embed URL + TOTP into packets DataStream-->>Client: Transmit watermarked data Client->>Client: Generate matching TOTP token Client->>Client: Decode URL from data packets Client->>Server: Access dynamic URL (link is valid) end
1.3. Cross-Domain Application: Aerospace Component Lifecycle Management
Enabling Description: This method is applied to the manufacturing and maintenance of aerospace components. During fabrication, a unique identifier and a network address pointing to the component's digital twin (a comprehensive CAD model with manufacturing and stress-test data) are steganographically embedded into the component's surface coating using laser-induced micro-pitting. The pattern is imperceptible and follows the component's surface curvature. Maintenance crews using a specialized portable profilometer or a high-resolution optical scanner can read the embedded URL. This link directs them to the component's specific online manual, service history, and stress analysis data, eliminating the need for manual serial number lookups and reducing the risk of using incorrect documentation. The data can be embedded in non-critical structural areas or within layers of composite materials.
Mermaid.js Diagram:
flowchart LR A[Component Digital Twin URL] --> B{Laser Micro-Pitting Encoder}; B --> C(Aerospace Component); D[Portable Profilometer] -- Scans Surface --> C; D --> E{Decode URL}; E --> F[Access Secure Server]; F --> G[Display Maintenance History & Specs];
1.4. Integration with Emerging Tech: AI-Generated, Context-Aware Watermarks
Enabling Description: This system integrates a generative adversarial network (GAN) to create optimized steganographic noise patterns. Instead of using a static pseudo-random noise signal, a trained AI analyzes the host image or audio file in real-time. The GAN's generator network proposes an embedding pattern (the "noise") that is specifically designed to be minimally perceptible given the frequency, texture, and psychovisual/psychoacoustic properties of that specific content. The discriminator network attempts to detect the pattern. This process iterates until a maximally robust yet imperceptible pattern is created. The resulting pattern, which encodes the network address, is thus unique to each piece of content. This makes the watermark more resilient to compression artifacts and targeted attacks, as there is no universal pattern to reverse-engineer.
Mermaid.js Diagram:
graph TD subgraph "Embedding System" A[Source Image/Audio] --> B[AI Feature Analysis]; C[Network Address] --> D{Embedding Algorithm}; B --> D; E[GAN Generator] -- Proposes Pattern --> D; D -- Embeds --> F[Encoded Image]; F -- Feeds into --> G[GAN Discriminator]; G -- Feedback --> E; end F --> H[Stored/Transmitted Object];
1.5. The "Inverse" or Failure Mode: Gracefully Degrading Hierarchical Links
Enabling Description: This method encodes multiple network addresses into a single data object using a hierarchical, multi-resolution steganographic scheme. A high-fidelity, complete URL is embedded using a fragile watermarking technique that corrupts easily. A second, more robust but lower-information-density watermark is also embedded, containing a shortened URL or just a root domain. A third, extremely robust watermark contains only a unique object ID. If the object is transmitted perfectly, a decoder extracts the full URL. If the object undergoes slight compression or degradation, the first watermark fails, but the second one is still readable, directing the user to a general company website. If the object is severely degraded (e.g., a thumbnail of an image), only the object ID is readable, which can be used to query a database. This ensures that some form of link or identification survives even significant data loss.
Mermaid.js Diagram:
stateDiagram-v2 state "Full Quality" as Full state "Slight Degradation" as Degraded state "Severe Degradation" as Severe [*] --> Full: Initial State Full --> Degraded: Compression/Noise Degraded --> Severe: Further Data Loss Full: Decode L1 Watermark -> Full URL Full: Decode L2 Watermark -> Root Domain Full: Decode L3 Watermark -> Object ID Degraded: L1 Decode Fails Degraded: Decode L2 Watermark -> Root Domain Degraded: Decode L3 Watermark -> Object ID Severe: L1 Decode Fails Severe: L2 Decode Fails Severe: Decode L3 Watermark -> Object ID
Derivative Set 2: Variations on Claim 5 (Linking from Printed Object)
The core claim describes linking from a printed object by capturing its data with an input device to find an embedded network address.
2.1. Cross-Domain Application: AgTech - Smart Seed and Plant Authentication
Enabling Description: A unique network address pointing to a specific batch's genetic information, optimal growing conditions, and supply chain history is steganographically embedded onto the surface of agricultural seeds or plant tags. The embedding medium is a non-toxic, biodegradable, and FDA-approved edible polymer coating applied during seed treatment. The code is embedded by modulating the micro-topography of this coating. An optical reader, potentially integrated into automated planting equipment or a handheld device for field use, scans the seed or tag. The decoded URL links to a database, allowing a farmer to verify the authenticity of the seeds, receive real-time planting advice, and automatically log the batch into a farm management system.
Mermaid.js Diagram:
graph TD A[Seed Batch Data URL] --> B{Micro-Topography Encoder}; B -- Applies coating --> C[Agricultural Seed]; D[Field Scanner/Planter] -- Scans Seed --> C; D --> E{URL Decode}; E --> F[Access Ag-Database]; F --> G[Display Genetic Info & Planting Guide];
2.2. Integration with Emerging Tech: IoT-Enabled Packaging with Blockchain Verification
Enabling Description: A product package (e.g., for pharmaceuticals or luxury goods) is printed with an image containing a steganographically embedded URL. The package also includes an NFC/BLE IoT sensor that detects when the package is opened. When a user scans the image with a smartphone, the decoded URL is sent to a server. The server first queries the IoT sensor's state via the network. If the package has been previously opened, the URL redirects to a warning page about potential tampering. If unopened, it redirects to the product's authentic verification page. Each scan and its outcome (tampered/untampered) is logged as a transaction on a private blockchain, creating an immutable audit trail for the product's lifecycle from factory to consumer.
Mermaid.js Diagram:
sequenceDiagram actor User participant PhoneApp participant ProductPackage participant VerificationServer participant Blockchain User->>PhoneApp: Scan Image on Package PhoneApp->>PhoneApp: Decode Steganographic URL PhoneApp->>VerificationServer: Request URL VerificationServer->>ProductPackage: Query IoT Sensor State (e.g., via BLE) ProductPackage-->>VerificationServer: Return State (Opened/Sealed) alt State is Sealed VerificationServer->>Blockchain: Log "Verified" Transaction VerificationServer-->>PhoneApp: Redirect to Authentic Product Page else State is Opened VerificationServer->>Blockchain: Log "Tamper Warning" Transaction VerificationServer-->>PhoneApp: Redirect to Tamper Alert Page end
Combination Prior Art Scenarios
These scenarios combine the teachings of US 5,841,978 with existing, open-source standards to create novel systems that are now placed in the public domain.
3.1. Combination with QR Code Standard (ISO/IEC 18004)
- Concept: Redundant and Enhanced Data Linking via Hybrid Encoding.
- Enabling Description: An image contains a standard, visible QR code that links to a primary network address (e.g., a product's main webpage). The same image is also steganographically encoded with a secondary, different network address using the method of Rhoads '978. This secondary address could point to a high-security resource, such as a single-use login token, a direct download link for associated software, or a page with owner-specific information. An application designed to read this hybrid image would first read the QR code for general access. A separate, authenticated function within the same application would then process the full image to decode the steganographic link, providing a two-factor or privileged access route. The steganographic data's presence could be signaled by a specific pattern within the QR code's quiet zone, indicating to a compatible reader that a hidden layer of information exists.
3.2. Combination with the IIIF (International Image Interoperability Framework) Standard
- Concept: Dynamic, View-Specific Linking in Digital Archives.
- Enabling Description: High-resolution images served by a IIIF-compliant server in a museum or library archive are dynamically watermarked on-the-fly. The standard IIIF Image API allows users to request specific regions, sizes, and rotations of an image. When the server generates the requested derivative image, it steganographically embeds a URL unique to that specific request. This URL would point to a metadata record for the exact view the user requested (e.g., "the upper-left quadrant of folio 3, rotated 90 degrees"). If a user saves and shares this specific derivative image, the embedded link always resolves back to the original source and context in the archive, preserving provenance and preventing decontextualized use of cultural heritage objects. The steganographic payload would be the IIIF Image API syntax string that generated that specific view.
3.3. Combination with the WebRTC (Web Real-Time Communication) Open Standard
- Concept: Peer-to-Peer Data Validation via Live Video Steganography.
- Enabling Description: During a live, peer-to-peer video call established using WebRTC, one peer's client application steganographically embeds a checksum or hash of a shared document into the outgoing video stream. The receiving peer's client decodes this hash from the video frames in real-time. It then compares this received hash with a locally computed hash of its own version of the document. This provides a continuous, out-of-band verification that both parties are viewing the identical, unmodified document during the call. The network address embedded is not a URL but a data URI (
data:;base64,...) containing the hash and a timestamp, making the verification self-contained within the media stream and not reliant on an external server. This ensures document integrity during sensitive remote collaborations or contract signings.
Generated 4/30/2026, 5:01:47 AM