Awakening an application by means of a mobile browser

• US 10,977,103 B2
• Filed: 01/25/2019
• Issued: 04/13/2021
• Est. Priority Date: 07/27/2016
• Status: Active Grant

• Current Assignee: Advanced New Technologies Company Limited (Ant Group Co., Ltd.)
• Original Assignee: Advanced New Technologies Company Limited (Ant Group Co., Ltd.)
• Inventors: Lin, Chuanjie
• Primary Examiner(s): Anya, Charles E
• Application Number:
  US16/257,847
• Publication Number:
  US 20190155668A1
• Time in Patent Office: 809 Days
• Field of Search: None
• CPC Class Codes: G06F 9/44 Arrangements for executing specific programs
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/45529 Embedded in an application, e.g. JavaScript in a Web browser
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32

Abstract

First call data submitted by a mobile browser when a service call for a target application (app) is initiated is received, where the first call data comprises a custom parameter used to invoke the target app and identification information of the mobile browser, and where the identification information comprises package name information of the mobile browser. Based on the custom parameter, the target app is invoked to execute a corresponding target service. The identification information of the mobile browser is transferred to the target app. In response to executing the corresponding target service, responding to second call data including the package name information of the mobile browser and submitted by the target app, to automatically return to the mobile browser.

Claims

1. A computer-implemented method of invoking a third-party target application (app) from a mobile browser and automatically returning to the mobile browser upon completion without user intervention, the computer-implemented method comprising:

receiving, by a mobile device platform of a mobile device, first call data of a service process submitted by the mobile browser of the mobile device when a service call for the third-party target app installed on the mobile device is initiated, wherein the first call data comprises a custom parameter used to invoke the third-party target app and identification information of the mobile browser, and wherein the identification information comprises package name information of the mobile browser;

invoking, by the mobile device platform based on the custom parameter, the third-party target app to execute a corresponding target service;

transferring, by the mobile device platform, the identification information of the mobile browser to the third-party target app to cause the third-party target app to execute the corresponding target service;

receiving, by the mobile device platform, second call data indicating that the third-party target app executed the corresponding target service, the second call data including the package name information of the mobile browser submitted by the third-party target app, wherein the second call data comprises an intent constructed, based on the package name information of the mobile browser, by the third-party target app and used to invoke the mobile browser;

receiving, by the mobile device platform, the intent;

querying, by the mobile device platform, a system server for an activity component corresponding to the package name information of the mobile browser; and

invoking, by the mobile device platform, the activity component to return to the mobile browser, wherein invoking the activity component to return to the mobile browser includes ensuring application compatibility and eliminating data security breach points by automatically returning to the mobile browser instead of requiring manual selection of the mobile browser.

2. The computer-implemented method of claim 1, wherein receiving the first call data comprises:

retrieving identification information of the mobile browser when a service call for the third-party target app is initiated; and

submitting the first call data for the third-party target app.

3. The computer-implemented method of claim 2, wherein retrieving the identification information comprises:

retrieving user agent information of the mobile browser; and

querying, based on the user agent information of the mobile browser, the system server for the package name information of the mobile browser.

4. The computer-implemented method of claim 3, wherein the package name information of the mobile browser comprises version information of the mobile browser.

5. The computer-implemented method of claim 4, wherein:

the identification information of the mobile browser further comprises the user agent information of the mobile browser; and

in response to determining that the identification information of the mobile browser is the user agent information of the mobile browser, retrieving, based on the user agent information of the mobile browser and by the third-party target app, the package name information of the mobile browser.

6. The computer-implemented method of claim 5, wherein:

the first call data comprises a Universal Resource Locator (URL) defined based on a Schema protocol; and

submitting the first call data for the third-party target app comprises;

defining the URL based on the Schema protocol when the service call for the third-party target app is initiated;

parsing the URL to obtain the custom parameter and the identification information of the mobile browser;

encapsulating, in the URL, the custom parameter and the identification information of the mobile browser, wherein the custom parameter is used to invoke a target service page of the third-party target app; and

invoking a system interface to submit the URL.

7. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations of invoking a third-party target application (app) from a mobile browser and automatically returning to the mobile browser upon completion without user intervention, the operations comprising:

receiving, by a mobile device platform of a mobile device, first call data of a service process submitted by the mobile browser of the mobile device when a service call for the third-party target app installed on the mobile device is initiated, wherein the first call data comprises a custom parameter used to invoke the third-party target app and identification information of the mobile browser, and wherein the identification information comprises package name information of the mobile browser;

invoking, by the mobile device platform based on the custom parameter, the third-party target app to execute a corresponding target service;

transferring, by the mobile device platform, the identification information of the mobile browser to the third-party target app to cause the third-party target app to execute the corresponding target service;

