Derivative works — US Patent 6076733

Defensive Disclosure and Prior Art Generation Based on U.S. Patent 6,076,733

Publication Date: April 29, 2026
Subject Matter: Systems and Methods for Accessing Networked Resources via Scanned Codes.

This document serves as a defensive publication to disclose variations, extensions, and combinations of the technologies described in U.S. Patent 6,076,733. The intent is to place these concepts into the public domain, thereby establishing them as prior art for any future patent applications.

Derivative Embodiments of Claim 1 (The System)

The core claim describes a system comprising an Internet access terminal with a GUI browser and a bar code reader programmed to read URL-encoded bar codes to automatically access and display a web document. The following are derivative embodiments of this system.

1. Material & Component Substitution

Derivative 1.1: Quantum Dot Barcode System

Enabling Description: The printed barcode is replaced with a pattern of quantum dots (QDs), each engineered to emit light at a specific, narrow wavelength when excited by a UV or near-infrared (NIR) light source. The "barcode reader" is a specialized spectrophotometer coupled with an imaging sensor. The scanner excites the QD pattern and reads the sequence of emitted wavelengths, which are decoded into a URL. This method provides a high-density, invisible, and difficult-to-replicate alternative to traditional printed barcodes. The terminal's software includes a decoding library that maps the sequence of spectral peaks to their corresponding ASCII characters to reconstruct the URL before passing it to the browser.

Mermaid Diagram:

graph TD
    A[UV/NIR Emitter] --> B{QD Pattern on Substrate};
    B --> C[Spectrophotometer & Imager];
    C --> D[Wavelength Sequence Processor];
    D --> E{URL Reconstruction Module};
    E --> F[Internet Browser];
    F --> G[Access Web Resource];

Derivative 1.2: Haptic Feedback Barcode Reader for Tactile Input

Enabling Description: The barcode is a 3D-printed topographical pattern of varying heights and spacings, compliant with a tactile data standard. The "reader" is a high-resolution tactile sensor array, such as those used in robotics, which measures the physical variations on the surface. An onboard processor with pattern recognition software converts the topographical data into a digital string representing the URL. This system is designed for environments where optical scanning is impractical (e.g., in complete darkness, on highly reflective or transparent surfaces) or for accessibility applications for the visually impaired.

Mermaid Diagram:

sequenceDiagram
    participant User
    participant TactileScanner
    participant Computer
    participant WebServer

    User->>+TactileScanner: Drags scanner over 3D barcode
    TactileScanner->>TactileScanner: Read topographical data
    TactileScanner->>Computer: Transmit decoded URL string
    deactivate TactileScanner
    Computer->>Computer: Input URL into browser
    Computer->>+WebServer: HTTP GET Request
    WebServer-->>-Computer: Return HTML Document
    Computer->>User: Display Web Page

2. Operational Parameter Expansion

Derivative 2.1: High-Temperature Industrial Process Control System

Enabling Description: In an industrial furnace or manufacturing environment exceeding 1000°C, machine-readable codes are laser-etched onto ceramic or high-temperature alloy plates affixed to equipment. The code encodes a URL pointing to a specific endpoint on an internal SCADA (Supervisory Control and Data Acquisition) system's web server. The scanner is a high-temperature, water-cooled boroscope with a long-wavelength infrared (LWIR) imager that can read the thermally-stable etched code. Upon scanning, a technician's ruggedized terminal accesses the URL, which displays real-time temperature, pressure, and chemical composition data for that specific zone or component.

Mermaid Diagram:

graph TD
    subgraph Furnace [High-Temperature Environment >1000°C]
        A[Ceramic Plate with Etched Code]
    end
    B[Water-Cooled LWIR Scanner] -- Reads --> A
    B -- Decoded URL --> C[Ruggedized Terminal]
    C -- HTTP Request --> D[SCADA Web Server]
    D -- Real-time Process Data --> C
    C -- Displays Data --> E[Technician Interface]

Derivative 2.2: Nanoscale Feature Identification System

Enabling Description: A pattern is etched onto a silicon wafer or biological slide using electron-beam lithography at the nanometer scale. This pattern, when imaged by an Atomic Force Microscope (AFM) or Scanning Electron Microscope (SEM), represents a binary encoding of a URL. Image processing software, integrated with the microscope's control system, decodes the pattern and transmits the URL to a connected computer's web browser. The URL links to a database containing the full experimental data, manufacturing parameters, or genetic information associated with the specific nano-feature being imaged.

Mermaid Diagram:

flowchart LR
    subgraph Microscope
        A[AFM/SEM Tip] --> B(Nanoscale Etched Pattern)
        B --> C{Image Capture}
    end
    C --> D[Image Processing & Decoding Engine]
    D -- "URL: http://data.repo/wafer3/feature7" --> E[Workstation Browser]
    E -- Request --> F((Database))
    F -- "Full Dataset" --> E

3. Cross-Domain Application

