Interaction method, device and computer equipment among micro-applications

Abstract

This application provides a method, apparatus, and computer device for interaction between micro-applications, belonging to the field of computer technology. The method includes: in response to receiving a call instruction from a first micro-application to a first application interface through a client of a target application, obtaining first interface parameters; based on an interface identifier, launching a second micro-application in the client, and sending the interface identifier and call parameters to the second micro-application; in response to receiving a call instruction from the second micro-application to a second application interface through the client, returning the second interface parameters to the first micro-application. This solution eliminates the need for specific application adaptation between micro-applications, enabling interaction between micro-applications via a client of the target application.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus and computer device for interaction between micro-applications. Background Technology

[0002] With the development of computer technology, micro-applications have enabled a wide variety of functions, such as shopping, playing games, and office work. Micro-applications are applications that can be used without downloading and installation, typically relying on an already installed application to run. Because micro-applications are usually independent of each other, different micro-applications relying on the same application cannot interact with each other.

[0003] For example, since micro-application A, which implements the approval function, and micro-application B, which implements the procurement function, are independent of each other, additional application adaptation is usually required to connect the two micro-applications and enable them to interact to realize the approval and procurement of office supplies.

[0004] However, due to the sheer number of micro-applications and the fact that different micro-applications may belong to different service providers, a single micro-application may need to be adapted for different micro-applications, resulting in high interaction costs between different micro-applications. Summary of the Invention

[0005] This application provides a method, apparatus, and computer device for interaction between micro-applications. It enables interaction between micro-applications, using the client of the target application as an intermediary, without requiring specific application adaptation between the micro-applications. The technical solution is as follows:

[0006] On the one hand, a method for interaction between micro-applications is provided, the method comprising:

[0007] In response to receiving a call instruction from the first micro-application to the first application interface through the client of the target application, the first interface parameters are obtained. The first application interface is provided by the client. The first interface parameters are the parameters required to call the first application interface. The first interface parameters include the interface identifier of the first business interface and the call parameters of the first business interface. The first micro-application runs on the basis of the target application.

[0008] Based on the interface identifier, a second micro-application is launched in the client, and the interface identifier and the calling parameters are sent to the second micro-application. The second micro-application is used to provide the first business interface, and the second micro-application runs on the basis of the target application.

[0009] In response to receiving a call instruction from the second micro-application to the second application interface through the client, the second interface parameters are returned to the first micro-application. The second application interface is provided by the client, and the second interface parameters are the parameters required to call the second application interface, including the processing result obtained from calling the first business interface.

[0010] On the other hand, a method for interaction between micro-applications is provided, which is applied to a target server, the target server being used to provide background services for the target application;

[0011] The method includes:

[0012] In response to the first server's call instruction to the first service interface, the third interface parameters are obtained. The first server is used to provide background services for the first micro-application. The first service interface is provided by the target server. The third interface parameters are the parameters required to call the first service interface. The third interface parameters include the interface identifier of the second business interface and the call parameters of the second business interface. The first micro-application runs on the basis of the target application.

[0013] In response to the inclusion of a first account identifier in the first micro-application in the call parameters, the first account identifier is converted into a second account identifier in the second micro-application, and both of the second micro-applications rely on the target application to run;

[0014] The first micro-application sends the fourth interface parameters returned by the second server through the second service interface to the first server. The processing result included in the fourth interface parameters is displayed by the first micro-application. The second service interface is provided by the target server. The second server is used to provide background services for the second micro-application. The processing result is obtained by the second server calling the second business interface based on the call parameters and the second account identifier.

[0015] On the other hand, an interaction device between micro-applications is provided, the device comprising:

[0016] The parameter acquisition module is used to respond to receiving a call instruction from the first micro-application to the first application interface through the client of the target application, and to acquire the first interface parameters. The first application interface is provided by the client, and the first interface parameters are the parameters required to call the first application interface. The first interface parameters include the interface identifier of the first business interface and the call parameters of the first business interface. The first micro-application runs on the target application.

[0017] The sending module is used to launch a second micro-application in the client based on the interface identifier, and send the interface identifier and the calling parameters to the second micro-application. The second micro-application is used to provide the first business interface, and the second micro-application runs on the target application.

[0018] The parameter return module is used to respond to the client receiving a call instruction from the second micro-application to the second application interface, and to return the second interface parameters to the first micro-application. The second application interface is provided by the client, and the second interface parameters are the parameters required to call the second application interface, including the processing result obtained from calling the first business interface.

[0019] In some embodiments, the invocation instruction of the first application interface is triggered based on the first interface, which is provided by the first micro-application;

[0020] The device further includes:

[0021] A first display module is used to display the first interface through the client, wherein the first interface displays a first control;

[0022] The first generation module is used to respond to the trigger operation of the first control and generate a call instruction for the first application interface based on the content entered in the first interface through the first micro-application.

[0023] In some embodiments, the call instruction of the second application interface is triggered based on the second interface, which is obtained by the second micro-application calling the first business interface based on the call parameters;

[0024] The device further includes:

[0025] The second display module is used to display the second interface through the client, and the second interface displays the second control.

[0026] The second generation module is used to respond to the trigger operation of the second control and generate a call instruction for the second application interface based on the content entered in the second interface through the second micro-application.

[0027] In some embodiments, the first interface parameter further includes the application identifier of the second micro-application;

[0028] The sending module is configured to, based on the interface identifier, obtain at least one third micro-application that provides the first service interface from multiple micro-applications, wherein the multiple micro-applications run on the target application; determine the second micro-application from the at least one third micro-application based on the application identifier; and launch the second micro-application in the client.

[0029] In some embodiments, the sending module is configured to determine the interface level of the first service interface based on the interface identifier; in response to the interface level being greater than the account level of the client's logged-in account, display a first prompt message on the client, the first prompt message indicating that there is no permission to call the first service interface; and in response to the interface level not being greater than the account level of the client's logged-in account, launch the second micro-application in the client.

[0030] In some embodiments, the sending module is configured to display at least one candidate micro-application through the client based on the interface identifier, the candidate micro-application being used to provide the first service interface; and to launch the second micro-application selected from the at least one candidate micro-application in the client.

[0031] In some embodiments, the sending module is configured to obtain at least one third micro-application providing the first service interface from multiple micro-applications based on the interface identifier, wherein the multiple micro-applications run on the target application; determine the second micro-application from the at least one third micro-application based on the historical call behavior of the account logged in by the client; and start the second micro-application in the client.

[0032] On the other hand, an interaction device between micro-applications is provided, which is deployed in a target server, the target server being used to provide background services for the target application;

[0033] The device includes:

[0034] The parameter acquisition module is used to obtain third interface parameters in response to the call instruction of the first server to the first service interface. The first server is used to provide background services for the first micro-application. The first service interface is provided by the target server. The third interface parameters are the parameters required to call the first service interface. The third interface parameters include the interface identifier of the second business interface and the call parameters of the second business interface. The first micro-application runs on the basis of the target application.

[0035] The account identifier conversion module is used to convert the first account identifier in the first micro-application into a second account identifier in the second micro-application in response to the call parameters including the first account identifier in the first micro-application. Both of the second micro-applications rely on the target application to run.

