Obviousness

Obviousness Analysis of US Patent 7784058

Date of Analysis: May 14, 2026

Patent under Review: US 7,784,058 B2 ("the '058 patent")

Subject: Computing system having user mode critical system elements as shared libraries.

I. Introduction

This analysis examines the obviousness of the claims of US patent 7,784,058 under 35 U.S.C. § 103. The '058 patent, filed on September 21, 2004, and claiming a priority date of September 22, 2003, describes a computing system architecture where "critical system elements" (CSEs), traditionally located in the operating system kernel, are replicated and made available to software applications in user mode through shared libraries. This allows each application to have its own instance of a CSE, avoiding conflicts that can arise from a single, centralized system element.

II. Claim Analysis

The independent claims of the '058 patent are central to this analysis. Claim 1, for instance, outlines a computing system with:

• An operating system kernel with its own critical system elements (OSCSEs) running in kernel mode.
• A shared library containing replicas of at least some of these critical system elements (SLCSEs) for use by applications in user mode.
• These SLCSEs are accessible to applications and, when accessed, become part of the application.
• Crucially, an instance of an SLCSE provided to a first application runs in that application's context and is not shared with other applications. A second application can simultaneously use its own unique instance of a corresponding SLCSE.

III. Prior Art References

The following prior art references, cited in the '058 patent, are relevant to the obviousness analysis:

• US 6,212,574 B1 ("'574 patent"): Discloses a "user mode proxy" for kernel mode operations. This allows certain operating system services to be handled in user mode, which can improve performance and stability. It teaches the general concept of moving functionality from the kernel to user space.
• US 2004/0025165 A1 ("'165 application"): Describes methods for extending operating system functionality for an application. This includes providing application-specific services that can augment or replace standard OS services. This reference suggests a motivation to customize the operating environment for individual applications.
• US 5,481,706 A ("'706 patent"): Details a system for creating thread-safe shared libraries. This is relevant as it addresses the safe sharing of code among multiple concurrent threads or processes, a foundational concept for the implementation of the '058 patent's shared libraries.
• US 2003/0101292 A1 ("'292 application"): Focuses on a system and method for isolating applications from each other. This is a key motivation behind the '058 patent, which seeks to prevent conflicts between applications by providing them with their own instances of critical system elements.
• US 6,260,075 B1 ("'075 patent"): Describes a system for providing a shared global offset table for a common shared library. This is a more technical reference related to the implementation of shared libraries and how they can be efficiently used by multiple applications.

IV. Obviousness Combinations

A person having ordinary skill in the art (POSITA) at the time of the invention would have been motivated to combine the teachings of these references to arrive at the invention claimed in the '058 patent.

A. Combination of '574 patent and '165 application:

The '574 patent teaches moving kernel operations to user mode via a proxy for performance and stability benefits. The '165 application provides a motivation for this by suggesting the extension of OS functionality on a per-application basis. A POSITA would have found it obvious to combine these teachings. For instance, to provide an application with a specific version of a network stack (a critical system element), one could implement a user-mode version of that stack (as suggested by the '574 patent's general principle) and provide it to the application as an extension (as motivated by the '165 application). This combination directly leads to the core idea of the '058 patent: providing application-specific, user-mode versions of critical system elements.

B. Combination of '292 application and '574 patent:

The '292 application explicitly addresses the problem of application isolation to prevent conflicts. The '058 patent presents its invention as a solution to this very problem. A POSITA, seeking to achieve the isolation described in the '292 application, would have looked for mechanisms to provide applications with their own resources. The '574 patent's teaching of moving kernel components to user mode would have been an obvious mechanism to consider. By providing each application with its own user-mode instance of a critical system element, the desired isolation is achieved. The use of shared libraries would be a standard and well-known method for delivering such user-mode components to applications.

C. Addition of '706 patent and '075 patent to the combinations:

The '706 and '075 patents address the technical implementation of shared libraries. While the primary inventive concept of the '058 patent lies in the architectural decision to provide per-application CSEs in user mode, the use of shared libraries is a necessary component of its implementation. A POSITA, having conceived of the core idea from the '574, '165, and '292 references, would have naturally turned to well-established technologies like shared libraries for implementation. The '706 and '075 patents demonstrate that the techniques for creating and managing shared libraries were well within the state of the art. Therefore, the implementation of the claimed invention using shared libraries would have been a matter of routine engineering for a POSITA.

V. Motivation to Combine

A person of ordinary skill in the art in 2003 would have been a software engineer or architect with experience in operating system design. They would have been familiar with the trade-offs between monolithic and microkernel architectures, the use of shared libraries, and the challenges of application compatibility and resource conflicts.

The primary motivations to combine the prior art would have been:

• Performance: Moving services out of the kernel can, in some cases, reduce the overhead of kernel-to-user mode transitions.
• Stability: A fault in a user-mode service will typically only crash the application using it, not the entire operating system.
• Flexibility and Customization: Providing application-specific versions of system services allows for greater flexibility. For example, an application could use a newer version of a library without affecting other applications on the system.
• Isolation and Security: As described in the '292 application, isolating applications and their resources is a key goal in multi-user and multi-application systems.

These motivations were well-known in the field at the time. The cited prior art references address these same issues and suggest solutions that, when combined, point directly to the invention of the '058 patent.

VI. Conclusion

The claims of US patent 7,784,058 are likely obvious under 35 U.S.C. § 103. The core inventive concept—providing per-application instances of critical system elements in user mode via shared libraries—is a logical and predictable combination of teachings found in the prior art. The motivation to combine these teachings would have been strong for a person of ordinary skill in the art seeking to improve application performance, stability, and isolation on a computing system. The implementation details, such as the use of shared libraries, were also well-established in the art. Therefore, the '058 patent does not appear to represent a non-obvious leap in the field of operating system architecture.