Derivative works

As a Senior Patent Strategist and Research Engineer, I have analyzed US Patent 8,805,728 to generate the following Defensive Disclosure. This document details derivative works and technical variations of the core claims to establish prior art, thereby rendering future incremental improvements by competitors obvious or non-novel.

Reference Patent: US 8805728
Title: System and method for using an ordinary article of commerce to access a remote computer
Core Claim (Paraphrased): A user device scans a barcode (index) on a product, sends the index to a remote server, which looks up and returns a pointer (e.g., URL), which the user device then uses to connect directly to a final remote information computer.
Publication Date: April 28, 2026

---

Defensive Disclosure: Derivative Works and Technical Embodiments

1. Material & Component Substitution Derivatives

1.1. Radio-Frequency Index Resolution System

• Enabling Description: This embodiment replaces the optical bar code symbol and scanner with a radio-frequency (RF) subsystem. A passive Near-Field Communication (NFC) Forum Type 4 Tag or an ISO/IEC 18000-6C RFID tag is embedded within the article of commerce or its packaging. This tag is pre-provisioned with a unique identifier which serves as the "index." The user computing device is equipped with an NFC controller or UHF RFID reader, which functions as the "scanner." Upon bringing the device within the RF field of the tag (e.g., <10 cm for NFC), the device energizes the tag and reads the index via inductive coupling. The device's operating system or a dedicated application transmits this index over a TCP/IP network to the remote server computer for pointer resolution, as described in the core method. This method provides an alternative data acquisition layer that is non-optical and does not require line-of-sight.

• Mermaid Diagram:

  sequenceDiagram
      participant UserDevice as User Device (NFC Reader)
      participant RF_Tag as RF Tag (NFC/RFID)
      participant ResolverServer as Remote Resolver Server
      participant InfoServer as Remote Information Server
  
      UserDevice->>+RF_Tag: Energize and Read Index
      RF_Tag-->>-UserDevice: Return Index (e.g., UUID)
      UserDevice->>+ResolverServer: Transmit Index over HTTPS
      ResolverServer->>ResolverServer: Lookup Index in Database
      ResolverServer-->>-UserDevice: Return Pointer (URL)
      UserDevice->>+InfoServer: HTTP GET request using Pointer
      InfoServer-->>-UserDevice: Return Information Resource
  

1.2. Steganographic Index Resolution System

• Enabling Description: This embodiment uses digital watermarking to conceal the index within the graphical artwork or texture of the article of commerce's packaging. A multi-bit index is steganographically encoded into the luminance or chrominance channels of the printed artwork using a robust spread-spectrum encoding algorithm. The "scanner" is a standard smartphone camera, coupled with a software library (e.g., an OpenCV-based module) that performs image registration, geometric distortion correction, and subsequent extraction of the embedded digital watermark (the index). The extracted index is then transmitted to the remote server for pointer resolution. This system eliminates the need for a dedicated, visible barcode, integrating the index invisibly into the product's branding.

• Mermaid Diagram:

  flowchart TD
      A[User Device Captures Image of Product] --> B{Software Decoder};
      B -->|Image Processing & FFT| C[Extracts Hidden Index];
      C --> D[Transmit Index to Resolver Server];
      D --> E{Resolver Server};
      E -->|Lookup in DB| F[Retrieve Pointer];
      F --> G[Return Pointer to User Device];
      G --> H[Device Connects to Information Server];
  

2. Operational Parameter Expansion Derivatives

2.1. High-Throughput Industrial Pointer Resolution System

• Enabling Description: This system operates in a high-speed industrial automation context, such as a pharmaceutical packaging line or logistics sorting facility, processing over 1,000 units per minute. An array of fixed-mount industrial machine vision cameras (the "scanners") are positioned over a conveyor. Each article of commerce features a Data Matrix code (the "index"). As articles pass, the cameras capture images and a local edge-computing gateway performs image processing to decode the indices. These indices are batched and streamed via a high-bandwidth, low-latency protocol (e.g., MQTT over a private 5G network) to a local resolver server. The server returns pointers that are not URLs for human browsing, but rather URIs that resolve to machine-readable data packages, such as quality control parameters, serialization data, or routing instructions for a Programmable Logic Controller (PLC) that controls downstream robotic sorters.