[0036] The parameter return module is used to send the fourth interface parameters returned by the second server through the second service interface to the first server. The first micro-application displays the processing results included in the fourth interface parameters. The second service interface is provided by the target server. The second server is used to provide background services for the second micro-application. The processing results are obtained by the second server calling the second business interface based on the call parameters and the second account identifier.

[0037] In some embodiments, the first account identifier and the second account identifier are obtained by using different encryption methods from the target account of the target application, and the third interface parameter also includes the server identifier of the second server, and the target account is the account logged in by the target application;

[0038] The account identifier conversion module is used to respond to the call parameters including a first account identifier in the first micro-application, decrypt the first account identifier based on the encryption method corresponding to the first server to obtain the target account; determine the encryption method corresponding to the second server based on the server identifier of the second server; and encrypt the target account based on the encryption method corresponding to the second server to obtain the second account identifier.

[0039] In some embodiments, the calling parameters further include a device identifier, which is used to indicate the device on which the target application is installed;

[0040] The account identifier conversion module is configured to, in response to the call parameters including a first account identifier in the first micro-application, obtain a second account identifier from the device based on the device identifier; and replace the first account identifier in the call parameters with the second account identifier in the second micro-application.

[0041] In some embodiments, the apparatus further includes:

[0042] The interface return module is used to respond to receiving an interface registration request sent through the terminal and return an interface registration interface to the terminal. The interface registration interface is used to input the information of the target interface of the micro-application.

[0043] The information receiving module is used to receive interface information of the target interface sent by the terminal, wherein the interface information includes the name of the target interface and the form of the calling parameters of the target interface;

[0044] The entry display module is used to display the information entry of the target interface on the interface display interface. The information entry is used to display the interface information of the target interface after being triggered.

[0045] On the other hand, a computer device is provided, the computer device including a processor and a memory, the memory being used to store at least one computer program, the at least one computer program being loaded and executed by the processor to implement the interaction method between micro-applications in the embodiments of this application.

[0046] On the other hand, a computer-readable storage medium is provided that stores at least one computer program, which is loaded and executed by a processor to implement the interaction method between micro-applications as described in the embodiments of this application.

[0047] On the other hand, a computer program product is provided, which includes a computer program that, when executed by a processor, implements an interactive method for a micro-application provided in various alternative implementations of the above aspects.

[0048] This application provides an interaction method between micro-applications. By having the client of the target application provide a first application interface and a second application interface, the first micro-application can indirectly call the first business interface provided by the second micro-application through the first application interface. In turn, the second micro-application can indirectly return the processing result of the first business interface to the first micro-application through the second application interface. Thus, interaction between micro-applications with the client of the target application as the intermediary can be achieved without the need for specific application adaptation between micro-applications. Attached Figure Description

[0049] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0050] Figure 1 This is a schematic diagram of the implementation environment of an interaction method between micro-applications provided in an embodiment of this application;

[0051] Figure 2 This is a flowchart of an interaction method between micro-applications provided according to an embodiment of this application;

[0052] Figure 3 This is a flowchart of another interaction method between micro-applications provided according to an embodiment of this application;

[0053] Figure 4 This is an interaction flowchart between micro-applications provided according to an embodiment of this application;

[0054] Figure 5This is a flowchart of another interaction method between micro-applications provided according to an embodiment of this application;

[0055] Figure 6 This is a flowchart of another interaction method between micro-applications provided according to an embodiment of this application;

[0056] Figure 7 This is another flowchart of interaction between micro-applications provided according to an embodiment of this application;

[0057] Figure 8 This is a schematic diagram of an interface registration interface provided according to an embodiment of this application;

[0058] Figure 9 This is a schematic diagram of an interface display interface provided according to an embodiment of this application;

[0059] Figure 10 This is a block diagram of an interaction device between micro-applications according to an embodiment of this application;

[0060] Figure 11 This is a block diagram of an interaction device between micro-applications according to an embodiment of this application;

[0061] Figure 12 This is a block diagram of another micro-application interaction device provided according to an embodiment of this application;

[0062] Figure 13 This is a block diagram of another micro-application interaction device provided according to an embodiment of this application;

[0063] Figure 14 This is a structural block diagram of a terminal provided according to an embodiment of this application;

[0064] Figure 15 This is a schematic diagram of the structure of a server according to an embodiment of this application. Detailed Implementation

[0065] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0066] In this application, the terms "first," "second," etc., are used to distinguish identical or similar items with essentially the same function. It should be understood that there is no logical or temporal dependency between "first," "second," and "nth," nor are there any restrictions on quantity or execution order.

[0067] In this application, the term "at least one" means one or more, and "multiple" means two or more.

[0068] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the interface parameters and calling parameters involved in this application were obtained with full authorization.

[0069] The interaction method between micro-applications provided in this application can be executed by a computer device. In some embodiments, the computer device is a terminal or a server. The following section first uses a computer device as an example to describe the implementation environment of the interaction method between micro-applications provided in this application. Figure 1 This is a schematic diagram illustrating the implementation environment of a micro-application interaction method provided in an embodiment of this application. See also... Figure 1 The implementation environment includes terminal 101 and server 102.

[0070] Terminal 101 and server 102 can be connected directly or indirectly via wired or wireless communication, and this application does not impose any restrictions on this.

[0071] In some embodiments, terminal 101 may be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, smart voice interaction device, smart home appliance, vehicle terminal, or aircraft, but is not limited thereto. Terminal 101 has an application that supports micro-applications installed and running, and various different types of micro-applications can run on this application. Micro-applications may also be called embedded applications, such as applets or H5 (HTML 5, Hypertext 5) programs.

[0072] In some embodiments, server 102 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Server 102 is used to provide background services for applications supporting virtual scenarios. In some embodiments, server 102 undertakes the main computing work, and terminal 101 undertakes the secondary computing work; or, server 102 undertakes the secondary computing work, and terminal 101 undertakes the main computing work; or, server 102 and terminal 101 collaborate on computing using a distributed computing architecture.

[0073] Those skilled in the art will understand that the number of terminals described above can be more or less. For example, there may be only one terminal, or there may be dozens or hundreds of terminals, or even more. This application does not limit the number of terminals or the type of device.

[0074] Interactions between micro-applications fall into two categories: one is implemented based on the target application's client, and the other is implemented based on the target application's backend server. We will first introduce the solution for inter-micro-application interaction based on the target application's client.

[0075] Figure 2 This is a flowchart illustrating an interaction method between micro-applications according to an embodiment of this application, such as... Figure 2 As shown in the illustration, this application embodiment uses execution by a terminal as an example. The method includes the following steps:

[0076] 201. In response to receiving a call instruction from the first micro-application to the first application interface through the client of the target application, the terminal obtains the first interface parameters. The first application interface is provided by the client. The first interface parameters are the parameters required to call the first application interface. The first interface parameters include the interface identifier of the first business interface and the call parameters of the first business interface. The first micro-application runs on the basis of the target application.

[0077] In this embodiment, a client application for the target application is installed and running on the terminal. The target application can be a social application, an office application, or a communication application, etc., and this embodiment does not impose any restrictions. The target application is associated with multiple micro-applications, which run dependent on the target application.

[0078] For any given micro-application, it can indirectly call the business interfaces provided by other micro-applications by calling the application interfaces provided by the client of the target application. For ease of description, in this embodiment, the micro-application that calls the business interfaces is referred to as the first micro-application, and the application whose business interfaces are called is referred to as the second micro-application.

