Method and apparatus for remotely running application program

• US 10,057,364 B2
• Filed: 12/07/2015
• Issued: 08/21/2018
• Est. Priority Date: 10/30/2013
• Status: Active Grant

• Current Assignee: Huawei Cloud Computing Technologies Company Limited (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Chen, Pu, Wei, Kaizhi
• Primary Examiner(s): Nguyen, Quang N
• Application Number:
  US14/961,270
• Publication Number:
  US 20160088109A1
• Time in Patent Office: 988 Days
• Field of Search: 709203, 709206, 709217, 709219, 709223, 709224, 709226, 709228, 709230, 709231, 709232, 709238, 704 9, 704231, 726 14, 726 29, 717172, 37926509
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata

Abstract

A method for remotely running an application program. A client acquires an application program from a server, runs the application program on the client, and detects whether the application program triggers an application programming interface (API) invocation request. If the application program triggers the API invocation request, the client determines that the client or the server executes API invocation according to a preset invocation policy. A device resource of the client can be used to execute a part of the API invocation, which enhances efficiency in remote running of the application program and improves user experience. In addition, the latest data obtained according to a result of application program running can be saved onto the server, which ensures data access security.

Claims

1. A method for remotely running an application program, comprising:

acquiring, by a client, an application program from a server and running the application program on the client;

detecting, by the client, whether the application program triggers an application programming interface (API) invocation request intended for a system API on the server;

intercepting, by the client, the API invocation request intended for the system API;

determining, by the client according to a preset invocation policy, that the client or the server executes API invocation when the application program triggers the API invocation request;

generating, by the client, a local API invocation request according to the API invocation request when determining that the client executes the API invocation;

invoking, by the client, a device resource of the client and executing local API invocation according to the local API invocation request, so as to generate an execution result of the local API invocation;

sending, by the client, the execution result of the local API invocation to the application program;

generating, by the client, a remote API invocation request according to the API invocation request when determining that the server executes the API invocation;

sending, by the client, the remote API invocation request to the server, the remote API invocation request being used to instruct the server to execute remote API invocation and return an execution result of the remote API invocation;

receiving, by the client from the server, the execution result of the remote API invocation; and

sending, by the client, the execution result of the remote API invocation to the application program.

2. The method according to claim 1, wherein acquiring, by the client, the application program from the server and running the application program on the client comprises:

sending, by the client to the server, an acquisition request for a target program of the application program, the acquisition request being used to instruct the server to return the target program of the application program;

receiving, by the client, the target program from the server; and

executing, by the client, the target program, so as to run the application program on the client.

3. The method according to claim 1, wherein determining, by the client according to the preset invocation policy, that the client or the server executes API invocation comprises:

determining, by the client, whether the API invocation needs to be executed using the device resource of the client;

determining that the client executes the API invocation when the API invocation needs to be executed using the device resource of the client; and

determining that the server executes the API invocation when the API invocation does not need to be executed using the device resource of the client.

4. The method according to claim 3, wherein the preset invocation policy comprises determining that the API invocation does not need to be executed using the device resource of the client when the API invocation is to request to write data into a registry of the server, request to save, onto the server, data obtained after running of the application program is ended, or request to access a network using a network resource of the server.

5. The method according to claim 1, wherein sending, by the client, the remote API invocation request to the server comprises:

serializing, by the client, the remote API invocation request so as to generate request data of the remote API invocation, the request data carrying information about a serialized remote API invocation request;

encrypting, by the client, the request data; and

sending, by the client, the encrypted request data to the server.

6. The method according to claim 1, wherein receiving, by the client from the server, the execution result of the remote API invocation comprises:

receiving, by the client from the server, response data of the API invocation, the response data carrying information about a serialized execution result of the remote API invocation;

decrypting, by the client, the response data, when the response data is encrypted; and

deserializing, by the client, the response data that is decrypted, so as to obtain the execution result of the remote API invocation.

7. An apparatus for remotely running an application program, comprising:

a processor configured to;

acquire an application program from a server and run the application program on a client;

detect whether the application program triggers an application programming interface (API) invocation request intended for a system API on the server;

intercept the API invocation request intended for the system API;

determine, according to a preset invocation policy, that the client or the server executes API invocation when the application program triggers the API invocation request;

generate a local API invocation request according to the API invocation request when it is determined that the client executes the API invocation;

invoke a device resource of the client and execute local API invocation according to the local API invocation request, so as to generate an execution result of the local API invocation;

send the execution result of the local API invocation to the application program;

generate a remote API invocation request according to the API invocation request when it is determined that the server executes the API invocation;

send the remote API invocation request to the server, the remote API invocation request being used to instruct the server to execute remote API invocation and return an execution result of the remote API invocation;

receive, from the server, the execution result of the remote API invocation; and

send the execution result of the remote API invocation to the application program.

8. The apparatus according to claim 7, wherein the processor is further configured to:

send an acquisition request for a target program of the application program to the server, the acquisition request being used to instruct the server to return the target program of the application program;

receive the target program from the server; and

execute the target program, so as to run the application program on the client.

9. The apparatus according to claim 7, wherein the processor is further configured to:

determine whether the API invocation needs to be executed using the device resource of the client;

determine that the client executes the API invocation when the API invocation needs to be executed using the device resource of the client; and

determine that the server executes the API invocation when the API invocation does not need to be executed using the device resource of the client.

10. The apparatus according to claim 9, wherein the preset invocation policy comprises determining that the API invocation does not need to be executed using the device resource of the client, when the API invocation is to request to write data into a registry of the server, request to save, onto the server, data obtained after running of the application program is ended, or request to access a network using a network resource of the server.

11. The apparatus according to claim 7, wherein the processor is further configured to:

serialize the remote API invocation request, so as to generate request data of the remote API invocation, the request data carrying information about a serialized remote API invocation request;

encrypt the request data; and

send the encrypted request data to the server.

12. The apparatus according to claim 7, wherein the processor is further configured to:

receive response data of the API invocation from the server, the response data carrying information about a serialized execution result of the remote API invocation;

decrypt the response data when the response data is encrypted; and

deserialize the response data that is decrypted, so as to obtain the execution result of the remote API invocation.