US 8488173

Here's a concise summary of US Patent 8488173:

Title: Distributed computer architecture and process for document management

Assignee: MPHJ Tech Investments LLC.

Inventors: Laurence C. Klein.

Filing Date: July 14, 2011.

Issue Date: July 16, 2013.

Abstract:
A computer architecture and process for document management is disclosed, generally related to a computer architecture and process for stand-alone and/or distributed environments, and more particularly to a computer architecture and process using a substantially uniform management in a stand-alone and/or distributed computing environment including, for example, client server and/or intranet and/or Internet operating environments.

Plain-Language Overview of Independent Claims:

The patent US8488173B2 contains several independent claims. The following provides a plain-language overview of each:

• Claim 1 (Computer Implemented Process): This claim describes a computer-implemented process for migrating a program-specific Application Programmer Interface (API) from its original state into a generic interface. This is achieved by building an object for each "engine" (independent core technology). This object provides a consistent way to access the engine and its settings. The process includes an engine management function that interfaces with the program-specific API, providing a protective wrapper for function calls, trapping errors, and managing errors. It also includes an engine configuration function that transforms API calls into standardized calls and provides functionality for safely loading and unloading the engine. Finally, an engine function manages these standardized calls, ensuring uniform access to the engine and its settings.

• Claim 13 (Computer Implemented Method): This claim outlines a computer-implemented method for migrating at least one program-specific API into a generic interface by creating an object for each engine, providing substantially uniform access to the engine and its settings. The method involves defining a consistent interface for individual object components representing diverse technologies, migrating multiple engines to this consistent interface, and automatically or uniformly managing these object components using a predefined object manager and the consistent interface.

• Claim 26 (Computer Architecture): This claim describes a computer architecture that migrates at least one program-specific API from its original state into a generic interface by building an object for each engine, providing substantially uniform access to the engine and its settings. The architecture comprises three layers: an engine management layer (interfacing with the program-specific API, providing management and administration), an engine configuration layer (transforming API calls into standardized calls), and an engine layer (managing the standardized calls for each engine).

• Claim 37 (Distributed Computer System): This claim details a distributed computer system that migrates a program-specific API into a generic interface by building an object for each engine, providing uniform access to the engine and its settings. The system includes a server with at least one engine having an interface for executing features, and at least one engine component configured to execute these features by mapping a consistent interface to the engine's interface. It also includes at least one client connectable to the server (and optionally another server), with an object manager layer that communicates with and manages the engine component on the server via the consistent interface.

• Claim 42 (Distributed Computer Implemented Process): This claim describes a distributed computer-implemented process that migrates a program-specific API into a generic interface by building an object for each engine, providing uniform access. The process involves providing, on a server, at least one engine with an interface and features to be executed. It also includes providing, on the server and/or another connectable server, at least one engine component configured to execute the engine's features by mapping a consistent interface. Furthermore, it involves providing, on a client connectable to the server (and optionally another server), an object manager layer that communicates with and manages the engine component via the consistent interface.

• Claim 47 (Image Viewer Process): This claim describes an image viewer process for viewing at least one document image (including electronic document images) and performing viewing operations. The process includes steps for a user to select one of multiple image viewing perspectives, select the document image to be viewed, retrieve the document image, and display it according to the user's selected perspective.

• Claim 51 (Computer Data Management System): This claim describes a computer data management system capable of transmitting electronic images, graphics, and documents to various external destinations (devices and applications) locally or via the Internet. It includes memory storing interface protocols and a processor that implements these protocols as a software application. The system can seamlessly integrate and replicate images into other devices/applications (including via the Internet) without modifying the destination application. It also features an interface enabling image copying between physical devices, applications, and the Internet using a single "GO" operation, and the capability to add electronic document and paper processing with a single programming step.

• Claim 58 (Computer Data Management System): This claim describes a computer data management system that functions as an electronic image, graphics, and document management system. It is capable of transmitting electronic images, graphics, and documents to external destinations (devices and applications) locally and via the Internet. The system offers three key capabilities: seamlessly replicating images using software into other devices/applications and via the Internet; integrating electronic images into existing applications without modification; and an interface (software application) that enables copying images between physical devices, applications, and the Internet using a single "GO" operation, along with the ability to add electronic document and paper processing with a single programming step.

• Claim 60 (Computer Data Management System - Common Interface): This claim specifies a computer data management system for managing and transmitting electronic images, graphics, and documents to external destinations (devices and applications) locally and via the Internet. It includes memory storing a common and universal interface protocol and a processor that implements this protocol as a software application for interfacing and communicating with these external destinations.

• Claim 62 (Computer Readable Tangible Medium): This claim covers a computer-readable tangible medium that stores instructions for implementing a process driven by a computer. This process operates on an electronic image, graphics, and document management system capable of managing and transmitting electronic content to external destinations locally and via the Internet. The instructions control the computer to store a common and universal interface protocol in memory and implement it as a software application for interfacing and communicating with the external destinations.