[0079] The first micro-application can send a call instruction to the client of the target micro-application to request the invocation of the aforementioned first service interface. In response to the call instruction, the terminal can obtain the first interface parameters through the client of the target application. The first interface parameters can be carried by the call instruction or provided by the first micro-application in other ways, and this application embodiment does not impose any restrictions on this.

[0080] 202. Based on the interface identifier, the terminal starts the second micro-application in the client and sends the interface identifier and call parameters to the second micro-application. The second micro-application is used to provide the first business interface and runs on the basis of the target application.

[0081] In this embodiment, after obtaining the first interface parameters, the terminal can determine the micro-application used to provide the first service interface based on the interface identifier, which is referred to as the second micro-application for ease of description. Then, the terminal launches the second micro-application in the client of the target application, that is, displays the relevant interface of the second micro-application. The interface identifier and calling parameters in the first interface parameters are sent to the second micro-application, which then calls the first service interface indicated by the interface identifier.

[0082] 203. In response to receiving a call instruction from the second micro-application to the second application interface through the client, the terminal returns the second interface parameters to the first micro-application. The second application interface is provided by the client, and the second interface parameters are the parameters required to call the second application interface. The second interface parameters include the processing result obtained from calling the first business interface.

[0083] In this embodiment, after the second micro-application calls the first business interface, it can obtain a processing result, which can be a numerical value or a string. The second micro-application can send a call instruction to the client of the target micro-application to return the aforementioned processing result to the first micro-application. In response to the call instruction, the terminal can obtain the second interface parameters through the client of the target application. The second interface parameters can be carried by the call instruction or provided by the second micro-application in other ways; this embodiment does not impose any restrictions on this.

[0084] This application provides an interaction method between micro-applications. By having the client of the target application provide a first application interface and a second application interface, the first micro-application can indirectly call the first business interface provided by the second micro-application through the first application interface. In turn, the second micro-application can indirectly return the processing result of the first business interface to the first micro-application through the second application interface. Thus, interaction between micro-applications with the client of the target application as the intermediary can be achieved without the need for specific application adaptation between micro-applications.

[0085] Figure 2 The main flow of the interaction method between micro-applications provided in the embodiments of this application is illustrated by way of example. The method will be further described below. Figure 3 This is a flowchart of another interaction method between micro-applications provided according to an embodiment of this application, such as... Figure 3 As shown in the illustration, this application embodiment uses execution by a terminal as an example. The method includes the following steps:

[0086] 301. The terminal displays a first interface through the client of the target application. The first interface displays a first control. The first interface is provided by a first micro-application, which runs on the basis of the target application.

[0087] In this embodiment, the terminal and target application refer to step 201 above, and will not be repeated here. The first micro-application is any micro-application that runs on the target application. Multiple micro-applications that rely on the target application can interact with each other through the target application, such as calling the interface provided by the micro-application or sending information to the micro-application. For ease of description, the micro-application that requests to call the interface is referred to as the first micro-application. The terminal can display the first interface provided by the first micro-application through the client of the target application. The first interface can be displayed in a nested form in any interface of the client, or the client can directly display the first interface. The first control is used to generate a call instruction for the first application interface after triggering, as described in step 302 below.

[0088] 302. In response to the triggering operation of the first control, the terminal generates a call instruction for the first application interface based on the content entered in the first interface through the first micro-application. The first application interface is provided by the client.

[0089] In this embodiment, the first interface is used to input parameters required to call the first application interface, such as the interface identifier and call parameters of the business interface. When the first control is triggered, the first micro-application can generate a call instruction for the first application interface. The call instruction may include the content input in the first interface, thereby obtaining the interface parameters of the first application interface through the call instruction; alternatively, it may not include the content input in the first interface, thereby instructing the client to obtain the interface parameters of the first application interface.

[0090] For example, taking the first micro-application as an office application, the first interface is used to fill out reports within the office application. Since the report processing requires calling calculation functions, even if the first micro-application does not provide such functions, the interface identifier of the calculation function entered in the report interface and the data to be calculated are used as the call parameters to generate the call instruction for the first application interface. This instruction is then used by the client of the target application to call the calculation functions provided by other micro-applications.

[0091] 303. In response to receiving a call instruction from the first micro-application to the first application interface through the client of the target application, the terminal obtains the first interface parameters through the client. The first application interface is provided by the client. The first interface parameters are the parameters required to call the first application interface. The first interface parameters include the interface identifier of the first business interface and the call parameters of the first business interface.

[0092] In this embodiment, the first micro-application can send a call instruction to the first application interface to the client of the target application. After receiving the call instruction, the client can obtain the first interface parameters. The first interface parameters can be obtained by parsing the call instruction or obtained from the first micro-application; this embodiment does not impose any restrictions on this.

[0093] 304. Based on the interface identifier, the terminal starts the second micro-application in the client of the target application, and sends the interface identifier and calling parameters to the second micro-application. The second micro-application is used to provide the first business interface and runs on the basis of the target application.

[0094] In this embodiment, the first business interface to be called can be determined based on the interface identifier. If only one micro-application provides the first business interface, the client identifies that micro-application as the second application; if multiple micro-applications provide the first business interface, the client can select one from among them as the second micro-application. The client can select the second micro-application from among multiple micro-applications in four ways.

[0095] In the first approach, the aforementioned first interface parameter also includes an application identifier for the second micro-application. This application identifier allows the second micro-application to be identified from multiple micro-applications. Correspondingly, the terminal, based on the interface identifier, obtains at least one third micro-application providing the first business interface from among the multiple micro-applications. These multiple micro-applications run on top of the target application. Then, based on the application identifier, the terminal identifies the second micro-application from among the at least one third micro-application. Finally, the terminal launches the second micro-application on the client side. There can be an association between the interface identifier and the micro-applications. This association allows for the rapid identification of the at least one third micro-application based on the interface identifier, without traversing all the micro-applications. By performing preliminary filtering based on the interface identifier, the efficiency of identifying the second micro-application is improved by eliminating the need to traverse all micro-applications when identifying it based on the application identifier. Of course, the terminal can also directly identify the second micro-application from among the multiple micro-applications using the application identifier.

[0096] In the second approach, the client login account has an account level, and the business interface has an interface level. The interface level restricts the account level required to call the business interface. Accordingly, the terminal determines the interface level of the first business interface based on the interface identifier. If the interface level is greater than the account level of the client's logged-in account, it means that the account cannot call the first business interface, and the terminal can display a first prompt message on the client, indicating that the account lacks permission to call the first business interface. If the interface level is not greater than the account level of the client's logged-in account, the terminal can launch a second micro-application in the client. This second micro-application can be determined using the first approach described above, randomly selected from the micro-applications providing the first business interface, or determined according to the priority of the micro-applications; this embodiment does not impose any restrictions on this. By setting account and interface levels, business interfaces require specific permissions to call, preventing arbitrary calls to business interfaces and conserving interface resources.

[0097] The third approach allows users to choose which micro-application provides the first service interface; the micro-application selected by the user becomes the second micro-application. Correspondingly, the terminal displays at least one candidate micro-application through the client based on the interface identifier. This candidate micro-application provides the first service interface. The terminal then launches the selected second micro-application from the at least one candidate micro-application in the client. By providing at least one candidate micro-application for user selection, users can choose which second micro-application to use to provide the service according to their preferences, thus improving the flexibility of interaction between micro-applications.

