Arithmetic Processing Offload with Subsequent-Function Proxy Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing offload systems face challenges in achieving low latency and resource efficiency when synchronously or asynchronously calling multiple functions, as they require multiple network round trips and consume significant network and CPU resources.
Innovation Solution
An arithmetic processing offload system that includes a client and server, utilizing a subsequent function determination part and proxy execution part to determine and execute subsequent functions locally, reducing the number of network calls and maintaining function interface transparency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If multiple functions are called synchronously via network offloading, then resource saving is achieved, but latency increases
Solution Approach 1:
The patent applies preliminary action by having the server execute subsequent functions in advance before the client actually calls them. The server's function execution part pre-performs functions that are likely to be called, storing results temporarily. When the client calls these functions, the results are already available or nearly ready, significantly reducing network round-trip latency while maintaining resource-efficient synchronous processing.
Solution Approach 2:
The patent implements beforehand cushioning by preparing function results in advance on the server side. The system anticipates client function calls and pre-computes results, creating a buffer of ready-to-return data. This cushioning effect absorbs the network latency that would otherwise occur during synchronous function calls, allowing the client to receive results quickly without incurring full network round-trip delays for each function call.
2Loss of time
If multiple functions are called asynchronously via network offloading, then low latency is achieved, but resource consumption increases
Solution Approach 1:
The patent applies self-service by enabling the server to autonomously determine and execute subsequent functions without waiting for explicit client requests. The function execution part on the server automatically identifies which functions should be called next and executes them independently. This self-service mechanism reduces the need for continuous client-server communication overhead, achieving low latency while optimizing resource usage compared to traditional asynchronous approaches.
3Loss of energy
If function calls are reduced via proxy execution, then network resource usage decreases, but interface transparency must be maintained
Solution Approach 1:
The patent uses an intermediary approach by introducing a proxy execution mechanism that sits between the client and server function calls. The proxy on the server side receives function call requests from the client, determines whether subsequent functions should be executed, and manages their execution transparently. This intermediary layer reduces network resource usage by batching and optimizing function calls while maintaining interface transparency, as the client continues to use standard function call interfaces without modification.
Data Source
AI summary
A server includes: a function call information receiver-parser part that extracts function call information from data received from a client; a subsequent function necessity determination part that determines whether a callee function is indicated by the function call information; and a subsequent function proxy execution part that, when it is determined that a callee function is indicated, instructs a function execution part to perform proxy execution of a subsequent function corresponding to the callee function. The client includes a subsequent function call proxy responder part that, upon reception of a notification of an execution result of the callee function from the server, notifies a user application of a response of the callee function for which the execution result has been received, and responds, as a proxy of the server, to a call to the subsequent function, which call is made by the user application in response to the notification.