• Mermaid Diagram:

  stateDiagram-v2
      [*] --> Scanning
      Scanning --> Processing: Item detected
      state Scanning {
          direction LR
          Camera1: Reads Index_A
          Camera2: Reads Index_B
          Camera3: Reads Index_C
      }
      Processing --> Resolving: Batch of indices ready
      state Resolving {
          EdgeGateway --> ResolverServer: Transmit [Index_A, Index_B, Index_C]
          ResolverServer --> EdgeGateway: Return [Pointer_A, Pointer_B, Pointer_C]
      }
      Resolving --> Action: Pointers received
      state Action {
          direction LR
          PLC_A: Uses Pointer_A to fetch routing data
          PLC_B: Uses Pointer_B to update QA log
          PLC_C: Uses Pointer_C to direct robotic arm
      }
      Action --> [*]
  

3. Cross-Domain Application Derivatives

3.1. Aerospace Component Digital Passport System

• Enabling Description: This system is applied to aerospace component lifecycle management. Every critical component (e.g., a turbine blade, an actuator) is permanently marked with a laser-etched Data Matrix code per ATA Spec 2000, which serves as its unique index. During a maintenance check, an engineer uses a ruggedized tablet ("user computing device") to scan the index. The tablet transmits the index over a secure network to a resolver server managed by the component OEM. The server validates the request and returns a temporary, single-use, cryptographically signed pointer (e.g., a JSON Web Token-based URL). The tablet's maintenance software uses this pointer to establish a direct, authenticated TLS connection to the component's specific "Digital Passport" server, which serves its complete, non-repudiable history including manufacturing data, flight hours, stress telemetry, and maintenance records.

• Mermaid Diagram:

  sequenceDiagram
      participant EngineerTablet as Ruggedized Tablet
      participant ResolverOEM as OEM Resolver Server
      participant DigitalPassport as Component Info Server
  
      EngineerTablet->>+ResolverOEM: Transmit Component Index
      ResolverOEM->>ResolverOEM: Verify Credentials & Lookup
      ResolverOEM-->>-EngineerTablet: Return Signed Pointer (JWT-URL)
      EngineerTablet->>+DigitalPassport: Connect using Signed Pointer
      DigitalPassport->>DigitalPassport: Validate JWT Signature
      DigitalPassport-->>-EngineerTablet: Stream Component Lifecycle Data
  

4. Integration with Emerging Technology Derivatives

4.1. AI-Powered Contextual Pointer System

• Enabling Description: This embodiment integrates AI for a more dynamic interaction. The user device does not scan a barcode. Instead, it captures an image or video of the article of commerce. A lightweight, on-device Convolutional Neural Network (CNN) performs object recognition to generate a probabilistic feature vector that acts as a "soft index." This soft index is transmitted to the remote resolver server along with contextual metadata from the device's IoT sensors (e.g., GPS coordinates, timestamp, accelerometer data). The server uses a larger machine learning model to interpret this combined input. For example, if a food item's soft index is received with a timestamp of 6 PM from a residential location, the model returns a pointer to an interactive cooking recipe. If the same soft index is received from a retail store location, the pointer resolves to a price comparison engine or a product recall notice.

• Mermaid Diagram:

  flowchart TD
      subgraph UserDevice
          A[Capture Image] --> B[On-Device CNN];
          B --> C[Generate Soft Index];
          D[Read IoT Sensors] --> E[Collect Context Metadata];
      end
      subgraph ResolverServer
          F[Receive Soft Index & Metadata] --> G{Contextual AI Model};
          G -->|Is location=home, time=evening?| H[Select "Recipe" Pointer];
          G -->|Is location=retail?| I[Select "Recall/Price" Pointer];
          H --> J[Return Pointer];
          I --> J;
      end
      UserDevice --> F;
      J --> UserDevice;
  

4.2. Blockchain-Verified Provenance System

