Patent 5905248
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
Active provider: Google · gemini-2.5-pro
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
Obviousness Analysis of U.S. Patent 5,905,248 under 35 U.S.C. § 103
This analysis evaluates whether the invention claimed in U.S. Patent 5,905,248 would have been obvious to a Person Having Ordinary Skill in the Art (PHOSITA) at the time the invention was made, considering the prior art. The filing date is August 22, 1997, which establishes the relevant timeframe for the state of the art.
Legal Standard for Obviousness
Under 35 U.S.C. § 103, a patent claim is invalid "if the differences between the subject matter sought to be patented and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art." This requires an analysis of the scope and content of the prior art, the differences between the prior art and the claims at issue, and the level of ordinary skill in the pertinent art.
Person Having Ordinary Skill in the Art (PHOSITA)
At the time of filing in mid-1997, a PHOSITA would be an individual with a bachelor's degree in computer science or a related field, and several years of experience in client-server application development, network programming, and emerging World Wide Web technologies. This person would have been familiar with:
- The function of barcode scanners as computer input devices (keyboard wedges).
- The architecture of the Internet, including TCP/IP, HTTP, and the syntax of Uniform Resource Locators (URLs).
- HTML and the capabilities of web browsers like Netscape Navigator and Internet Explorer.
- Emerging technologies for creating interactive web content, most notably Java Applets, which were introduced in 1995 and had gained significant traction by 1997.
Obviousness Combination of Prior Art
The independent claims (1, 15, and 29) of the '248 patent are likely obvious in view of a combination of U.S. Patent 5,602,377 ("the '377 patent") and the general state of the art concerning the World Wide Web, as exemplified by patents like U.S. Patent 5,794,210 ("the '210 patent") and the well-known capabilities of Java Applets at the time.
1. Base Reference: U.S. Patent 5,602,377
The '377 patent discloses the core concept of using a scanner to read an encoded symbol on a physical item to initiate a remote transaction with a central computer. The system described allows a user to, for example, scan a product in a catalog to place an order. This reference teaches the fundamental "scan-to-transact" link between a physical object and a remote commercial action.
However, the '377 patent is deficient in two key areas relative to the '248 claims:
- It describes communication over a telephone network or a direct connection to a specific central computer, not via the open, standardized protocols of the World Wide Web (HTTP and URLs).
- It does not disclose the use of a web document containing an interactive, automatically executing "applet" to manage the transaction.
2. Motivation to Modify the '377 Patent
By 1997, the World Wide Web was experiencing explosive growth and was rapidly becoming the dominant platform for networked communication and electronic commerce. The '210 patent, filed in 1996, demonstrates that the Internet was already a well-established environment for conducting commercial transactions and user interactions.
A PHOSITA looking at the system in the '377 patent would have immediately recognized its limitations. A proprietary, direct-dial system is inefficient, difficult to scale, and lacks the universal accessibility of a web-based system. There would have been a strong and obvious motivation to update the '377 system by replacing its proprietary network infrastructure with the standardized, ubiquitous, and far more cost-effective architecture of the World Wide Web.
This motivation is not based on hindsight, but on the clear and well-documented technological and commercial trends of the mid-1990s. Porting existing networked applications to the Web was a common and logical engineering task at the time.
3. Applying Web Technologies to the '377 Concept
Making the '377 system web-based would involve predictable, non-inventive design choices for a PHOSITA in 1997:
- Replacing the Central Computer with a Web Server: The "central computer" in the '377 patent would naturally be replaced by a web server running HTTP server software.
- Encoding a URL in the Barcode: To direct a client computer to the correct web server and the specific transaction page, the standard and only logical addressing mechanism on the Web was a URL. Therefore, it would have been obvious to encode the URL for the transaction page in the barcode, rather than the proprietary product data and connection information used in the '377 system.
- Using a Web Browser as the Client: The client-side terminal would be a standard computer running a web browser, which was the universal tool for accessing resources on the Web.
This combination of the '377 patent's "scan-to-transact" method with standard Web architecture directly teaches the core elements of the '248 claims: a client system with a browser, a code reader, and a URL-encoded symbol that, when read, directs the browser to a specific web document on an Internet server.
4. The "Transaction-Enabling Applet"
The final key element of the claims is the "transaction-enabling applet" embedded in the web document that is "automatically launched and executed."
By 1997, Java Applets were a widely-publicized and well-understood technology. Their primary purpose, as promoted by Sun Microsystems and supported by browsers like Netscape, was to create rich, interactive, application-like experiences within a web page, overcoming the limitations of static HTML. For a PHOSITA tasked with creating a robust transaction interface on a web page, using a Java Applet was not an inventive leap but rather the selection of the most suitable, state-of-the-art tool for the job. The ability for an applet to launch automatically upon page load was an inherent and standard feature of how applets were implemented using the <APPLET> tag in HTML. The '248 patent itself describes this standard implementation (Detailed Description, Col. 14-16).
Therefore, once the decision was made to build the transaction system on the Web, employing a Java Applet to handle the transaction logic was an obvious design choice.
Conclusion
A person having ordinary skill in the art in 1997 would have found it obvious to combine the teachings of the prior art to arrive at the invention claimed in U.S. Patent 5,905,248. The '377 patent taught the core concept of scanning a symbol to initiate a remote transaction. The immense commercial and technical momentum of the World Wide Web, as evidenced by patents like '210 and general industry knowledge, would have provided a clear motivation to adapt the '377 system to the web's architecture. This adaptation would have involved the predictable use of web servers, URLs encoded in barcodes, and web browsers. Finally, implementing the transaction interface itself using a Java Applet was the obvious choice for creating an interactive application within a web page at that time. Each element existed, and the motivation to combine them in the claimed manner was driven by predictable trends and a desire for efficiency, scalability, and interoperability.
Generated 4/28/2026, 4:51:03 AM