receiving, by the mobile device platform, second call data indicating that the third-party target app executed the corresponding target service, the second call data including the package name information of the mobile browser submitted by the third-party target app, wherein the second call data comprises an intent constructed, based on the package name information of the mobile browser, by the third-party target app and used to invoke the mobile browser;

receiving, by the mobile device platform, the intent;

querying, by the mobile device platform, a system server for an activity component corresponding to the package name information of the mobile browser; and

invoking, by the mobile device platform, the activity component to return to the mobile browser, wherein invoking the activity component to return to the mobile browser includes ensuring application compatibility and eliminating data security breach points by automatically returning to the mobile browser instead of requiring manual selection of the mobile browser.

8. The non-transitory, computer-readable medium of claim 7, wherein receiving the first call data comprises:

retrieving identification information of the mobile browser when a service call for the third-party target app is initiated; and

submitting the first call data for the third-party target app.

9. The non-transitory, computer-readable medium of claim 8, wherein retrieving the identification information comprises:

retrieving user agent information of the mobile browser; and

querying, based on the user agent information of the mobile browser, the system server for the package name information of the mobile browser.

10. The non-transitory, computer-readable medium of claim 9, wherein the package name information of the mobile browser comprises version information of the mobile browser.

11. The non-transitory, computer-readable medium of claim 10, wherein:

the identification information of the mobile browser further comprises the user agent information of the mobile browser; and

in response to determining that the identification information of the mobile browser is the user agent information of the mobile browser, retrieving, based on the user agent information of the mobile browser and by the third-party target app, the package name information of the mobile browser.

12. The non-transitory, computer-readable medium of claim 11, wherein:

the first call data comprises a Universal Resource Locator (URL) defined based on a Schema protocol; and

submitting the first call data for the third-party target app comprises;

defining the URL based on the Schema protocol when the service call for the third-party target app is initiated;

parsing the URL to obtain the custom parameter and the identification information of the mobile browser;

encapsulating, in the URL, the custom parameter and the identification information of the mobile browser, wherein the custom parameter is used to invoke a target service page of the third-party target app; and

invoking a system interface to submit the URL.

13. A computer-implemented system, comprising:

one or more computers; and

one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations of invoking a third-party target application (app) from a mobile browser and automatically returning to the mobile browser upon completion without user intervention, the one or more operations comprising;

receiving, by a mobile device platform of a mobile device, first call data of a service process submitted by the mobile browser of the mobile device when a service call for the third-party target app installed on the mobile device is initiated, wherein the first call data comprises a custom parameter used to invoke the third-party target app and identification information of the mobile browser, and wherein the identification information comprises package name information of the mobile browser;

invoking, by the mobile device platform based on the custom parameter, the third-party target app to execute a corresponding target service;

transferring, by the mobile device platform, the identification information of the mobile browser to the third-party target app to cause the third-party target app to execute the corresponding target service;

receiving, by the mobile device platform, second call data indicating that the third-party target app executed the corresponding target service, the second call data including the package name information of the mobile browser submitted by the third-party target app, wherein the second call data comprises an intent constructed, based on the package name information of the mobile browser, by the third-party target app and used to invoke the mobile browser;

receiving, by the mobile device platform, the intent;

querying, by the mobile device platform, a system server for an activity component corresponding to the package name information of the mobile browser; and

invoking, by the mobile device platform, the activity component to return to the mobile browser, wherein invoking the activity component to return to the mobile browser includes ensuring application compatibility and eliminating data security breach points by automatically returning to the mobile browser instead of requiring manual selection of the mobile browser.

14. The computer-implemented system of claim 13, wherein receiving the first call data comprises:

retrieving identification information of the mobile browser when a service call for the third-party target app is initiated; and

submitting the first call data for the third-party target app.

15. The computer-implemented system of claim 14, wherein retrieving the identification information comprises:

retrieving user agent information of the mobile browser; and

querying, based on the user agent information of the mobile browser, the system server for the package name information of the mobile browser, wherein the package name information of the mobile browser comprises version information of the mobile browser.

16. The computer-implemented system of claim 15, wherein:

the identification information of the mobile browser further comprises the user agent information of the mobile browser; and

in response to determining that the identification information of the mobile browser is the user agent information of the mobile browser, retrieving, based on the user agent information of the mobile browser and by the third-party target app, the package name information of the mobile browser.

17. The computer-implemented system of claim 16, wherein:

the first call data comprises a Universal Resource Locator (URL) defined based on a Schema protocol; and

submitting the first call data for the third-party target app comprises;

defining the URL based on the Schema protocol when the service call for the third-party target app is initiated;

parsing the URL to obtain the custom parameter and the identification information of the mobile browser;

encapsulating, in the URL, the custom parameter and the identification information of the mobile browser, wherein the custom parameter is used to invoke a target service page of the third-party target app; and

invoking a system interface to submit the URL.