[0098] The fourth method involves the terminal determining the second micro-application based on the client's logged-in account's historical call history. Accordingly, the terminal retrieves at least one third micro-application providing the first business interface from multiple micro-applications based on an interface identifier; these micro-applications run on top of the target application. Then, based on the client's logged-in account's historical call behavior, the terminal determines the second micro-application from at least one third micro-application. Finally, the second micro-application is launched on the client. By determining the second micro-application based on historical call behavior, this method makes the second micro-application more aligned with user habits and expectations.

[0099] 305. The terminal displays a second interface through the client. The second interface displays a second control. The second interface is obtained by the second micro-application calling the first business interface based on the call parameters.

[0100] In this embodiment, the terminal calls the first service interface provided by the second micro-application through the second micro-application. At this time, the terminal can display a second interface provided by the second micro-application through the client. The second interface can display content related to the call parameters and a second control. The second control is used to generate a call instruction for the second application interface after triggering, as shown in step 306 below.

[0101] 306. In response to the triggering operation of the second control, the terminal generates a call instruction for the second application interface based on the content entered in the second interface through the second micro-application.

[0102] In this embodiment, the second interface is used for inputting content. This content can be parameters required during the invocation of the first business interface; it can also be parameters required when returning the processing result of the first business interface after invoking it; or it can be parameters required for invoking the second application interface. This embodiment does not impose any restrictions on this. Based on the content input on the second interface, the second application can generate an invocation instruction for the second application interface.

[0103] For example, taking the input on the second interface as the parameters required during the call to the first business interface, where the first business interface is a calculation interface, the second interface displays the data passed in when calling this calculation interface, i.e., the data to be calculated. Through this second interface, the functions required for the calculation can be set, such as a summation function or a square function.

[0104] For example, taking the input on the second interface as the parameter required to return the processing result of the first business interface, the first business interface is a calculation interface, and the processing result of the first business interface is multiple calculation results. The second interface displays options for processing these multiple calculation results, such as sorting, rounding, or filtering. At least one calculation result obtained after processing is used as the above processing result.

[0105] 307. In response to receiving a call instruction from the second micro-application to the second application interface through the client, the terminal returns the second interface parameters to the first micro-application. The second application interface is provided by the client, and the second interface parameters are the parameters required to call the second application interface. The second interface parameters include the processing result obtained from calling the first business interface.

[0106] In this embodiment, the way the second micro-application calls the second application interface is similar to the way the first micro-application calls the first application interface. This step is the same as step 203 described above and will not be repeated here.

[0107] It should be noted that, for a more intuitive description of the interaction method between micro-applications provided in the embodiments of this application, please refer to... Figure 4 As shown, Figure 4This is a flowchart illustrating the interaction between micro-applications according to an embodiment of this application, demonstrating the interaction between a first micro-application, a second micro-application, and a client of a target application. Figure 4 The process includes the following steps: 401. The first micro-application calls the first application interface, passing the application identifier of the second micro-application, the interface identifier of the first business interface, and the call parameters of the first business interface to the client of the target application. 402. The client of the target application starts the second micro-application and passes the interface identifier and call parameters to the second micro-application. 403. The client of the target application displays the interface of the second micro-application, at which time the user can operate on this interface to use the second micro-application. 404. The second micro-application calls the second application interface, returning the application identifier of the first micro-application and the processing result of the first business interface to the client of the target application. 405. The client of the target application closes the second micro-application and returns the processing result to the first micro-application for display.

[0108] It should be noted that the embodiments of this application use the interaction between the first micro-application and the second micro-application as an example for illustration. In some embodiments, the second micro-application can also be abstracted as a code library, which the first micro-application can integrate to directly call the code in the code library. The embodiments of this application do not limit the specific implementation method.

[0109] This application provides an interaction method between micro-applications. By having the client of the target application provide a first application interface and a second application interface, the first micro-application can indirectly call the first business interface provided by the second micro-application through the first application interface. In turn, the second micro-application can indirectly return the processing result of the first business interface to the first micro-application through the second application interface. Thus, interaction between micro-applications with the client of the target application as the intermediary can be achieved without the need for specific application adaptation between micro-applications.

[0110] The following section introduces a solution for enabling interaction between micro-applications based on the target application's backend server.

[0111] Figure 5 This is a flowchart of another interaction method between micro-applications provided according to an embodiment of this application. For example... Figure 5 As shown in the embodiment of this application, the method is illustrated using an example executed by a target server, which provides background services for the target application. The method includes the following steps:

[0112] 501. In response to the first server's call instruction to the first service interface, the target server obtains the third interface parameters. The first server is used to provide background services for the first micro-application. The first service interface is provided by the target server. The third interface parameters are the parameters required to call the first service interface. The third interface parameters include the interface identifier of the second business interface and the call parameters of the second business interface. The first micro-application runs on the basis of the target application.

[0113] In this embodiment of the application, the target application is associated with multiple micro-applications, which run on the basis of the target application.

[0114] For any given micro-application, it can indirectly call the business interfaces provided by the backend servers of other micro-applications by calling the service interfaces provided by the target server through the backend server. For ease of description, in this embodiment, the backend server that calls the business interface is referred to as the first server, and the application whose business interface is called is referred to as the second server. Specifically, the first server is the backend server of the first micro-application, and the second server is the backend server of the second micro-application.

[0115] The first server can send a call instruction to the target server for the first service interface to request the invocation of the second service interface provided by the second server. In response to the call instruction, the target server can obtain third interface parameters, which can be carried in the call instruction or provided by the first server in other ways; this embodiment of the application does not impose any restrictions on this.

[0116] 502. In response to the inclusion of the first account identifier in the first micro-application in the call parameters, the target server converts the first account identifier into the second account identifier in the second micro-application. All second micro-applications rely on the target application to run.

[0117] In this embodiment, the account identifier of the same user is different in different micro-applications, and all are provided by the target server. The target server can then convert the first account identifier in the first micro-application into a second account identifier in the second micro-application. The target server can then send the converted call parameters and the interface identifier of the second business interface to the second server, which will then call the second business interface based on the call parameters and the second account identifier.

[0118] 503. Send the fourth interface parameters returned by the second server through the second service interface to the first server. The target server displays the processing results included in the fourth interface parameters through the first micro-application. The second service interface is provided by the target server. The second server is used to provide background services for the second micro-application. The processing results are obtained by the second server calling the second business interface based on the call parameters and the second account identifier.

[0119] In this embodiment, after the second server invokes the second service interface based on the invocation parameters and the second account identifier, it can obtain a processing result, which can be a numerical value or a string. The second server can send an invocation instruction for the second service interface to the target server to return the aforementioned processing result to the first server. In response to the second server's invocation instruction for the second service interface, the target server can obtain a fourth interface parameter. This fourth interface parameter can be carried in the invocation instruction or provided by the second server in other ways; this embodiment does not impose any restrictions on this.

