US 7765126

An analysis of United States Patent 7,765,126 reveals the following details:

Title: System and method for automatic access of a remote computer over a network

Assignee: The listed current assignee is Nm LLC. The original assignee was Neomedia Technologies Inc.

Inventors: Frank C. Hudetz and Peter R. Hudetz

Filing Date: June 20, 2007

Issue Date: July 27, 2010

Abstract:
The patent describes a system and method that uses identification codes, such as Uniform Product Codes (UPCs) found on commercial articles, to access remote computers on a network. A user can input a product's UPC, for instance by scanning the barcode, into a computer. A database then uses this UPC to find a corresponding network address, like an Internet URL. This location information is then used by the user's computer to access the desired online resource related to that product.

Overview of Independent Claims:

This patent has three independent claims, which are the broadest claims of the patent.

Independent Claim 1: This claim outlines a method for connecting a user's device to a remote computer. The process involves:

1. A user scans a barcode to get an "index."
2. The user's device sends this index over a network to a remote server.
3. The server uses the index to look up a corresponding Uniform Resource Locator (URL) in a database. This database links various indexes to the URLs of different remote computers.
4. The server finds and sends at least one URL back to the user's device.
5. The user's device then uses one of these URLs to connect directly to the specific remote computer.

Independent Claim 7: This claim describes a system that accomplishes the method of Claim 1. The system consists of:

• A user's computing device.
• A barcode scanner connected to the device to read a barcode and get an index.
• A remote server, accessible via a network, that holds a database. This database links indexes to the URLs of remote computers.
  The user's device is equipped to communicate with the server to send the index and receive the URL(s), and then to use a URL to connect to the targeted remote computer.

Independent Claim 11: This claim focuses on the user's computing device itself. The device includes:

• A barcode scanner for reading an index from a barcode.
• A computer processor running software that can:
  • Send the index to a remote server so the server can find the corresponding URL(s) in its database.
  • Receive the URL(s) back from the server.
  • Use one of the received URLs to connect to the designated remote computer over the network.

As of April 28, 2026, a search of the dockets for the Court of Appeals for the Federal Circuit (CAFC) for the year 2026 did not reveal any public records specifically associated with US patent 7,765,126.

Known Litigation Involving US Patent 7,765,126

Based on a review of patent litigation databases, US Patent 7,765,126 has been asserted in multiple lawsuits. The original assignee, Neomedia Technologies, Inc., and the current assignee, NM, LLC, have been active in litigating this patent.

A notable series of lawsuits was filed in 2014 by Neomedia Technologies, Inc. against several major retailers. The core allegation in these cases was that the defendants' use of QR code systems for marketing and customer engagement infringed upon the technology described in US Patent 7,765,126 and related patents.

Details of these cases are as follows:

• Plaintiff: Neomedia Technologies, Inc.
  Defendant: The Kroger Co.
  Jurisdiction: U.S. District Court for the District of Colorado
  Case Number: 1:14-cv-01315
  Filing Date: May 9, 2014
  Outcome/Status: The case was terminated on November 21, 2014. Public records suggest the parties likely reached a settlement, as is common in such disputes, though the specific terms were not disclosed.

• Plaintiff: Neomedia Technologies, Inc.
  Defendant: Wal-Mart Stores, Inc. (now Walmart Inc.)
  Jurisdiction: U.S. District Court for the District of Colorado
  Case Number: 1:14-cv-01211
  Filing Date: April 30, 2014
  Outcome/Status: This case was also terminated on November 21, 2014, under circumstances that suggest a settlement was reached.

• Plaintiff: Neomedia Technologies, Inc.
  Defendant: Home Depot U.S.A., Inc.
  Jurisdiction: U.S. District Court for the District of Colorado
  Case Number: 1:14-cv-01191
  Filing Date: April 28, 2014
  Outcome/Status: This case was terminated on November 21, 2014, consistent with the timing of the other related lawsuits, pointing towards a likely settlement.

• Plaintiff: Neomedia Technologies, Inc.
  Defendant: Target Corp.
  Jurisdiction: U.S. District Court for the District of Colorado
  Case Number: 1:14-cv-01190
  Filing Date: April 28, 2014
  Outcome/Status: The case against Target was terminated on November 21, 2014, presumably as part of a broader settlement agreement covering the various defendants.

• Plaintiff: Neomedia Technologies, Inc.
  Defendant: Costco Wholesale Corporation
  Jurisdiction: U.S. District Court for the District of Colorado
  Case Number: 1:14-cv-01189
  Filing Date: April 28, 2014
  Outcome/Status: This case was terminated on November 21, 2014.

It appears that Neomedia Technologies, Inc. engaged in a concerted litigation campaign in 2014, which was resolved by the end of that year. No further litigation involving US Patent 7,765,126 has been identified in the period since these cases were terminated.

Proceedings overview

The USPTO ODP API indicates no AIA trial proceedings on file for US Patent 7,765,126. This means there are currently no active or terminated IPR, PGR, or CBM proceedings listed in the official USPTO data for this patent. Consequently, all claims of the patent remain untested by PTAB proceedings.

Strategic summary

As of the current date, all claims of US Patent 7,765,126 are untested by PTAB proceedings. No claims have been canceled, sustained, or modified through IPR, PGR, or CBM trials. This means there is no estoppel landscape established by PTAB decisions under § 315(e)(2) for potential petitioners. The absence of PTAB activity could suggest various things, such as the patent not being asserted widely enough to attract IPR challenges, or that past assertions were settled before an IPR was deemed necessary.

Recommended next steps