• Claim 64 (Computer Data Management System - Single Function Copy): This claim describes a computer data management system capable of transmitting electronic images, graphics, and documents to external destinations locally and via the Internet. It includes: a single-function copy operation linking devices, applications, and the Internet (including a "go" operation, single-function paper copy between devices and software, and between software and devices); a one-step programming method to add paper support to electronic business processes (optionally including legacy systems with minimal reprogramming); and a copier interface implemented as a software application (a virtual copier interface for presenting copying operations to/from digital imaging devices and software applications in a single step, and providing direct access to tutorials/options from a main application window).

• Claim 66 (Server Module): This claim focuses on a server module within a computer data management system. It includes means for: enabling virtual copy operations (initiating, canceling, resetting); maintaining a registry of available input, output, and process modules (read on startup, copied to a modules object); maintaining currently active input, output, and process modules for a copy operation in a program object and saving them in a process template file; and maintaining complete document information for a current file being copied, saving it in a document template file. The server module also includes at least one server module API, comprising COM-based interfaces for a modules object, a program object, a document object, a system management method object, and a system management event object.

• Claim 68 (Computer Data Management Method): This claim describes a computer data management method for a system capable of transmitting electronic content to external destinations locally and via the Internet. The method comprises steps for: integrating an image using software for seamless replication into other devices/applications and via the Internet; integrating electronic images into existing applications without modification; interfacing via a software application to enable copying images between physical devices, applications, and the Internet using a single "GO" operation; and adding electronic document and paper processing with a single programming step.

• Claim 70 (Server Method): This claim describes a server method for a computer data management system. It includes steps for: initiating, canceling, and resetting the system; maintaining a registry of available input, output, and process modules (read on startup, copied to a modules object); maintaining currently active input, output, and process modules for a copy operation in a program object and saving them in a process template file; and maintaining information regarding a current file being copied and saving it in a document template file.

• Claims 72, 79, 81, 83, 85, 87, 89, 91, 93, 95, 97, 99, 101, 103, 105, 107, 109, 111, 113, 115, 117, 119, 121, 123, 125, 127, 129, 131, 133, 135, 137, 139, 141, 143, 145, 147, 149, 151, 153, 155, 157, 159, 161, 163, 165, 167, 169 (Repetitive Claims with minor variations in terminology): Many subsequent independent claims (e.g., Claims 72, 81, 91, 101, 111, 121, 131, 141, 151, 161) appear to be substantially similar in scope and wording to earlier independent claims (e.g., Claim 51, 58, 60, 62, 64, 66, 68, 70), often replacing "data management system" with "data administration system," "information management system," "workstation data management system," or "computer data management apparatus." They also sometimes vary in the use of "plurality" vs. "one or more" in lists of features, or "memory" vs. "storage" for data storage, or "processor" vs. "data processor." These variations are generally minor and do not significantly alter the fundamental scope of the claimed invention.

CAFC 2026 Dockets for 8488173:
A direct search of the provided Google Search results did not yield specific CAFC 2026 dockets for patent 8488173. The search results indicated general information about accessing CAFC case information, but not a direct link to a docket search. To confirm, a dedicated search of the CAFC docket system would be required.Here's a concise summary of US Patent 8488173:

Title: Distributed computer architecture and process for document management

Assignee: MPHJ Tech Investments LLC.

Inventors: Laurence C. Klein.

Filing Date: July 14, 2011.

Issue Date: July 16, 2013.

Abstract:
A computer architecture and process for document management is disclosed, generally related to a computer architecture and process for stand-alone and/or distributed environments, and more particularly to a computer architecture and process using a substantially uniform management in a stand-alone and/or distributed computing environment including, for example, client server and/or intranet and/or Internet operating environments.

Plain-Language Overview of Independent Claims:

• Claim 1 (Computer Implemented Process): This claim describes a computer process that converts a program's specific API (Application Programmer Interface) into a standard, generic interface. It does this by creating a software "object" for each core technology, or "engine." This object allows consistent access to the engine and its settings. The process involves an "engine management function" that acts as a protective layer for the original API, handling errors and preventing malfunctions. It also includes an "engine configuration function" that translates the original API calls into standardized ones and safely loads/unloads the engine. Finally, an "engine function" manages these standardized calls to ensure consistent access to the engine and its settings.

• Claim 13 (Computer Implemented Method): This claim outlines a computer method for making diverse technologies accessible through a consistent interface. It involves defining a standard interface for individual software components (representing various technologies), migrating multiple "engines" to use this standard interface, and then automatically or uniformly managing these components using a predefined object manager and the established interface.

• Claim 26 (Computer Architecture): This claim describes a computer system design that transforms a program's specific API into a generic interface. It achieves this by building an object for each core technology ("engine"), providing uniform access to the engine and its settings. The architecture consists of three layers: an "engine management layer" that interacts with the specific API for overall engine administration, an "engine configuration layer" that standardizes API calls, and an "engine layer" that manages these standardized calls for each engine.

