Micro-application opening method, related device and medium

Abstract

The invention provides a micro-application opening method, a related device and a medium. The method comprises the steps that in response to triggering of a simulator on first equipment, a simulator interface is displayed, the simulator interface is used for simulating a display interface of second equipment, the simulator interface is provided with a first micro-application opening control of a first micro-application, and a target basic application to which the first micro-application is mounted is not loaded on the display interface; in response to triggering of the first micro-application opening control, a basic application interface of the target basic application is displayed, and the basic application interface comprises a first micro-application interface of the first micro-application. According to the method and the device, when the first equipment simulates the operation of the micro-application on the second equipment by utilizing the simulator, the micro-application can still be normally opened even if the first equipment is not provided with a basic instant session application on which the micro-application depends, so that the opening success rate of the micro-application is improved. The method can be applied to various scenes such as artificial intelligence and cloud technology.

Description

Technical Field

[0001] The present disclosure relates to the field of terminal technology, and in particular to a micro-application opening method, related devices and media. Background Art

[0002] Micro applications refer to applications that can be used without downloading and installing. Micro applications generally need to be opened in the instant chat application. Common micro applications include mini programs and mini games. At present, in order to test the operation of micro applications on mobile terminals on the computer side, simulators are often run on the computer side. Simulators are an application that can simulate the operating environment in mobile terminals. Running an application in the simulator on the computer side has the same effect as running the application directly on the corresponding mobile terminal.

[0003] When running a micro-app on a mobile terminal, you need to first download and install the instant chat app that the micro-app depends on. Similarly, when running a micro-app in a simulator on a computer, you also need to first download and install the instant chat app that the micro-app depends on. Downloading and installing the instant chat app will cause a lot of storage space on the computer to be occupied. If you do not download and install the instant chat app, the micro-app cannot be opened in the simulator. Summary of the invention

[0004] The embodiments of the present disclosure provide a micro-application opening method, related devices and media, which can enable a first device to use a simulator to simulate the running of a micro-application on a second device, so that the micro-application can still be opened normally even if the first device does not have a basic instant conversation application that the micro-application depends on installed, thereby improving the opening success rate of the micro-application.

[0005] According to one aspect of the present disclosure, a method for opening a micro-application is provided, the method comprising:

[0006] In response to triggering the simulator on the first device, displaying a simulator interface, wherein the simulator interface is used to simulate a display interface of the second device, the simulator interface has a first micro-application opening control of the first micro-application, and the target basic application to which the first micro-application is mounted is not loaded on the display interface;

[0007] In response to triggering the first micro-application opening control, a basic application interface of the target basic application is displayed, wherein the basic application interface includes a first micro-application interface of the first micro-application.

[0008] According to one aspect of the present disclosure, a micro-application opening device is provided, the device comprising:

[0009] A first display unit is configured to display a simulator interface in response to a trigger on the simulator on the first device, wherein the simulator interface is used to simulate a display interface of the second device, the simulator interface has a first micro-application opening control of the first micro-application, and the target basic application to which the first micro-application is mounted is not loaded on the display interface;

[0010] The second display unit is configured to display a basic application interface of the target basic application in response to triggering an opening control of the first micro-application, wherein the basic application interface includes a first micro-application interface of the first micro-application.

[0011] Optionally, the simulator interface has a third-party application control;

[0012] The second display unit is used for:

[0013] In response to triggering the third-party application control, displaying a third-party application interface, wherein the third-party application interface has the first micro-application opening control;

[0014] In response to triggering the first micro-application opening control on the third-party application interface, the basic application interface of the target basic application is displayed.

[0015] Optionally, the second display unit is used for:

[0016] In response to triggering the first micro-application opening control, displaying a confirmation area, the confirmation area including a confirmation control for confirming display of the basic application interface;

[0017] In response to triggering the confirmation control, the basic application interface of the target basic application is displayed.

[0018] Optionally, the second display unit is used for:

[0019] In response to triggering the first micro-application opening control, displaying a login area of ​​the target basic application;

[0020] In response to inputting login information of a target user in the login area, if the login information is verified, displaying the basic application interface of the target basic application corresponding to the target user.

[0021] Optionally, the micro-application opening device further includes a third display unit, and the third display unit is used to:

[0022] In response to inputting the login information of the target user in the login area, if the login information verification fails, a verification failure interface is displayed.

[0023] Optionally, the first micro-application is mounted to a plurality of candidate basic applications;

[0024] The second display unit is used for:

[0025] In response to triggering the first micro-application opening control, displaying a selection area, the selection area including a plurality of selection controls corresponding to the plurality of candidate basic applications;

[0026] In response to triggering a target selection control corresponding to the target basic application among the multiple selection controls, the basic application interface of the target basic application is displayed.

[0027] Optionally, the simulator interface further has a second micro-application opening control for a second micro-application, and the second micro-application is mounted to the target basic application;

[0028] The micro-application opening device further includes a fourth display unit, and the fourth display unit is used to:

[0029] In response to triggering the second micro-application opening control, the basic application interface of the target basic application is displayed, and the first micro-application interface and the second micro-application interface are displayed side by side in the basic application interface.

[0030] Optionally, the second display unit includes:

[0031] an identification module, configured to identify that the target basic application is not loaded on the display interface in response to triggering the first micro-application opening control;

[0032] A generation module, used for generating basic application readiness information of a modified target;

[0033] A sending module, configured to send the modified target basic application ready information to the micro-application interface corresponding to the first micro-application, so as to receive the micro-application page rendering information of the first micro-application from the micro-application interface;

[0034] The display module is used to display the basic application interface and render the first micro-application interface within the basic application interface based on the micro-application page rendering information.

[0035] Optionally, the generating module includes:

[0036] An acquisition submodule, used to acquire micro-application page attribute information of the first micro-application;

[0037] A verification submodule, used to perform a first verification on the micro-application page attribute information;

[0038] A generating submodule is used to generate altered target basic application readiness information if it is determined that the first verification passes.

[0039] Optionally, the verification submodule is used to:

[0040] Acquire candidate application information of a plurality of candidate applications, wherein the plurality of candidate applications are mounted to the target basic application, and the candidate applications are not allowed to generate the altered target basic application ready information when triggered;

[0041] Compare the micro-application page attribute information with each of the candidate application information;

[0042] If it is determined that the micro-application page attribute information is inconsistent with each of the candidate application information, it is determined that the first verification is passed.

[0043] Optionally, the generating submodule is used for:

[0044] Obtaining application attribute information and application version information of the target basic application;

[0045] Generate a signature based on the application attribute information to obtain application signature information;

[0046] The application version information and the application signature information are integrated into the altered target basic application ready information.

[0047] Optionally, the sending module is used to:

[0048] Sending the modified target basic application ready information to the micro-application interface corresponding to the first micro-application, so that the micro-application interface determines that the target basic application has been loaded on the simulator based on the modified target basic application ready information, and filling the micro-application page identifier and micro-application page path of the first micro-application into the obtained first micro-application page parameter to construct the micro-application page rendering information, and sending the micro-application page rendering information to the simulator;

[0049] Receive micro-application page rendering information of the first micro-application from the micro-application interface.

[0050] Optionally, the micro-application opening device further includes a prompt unit, and the prompt unit is used to:

[0051] Generate a first prompt based on the constructed micro-application page rendering information, wherein the first prompt is used to indicate that the first micro-application interface of the first micro-application has been successfully called;

[0052] The first prompt is sent to an application server corresponding to the first micro-application.

[0053] Optionally, the micro-application page rendering information is loaded in a target protocol field;

[0054] The display module is used for:

[0055] If the target protocol field is detected in the message channel of the simulator, the micro-application page rendering information is parsed from the target protocol field, wherein the micro-application page rendering information includes a micro-application page identifier and a micro-application page path corresponding to the first micro-application interface;

[0056] Sending the micro-application page identifier to the application interface corresponding to the target basic application to receive the reference page identifier corresponding to the first micro-application interface from the application interface;

[0057] Based on the reference page identifier and the micro-application page path, generating combined page rendering information of the first micro-application interface;

[0058] Based on the combined page rendering information, the basic application interface is displayed, and the first micro-application interface is rendered within the basic application interface.

[0059] Optionally, the target protocol field is generated in the following manner:

[0060] Acquire a first character string indicating the micro-application page identifier and a second character string indicating the micro-application page path from the micro-application page rendering information;

[0061] Obtaining a preset protocol field template, wherein the protocol field template includes a page identification field and a page path field;

[0062] The first character string is filled into the page identification field, and the second character string is filled into the page path field to generate the target protocol field.

[0063] Optionally, sending the micro-application page identifier to an application interface corresponding to the target basic application to receive a reference page identifier corresponding to the first micro-application interface from the application interface includes:

[0064] Sending the micro-application page identifier to the application interface corresponding to the target basic application, so that the application interface determines the reference page identifier according to a preset identifier mapping table and the micro-application page identifier, and returns the reference page identifier, wherein the preset identifier mapping table is used to indicate the correspondence between the candidate page identifiers and the candidate reference identifiers of each candidate application page, and the reference page identifier is the candidate reference identifier corresponding to the candidate page identifier consistent with the micro-application page identifier;

[0065] A reference page identifier corresponding to the first micro-application interface is received from the application interface.

[0066] According to one aspect of the present disclosure, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the micro-application opening method as described above when executing the computer program.

[0067] According to one aspect of the present disclosure, a computer-readable storage medium is provided, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the micro-application opening method described above is implemented.

[0068] According to one aspect of the present disclosure, a computer program product is provided, which includes a computer program, and the computer program is read and executed by a processor of a computer device, so that the computer device executes the micro-application opening method as described above.

[0069] In the disclosed embodiment, when the first device uses the simulator to simulate the operation of the micro-application on the second device, the user can first trigger the simulator on the first device. At this time, the simulator will respond to the triggering of the simulator on the first device and display the simulator interface, wherein the simulator interface is used to simulate the display interface of the second device, and the simulator interface has the first micro-application opening control of the first micro-application, and the target basic application mounted on the first micro-application is not loaded on the display interface. Further, when the user wants to open the first micro-application on the simulator interface, the first micro-application opening control is triggered. At this time, the simulator will respond to the triggering of the first micro-application opening control, display the basic application interface of the target basic application, and display the first micro-application interface of the first micro-application in the basic application interface. In this way, when the first device uses the simulator to simulate the operation of the micro-application on the second device, even if the first device does not install the basic instant conversation application that the micro-application depends on, the micro-application can still be opened normally, thereby improving the opening success rate of the micro-application.

[0070] Other features and advantages of the present disclosure will be described in the following description, and partly become apparent from the description, or be understood by practicing the present disclosure. The purpose and other advantages of the present disclosure can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] The accompanying drawings are used to provide further understanding of the technical solution of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the technical solution of the present disclosure and do not constitute a limitation on the technical solution of the present disclosure.

[0072] Figure 1 is a system architecture diagram of a system for applying a micro-application opening method according to an embodiment of the present disclosure;

[0073] Figure 2A-2B A schematic diagram showing the application of the micro-application opening method according to an embodiment of the present disclosure in a micro-application opening scenario;

[0074] Figure 3 is a flowchart of a micro-application opening method according to an embodiment of the present disclosure;

[0075] Figure 4 is a flowchart of triggering a first micro-application opening control on a third-party application interface according to an embodiment of the present disclosure;

[0076] Figure 5A-Figure 5B is a schematic diagram of an implementation process of triggering a first micro-application opening control on a third-party application interface according to an embodiment of the present disclosure;

[0077] Figure 6 is a flow chart showing a basic application interface of a target basic application according to an embodiment of the present disclosure;

[0078] Figure 7A-7C is a schematic diagram of an implementation process of displaying a basic application interface of a target basic application according to an embodiment of the present disclosure;

[0079] Figure 8 is a flow chart of displaying a basic application interface of a target basic application according to another embodiment of the present disclosure;

[0080] Figure 9A-9B is a schematic diagram of an implementation process of login verification when displaying a basic application interface according to an embodiment of the present disclosure;

[0081] Fig.10 is a flow chart showing a basic application interface according to another embodiment of the present disclosure;

[0082] Figures 11A-11C is a schematic diagram of an implementation process of displaying a basic application interface of a target basic application according to another embodiment of the present disclosure;

[0083] Figure 12A-12B is a schematic diagram of an implementation process of opening multiple micro-applications according to an embodiment of the present disclosure;

[0084] Fig.13 is a flowchart of rendering a first micro-application interface within a basic application interface according to an embodiment of the present disclosure;

[0085] Fig.14 is a flow chart of generating altered target basic application ready information according to an embodiment of the present disclosure;

[0086] Fig.15is a flowchart of performing a first verification of micro-application page attribute information according to an embodiment of the present disclosure;

[0087] Figure 16A-16B is a schematic diagram of an implementation process of performing a first verification on micro-application page attribute information according to an embodiment of the present disclosure;

[0088] Fig.17 is a flow chart of generating altered target basic application ready information according to another embodiment of the present disclosure;