If you are a defendant facing assertion of US Patent 7,765,126, the absence of PTAB activity means that the claims have not been challenged or affirmed in these specific administrative forums. This provides a clean slate for a potential IPR, PGR, or CBM petition, as there are no existing PTAB decisions to consider for estoppel. You would need to conduct a thorough prior art search and develop arguments for unpatentability if you chose to pursue an AIA trial.

Inventors

• Frank C. Hudetz: Employer at the time of filing (June 20, 2007) is not explicitly stated in the patent. However, as Neomedia Technologies Inc. is listed as the applicant and original assignee, it is highly probable he was an employee or had assigned his rights to Neomedia at that time.
• Peter R. Hudetz: Employer at the time of filing (June 20, 2007) is not explicitly stated in the patent. Similar to Frank C. Hudetz, it is highly probable he was an employee of, or had assigned his rights to, Neomedia Technologies Inc. at that time.

No unusual patterns regarding inventor departures are evident from the provided information within 12 months of the filing date.

Original assignee

The entity named on the issued patent (US7765126B2) as the original assignee is Neomedia Technologies Inc.

Neomedia Technologies, Inc. developed 2D mobile barcode technology and service solutions, including products like NeoReader (a barcode scanning application) and NeoSphere/QodeScan (cloud-based barcode management software). Their "PaperClick" technology, which allowed users to scan barcodes to access product-related websites, directly embodied the claims of the patent. This indicates they did ship products and services embodying the claims. They also provided IP licensing services.

As of May 2026, Neomedia Technologies, Inc. (NEOM) is trading on the OTC Markets at a very low price, with minimal reporting and only 3 employees reported as of 2016. While OTC Markets lists them as "Shell: No," their operational status appears significantly diminished, suggesting they are largely inactive or primarily engaged in IP licensing, rather than robust product development. The patent itself is listed as "Expired - Fee Related," further indicating a decline in the company's active portfolio management.

Assignment timeline

• 2008-10-31 (executed) / recorded 2008-11-04 — Reel 021950/0279
  • Conveyance: Security Agreement
  • Assignor: NEOMEDIA TECHNOLOGIES INC.
  • Assignee: YA GLOBAL INVESTMENTS, L.P.
  • Correspondent: KAREN S. ROBINSON; BAKER & MCKENZIE LLP; ONE PRUDENTIAL PLAZA, 130 E RANDOLPH DR, CHICAGO, IL 60601
  • Context: Securitization of patent assets by the original assignee.
• 2009-05-13 (executed) / recorded 2009-05-13 — Reel 022728/0861
  • Conveyance: Assignment of Assignors Interest
  • Assignor: HUDETZ, FRANK C; HUDETZ, PETER R
  • Assignee: SOLAR COMMUNICATIONS, INC.
  • Correspondent: W. RANDOLPH MAY; STERNE, KESSLER, GOLDSTEIN & FOX P.L.L.C.; 1100 NEW YORK AVENUE, N.W., WASHINGTON, DC 20005. This correspondent will recur.
  • Context: Transfer of inventor rights to an intermediate entity.
• 2009-05-13 (executed) / recorded 2009-05-13 — Reel 022728/0863
  • Conveyance: Assignment of Assignors Interest
  • Assignor: SOLAR COMMUNICATIONS, INC.
  • Assignee: NEOMEDIA TECHNOLOGIES, INC.
  • Correspondent: W. RANDOLPH MAY; STERNE, KESSLER, GOLDSTEIN & FOX P.L.L.C.; 1100 NEW YORK AVENUE, N.W., WASHINGTON, DC 20005. This correspondent recurs.
  • Context: Transfer from the intermediate entity back to the original assignee.
• 2016-01-28 (executed) / recorded 2016-01-29 — Reel 036835/0073
  • Conveyance: Notice of Security Interest
  • Assignor: NEOMEDIA TECHNOLOGIES, INC.
  • Assignee: YA GLOBALINVESTMENTS, L.P.
  • Correspondent: J. STEPHEN DOOLEY; THE DOOLEY LAW FIRM P.A.; 101 N. TRYON ST., SUITE 1100, CHARLOTTE, NC 28246. This correspondent will recur.
  • Context: Establishment of a new or updated security agreement.
• 2016-09-01 (executed) / recorded 2016-09-02 — Reel 037920/0942
  • Conveyance: Assignment of Assignors Interest
  • Assignor: NEOMEDIA TECHNOLOGIES, INC.
  • Assignee: NM, LLC
  • Correspondent: WILLIAM B. NASH; WILLIAM B. NASH, P.A.; 4531 OLD CANTON ROAD, SUITE 213, JACKSON, MS 39211
  • Context: Transfer of ownership from the original assignee to a new entity.
• 2017-01-24 (executed) / recorded 2017-01-24 — Reel 038446/0970
  • Conveyance: Release
  • Assignor: YA GLOBAL INVESTMENTS, L.P.
  • Assignee: NEOMEDIA TECHNOLOGIES, INC.
  • Correspondent: J. STEPHEN DOOLEY; THE DOOLEY LAW FIRM P.A.; 101 N. TRYON ST., SUITE 1100, CHARLOTTE, NC 28246. This correspondent recurs.
  • Context: Release of security interest, typically after debt repayment or in conjunction with other transactions.
• 2017-01-24 (executed) / recorded 2017-01-24 — Reel 038446/0971
  • Conveyance: Release
  • Assignor: YA GLOBAL INVESTMENTS, L.P.
  • Assignee: NEOMEDIA TECHNOLOGIES, INC.
  • Correspondent: J. STEPHEN DOOLEY; THE DOOLEY LAW FIRM P.A.; 101 N. TRYON ST., SUITE 1100, CHARLOTTE, NC 28246. This correspondent recurs.
  • Context: Another release of security interest, likely a duplicate or related to a broader portfolio release.

