US 6771381

Here's a concise summary of US patent 6771381:

US Patent 6771381: Distributed computer architecture and process for virtual copying

• Title: Distributed computer architecture and process for virtual copying
• Current Assignee: MPHJ Tech Investments LLC
• Inventor: Laurence C. Klein
• Filing Date: 1999-11-12
• Issue Date (Publication Date): 2004-08-03
• Abstract: A computer architecture and process is disclosed for managing a diverse set of independent core technologies ("engines") using a single consistent framework. The architecture balances two seemingly opposing requirements: the need to provide a single consistent interface to many different engines with the ability to access the unique features of each engine. The benefit of the architecture is that it enables a company to rapidly "wrap" a sophisticated technology so that other high-level developers can easily learn and implement the core technology. The computer architecture is therefore a middleware or enabling technology. The computer architecture may be implemented using a client server and/or intranet and/or internet operating environments.

Plain-Language Overview of Independent Claims:

US6771381 has numerous claims. Below is an overview of the first independent claim from each major claim category (computer implemented process, computer implemented method, computer architecture, distributed computer system, distributed computer implemented process, image viewer process, computer readable tangible medium, computer data management system, computer data administration system, computer information management system, workstation data management system, computer data management apparatus):

• Claim 1 (Computer Implemented Process): This claim describes a computer-implemented process for standardizing access to different "engines" (core technologies). It involves building an object for each engine to provide a uniform way to access the engine and its settings. The process includes an engine management function to interface with the engine's original API, providing error handling and administration, and an engine configuration function to convert API calls into standardized calls, also handling loading and unloading the engine. Finally, an engine function manages these standardized calls, ensuring consistent access to the engine and its settings.

• Claim 12 (Computer Implemented Method): This claim outlines a computer-implemented method to standardize diverse technologies. It involves defining a consistent interface for individual software components that represent different technologies and then integrating multiple "engines" (core technologies) to use this consistent interface. The method also includes managing these components automatically or uniformly using a predefined object manager and the consistent interface.

• Claim 15 (Computer Architecture): This claim describes a computer architecture designed to standardize diverse core technologies. It includes an engine management layer that interfaces with the specific API of an engine and handles its management and administration. An engine configuration layer transforms the API calls into a standard format. An engine layer then manages these standardized calls for each engine, providing consistent access to the engine and its settings.

• Claim 20 (Distributed Computer System): This claim details a distributed computer system for standardizing program-specific APIs. It features a server containing at least one "engine" with an interface offering features to be executed. The system also includes at least one engine component that executes these features by mapping a consistent interface to the engine's original interface. Furthermore, at least one client is connected to the server (and optionally to other servers) and includes an object manager layer that communicates with and manages the engine component on the server through the consistent interface.

• Claim 23 (Distributed Computer Implemented Process): This claim describes a distributed computer-implemented process for integrating program-specific APIs into a generic interface. It involves providing an engine with an interface and features on a server. An engine component is provided on either the server or another connected server, configured to execute the engine's features by mapping a consistent interface to the engine's native interface. A client, connected to the server, has an object manager layer that communicates with and manages this engine component using the consistent interface.

• Claim 26 (Image Viewer Process): This claim describes an image viewer process for viewing electronic document images and performing viewing operations. It involves a user selecting from multiple image viewing perspectives, each offering a different predefined way to view the document. The user then selects the document to be viewed, the process retrieves it, and then displays the selected document according to the user's chosen viewing perspective.

• Claim 29 (Computer Readable Tangible Medium): This claim covers a computer-readable tangible medium that stores instructions for executing a computer-implemented process. This process integrates a program-specific Application Programmer Interface (API) from its original state into a generic interface by building an object for each engine, providing uniform access to the engine and its settings.

• Claim 30 (Computer Data Management System): This claim describes a computer data management system (for electronic images, graphics, and documents) capable of transmitting data to external devices and applications, locally or via the Internet. It includes memory for storing interface protocols and a processor that implements these protocols as a software application. The system integrates images using software for seamless replication to other devices, applications, and the Internet, and integrates electronic images into existing applications without modification. It features an interface with a "GO" operation for copying images between physical devices, applications, and the Internet, and can add electronic document and paper processing with a single programming step.

• Claim 37 (Computer Data Administration System): This claim is substantially identical in structure and function to Claim 30, but refers to a "computer data administration system" instead of a "computer data management system."

• Claim 44 (Computer Information Management System): This claim is substantially identical in structure and function to Claim 30, but refers to a "computer information management system" and "information" instead of "data" or "document" in some contexts.

• Claim 51 (Workstation Data Management System): This claim is substantially identical in structure and function to Claim 30, but refers to a "workstation data management system."

• Claim 58 (Computer Data Management Apparatus): This claim is substantially identical in structure and function to Claim 30, but refers to a "computer data management apparatus."

CAFC 2026 Dockets:
I have searched for US patent 6771381 in CAFC 2026 dockets. The provided search results for CAFC in 2026 discuss various patent cases, but none specifically mention US patent 6771381. While the patent has had litigation in the past (as indicated by the Google Patents "Family has litigation" section showing cases filed in Vermont District Court, Court of Appeals for the Federal Circuit, Louisiana Eastern District Court, Texas Western District Court, and a PTAB case IPR2013-00309), there is no authoritative information from the provided search results indicating active litigation concerning this specific patent number in the CAFC dockets for 2026.

Uncertainties:
The current assignee, "MPHJ Tech Investments LLC", is listed as an assumption by Google Patents, noting that "Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed." Therefore, while it is the listed assignee, its accuracy is noted as an assumption.