The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Sep. 02, 2014
Filed:
Apr. 18, 2008
Narasimha Rao S.s. Nagampalli, Bellevue, WA (US);
Alireza Dabagh, Kirkland, WA (US);
Alok Manchanda, Redmond, WA (US);
Taroon Mandhana, Redmond, WA (US);
Sharad Mittal, Redmond, WA (US);
Olivier Contant, Redmond, WA (US);
Noel W. Anderson, Bellevue, WA (US);
Bernard Aboba, Bellevue, WA (US);
Jerry E. Peterson, Bellevue, WA (US);
Narasimha Rao S.s. Nagampalli, Bellevue, WA (US);
Alireza Dabagh, Kirkland, WA (US);
Alok Manchanda, Redmond, WA (US);
Taroon Mandhana, Redmond, WA (US);
Sharad Mittal, Redmond, WA (US);
Olivier Contant, Redmond, WA (US);
Noel W. Anderson, Bellevue, WA (US);
Bernard Aboba, Bellevue, WA (US);
Jerry E. Peterson, Bellevue, WA (US);
Microsoft Corporation, Redmond, WA (US);
Abstract
A computer with an extensible framework for facilitating communication between a software component installed on the computer and a device driver that executes functions in response to vendor-specific command objects (e.g., OIDs). The framework defines data structures and a standardized format for defining and implementing private interfaces. After selecting a private interface that is commonly supported by a software component and a driver, a private communication path may be established by an operating system component to facilitate the transfer of command information from the software component to the driver. The private communication path allows commands packaged as OIDs to be routed from software components to intended drivers. By defining private interfaces which route commands from software components to intended drivers, the extensible framework mitigates potential incompatibilities that may arise when drivers created by different vendors include OIDs with the same OID value.