[0089] Figure 18A-18B is a specific implementation flow chart of opening a first micro-application interface of a first micro-application according to an embodiment of the present disclosure;

[0090] Fig.19 is a flow chart of obtaining micro-application page rendering information according to an embodiment of the present disclosure;

[0091] Fig. 20 is a specific implementation flow chart of obtaining micro-application page rendering information according to an embodiment of the present disclosure;

[0092] Fig.21 is a flowchart of rendering a first micro-application interface within a basic application interface according to another embodiment of the present disclosure;

[0093] Fig. 22 is a flow chart of obtaining a reference page identifier according to an embodiment of the present disclosure;

[0094] Fig.23 is a schematic diagram of an implementation process of obtaining a reference page identifier according to an embodiment of the present disclosure;

[0095] Fig.24 is a flow chart of generating a target protocol field according to one embodiment of the present disclosure;

[0096] Figure 25A-25B It is a specific implementation flow chart of passing an opening parameter to a front end of a simulator and opening a first micro-application interface at the front end of the simulator according to an embodiment of the present disclosure;

[0097] Fig.26 is a schematic diagram of implementation details of a micro-application opening method according to an embodiment of the present disclosure;

[0098] Fig. 27 is a module diagram of a micro-application opening device according to an embodiment of the present disclosure;

[0099] Fig.28 is a terminal structure diagram of a micro-application opening method according to an embodiment of the present disclosure;

[0100] Fig.29It is a server structure diagram of a micro-application opening method according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0101] In order to make the purpose, technical solution and advantages of the present disclosure more clear, the present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure and are not used to limit the present disclosure.

[0102] The following describes the system architecture and scenarios for application of the embodiments of the present disclosure.

[0103] Figure 1 It is a system architecture diagram used by the micro-application opening method according to an embodiment of the present disclosure, which includes an object terminal 140, the Internet 130, a gateway 120, a simulator server 110, a basic application server 150, a micro-application server 160, and a third-party application server 170.

[0104] The object terminal 140 includes various forms such as desktop computers, laptop computers, tablet computers, PDAs (personal digital assistants), mobile phones, vehicle-mounted terminals, smart TVs, home theater terminals, and dedicated terminals. In addition, it can be a single device or a collection of multiple devices. The object terminal 140 can communicate with the Internet 130 in a wired or wireless manner to exchange data. Among them, the object terminal 140 includes a simulator platform, which is used to provide users with the application to be run and display the running status of the selected application.

[0105] The simulator server 110, the basic application server 150, the micro application server 160 and the third-party application server 170 refer to computer systems that can provide certain services to the object terminal 140. Compared with the ordinary object terminal 140, the simulator server 110, the basic application server 150, the micro application server 160 and the third-party application server 170 have higher requirements in terms of stability, security, performance, etc. The simulator server 110, the basic application server 150, the micro application server 160 and the third-party application server 170 can be a high-performance computer in the network platform, a cluster of multiple high-performance computers, a part of a high-performance computer (such as a virtual machine), a combination of parts of multiple high-performance computers (such as virtual machines), etc. The simulator server 110, the basic application server 150, the micro application server 160 and the third-party application server 170 include multiple types of services, among which the implementation of each service of the simulator server 110, the basic application server 150, the micro application server 160 and the third-party application server 170 is often associated with some intermediate databases or storage media.

[0106] The simulator server 110 is used to receive the user's request to open each application, and after requesting the server corresponding to the application to obtain the corresponding page rendering information, display the program interface corresponding to the application. The micro-application server 160 is used to provide the page rendering information required to open the micro-application interface of the micro-application. The third-party application server 170 is used to provide the page rendering information required to open the application interface of the third-party application in the simulator. The basic application server 150 is used to provide the corresponding platform interface to render the micro-application interface of the micro-application in the application interface corresponding to the basic application according to the user's request to open the micro-application.

[0107] The gateway 120 is also called an internetwork connector or a protocol converter. The gateway realizes network interconnection at the transport layer and is a computer system or device that acts as a converter. The gateway is a translator between two systems that use different communication protocols, data formats or languages, or even have completely different architectures. At the same time, the gateway can also provide filtering and security functions. The message sent by the object terminal 140 to the simulator server 110, the basic application server 150, the micro application server 160 or the third-party application server 170 must be sent to the corresponding simulator server 110, the basic application server 150, the micro application server 160 or the third-party application server 170 through the gateway 120. The message sent by the simulator server 110, the basic application server 150, the micro application server 160 or the third-party application server 170 to the object terminal 140 must also be sent to the corresponding object terminal 140 through the gateway 120.

[0108] The embodiments of the present disclosure can be applied in various scenarios, such as Figure 2A-2B The micro-application opening scenario shown, etc.

[0109] like Figure 2A As shown, when the target object wants to simulate some common applications on the computer terminal, as well as micro-applications that need to be mounted on the basic application, etc., when running on the mobile terminal, the target object will open the simulator interface of the simulator on the computer terminal. At this time, the simulator interface displays applications including basic application 1, basic application 2, basic application 3, micro-application 1 mounted on basic application 1, third-party application 1 and third-party application 2, etc. Among them, the basic application 1 mounted on micro-application 1 is not installed. Based on this, the target object wants to open micro-application 1, and the target object clicks the open control corresponding to "micro-application 1" on the simulator interface.

[0110] like Figure 2BAs shown, when the target object clicks the open control corresponding to "micro application 1" on the simulator interface, it indicates that the user has triggered the first micro application open control corresponding to micro application 1. Based on this, the basic application interface of the basic application 1 mounted by micro application 1 is displayed on the first device, and the first micro application interface of micro application 1 "xxx examination platform" is displayed in the basic application interface to open micro application 1.

[0111] The following is a general description of the embodiments of the present disclosure.

[0112] According to one embodiment of the present disclosure, a micro-application opening method is provided.

[0113] The micro-application opening method is generally used in a business scenario where a first device uses a simulator to simulate the running status of a micro-application on a second device, for example Figure 2A-2B The micro-application opening scenario shown. The disclosed embodiment provides a solution that can open the micro-application normally when a first device uses an emulator to simulate the running of a micro-application on a second device, even if the first device does not have the basic instant conversation application that the micro-application depends on installed, so that the micro-application can be opened normally when the first device uses an emulator to simulate the running of the micro-application on the second device, even if the first device does not have the basic instant conversation application that the micro-application depends on installed, thereby improving the opening success rate of the micro-application.

[0114] like Figure 3 As shown, the micro-application opening method according to one embodiment of the present disclosure may be executed by an electronic device, which may be Figure 1 The simulator server or target terminal shown in the figure, the micro-application opening method includes:

[0115] Step 310: In response to triggering the simulator on the first device, displaying the simulator interface;

[0116] Step 320: In response to triggering the first micro-application opening control, display the basic application interface of the target basic application.

[0117] Steps 310 - 320 are described in detail below.

[0118] In step 310 , in response to triggering the simulator on the first device, a simulator interface is displayed.

[0119] The first device and the second device refer to terminal devices, and the first device and the second device are different terminal devices. For example, the first device is a computer terminal device, such as a desktop computer, etc., and the second device can be a mobile terminal device, such as a mobile phone, etc.

[0120] A simulator is an application that can simulate the operating environment in a mobile terminal. Running an application in a simulator on a computer is basically the same as running the application directly on the corresponding mobile terminal.

[0121] The simulator interface is used to simulate the display interface of the second device.

[0122] Among them, the target basic application to which the first micro-application is mounted is not loaded on the display interface of the second device (the simulator interface on the first device).

[0123] It should be noted that the target basic application mounted to the first micro-application is not loaded on the display interface of the second device, which means that the target basic application has not been installed in the second device, and the second device does not contain the installation package corresponding to the target basic application. When the target basic application is not loaded on the display interface of the second device (the simulator interface on the first device), the installation control corresponding to the target basic application can be displayed on the display interface of the second device (the simulator interface on the first device), so that the user can trigger the installation control according to actual needs to download and install the target basic application. Furthermore, when the target basic application is installed, indicating that the target basic application has been loaded on the second device (the simulator of the first device), the open control corresponding to the target basic application will be displayed on the display interface of the second device (the simulator interface of the first device), so that the user can open the basic application interface corresponding to the target basic application at any time.

[0124] The above-mentioned mounting of the first micro-application to the target basic application means that the opening and use of the first micro-application is dependent on the target basic application. The first micro-application can only be opened and used when the target basic application is running; at the same time, the micro-application interface of the first micro-application will be embedded in the basic application interface of the target basic application when displayed.

[0125] The target basic application refers to the application that users need to use when using terminal devices for daily affairs such as conversation communication or resource interaction. Among them, the target basic application can allow other micro applications (such as mini programs or mini games) to be opened and run in it. For example, commonly used instant conversation applications, resource interaction applications, etc. can all be used as target basic applications.

[0126] Among them, the simulator interface has a first micro-application opening control of the first micro-application.

[0127] The first micro-application opening control is used to provide the user with an interactive operation so as to open the first micro-application for the user after the user performs the interactive operation.

[0128] In the specific implementation of this embodiment, when the user wants to open the simulator on the first device, the user triggers the opening control corresponding to the simulator on the first device. Based on this, the simulator server detects the triggering event of the user for the opening control corresponding to the simulator, and displays the simulator interface on the first device. Among them, the simulator interface will display multiple loaded applications (including basic applications and third-party applications), and micro-application opening controls of multiple micro-applications.

[0129] In step 320 , in response to triggering the first micro-application opening control, a basic application interface of the target basic application is displayed.

[0130] The basic application interface is used to indicate the specific page content that will be displayed after the target basic application is opened.

[0131] The basic application interface includes a first micro-application interface of a first micro-application.

[0132] The first micro-application interface is used to display the specific content information contained in the first micro-application.

[0133] In the specific implementation of this embodiment, when the user wants to open the first micro-application on the simulator interface, the user triggers the first micro-application opening control on the simulator interface. Based on this, the simulator server detects the user's triggering event of opening the first micro-application control, and in response to the triggering of the first micro-application opening control, displays the basic application interface of the target basic application on the first device, and displays the first micro-application interface embedded in the basic application interface.

[0134] It should be noted that, in the disclosed embodiment, the triggering mode of the user triggering the first micro-application opening control includes but is not limited to key triggering, touch triggering, etc. For example, when the first device is a tablet computer, the user can trigger the first micro-application opening control by touch triggering.

[0135] To save space, the specific implementation process of the first micro-application interface of the embodiment of the present disclosure will be described in detail below. No further details will be given here.

[0136] Through the above steps 310-320, in the embodiment of the present disclosure, when the first device uses the simulator to simulate the operation of the micro-application on the second device, the user can first trigger the simulator on the first device. At this time, the simulator will respond to the triggering of the simulator on the first device, and display the simulator interface, wherein the simulator interface is used to simulate the display interface of the second device, and the simulator interface has the first micro-application opening control of the first micro-application, and the target basic application mounted on the first micro-application is not loaded on the display interface. Further, when the user wants to open the first micro-application on the simulator interface, the first micro-application opening control is triggered. At this time, the simulator will respond to the triggering of the first micro-application opening control, display the basic application interface of the target basic application, and display the first micro-application interface of the first micro-application in the basic application interface. In this way, when the first device uses the simulator to simulate the operation of the micro-application on the second device, even if the first device does not install the basic instant conversation application that the micro-application depends on, the micro-application can still be opened normally, thereby improving the opening success rate of the micro-application.

[0137] The above is a general description of steps 310 to 320. Since step 310 has been described in detail in the above general description, the specific implementation of step 320 will be described in detail below.

[0138] Step 320 is described in detail below.

[0139] In step 320 , in response to triggering the first micro-application opening control, a basic application interface of the target basic application is displayed.

[0140] In order to meet the needs of opening micro-applications in different scenarios, the embodiments of the present disclosure provide a solution for opening micro-applications based on triggering interactive controls in third-party applications, which can improve the flexibility of opening micro-applications.

[0141] In the disclosed embodiment, the simulator interface has a third-party application control.

[0142] The third-party application control is used to provide interactive operations to users, and when triggered by the user, instructs the user to open the third-party application interface corresponding to the third-party application.

[0143] Please refer to Figure 4 In one embodiment, step 320 specifically includes but is not limited to the following steps 410-420:

[0144] Step 410: In response to triggering the third-party application control, display the third-party application interface;

[0145] Step 420: In response to triggering the opening control of the first micro-application on the third-party application interface, display the basic application interface of the target basic application.

[0146] Steps 410 - 420 are described in detail below.

[0147] In step 410, the third-party application interface has the first micro-application opening control.

[0148] In the specific implementation of this embodiment, when the user wants to open a third-party application on the simulator interface, the user triggers the third-party application control corresponding to the third-party application on the simulator interface. Based on this, the simulator server detects the user's trigger event for the third-party application control, and displays the third-party application interface on the first terminal in response to the triggering of the third-party application control.

[0149] In step 420, when the user wants to open the first micro-application on the simulator interface or the third-party application interface, the user triggers the first micro-application opening control on the simulator interface or the third-party application interface. Based on this, the simulator server detects the user's triggering event of opening the first micro-application control, and in response to the triggering of the first micro-application opening control, displays the basic application interface of the target basic application on the first device, and displays the first micro-application interface embedded in the basic application interface.