[0120] This application provides an interaction method between micro-applications. By having a target server provide a first service interface and a second service interface, the backend server of the first micro-application can indirectly call the second business interface provided by the backend server of the second micro-application through the first service interface. In turn, the backend server of the second micro-application can indirectly return the processing result of the second business interface to the backend server of the first micro-application through the second service interface. Thus, backend interaction between micro-applications with the target server as the intermediary can be achieved without the need for specific application adaptation between micro-applications.

[0121] Figure 5 The main flow of the interaction method between micro-applications provided in the embodiments of this application is illustrated by way of example. The method will be further described below. Figure 6 This is a flowchart of another interaction method between micro-applications provided according to an embodiment of this application, such as... Figure 6 As shown in the illustration, this application embodiment uses execution by the target server as an example. The method includes the following steps:

[0122] 601. In response to the first server's call instruction to the first service interface, the target server obtains the third interface parameters. The first server is used to provide background services for the first micro-application. The first service interface is provided by the target server. The third interface parameters are the parameters required to call the first service interface. The third interface parameters include the interface identifier of the second business interface and the call parameters of the second business interface. The first micro-application runs on the basis of the target application.

[0123] This step is the same as step 501 above, and will not be repeated here.

[0124] 602. In response to the call parameters including the first account identifier in the first micro-application, the target server converts the first account identifier into the second account identifier in the second micro-application, and the second micro-application runs on the basis of the target application.

[0125] In this embodiment, the second account identifier can be obtained by the target server by parsing the first account tag, or it can be obtained by the target server from the device where the target application is located. See the following two acquisition methods.

[0126] In the first acquisition method, the first and second account identifiers are obtained from the target account of the target application using different encryption methods. The target account is the login account of the target application, and the third interface parameter also includes the server identifier of the second server. Accordingly, in response to the first account identifier from the first micro-application included in the call parameters, the target server decrypts the first account identifier based on the encryption method corresponding to the first server to obtain the target account. Then, the target server determines the encryption method corresponding to the second server based on the server identifier of the second server. Finally, the target server encrypts the target account based on the encryption method corresponding to the second server to obtain the second account identifier. By using encryption and decryption to convert the first account identifier into the second account identifier, the first account identifier is less susceptible to tampering, thus ensuring the accuracy of the second account and improving the security of the interaction process.

[0127] Method 2: The call parameters also include a device identifier, which indicates the device on which the target application is installed. Correspondingly, in response to the inclusion of the first account identifier in the call parameters of the first micro-application, the target server retrieves the second account identifier from the device based on the device identifier. Then, the target server replaces the first account identifier in the call parameters with the second account identifier from the second micro-application. Since the call parameters include a device identifier, indicating that the first and second micro-applications are located on the same device, the first and second account identifiers are associated with the device identifier. Therefore, the target server can directly retrieve the second account identifier from the device, improving the efficiency of obtaining the second account identifier.

[0128] 603. The target server sends the interface identifier of the second business interface and the calling parameters of the second business interface to the second server.

[0129] In this embodiment, the target server can determine the second service interface based on the aforementioned interface identifier. If only one server provides the second service interface, the target server designates that server as the second server. If multiple servers provide the second service interface, the target server can select one of them as the second server. The methods by which the target server selects the second server from multiple servers include the following three:

[0130] In the first approach, the third interface parameter also includes the server identifier of the second server, which allows the second server to be identified from multiple servers. Accordingly, the target server, based on the interface identifier, obtains at least one third server providing the second business interface from among the multiple servers. Then, the target server, based on the application identifier, identifies the second server from among the at least one third server. Finally, the target server starts the second server. A relationship can exist between the interface identifier and the server; this relationship allows for quick identification of the at least one third server based on the interface identifier, without traversing all servers. By initially filtering multiple servers based on the interface identifier, the efficiency of identifying the second server is improved by eliminating the need to traverse all servers when determining the second server based on the server identifier. Of course, the target server can also directly identify the second server from among the multiple servers using the server identifier.

[0131] In the second approach, the target application's login account has an account level, and the business interface has an interface level. This interface level restricts the account level required to call the business interface. Accordingly, the target server determines the interface level of the first business interface based on the interface identifier. If the interface level is greater than the account level of the target application's login account, it indicates that the account cannot call the second business interface, and the target server returns a second prompt message to the target application, indicating that the account lacks permission to call the second business interface. If the interface level is not greater than the account level of the target application's login account, the target server can send the interface identifier of the second business interface and the calling parameters of the second business interface to the second server. The second server can be determined using the first approach described above, randomly selected from the servers providing the second business interface, or determined according to server priority; this embodiment does not impose any restrictions on this. By setting account and interface levels, business interfaces require specific permissions to call, preventing arbitrary calls and conserving interface resources.

[0132] 604. In response to receiving the call instruction from the second server to the second service interface, the target server obtains the fourth interface parameters. The second service interface is provided by the target server. The second server is used to provide background services for the second micro-application. The processing result is obtained by the second server calling the second business interface based on the call parameters and the second account identifier.

[0133] In this embodiment, after the second server invokes the second business interface based on the invocation parameters and the second account identifier, it can obtain the processing result. The second server then returns the processing result to the first server by invoking the second service interface.

[0134] 605. The target server sends the fourth interface parameter to the first server, and the first micro-application displays the processing result included in the fourth interface parameter.

[0135] It should be noted that, for a more intuitive description of the interaction method between micro-applications provided in the embodiments of this application, please refer to... Figure 7 As shown, Figure 7 This is another micro-application interaction flowchart provided according to an embodiment of this application, exemplarily illustrating the interaction between a first server, a second server, and a target server. For example... Figure 7 The process includes the following steps: 701. The first server calls the first service interface, passing the interface identifier of the second business interface and the call parameters of the second business interface to the target server. 702. The target server converts the first account identifier in the call parameters into the second account identifier. 703. The target server passes the interface identifier of the second business interface and the call parameters of the second business interface to the second server. 704. The second server calls the second business interface based on the call parameters and obtains the processing result. 705. The second server calls the second server interface and returns the processing result to the target server. 706. The target server returns the processing result to the first server.

[0136] It should be noted that service providers with interface capabilities can log in to the service provider assistant program via the terminal to register interface information. After registration, the business interfaces can be invoked using the solution provided in this application.

[0137] In some embodiments, in response to receiving an interface registration request sent via a terminal, the target server can return an interface registration interface to the terminal, which is used to input information about the target interface of the micro-application. Then, the target server receives the interface information of the target interface sent by the terminal, including the name of the target interface and the format of its calling parameters. Finally, the target server displays the information entry point of the target interface on an interface display interface, which is used to display the interface information of the target interface upon triggering. By providing an interface registration function, the interface resources of service providers are effectively integrated, and the registered interface resources are displayed, improving the efficiency of interface usage.

[0138] For example, see Figure 8 As shown, Figure 8 This is a schematic diagram of an interface registration interface provided according to an embodiment of this application. For example... Figure 8 As shown in (a), the interface registration interface is used to register information such as interface identifier, interface name, interface description, and calling parameters. Figure 8Example (b) illustrates the area in the interface registration interface used to set call parameters, including request parameters and return parameters. Optionally, after interface registration is complete, the server may also provide documentation describing the business interface to introduce its capabilities and facilitate its invocation. See also Figure 8 As shown in (c) in the figure. Figure 9 This is a schematic diagram of an interface display interface provided according to an embodiment of this application. See also... Figure 9 As shown, an example is illustrated with information entry points for multiple business interfaces.