Derivative 3.1: Aerospace - In-Situ Component Lifecycle Management

Enabling Description: A 2D data matrix code is chemically etched or laser-annealed onto a critical, non-rotating aircraft engine turbine blade. The code contains a secure URL pointing to a private, access-controlled server. During maintenance, a technician uses a handheld, ruggedized endoscope with an integrated scanner to read the code without disassembling the engine. The URL, combined with the technician's cryptographic credentials, opens a web interface displaying the blade's full lifecycle history: manufacturing date, material batches, flight hours, thermal cycles, inspection records, and a link to its digital twin for stress analysis.

Mermaid Diagram:

sequenceDiagram
    participant Technician
    participant EndoscopeScanner
    participant SecureWebServer
    participant DigitalTwinDB

    Technician->>+EndoscopeScanner: Scan code on turbine blade
    EndoscopeScanner->>SecureWebServer: HTTPS GET request with URL + Auth Token
    SecureWebServer->>+DigitalTwinDB: Query for component 'xyz'
    DigitalTwinDB-->>-SecureWebServer: Return lifecycle data
    SecureWebServer-->>-EndoscopeScanner: Serve HTML page with data
    EndoscopeScanner->>Technician: Display component history & digital twin link

Derivative 3.2: AgTech - Precision Agriculture and Phenotyping

Enabling Description: A weatherproof tag with a URL-encoded QR code is attached to an individual plant in a research field or vertical farm. An autonomous rover or drone equipped with a scanner and imaging system periodically scans the code. The URL for each plant links to a specific record in a cloud-based agricultural database. Upon a successful scan, the rover uploads a multi-spectral image of the plant, soil moisture readings, and physical measurements to that URL endpoint via a REST API. Researchers can then scan the same code with a mobile device to pull up the plant's complete, time-series growth data and imagery.

Mermaid Diagram:

erDiagram
    PLANT ||--o{ LOG_ENTRY : has
    PLANT {
        string plantID PK
        string url "Unique URL"
        string genotype
        string location
    }
    LOG_ENTRY {
        string plantID FK
        datetime timestamp
        string multispectralImagePath
        float soilMoisture
        float height
    }

Derivative 3.3: Emergency Services - Dynamic Medical Information Access

Enabling Description: A durable wristband or ID card provided to individuals with chronic medical conditions (e.g., severe allergies, diabetes) contains a URL-encoded barcode. The URL is a persistent but dynamically linked address. In an emergency, a first responder scans the code with their department-issued secure mobile device. The device's browser accesses the URL, which directs to a HIPAA-compliant medical information portal. The portal, after authenticating the responder's device, displays critical information: allergies, current medications, emergency contacts, and advance directives. The backend service can update the information pointed to by the URL without needing to issue a new wristband.

Mermaid Diagram:

graph TD
    A[First Responder] -- Scans --> B(Patient Wristband QR Code);
    B -- "URL: https://ems.health/id/12345" --> C(Secure Mobile Device);
    C -- HTTPS Request + Device Auth --> D{HIPAA-Compliant Server};
    D -- Authenticates Responder --> E[Dynamic Health Record DB];
    E -- "Critical Patient Data" --> D;
    D -- Serves Emergency Data Page --> C;

4. Integration with Emerging Tech

Derivative 4.1: AI - Predictive Maintenance System

Enabling Description: A barcode on a piece of industrial machinery encodes a URL. When a technician scans the code with a smartphone, it opens a web application. The application uses the phone's camera to capture a short video or sound recording of the machine in operation. This data is uploaded to a cloud-based AI model associated with the URL's endpoint. The AI analyzes the data for signs of wear and tear (e.g., vibration anomalies, specific acoustic signatures) and compares it to the machine's historical data. The web page then displays a real-time health score, a prediction of potential failure modes, and recommended preventative maintenance actions.

Mermaid Diagram:

sequenceDiagram
    participant Technician
    participant SmartphoneApp
    participant AI_Analysis_Service
    participant Machine_Data_Store

    Technician->>SmartphoneApp: Scan URL-barcode on machine
    SmartphoneApp->>AI_Analysis_Service: Open web app & request data capture
    Technician->>SmartphoneApp: Record machine audio/video
    SmartphoneApp->>AI_Analysis_Service: Upload media data via URL endpoint
    AI_Analysis_Service->>Machine_Data_Store: Fetch historical data for this machine
    AI_Analysis_Service->>AI_Analysis_Service: Run predictive maintenance model
    AI_Analysis_Service-->>SmartphoneApp: Return health score & recommendations
    SmartphoneApp->>Technician: Display analysis results

Derivative 4.2: IoT - Real-Time Environmental Monitoring

Enabling Description: A barcode is placed on a physical asset, such as a shipping container. The barcode's URL points to a web dashboard. The container is also equipped with a suite of IoT sensors (GPS, temperature, humidity, accelerometer). These sensors continuously transmit data to a cloud platform. When the barcode is scanned, the web browser on the scanning device navigates to the specific URL, which displays a real-time dashboard of the container's current location on a map, its internal environmental conditions, and any shock or tilt alerts. The URL itself can contain query parameters to pre-filter the time range of data displayed.

Mermaid Diagram:

graph TD
    subgraph Container
        A[IoT Sensors]
        B[URL Barcode]
    end
    subgraph Cloud
        C[IoT Data Ingestion]
        D[Time-Series Database]
        E[Web Dashboard Server]
    end
    A -- "Data Stream (GPS, Temp)" --> C
    C --> D
    E -- Queries --> D
    F[User with Scanner] -- Scans --> B
    B -- "URL: .../dashboard?id=XYZ" --> F
    F -- HTTP Request --> E
    E -- "Renders Real-time Dashboard" --> F

Derivative 4.3: Blockchain - Supply Chain Verification

Enabling Description: A product (e.g., a pharmaceutical bottle, a bag of fair-trade coffee) is marked with a tamper-evident seal and a URL-encoded barcode. The URL points to a web interface that acts as a front-end to a public or permissioned blockchain. The path of the URL contains the unique batch ID of the product. When a consumer scans the code, the web page queries the blockchain for that batch ID and displays its immutable journey from origin to retail: farm/factory location, quality control checks, shipping dates, and custodian transfers, each recorded as a transaction on the blockchain. This provides a high-trust method for verifying authenticity and provenance.

Mermaid Diagram:

flowchart LR
    A[Product with URL Barcode] --> B{Consumer Scans Code};
    B --> C[Mobile Device Browser];
    C -- "HTTP GET to /verify?batch=123" --> D[Web3 Gateway Server];
    D -- "Read transaction log for 'batch123'" --> E((Immutable Blockchain Ledger));
    E -- Provenance Data --> D;
    D -- Formats & Serves HTML Page --> C;

5. The "Inverse" or Failure Mode

Derivative 5.1: Graceful Degradation for Network Outage

Enabling Description: The system is designed for environments with intermittent network connectivity (e.g., remote field sites, emergency response zones). The URL-encoded barcode contains two data segments. The primary segment is the standard HTTPS URL. A secondary, specially formatted segment contains a compressed, minimalist set of critical data (e.g., "Item: First-Aid Kit", "Expires: 2027-12", "Owner: MedBay-3"). The client application (browser or dedicated app) first attempts to resolve the HTTPS URL. If it fails due to a network outage, it falls back to a "local resolution mode," parsing the secondary data segment and displaying the critical information directly from the barcode itself, ensuring essential data is always available.

Mermaid Diagram:

stateDiagram-v2
    [*] --> Attempt_Connection
    Attempt_Connection --> Connected: Network Available
    Attempt_Connection --> Offline_Mode: Network Unavailable
    Connected: Display Full Web Page
    Offline_Mode: Decode Local Data from Barcode
    Offline_Mode: Display Critical Information
    Connected --> [*]
    Offline_Mode --> [*]

Combination with Open-Source Standards

Scenario 1: Integration with W3C Verifiable Credentials

Description: A barcode on a physical ID card or certificate contains a URL. When scanned, this URL resolves to a service that initiates a challenge-response protocol using the W3C Verifiable Credentials data model. The user's device (acting as a digital wallet) responds to the challenge by presenting a cryptographically signed Verifiable Credential (e.g., a proof of graduation, a professional license). The web service at the URL verifies the signature against a public key stored in a distributed ledger or a trusted registry (like did:web). This combines the physical-to-digital link of the barcode with a decentralized, open-standard method for identity and credential verification.

Scenario 2: Integration with MQTT for IoT Messaging

Description: Instead of an http:// URL, the barcode encodes a URL with a custom scheme, such as mqtt://. A specialized client application, rather than a standard web browser, is registered to handle this scheme. The URL contains the address of an MQTT broker, a topic name, and a payload. For example: mqtt://broker.example.com/device/789/command?payload={"action":"calibrate"}. When a technician scans this barcode on an IoT device, the client app automatically publishes the specified message to the MQTT topic, instructing the device to perform an action like self-calibration, rebooting, or entering a diagnostic mode. This leverages the lightweight, publish/subscribe nature of the open MQTT protocol for direct device control.

Scenario 3: Integration with OPC Unified Architecture (OPC UA)

Description: In an Industry 4.0 manufacturing setting, a barcode on a machine component encodes an OPC UA endpoint URL (e.g., opc.tcp://192.168.1.100:4840/server/node?id=ns=2;s=MotorSpeed). A technician's tablet or HMI (Human-Machine Interface) device has a client application capable of acting as an OPC UA client. Scanning the barcode causes the client to connect directly to the OPC UA server embedded in the machine's PLC or controller. The client then reads or subscribes to the specific node ID encoded in the URL, displaying a real-time value (like motor RPM, temperature, or fault codes) directly from the machine's control system. This uses an open standard for industrial interoperability to create a direct link from a physical component to its live operational data.