[0150] Combine the following Figure 2A , Figure 5A and Figure 5B The specific process of opening the first micro-application by triggering the first micro-application opening control in the third-party application is described in detail.

[0151] like Figure 2A As shown, the simulator interface of the simulator displays a third-party application 1 and a third-party application 2. Among them, the third-party application 1 is an application related to examinations and education that supports horizontal screen. The third-party application 1 has been installed in the simulator, and the third-party application control of the third-party application 1 is an interactive control with the word "Open" written on it. The third-party application 2 is an application related to the sharing of comprehensive information, the latest hot events, etc. The third-party application 2 is not installed in the simulator for the time being, and the third-party application control of the third-party application 2 is an interactive control with the word "Install" written on it. Based on this, the user clicks the "Open" interactive control corresponding to the third-party application 1 on the simulator interface to open the third-party application 1.

[0152] like Figure 5AAs shown, after the user triggers the "Open" interactive control of the third-party application 1 on the simulator interface, the third-party application interface of the third-party application 1 is displayed to the user. Among them, the top of the third-party application interface displays the application name of the third-party application 1 "Third-party Application 1 (xx Exam)", and the bottom of the third-party application interface displays multiple paging interactive controls for viewing different columns, and the paging interactive controls include interactive controls with the words "Practice", interactive controls with the words "Course", interactive controls with the words "Live Broadcast", etc. The main area of ​​the third-party application interface displays the "Newbie Special Training" interactive control for viewing content related to exam special training, the "Member Center" interactive control for viewing content related to application members, and the "Free Materials" interactive control for receiving free materials. Among them, the collection of free materials is provided by a micro-application that is different from the third-party application, and the "Free Materials" interactive control is used to provide users with the micro-application to open and enable users to perform interactive operations related to receiving free materials.

[0153] like Figure 5B As shown, when the user clicks the interactive control corresponding to "free materials" on the third-party application interface, it indicates that the user has triggered the first micro-application opening control corresponding to micro-application 1. Based on this, the basic application interface of the basic application 1 mounted by micro-application 1 is displayed on the first device, and the first micro-application interface of the "free material collection platform" of micro-application 1 is displayed in the basic application interface. Among them, the first micro-application interface of the "free material collection platform" of micro-application 1 is jumped and displayed based on the third-party application 1 "xx exam". The prompt field "Congratulations on your successful acquisition of Xxxxx exam materials!" is displayed on the first micro-application interface to indicate that the user has successfully collected the Xxxxx exam materials in the third-party application 1 (xx exam); at the same time, the first micro-application interface also displays an "open" interactive control for opening the collected Xxxxx exam materials, and a "share" interactive control for sharing the free materials on the first micro-application interface to other users.

[0154] The advantage of this embodiment is that the first micro-application opening control of the first micro-application can be directly displayed on the simulator interface or embedded in the third-party application interface of the third-party application for display. This method realizes the diversity of the position setting of the first micro-application opening control, so that when using the simulator to simulate the running status of the micro-application, it is possible to directly open each micro-application displayed in the simulator interface (the display interface of the second device), or to open each third-party application in the simulator interface (the display interface of the second device), and further open the micro-application associated with the third-party application on the third-party application interface of the third-party application, which can improve the flexibility of opening the micro-application and facilitate a more comprehensive simulation of the operation of the micro-applications in various locations in the second device.

[0155] After the micro-application opening control of each micro-application is displayed on the simulator interface or the third-party application interface, the user can freely trigger the micro-application opening control and open the micro-application interface. However, in actual operation, there will be a situation where the user does not want to open the micro-application interface, but accidentally triggers the micro-application opening control, which will cause the micro-application to be opened by mistake. Based on this, the present disclosure provides a solution for introducing a confirmation link when opening a micro-application, which can open the micro-application only after the user confirms, thereby improving the opening accuracy of the micro-application.

[0156] Please refer to Figure 6 In one embodiment, step 320 specifically includes but is not limited to the following steps 610-620:

[0157] Step 610: In response to triggering the first micro-application opening control, display a confirmation area;

[0158] Step 620: In response to triggering the confirmation control, display the basic application interface of the target basic application.

[0159] Steps 610-620 are described in detail below.

[0160] In step 610 , the confirmation area includes a confirmation control for confirming display of the basic application interface.

[0161] When this embodiment is specifically implemented, when the user wants to open the first micro-application on the simulator interface or the third-party application interface, the user will trigger the first micro-application opening control on the simulator interface or the third-party application interface. Based on this, the simulator server will detect the user's triggering event of opening the first micro-application control, and in response to the triggering of the first micro-application opening control, a confirmation area will be displayed on the simulator interface or the third-party application interface, so that the user can choose whether to really open the first micro-application in the confirmation area according to the actual needs. Among them, the confirmation area can be displayed on the simulator interface or the third-party application interface in the form of a floating window or a pop-up window, or it can be embedded in the simulator interface or the third-party application interface for display, without limitation.

[0162] In step 620, when the user views the confirmation area and really needs to open the first micro-application, the user triggers the confirmation control in the confirmation area. Based on this, the simulator server detects the user's triggering event of the confirmation control, and in response to the triggering of the confirmation control, displays the basic application interface of the target basic application on the first device, and displays the first micro-application interface embedded in the basic application interface.

[0163] In addition, in addition to the confirmation control for confirming the display of the basic application interface, the confirmation area may also include a cancel control for canceling the display of the basic application interface, or a deny control for denying the display of the basic application interface. When the user views the confirmation area and does not need to open the first micro-application, the user triggers the cancel control or the deny control in the confirmation area. Based on this, the simulator server detects the user's triggering event of the cancel control or the deny control, and in response to the triggering of the cancel control or the deny control, the basic application interface of the target basic application and the first micro-application interface are not displayed on the first device.

[0164] Combine the following FIG. 7A to FIG. 7C The specific process of adding an inquiry link when opening the first micro-application interface of the first micro-application is described in detail.

[0165] like Fig. 7A As shown, when the user clicks the "Open" interactive control corresponding to the third-party application 1 on the simulator interface, the third-party application interface of the third-party application 1 will be displayed on the first device. Among them, multiple paging interactive controls for viewing different columns will be displayed on the third-party application interface, and the paging interactive controls include interactive controls with the words "Practice", interactive controls with the words "Course", interactive controls with the words "Live Broadcast", etc. In addition, the right side of the third-party application interface corresponding to the third-party application 1 also has a floating pdf file with the words "Data Package", which is provided by micro-application 1 and is used to enter the entry control of micro-application 1 (the first micro-application opening control).

[0166] like Figure 7B As shown, when the user clicks "Resource Package" on the third-party application interface, it indicates that the user has triggered the first micro-application opening control corresponding to micro-application 1. Based on this, a confirmation pop-up window is displayed on the third-party application interface. This confirmation pop-up window is a pop-up window area for confirming to the user whether to open the first micro-application interface of micro-application 1. Specifically, a prompt field "Go to basic application 1 to receive benefits" is displayed in the confirmation pop-up window, and a "Cancel" control and an "OK" control are provided. At this time, the user clicks "OK" in the confirmation pop-up window to confirm the field data package benefits in the basic application 1 mounted on micro-application 1.

[0167] like Figure 7CAs shown, after the user clicks "OK" in the confirmation pop-up window, the basic application interface of the basic application 1 mounted by the micro-application 1 is displayed on the first device, and the first micro-application interface of the micro-application 1 "free information collection platform" is displayed in the basic application interface. Among them, the first micro-application interface of the micro-application 1 "free collection of welfare gift packages" is based on the jump display of the third-party application 1 "xx exam". The first micro-application interface displays a prompt field "Congratulations on your successful acquisition of free benefits", wherein the free benefits are special preparation materials, to indicate that the user has successfully obtained the special preparation materials in the third-party application 1 (xx exam); at the same time, the first micro-application interface also displays an operation guide for activating the free benefits, wherein the operation guide includes the first step "obtaining benefits" that has been completed, and the second step "activating benefits" to be completed. The interactive control corresponding to the second step "activating benefits" displays a prompt field "Click the button to activate for free, effective immediately" to guide the user to trigger the interactive control corresponding to the second step "activating benefits" to activate this free benefit.

[0168] The benefit of this embodiment is that a confirmation link is introduced when the first micro-application opening control is triggered and the first micro-application interface of the first micro-application is opened. Specifically, after the user triggers the first micro-application opening control, a confirmation area is first displayed, and after the user triggers the confirmation control on the confirmation area, the basic application interface of the target basic application and the first micro-application interface in the basic application interface are displayed. This method can reduce the risk of opening the first micro-application interface due to the erroneous triggering of the first micro-application opening control, thereby improving the opening accuracy of the first micro-application and the display accuracy of the first micro-application interface.

[0169] Since the opening of each micro-application depends on some basic applications (such as instant conversation applications), when using various basic applications, users often need to provide login information and can only use the basic application normally after logging in. Otherwise, the specific interface information of the basic application cannot be obtained. In addition, if the user is allowed to use the basic application without obtaining the user's specific login information, the use security of the basic application and the security of the application information will also be reduced. Based on this, the embodiment of the present disclosure provides a solution for logging in to the target basic application based on the login information provided by the user, and opening the first micro-application on the target basic application, which can effectively record the specific user information and operation log information of opening the first micro-application, and improve the access security of the first micro-application.

[0170] Please refer to Figure 8 In one embodiment, step 320 specifically includes but is not limited to the following steps 810-820:

[0171] Step 810: In response to triggering the first micro-application opening control, displaying the confirmation area; In response to triggering the first micro-application opening control, displaying the login area of ​​the target basic application;

[0172] Step 820: In response to inputting the login information of the target user in the login area, if the login information is verified, displaying the basic application interface of the target basic application corresponding to the target user.

[0173] Steps 810-820 are described in detail below.

[0174] In step 810, the login area is used to provide the user with specific information required to input login to the target basic application.

[0175] When this embodiment is specifically implemented, when the user wants to open the first micro-application on the simulator interface or the third-party application interface, the user will trigger the first micro-application opening control on the simulator interface or the third-party application interface. Based on this, the simulator server will detect the user's triggering event of opening the first micro-application control, and in response to the triggering of the first micro-application opening control, display the login area of ​​the target basic application, so that the user can enter specific information for logging into the target basic application in the login area. Among them, the login area can be displayed on the simulator interface or the third-party application interface in the form of a floating window or a pop-up window, or it can be embedded in the simulator interface or the third-party application interface for display, without limitation.

[0176] In step 820, the target user refers to a specific user pointed to by the input login information.

[0177] The login information is used to indicate the specific identity of the user who is to log in to the target basic application, wherein the login information of different users is often the same.

[0178] When this embodiment is implemented, after the login area is displayed, the user can request to log in to the target basic application as the target user by scanning a graphic code, or entering the target user's login identification and login password, or entering the target user's user identification and verification password. Among them, the login identification and user identification are strings set by the target user when registering to identify the identity of the target user, and the login password is used to indicate the key information set by the target user when registering to log in to the target basic application. The verification password is a string with a relatively short validity period assigned to the target user based on the target user's user identification at the current moment. It should be noted that the target user's login identification and login password, user identification and verification password can all be used as the target user's login information.

[0179] Based on this, according to the interactive operation performed by the user in the login area, the simulator server will receive the login information of the target user entered in the login area, and request the target basic application server to obtain the registration information of the target user, so as to verify the login information according to the registration information. Then, if the registration information and the login information are consistent, indicating that the object to be logged in to the target basic application at the current moment and to open the first micro-application is the target user, it is determined that the login information verification is passed, and if the login information verification is passed, the basic application interface of the target basic application corresponding to the target user is displayed, and the first micro-application interface within the basic application interface is displayed.

[0180] In addition, in this embodiment, after displaying the login area of ​​the target basic application in response to triggering the first micro-application opening control, the micro-application opening method further includes:

[0181] In response to inputting the login information of the target user in the login area, in the case where the login information verification fails, a verification failure interface is displayed.

[0182] The verification failure interface is used to indicate that the input login information of the target user is inconsistent with the registration information of the target user, and it is impossible to log in to the basic application interface of the target basic application corresponding to the target user, and the first micro-application interface of the first micro-application is not allowed to open.

[0183] When this embodiment is implemented, first, according to the interactive operation performed by the user in the login area, the simulator server receives the login information of the target user entered in the login area, and requests the target basic application server to obtain the registration information of the target user, so as to verify the login information according to the registration information. Then, if the registration information and the login information are inconsistent, it indicates that the object to log in to the target basic application and open the first micro-application at the current moment is not the target user, and there is a high probability that other users want to access the target basic application and the first micro-application in the name of the target user out of malicious needs, so it is determined that the login information verification fails, and the verification failure interface is displayed to refuse to open the first micro-application.

[0184] Combine the following FIG. 9A to FIG. 9B The specific process of adding a login and verification link when opening the first micro-application interface of the first micro-application is described in detail.

