Patent 7986426
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-flash
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
Obviousness Analysis of US Patent 7986426 Under 35 U.S.C. § 103
Claims 1-11 of US7986426 were previously challenged in Inter Partes Review (IPR) IPR2013-00302 and found unpatentable by the PTAB on grounds of anticipation under 35 U.S.C. § 102 by individual prior art references, namely XNS (Ex. 1002) and Salgado (U.S. Patent No. 5,872,569, Ex. 1005). An invention that is anticipated by a single prior art reference necessarily lacks novelty and is therefore also considered obvious. Consequently, for claims 1-11, the question of obviousness through combinations of prior art references is, strictly speaking, subsumed by the PTAB's finding of anticipation.
However, in addressing the request for an obviousness analysis involving combinations of prior art, a hypothetical scenario can be considered where claims 1-11 were not fully anticipated by a single reference but would have been obvious to a person having ordinary skill in the art (POSA) by combining multiple references.
Prior Art References for Obviousness Analysis
The relevant prior art identified in the IPR proceeding includes:
- XNS (Ex. 1002): While the full content of "XNS" as used in Ex. 1002 is not provided, "XNS" commonly refers to the Xerox Network Systems architecture, a suite of network protocols and concepts for distributed computing developed by Xerox Corporation. Such a reference would generally disclose foundational principles of distributed systems, network communication, and potentially distributed object models or inter-process communication mechanisms.
- Salgado (U.S. Patent No. 5,872,569, Ex. 1005): Titled "Method and apparatus for managing documents using document identification in a distributed environment," this patent explicitly addresses document management within a distributed computing context.
Hypothetical Obviousness Argument and Motivation to Combine
Claims 1-11 of US7986426 generally relate to a distributed computer architecture and process for document management, specifically focusing on migrating program-specific Application Programmer Interfaces (APIs) to a generic interface. This is achieved by building objects for diverse "engines" (independent core technologies) to provide substantially uniform access, particularly in a distributed environment, and describes architectural layers for engine management, configuration, and function calls.
A Person Having Ordinary Skill in the Art (POSA) in the field of distributed document management systems, at the time of the invention (priority date October 18, 1996), would have been motivated to combine the teachings of a distributed network system (such as XNS) with a distributed document management system (such as Salgado) to achieve the functionalities claimed in US7986426.
Motivation to Combine:
- Need for Integrated Document Management: Businesses in the late 1990s were increasingly digitizing operations and facing challenges in managing electronic documents across various devices and applications in networked environments. The patent US7986426 itself notes that "Businesses continue to automate more processes, but managing the associated paper is often ignored, resulting in inefficiency and higher costs." A POSA would recognize the need for robust systems to handle documents in a distributed manner.
- Leveraging Distributed Computing Foundations: A reference like XNS would provide a POSA with established principles and architectures for building distributed computer systems, including how various components or services can communicate and operate across a network. This knowledge would be foundational for any distributed application, including document management.
- Enhancing Distributed Document Management with Flexible Engine Integration: Salgado (U.S. Patent No. 5,872,569) would teach methods and apparatus for managing documents in a distributed environment, likely including aspects of document storage, retrieval, and identification. However, integrating diverse, third-party document processing "engines" (e.g., Optical Character Recognition (OCR), barcode recognition, forms processing, as discussed in US7986426) with their disparate APIs into such a system would present an engineering challenge.
- Routine Engineering for API Abstraction: A POSA, faced with the task of integrating multiple "engines" with distinct APIs into a distributed document management system, would find it obvious to implement an abstraction layer or generic interface to standardize communication. This approach simplifies development, reduces complexity, and promotes reusability, which are common goals in software engineering. The concepts of "building an object for each engine" to provide "substantially uniform access" and using "engine management functions," "protective wrappers," and "standardized calls" (as described in claims 1, 2, 3, 4, 6, 7, 8, 10, and 11) would be considered routine software design patterns for managing diverse components in an object-oriented, distributed system.
- Achieving Seamless Operation: The "Virtual Copier" concept, allowing seamless electronic copying of paper and electronic documents between devices and applications, including over the Internet (as broadly described in US7986426), represents a desirable functional outcome for a distributed document management system. A POSA combining the networking capabilities taught by XNS with the document management specifics of Salgado would be motivated to devise an architecture that facilitates such seamless interaction and integration of various document-related functionalities.
Therefore, even if claims 1-11 were not individually anticipated, a POSA would have been motivated to combine the general distributed computing principles (e.g., as found in XNS) with specific distributed document management techniques (e.g., as found in Salgado) and apply common software engineering practices for API abstraction and component integration to arrive at the architecture and process claimed in US7986426. This combination would have been driven by the clear need for efficient and flexible document handling in increasingly networked business environments.
Generated 5/29/2026, 8:50:51 PM