Derivative works — US Patent 7383209

Defensive Disclosure Document for U.S. Patent 7,383,209

Publication Date: April 26, 2026
Subject Matter: Derivative works and extensions of the system and method for automatic access of a remote computer over a network, as described in U.S. Patent 7,383,209. The core concept involves reading an index from a data carrier, using the index to look up a corresponding pointer from one or more remote routing computers, and using the pointer to access an information computer.

Axis 1: Material & Component Substitution

Derivative 1.1: Spectrographic Indexing System for High-Security Authentication

Enabling Description: This variation replaces the conventional barcode with a chemical data carrier possessing a unique spectrographic signature. An object is coated or infused with a transparent polymer containing a precise, non-replicable combination of inert dyes or quantum dots. These markers are invisible to the naked eye but have distinct absorption or emission peaks in non-visible spectra (e.g., near-infrared or Raman spectroscopy). The computer input device is a handheld spectrometer that illuminates the coating with a specific wavelength and captures the spectral response. This analog response is digitized and converted into a hash, which serves as the index. This index is sent to a routing computer which maps the hash to a pointer (e.g., a URL for an authentication record). This method provides a higher level of security than a visually-reproducible barcode, making it suitable for authenticating high-value goods or currency.

Mermaid.js Diagram:

flowchart TD
    A[Object with Spectrographic Coating] --> B{Handheld Spectrometer};
    B -- Laser Illumination --> A;
    B -- Captures Spectral Signature --> C[Requesting Computer];
    C -- Generates Hash (Index) --> D[Transmit Index];
    D --> E[Routing Computer];
    E -- Lookup Hash in Table --> F[Return Pointer];
    F --> C;
    C -- Use Pointer to Access --> G[Information Computer - Authentication Record];

Derivative 1.2: Biological and DNA-based Indexing for Organic Provenance

Enabling Description: This embodiment uses a synthetic, inert DNA sequence as the index. The data carrier is a small amount of this DNA encapsulated in a durable medium (e.g., silica particles) and applied to an object, such as an organic food item or a piece of timber. The computer input device is a portable, rapid DNA sequencing unit (e.g., a nanopore-based sequencer). A sample is taken from the object, and the device sequences the DNA barcode. The resulting base-pair sequence ('ATCG...') is the index. This index is transmitted to a routing computer, which maintains a table mapping these unique DNA sequences to pointers. The pointer could lead to an information computer containing the full provenance data for the item, such as the farm of origin, genetic lineage, and date of harvest, stored on a secure server.

Mermaid.js Diagram:

sequenceDiagram
    participant User
    participant Sequencer as Portable DNA Sequencer
    participant Phone as Requesting Computer
    participant Router as Routing Computer
    participant Server as Information Computer

    User->>+Sequencer: Collect sample and initiate scan
    Sequencer->>-Phone: Transmit DNA Sequence (Index)
    Phone->>+Router: Query with DNA Index
    Router->>-Phone: Return URL (Pointer)
    Phone->>+Server: Request URL
    Server->>-Phone: Return Provenance Data

Derivative 1.3: Decentralized Lookup via a Distributed Ledger

Enabling Description: This variation replaces the centralized routing computer with a decentralized network of nodes operating a distributed ledger (e.g., a permissioned blockchain). The table of index-to-pointer mappings is stored as an immutable set of records on this ledger. When a requesting computer reads an index (e.g., a standard QR code), it submits a transaction query to a smart contract on the network. The smart contract performs the lookup function, retrieving the associated pointer from the ledger's state. This decentralization prevents censorship and eliminates single points of failure. The pointer itself could be a content identifier (CID) for a resource stored on a decentralized file system like IPFS, which would serve as the information computer.

Mermaid.js Diagram:

flowchart TD
    subgraph Requesting Client
        A[Scan Index] --> B[Submit Query to Smart Contract];
    end
    subgraph Distributed Ledger Network
        C[Node 1]
        D[Node 2]
        E[Node N]
    end
    B --> C;
    B --> D;
    B --> E;
    C -- Execute Lookup --> F[(Distributed Table)];
    F -- Pointer --> B;
    B --> G{Use Pointer (e.g., IPFS CID)};
    G --> H[Access Decentralized Information];