• Claim 37 (Distributed Computer System): This claim details a distributed computer system where a program's specific API is converted into a generic interface by creating an object for each engine, enabling uniform access to the engine and its settings. The system includes a server hosting at least one engine with an interface for executing specific functions. An "engine component" is configured to execute these functions by mapping a consistent interface to the engine's interface. Additionally, clients can connect to the server (and potentially other servers), with an "object manager layer" on the client communicating with and managing the engine component via the consistent interface.

• Claim 42 (Distributed Computer Implemented Process): This claim describes a distributed computer process for migrating a program's specific API to a generic interface using engine objects for uniform access. The process involves: providing an engine with its interface and features on a server; providing an "engine component" on the server (or another connected server) that executes the engine's features by mapping a consistent interface; and providing an "object manager layer" on a client (connected to the server and potentially other servers) that communicates with and manages the engine component via this consistent interface.

• Claim 47 (Image Viewer Process): This claim describes a process for viewing digital document images. A user selects a desired viewing perspective from several options. The process then allows the user to select an image, retrieves it, and displays it according to the chosen perspective.

• Claim 51 (Computer Data Management System): This claim covers a computer system for managing and transmitting electronic images, graphics, and documents to various external devices and applications, both locally and over the Internet. It uses stored interface protocols and a processor to implement these as a software application. Key capabilities include seamless integration and replication of images without modifying the destination application, an interface that allows copying images between physical devices, applications, and the Internet with a single "GO" operation, and the ability to add electronic document/paper processing with a single programming step.

• Claim 58 (Computer Data Management System - Capabilities): This claim describes a computer data management system that transmits electronic images, graphics, and documents to external destinations locally and via the Internet. It has three main capabilities: seamlessly replicating images using software to other devices/applications and the Internet; integrating electronic images into existing applications without needing to modify them; and providing a software application interface that enables copying images between physical devices, applications, and the Internet with a single "GO" operation, along with the ability to add electronic document and paper processing with a single programming step.

• Claim 60 (Computer Data Management System - Universal Interface): This claim details a computer data management system that manages and transmits electronic images, graphics, and documents to external destinations locally and via the Internet. It features memory storing a common and universal interface protocol, and a processor that implements this protocol as a software application for communicating with these external destinations.

• Claim 62 (Computer Readable Tangible Medium): This claim is for a physical computer-readable storage medium (like a hard drive or solid-state drive) that contains instructions. These instructions, when executed by a computer, implement a process on an electronic image, graphics, and document management system. This system is capable of managing and transmitting electronic content to various external devices and applications, locally and over the Internet. The instructions enable the computer to store and implement a common and universal interface protocol for communication with these external destinations.

• Claim 64 (Computer Data Management System - Single Function Operations): This claim describes a computer data management system for transmitting electronic content to external destinations locally and via the Internet. It includes: a single-function copy operation (a "go" operation) that links devices, applications, and the Internet for copying paper between them; a one-step programming method to add paper support to electronic business processes (even legacy systems, with minimal reprogramming); and a software-implemented "copier interface" (a virtual copier interface) that allows users to copy files and electronic images to and from digital imaging devices and software applications in a single step, while also providing direct access to tutorials and options from the main application window.

• Claim 66 (Server Module): This claim focuses on a server module within a computer data management system. It includes components ("means for") to: initiate, cancel, and reset virtual copy operations; maintain a registry (list) of available input, output, and process modules (read on startup and accessible as a "modules object"); maintain currently active modules for a copy operation in a "program object" and save them in a "process template file"; and maintain information about the current file being copied, saving it in a "document template file." This server module also has an API (Application Programmer Interface) that includes specific COM-based interfaces for managing modules, programs, documents, and system events.

• Claim 68 (Computer Data Management Method - Integration Steps): This claim describes a computer data management method for a system that transmits electronic content to external destinations locally and via the Internet. The method involves several steps: using software to seamlessly integrate and replicate an image into other devices, applications, and the Internet; integrating electronic images into existing applications without modification; providing a software application interface that enables copying images between physical devices, applications, and the Internet with a single "GO" operation; and adding electronic document and paper processing with a single programming step.

• Claim 70 (Server Method): This claim outlines a server method for a computer data management system. The method includes the steps of: initiating, canceling, and resetting the system; maintaining a registry of available input, output, and process modules (read on startup and also stored in a modules object); maintaining the currently active input, output, and process modules for a copy operation in a program object and saving them in a process template file; and maintaining information about the current file being copied and saving it in a document template file.

CAFC 2026 Dockets:
As of April 26, 2026, a search of publicly available information through the provided tools did not yield specific 2026 dockets from the U.S. Court of Appeals for the Federal Circuit (CAFC) directly referencing patent number 8488173. General information about CAFC case records is available, but specific docket entries for this patent in 2026 could not be located through the automated search.