[0139] Figure 10 This is a block diagram of an interaction device between micro-applications according to an embodiment of this application. The device is used to perform the steps in the above-described interaction method between micro-applications. See also... Figure 10 The device includes: a parameter acquisition module 1001, a sending module 1002, and a parameter return module 1003.

[0140] The parameter acquisition module 1001 is used to respond to the call instruction from the first micro-application to the first application interface received by the client of the target application, and to acquire the first interface parameters. The first application interface is provided by the client, and the first interface parameters are the parameters required to call the first application interface. The first interface parameters include the interface identifier of the first business interface and the call parameters of the first business interface. The first micro-application runs on the target application.

[0141] The sending module 1002 is used to launch a second micro-application in the client based on the interface identifier, and send the interface identifier and calling parameters to the second micro-application. The second micro-application is used to provide the first business interface and runs on the basis of the target application.

[0142] The parameter return module 1003 is used to respond to the call instruction from the second micro-application to the second application interface received from the client, and return the second interface parameters to the first micro-application. The second application interface is provided by the client, and the second interface parameters are the parameters required to call the second application interface. The second interface parameters include the processing result obtained from calling the first business interface.

[0143] In some embodiments, the call instruction of the first application interface is triggered based on the first interface, which is provided by the first micro-application;

[0144] Figure 11 This is a block diagram of an interaction device between micro-applications according to an embodiment of this application. See also... Figure 11 As shown, the device also includes:

[0145] The first display module 1101 is used to display a first interface through a client, and the first interface displays a first control.

[0146] The first generation module 1102 is used to respond to the trigger operation of the first control and generate a call instruction for the first application interface based on the content entered in the first interface through the first micro-application.

[0147] In some embodiments, the call instruction for the second application interface is triggered based on the second interface, which is obtained by the second micro-application calling the first business interface based on the call parameters;

[0148] See Figure 11 As shown, the device also includes:

[0149] The second display module 1103 is used to display a second interface through the client, and the second interface displays a second control.

[0150] The second generation module 1104 is used to respond to the trigger operation of the second control and generate a call instruction for the second application interface based on the content entered in the second interface through the second micro-application.

[0151] In some embodiments, the first interface parameter further includes the application identifier of the second micro-application;

[0152] The sending module 1002 is used to obtain at least one third micro-application that provides the first business interface from multiple micro-applications based on the interface identifier, wherein the multiple micro-applications run on the target application; determine a second micro-application from at least one third micro-application based on the application identifier; and start the second micro-application in the client.

[0153] In some embodiments, the sending module 1002 is configured to determine the interface level of the first service interface based on the interface identifier; in response to the interface level being greater than the account level of the client's logged-in account, display a first prompt message on the client, the first prompt message being used to indicate that there is no permission to call the first service interface; in response to the interface level not being greater than the account level of the client's logged-in account, launch a second micro-application in the client.

[0154] In some embodiments, the sending module 1002 is configured to display at least one candidate micro-application through a client based on an interface identifier, the candidate micro-application being used to provide a first service interface; and to launch a second micro-application selected from at least one candidate micro-application in the client.

[0155] In some embodiments, the sending module 1002 is configured to obtain at least one third micro-application that provides a first business interface from multiple micro-applications based on an interface identifier, wherein the multiple micro-applications run on the target application; determine a second micro-application from the at least one third micro-application based on the historical call behavior of the account logged in by the client; and start the second micro-application in the client.

[0156] This application provides an interaction method between micro-applications. By having the client of the target application provide a first application interface and a second application interface, the first micro-application can indirectly call the first business interface provided by the second micro-application through the first application interface. In turn, the second micro-application can indirectly return the processing result of the first business interface to the first micro-application through the second application interface. Thus, interaction between micro-applications with the client of the target application as the intermediary can be achieved without the need for specific application adaptation between micro-applications.

[0157] Figure 12 This is a block diagram of another micro-application interaction device provided according to an embodiment of this application. This device is used to perform the steps in the above-described micro-application interaction method, see [link to relevant documentation]. Figure 12 The device is deployed in the target server, which is used to provide background services for the target application. The device includes: a parameter acquisition module 1201, an account identifier conversion module 1202, and a parameter return module 1203.

[0158] The parameter acquisition module 1201 is used to respond to the call instruction of the first server to the first service interface and acquire the third interface parameters. The first server is used to provide background services for the first micro-application. The first service interface is provided by the target server. The third interface parameters are the parameters required to call the first service interface. The third interface parameters include the interface identifier of the second business interface and the call parameters of the second business interface. The first micro-application runs on the basis of the target application.

[0159] The account identifier conversion module 1202 is used to convert the first account identifier in the first micro-application into the second account identifier in the second micro-application in response to the call parameters including the first account identifier in the first micro-application. The second micro-applications all rely on the target application to run.

[0160] The parameter return module 1203 is used to send the fourth interface parameters returned by the second server through the second service interface to the first server. The first micro-application displays the processing results included in the fourth interface parameters. The second service interface is provided by the target server. The second server is used to provide background services for the second micro-application. The processing results are obtained by the second server calling the second business interface based on the call parameters and the second account identifier.

[0161] In some embodiments, the first account identifier and the second account identifier are obtained by using different encryption methods from the target account of the target application, and the third interface parameter also includes the server identifier of the second server, and the target account is the account logged in by the target application;

[0162] The account identifier conversion module 1202 is used to respond to the call parameters including the first account identifier in the first micro-application, decrypt the first account identifier based on the encryption method corresponding to the first server to obtain the target account; determine the encryption method corresponding to the second server based on the server identifier of the second server; and encrypt the target account based on the encryption method corresponding to the second server to obtain the second account identifier.

[0163] In some embodiments, the calling parameters also include a device identifier, which is used to indicate the device on which the target application is installed;

[0164] The account identifier conversion module 1202 is used to respond to the call parameters including the first account identifier in the first micro-application, obtain the second account identifier from the device based on the device identifier, and replace the first account identifier in the call parameters with the second account identifier in the second micro-application.

[0165] In some embodiments, Figure 13 This is a block diagram of another micro-application interaction device provided according to an embodiment of this application. See also Figure 13 As shown, the device also includes:

[0166] The interface return module 1301 is used to respond to receiving an interface registration request sent through the terminal and return an interface registration interface to the terminal. The interface registration interface is used to input the information of the target interface of the micro-application.

[0167] The information receiving module 1302 is used to receive interface information of the target interface sent by the terminal. The interface information includes the name of the target interface and the form of the calling parameters of the target interface.

[0168] The entry display module 1303 is used to display the information entry of the target interface on the interface display interface. The information entry is used to display the interface information of the target interface after being triggered.

[0169] It should be noted that the interaction device between micro-applications provided in the above embodiments is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the interaction device between micro-applications and the interaction method embodiment provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiment, which will not be repeated here.

[0170] In the embodiments of this application, the computer device can be configured as a terminal or a server. When the computer device is configured as a terminal, the terminal can act as the execution subject to implement the technical solutions provided in the embodiments of this application. When the computer device is configured as a server, the server can act as the execution subject to implement the technical solutions provided in the embodiments of this application. Alternatively, the technical solutions provided in this application can be implemented through the interaction between the terminal and the server. The embodiments of this application do not limit this.

