Obviousness

The provided patent text for US6771381 does not contain a "Prior Art section" listing specific prior art documents or references. Instead, it provides "Prior art keywords" (electronic, applications, management system, paper, computer data) and a "Prior art date" of 1998-11-13. To conduct an obviousness analysis under 35 U.S.C. § 103, specific prior art references are necessary. Since no such references are present in the provided patent text, I will perform live web searches using the provided keywords and the indicated prior art date to identify relevant prior art.

Search for Relevant Prior Art

Given the "Prior art date" of 1998-11-13, the following search queries will focus on technologies available before this date.

The search results provide a solid foundation for an obviousness analysis, demonstrating the existence of many key technologies before the priority date of US6771381 (November 13, 1998).

Obviousness Analysis of US Patent 6771381 under 35 U.S.C. § 103

A patent claim is obvious if "the differences between the claimed invention 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." (35 U.S.C. § 103). This analysis requires identifying:

1. The scope and content of the prior art.
2. The differences between the prior art and the claims at issue.
3. The level of ordinary skill in the pertinent art.
4. Motivation to combine prior art references.

Level of Ordinary Skill in the Art:
A person having ordinary skill in the art (PHOSITA) in 1998 in the domain of distributed computer architecture and document management would likely possess a Bachelor's or Master's degree in Computer Science or a related field, with several years of experience in software development, network programming, and enterprise system integration. This individual would be familiar with operating systems, various programming languages (including C/C++), network protocols, database systems, and client-server architectures. They would also understand the challenges of integrating disparate software systems and managing digital and scanned documents.

Prior Art Identified and their Relevance:

The search results reveal several key areas of prior art existing before November 13, 1998:

• Electronic Document Management Systems (EDMS): EDMS emerged in the 1980s to digitize paper records, with early systems focusing on document imaging (scanning, indexing, retrieving paper records). By the early 1990s, EDMS included version control, access management, and full-text retrieval. Workflow automation became a focus in the 1990s, integrating document management with business processes. Web-based systems for accessing and managing documents started appearing in the late 1990s. Companies like Laserfiche (founded 1974, first DOS-based document imaging system 1987) and FileNet (founded 1982, combined imaging with workflow) were pioneers. TOWER Software introduced Captura in 1998, regarded by some as the first modern DMS.
• Optical Character Recognition (OCR): Commercial OCR software became viable in the 1980s and 1990s as scanning technology and computing power improved, enabling conversion of scanned documents into editable text.
• APIs and Application Integration (Middleware): Remote Procedure Calls (RPCs) existed from the 1970s-1990s, allowing programs to invoke functions on remote systems. Middleware, including technologies like Common Object Request Broker Architecture (CORBA) and Component Object Model (COM), emerged in the 1990s to integrate disparate applications and allow them to communicate regardless of language. COM, a binary-interface technology from Microsoft, was introduced in 1993, enabling language-neutral object use across different programming languages, contexts, processes, and machines. COM was the basis for OLE, OLE Automation, and ActiveX, and DCOM (Distributed COM) extended COM to work across networks in 1996. COM relied on the Windows Registry for dynamic discovery of components. APIs, in general, gained popularity in the 1990s for exchanging data between applications across the internet using standard protocols.
• Distributed Computing Systems: The concept of distributed systems, where inter-communicating components are located on different networked computers, was a field of study in computer science prior to 1998. Architectures for distributed systems, specifying standard services working uniformly, were discussed in the late 1980s and early 1990s. Client-server architecture is a common pattern for distributed computing.

Obviousness Combinations and Rationale

The independent claims of US6771381 generally revolve around a system and method for providing a uniform interface to diverse "engines" (core technologies), often in a distributed environment, to facilitate "virtual copying" of electronic documents and paper.

Combination 1: EDMS + OCR + Middleware (e.g., COM/DCOM) for "Virtual Copying" (Claims 1, 12, 15, 20, 23, 30, 37, 44, 51, 58)