[0185] like Fig. 9AAs shown, after the user clicks the "Open" control corresponding to the micro-application 1 on the simulator interface, the user has not logged in to the simulator interface, and the target basic application 1 mounted by the micro-application 1 is not installed on the simulator. Therefore, the login area (login pop-up window) corresponding to the basic application 1 is displayed in the form of a pop-up window on the simulator interface. Among them, the login area displays prompt fields such as "Log in to experience more exciting content, account synchronization, resource synchronization, and record synchronization". At the same time, a graphic code and a guide field corresponding to the graphic code "Please scan the code to log in to basic application 1" are also displayed. At this time, the user will enter the login information for logging in to the basic application 1 in the form of scanning the graphic code.

[0186] like Fig. 9B As shown, after the user enters the login information for logging into the basic application 1 in the form of scanning the graphic code, the simulator server will rely on the registration information recorded in the server corresponding to the basic application 1 to verify the login information submitted by the user. Further, when the verification is passed, the basic application interface corresponding to the basic application 1 and the first micro application interface corresponding to the micro application 1 will be displayed on the first device (such as Figure 2B ). When the verification fails, a verification failure interface is displayed on the first device, wherein a pop-up window is displayed on the verification failure interface, and a prompt field "Login information verification failed, unable to log in to the target basic application 1" is displayed in the pop-up window, and an "OK" control and a "Help" control are displayed to remind the user that the target basic application 1 cannot be logged in, and the target basic application 1 cannot be used to open the micro application 1.

[0187] The advantage of this embodiment is that when opening the first micro-application interface of the first micro-application, a login and verification link is added, so that after the user triggers the first micro-application opening control, he or she is also required to provide specific login information, and the user is allowed to log in to the target basic application only after the login information is verified, and the basic application interface corresponding to the target user and the first micro-application interface are displayed to the user. In this way, the specific user information and operation log information of opening the first micro-application can be effectively recorded according to the login information, and the access security of the first micro-application can be improved.

[0188] Since in actual applications, a micro-application can often be mounted on multiple basic applications at the same time, if when opening a micro-application, one of the multiple basic applications is randomly selected to display the application interface of the basic application and the micro-application interface of the micro-application is displayed, it may cause the basic application used when opening the micro-application to not meet the real needs of the user. However, if when opening this micro-application, the application interfaces of each basic application and the micro-application interface within the application interface of each basic application are displayed at the same time, there will be too many basic applications opened at the same time, and the problem of repeatedly displaying the micro-application interface of the micro-application will result in low interface loading efficiency and waste of resources. Based on this, the embodiment of the present disclosure provides a solution for opening a micro-application based on a user-defined target basic application, which can effectively improve the interface loading efficiency and reduce resource waste while meeting user needs.

[0189] In an embodiment of the present disclosure, the first micro-application is mounted to multiple candidate basic applications.

[0190] The candidate basic application refers to various application programs that allow the first micro-application to be mounted and can display the first micro-application interface in its own application interface. Among them, the application functions, application sources, etc. of different candidate basic applications can be different.

[0191] Please refer to Fig.10 In one embodiment, step 320 specifically includes but is not limited to the following steps 1010-1020:

[0192] Step 1010: In response to triggering the first micro-application opening control, displaying a selection area;

[0193] Step 1020 : In response to triggering a target selection control corresponding to the target basic application among the multiple selection controls, display a basic application interface of the target basic application.

[0194] Steps 1010 - 1020 are described in detail below.

[0195] In step 1010 , the selection area includes multiple selection controls corresponding to multiple candidate basic applications.

[0196] The selection control is used to provide the user with a candidate basic application to be used to open the first micro-application.

[0197] In the specific implementation of this embodiment, when the user wants to open the first micro-application on the simulator interface or the third-party application interface, the user will trigger the first micro-application opening control on the simulator interface or the third-party application interface. Based on this, the simulator server will detect the user's triggering event of opening the first micro-application control, and in response to the triggering of the first micro-application opening control, display the selection area, and display the basic information of each candidate basic application mounted to the first micro-application in the selection area, as well as the selection controls corresponding to each candidate basic application, so that the user can select one of the multiple candidate basic applications as the basic application to be used to open the first micro-application. Among them, the basic information of each candidate basic application may include, but is not limited to, the application name, application type, and installation status or loading status of the candidate basic application in the simulator, etc.

[0198] It should be noted that the selection area can be displayed in the form of a floating window or a pop-up window on the simulator interface or the third-party application interface, or can be embedded in the simulator interface or the third-party application interface for display, without limitation.

[0199] In step 1020, after the selection area is displayed, the user can freely select a candidate basic application that he wants to use when opening the first micro-application in the selection area as the target basic application. After the user considers which candidate basic application he wants to use when opening the first micro-application, the target basic application is determined, and the user can trigger the target selection control corresponding to the target basic application in the selection area to determine to use the target basic application to open the first micro-application. Based on this, the server will respond to the triggering of the target selection control corresponding to the target basic application in the multiple selection controls, and display the basic application interface of the target basic application on the first device, and only display the first micro-application interface in the basic application interface of the target basic application, and no longer display the basic application interfaces of each candidate basic application other than the target basic application.

[0200] Combine the following FIG. 11A to FIG. 11C The specific process of opening the first micro-application interface of the first micro-application when the first micro-application mounts multiple candidate basic applications is described in detail.

[0201] like Fig.11AAs shown, three candidate basic applications mounted to micro application 1 are displayed on the simulator interface. The three candidate basic applications are basic application 3 installed on the simulator, and basic application 1 and basic application 2 not installed on the simulator. Basic application 1, basic application 2 and basic application 3 are all social applications, but basic application 1 and basic application 2 tend to be chat applications (instant conversation applications), and basic application 3 tends to be life applications. Based on this, the user clicks the "Open" control corresponding to micro application 1 on the simulator interface to determine that the micro application interface corresponding to micro application 1 is to be opened.

[0202] like Fig. 11B As shown, when the user clicks the "Open" control corresponding to micro-application 1 on the simulator interface, a selection pop-up window will be displayed on the simulator interface, and a prompt field "Please select the target basic application to be used to open the micro-application from the following three candidate basic applications" is displayed in the selection pop-up window; at the same time, the selection pop-up window also displays the selection controls corresponding to basic application 1 in an uninstalled state, basic application 2 in an uninstalled state, and basic application 3 in an installed state. Based on this, the user clicks the selection control corresponding to basic application 2 in an uninstalled state to select basic application 2, and clicks the "OK" button to determine that basic application 2 is used as the target basic application to be used to open the micro-application.

[0203] like Fig. 11C As shown, after the user selects to use basic application 2 to open micro application 1, the basic application interface corresponding to basic application 2 will be displayed on the first device, and the first micro application interface corresponding to micro application 1 "xxx examination platform" will be displayed in the basic application interface.

[0204] The benefit of this embodiment is that the micro-application is opened based on the user-defined target basic application. When the micro-application is mounted to multiple candidate basic applications, the user can freely select a candidate basic application as the target basic application in the selection area according to the basic information of each candidate basic application, and open the micro-application interface corresponding to the micro-application in the target basic application. This method can reduce the number of basic applications opened at the same time while meeting user needs, thereby effectively improving the interface loading efficiency and reducing resource waste.

[0205] In one embodiment, the simulator interface further has a second micro-application opening control of the second micro-application, and the second micro-application is mounted to the target basic application. After the basic application interface of the target basic application is displayed in response to the triggering of the first micro-application opening control, the micro-application opening method further includes:

[0206] In response to triggering the second micro-application opening control, a basic application interface of the target basic application is displayed, and the first micro-application interface and the second micro-application interface are displayed side by side in the basic application interface.

[0207] The second micro-application refers to another micro-application different from the first micro-application.

[0208] The second micro-application opening control is used to provide the user with an interactive operation so as to open the second micro-application for the user after the user performs the interactive operation.

[0209] The second micro-application interface is used to display the specific content information contained in the second micro-application.

[0210] In the specific implementation of this embodiment, after the first micro-application interface of the first micro-application is displayed in the basic application interface of the target basic application, if the user wants to continue to open the second micro-application mounted on the target basic application, the user will trigger the second micro-application opening control on the simulator interface or the third-party application interface. Based on this, the simulator server will detect the user's triggering event of opening the second micro-application control, and in response to the triggering of the second micro-application opening control, continue to display the basic application interface of the target basic application, and display the first micro-application interface and the second micro-application interface side by side in the basic application interface to realize the simultaneous opening of the first micro-application and the second micro-application.

[0211] Combine the following FIG. 12A to FIG. 12B The specific process of opening the second micro-application after opening the first micro-application is described in detail.

[0212] like Fig. 12A As shown, in addition to micro application 1, micro application 2 for social interaction and video publishing is also displayed on the simulator interface, wherein micro application 2 and micro application 1 are both mounted to basic application 1. Based on this, after the user opens micro application 1, the first micro application interface of micro application 1 will be displayed in the basic application interface of basic application 1. At this time, if the user wants to continue to open micro application 2, the user will click the "Open" control corresponding to micro application 2 on the simulator interface.

[0213] like Fig. 12B As shown, when the user clicks the "Open" control corresponding to micro-application 2 on the simulator interface, the basic application interface of basic application 1 is displayed on the first device. Among them, the first micro-application interface of micro-application 1 "xxx examination platform" and the second micro-application interface of micro-application 2 "xxx social platform" are displayed in the basic application interface at the same time.

[0214] The advantage of this embodiment is that it takes into account the needs of users to open multiple micro-applications at the same time. When users want to open multiple micro-applications mounted on the same basic application at the same time, the micro-application interfaces of the micro-applications whose opening controls are triggered are displayed in parallel in the basic application interface of the basic application according to the triggering conditions of the opening controls of each micro-application. This can meet the business needs of opening multiple micro-applications at the same time, thereby improving the flexibility of opening micro-applications.

[0215] The specific process of the simulator server executing step 320 in one embodiment of the present disclosure is described in detail below.

[0216] Please refer to Fig.13 In one embodiment, the specific process of the simulator server executing step 320 includes but is not limited to the following steps 1310-1340:

[0217] Step 1310: In response to triggering the first micro-application opening control, identifying that the target basic application is not loaded on the display interface;

[0218] Step 1320: Generate altered target basic application ready information;

[0219] Step 1330: Send the modified target basic application ready information to the micro-application interface corresponding to the first micro-application, so as to receive the micro-application page rendering information of the first micro-application from the micro-application interface;

[0220] Step 1340: Display the basic application interface, and render the first micro-application interface within the basic application interface based on the micro-application page rendering information.

[0221] Steps 1310 - 1340 are described in detail below.

[0222] In step 1310 , in response to triggering the first micro-application opening control, it is identified that the target basic application is not loaded on the display interface.

[0223] In the specific implementation of this embodiment, when the user wants to open the first micro-application on the simulator interface or the third-party application interface, the user will trigger the first micro-application opening control on the simulator interface or the third-party application interface. Based on this, the simulator server will detect the user's triggering event of opening the first micro-application control, and in response to the triggering of the first micro-application opening control, extract information from various applications that have been loaded or installed, and obtain application information of various applications that have been loaded or installed. Next, the basic application information of the target basic application mounted by the first micro-application is compared with the obtained application information. If there is no application information of various applications that have been loaded or installed, and it is consistent with the basic application information of the target basic application, it indicates that the target basic application is not loaded or installed on the simulator, so it will be identified that the target basic application is not loaded on the display interface.

[0224] In step 1320, the altered target basic application ready information is generated.

[0225] The modified target basic application ready information is used to indicate that the target basic application has been installed or loaded on the simulator when the target basic application has not been loaded or installed on the simulator.

[0226] In the specific implementation of this embodiment, since the normal opening of the first micro-application depends on the target basic application, when the target basic application is not loaded or installed on the simulator, the simulator cannot directly obtain the first micro-application interface rendering information used to render the first micro-application. Based on this, the simulator will generate a modified target basic application ready information according to the application parameters that the target basic application should have when it is installed, so as to use the modified target basic application ready information to indicate to other applications that the target basic application has been installed.

[0227] To save space, the specific process of generating the modified target basic application readiness information in the embodiment of the present disclosure will be described in detail below and will not be repeated here.

[0228] In step 1330 , the modified target basic application ready information is sent to the micro-application interface corresponding to the first micro-application to receive the micro-application page rendering information of the first micro-application from the micro-application interface.

[0229] The micro-application interface refers to an API interface for data transmission between the micro-application server corresponding to the first micro-application and other servers (such as a basic application server, a simulator server, or a third-party application server).

[0230] The micro-application page rendering information is used to indicate the specific materials or specific configuration parameters required to render the first micro-application interface of the first micro-application. For example, the micro-application page rendering information includes the material call path or interface name corresponding to the first micro-application interface of the first micro-application.