Axis 2: Operational Parameter Expansion

Derivative 2.1: Nanoscale Molecular Indexing for LIMS

Enabling Description: This system operates at the molecular scale to identify individual nanoparticles or macromolecules. The data carrier is the molecule itself, which is designed with a specific geometric or electronic feature. The computer input device is a high-resolution imaging tool like an Atomic Force Microscope (AFM) or a Scanning Tunneling Microscope (STM). The microscope scans the molecule and produces a signature (e.g., a topographic map or a current-voltage curve) that serves as the index. This complex signature is transmitted to a Laboratory Information Management System (LIMS) acting as the routing computer. The LIMS table maps the unique molecular signature to a pointer that links to the molecule's entry in a database, containing its synthesis protocol and experimental data (information computer).

Mermaid.js Diagram:

stateDiagram-v2
    [*] --> Scanning
    Scanning: AFM scans molecule
    Scanning --> Processing: Raw topographical data
    Processing: Generate unique signature (Index)
    Processing --> Querying: Transmit Index to LIMS
    Querying --> Retrieving: LIMS returns pointer
    Retrieving --> Display: Access data via pointer
    Display --> [*]

Derivative 2.2: Industrial Process Control in Extreme Environments

Enabling Description: This embodiment is designed for high-temperature industrial environments, such as a steel foundry. An ingot (data carrier) is engraved with a robust 2D matrix code (index) capable of being read while the metal is incandescent. A specially-shielded, high-dynamic-range camera (computer input device) captures an image of the code from a distance. Image processing software on a requesting computer decodes the index and transmits it to a Manufacturing Execution System (MES), which acts as the routing computer. The MES table maps the ingot's ID to a pointer. In this application, the pointer is a process control command or an API endpoint, not a URL. The system uses this pointer to instruct the next machine in the production line (e.g., a rolling mill, which functions as the information computer) to apply a specific set of operational parameters.

Mermaid.js Diagram:

sequenceDiagram
    participant Ingot
    participant Camera
    participant MES as Routing Computer
    participant Mill as Information Computer

    Camera->>MES: Transmit Ingot ID (Index)
    MES->>MES: Lookup Process Parameters
    MES->>Mill: Send Control Command (Pointer)
    Mill->>Ingot: Apply specific rolling process

Axis 3: Cross-Domain Application

Derivative 3.1: Aerospace - Digital Twin and Maintenance Log Access

Enabling Description: In the aerospace industry, every critical aircraft component (e.g., a landing gear strut) is permanently marked with a unique Data Matrix code (index). A maintenance technician uses a handheld scanner (computer input device) to read this code. The requesting computer (a ruggedized tablet) sends the component's serial number (index) to the airline's Product Lifecycle Management (PLM) system (routing computer). The PLM database (table) links the serial number to a pointer for the component's Digital Twin. This pointer directs the tablet to retrieve a comprehensive data package from a server (information computer), including its 3D model, full maintenance history, flight hours, and material certifications.

Mermaid.js Diagram:

flowchart TD
    A[Scan Component's Data Matrix Code] --> B[Tablet sends Serial Number (Index)];
    B --> C[PLM System (Routing Computer)];
    C -- Looks up Index in Database --> D[Finds Pointer to Digital Twin];
    D --> B;
    B -- Uses Pointer to Request Data --> E[Digital Twin Server (Information Computer)];
    E -- Returns 3D Model, Maint. History, etc. --> B;
    B --> F[Display Full Component Data to Technician];

Derivative 3.2: AgTech - Livestock Health and Provenance Tracking

Enabling Description: This application tracks individual animals in a herd. Each animal is equipped with an RFID ear tag (data carrier) containing a unique ID (index). RFID readers (computer input devices) installed at feeding stations or weigh-in scales automatically capture the index as the animal passes. The index is sent to a cloud-based farm management platform (routing computer). The platform's database (table) maps the animal's ID to a pointer to its individual, dynamic health record hosted on a web server (information computer). This allows for automated tracking of food intake, weight gain, and health treatments, creating a complete and verifiable history for each animal.

Mermaid.js Diagram:

erDiagram
    ANIMAL ||--o{ RFID_TAG : has
    ANIMAL {
        string AnimalID PK
        date DateOfBirth
        string Breed
    }
    RFID_TAG {
        string Index PK
        string AnimalID FK
    }
    ANIMAL ||--|{ HEALTH_RECORD : "maintains"
    HEALTH_RECORD {
        string RecordID PK
        string AnimalID FK
        date TreatmentDate
        string Notes
    }

Derivative 3.3: Consumer Electronics - Dynamic Warranty & Support Portal

Enabling Description: A unique QR code (index) containing the device serial number is placed on a consumer electronic product, such as a router. When a user scans the code with their smartphone (requesting computer), an app sends the index to the manufacturer's customer relationship management (CRM) system (routing computer). The CRM table cross-references the serial number with sales and registration data to determine the product's exact model, warranty status, and geographical region. It then dynamically generates a pointer (a unique URL) that directs the user to a personalized support microsite (information computer). This site is pre-populated with the user's device information and displays relevant FAQs, firmware downloads, and localized contact information.

Mermaid.js Diagram:

sequenceDiagram
    participant User
    participant Smartphone
    participant CRM as Routing Computer
    participant WebServer as Information Computer

    User->>Smartphone: Scan QR Code on Router
    Smartphone->>+CRM: Send Serial Number (Index)
    CRM->>CRM: Lookup device info, warranty, region
    CRM->>-Smartphone: Return dynamically-generated URL (Pointer)
    Smartphone->>+WebServer: Request personalized URL
    WebServer->>-Smartphone: Display tailored support page

Axis 4: Integration with Emerging Technologies

Derivative 4.1: AI-Optimized Contextual Pointer Resolution

Enabling Description: This derivative enhances the routing computer with an AI-driven decision engine. When a user scans a product's UPC code (index), the requesting computer also sends a payload of contextual data (e.g., user's location, time, declared dietary preferences from a profile). The routing computer feeds the index and context into a machine learning model. Instead of a static table, the model predicts the user's intent and generates the most relevant pointer. For a user with a gluten allergy scanning a loaf of bread, the pointer may lead to an allergen information page. For another user scanning the same code, it might point to a recipe. This creates a dynamic, personalized user experience.

Mermaid.js Diagram:

flowchart TD
    A[Scan UPC (Index)] --> B{Package Index + User Context};
    B --> C[AI Routing Engine];
    C -- ML Model Prediction --> D{Generate Contextual Pointer};
    subgraph "Possible Pointers"
        D1[Recipe Page]
        D2[Allergen Info]
        D3[Promotional Offer]
    end
    D -- "User A" --> D1;
    D -- "User B" --> D2;
    D -- "User C" --> D3;

Derivative 4.2: IoT-Enabled Real-Time System Control

Enabling Description: In a smart factory setting, a technician scans a QR code (index) on a machine. A tablet (requesting computer) sends the machine's ID to an IoT control platform (routing computer). The platform's table resolves the ID to a pointer that is an MQTT topic string or a secure API endpoint for the machine's embedded Programmable Logic Controller (PLC), which acts as the information computer. The tablet then uses this pointer to establish a direct communication channel, subscribing to real-time telemetry data (e.g., factory/machine/123/temp) and enabling the technician to send control commands (e.g., publish a message to factory/machine/123/control) to the machine.

Mermaid.js Diagram:

sequenceDiagram
    actor Technician
    participant Tablet
    participant IoT_Platform as Routing Computer
    participant PLC as Information Computer

    Technician->>Tablet: Scans machine QR code (Index)
    Tablet->>+IoT_Platform: Request pointer for Index
    IoT_Platform->>-Tablet: Return MQTT Topic (Pointer)
    Tablet->>PLC: Subscribe to MQTT Topic
    PLC-->>Tablet: Stream real-time telemetry
    Technician->>Tablet: Initiate diagnostic command
    Tablet->>PLC: Publish command to MQTT Topic

Derivative 4.3: Blockchain-Verified Authenticity and Provenance

Enabling Description: A luxury item is equipped with a secure NFC chip (data carrier) whose public key is the index. A consumer uses their smartphone (requesting computer) to read the index. The phone sends the index to a blockchain oracle (routing computer). The oracle queries a supply chain blockchain (table) for records associated with that public key. The oracle verifies the item's manufacturing and ownership history and returns a pointer to a web-based blockchain explorer. This explorer page (information computer) displays the immutable, verifiable transaction history of the item, proving its authenticity from the point of origin.

Mermaid.js Diagram:

flowchart TD
    A[Tap phone to NFC chip on item] --> B[Phone reads Public Key (Index)];
    B --> C[Blockchain Oracle (Routing Computer)];
    C -- Query Ledger --> D[(Supply Chain Blockchain)];
    D -- Transaction History --> C;
    C -- Return URL (Pointer) --> B;
    B -- Access URL --> E[Blockchain Explorer (Information Computer)];
    E --> F[Display immutable provenance record];

Axis 5: The "Inverse" or Failure Mode

Derivative 5.1: "Inverse" - On-Demand Physical Index Generation

Enabling Description: This describes the inverse operation. A user provides a pointer (e.g., a URL to a cloud document) to a web service (routing computer). This service generates a new, unique index (e.g., a short alphanumeric code), stores the association in its database (table), and then commands an output device (e.g., a 2D barcode printer or an engraving laser) to create a physical data carrier modulated with the new index. This physical token can then be applied to an object, effectively creating a durable, real-world link to the digital resource that was initially provided.

Mermaid.js Diagram:

flowchart TD
    A[User provides Pointer (URL)] --> B[Routing Service];
    B -- 1. Generate new Index --> C[(Database)];
    B -- 2. Store (Index, Pointer) association --> C;
    B -- 3. Send Index to Output Device --> D[Barcode Printer / Engraver];
    D --> E[Generate Physical Data Carrier];

Derivative 5.2: Graceful Degradation with Local Fallback Cache

Enabling Description: This system is designed for network-denied environments. A requesting computer (e.g., a medic's tablet) is pre-loaded with an encrypted, local table containing a subset of critical information. When the user scans a medical kit's barcode (index), the device first attempts to contact the main server (routing computer). If the connection fails, it enters a limited-functionality mode. It performs a lookup on its local table to find a pointer. This pointer does not lead to a network resource, but to a file (e.g., a PDF of emergency instructions) stored in its own local memory (local information computer). This ensures core functionality is always available, even when the network is not.

Mermaid.js Diagram:

stateDiagram-v2
    state "Online Mode" as Online
    state "Offline Mode" as Offline

    [*] --> Online: Network available
    Online --> Online: Scan Index -> Query Remote Router
    Online --> Offline: Network connection lost

    Offline --> Offline: Scan Index -> Query Local Cache
    Offline --> Online: Network connection restored

Combination Prior Art Scenarios

Combination with GS1 Digital Link Standard: The claimed method is implemented as a component of the open GS1 Digital Link standard. A device reads a GTIN (index) from a product, constructs a URL according to the GS1 URI syntax (e.g., https://id.gs1.org/gtin/0123...), and sends it to a GS1 resolver (routing computer). The resolver, following the open standard, issues an HTTP redirect (pointer) to the brand-owner's specified product information page (information computer).
Combination with W3C Verifiable Credentials: The method is applied to the open W3C Verifiable Credentials data model for identity verification. A QR code on an ID card (data carrier) contains a Decentralized Identifier or DID (index). A scanner app (requesting computer) reads the DID, uses an open DID method to find a service endpoint in a DID Document, and queries that endpoint (routing computer) for a credential. The pointer returned is a cryptographically-signed Verifiable Credential (information) which the app can then verify.
Combination with MQTT (ISO/IEC 20922): The method is used for device provisioning in an IoT system based on the open MQTT protocol. A gateway (requesting computer) scans a barcode (index) on a new sensor. It uses this index to query a local DNS-SD service (routing computer) to discover the correct MQTT topic string (pointer) for that device. The gateway then uses this pointer to subscribe to the sensor's data stream via an MQTT broker (information computer), establishing communication according to the open standard.