Obviousness — US Patent 8805728

Based on my analysis of the provided prior art, here is an assessment of the obviousness of US Patent 8,805,728 under 35 U.S.C. § 103.

Obviousness Analysis (35 U.S.C. § 103)

An invention is considered obvious if the differences between the claimed invention and the prior art are such that the invention as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art (POSITA). This analysis considers combinations of prior art references.

The core of independent claim 1 of the '728 patent is a three-party system where a user device scans a product barcode (an "index"), sends that index to an intermediary server, receives a "pointer" (like a URL) back from the server, and then uses that pointer to connect directly to a final destination computer. This architecture avoids encoding the entire, often lengthy, URL directly into the barcode. The following combinations of the cited prior art would have rendered this claimed method obvious.

Combination 1: U.S. Patent 6,049,835 (Gagnon) in view of U.S. Patent 5,804,803 (Crandall)

What Gagnon Teaches: Gagnon discloses the fundamental server-side architecture of the '728 patent. It teaches a system for providing easy access to websites using short, multi-digit "jump codes" (the '728 patent's "index"). A user submits this index to a remote server, which maintains a database linking these short codes to full URLs (the '728 patent's "pointers"). The server resolves the index to the pointer and directs the user's device to the final destination. Gagnon explicitly addresses the problem of long, cumbersome URLs, which is a key problem the '728 patent also purports to solve.
What Gagnon Lacks: Gagnon's primary embodiment relies on the user manually typing the jump code. It does not teach the initial step of scanning a bar code symbol to acquire the index automatically.
What Crandall Teaches: Crandall explicitly teaches a system where a user device, equipped with a scanner, reads a code from a physical object to retrieve an object identifier. This identifier is then used in a network transaction to retrieve related information. Crandall thus teaches the use of a scanner for automated, error-free entry of an identifier from an object to initiate a network lookup.
Motivation to Combine: A person of ordinary skill in the art seeking to improve upon Gagnon's system would have been motivated to replace the manual entry of the "jump code" with a more efficient and user-friendly input method. Manual data entry is inherently slower and more prone to error than automated methods. Barcode scanning, as taught by Crandall, was a well-known and commercially ubiquitous method for rapid and accurate data input from physical objects at the time. The combination would be a simple substitution of one known input element (manual entry) for another (scanning) to enhance the usability of Gagnon's lookup system. This would have yielded the predictable result of a faster and more reliable system for linking to web resources, thereby arriving at the invention claimed in the '728 patent.

Combination 2: U.S. Patent 5,918,214 (Perkowski) in view of U.S. Patent 5,804,803 (Crandall)

What Perkowski Teaches: Perkowski is highly relevant because it teaches the specific database concept at the heart of the '728 patent's commercial application: linking product identification numbers, such as those found in a UPC on an "article of commerce," to network addresses (URLs) of manufacturers' websites. It directly discloses the "predetermined relationships that link an index to a pointer" using the exact type of index (product codes) contemplated by the '728 patent.
What Perkowski Lacks: Perkowski focuses on the database system and a user searching that database. It does not explicitly teach the complete, automated workflow as claimed: a user device scanning the code, automatically transmitting the index, the server returning the pointer, and the device using the pointer to establish a direct connection.
What Crandall Teaches: Crandall teaches this exact automated workflow. It discloses scanning a code on an object, transmitting the resulting identifier to a server, receiving a network address in return, and using that address to access a remote resource.
Motivation to Combine: A POSITA starting with Perkowski's valuable database linking product codes to websites would be motivated to create the most seamless user experience possible. The goal would be to allow a consumer holding a product to access the related website with minimal effort. Crandall provides the blueprint for this exact type of seamless interaction with a physical object. It would have been obvious to apply the automated scanning-and-linking method taught by Crandall to Perkowski's specific and commercially valuable product database. This combination would directly connect the physical product (via its UPC, per Perkowski) to its online resource using the automated workflow of Crandall, achieving the predictable and highly desirable result of a "scan-to-connect" functionality for consumer products. This combination teaches all elements of claim 1.