[0231] When this embodiment is specifically implemented, first, the simulator server sends the modified target basic application ready information to the micro-application interface corresponding to the first micro-application, so that the first micro-application confirms that the target basic application has been installed on the simulator according to the modified target basic application ready information. Then, after confirming that the target basic application has been installed on the simulator, the first micro-application transmits the micro-application page rendering information of the first micro-application to the simulator. Based on this, the simulator can receive the micro-application page rendering information of the first micro-application from the micro-application interface.

[0232] In step 1340 , the basic application interface is displayed, and within the basic application interface, the first micro-application interface is rendered based on the micro-application page rendering information.

[0233] In the specific implementation of this embodiment, after receiving the micro-application page rendering information of the first micro-application, the simulator will first request the application server corresponding to the target basic application to call the application interface of the target basic application; then, based on the called application interface, the basic application interface of the target basic application is loaded, and within the basic application interface, according to the micro-application page rendering information, the first micro-application interface of the first micro-application is rendered, wherein the first micro-application interface has the specific content indicated by the micro-application page rendering information.

[0234] The benefit of this embodiment is that when the simulator service detects that the user has triggered the first micro-application opening control on the simulator interface, and identifies that the target basic application is not loaded or installed in the simulator, the simulator server generates modification ready information, so that when the target basic application is not installed, the servers corresponding to other applications believe that the target basic application has been installed in the simulator, thereby improving the credibility of the existence of the target basic application; at the same time, the server corresponding to the first micro-application provides the micro-application page rendering information to the simulator when it believes that the target basic application has been installed, so that the first micro-application interface can be successfully rendered and displayed in the basic application interface. This method can improve the success rate of obtaining the micro-application page rendering information, and thus improve the success rate of opening the first micro-application interface.

[0235] Since there are often multiple mounted micro-applications in a basic application, if the basic application is not loaded, all micro-applications mounted on the basic application are allowed to be opened by generating altered ready information, which will cause certain usage security risks of the basic application. In addition, in some transactions such as resource interaction and information interaction that rely on the implementation of the basic application, it is often necessary to verify whether the basic application has been installed. If the installation status of the basic application is incorrectly judged in these processes, the transaction cannot be executed normally. Based on this, the embodiment of the present disclosure provides an altered information generation scheme based on interface verification, which can verify the interface to be displayed when generating the altered installation information of the target basic application, thereby improving the generation security of the altered target basic application ready information and the security of page loading.

[0236] Please refer to Fig.14 In one embodiment, the specific process of step 1320 includes but is not limited to the following steps 1410-1430:

[0237] Step 1410: Obtain micro-application page attribute information of the first micro-application;

[0238] Step 1420: Perform a first verification on the micro-application page attribute information;

[0239] Step 1430: If it is determined that the first verification is passed, generate the altered target basic application ready information.

[0240] Steps 1410-1430 are described in detail below.

[0241] In step 1410 , micro-application page attribute information of the first micro-application is obtained.

[0242] The micro-application page attribute information is used to indicate the basic interface attributes of the first micro-application interface of the first micro-application, wherein the micro-application page attribute information includes the page identifier (username) of the first micro-application interface, the storage path (path) of the resources used to render the first micro-application interface, and the like.

[0243] In the specific implementation of this embodiment, since the application interface information of various micro-applications and various application programs will be recorded in the background log of the simulator server, based on this, with authorization, the micro-application page attribute information of the first micro-application is extracted from the background log of the simulator server.

[0244] In step 1420 , a first verification is performed on the micro-application page attribute information.

[0245] The first verification is used to verify whether the micro-application page attribute information of the first micro-application meets the condition requirements for generating the altered target basic application ready information.

[0246] To save space, the specific process of performing the first verification on the micro-application page attribute information in the embodiment of the present disclosure will be described in detail below and will not be repeated here.

[0247] In step 1430 , if it is determined that the first verification is passed, then altered target basic application ready information is generated.

[0248] In the specific implementation of this embodiment, if it is determined that the first verification is passed, it indicates that the micro-application page attribute information of the first micro-application meets the conditional requirements for generating the altered target basic application ready information, and the altered target basic application ready information can be constructed based on the application attribute information of the target basic application, so that when the target basic application is not loaded (not installed) on the simulator, the server corresponding to other applications (such as the server corresponding to the first micro-application) believes that the target basic application has been loaded (installed) on the simulator according to the altered target basic application ready information. On the contrary, if it is determined that the first verification is not passed, it indicates that the micro-application page attribute information of the first micro-application does not meet the conditional requirements for generating the altered target basic application ready information. For the safety of the application, the altered target basic application ready information is not generated.

[0249] The benefit of this embodiment is that when generating the altered target basic application ready information, an interface verification link is introduced. Specifically, the micro-application page attribute information of the first micro-application is verified, and the altered target basic application ready information is generated only when it is determined that the first verification is passed. This method realizes the verification of the first micro-application interface to be displayed, which can improve the security and rationality of generating the altered target basic application ready information, and can also improve the security of page loading.

[0250] Please refer to Fig.15 In one embodiment, the specific process of step 1420 includes but is not limited to the following steps 1510-1530:

[0251] Step 1510, obtaining candidate application information of multiple candidate applications;

[0252] Step 1520: Compare the micro-application page attribute information with each candidate application program information;

[0253] Step 1530: If it is determined that the micro-application page attribute information is inconsistent with the information of each candidate application program, it is determined that the first verification is passed.

[0254] Steps 1510-1530 are described in detail below.

[0255] In step 1510, candidate application information of a plurality of candidate applications is obtained.

[0256] Among them, multiple candidate applications are mounted to the target basic application, and the candidate applications are not allowed to generate or alter the target basic application ready information when triggered.

[0257] The candidate application information is used to indicate basic interface attributes of the application interface corresponding to the candidate application, wherein the candidate application information includes a page identifier, an interface type, etc. of the application interface corresponding to the candidate application.

[0258] When this embodiment is implemented, the specific process of step 1510 is similar to the above step 1410. To save space, it will not be described again.

[0259] In step 1520 , the micro-application page attribute information is compared with each candidate application information.

[0260] In a specific implementation of this embodiment, for each candidate application, the candidate application information is compared with the micro-application page attribute information to determine whether the candidate application information is consistent with the micro-application page attribute information.

[0261] Among them, when the candidate application information of a candidate application is consistent with the micro-application page attribute information, it indicates that the candidate application and the first micro-application are the same application.

[0262] In step 1530 , if it is determined that the micro-application page attribute information is inconsistent with each candidate application program information, it is determined that the first verification is passed.

[0263] In the specific implementation of this embodiment, if it is determined that the micro-application page attribute information is inconsistent with the information of each candidate application, it indicates that the first micro-application does not belong to an application that is not allowed to generate altered target basic application ready information, and if the target basic application is not installed, generating the corresponding altered target basic application ready information will not cause adverse effects. Therefore, it is determined that the first verification is passed, and the target basic application ready information is allowed to be generated when the first micro-application is to be opened.

[0264] On the contrary, if it is determined that the micro-application page attribute information is inconsistent with the candidate application information of one of the multiple candidate applications, it indicates that the first micro-application is an application that is not allowed to generate altered target basic application ready information, and if the target basic application is not installed, generating the corresponding altered target basic application ready information is likely to cause adverse effects. Therefore, it is determined that the first verification fails, and the generation of the target basic application ready information is rejected.

[0265] It should be noted that, during the first verification, it is also possible to obtain multiple program attribute information possessed by the candidate application programs that are mounted to the target basic application and allow the generation of altered target basic application ready information when triggered, and compare the program attribute information of this type of candidate application programs with the micro-application page attribute information of the first micro-application. If there is a candidate application program attribute information that is consistent with the micro-application page attribute information, it is determined that the first verification is passed, and the specific process of this implementation is similar to the above steps 1510-1530. The difference is that the candidate application program of the above steps 1510-1530 is an application program (non-whitelist application program) that is not allowed to generate altered target basic ready information, and the candidate application program of this implementation is an application program (whitelist application program) that is allowed to generate altered target basic ready information. To save space, it will not be repeated.

[0266] like Fig.16A As shown, it is a specific process of performing the first verification based on the candidate application list that is not allowed to construct the target basic application ready information. Specifically, the candidate application list that is not allowed to construct the target basic application ready information includes 5 candidate applications, namely candidate application 1, candidate application 2, candidate application 10, candidate application 14 and candidate application 25. Among them, the program page attribute identifier of candidate application 1 is Qeda1; the program page attribute identifier of candidate application 2 is dqaq414; the program page attribute identifier of candidate application 10 is Qe12da1; the program page attribute identifier of candidate application 14 is dmqe89; the program page attribute identifier of candidate application 25 is cmqfiqw09. Based on this, when the page attribute identifier in the micro-application page attribute information of the first micro-application is sada3q1, since the page attribute identifier of the first micro-application is different from the program page attribute identifiers of the five candidate applications, it indicates that the first micro-application does not belong to the application that is not allowed to generate the target basic application ready information, so it is determined that the first verification is passed.

[0267] As shown in 16B, it is a specific process of performing the first verification based on the candidate application list that is allowed to construct the target basic application ready information for alteration. Specifically, the candidate application list that is allowed to construct the target basic application ready information for alteration includes 5 candidate applications, namely candidate application 3, candidate application 4, candidate application 6, candidate application 7 and candidate application 8. Among them, the program page attribute identifier of candidate application 3 is foqnfa87; the program page attribute identifier of candidate application 4 is sada3q1; the program page attribute identifier of candidate application 6 is dqq31xqe; the program page attribute identifier of candidate application 7 is 8rqcq4; the program page attribute identifier of candidate application 8 is asdqe123. Based on this, when the page attribute identifier in the micro-application page attribute information of the first micro-application is sada3q1, since the page attribute identifier of the first micro-application is the same as the program page attribute identifier of candidate application 4, it indicates that the first micro-application and candidate application 4 are the same application, and the first micro-application belongs to the application that is allowed to generate the target basic application ready information for alteration, so it is determined that the first verification is passed.

[0268] The benefit of this embodiment is that when generating the altered target basic application ready information, an interface verification link is introduced. Specifically, the micro-application page attribute information of the first micro-application is compared with the candidate application information of the candidate application that is not allowed to generate the altered target basic application ready information, or the micro-application page attribute information of the first micro-application is compared with the candidate application information of the candidate application that is allowed to generate the altered target basic application ready information. The first micro-application interface is verified by information comparison, which can improve the accuracy and efficiency of interface verification.

[0269] Please refer to Fig.17 In one embodiment, the specific process of step 1430 includes but is not limited to the following steps 1710-1730:

[0270] Step 1710: Obtain application attribute information and application version information of the target basic application;

[0271] Step 1720: Generate a signature based on the application attribute information to obtain application signature information;

[0272] Step 1730: Integrate the application version information and the application signature information into the modified target basic application ready information.

[0273] Steps 1710-1730 are described in detail below.

[0274] In step 1710, application attribute information and application version information of the target basic application are obtained.

[0275] The application attribute information is used to indicate the basic attributes of the target basic application, wherein the application attribute information includes but is not limited to the application name, development information, configuration parameters, interface attributes (style, layout, language, etc.) of the target basic application, and the like.

[0276] The application version information is used to indicate information such as the version number and version identifier of the target basic application that can be installed at the current moment.

[0277] In the specific implementation of this embodiment, since the simulator server will record the attribute information and version information that the target basic application that is allowed to be loaded and run at the current time point should have, the attribute information and version information that the target basic application should have is mainly used to verify the target basic application that the user wants to download and use, so as to reduce the use failure caused by the version of the target basic application downloaded or used being too low. Based on this, the application attribute information and application version information of the target basic application are pre-stored in the simulation server, and with authorization and permission, the pre-stored application attribute information and application version information of the target basic application can be directly called.

[0278] In step 1720, a signature is generated based on the application attribute information to obtain application signature information.

[0279] The application signature information is used to indicate the ciphertext representation of the application attribute information of the target basic application.

[0280] In the specific implementation of this embodiment, since the application attribute information of the target basic application is relatively important, when constructing and modifying the ready information of the target basic application, the application attribute information of the target basic application is signed using the server key of the simulator server, and the application attribute information in plain text is encrypted into application signature information in cipher text to improve the confidentiality of the application attribute information.

[0281] In step 1730, the application version information and the application signature information are integrated into the altered target basic application ready information.

[0282] In the specific implementation of this embodiment, in order to improve the verifiability of the standardization of the modified target basic application ready information; first, according to the information format that the real target basic application ready information should have after the target basic application is actually installed, the application version information and the application signature information are integrated according to the information format to form a complete information body, and the obtained information body is used as the modified target basic application ready information.

[0283] It should be noted that the forged target basic application ready information and the real target basic application ready information are basically the same in format and content. The difference between the two is that the forged target basic application ready information is forged information, and the corresponding target basic application is not actually installed on the simulator; while the real target basic application ready information is based on the target basic application having been successfully installed on the simulator, and is not forged information.

[0284] The benefit of this embodiment is that, for more important application attribute information, the simulator server uses the server key to sign the application attribute information into application signature information, and integrates the application signature information and the application version information into the altered target basic application ready information, so that the altered target basic application ready information contains the specific attribute parameters and specific version parameters of the target basic application, which can improve the information comprehensiveness and information security of the constructed altered target basic application ready information, thereby using the altered target basic application ready information to improve the success rate of opening the first micro-application when the target basic application is not installed.