[0171] When a computer device is configured as a terminal, Figure 14 This is a structural block diagram of a terminal 1400 provided according to an embodiment of this application. The terminal 1400 can be a portable mobile terminal, such as a smartphone, tablet computer, MP3 player (Moving Picture Experts Group Audio Layer III), MP4 player (Moving Picture Experts Group Audio Layer IV), laptop computer, or desktop computer. The terminal 1400 may also be referred to as user equipment, portable terminal, laptop terminal, desktop terminal, or other names.

[0172] Typically, terminal 1400 includes a processor 1401 and a memory 1402.

[0173] Processor 1401 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1401 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1401 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1401 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the screen. In some embodiments, processor 1401 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0174] Memory 1402 may include one or more computer-readable storage media, which may be non-transitory. Memory 1402 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in memory 1402 are used to store at least one computer program, which is executed by processor 1401 to implement the interaction method between microapplications provided in the method embodiments of this application.

[0175] In some embodiments, the terminal 1400 may also optionally include a peripheral device interface 1403 and at least one peripheral device. The processor 1401, memory 1402, and peripheral device interface 1403 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1403 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency circuit 1404, a display screen 1405, a camera assembly 1406, an audio circuit 1407, and a power supply 1408.

[0176] Peripheral device interface 1403 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 1401 and memory 1402. In some embodiments, processor 1401, memory 1402 and peripheral device interface 1403 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 1401, memory 1402 and peripheral device interface 1403 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0177] The radio frequency (RF) circuit 1404 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 1404 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 1404 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. In some embodiments, the RF circuit 1404 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 1404 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 1404 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0178] Display screen 1405 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 1405 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 1401 for processing. In this case, display screen 1405 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one display screen 1405, disposed on the front panel of terminal 1400; in other embodiments, there may be at least two display screens, disposed on different surfaces of terminal 1400 or in a folded design; in still other embodiments, display screen 1405 may be a flexible display screen, disposed on a curved or folded surface of terminal 1400. Furthermore, display screen 1405 may be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. The display screen 1405 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0179] The camera assembly 1406 is used to acquire images or videos. In some embodiments, the camera assembly 1406 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 1406 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash is a combination of a warm-light flash and a cool-light flash, which can be used for light compensation at different color temperatures.

[0180] The audio circuit 1407 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting the sound waves into electrical signals that are input to the processor 1401 for processing, or input to the radio frequency circuit 1404 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each positioned at a different location on the terminal 1400. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 1401 or the radio frequency circuit 1404 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 1407 may also include a headphone jack.

[0181] Power supply 1408 is used to power the various components in terminal 1400. Power supply 1408 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 1408 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, and a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0182] Those skilled in the art will understand that Figure 14 The structure shown does not constitute a limitation on terminal 1400 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0183] When a computer device is configured as a server, Figure 15This is a schematic diagram of a server structure according to an embodiment of this application. The server 1500 can vary significantly due to different configurations or performance. It may include one or more Central Processing Units (CPUs) 1501 and one or more memories 1502. The memory 1502 stores at least one computer program, which is loaded and executed by the processor 1501 to implement the interaction methods between micro-applications provided in the various method embodiments described above. Of course, the server may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The server may also include other components for implementing device functions, which will not be elaborated here.

[0184] This application also provides a computer-readable storage medium storing at least one computer program. This computer program is loaded and executed by a processor of a computer device to implement the operations performed by the computer device in the micro-application interaction method described above. For example, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, or optical data storage device, etc.

[0185] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, causing the computer device to perform the micro-application interaction methods provided in the various optional implementations described above.

[0186] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0187] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for interaction between micro-applications, characterized in that, The method includes: In response to receiving a call instruction from the first micro-application to the first application interface through the client of the target application, the first interface parameters are obtained. The first application interface is provided by the client. The first interface parameters are the parameters required to call the first application interface. The first interface parameters include the interface identifier of the first business interface and the call parameters of the first business interface. The first micro-application runs on the target application. The first interface parameters also include the application identifier of the second micro-application. Based on the interface identifier, at least one third micro-application providing the first business interface is obtained from multiple micro-applications, and the multiple micro-applications run on the target application; based on the application identifier, a second micro-application is determined from the at least one third micro-application, the second micro-application is started in the client, and the interface identifier and the calling parameters are sent to the second micro-application, the second micro-application is used to provide the first business interface, and the second micro-application runs on the target application; In response to receiving a call instruction from the second micro-application to the second application interface through the client, the second interface parameters are returned to the first micro-application. The second application interface is provided by the client, and the second interface parameters are the parameters required to call the second application interface, including the processing result obtained from calling the first business interface.

2. The method of claim 1, wherein, The call instruction of the first application interface is triggered based on the first interface, which is provided by the first micro-application; The method further includes: The first interface is displayed through the client, and the first interface displays a first control. In response to the triggering operation of the first control, the first micro-application generates a call instruction for the first application interface based on the content entered in the first interface.

3. The method of claim 1, wherein, The call instruction for the second application interface is triggered based on the second interface, which is obtained by the second micro-application calling the first business interface based on the call parameters; After launching the second micro-application in the client and sending the interface identifier and the calling parameters to the second micro-application, the method further includes: The second interface is displayed through the client, and the second interface displays the second control. In response to the triggering operation of the second control, the second micro-application generates a call instruction for the second application interface based on the content entered in the second interface.

4. The method of claim 1, wherein, The method further includes: Based on the interface identifier, determine the interface level of the first service interface; In response to the interface level being greater than the account level of the client's logged-in account, a first prompt message is displayed on the client, the first prompt message indicating that there is no permission to call the first business interface; In response to the interface level being no higher than the account level of the client's logged-in account, the second micro-application is launched in the client.

5. The method of claim 1, wherein, The method further includes: Based on the interface identifier, at least one candidate micro-application is displayed through the client, and the candidate micro-application is used to provide the first service interface; The second micro-application selected from the at least one candidate micro-applications is launched in the client.

6. The method of claim 1, wherein, The method further includes: Based on the interface identifier, at least one third micro-application that provides the first business interface is obtained from multiple micro-applications, and the multiple micro-applications run on the target application; Based on the historical call behavior of the account logged in by the client, the second micro-application is determined from the at least one third micro-application; Launch the second micro-application in the client.

7. An interaction method between micro-applications, characterized in that, It is applied to a target server, which is used to provide background services for a target application; The method includes: In response to the first server's call instruction to the first service interface, the third interface parameters are obtained. The first server is used to provide background services for the first micro-application. The first service interface is provided by the target server. The third interface parameters are the parameters required to call the first service interface. The third interface parameters include the interface identifier of the second business interface and the call parameters of the second business interface. The first micro-application runs on the basis of the target application. In response to the inclusion of a first account identifier in the first micro-application in the call parameters, the first account identifier is converted into a second account identifier in the second micro-application, and both of the second micro-applications rely on the target application to run; The first micro-application sends the fourth interface parameters returned by the second server through the second service interface to the first server. The first micro-application displays the processing results included in the fourth interface parameters. The second service interface is provided by the target server. The second server is used to provide background services for the second micro-application. The processing results are obtained by the second server calling the second business interface based on the call parameters and the second account identifier. In response to receiving an interface registration request sent through a terminal, an interface registration interface is returned to the terminal, the interface registration interface being used to input information about the target interface of the micro-application; The terminal sends interface information of the target interface, the interface information including the name of the target interface and the form of the calling parameters of the target interface; The interface display interface shows the information entry point of the target interface, which is used to display the interface information of the target interface after being triggered.

