# US 2009/0158303 A1 · Accessing function from different addressing bit system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2009/0158303 A1 - Document ID: US20090158303A1 - Status: Published application - Kind: A1 - Application number: 11/958,178 - Filed: 2007-12-17 - Published: 2009-06-18 - Earliest claimed: 2007-12-17 - Assignees: CA, Inc. - Inventors: Ralf Saborowski - Web page: https://patentgrep.com/patent/US20090158303A1 ## CPC - G06F 9/45516: {Runtime code conversion or optimisation} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A system and method of accessing functions includes running n-bit based code in an n-bit supporting system environment. An m-bit based provider object is instantiated in an m-bit hardware and operating system environment server. The provider object provides an interface between the n-bit based code and m-bit based server functions. m-bit based server functions are accessed from the n-bit based code via the m-bit based provider object. ## Claims ### Claim 1 A method of accessing functions, the method comprising: running n-bit based code in an n-bit supporting environment; instantiating an m-bit based provider object in an m-bit hardware and operating system environment server, wherein the provider object provides an interface between the n-bit based code and m-bit based server functions; and accessing m-bit based server functions from the n-bit based code via the m-bit based provider object. ### Claim 2 (depends on 1) The method of claim 1 wherein the provider object includes m-bit based functions APIs exposed as COM interfaces. ### Claim 3 (depends on 2) The method of claim 2 wherein the provider object is implemented using DLL surrogation. ### Claim 4 (depends on 3) The method of claim 3 wherein the DLL surrogation is implemented by using a default DLL surrogation host provided by the m-bit system or a custom DLL surrogation host. ### Claim 5 (depends on 2) The method of claim 2 wherein the provider object is implemented as a standalone m-bit application using a local COM out of process server. ### Claim 6 (depends on 1) The method of claim 1 wherein the functions comprise application services. ### Claim 7 (depends on 6) The method of claim 6 wherein the application services comprise management and configuration functionality through Microsoft Windows® PowerShell with application specific .NET extensions. ### Claim 8 (depends on 1) The method of claim 1 wherein n is 32 and m is 64. ### Claim 9 (depends on 1) The method of claim 1 wherein an application module for managing/monitoring an application running in isolated 32-bit WoW64 access the m-bit based server functions from the n-bit based code via the m-bit based provider object. ### Claim 10 (depends on 1) The method of claim 1 wherein m-bit based server functions are accessed by the n-bit based code via the m-bit based provider object via a simple method call with zero or more parameters passed by value on invocation. ### Claim 11 (depends on 1) The method of claim 1 wherein m-bit based server functions are accessed by the n-bit based code via the m-bit based provider object via a complex method call with zero or more parameters passed by value on invocation to access multiple pieces of information. ### Claim 12 (depends on 1) The method of claim 1 wherein m-bit based server functions are accessed by the n-bit based code via the m-bit based provider object via a generic method call with m-bit embedded code passed on invocation. ### Claim 13 A system comprising: a provider that runs in an m-bit environment and exposes m-bit functionality of an application through m-bit based APIs to m-bit functions; wherein the provider exposes such APIs to n-bit based agents via COM interfaces. ### Claim 14 (depends on 13) The system of claim 13 wherein the m-bit functions comprise management and configuration interfaces. ### Claim 15 (depends on 14) The system of claim 14 wherein the application comprises Microsoft Exchange 2007. ### Claim 16 (depends on 1) The method of claim 1 wherein n is 32 and m is 64. ### Claim 17 A computer readable medium having instructions for causing a computer to implement a method of accessing functions, the method comprising: instantiating an m-bit based provider object in an m-bit hardware and operating system environment server, wherein the provider object provides an interface between the n-bit based code and m-bit based server functions; receiving n-bit based method calls from an n-bit based agent; and accessing m-bit based server functions from the n-bit based agent via the m-bit based provider object. ### Claim 18 (depends on 17) The computer readable medium of claim 17 wherein the received n-bit based method calls relate to m-bit based functions related to managing monitoring and configuring an n-bit based application. ### Claim 19 (depends on 17) The computer readable medium of claim 17 wherein the provider object includes m-bit based function APIs as COM interfaces and is implemented using DLL surrogation, a default DLL surrogation host provided by the m-bit system or a custom DLL surrogation host. ### Claim 20 (depends on 17) The computer readable medium of claim 17 wherein the n-bit method call comprises a simple method call with zero or more parameters passed by value on invocation, a complex method call with zero or more parameters passed by value on invocation to access multiple pieces of information, or a generic method call with m-bit embedded code passed on invocation. ### Claim 21 A method of accessing functions, the method comprising: instantiating a proxy object in an application running n-bit based code; accessing, via the n-bit proxy object, an m-bit based provider object in an m-bit hardware and operating system environment server, wherein the provider object provides an interface between the n-bit based code and m-bit based server functions; and receiving results from m-bit based server functions via the m-bit based provider object.