[0285] Combine the following FIG. 18A to FIG. 18B The specific implementation process of generating the modified target basic application ready information of the target basic application is described in detail.

[0286] like Fig.18A As shown, it is a specific indication of opening the first micro-application interface without interface verification. Specifically, when the first micro-application is to be opened on the simulator, first, the simulator will call the opening interface (micro-application interface) of the first micro-application, and then the simulator will determine whether the target basic application is installed on the simulator. When it is determined that the target basic application has been installed on the simulator, the first micro-application opening control can be triggered, and the first micro-application interface of the first micro-application can be opened directly in the target basic application. However, when it is determined that the target basic application is not installed on the simulator, the simulator will forge a target basic application ready information that the target basic application is already installed, and based on the forged target basic application ready information, the first micro-application interface of the first micro-application is opened in the target basic application.

[0287] like Fig.18BAs shown, it is a specific indication of opening the first micro-application interface under the condition of interface verification. Specifically, when the first micro-application is to be opened on the simulator, first, the simulator will call the opening interface (micro-application interface) of the first micro-application, and then the simulator will determine whether the target basic application is installed on the simulator. When it is determined that the target basic application has been installed on the simulator, the first micro-application opening control can be triggered, and the first micro-application interface of the first micro-application can be directly opened in the target basic application. However, when it is determined that the target basic application is not installed on the simulator, the simulator will further determine whether the first micro-application interface to be opened is a specific page, wherein the specific page refers to the application interface that does not allow the modification of the relevant information of the target basic application to be installed. Based on this, when it is determined that the first micro-application interface to be opened is a specific page, the process of opening the first micro-application is directly terminated, and the modification of the target basic application ready information is not allowed. When it is determined that the first micro-application interface to be opened is not a specific page, the modification of the target basic application ready information that a target basic application has been installed is modified, and the first micro-application interface of the first micro-application is opened in the target basic application based on the modification of the target basic application ready information.

[0288] Please refer to Fig.19 In one embodiment, the specific process of step 1330 includes but is not limited to the following steps 1910-1920:

[0289] Step 1910: Send the modified target basic application ready information to the micro-application interface corresponding to the first micro-application, so that the micro-application interface determines that the target basic application has been loaded on the simulator based on the modified target basic application ready information, fills the micro-application page identifier and micro-application page path of the first micro-application into the obtained first micro-application page parameter to construct the micro-application page rendering information, and sends the micro-application page rendering information to the simulator;

[0290] Step 1920: Receive micro-application page rendering information of the first micro-application from the micro-application interface.

[0291] Steps 1910-1920 are described in detail below.

[0292] In step 1910, the modified target basic application ready information is sent to the micro-application interface corresponding to the first micro-application, so that the micro-application interface determines that the target basic application has been loaded on the simulator based on the modified target basic application ready information, fills the micro-application page identifier and micro-application page path of the first micro-application into the obtained first micro-application page parameters to construct the micro-application page rendering information, and sends the micro-application page rendering information to the simulator.

[0293] The micro-application page identifier is used to indicate that the first micro-application interface of the first micro-application is marked to distinguish the first micro-application interface from other application interfaces.

[0294] The micro-application page path is used to indicate the storage path of specific resources required to render the first micro-application interface, etc.

[0295] The first micro-application page parameter is used to indicate the page information of the first micro-application collected by the target basic application using the target component. Among them, the target control can be any component used to manage application data access, such as a ContentProvider component, a Service component, or an Activity component. Taking the ContentProvider component as an example, when the first micro-application interface of the first micro-application is to be displayed on the basic application interface of the target basic application, the target basic application will collect the relevant interface parameters of the first micro-application through the ContentProvider component to render the first micro-application interface.

[0296] When this embodiment is specifically implemented, first, the simulator server will send the modified target basic application ready information to the micro-application interface corresponding to the first micro-application. Then, after the micro-application interface corresponding to the first micro-application receives the modified target basic application ready information, it will be considered that the target basic application has been installed on the simulator. Further, the first micro-application will request the application interface of the target basic application to obtain the basic application interface of the target basic application, and call the target control (ContentProvider) of the target basic application to obtain the specific rendering information of the first micro-application. However, since the target basic application is not actually installed, the operation will fail to execute, and at the same time, the first micro-application page parameters of the first micro-application that can be collected by the target control will be empty. Then, the micro-application page identifier and micro-application page path of the first micro-application are filled into the first micro-application page parameters obtained, and the first micro-application page parameters are updated to obtain the micro-application page rendering information. Finally, the micro-application page rendering information is sent to the simulator.

[0297] In step 1920 , micro-application page rendering information of the first micro-application is received from the micro-application interface.

[0298] In the specific implementation of this embodiment, after the first micro application confirms that the target basic application has been installed on the simulator according to the micro application page rendering information, the micro application page rendering information is transmitted to the simulator through the micro application interface. Based on this, the simulator can receive the micro application page rendering information of the first micro application from the micro application interface.

[0299] The benefit of this embodiment is that, when the target basic application is not installed on the simulator, the simulator sends the modified target basic application ready information to the micro-application interface corresponding to the first micro-application, so that the first micro-application confirms that the target basic application is ready to be installed, thereby interacting with the target basic application normally, and timely updating the acquired first micro-application page parameters to construct the micro-application page rendering information, which can achieve the transmission success rate of the micro-application page rendering information, thereby improving the opening success rate of the first micro-application.

[0300] In one embodiment, after sending the micro-application page rendering information to the simulator, the micro-application opening method further includes:

[0301] Generate a first prompt based on the constructed micro-application page rendering information;

[0302] The first prompt is sent to an application server corresponding to the first micro-application.

[0303] The first prompt is used to indicate that the first micro-application interface of the first micro-application has been successfully called.

[0304] In the specific implementation of this embodiment, after the micro-application interface constructs the micro-application page rendering information, the micro-application interface sends the micro-application page rendering information to the simulator. Then, after confirming that the simulator has successfully received the micro-application page rendering information, the micro-application interface generates a first prompt indicating that the first micro-application interface of the first micro-application has been successfully called, and sends the first prompt to the application server corresponding to the first micro-application to remind the application server corresponding to the first micro-application that the forwarding of the micro-application page rendering information has been completed.

[0305] The advantage of this embodiment is that after forwarding the micro-application page rendering information to the simulator, the forwarding status of the micro-application page rendering information is also detected, and when it is determined that the forwarding is successful, a first prompt is generated to indicate that the interface information corresponding to the first micro-application interface has been successfully called, which can realize the full process management of information forwarding and improve the reliability of information transmission.

[0306] like Fig. 20As shown, in the case where the altered target basic application ready information is generated, the micro-application page rendering information is sent to the simulator. Specifically, when the process of opening the first micro-application interface of the first micro-application is executed according to the generated altered target basic application ready information, when the first micro-application confirms that the target basic application has been installed on the simulator according to the altered target basic application ready information, the first micro-application will request the application interface of the target basic application to evoke the basic application interface of the target basic application. At this time, according to the operation of obtaining the basic application interface of the target basic application by the request of the first micro-application, the target basic application generally calls the target control (ContentProvider) to obtain the specific rendering information of the first micro-application. However, since the target basic application is not actually installed, the evoke operation will fail to execute, and at the same time, the specific rendering information of the first micro-application that the target control can collect is empty. If the empty specific rendering information is returned to the simulator, the first micro-application cannot be opened. Based on this, after calling the target control to obtain the specific rendering information of the first micro-application, the open parameters collected by the target control (empty specific rendering information) are first intercepted, and the micro-application page identifier and micro-application page path of the first micro-application are filled into the collected open parameters to update the open parameters, and the updated open parameters are forwarded to the simulator server. In addition, after the forwarding is completed, a successful call prompt is returned to the first micro-application to confirm that the micro-application page rendering information is successfully sent to the simulator according to the modified target basic application ready information.

[0307] In an embodiment of the present disclosure, micro-application page rendering information is loaded in a target protocol field.

[0308] The target protocol field refers to a code segment that meets the format specified by the transmission requirements of the simulator and contains specific transmission parameters or specific transmission content.

[0309] Please refer to Fig.21 In one embodiment, the specific process of step 1340 includes but is not limited to the following steps 2110-2140:

[0310] Step 2110: If a target protocol field is detected in the message channel of the simulator, the micro-application page rendering information is parsed from the target protocol field;

[0311] Step 2120: Send the micro-application page identifier to the application interface corresponding to the target basic application, so as to receive the reference page identifier corresponding to the first micro-application interface from the application interface;

[0312] Step 2130: Generate combined page rendering information of the first micro-application interface based on the reference page identifier and the micro-application page path;

[0313] Step 2140: Based on the combined page rendering information, the basic application interface is displayed, and the first micro-application interface is rendered within the basic application interface.

[0314] Steps 2110-2140 are described in detail below.

[0315] In step 2110, if a target protocol field is detected in the message channel of the simulator, micro-application page rendering information is parsed from the target protocol field.

[0316] The message channel refers to the space used to store various file messages received by the simulator.

[0317] The micro-application page rendering information includes a micro-application page identifier and a micro-application page path corresponding to the first micro-application interface.

[0318] In the specific implementation of this embodiment, if the target protocol field is detected in the simulator's message channel, it indicates that the simulator has successfully obtained the micro-application page rendering information of the first micro-application. Based on this, the simulator server will first extract the written target protocol field from the message channel; then, perform field parsing on the target protocol field, obtain the specific field values ​​of each field in the target protocol field, and determine the micro-application page rendering information according to the specific field values.

[0319] In step 2120, a micro-application page identifier is sent to an application interface corresponding to the target basic application to receive a reference page identifier corresponding to the first micro-application interface from the application interface.

[0320] The application interface refers to the API interface for data transmission between the basic server corresponding to the target basic application and other servers (such as micro-application servers, simulator servers or third-party application servers).

[0321] The reference page identifier is used to indicate that the target basic application is page identifier information specified by the first micro-application.

[0322] To save space, the specific process of obtaining the reference page identifier corresponding to the first micro-application interface in the embodiment of the present disclosure will be described in detail below and will not be repeated here.

[0323] In step 2130 , based on the reference page identifier and the micro-application page path, combined page rendering information of the first micro-application interface is generated.

[0324] The combined page rendering information is used to indicate the parameter information actually required to render the first micro-application interface on the basic application interface of the target basic application.

[0325] In the specific implementation of this embodiment, the reference page identifier and the micro-application page path can be spliced ​​into a whole, and the splicing result of the reference page identifier and the micro-application page path is used as the combined page rendering information of the first micro-application interface.

[0326] In step 2140 , based on the combined page rendering information, the basic application interface is displayed, and the first micro-application interface is rendered within the basic application interface.

[0327] In the specific implementation of this embodiment, after generating the combined page rendering information of the first micro-application interface, the simulator will first request the application server corresponding to the target basic application to call the application interface of the target basic application; then, based on the called application interface, the basic application interface of the target basic application is loaded, and within the basic application interface, the first micro-application interface of the first micro-application is rendered according to the combined page rendering information.

[0328] The benefit of this embodiment is that the micro-application rendering information is loaded into the target protocol field and written into the simulator's message channel, which can improve the security and integrity of information writing. Furthermore, after parsing the micro-application page rendering information from the target protocol field, the reference page identifier corresponding to the micro-application page identifier is obtained from the target basic application, and the reference page identifier and the micro-application page path are spliced ​​into the combined page rendering information, which can improve the information standardization of the combined page rendering information, and is conducive to improving the accuracy and reliability of the first micro-application interface rendered based on the combined page rendering information.

[0329] Since the page identifiers of applications such as the first micro-application are often defined by each application itself, the page identifiers of different applications often follow different definition rules. Based on this, in order to improve the accuracy of page rendering, a set of more standardized and unified definition rules are often set in the basic application to identify the page identifiers of each application. Therefore, the disclosed embodiment provides a solution for introducing a page identifier replacement operation when opening the first micro-application, which can more easily obtain the page identifier specified by the target basic application for the first micro-application, which is conducive to improving the rendering accuracy of the first micro-application interface.

[0330] Please refer to Fig. 22 In one embodiment, the specific process of step 2120 includes but is not limited to the following steps 2210-2220:

[0331] Step 2210: Send the micro-application page identifier to the application interface corresponding to the target basic application, so that the application interface determines the reference page identifier according to the preset identifier mapping table and the micro-application page identifier, and returns the reference page identifier;

[0332] Step 2220: Receive a reference page identifier corresponding to the first micro-application interface from the application interface.

[0333] Steps 2210-2220 are described in detail below.

[0334] In step 2210, the micro-application page identifier is sent to the application interface corresponding to the target basic application, so that the application interface determines the reference page identifier according to the preset identifier mapping table and the micro-application page identifier, and returns the reference page identifier.