• Enabling Description: This system leverages a distributed ledger for supply chain verification. The barcode on an article of commerce (e.g., a bottle of wine, a luxury handbag) encodes an index that corresponds to a unique digital asset (e.g., an NFT) on a public blockchain (e.g., Ethereum). When scanned, the index is sent to a resolver server that functions as a blockchain oracle. The server queries the blockchain's smart contract for the token URI associated with the index. The returned "pointer" is not a standard HTTPS URL but a content-addressed URI for a resource stored on the InterPlanetary File System (IPFS), such as ipfs://<hash>. The user device, using an IPFS-aware client, connects directly to the peer-to-peer IPFS network to retrieve and display the immutable provenance record for that specific item, which may include sourcing details, ownership history, and authenticity certificates.

• Mermaid Diagram:

  sequenceDiagram
      participant UserDevice
      participant OracleServer as Resolver Server (Oracle)
      participant Blockchain as Smart Contract
      participant IPFS_Network as IPFS (P2P Network)
  
      UserDevice->>UserDevice: Scan QR Code (Index)
      UserDevice->>+OracleServer: Transmit Index
      OracleServer->>+Blockchain: Query Smart Contract for Token URI (Pointer)
      Blockchain-->>-OracleServer: Return Pointer (ipfs://...)
      OracleServer-->>-UserDevice: Return Pointer
      UserDevice->>+IPFS_Network: Request Content from Pointer Hash
      IPFS_Network-->>-UserDevice: Return Immutable Provenance File
  

5. "Inverse" or Failure Mode Derivatives

5.1. System with Graceful Degradation via Dual-Mode Index

• Enabling Description: This embodiment is designed for high-reliability applications where information access is critical, even during network outages. The "barcode symbol" (e.g., a QR code) is structured to encode a composite payload containing both a primary index (e.g., a UUID) for the standard online lookup, and a secondary, self-contained fallback pointer. This fallback pointer is a highly compressed, data-efficient representation of critical information, such as a Base64-encoded Protobuf message containing emergency contact numbers or first-aid instructions. The user device first attempts the standard resolution process with the primary index. If the remote resolver server is unreachable (e.g., due to a network timeout), the application logic automatically triggers a local decoder for the secondary fallback pointer and displays the essential offline information to the user without requiring any network connectivity.

• Mermaid Diagram:

  graph TD
      A[Scan Dual-Mode Barcode] --> B{Extract Primary Index & Fallback Pointer};
      B --> C[Attempt to Transmit Primary Index to Server];
      C --> D{Network Connection Successful?};
      D -- Yes --> E[Receive Pointer from Server];
      E --> F[Connect to Information Server];
      D -- No --> G[Decode Fallback Pointer Locally];
      G --> H[Display Critical Offline Information];
  

---

Combination Prior Art Scenarios

1. Combination with GS1 Digital Link Standard: The system uses a QR code encoding a GS1 Digital Link URI (e.g., https://brand.com/gtin/01234567890128). A specialized application on the user device intercepts this scan. Instead of navigating directly, it parses the GTIN (01234567890128) from the URI and transmits it as the "index" to a separate remote resolver server as described in patent 8805728. This server returns a pointer to a context-specific resource (e.g., an augmented reality product visualization), providing enhanced functionality beyond the generic webpage that the GS1 standard would typically resolve to.

2. Combination with W3C Verifiable Credentials Standard: Upon receiving the scanned product index, the remote resolver server returns a "pointer" that is a URI. When the user device accesses this URI, the information server doesn't return a webpage but instead initiates a credential issuance flow. It returns a cryptographically signed W3C Verifiable Credential in JSON-LD format, attesting to the product's authenticity or a specific attribute (e.g., "Certified Organic"). The user's device, acting as a digital wallet, receives and verifies this credential, providing a trusted claim rather than just information.

3. Combination with the Matter IoT Standard: A user scans a QR code on a new smart light bulb. The index from the QR code is sent to the manufacturer's resolver server. This server's database links the product index to the device's unique Matter onboarding credentials. The server returns these credentials formatted as a "pointer" with a custom URI scheme (e.g., matter://onboard?code=...). The mobile OS on the user's device recognizes this URI scheme and automatically launches the system's Matter commissioning service. This service then uses the pointer data to securely and directly connect the light bulb to the user's local smart home network, completing the final communication step over a local protocol like Thread.