• Prior Art:

  • Electronic Document Management Systems (EDMS): Provided the foundational capability to scan paper documents into electronic images, store them, retrieve them, and manage workflows.
  • Optical Character Recognition (OCR): Enabled the conversion of scanned document images into editable, searchable text.
  • Middleware (COM/DCOM): Enabled different applications and components to communicate and integrate, even across networks. COM specifically provided a binary-interface standard for reusable components and was extended to DCOM for network operation before 1998.

• Rationale for Combination: A PHOSITA in 1998, faced with the growing need to manage paper and electronic documents (as highlighted by the "corporate paper problem" mentioned in the patent), and already using EDMS and OCR, would have been motivated to integrate these functionalities seamlessly into existing business applications. The limitations of proprietary formats and custom communication (as noted in the evolution of APIs and integration platforms) would drive the desire for standardized interfaces.

  • The concept of a "virtual copier" (copying paper from one device/location to another device/application/Internet, potentially with a single "GO" operation) would be an obvious extension of existing EDMS capabilities combined with networking and application integration. Existing EDMS already allowed scanning to electronic storage and distribution via email or fax. The idea of a "single GO operation" mirrors the physical photocopier which had been ubiquitous for decades.
  • Middleware technologies like COM/DCOM were specifically designed to allow "disparate applications to communicate, regardless of the languages in which they were developed" and to "standardize communication protocols, reducing the cost and complexity of developing new integrations." A PHOSITA would naturally turn to such technologies to create a uniform "wrapper" or "interface" (as described in the patent's claims for engines/APIs) to integrate diverse imaging devices (scanners, digital copiers) and business applications (e.g., accounting systems, as discussed in the patent) for document handling. The use of COM-based interfaces for modules and object registration in a system registry (like Windows Registry for COM components) was also known.
  • The goal of "integrating electronic images into existing applications without the need to modify the destination application" (Claim 30) would be a direct motivation for using middleware, which aimed to "isolate changes in one application from impacting others."
  • The modular architecture described for Virtual Copier (Input, Output, Process, Client, Server modules) is a standard software engineering practice for complex systems, and particularly for integrating diverse technologies, where each module can manage a specific aspect (e.g., input from a scanner, output to a printer, processing like OCR).

Combination 2: Distributed Systems Architecture + Component-based Middleware (e.g., DCOM/CORBA) for Managing Diverse Engines (Claims 1, 12, 15, 20, 23)

• Prior Art:

  • Distributed Systems Architectures: Discussions and frameworks for distributed systems were prominent in the late 1980s and early 1990s, aiming for integrated systems with uniform access, security, and management across networked computers. Client-server architecture was a known pattern.
  • Component Object Model (COM) and Distributed COM (DCOM) / CORBA: These middleware technologies were specifically designed to enable communication and object invocation between components, including those located on different machines in a distributed environment. DCOM, extending COM across networks, was introduced in 1996. RPC, a precursor to modern APIs, allowed programs to execute functions on other machines over networks.

• Rationale for Combination: A PHOSITA dealing with "diverse set of independent core technologies ('engines')" (as per the patent's abstract) in a distributed computing environment would naturally seek a standardized way to manage and interact with them.

  • The problem of "near-infinite variety of styles" of C-level APIs, leading to difficulties in integration, would motivate the use of a component-based middleware approach. Middleware (like COM/DCOM/CORBA) provided "generic interfaces that applications can use to communicate, replacing brittle point-to-point integration". These technologies were explicitly developed to standardize communication protocols and enable disparate applications to communicate, regardless of their underlying language or implementation.
  • The idea of a "component factory" or a structured approach to "wrapping" diverse APIs into a consistent interface is inherently suggested by the nature and purpose of component-based middleware like COM. COM aimed to encapsulate reusable components as binary entities, allowing for updates without breaking compatibility, by defining interfaces separate from implementation. The use of multiple layers for API migration (e.g., Level 1 to Level 2 to Level 3) would be an obvious software engineering approach to incrementally standardize complex, varied APIs, a known challenge in application integration.

Combination 3: EDMS + Workflow Automation for "Single Programming Step" Integration (Claims 30, 37, 44, 51, 58, and related methods)

• Prior Art:

  • EDMS with Workflow Automation: By the 1990s, EDMS focused on "workflow automation," integrating document management systems with business processes to streamline operations and automate document-related tasks. This included features like routing documents for approval and automatic archiving.
  • Application Integration Middleware (EAI): The field of Enterprise Application Integration (EAI) emerged in the 1990s to integrate disparate applications and data using middleware, aiming to be flexible and isolate changes.

• Rationale for Combination: The patent emphasizes "adding at least one of electronic document and paper processing with a single programming step" or "one step method of supporting paper within electronic business process application optionally including legacy systems with no or minimal reprogramming" (Claim 30, 37, 44, 51, 58).

  • A PHOSITA, already implementing EDMS with workflow automation to streamline paper processes and familiar with EAI solutions, would be motivated to simplify the integration of document processing into existing business applications. The "one-step programming method" could be viewed as an optimization or abstraction layer built upon existing middleware and workflow concepts.
  • The very purpose of middleware and EAI was to "simplify access so developers can focus on other areas of the application" and "reduce the cost and complexity of developing new integrations." Achieving a "single programming step" for common document operations would be a natural and desirable goal for a PHOSITA seeking to improve efficiency and ease of integration in enterprise systems using these known technologies.

Image Viewer Process (Claim 26):

• Prior Art: Document imaging systems, which allowed scanning and electronic storage of documents, were available from the 1980s. Graphical user interfaces (GUIs) were introduced by Apple and Macintosh in the early 1990s, greatly facilitating the ability to view documents from a computer screen. Computer processing speeds also increased, making document software on desktops practical.
• Rationale for Obviousness: The ability to view electronic document images and select different viewing perspectives is a standard feature of any image viewing or document management software developed in the 1990s. GUIs were common, and allowing users to customize their viewing experience (e.g., zoom, rotate, fit to page, single page/two page view, etc.) would be an obvious design choice for a PHOSITA developing such a system. Retrieving and displaying images based on user selection is fundamental functionality.

Conclusion on Obviousness:

Based on the available prior art, many aspects of US patent 6771381 appear to be combinations of existing technologies that would have been obvious to a PHOSITA by the priority date of November 13, 1998.

• The core concept of managing electronic documents, scanning paper, and integrating these into business workflows was well-established in Electronic Document Management Systems (EDMS) by the 1990s.
• The use of middleware technologies like COM/DCOM to provide a uniform interface for diverse applications and components, especially in a distributed environment, was a known solution for application integration challenges. These technologies were specifically designed to overcome interoperability issues and standardize communication.
• The modularization of a complex system into Input, Output, Process, Client, and Server modules is a fundamental software engineering principle.
• Extending the metaphor of a physical copier ("virtual copier" with a "GO" button) to electronic document handling would be an obvious user interface design choice, given the widespread familiarity with physical copiers. The functional elements (select source, select destination, execute copy) directly parallel existing physical devices.
• The goal of simplifying integration (e.g., "single programming step") or integrating with legacy applications without modification were known challenges that middleware and EAI solutions aimed to address.
• Image viewing functionalities, including selectable perspectives, were standard in image processing software.

A PHOSITA, motivated by the desire to streamline document management, reduce paper, and improve application interoperability in enterprise settings (problems explicitly recognized in the late 1990s), would have found ample reason to combine these known elements. The patent's inventive step appears to lie in the specific application and integration of these existing concepts and technologies in a "virtual copying" context, rather than in the invention of the underlying architectural components or integration methods themselves. The overall architecture and process, while potentially novel in its specific combination and marketing as a "virtual copier," leverages capabilities already present in the prior art, and the motivations for combining them would have been apparent to a skilled practitioner.