[0335] The preset identifier mapping table is used to indicate the correspondence between the candidate page identifiers and the candidate reference identifiers of each candidate application page, and the base page identifier is the candidate reference identifier corresponding to the candidate page identifier that is consistent with the micro-application page identifier.

[0336] The candidate application page is used to indicate the application page of each candidate application program that can be rendered and displayed in the basic application interface of the target basic application.

[0337] The candidate page identifier is used to indicate identification information set by each candidate application program and capable of distinguishing the application page corresponding to the candidate application program from program pages of other candidate application programs.

[0338] The candidate reference identifier is used to indicate identification information of a program page set by the target basic application and capable of distinguishing different candidate application programs.

[0339] In the specific implementation of this embodiment, first, the simulator server sends the micro-application page identifier to the application interface corresponding to the target basic application, so that the application interface of the target basic application searches for the candidate page identifier that is the same as the micro-application page identifier in the maintained preset identifier mapping table according to the micro-application page identifier, and determines the candidate reference identifier corresponding to the candidate page identifier as the benchmark page identifier, thereby returning the benchmark page identifier.

[0340] In step 2220, a reference page identifier corresponding to the first micro-application interface is received from the application interface.

[0341] In the specific implementation of this embodiment, after finding the reference page identifier using the application interface of the target basic application, the target basic application transmits the reference page identifier to the simulator through the application interface. Based on this, the simulator can receive the reference page identifier corresponding to the first micro-application interface from the application interface.

[0342] like Fig.23As shown, it is a specific schematic diagram of searching for a reference page identifier corresponding to a micro-application page identifier in a preset identifier mapping table. Specifically, there is a correspondence between the candidate page identifier (username) and the candidate reference identifier (wxappid) of each candidate application page in the preset mapping table. Among them, the candidate reference identifier of the candidate application page with the candidate page identifier Youxi001 is A1; the candidate reference identifier of the candidate application page with the candidate page identifier Youxi002 is A2; the candidate reference identifier of the candidate application page with the candidate page identifier Bangong001 is B1; the candidate reference identifier of the candidate application page with the candidate page identifier Bangong002 is B2; ...; the candidate reference identifier of the candidate application page with the candidate page identifier Gouwu001 is K1; the candidate reference identifier of the candidate application page with the candidate page identifier Gouwu002 is K2. Based on this, when the micro-application page identifier of the first micro-application is Youxi002, the candidate reference identifier corresponding to it can be queried in the preset identifier mapping table as A2, so the reference page identifier is determined to be A2.

[0343] The benefit of this embodiment is that a page identifier replacement operation is introduced when opening the first micro-application, and the micro-application page identifier of the first micro-application is compared with each candidate page identifier in the preset mapping table, so that the page identifier (base page identifier) ​​specified by the target basic application for the first micro-application can be obtained more conveniently, and the base page identifier and the micro-application page path can be integrated into the final combined page rendering information, which can improve the format standardization and information accuracy of the combined page rendering information, thereby improving the rendering accuracy of the first micro-application interface.

[0344] Please refer to Fig.24 In one embodiment, the specific process of generating the target protocol field includes but is not limited to the following steps 2410-2430:

[0345] Step 2410: Obtain a first character string indicating a micro-application page identifier and a second character string indicating a micro-application page path from the micro-application page rendering information;

[0346] Step 2420: Obtain a preset protocol field template;

[0347] Step 2430: fill the first string into the page identification field, and fill the second string into the page path field to generate a target protocol field.

[0348] Steps 2410-2430 are described in detail below.

[0349] In step 2410 , a first character string indicating a micro-application page identifier and a second character string indicating a micro-application page path are obtained from the micro-application page rendering information.

[0350] In the specific implementation of this embodiment, with authorization permission, information items are extracted from the micro-application page rendering information containing multiple information items to obtain a first character string indicating the micro-application page identifier and a second character string indicating the micro-application page path.

[0351] In step 2420, a preset protocol field template is obtained.

[0352] The protocol field template includes a page identification field and a page path field.

[0353] The page identification field is used to indicate the writing location of specific content related to identifying the application page of each application program.

[0354] The page path field is used to indicate the writing location of specific resource content related to rendering the application page of each application.

[0355] In the specific implementation of this embodiment, the protocol field template is pre-defined by the simulator server, and the protocol field template meets the protocol transmission requirements of the simulator server. Based on this, the pre-defined protocol field template can be directly called under the condition of authorization.

[0356] In step 2430, the first character string is filled into the page identification field, and the second character string is filled into the page path field, so as to fill the content of the protocol field template and generate the target protocol field.

[0357] For example, in a specific example, the preset protocol field template may include an indication field "androws: / / app / openWxAppFromEmulator"; a page identification field "username" and a page path field "apk_deep_link", wherein the indication field indicates that the micro-application is opened in the target basic application. Based on this, when the first string corresponding to the micro-application page identification is gh_e4926036e01d and the second string corresponding to the micro-application page path is %3Fwxgamepro%3DCpsCBgAAoXkpQY8rGUblwrOd, the target protocol field can be expressed as "androws: / / app / openWxAppFromEmulator?username=gh_e4926036e01d&apk_deep_link=%3Fwxgamepro%3DCpsCBgAAoXkpQY8rGUblwrOd".

[0358] The advantage of this embodiment is that the first string indicating the micro-application page identifier and the second string field indicating the micro-application page path in the micro-application page rendering information are loaded into a preset protocol field template, which can improve the storage standardization of the micro-application page rendering information. At the same time, the field format of the target protocol field is relatively fixed. Using the target protocol field for information transmission can better improve the information transmission efficiency and reduce the parsing complexity of the target protocol field.

[0359] Combine the following FIG. 25A to FIG. 25B The specific process of opening the first micro-application interface of the first micro-application according to the micro-application page rendering information is described in detail.

[0360] like Fig.25A As shown, it is a specific indication that the micro-application page rendering information is forwarded to the simulator. Specifically, when the first micro-application opening control of the first micro-application is embedded in a third-party application, the opening parameters (micro-application page rendering information) of the first micro-application can be obtained by the third-party application, and the opening parameters are written into the message channel of the simulator by the third-party application. Based on this, the back-end server of the simulator can obtain the write data of the message channel in real time, and when the opening parameters are detected to be written in the message channel, the back-end of the simulator will forward the opening parameters to the front end of the simulator.

[0361] like Fig.25B As shown, it is a schematic diagram of the process of the specific operation performed by the front end of the simulator according to the opening parameters of the first micro-application. Specifically, after the front end of the simulator receives the opening parameters, it will first request the target basic application to obtain the reference page identifier through the micro-application page identifier in the opening parameters. Then, after obtaining the reference page identifier, the open platform interface of the target basic application is called, and the reference page identifier and the micro-application page path are passed, so as to open the first micro-application interface of the first micro-application on the basic application interface of the target basic application.

[0362] Refer to the following Fig.26 A specific implementation process of the micro-application opening method of the embodiment of the present disclosure is described in detail.

[0363] like Fig.26As shown, it is the specific process of opening the first micro-application in the simulator. Specifically, first, open a third-party application on the simulator front-end interface, wherein the third-party application is a third-party application where the micro-application opening control of the first micro-application is located. Then, click the entry control (micro-application opening control) of the first micro-application on the third-party application, and query the back-end server corresponding to the simulator to interact to determine whether the target basic application mounted by the first micro-application has been installed. At this time, when the target basic application is not installed on the simulator, the back-end server corresponding to the simulator will generate a modified target basic application ready information, and return the modified target basic application ready information to the third-party application, informing the third-party application and the first micro-application that the target basic application has been installed. Further, call the micro-application interface of the first micro-application on the third-party application, and call the target control, so that the back-end server corresponding to the simulator sends the obtained micro-application page rendering information (username+path) to the front end of the simulator. Then, the front end of the simulator will request the back-end server of the target basic application to obtain the reference page identification (wxAPPid) through the micro-application page identification (Username), and receive the reference page identification returned by the back-end server of the target basic application. Finally, the front end of the simulator will open the basic application interface of the target basic application on the front end interface of the simulator based on the baseline page identifier and the micro-application page path, and display the opened first micro-application interface in the basic application interface.

[0364] The following describes the apparatus and devices of the embodiments of the present disclosure.

[0365] It is to be understood that, although the steps in the above-mentioned flowcharts are sequentially displayed according to the characterization of arrows, these steps are not necessarily executed in sequence according to the order of arrow characterization. Unless there is a clear description in the present embodiment, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the above-mentioned flowcharts can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the steps or stages in other steps.

[0366] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to the characteristics of the target object such as the target object attribute information or attribute information set, the permission or consent of the target object will be obtained first, and the collection, use and processing of these data will comply with relevant laws, regulations and standards. In addition, when the embodiment of the present application needs to obtain the attribute information of the target object, the separate permission or separate consent of the target object will be obtained through a pop-up window or jump to a confirmation page. After clearly obtaining the separate permission or separate consent of the target object, the necessary target object-related data used to enable the normal operation of the embodiment of the present application is obtained.

[0367] Fig. 27 A schematic diagram of the structure of a micro-application opening device 2700 provided in an embodiment of the present disclosure. The micro-application opening device 2700 includes:

[0368] The first display unit 2710 is used to display a simulator interface in response to a trigger on the simulator on the first device, wherein the simulator interface is used to simulate the display interface of the second device, the simulator interface has a first micro-application opening control of the first micro-application, and the target basic application to which the first micro-application is mounted is not loaded on the display interface;

[0369] The second display unit 2720 is used to display a basic application interface of the target basic application in response to triggering the first micro-application opening control, where the basic application interface includes the first micro-application interface of the first micro-application.

[0370] Optionally, the simulator interface has third-party application controls;

[0371] The second display unit 2720 is used for:

[0372] In response to triggering the third-party application control, displaying the third-party application interface, where the third-party application interface has a first micro-application opening control;

[0373] In response to triggering an opening control of the first micro-application on the third-party application interface, a basic application interface of the target basic application is displayed.

[0374] Optionally, the second display unit 2720 is used for:

[0375] In response to triggering the first micro-application opening control, displaying a confirmation area, the confirmation area including a confirmation control for confirming display of the basic application interface;

[0376] In response to triggering the confirmation control, a basic application interface of the target basic application is displayed.

[0377] Optionally, the second display unit 2720 is used for:

[0378] In response to triggering the first micro-application opening control, displaying a login area of ​​the target basic application;

[0379] In response to inputting login information of a target user in the login area, if the login information is verified, a basic application interface of the target basic application corresponding to the target user is displayed.

[0380] Optionally, the micro-application opening device 2700 further includes a third display unit (not shown), and the third display unit (not shown) is used to:

[0381] In response to inputting the login information of the target user in the login area, in the case where the login information verification fails, a verification failure interface is displayed.

[0382] Optionally, the first micro-application is mounted to a plurality of candidate basic applications;

[0383] The second display unit 2720 is used for:

[0384] In response to triggering the first micro-application opening control, displaying a selection area, the selection area including a plurality of selection controls corresponding to a plurality of candidate basic applications;

[0385] In response to triggering a target selection control corresponding to a target basic application among the plurality of selection controls, a basic application interface of the target basic application is displayed.

[0386] Optionally, the simulator interface further has a second micro-application opening control for the second micro-application, and the second micro-application is mounted to the target basic application;

[0387] The micro-application opening device 2700 further includes a fourth display unit (not shown), which is used to:

[0388] In response to triggering the second micro-application opening control, a basic application interface of the target basic application is displayed, and the first micro-application interface and the second micro-application interface are displayed side by side in the basic application interface.

[0389] Optionally, the second display unit 2720 includes:

[0390] an identification module (not shown), configured to identify that a target basic application is not loaded on the display interface in response to triggering the first micro-application opening control;

[0391] A generating module (not shown), used to generate altered target basic application ready information;

[0392] A sending module (not shown), configured to send the modified target basic application ready information to the micro-application interface corresponding to the first micro-application, so as to receive the micro-application page rendering information of the first micro-application from the micro-application interface;

[0393] The display module (not shown) is used to display the basic application interface and render the first micro-application interface based on the micro-application page rendering information within the basic application interface.

[0394] Optionally, the generating module (not shown) includes:

[0395] An acquisition submodule (not shown), configured to acquire micro-application page attribute information of the first micro-application;

[0396] A verification submodule (not shown), configured to perform a first verification on the micro-application page attribute information;

[0397] A generating submodule (not shown) is used to generate altered target basic application readiness information if it is determined that the first verification passes.

[0398] Optionally, a verification submodule (not shown) is used to:

[0399] Acquire candidate application information of a plurality of candidate applications, wherein the plurality of candidate applications are mounted to a target basic application, and the candidate applications are not allowed to generate or alter the target basic application ready information when triggered;

[0400] comparing the micro-application page attribute information with each candidate application information;

[0401] If it is determined that the micro-application page attribute information is inconsistent with each candidate application information, it is determined that the first verification is passed.

[0402] Optionally, a generation submodule (not shown) is used to:

[0403] Obtain application attribute information and application version information of the target basic application;

[0404] Generate a signature based on the application attribute information to obtain application signature information;

[0405] The application version information and the application signature information are integrated into the modification target basic application readiness information.