Timeline diagram

timeline
    title Ownership of US 7765126
    2007 : Application filed
    2008 : Security agreement with YA Global
    2009 : Inventors to Solar Comm
         : Solar Comm to Neomedia Tech Inc
    2010 : Patent issued
    2014 : First infringement suits filed
    2016 : Security agreement with YA Global
         : Assigned to NM LLC
    2017 : Security interest released by YA Global

NPE / troll-pattern signals

1. Shell-entity transfer — Present.
   • NM, LLC (assignee on 2016-09-02, Reel 037920/0942) is the current assignee. Its generic name ("NM, LLC") and the lack of readily available information about products or services associated with it strongly suggest it is a licensing-only entity. Neomedia Technologies Inc., while an operating company, had also engaged in "IP licensing services", indicating a dual strategy that could transition to a more pure-play NPE model.
2. Known asserter in the chain — Unclear.
   • YA Global Investments, L.P. appears as an assignee for security interests (2008-11-04, Reel 021950/0279; 2016-01-29, Reel 036835/0073). While some investment firms engage in patent-related activities, there's no immediate indication that YA Global Investments is a known NPE in the same vein as those listed (Acacia, Marathon, etc.). Neomedia Technologies Inc. itself was active in litigation but is not typically listed as a general "NPE." NM, LLC is not widely recognized on public NPE lists without further investigation.
3. Repeat correspondent across the chain — Present.
   • W. Randolph May of STERNE, KESSLER, GOLDSTEIN & FOX P.L.L.C. appears as the correspondent for both the 2009-05-13 inventor assignment to Solar Communications, Inc. (Reel 022728/0861) and the subsequent assignment from Solar Communications, Inc. to Neomedia Technologies, Inc. (Reel 022728/0863).
   • J. Stephen Dooley of THE DOOLEY LAW FIRM P.A. appears as the correspondent for the 2016-01-29 Notice of Security Interest (Reel 036835/0073) and the two 2017-01-24 Release documents (Reel 038446/0970 and 038446/0971).
   • The recurrence of these specific attorneys for related transactions (May for the 2009 transfers, Dooley for the 2016-2017 security agreements/releases) within the chain is a signal.
4. Cascading transfers — Not present.
   • While there are two assignments on the same day in 2009, they are part of a clean-up of inventor rights, not a chain of LLCs passing the patent. The other assignments are spaced out.
5. Pre-litigation transfer — Not present.
   • The first litigation suit was filed in April 2014. The last assignment prior to this was the security agreement in 2008, and the inventor assignments in 2009. There was no assignment within 6 months before the 2014 litigation. The significant assignment to NM, LLC occurs after the 2014 litigation.
6. Bankruptcy fire-sale — Unclear.
   • While Neomedia Technologies Inc. shows signs of being largely inactive (very low stock price, few employees), there is no explicit record of a Chapter 7 or 11 bankruptcy filing leading to a patent sale. The transfer to NM, LLC could be an asset sale outside of formal bankruptcy proceedings, but without direct evidence, it remains unclear.
7. Privateering — Unclear.
   • There is no evidence in the provided information to suggest an operating company transferred the patent to an NPE to assert on its behalf against competitors.
8. Defensive aggregator (anti-NPE) — Not present.
   • The chain does not terminate at any known defensive aggregators.

Verdict

NPE — moderate confidence

The transfer from Neomedia Technologies, Inc. (an operating company with some IP licensing activities) to NM, LLC (a generic-named entity with no clear operating business) on 2016-09-02 (Reel 037920/0942) is a strong signal of a shell-entity transfer. The recurrence of specific correspondent attorneys (W. Randolph May and J. Stephen Dooley) throughout the chain, particularly for security interests and assignments, further supports this pattern by indicating a consistent legal strategy for managing the patent assets. The fact that the patent itself is now "Expired - Fee Related" further points away from active product development and towards an asset management or assertion focus.

USPTO Assignment Center Search for US7765126

Based on a technical analysis of US patent 7,765,126 and the prior art cited during its examination by the USPTO, the following references are identified as most relevant. These references describe technologies that existed before the patent's priority date of June 20, 1995, and disclose systems and methods similar to those claimed in the '126 patent.

An anticipatory prior art reference under 35 U.S.C. § 102 must disclose every element of a patent claim, either explicitly or inherently. The analysis below outlines how each cited reference potentially anticipates the independent claims (1, 7, and 11) of the '126 patent.

Most Relevant Prior Art

1. EP 0 744 856 A3 (AT&T Corp)

• Full Citation: European Patent Application EP0744856A3, "Apparatus for and method of utilizing product identifier codes to establish communication connections." Filed on May 26, 1995.
• Brief Description: This patent application discloses a system where a user can scan a product identifier, such as a UPC barcode on a product, using a scanning device. This identifier is then sent to a remote service that contains a database. The database maps the product identifier to a corresponding communication address, such as a telephone number or a network address. The system then uses this address to establish a communication link, for instance, to connect to a vendor for that product.
• Potential Anticipation of Claims 1, 7, and 11:
  This European patent application, with a filing date that predates the priority date of the '126 patent, is particularly strong prior art.
  • It discloses scanning a barcode to get an "index" (the product identifier), as required by Claim 1(a).
  • It describes transmitting this identifier to a remote service/server over a network, aligning with Claim 1(b).
  • The remote service uses a database to look up a communication/network address based on the identifier, which corresponds to the database and URL lookup steps in Claim 1(c) and 1(d).
  • Finally, it describes establishing a communication connection based on the looked-up address, which is the functional result of the final step in Claim 1(f) where the user's device connects to the remote computer. The process described is functionally equivalent to the system, method, and device claimed in the '126 patent.