8. The method of claim 7, wherein, The first account identifier and the second account identifier are obtained by using different encryption methods from the target account of the target application. The third interface parameter also includes the server identifier of the second server. The target account is the account logged in by the target application. The response that the call parameters include a first account identifier in the first micro-application, converting the first account identifier into a second account identifier in the second micro-application, includes: In response to the fact that the call parameters include a first account identifier in the first micro-application, the first account identifier is decrypted based on the encryption method corresponding to the first server to obtain the target account; Based on the server identifier of the second server, determine the encryption method corresponding to the second server; Based on the encryption method corresponding to the second server, the target account is encrypted to obtain the second account identifier.

9. The method of claim 7, wherein, The call parameters also include a device identifier, which is used to indicate the device on which the target application is installed; The response that the call parameters include a first account identifier in the first micro-application, converting the first account identifier into a second account identifier in the second micro-application, includes: In response to the inclusion of a first account identifier in the first micro-application in the call parameters, the second account identifier is obtained from the device based on the device identifier; Replace the first account identifier in the call parameters with the second account identifier in the second micro-application.

10. An apparatus for interaction between micro-applications, characterized in that, The device includes: The parameter acquisition module is used to respond to receiving a call instruction from the first micro-application to the first application interface through the client of the target application, and to acquire the first interface parameters. The first application interface is provided by the client. The first interface parameters are the parameters required to call the first application interface. The first interface parameters include the interface identifier of the first business interface and the call parameters of the first business interface. The first micro-application runs on the target application. The first interface parameters also include the application identifier of the second micro-application. The sending module is configured to, based on the interface identifier, obtain at least one third micro-application that provides the first service interface from multiple micro-applications, wherein the multiple micro-applications run in relation to the target application; based on the application identifier, determine the second micro-application from the at least one third micro-application, start the second micro-application in the client, and send the interface identifier and the calling parameters to the second micro-application, wherein the second micro-application is used to provide the first service interface and runs in relation to the target application; The parameter return module is used to respond to the client receiving a call instruction from the second micro-application to the second application interface, and to return the second interface parameters to the first micro-application. The second application interface is provided by the client, and the second interface parameters are the parameters required to call the second application interface, including the processing result obtained from calling the first business interface.

11. The apparatus according to claim 10, characterized in that, The call instruction of the first application interface is triggered based on the first interface, which is provided by the first micro-application; The device further includes: A first display module is used to display the first interface through the client, wherein the first interface displays a first control; The first generation module is used to respond to the trigger operation of the first control and generate a call instruction for the first application interface based on the content entered in the first interface through the first micro-application.

12. The apparatus according to claim 10, characterized in that, The call instruction for the second application interface is triggered based on the second interface, which is obtained by the second micro-application calling the first business interface based on the call parameters; The device further includes: The second display module is used to display the second interface through the client, and the second interface displays the second control. The second generation module is used to respond to the trigger operation of the second control and generate a call instruction for the second application interface based on the content entered in the second interface through the second micro-application.

13. The apparatus of claim 10, wherein, The sending module is further configured to: Based on the interface identifier, determine the interface level of the first service interface; In response to the interface level being greater than the account level of the client's logged-in account, a first prompt message is displayed on the client, the first prompt message indicating that there is no permission to call the first business interface; In response to the interface level not being greater than the account level of the client's logged-in account, the second micro-application is launched in the client.

14. The apparatus of claim 10, wherein, The sending module is further configured to: Based on the interface identifier, at least one candidate micro-application is displayed through the client, and the candidate micro-application is used to provide the first service interface; The second micro-application selected from the at least one candidate micro-applications is launched in the client.

15. The apparatus of claim 10, wherein, The sending module is further configured to: Based on the interface identifier, at least one third micro-application that provides the first business interface is obtained from multiple micro-applications, and the multiple micro-applications run on the target application; Based on the historical call behavior of the account logged in by the client, the second micro-application is determined from the at least one third micro-application; Launch the second micro-application in the client.

16. An apparatus for interaction between micro-applications, characterized in that, Deployed on the target server, which is used to provide background services for the target application; The device includes: The parameter acquisition module is used to respond to the call instruction of the first server to the first service interface and acquire the third interface parameters. The first server is used to provide background services for the first micro-application. The first service interface is provided by the target server. The third interface parameters are the parameters required to call the first service interface. The third interface parameters include the interface identifier of the second business interface and the call parameters of the second business interface. The first micro-application runs on the target application. The account identifier conversion module is used to convert the first account identifier in the first micro-application into a second account identifier in the second micro-application in response to the call parameters including the first account identifier in the first micro-application. Both of the second micro-applications rely on the target application to run. The parameter return module is used to send the fourth interface parameters returned by the second server through the second service interface to the first server. The first micro-application displays the processing results included in the fourth interface parameters. The second service interface is provided by the target server. The second server is used to provide background services for the second micro-application. The processing results are obtained by the second server calling the second business interface based on the call parameters and the second account identifier. The interface return module is used to respond to receiving an interface registration request sent through the terminal and return an interface registration interface to the terminal. The interface registration interface is used to input the information of the target interface of the micro-application. The information receiving module is used to receive interface information of the target interface sent by the terminal, wherein the interface information includes the name of the target interface and the form of the calling parameters of the target interface; The entry display module is used to display the information entry of the target interface on the interface display interface. The information entry is used to display the interface information of the target interface after being triggered.

17. The apparatus of claim 16, wherein, The first account identifier and the second account identifier are obtained by using different encryption methods from the target account of the target application. The third interface parameter also includes the server identifier of the second server. The target account is the account logged in by the target application. The account identifier conversion module is used for: In response to the fact that the call parameters include a first account identifier in the first micro-application, the first account identifier is decrypted based on the encryption method corresponding to the first server to obtain the target account; Based on the server identifier of the second server, determine the encryption method corresponding to the second server; Based on the encryption method corresponding to the second server, the target account is encrypted to obtain the second account identifier.

18. The apparatus of claim 16, wherein, The call parameters also include a device identifier, which is used to indicate the device on which the target application is installed; The account identifier conversion module is used for: In response to the inclusion of a first account identifier in the first micro-application in the call parameters, the second account identifier is obtained from the device based on the device identifier; Replace the first account identifier in the call parameters with the second account identifier in the second micro-application.

19. A computer device, comprising: The computer device includes a processor and a memory, the memory being used to store at least one computer program, the at least one computer program being loaded by the processor and executed as the interaction method between micro-applications according to any one of claims 1 to 6, or the at least one computer program being loaded by the processor and executed as the interaction method between micro-applications according to any one of claims 7 to 9.

20. A computer program product comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the interaction method between micro-applications as described in any one of claims 1 to 6, or when the computer program is executed by the processor, it implements the interaction method between micro-applications as described in any one of claims 7 to 9.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one computer program, which is loaded and executed by a processor to implement the interaction method between micro-applications as described in any one of claims 1 to 6, or to implement the interaction method between micro-applications as described in any one of claims 7 to 9.

Images