[0406] Optionally, the sending module (not shown) is used to:

[0407] Sending the modified target basic application ready information to the micro-application interface corresponding to the first micro-application, so that the micro-application interface determines that the target basic application has been loaded on the simulator based on the modified target basic application ready information, and fills the micro-application page identifier and micro-application page path of the first micro-application into the obtained first micro-application page parameter to construct the micro-application page rendering information, and sends the micro-application page rendering information to the simulator;

[0408] Receive micro-application page rendering information of the first micro-application from the micro-application interface.

[0409] Optionally, the micro-application opening device 2700 further includes a prompt unit (not shown), which is used to:

[0410] Based on the constructed micro-application page rendering information, generate a first prompt, wherein the first prompt is used to indicate that the first micro-application interface of the first micro-application has been successfully called;

[0411] The first prompt is sent to an application server corresponding to the first micro-application.

[0412] Optionally, the micro-application page rendering information is loaded in the target protocol field;

[0413] The display module (not shown) is used to:

[0414] If a target protocol field is detected in the message channel of the simulator, the micro-application page rendering information is parsed from the target protocol field, wherein the micro-application page rendering information includes a micro-application page identifier and a micro-application page path corresponding to the first micro-application interface;

[0415] Sending a micro-application page identifier to an application interface corresponding to a target basic application to receive a reference page identifier corresponding to a first micro-application interface from the application interface;

[0416] Generate combined page rendering information of the first micro-application interface based on the reference page identifier and the micro-application page path;

[0417] Based on the combined page rendering information, the basic application interface is displayed, and the first micro-application interface is rendered within the basic application interface.

[0418] Optionally, the Target Protocol field is generated by:

[0419] Obtaining a first character string indicating a micro-application page identifier and a second character string indicating a micro-application page path from the micro-application page rendering information;

[0420] Obtaining a preset protocol field template, wherein the protocol field template includes a page identification field and a page path field;

[0421] The first string is filled into the page identification field, and the second string is filled into the page path field to generate a target protocol field.

[0422] Optionally, sending a micro-application page identifier to an application interface corresponding to a target basic application to receive a reference page identifier corresponding to a first micro-application interface from the application interface includes:

[0423] Send the micro-application page identifier to the application interface corresponding to the target basic application, so that the application interface determines the reference page identifier according to the preset identifier mapping table and the micro-application page identifier, and returns the reference page identifier, wherein the preset identifier mapping table is used to indicate the correspondence between the candidate page identifiers and the candidate reference identifiers of each candidate application page, and the reference page identifier is the candidate reference identifier corresponding to the candidate page identifier consistent with the micro-application page identifier;

[0424] A reference page identifier corresponding to the first micro-application interface is received from the application interface.

[0425] Reference Fig.28 , Fig.28 The structural block diagram of the object terminal of the micro-application opening method of the embodiment of the present disclosure is as follows: the object terminal includes: a radio frequency (RF) circuit 2810, a memory 2815, an input unit 2830, a display unit 2840, a sensor 2850, an audio circuit 2860, a wireless fidelity (WiFi) module 2870, a processor 2880, and a power supply 2890. Those skilled in the art can understand that Fig.28 The terminal structure shown does not constitute a limitation on the mobile phone or computer, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0426] The RF circuit 2810 may be used for receiving and sending signals during information transmission or calls. In particular, after receiving the downlink information from the base station, it is sent to the processor 2880 for processing; in addition, the designed uplink data is sent to the base station.

[0427] The memory 2815 may be used to store software programs and modules. The processor 2880 executes various functional applications and data processing of the target terminal by running the software programs and modules stored in the memory 2815 .

[0428] The input unit 2830 may be used to receive input digital or character information and generate key signal input related to the setting and function control of the target terminal. Specifically, the input unit 2830 may include a touch panel 2831 and other input devices 2832.

[0429] The display unit 2840 may be used to display input information or provided information and various menus of the target terminal. The display unit 2840 may include a display panel 2841.

[0430] The audio circuit 2860, the speaker 2861, and the microphone 2862 may provide an audio interface.

[0431] In this embodiment, the processor 2880 included in the target terminal can execute the micro-application opening method of the previous embodiment.

[0432] The embodiments of the present invention can be applied to various scenarios, including but not limited to data security, blockchain, data storage, information technology, and application treasures.

[0433] Fig.29 A block diagram of the structure of the server for implementing the micro-application opening method of the embodiment of the present disclosure. The server may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPU) 2922 (for example, one or more processors) and memory 2932, one or more storage media 2930 (for example, one or more mass storage devices) storing application programs 2942 or data 2944. Among them, memory 2932 and storage medium 2930 can be short-term storage or permanent storage. The program stored in storage medium 2930 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the server. Further, the central processing unit 2922 can be configured to communicate with the storage medium 2930, and execute a series of instruction operations in the storage medium 2930 on the server.

[0434] The server may also include one or more power supplies 2923, one or more wired or wireless network interfaces 2950, ​​one or more input and output interfaces 2958, and / or one or more operating systems 2941, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

[0435] The central processor 2922 in the server can be used to execute the micro-application opening method of the embodiment of the present disclosure.

[0436] The embodiments of the present disclosure also provide a computer-readable storage medium, which is used to store a computer program, and the computer program is used to execute the micro-application opening method of each of the aforementioned embodiments.

[0437] The embodiment of the present disclosure also provides a computer program product, which includes a computer program. A processor of a computer device reads and executes the computer program, so that the computer device executes and implements the above-mentioned micro-application opening method.

[0438] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present disclosure described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "comprises" and "comprising" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0439] It should be understood that in the present disclosure, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0440] It should be understood that in the description of the embodiments of the present disclosure, the meaning of multiple (or multiple items) is more than two, greater than, less than, exceed, etc. are understood to not include the number, and above, below, within, etc. are understood to include the number.

[0441] In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0442] In the embodiments of the present disclosure, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0443] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0444] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0445] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store program codes.

[0446] It should also be understood that the various implementations provided in the embodiments of the present disclosure can be combined arbitrarily to achieve different technical effects.

[0447] The above is a specific description of the implementation methods of the present disclosure, but the present disclosure is not limited to the above implementation methods. Technical personnel familiar with the art can also make various equivalent modifications or substitutions without violating the spirit of the present disclosure. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present disclosure.

Claims

1. A method for opening a micro application, characterized in that: The method comprises: In response to triggering the simulator on the first device, displaying a simulator interface, wherein the simulator interface is used to simulate a display interface of the second device, the simulator interface has a first micro-application opening control of the first micro-application, and the target basic application to which the first micro-application is mounted is not loaded on the display interface; In response to triggering the first micro-application opening control, a basic application interface of the target basic application is displayed, wherein the basic application interface includes a first micro-application interface of the first micro-application.

2. The micro-application opening method according to claim 1, characterized in that: The simulator interface has third-party application controls; The step of displaying the basic application interface of the target basic application in response to triggering the first micro-application opening control includes: In response to triggering the third-party application control, displaying a third-party application interface, wherein the third-party application interface has the first micro-application opening control; In response to triggering the first micro-application opening control on the third-party application interface, the basic application interface of the target basic application is displayed.

3. The micro-application opening method according to claim 1, characterized in that: The step of displaying the basic application interface of the target basic application in response to triggering the first micro-application opening control includes: In response to triggering the first micro-application opening control, displaying a confirmation area, the confirmation area including a confirmation control for confirming display of the basic application interface; In response to triggering the confirmation control, the basic application interface of the target basic application is displayed.

4. The micro-application opening method according to claim 1, characterized in that: The step of displaying the basic application interface of the target basic application in response to triggering the first micro-application opening control includes: In response to triggering the first micro-application opening control, displaying a login area of ​​the target basic application; In response to inputting login information of a target user in the login area, if the login information is verified, displaying the basic application interface of the target basic application corresponding to the target user.

5. The micro-application opening method according to claim 4, characterized in that: After displaying the login area of ​​the target basic application in response to triggering the first micro-application opening control, the method further includes: In response to inputting the login information of the target user in the login area, if the login information verification fails, a verification failure interface is displayed.

6. The micro-application opening method according to claim 1, characterized in that: The first micro-application is mounted to a plurality of candidate basic applications; The step of displaying the basic application interface of the target basic application in response to triggering the first micro-application opening control includes: In response to triggering the first micro-application opening control, displaying a selection area, the selection area including a plurality of selection controls corresponding to the plurality of candidate basic applications; In response to triggering a target selection control corresponding to the target basic application among the multiple selection controls, the basic application interface of the target basic application is displayed.

7. The micro-application opening method according to claim 1, characterized in that: The simulator interface also has a second micro-application opening control for a second micro-application, and the second micro-application is mounted to the target basic application; After displaying the basic application interface of the target basic application in response to triggering the first micro-application opening control, the method further includes: In response to triggering the second micro-application opening control, the basic application interface of the target basic application is displayed, and the first micro-application interface and the second micro-application interface are displayed side by side in the basic application interface.

8. The micro-application opening method according to claim 1, characterized in that: The step of displaying the basic application interface of the target basic application in response to triggering the first micro-application opening control includes: In response to triggering the first micro-application opening control, identifying that the target basic application is not loaded on the display interface; Generates modification target basic application readiness information; Sending the modified target basic application ready information to the micro-application interface corresponding to the first micro-application to receive the micro-application page rendering information of the first micro-application from the micro-application interface; The basic application interface is displayed, and within the basic application interface, the first micro-application interface is rendered based on the micro-application page rendering information.

9. The micro-application opening method according to claim 8, characterized in that: The generating and modifying target basic application readiness information includes: Obtaining micro-application page attribute information of the first micro-application; Performing a first verification on the micro-application page attribute information; If it is determined that the first verification passes, the altered target basic application readiness information is generated.

10. The micro-application opening method according to claim 9, characterized in that: The first verification of the micro-application page attribute information includes: Acquire candidate application information of a plurality of candidate applications, wherein the plurality of candidate applications are mounted to the target basic application, and the candidate applications are not allowed to generate the altered target basic application ready information when triggered; Compare the micro-application page attribute information with each of the candidate application information; If it is determined that the micro-application page attribute information is inconsistent with each of the candidate application information, it is determined that the first verification is passed.

11. The micro-application opening method according to claim 9, characterized in that: The generating and modifying target basic application readiness information includes: Obtaining application attribute information and application version information of the target basic application; Generate a signature based on the application attribute information to obtain application signature information; The application version information and the application signature information are integrated into the altered target basic application ready information.

12. The micro-application opening method according to claim 8, characterized in that: The sending the modified target basic application ready information to the micro-application interface corresponding to the first micro-application to receive the micro-application page rendering information of the first micro-application from the micro-application interface includes: Sending the modified target basic application ready information to the micro-application interface corresponding to the first micro-application, so that the micro-application interface determines that the target basic application has been loaded on the simulator based on the modified target basic application ready information, and filling the micro-application page identifier and micro-application page path of the first micro-application into the obtained first micro-application page parameter to construct the micro-application page rendering information, and sending the micro-application page rendering information to the simulator; Receive micro-application page rendering information of the first micro-application from the micro-application interface.

13. The micro-application opening method according to claim 12, characterized in that: After sending the micro-application page rendering information to the simulator, the method further includes: Generate a first prompt based on the constructed micro-application page rendering information, wherein the first prompt is used to indicate that the first micro-application interface of the first micro-application has been successfully called; The first prompt is sent to an application server corresponding to the first micro-application.

14. The micro-application opening method according to claim 8, characterized in that: The micro-application page rendering information is loaded in the target protocol field; The displaying of the basic application interface and rendering the first micro-application interface based on the micro-application page rendering information in the basic application interface includes: If the target protocol field is detected in the message channel of the simulator, the micro-application page rendering information is parsed from the target protocol field, wherein the micro-application page rendering information includes a micro-application page identifier and a micro-application page path corresponding to the first micro-application interface; Sending the micro-application page identifier to the application interface corresponding to the target basic application to receive the reference page identifier corresponding to the first micro-application interface from the application interface; Based on the reference page identifier and the micro-application page path, generating combined page rendering information of the first micro-application interface; Based on the combined page rendering information, the basic application interface is displayed, and the first micro-application interface is rendered within the basic application interface.

15. A micro-application opening device, characterized in that: The device comprises: A first display unit is configured to display a simulator interface in response to a trigger on the simulator on the first device, wherein the simulator interface is used to simulate a display interface of the second device, the simulator interface has a first micro-application opening control of the first micro-application, and the target basic application to which the first micro-application is mounted is not loaded on the display interface; The second display unit is configured to display a basic application interface of the target basic application in response to triggering an opening control of the first micro-application, wherein the basic application interface includes a first micro-application interface of the first micro-application.

16. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the micro-application opening method described in any one of claims 1 to 14 is implemented.

17. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the micro-application opening method described in any one of claims 1 to 14 is implemented.

18. A computer program product, comprising a computer program, wherein the computer program is read and executed by a processor of an electronic device, so that the electronic device executes the micro-application opening method according to any one of claims 1 to 14.

Images