2. US 5,918,214 A (Perkowski)

• Full Citation: US Patent 5,918,214, "System and method for finding product and service related information on the internet." Filed on October 25, 1996.
• Brief Description: The Perkowski '214 patent details a system that allows users to find product information on the internet by using a product's identification number (e.g., UPC). A user inputs the number into their computer, which sends it to a server. The server holds a database linking these product numbers to specific URLs. The server finds the matching URL and sends it back to the user's computer, which can then connect to the relevant web page.
• Potential Anticipation of Claims 1, 7, and 11:
  Although filed after the '126 patent's priority date, this patent is cited as relevant art and describes a very similar system. It clearly teaches all the core elements of the independent claims:
  • Claims 1, 7, 11: Perkowski describes the exact workflow claimed in the '126 patent: a user device sending a product identifier (an "index") to a remote server, the server using a database to resolve this identifier into a URL, the server returning the URL to the user device, and the user device using that URL to establish a connection. While the patent doesn't explicitly require the initial input to be from a barcode scanner, using a product identification number like a UPC inherently suggests it, and barcode scanning was a well-known method for inputting UPCs at the time.

3. US 6,064,979 A (Perkowski)

• Full Citation: US Patent 6,064,979, "Method of and system for finding and serving consumer product related information over the internet using manufacturer identification numbers." Filed on October 25, 1996.
• Brief Description: This patent, related to the Perkowski '214 patent, focuses on a similar system but emphasizes using the manufacturer-specific portion of a product code. A user can input a manufacturer's ID, and a remote server's database will return a URL for that manufacturer, such as their main website.
• Potential Anticipation of Claims 1, 5, 7, and 11:
  This reference reinforces the disclosure of the '214 patent. It explicitly anticipates Claim 5, which specifies that the "index" can be "at least a portion of a Universal Product Code." The system's architecture and data flow—transmitting an identifier to a server for URL resolution and return—is identical to the process described in the independent claims of the '126 patent.

4. US 6,164,534 A (Rathus)

• Full Citation: US Patent 6,164,534, "Method and apparatus for accessing electronic data via a familiar printed medium." Filed on April 4, 1996.
• Brief Description: The Rathus patent describes linking printed materials, like books, to electronic data. A user scans a barcode in the book, and a computer retrieves an associated data file. The patent specifies that this data file can be retrieved from either a local storage device (like a CD-ROM) or a "remote server."
• Potential Anticipation of Claims 1, 7, and 11:
  Rathus discloses the fundamental concept of scanning a barcode to trigger the retrieval of electronic information. The key elements are present: a barcode scan provides a code (Claim 1(a)), and this code is used by a computing device to retrieve data. The disclosure that the data can come from a "remote server" implies a network connection and a lookup mechanism. While it doesn't detail the intermediate step of returning a URL as explicitly as Perkowski, the function of using a scanned code to access a specific remote network resource is clearly taught. This provides a strong basis for an anticipation argument against the broader claims of the '126 patent.

Based on the provided prior art and the state of technology as of the patent's priority date of June 20, 1995, an analysis of obviousness under 35 U.S.C. § 103 indicates that the independent claims of US patent 7,765,126 would have been obvious to a Person Having Ordinary Skill in the Art (PHOSITA).

A PHOSITA at that time would have possessed a working knowledge of computer networking, including the protocols and architecture of the burgeoning World Wide Web (WWW), familiarity with database systems, and an understanding of common data input methods, such as barcode scanning for product identification.

The core concept of the '126 patent is the use of a pre-existing product identifier (like a UPC) to look up a corresponding network address (URL) in a remote database, thereby linking a physical object to an online resource. The prior art, when combined, suggests this solution was an obvious advancement.

Obviousness Combinations

