WEB APPLICATION INTERACTION METHOD, APPARATUS, AND SYSTEM

• US 20150271245A1
• Filed: 06/03/2015
• Published: 09/24/2015
• Est. Priority Date: 12/18/2012
• Status: Abandoned Application

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: XU, Wenhua
• Application Number:
  US14/729,471
• Publication Number:
  US 20150271245A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/84 Mapping; Conversion
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Embodiments of the present invention provide a web application interaction method, apparatus, and system that are applied to the communications field and can remove a limitation of a web app opening manner during web app interaction. The method includes: acquiring a URL of a slave web application from an invocation request, where the slave web application is an invoked web application; acquiring a window object of the slave web application from a mapping relationship between a URL and a window object of the slave web application by using the URL of the slave web application; acquiring invocation information of a master web application from the invocation request; and sending the invocation information of the master web application to a window of the slave web application according to the window object of the slave web application, where the master web application is a web application that invokes the slave web application.

Claims

1. A web application interaction method, comprising:

acquiring a uniform resource locator URL of a slave web application from an invocation request, wherein the slave web application is an invoked web application;

acquiring a window object of the slave web application from a mapping relationship between a URL and a window object of the slave web application by using the URL of the slave web application;

acquiring invocation information of a master web application from the invocation request; and

sending the invocation information of the master web application to a window of the slave web application according to the window object of the slave web application, wherein the master web application is a web application that invokes the slave web application.

2. The method according to claim 1, wherein after the acquiring a uniform resource locator URL of a slave web application from an invocation request, the method further comprises:

querying, in the mapping relationship between a URL and a window object of the slave web application, whether the URL of the slave web application exists; and

if the URL of the slave web application does not exist, opening the slave web application and saving a mapping relationship between the URL and the window object of the slave web application.

3. The method according to claim 1, wherein:

the window object comprises a window identifier, a communication type, and a specific communication channel; and

the communication type comprises a data sharing area, a window communication channel, or a browser communication channel.

4. The method according to claim 1, wherein before the acquiring a uniform resource locator URL of a slave web application from an invocation request, the method further comprises:

sending an application programming interface API registration request of the slave web application to a server, wherein the API registration request comprises an API logic script of the slave web application, so that the server returns the API logic script of the slave web application to the master web application after receiving an API acquisition request of the slave web application.

5. The method according to claim 4, wherein before the acquiring a uniform resource locator URL of a slave web application from an invocation request, the method further comprises:

sending a domain registration request of the master web application to the server, wherein the domain registration request comprises domain information and/or path information of the master web application, so that the server saves the domain information and/or path information comprised in the domain registration request.

6. The method according to claim 5, wherein after the acquiring invocation information of a master web application from the invocation request, the method further comprises:

sending a detection request of the master web application to the server, so that the server performs matching between domain information and/or path information of the master web application carried in the detection request and the domain information and/or path information saved by the server; and

receiving detection result information sent by the server, wherein the detection result information carries matching result information.

7. The method according to claim 6, wherein after the detection result information indicates that the matching is successful, the method further comprises:

sending the API acquisition request of the slave web application to the server;

receiving the API logic script of the slave web application sent by the server; and

running the API logic script of the slave web application.

8. A web application interaction method, comprising:

receiving a detection request of a master web application in a browser, wherein the detection request is sent by the master web application and comprises domain information and/or path information of the master web application;

performing matching between the domain information and/or path information of the master web application carried in the detection request and domain information and/or path information saved by a server;

generating detection result information according to a matching result, wherein the detection result information indicates that the matching is successful or that the matching fails; and

sending the detection result information to the master web application in the browser.

9. The method according to claim 8, wherein the method further comprises:

receiving an application programming interface API registration request of a slave web application sent by the browser, wherein the API registration request comprises an API logic script of the slave web application; and

saving the API logic script of the slave web application.

10. The method according to claim 9, wherein the method further comprises:

receiving a domain registration request of the master web application, wherein the domain registration request comprises the domain information and/or path information of the master web application; and

saving the domain information and/or path information comprised in the domain registration request.

11. The method according to claim 10, wherein after the matching is successful, the method further comprises:

receiving an API acquisition request of the slave web application sent by the browser; and

sending the API logic script of the slave web application to the master web application in the browser, so that the master web application in the browser runs the API logic script of the slave web application.

12. A browser, comprising:

a processor, configured to acquire a uniform resource locator URL of a slave web application from an invocation request, wherein the slave web application is an invoked web application; and

a memory, configured to acquire a window object of the slave web application from a mapping relationship between a URL and a window object of the slave web application by using the URL of the slave web application, wherein;

the processor is further configured to acquire invocation information of a master web application from the invocation request; and

the processor is further configured to send the invocation information of the master web application to a window of the slave web application according to the window object of the slave web application, wherein the master web application is a web application that invokes the slave web application.

13. The browser according to claim 12, wherein the processor is further configured to:

query, in the mapping relationship between a URL and a window object of the slave web application, whether the URL of the slave web application exists; and

if the URL of the slave web application does not exist, open the slave web application and save a mapping relationship between the URL and the window object of the slave web application.

14. The browser according to claim 13, wherein:

the window object comprises a window identifier, a communication type, and a specific communication channel; and

the communication type comprises a data sharing area, a window communication channel, or a browser communication channel.

15. The browser according to claim 14, wherein the browser further comprises:

a sender, configured to send an application programming interface API registration request of the slave web application to a server, wherein the API registration request comprises an API logic script of the slave web application, so that the server returns the API logic script of the slave web application to the master web application after receiving an API acquisition request of the slave web application.

16. The browser according to claim 15, wherein:

the sender is further configured to send a domain registration request of the master web application to the server, wherein the domain registration request comprises domain information and/or path information of the master web application, so that the server saves the domain information and/or path information comprised in the domain registration request.

17. The browser according to claim 16, wherein:

the sender is further configured to send a detection request of the master web application to the server, so that the server performs matching between domain information and/or path information of the master web application carried in the detection request and the domain information and/or path information saved by the server; and

the browser further comprises;

a receiver, configured to receive detection result information sent by the server.

18. The browser according to claim 17, wherein:

the sender is further configured to send the API acquisition request of the slave web application to the server;

the receiver is further configured to receive the API logic script of the slave web application sent by the server; and

the processor is further configured to run the API logic script of the slave web application.

19. A server, comprising:

a receiver, configured to receive a detection request of a master web application in a browser, wherein the detection request is sent by the master web application and comprises domain information and/or path information of the master web application;

a processor, configured to perform matching between the domain information and/or path information of the master web application carried in the detection request and domain information and/or path information saved by a server, wherein;

the processor is further configured to generate detection result information according to a matching result, wherein the detection result information indicates that the matching is successful or that the matching fails; and

a sender, configured to send the detection result information to the master web application in the browser.

20. The server according to claim 19, wherein:

the receiver is further configured to receive an application programming interface API registration request of a slave web application sent by the browser, wherein the API registration request comprises an API logic script of the slave web application; and

the server further comprises;

a memory, configured to save the API logic script of the slave web application.

21. The server according to claim 20, wherein:

the receiver is further configured to receive a domain registration request of the master web application, wherein the domain registration request comprises the domain information and/or path information of the master web application; and

the memory is further configured to save the domain information and/or path information comprised in the domain registration request.

22. The server according to claim 21, wherein:

the receiver is further configured to receive an API acquisition request of the slave web application sent by the browser; and

the sender is further configured to send the API logic script of the slave web application to the master web application in the browser, so that the master web application in the browser runs the API logic script of the slave web application.

23. A web application interaction system, comprising:

a browser, comprising;

a processor, configured to acquire a uniform resource locator URL of a slave web application from an invocation request, wherein the slave web application is an invoked web application; and

a memory, configured to acquire a window object of the slave web application from a mapping relationship between a URL and a window object of the slave web application by using the URL of the slave web application, wherein;

the processor is further configured to acquire invocation information of a master web application from the invocation request; and

the processor is further configured to send the invocation information of the master web application to a window of the slave web application according to the window object of the slave web application, wherein the master web application is a web application that invokes the slave web application;

a server, comprising;

a receiver, configured to receive a detection request of a master web application in a browser, wherein the detection request is sent by the master web application and comprises domain information and/or path information of the master web application;

a processor, configured to perform matching between the domain information and/or path information of the master web application carried in the detection request and domain information and/or path information saved by a server, wherein;

the processor of the server is further configured to generate detection result information according to a matching result, wherein the detection result information indicates that the matching is successful or that the matching fails; and

a sender, configured to send the detection result information to the master web application in the browser.