Patents
Literature
Patsnap Eureka AI that helps you search prior art, draft patents, and assess FTO risks, powered by patent and scientific literature data.

2 results about "Remote function call" patented technology

A Remote Function Call (RFC) is the call or remote execution of a Remote Function Module in an external system. In the SAP system, these functions are provided by the RFC interface system. The RFC interface system enables function calls between two SAP systems.

A method for remote function call in a security application based on TEE specification

ActiveCN115964103BInterprogram communicationExecution paradigmsRemote function callCall site
The application relates to a method for remote function calling in a security application based on TEE specification, which comprises the following steps: 1) a client application calls TEEC_InvokeCommand, and a security application backs up an entry function context; 2) the security application executes business logic and judges whether remote function calling is needed, if not, the execution is completed, and a calling result is returned; if yes, calling parameters are encapsulated, an interrupt function context is backed up, and the client application is quickly returned; 3) the client application analyzes the calling parameters, system calling and encapsulated calling result, and calls TEEC_InvokeCommand; 4) the security application acquires a remote function calling context, restores a calling site, analyzes a remote calling result, and executes step 2). Compared with the prior art, the application has the advantages that the security application can use the function in a rich execution environment through a remote calling mode at any time, and parameters of any type and in any direction can be transmitted.
Owner:SHANGHAI TRUSTKERNEL INFORMATION TECH CO LTD

Remote computations using trusted execution environments

PendingUS20260154398A1Platform integrity maintainanceRemote function callSoftware engineering
To improve the ability of an application to process sensitive data, a trusted execution environment (TEE) can be used to store and compute sensitive sources (e.g., variables) from a set of sensitive sources. To make the TEE application language independent, a process can transform specific statements from the application code to a remote function call that can access the TEE. To identify these statements to transform, a forward and backward taint analysis can be performed to identify the statements to be transformed. The identified statements can be transformed into enclave instructions. At runtime, a cloak enclave environment within the TEE can execute the enclave instructions as called by the remote call in the application code. The sensitive sources in the identified statements are maintained and computed in the cloak enclave, grouped by a function runtime instance, which is uniquely identified by uuids.
Owner:TEXAS A&M UNIVERSITY