1. Combination of Rathus ('534) with the known architecture of the World Wide Web

• Rathus (US 6,164,534 A): Teaches a system for linking printed media to electronic data by scanning a barcode. Crucially, Rathus explicitly states that the associated data file could be retrieved from a local source (like a CD-ROM) or a "remote server." This establishes the core concept of using a barcode scan to trigger access to data over a network.
• Common Knowledge of the WWW (as of mid-1995): By 1995, the WWW was a rapidly expanding public network. The use of Uniform Resource Locators (URLs) as the standard addressing scheme to locate and retrieve resources from remote web servers was fundamental. Web browsers like Netscape Navigator were becoming widely available, and the problem of long, difficult-to-type URLs was a known usability issue, as acknowledged in the '126 patent's background section.
• Motivation to Combine: A PHOSITA, aware of the problem of cumbersome URL entry, would be motivated to find a more user-friendly method for accessing web resources. Seeing the Rathus patent's disclosure of using a barcode to access a "remote server," the PHOSITA would have found it obvious to apply this method to the most prominent and standardized network of remote servers in existence: the World Wide Web.
  • The Obvious Step: The logical and predictable implementation of Rathus's system in the context of the WWW would be to have the "remote server" be a web server and the "electronic data" be a web page. The unique identifier for that web page would be its URL. The intermediate step—using the scanned barcode as an index to a database that maps the code to the corresponding URL—is a standard and obvious method for implementing such a lookup service. Therefore, combining Rathus's general teaching with the specific, well-known architecture of the WWW renders the invention of the '126 patent obvious.

2. Combination of AT&T (EP 0 744 856 A3) with the known architecture of the World Wide Web

• AT&T ('856): Discloses a nearly complete system. It teaches scanning a product identifier (like a UPC), sending that identifier to a remote service with a database, mapping the identifier to a "communication address," and using that address to establish a connection.
• Common Knowledge of the WWW (as of mid-1995): As stated above, the URL was the standard for addressing informational resources on computer networks.
• Motivation to Combine: The AT&T application provides a blueprint for using product codes to initiate network connections. A PHOSITA would have been motivated to adapt this system for use with the WWW to allow consumers to easily access product information online. The term "communication address" in the AT&T filing is a general term. In the context of accessing information on a remote computer over the Internet in 1995, the most common, logical, and effective type of "communication address" was a URL. Substituting a URL for the more generic "communication address" is not an inventive step but rather an obvious implementation choice to apply the AT&T system to the dominant information network of the era. This combination makes all the steps of independent claim 1 obvious.

Analysis of Dependent Claims

The dependent claims of the '126 patent add limitations that were also either known or obvious at the time.

• Claim 5 (using a portion of a UPC): A UPC is inherently divisible into a manufacturer code and a product code. The idea of using only the manufacturer portion to find a manufacturer's general website (as opposed to a specific product page) would have been an obvious and desirable feature. This is further supported by the teachings of the Perkowski '979 patent, which, while filed later, describes this exact functionality, indicating it was a known variation.
• Claims 2, 3, 8, 12 (user selection via hypertext link): If the database lookup returned one or more URLs, the standard and universal method for presenting these to a user within a web browser in 1995 was as a selectable hypertext link. This is a fundamental feature of HTML and web browsers, not an invention.
• Claims 4, 9, 13 (automatic connection): The choice between presenting a link for a user to click and automatically redirecting the browser to the retrieved URL is a simple programming design choice. Both were well-understood capabilities. The motivation to automatically connect would be to further streamline the user experience, which is an obvious goal.

In conclusion, the core elements of the '126 patent—scanning a code, network transmission, remote database lookup, and using the resulting address for connection—were taught by the prior art. The specific application of this process to the World Wide Web using URLs and barcodes was an obvious step for a person of ordinary skill in the art in 1995, who was motivated by the known problem of simplifying access to the growing number of online resources.

Analysis of Patent Term, Adjustments, and Family for US Patent 7,765,126

As of April 28, 2026, an analysis of the prosecution history and legal status of US Patent 7,765,126 reveals the following details regarding its term, related applications, and patent family.

Application and Priority Dates:

• Application Number: 11/765,887
• Filing Date: June 20, 2007
• Priority Date: The patent claims priority to a series of earlier applications, with the earliest non-provisional filing date being October 3, 1995, based on application Ser. No. 08/538,365 (now US Patent 5,978,773). This 1995 date is critical for determining the patent's expiration.

Patent Term Adjustments (PTA) and Extensions (PTE):

A review of the patent's file history indicates that there were no Patent Term Adjustments (PTA) or Patent Term Extensions (PTE) granted for US Patent 7,765,126. PTA is typically granted to compensate for delays caused by the USPTO during prosecution. In this case, no such statutory adjustments were awarded.

Continuations and Divisional Applications:

US Patent 7,765,126 is part of a larger family of patents and applications stemming from the original 1995 application. This specific patent is a continuation of a prior application.

• Parent Application: The application for US 7,765,126 (Ser. No. 11/765,887) is a continuation of application Ser. No. 10/768,991 (filed January 29, 2004, now US Patent 7,383,209).
• Continuation Applications: A continuation application is filed to pursue additional claims related to the invention disclosed in a parent application while maintaining the parent's priority date. This patent family utilized a "daisy-chain" of continuation applications to prosecute different sets of claims over time.
• Divisional Applications: The '126 patent itself is not a divisional application, but its predecessor, US Patent 6,199,048, was a divisional of the original 1995 application. A divisional application is typically filed when the USPTO determines that a parent application contains more than one distinct invention.

Related Family Members:

The '126 patent is a member of a large patent family, all claiming priority back to the original provisional application filed on June 20, 1995, and the subsequent non-provisional application filed on October 3, 1995. Key US patents and applications in this family include:

• US 5,978,773: Filed October 3, 1995.
• US 6,199,048: Filed January 15, 1999 (Divisional of the '773 patent's application).
• US 7,383,209: Filed January 29, 2004 (Continuation of the '048 patent's application).
• US 8,131,597: Filed June 30, 2010 (Continuation of the '126 patent's application).
• US 8,805,728: Filed December 13, 2011 (Continuation of the '597 patent's application).
• US 2014/0361071 A1: Filed August 11, 2014 (Continuation of the '728 patent's application).

Projected Expiration Date:

For utility patents filed after June 8, 1995, the term is generally 20 years from the earliest non-provisional filing date to which priority is claimed.

1. Earliest Non-Provisional Filing Date: October 3, 1995.
2. Standard 20-Year Term: Adding 20 years to this date gives an initial expiration date of October 3, 2015.

However, public patent databases indicate that the legal status of US 7,765,126 is "Expired - Fee Related" with an adjusted expiration date of March 20, 2017. This discrepancy arises from the payment of maintenance fees. Patents are subject to maintenance fees at 3.5, 7.5, and 11.5 years after the grant date to remain in force for the full term. The listed status indicates that the required maintenance fees were not paid, leading to the patent's expiration before its full potential term was reached. The specific date of March 20, 2017, likely corresponds to the end of the grace period for paying a required maintenance fee.

Defensive Disclosure for US Patent 7,765,126

Publication Date: April 28, 2026
Subject: Systems and methods for resolving a physical object's machine-readable index to a network-accessible resource. This document describes derivative works, alternative embodiments, and expansions of the concepts disclosed in US 7,765,126 to place them in the public domain.

---

1. Derivative Implementations based on Material & Component Substitution

The core concept of translating a physical identifier to a network address can be achieved using a wide variety of index-and-reader component pairs beyond optical barcodes.

1.1. Acoustic Fingerprint Indexing

• Enabling Description: A user's computing device (e.g., smartphone or specialized industrial tool) utilizes its microphone to capture an ambient or intentionally broadcasted audio signal from a product or environment. The signal is processed to generate a unique acoustic fingerprint (the "index"), using techniques such as Fast Fourier Transform (FFT) to analyze frequency distribution or temporal hashing algorithms. This index is transmitted to a remote server, which maintains a database mapping these audio fingerprints to specific URLs. The server resolves the index and returns the corresponding URL, which could lead to product information, environmental safety data, or multimedia content related to the audio source.
• Diagram:

  sequenceDiagram
      participant UserDevice as User Device (with Mic)
      participant Product as Product (with Audio Emitter)
      participant ResolverServer as Resolver Server
      participant ContentServer as Content Server
  
      UserDevice->>+Product: Capture audio signal
      Product-->>-UserDevice: Emits unique sound/watermark
      UserDevice->>UserDevice: Generate Acoustic Fingerprint (Index)
      UserDevice->>+ResolverServer: Transmit Index
      ResolverServer->>ResolverServer: Lookup URL in Fingerprint DB
      ResolverServer-->>-UserDevice: Return URL
      UserDevice->>+ContentServer: Request content from URL
      ContentServer-->>-UserDevice: Return content
  

1.2. Spectroscopic and Chemical Signature Indexing

• Enabling Description: For high-security or regulated goods (e.g., pharmaceuticals, aerospace components, fine art), a portable spectrometer integrated with a user device serves as the reader. The "index" is a unique spectroscopic signature derived from the object's material composition, a chemical taggant, or a specialized coating. The device captures the spectral data (e.g., via Raman spectroscopy or X-ray fluorescence), computes a hash or signature, and sends it to a secure server. The server database links these unique chemical signatures to URLs pointing to encrypted provenance records, certificates of authenticity, or material safety data sheets (MSDS).
• Diagram:

  graph TD
      A[User Device with Spectrometer] -- 1. Scan Object --> B(Object with Chemical Taggant);
      B -- 2. Emit Spectroscopic Data --> A;
      A -- 3. Generate Signature (Index) --> A;
      A -- 4. Transmit Index --> C[Secure Resolver Server];
      C -- 5. Access Signature-URL Database --> D[Database];
      D -- 6. Find Match --> C;
      C -- 7. Return URL for Certificate --> A;
      A -- 8. Access Certificate --> E[Provenance & Auth Server];
  

1.3. Haptic or Capacitive Surface Indexing

• Enabling Description: An object's surface is embedded with a unique pattern of capacitive traces or a distinct haptic texture. A user device equipped with a multi-touch capacitive sensor or a high-resolution haptic feedback scanner reads this pattern when placed in contact with the surface. The resulting 2D or 3D map of capacitance or surface topology is converted into a unique digital index. This index is sent to a resolver server to retrieve a URL corresponding to the object's interactive controls, configuration manuals, or diagnostic interfaces. This is applicable to smart surfaces, interactive packaging, and accessibility aids for the visually impaired.
• Diagram:

  stateDiagram-v2
      [*] --> Scanning
      Scanning --> Transmitting: Capacitive pattern acquired
      Transmitting --> Resolving: Index sent to server
      Resolving --> Connecting: URL received
      Connecting --> Done: Content loaded
      note right of Scanning
          Device's sensor array
          maps the unique surface
          pattern into a digital index.
      end note
  

---

2. Derivative Implementations based on Operational Parameter Expansion

The core method can be adapted to operate at vastly different physical scales and under extreme environmental conditions.

2.1. Nanoscale Biological Indexing

• Enabling Description: In a medical or biological context, nanobots equipped with molecular sensors act as the "user device." The "index" is a specific protein sequence, DNA marker, or cellular surface antigen identified on a target cell or pathogen. Upon positive identification, the nanobot transmits a signal corresponding to this molecular index to an external receiver connected to the network. The receiver forwards the index to a medical server, which resolves it to a URL pointing to a specific drug-release protocol, a diagnostic data packet, or instructions for the nanobot's next action.
• Diagram:

  sequenceDiagram
      participant Nanobot as Nanobot Sensor
      participant TargetCell as Target Cell
      participant ExternalReceiver as Network Receiver
      participant MedicalServer as Protocol Server
  
      Nanobot->>+TargetCell: Read DNA Marker (Index)
      TargetCell-->>-Nanobot: Marker confirmed
      Nanobot->>+ExternalReceiver: Transmit Index signal
      ExternalReceiver->>+MedicalServer: Relay Index over network
      MedicalServer->>MedicalServer: Resolve Index to Protocol URL
      MedicalServer-->>-ExternalReceiver: Return Protocol URL
      ExternalReceiver->>Nanobot: Transmit instructions from URL
  

2.2. Large-Scale Infrastructure Indexing

• Enabling Description: A system for civil engineering and infrastructure management where drones or ground-based robotic platforms are the scanning devices. The "index" is a unique identifier derived from the analysis of a structure's physical properties, such as its unique pattern of cracks in concrete (via LiDAR scanning), its acoustic resonance signature (via ultrasonic sensors), or its thermal dissipation map (via infrared thermography). This complex, multi-modal index is transmitted to a central infrastructure management server. The server's database maps these structural signatures to URLs for the structure's digital twin, real-time stress sensor data streams, or historical maintenance records.
• Diagram:

  graph TD
      subgraph Drone Platform
          A[LiDAR Scanner]
          B[Ultrasonic Sensor]
          C[Thermal Camera]
      end
      Drone Platform -- 1. Scan Structure --> D(Bridge Segment)
      D -- 2. Return Physical Data --> Drone Platform
      Drone Platform -- 3. Compute Structural Index --> E{Index Processor}
      E -- 4. Transmit Index --> F[Infrastructure Server]
      F -- 5. Lookup URL --> G[Digital Twin Database]
      F -- 6. Return Digital Twin URL --> E
      E -- 7. Access URL --> H[Live Sensor Feed & Maintenance Logs]
  

---

3. Derivative Implementations based on Cross-Domain Application

The claimed method can be directly applied to industries far removed from its initial context of consumer products.

3.1. Aerospace: In-Situ Component Verification

• Enabling Description: During pre-flight checks or maintenance, an avionics technician uses an Augmented Reality (AR) visor. The visor's camera identifies a component's unique, laser-etched serial number or a 2D matrix code. The visor's software sends this index to a secure, distributed ledger maintained by the aircraft manufacturer and regulatory bodies. The ledger resolves the index to a URL pointing to an immutable record containing the component's manufacturing date, flight hours, stress test results, and authorized software version. The AR visor overlays this information directly onto the technician's view of the physical component.
• Diagram:

  sequenceDiagram
      participant Technician as AR Visor
      participant EngineComponent as Aircraft Part
      participant Resolver as Secure Resolver
      participant Ledger as Distributed Ledger
  
      Technician->>+EngineComponent: Visually scan etched code (Index)
      EngineComponent-->>-Technician: Code acquired
      Technician->>+Resolver: Transmit Index
      Resolver->>+Ledger: Query for component record URL
      Ledger-->>-Resolver: Return immutable record URL
      Resolver-->>-Technician: Return URL
      Technician->>Technician: Fetch and display data from URL in AR overlay
  

3.2. AgTech: Precision Farming Protocol Retrieval

• Enabling Description: An autonomous agricultural rover captures high-resolution imagery and soil sensor data from a specific plot of land. An onboard processor analyzes this data to create a "geospatial health index" for that plot, identifying specific nutrient deficiencies or pest infestations. This index is transmitted to a central AgTech cloud platform. The platform's database maps the index to a URL that points to a precise, machine-readable "prescription file" (e.g., specifying a variable-rate application of fertilizer or a targeted micro-dose of pesticide). The rover then downloads and executes the instructions from this URL.
• Diagram:

  flowchart LR
      A[Rover: Scan Soil & Image] --> B{Generate Geospatial Health Index};
      B --> C[Transmit Index to AgTech Cloud];
      C --> D[Cloud DB: Resolve Index to Prescription URL];
      D --> E[Return URL to Rover];
      E --> F[Rover: Download & Execute Prescription File];
  

3.3. Consumer Electronics: Dynamic Device Provisioning

• Enabling Description: A consumer purchases a new IoT device (e.g., smart lightbulb, security camera). During the setup process, the user's smartphone scans a QR code on the device. The QR code contains a unique, one-time provisioning token (the "index"). The smartphone app transmits this token to the manufacturer's provisioning server. The server validates the token, associates the device's hardware ID with the user's account, and returns a unique URL. This URL points to a temporary, signed firmware package and a set of network credentials specific to that user's smart home ecosystem. This automates and secures the onboarding process.
• Diagram:

  erDiagram
      USER_DEVICE ||--o{ IOT_DEVICE : scans
      USER_DEVICE {
          string App
          string ProvisioningToken
      }
      IOT_DEVICE {
          string HardwareID
          string QRCode
      }
      USER_DEVICE ||--|{ PROVISIONING_SERVER : transmits
      PROVISIONING_SERVER {
          string TokenValidation
          string URL_Generation
      }
      PROVISIONING_SERVER }o--|| FIRMWARE_SERVER : points_to
      FIRMWARE_SERVER {
          string SignedFirmware
          string NetworkCredentials
      }
  

---

4. Derivative Implementations based on Integration with Emerging Technology

The core process is enhanced by integrating it with modern computational and networking paradigms.

4.1. AI-Driven Predictive Resource Caching

• Enabling Description: When a user scans an index, the resolver server does not just return a single URL. It uses a predictive AI model, trained on user behavior, to return a manifest of related URLs and resources. For example, scanning a bag of coffee beans (index) returns the URL for the product page, but the AI also pushes URLs for brewing instructions, customer reviews, and a coupon for a related product. The user's device, running an AI agent, intelligently pre-fetches and caches these resources in the background, anticipating the user's next clicks and providing a near-instantaneous experience.
• Diagram:

  sequenceDiagram
      participant UserDevice as User Device (with AI Agent)
      participant AI_Resolver as AI Resolver Server
      participant ContentServers as Multiple Content Servers
  
      UserDevice->>+AI_Resolver: Transmit Index (e.g., coffee UPC)
      AI_Resolver->>AI_Resolver: 1. Lookup Primary URL <br/> 2. Predict related content
      AI_Resolver-->>-UserDevice: Return Manifest [URL_main, URL_reviews, URL_coupon]
      UserDevice->>UserDevice: AI Agent parses manifest
      par
          UserDevice->>+ContentServers: Request main content from URL_main
      and
          UserDevice->>+ContentServers: Pre-fetch/cache content from URL_reviews & URL_coupon
      end
  

4.2. IoT Real-Time Digital Twin Linkage

• Enabling Description: Every physical product with an IoT component (e.g., a smart appliance, an industrial motor) is marked with a persistent identifier (e.g., QR code). Scanning this index sends a request to a digital twin resolver server. The server returns a URL that loads a web-based dashboard. This dashboard is populated with real-time data by using the same initial index to subscribe to a WebSocket or MQTT stream originating directly from the physical object's sensors. This creates a direct, real-time link between the physical object and its interactive digital representation simply by scanning the object itself.
• Diagram:

  flowchart TD
      A[User scans QR code on Smart Appliance] --> B{Index sent to Digital Twin Server};
      B --> C[Server returns URL for Web Dashboard];
      A --> D[User Device loads Dashboard from URL];
      B -- Also provides MQTT Topic based on Index --> D;
      E[IoT Appliance] -- Publishes real-time data to MQTT Topic --> D;
      D -- Displays live data --> F[User View];
  

4.3. Blockchain-Enabled Provenance and Action URLS

• Enabling Description: An item in a supply chain (e.g., a batch of organic produce) is tagged with a QR code containing a unique identifier registered on a blockchain. When a user scans this index, the device queries a resolver smart contract on the blockchain. The smart contract does two things: 1) it returns the URL of the product's public provenance explorer, showing its journey from farm to shelf, and 2) it returns a unique, single-use URL that allows the current owner to execute a transaction on the blockchain, such as "Mark as Received" or "Transfer Ownership," by signing a message with their cryptographic key. This links the physical scan to both verifiable data and a state-changing network action.
• Diagram:

  sequenceDiagram
      participant User as User Wallet/Device
      participant Product as Physical Product
      participant ResolverContract as Blockchain Smart Contract
      participant ProvenanceExplorer as Web App
  
      User->>+Product: Scan QR Code (Index)
      User->>+ResolverContract: Query with Index
      ResolverContract-->>-User: Return {provenance_URL, action_URL}
      User->>+ProvenanceExplorer: Access provenance_URL
      ProvenanceExplorer-->>-User: Display supply chain history
      User->>User: User clicks action_URL to initiate ownership transfer
  

---

5. Derivative Implementations based on Inverse/Failure Modes

The system can be designed for resilience, graceful degradation, and offline functionality.

5.1. Embedded Fallback and Peer-to-Peer Resolution

• Enabling Description: A 2D barcode (e.g., QR code) is encoded with two data elements: the primary index for online resolution, and a secondary, compressed data payload containing essential information (e.g., product name, safety warnings). The user device software is designed to first attempt online resolution. If no network is detected, it falls back to decoding and displaying the local data. Furthermore, the index can be a content-addressable hash (e.g., an IPFS CID). If the primary HTTP server is down, the device can attempt to resolve the same index over a peer-to-peer network like IPFS or BitTorrent, retrieving the content from other users who have cached it.
• Diagram:

  flowchart TD
      A[Scan QR Code] --> B{Network Available?};
      B -- Yes --> C[Transmit Index to HTTP Server];
      C --> D{Server Responds?};
      D -- Yes --> E[Load Content from URL];
      B -- No --> F[Decode Local Fallback Data from QR Code];
      F --> G[Display Local Content];
      D -- No --> H[Attempt to Resolve Index on P2P Network (IPFS)];
      H --> E;
  

---

6. Combination Prior Art with Open-Source Standards

6.1. Combination with W3C Decentralized Identifiers (DID)

• Enabling Description: The system is implemented using the W3C DID standard. The barcode on an object contains a DID (e.g., did:example:123456789). A user device scans the barcode and uses a universal DID resolver library to resolve the DID. The resolver queries the underlying verifiable data registry (e.g., a blockchain or a trusted database) associated with the did:example method. It retrieves the corresponding DID Document, a standardized JSON file. This document contains a service endpoint section, which lists one or more service URLs for interacting with the object (e.g., a URL for its homepage, another for its API, and a third for its warranty registration). The user's device can then present these options or connect to the primary service. This approach removes the need for a centralized, proprietary resolver server.

6.2. Combination with OAuth 2.0/OpenID Connect

• Enabling Description: The system is used to initiate secure interactions. A user scans a QR code on a trusted device (e.g., a personal computer screen, a point-of-sale terminal) to log into a service. The QR code contains a unique, short-lived index. The user's mobile device transmits this index to an identity provider's server. This server, instead of returning a simple URL, uses the index to identify a specific authentication session and returns a URL that initiates an OAuth 2.0 or OpenID Connect authentication flow. By visiting this URL, the user can securely approve the login or transaction on their trusted mobile device, which already has an authenticated session with the identity provider.

6.3. Combination with the MQTT Protocol

• Enabling Description: The system is integrated into an industrial or home IoT environment using the open MQTT standard. A technician or user scans a barcode on a sensor or actuator. The index (e.g., the device's serial number) is sent to a local network server. The server's database maps this index not to an HTTP URL, but to a set of MQTT topics, such as devices/A7-3B-C1/telemetry for receiving data and devices/A7-3B-C1/command for sending instructions. The scanning device then automatically subscribes to the telemetry topic to display live data and presents controls to publish messages to the command topic, effectively using the barcode scan to link directly into the device's real-time messaging channels.