Method, device, medium and electronic device for controlling cross-application running of sub-applications

Abstract

The application provides a control method and device for running a sub-application across applications, a medium and an electronic device, and relates to the technical field of computers. In the process of running the applet across applications, the client of the first application displays a sub-application display interface in response to a trigger operation of opening the sub-application display interface by a target account, and the sub-application display interface displays identification information of the sub-application. In response to a start target sub-application operation triggered by the identification information of the target sub-application in the sub-application of the second application, the data of the target sub-application is obtained from the second application server, and the running interface of the target sub-application is displayed according to the data of the target sub-application. The method can enable the user to conveniently and quickly run the sub-application of the second application through the client of the first application, thereby improving the efficiency of running the sub-application across applications.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a control method, apparatus, medium, and electronic device for running sub-applications across applications. Background Technology

[0002] With the development of communication technology and the widespread adoption of smart terminals, sub-applications, as lightweight applications, have become an important form of mobile internet application. Sub-applications do not require downloading or installation; they run on top of applications installed on the terminal device. Users can use sub-applications to handle various business transactions, engage in entertainment, or social activities. Because sub-applications do not require downloading or installation and do not occupy the terminal device's storage space, they have gained widespread user acceptance.

[0003] To further increase the usability of sub-applications, there is a desire to be able to use them across different applications, that is, to use a sub-application of a second application within a first application. Currently, launching and running a sub-application of a second application within a first application requires a cumbersome process for the user, resulting in low efficiency for running sub-applications across applications. Summary of the Invention

[0004] To address the technical problems existing in related technologies, embodiments of this application provide a control method, apparatus, medium, and electronic device for running sub-applications across applications, which can improve the efficiency of running sub-applications across applications.

[0005] To achieve the above objectives, the technical solution of this application embodiment is implemented as follows:

[0006] In a first aspect, embodiments of this application provide a control method for running sub-applications across applications, applied to a client of a first application, the method comprising:

[0007] In response to a triggering operation that the target account opens the sub-application display interface, the sub-application display interface is displayed, and the sub-application display interface displays the identification information of the sub-application; the sub-application includes a sub-application of the second application; the identification information of the sub-application of the second application is obtained by the first application server associated with the first application from the second application server associated with the second application and sent to the client of the first application;

[0008] In response to a target sub-application launch operation triggered by the identification information of the target sub-application in a sub-application of the second application, data of the target sub-application is obtained from the second application server, and the running interface of the target sub-application is displayed based on the data of the target sub-application.

[0009] In one optional embodiment, the step of launching the target sub-application in response to the identification information of the target sub-application in a sub-application of the second application, obtaining data of the target sub-application from the second application server and displaying the running interface of the target sub-application based on the data of the target sub-application, includes:

[0010] In response to the operation of launching the target sub-application, a launch sub-application event is sent to the first application server;

[0011] If an interception notification is received from the first application server, the startup of the target sub-application is interrupted, and the information of the target sub-application being included in the list of faulty sub-applications is displayed.

[0012] If no interception notification is received from the first application server, the data of the target sub-application is obtained from the second application server, and the running interface of the target sub-application is displayed based on the data of the target sub-application.

[0013] Secondly, embodiments of this application provide a control method for running sub-applications across applications, applied to a first application server, the method comprising:

[0014] The system receives an information retrieval request sent by a target client, instructing the user to obtain the identification information of a sub-application of a second application; the target client is a client of the first application; the first application server is a server associated with the first application.

[0015] Based on the information acquisition request, the identification information of the sub-application of the second application is obtained from the second server; the second application server is the server associated with the second application;

[0016] Send the identification information of the sub-application of the second application to the target client so that the target client displays the identification information of the sub-application of the second application on the sub-application display interface.

[0017] In one optional embodiment, the information acquisition request is a sub-application search request; according to the information acquisition request, obtaining the identification information of the sub-application of the second application from the second server includes:

[0018] The sub-application search request is forwarded to the second application server; the sub-application search request contains key search information.

[0019] The system receives search result data returned by the second application server; the search result data is obtained by the second application server based on the search key information in the sub-application search request; the search result data includes at least one sub-application identification information;

[0020] Sending the identification information of the sub-application of the second application to the target client includes:

[0021] The search results data are sent to the target client.

[0022] In an optional embodiment, the search result data includes a number of sub-application identifiers and offset information limited by pagination control information; the pagination control information is used to limit the maximum number of sub-application identifiers included in the search result data returned by the second application server each time; the offset information is the position identifier of the first sub-application identifier included in the search result corresponding to the search key information but not included in the search result data; the search result corresponding to the search key information is the search result obtained by the first application server based on the search key information; the information acquisition request is a supplementary search result request; after sending the sub-application identifiers of the second application to the target client, the method further includes:

[0023] The supplementary search result request received from the target client is sent to the second application server; the supplementary search result request includes the search key information and the offset information;

[0024] Supplementary search data is returned to the target client so that the target client displays the identification information of the sub-application of the second application in the supplementary search data on the sub-application display interface; the supplementary search data is obtained by the second application server from the search results corresponding to the search key information based on the offset information and sent to the first application server after receiving the supplementary search result request forwarded by the first application server.

[0025] In one optional embodiment, the information acquisition request is a sub-application recommendation list acquisition request; according to the information acquisition request, the identification information of the sub-applications of the second application is obtained from the second server, including:

[0026] Based on the sub-application recommendation list retrieval request sent by the target client, a sub-application recommendation list retrieval message is sent to the second application server; the sub-application recommendation list retrieval request contains the identification information of the target account; the sub-application recommendation list retrieval message includes the identification information of the associated account corresponding to the target account; the associated account is an account of the second application;

[0027] The system receives a list of sub-applications used within a set time period returned by the second application server. The list of sub-applications used within a set time period is a list of sub-applications used by the associated account within a set time period obtained by the second application server based on the identification information of the associated account. The list of sub-applications used within a set time period includes the identification information of at least one sub-application sorted by the most recent startup time.

[0028] Sending the identification information of the sub-application of the second application to the target client includes:

[0029] Send the list of sub-applications to be used within the set time period to the target client.

[0030] In one optional embodiment, the first application is a team instant messaging application, the second application is a personal instant messaging application, and the method further includes:

[0031] Receive a sub-application add request sent by the target client; the sub-application add request contains the identification information of the target sub-application to be added to the quick access area of ​​the target account; the target account is the account associated with the target client;

[0032] Based on the identification information of the target sub-application in the sub-application addition request, the target sub-application is added to the storage area corresponding to the quick access area of ​​the target account, and a notification of successful sub-application addition is returned to the target client.

[0033] In one alternative embodiment, the method includes:

[0034] Receive the launch sub-application event sent by the target client;

[0035] If the target sub-application corresponding to the launch sub-application event is included in the list of faulty sub-applications, then an interception notification to interrupt the launch of the target sub-application is sent to the target client, along with information that the target sub-application is included in the list of faulty sub-applications; the list of faulty sub-applications includes sub-applications that are used in the first application server and are experiencing failures.

[0036] If the target sub-application corresponding to the launch sub-application event is not included in the list of faulty sub-applications, then the information of the launch sub-application event is recorded.

[0037] Thirdly, embodiments of this application provide a control method for running sub-applications across applications, applied to a second application server, the method comprising:

[0038] The system receives an information retrieval request from a first application server to obtain the identification information of a sub-application of a second application; the information retrieval request is an information retrieval request sent by a target client of the first application received by the first application server; the first application server is a server associated with the first application; the second application server is a server associated with the second application.

[0039] The identification information of the sub-application that made the information request is obtained from the sub-application of the second application and sent to the first application server, so that the first application server sends the identification information of the sub-application of the second application to the target client.

[0040] In one alternative embodiment, the method includes:

[0041] Based on the received information retrieval request forwarded by the first application server, the identification information of the sub-application of the second application is obtained; the information retrieval request is an information retrieval request that is forwarded by the first application server to the second application server after being sent by the target client to the first application server, and is used to indicate the retrieval of the identification information of the sub-application of the second application.

[0042] The identification information of the sub-application of the second application is sent to the second application server so that the second application server forwards the identification information of the sub-application of the second application to the target client after receiving it.

[0043] In an optional embodiment, the information retrieval message is a sub-application recommendation list retrieval message, which contains the identification information of the associated account corresponding to the target account; the target account is the target account associated with the target client; the step of retrieving the identification information of the sub-application requesting the information retrieval message from the sub-application information of the second application and sending it to the first application server includes:

[0044] Based on the identification information of the associated account in the message of the sub-application recommendation list, obtain the list of sub-applications used by the associated account within a set time period. The list of sub-applications used within the set time period includes the identification information of at least one sub-application sorted by the most recent launch time.

[0045] The list of sub-applications used by the associated account within a specified time period is sent to the first application server.

[0046] Fourthly, embodiments of this application provide a control device for running sub-applications across applications, applied to a client of a first application, the device comprising:

[0047] The sub-application display unit is used to display the sub-application display interface in response to a trigger operation that opens the sub-application display interface by a target account. The sub-application display interface displays the identification information of the sub-application. The sub-application includes a sub-application of a second application. The identification information of the sub-application of the second application is obtained by the first application server associated with the first application from the second application server associated with the second application and sent to the client of the first application.

[0048] The sub-application launch unit is used to respond to the launch operation of the target sub-application triggered by the identification information of the target sub-application in the sub-application of the second application, obtain the data of the target sub-application from the second application server, and display the running interface of the target sub-application based on the data of the target sub-application.

[0049] Fifthly, embodiments of this application provide a control device for running sub-applications across applications, applied to a first application server, the device comprising:

[0050] The first request receiving unit is configured to receive an information retrieval request sent by a target client, indicating that the target client is a client of the first application; the first application server is a server associated with the first application.

[0051] The first request response unit is used to obtain the identification information of the sub-application of the second application from the second server according to the information acquisition request; the second application server is the server associated with the second application;

[0052] The first request feedback unit is used to send the identification information of the sub-application of the second application to the target client, so that the target client displays the identification information of the sub-application of the second application on the sub-application display interface.

[0053] Sixthly, embodiments of this application provide a control device for running sub-applications across applications, applied to a second application server, the device comprising:

[0054] The second request receiving unit is configured to receive an information retrieval request sent by the first application server to obtain the identification information of a sub-application of the second application; the information retrieval request is an information retrieval request sent by the target client of the first application received by the first application server; the first application server is a server associated with the first application; the second application server is a server associated with the second application.

[0055] The second request response unit is used to obtain the identification information of the sub-application that made the information acquisition message request from the sub-application of the second application and send it to the first application server, so that the first application server sends the identification information of the sub-application of the second application to the target client.

[0056] In a seventh aspect, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the control method for cross-application sub-application execution in the first, second, or third aspects.

[0057] Eighthly, embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program that can run on the processor, and when the computer program is executed by the processor, the processor enables the processor to implement the control method for running sub-applications across applications as described in the first, second, or third aspects.

[0058] This application provides a control method, apparatus, medium, and electronic device for running sub-applications across applications. The sub-application display interface of a first application's client can display the identification information of a sub-application of a second application, allowing the user to launch the second application's sub-application through this identification information displayed in the first application's sub-application display interface. When the user touches the identification information of the target sub-application within the second application's sub-application, the first application's client receives the user-triggered launch operation for the target sub-application, retrieves the target sub-application's data from the second application's server, and displays the target sub-application's running interface. This method allows users to conveniently and quickly run sub-applications of a second application through the first application's client, thereby improving the efficiency of running sub-applications across applications. Attached Figure Description

[0059] 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.

[0060] Figure 1 This application provides an illustration of an application scenario for a control method for running sub-applications across applications, as illustrated in an embodiment of this application.

[0061] Figure 2 An interaction diagram of a control method for running sub-applications across applications provided in an embodiment of this application;

[0062] Figure 3 An interaction diagram of another control method for running sub-applications across applications provided in this application embodiment;

[0063] Figure 4 An interaction diagram of another control method for running sub-applications across applications provided in this application embodiment;

[0064] Figure 5 An interaction diagram of another control method for running sub-applications across applications provided in this application embodiment;

[0065] Figure 6 A schematic diagram illustrating a cross-application sub-application interface provided in an embodiment of this application;

[0066] Figure 7 A schematic diagram illustrating another cross-application running sub-application interface provided in an embodiment of this application;

[0067] Figure 8 A schematic diagram illustrating another cross-application running sub-application interface provided in an embodiment of this application;

[0068] Figure 9 A schematic diagram illustrating another cross-application running sub-application interface provided in an embodiment of this application;

[0069] Figure 10 A schematic diagram illustrating another cross-application running sub-application interface provided in an embodiment of this application;

[0070] Figure 11 A schematic diagram illustrating another cross-application running sub-application interface provided in an embodiment of this application;

[0071] Figure 12 A schematic diagram illustrating another cross-application running sub-application interface provided in this application embodiment;

[0072] Figure 13 A schematic diagram illustrating another cross-application running sub-application interface provided in an embodiment of this application;

[0073] Figure 14 A schematic diagram illustrating a prompt to delete a sub-application in a cross-application running sub-application interface, provided as an embodiment of this application;

[0074] Figure 15 A schematic diagram of a mini-program fault reporting interface provided in an embodiment of this application;

[0075] Figure 16 A schematic diagram of a WeChat Mini Program disabling prompt interface provided in an embodiment of this application;

[0076] Figure 17 A flowchart illustrating a control method for running sub-applications across applications, provided in an embodiment of this application;

[0077] Figure 18 A flowchart illustrating another control method for running sub-applications across applications provided in this application embodiment;

[0078] Figure 19A flowchart illustrating another control method for running sub-applications across applications provided in this application embodiment;

[0079] Figure 20 A structural block diagram of a control device for running sub-applications across applications is provided in an embodiment of this application;

[0080] Figure 21 A structural block diagram of another control device for running sub-applications across applications provided in this application embodiment;

[0081] Figure 22 A structural block diagram of another control device for running sub-applications across applications provided in this application embodiment;

[0082] Figure 23 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0083] Figure 24 This is a schematic diagram of the structure of another electronic device provided in an embodiment of this application. Detailed Implementation

[0084] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0085] It should be noted that the terms "comprising" and "having" and their variations used in this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product, or device.

[0086] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0087] (1) Application: An application installed on a terminal device, such as an APP installed on a mobile terminal like a mobile phone, which belongs to the software resources of the terminal device. Applications typically have a visual interface for interacting with the user during runtime. Some applications can also serve as carriers of sub-applications. For example, in this embodiment, an instant messaging application can display the identification information of a sub-application in certain interfaces. The identification information of the sub-application can serve as the entry point for the sub-application, and the user can enter the corresponding sub-application by clicking on the identification information. In this embodiment, some applications can also form associations with other applications. For example, the first application is a team instant messaging application, and the second application is a personal instant messaging application; the first application and the second application can form an association. Correspondingly, the associated account of a target account in one application can be determined in another application, thereby obtaining the associated account of the target account.

[0088] (2) Sub-application: A sub-application is an application that can run on a terminal device without downloading or installing, and may include mini-programs or lightweight applications. For example, a mini-program running on an instant messaging application. A mini-program is an application that can be used without downloading or installing. To provide users with more diversified business services, developers can develop corresponding mini-programs for terminal applications (such as instant messaging applications, shopping applications, email applications, etc.). These mini-programs can be embedded as sub-applications into the terminal application, and by running the sub-application (i.e., the corresponding mini-program) within the application, corresponding business services can be provided to the user. In some embodiments of this application, a mini-program running on an instant messaging application is used as an example for illustration.

[0089] (3) Toast: A toast is a simple message notification box that appears as a floating view in an application. Unlike a dialog box, a toast is only used to display information to the user and cannot capture user clicks; therefore, a toast cannot be clicked. Furthermore, the toast is only displayed for a limited time and will automatically disappear after the user-set display time.

[0090] (4) Offset: The distance between the actual address of a storage unit and the segment address of its segment is called the intra-segment offset, also known as the effective address. In this embodiment, when the target client pulls the sub-application recommendation list, the first application server corresponding to the target client sorts the sub-application launch event information according to the most recent usage time and returns the offset and mini-program list data to the target client. The returned offset can be understood as the distance between the address of the storage unit corresponding to the first mini-program not included in the mini-program list data and the address of the storage unit corresponding to the mini-program ranked first by the most recent usage time. It is used by the target client when it pulls more mini-programs that may exist in addition to the returned mini-program list data next time.

[0091] The word “exemplary” as used below means “serving as an example, embodiment, or illustration.” Any embodiment illustrated as an “exemplary” need not be construed as superior to or better than other embodiments.

[0092] The terms "first" and "second" used in this document are for descriptive purposes only and should not be construed as indicating relative importance or implying the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0093] To better understand the technical solutions provided in the embodiments of this application, the following is a brief introduction to the application scenarios to which the technical solutions provided in the embodiments of this application are applicable. It should be noted that the application scenarios described below are only for illustrating the embodiments of this application and are not intended to limit the scope. In specific implementation, the technical solutions provided in the embodiments of this application can be flexibly applied according to actual needs.

[0094] Figure 1 This paper illustrates an application scenario of the control method for running sub-applications across applications provided in an embodiment of this application. See [link to relevant documentation]. Figure 1 As shown, this application scenario includes a terminal device 100, a first application server 200, and a second application server 300. The terminal device 100, the first application server 200, and the second application server 300 can communicate and transmit data via a network 400. This network can be a wired network or a wireless network. For example, the terminal device 100 can transmit data with the first application server 200 and the second application server 300 via a cellular data network or a Wi-Fi wireless network; the first application server 200 can also transmit data with the second application server 300 via a cellular data network or a Wi-Fi wireless network.

[0095] The terminal device 100 can be a mobile terminal such as a mobile phone, a PDA (Personal Digital Assistant), a tablet computer, or a smart wearable device (such as a smartwatch and a smart helmet). The first application server 200 and the second application server 300 can be a single server or a server cluster or cloud computing center composed of several servers, or a virtualization platform, or a personal computer, a large or medium-sized computer, or a computer cluster, etc.

[0096] In the application scenario provided in this application embodiment, a client of a first application is installed on a terminal device 100. The first application server 200 can be a server providing background support for the first application, and the number of terminal devices 100 connected to the first application server 200 can be one or more. A second application server 300 can be a server providing background support for a second application, and the client of the second application can be installed on [the server name missing]. Figure 1 On terminal devices similar to terminal device 100, since the technical solution of this application is not directly related to the client of the second application, Figure 1 The document does not show terminal devices with the client of the second application installed. The number of terminal devices connected to the second application server 300 with the client of the second application installed can also be one or more. The first application and the second application can be related; that is, the first application and the second application can be two applications using the same mini-program framework. For example, the first application can be a team instant messaging application, and the second application can be a personal instant messaging application. Users can log in to the target account through the client of the first application. In this embodiment, the target client refers to the client of the first application used to log in to the target account.

[0097] For example, terminal device 100 can be a mobile phone, on which a first application is installed, and a first application server 200 provides background services for the first application. In related technologies, to run a sub-application of a second application within the first application, the second application must forward the sub-application's link to the first application's session. The user then needs to click the sub-application's link within the first application's session to launch the sub-application, a rather cumbersome process. Therefore, the method of running sub-applications across applications in related technologies is inefficient.

[0098] Based on this, embodiments of this application provide a control method, apparatus, medium, and electronic device for running sub-applications across applications. In this embodiment, after a user logs into a first application using a target account, during the use of the first application, the client of the first application responds to a trigger operation that opens the sub-application display interface in response to the target account, and displays the sub-application display interface. The sub-application display interface displays the identification information of the sub-application, wherein the sub-application may include a sub-application of the first application or a sub-application of the second application. In response to a launch operation of the target sub-application triggered by the identification information of the target sub-application within the sub-application of the second application, data of the target sub-application is obtained from the server of the second application, and the running interface of the target sub-application is displayed based on the data of the target sub-application. This method allows users to conveniently and quickly run sub-applications of the second application through the client of the first application, thereby improving the efficiency of running sub-applications across applications.

[0099] In some embodiments, while a user is using the first application on the terminal device 100, the client of the first application can also respond to a sub-application search operation triggered by the target account through the sub-application display interface, sending a sub-application search request to the first application server 200. The sub-application search request is used to search for sub-applications within the second application. The first application server 200 forwards the sub-application search request to the second application server 300. The second application server 300 searches the sub-application database based on the search keywords in the sub-application search request and returns the resulting search results data to the first application server 200. The search results data includes at least one identifier for a sub-application of the second application. The first application server 200 forwards the search results data to the client of the first application, so that the client of the first application displays the identifier information of the sub-application of the second application on the sub-application display interface.

[0100] Users can select the target sub-application to launch from the identification information displayed on the sub-application display interface by clicking on the target sub-application's identification information. The client of the first application receives the user's input to launch the sub-application for the target sub-application, sends a launch request to the second application server 300, retrieves the target sub-application's data from the second application server 300, and displays the target sub-application's running interface based on the target sub-application's data. The above-described process of running sub-applications across applications and the interaction between various devices during this process will be described in detail below.

[0101] In one embodiment, the control method for running sub-applications across applications is implemented through an interaction process between a terminal device and a first application server and a second application server. In this embodiment, a client of the first application is installed on the terminal device. In the following description of the technical solutions of this application, the client of the first application represents the terminal device on which the client is installed, and the interaction process between the client of the first application and the first and second application servers is described. The client of the first application can be a first instant messaging application client, the first application server can be a first instant messaging application server, and the second application server can be a second instant messaging application server. The first instant messaging application can be a team instant messaging application, and the second instant messaging application can be a personal instant messaging application. This interaction process can be as follows: Figure 2 As shown, it includes the following steps:

[0102] In step S201, the client of the first application responds to the trigger operation of the target account opening the sub-application display interface and displays the sub-application display interface.

[0103] The sub-application display interface shows the identification information of the sub-applications. Sub-applications can include sub-applications of the first application or sub-applications of the second application. The identification information of a sub-application may include its icon, name, etc. Specifically, the identification information of the sub-applications of the second application is obtained by the first application server associated with the first application from the second application server associated with the second application and sent to the client of the first application.

[0104] In some embodiments, the sub-application display interface can be understood as the workbench interface of the first application. The target account is the login account of the first application. The user can open the client of the first application on the terminal device and log in to the client of the first application using the account information of the target account. For example, the target user can open the client of the first instant messaging application on the mobile phone and enter the target user's first instant messaging application account information, thereby realizing the login of the client of the first application using the account information of the target account.

[0105] like Figure 6 As shown, the first application is a team instant messaging application. After a user logs into the client of the first application using the target account's account information, they can click the workbench icon displayed at the bottom of the interface. The client of the first application receives a trigger operation from the target account to open the sub-application display interface, which then displays... Figure 6The workbench interface shown is shown below. The workbench interface can display group applications and personal mini-programs. Mini-programs can be understood as the sub-applications mentioned above. Specifically, "Application 1" through "Application 5" in group applications, and "Mini-program 1" through "Mini-program 3" in personal mini-programs, can all be understood as identifiers for sub-applications. These sub-applications can each perform one or more functions. Group applications can be sub-applications set up by the administrator of the user's team (which can consist of the user and their colleagues) for the corresponding account group of that team, and can be displayed on the workbench interface of each account belonging to that account group. Personal mini-programs can be sub-applications that the user adds to the workbench independently, and are only displayed on the target account's workbench interface. The specific process of adding sub-applications to the workbench will be described below. Personal mini-programs can also be sub-applications recently used by the target account, or sub-applications recently used by other accounts in the target account's account group. In some embodiments, "Mini-program 1," "Mini-program 2," and "Mini-program 3" can all be sub-applications of a second application.

[0106] Specifically, in some embodiments, when the client of the first application receives a trigger operation to open the sub-application display interface of the target account, it can obtain the identification information of the sub-applications in the account group workbench of the account group to which the target account belongs and the identification information of the sub-applications added to the workbench by the user corresponding to the target account from the data saved in the storage space corresponding to the workbench of the target account on the terminal device, and display the identification information of the sub-applications in the account group workbench. Figure 6 The group application area in the workbench interface shown displays the identifier information of the sub-applications that the user has added to the workbench. Figure 6 The personal mini-program area in the workbench interface is shown. Each time a user adds or removes a sub-application from the workbench, the client of the first application updates the data stored in the target account's workbench storage space on the terminal device. The specific data update process will be described in detail below.

[0107] In other embodiments, when the client of the first application receives a trigger operation to open the sub-application display interface of the target account, it can send a workbench data retrieval request to the first application server. This request carries the identification information of the target account. Upon receiving the workbench data retrieval request from the client, the first application server, based on the target account's identification information, locates the storage area corresponding to the target account's workbench in the first application server or its corresponding database. It then sends the data stored in this storage area to the client, including the identification information of sub-applications in the account group workbench of the target account's account group and the identification information of sub-applications added to the workbench by the user corresponding to the target account. Upon receiving the data returned by the first application server, the client of the first application displays the identification information of the sub-applications in the account group workbench. Figure 6 The group application area in the workbench interface shown displays the identifier information of the sub-applications that the user has added to the workbench. Figure 6 The personal mini-program area in the workbench interface shown.

[0108] In other embodiments, when the client of the first application receives a trigger operation to open the sub-application display interface of the target account, it can first display the identification information of the sub-application in the account group's workbench based on the data saved in the storage space corresponding to the workbench of the target account on the terminal device. Figure 6 The group application area in the workbench interface shown displays the identifier information of the sub-applications that the user has added to the workbench. Figure 6 The personal mini-program area in the workbench interface shown facilitates quick display of the operation interface. Simultaneously, the client of the first application can send a workbench data retrieval request to the first application server to obtain the data stored in the storage area corresponding to the target account's workbench on the first application server. If the data stored in the storage area corresponding to the target account's workbench on the first application server is inconsistent with the data stored in the storage area corresponding to the target account's workbench on the terminal device, then the data will be updated according to the data stored in the storage area corresponding to the target account's workbench on the first application server. Figure 6 The content displayed on the workbench interface is shown. If the data stored in the storage area corresponding to the target account's workbench in the first application server is consistent with the data stored in the storage area corresponding to the target account's workbench on the terminal device, then no update is required. Figure 6 The content displayed on the workbench interface shown.

[0109] In one embodiment, a user can select a sub-application of interest as a target sub-application in the workbench interface, click on the target sub-application's identifier to input a launch operation, and then launch the target sub-application. If the target sub-application is a sub-application of a second application, the client of the first application responds to the launch operation triggered by the target sub-application's identifier, retrieves the target sub-application's data from the second application server, and displays the target sub-application's running interface based on the target sub-application's data. Therefore, through the workbench of the first application, users can conveniently and quickly run sub-applications of both the first and second applications; hence, the workbench can also be called a quick access area. Users can add their frequently used sub-applications to the workbench of the first application for repeated use, thereby expanding the user's usage scenarios for mini-programs and promoting their further adoption.

[0110] In other embodiments, the sub-application display interface can also be understood as the sub-application search interface of the first application, such as when a user... Figure 6 Clicking the "Mini Program" button in the workbench interface shown will take you to... Figure 7 , Figure 8 or Figure 9 One of the user interfaces shown can be called the sub-application search interface. The sub-application search interface includes a mini-program search input box for "Search Mini-Programs".

[0111] In step S202, the client of the first application receives the sub-application search operation triggered by the target account through the sub-application display interface.

[0112] In step S203, the client of the first application sends a sub-application search request to the server of the first application.

[0113] For example, the user in Figure 9 Enter the search keywords in the search information input box shown in the image, and press Enter to trigger the sub-application search operation. The search keywords can be the full name or partial keywords of a sub-application that needs to run across applications within the first application. For example, the user could enter "customer". The client of the first application receives the sub-application search operation triggered by the target account through the sub-application's display interface, and sends a sub-application search request to the first application server. The sub-application search request includes the search keywords corresponding to the sub-application search operation.

[0114] In step S204, the first application server sends a sub-application search request to the second application server.

[0115] For example, when a first instant messaging application server receives a sub-application search request from a client of a first instant messaging application, and determines, based on key search information, that the target account is searching for a sub-application of a second instant messaging application, it forwards the sub-application search request to the second instant messaging application server. The sub-application search request contains key search information, such as "client". The first instant messaging application is the application associated with the first instant messaging application server, and the sub-application is a sub-application of the second instant messaging application.

[0116] In step S205, the second application server performs a search based on the search keywords in the sub-application search request and obtains the search results data.

[0117] In step S206, the second application server sends search result data to the first application server.

[0118] In step S207, the first application server sends search result data to the client of the first application.

[0119] In step S208, the client of the first application displays the identification information of the sub-application of the second application from the search results data on the sub-application display interface.

[0120] In one embodiment, a second application server receives a sub-application search request from a first application server. Based on the search keywords in the request, the second application server searches its sub-application database to obtain search results data, which includes at least one sub-application identifier. The second application server sends the search results data to the first application server, which then forwards it to the client of the first application. The client of the first application receives the search results data returned by the first application server and displays the sub-application identifier information of the second application from the search results data on the sub-application display interface.

[0121] For example, the second instant messaging application server searches the sub-application database based on the search keywords in the received sub-application search request, obtains search results data, and sends the search results data to the first instant messaging application server. The search results data includes at least one mini-program's identification information. The mini-program can be one whose name contains the search keywords, or, if no mini-program with the search keywords in its name exists, the second instant messaging application server obtains it based on other set matching principles. These mini-programs may not contain the search keywords in their names, but they may be present in other locations.

[0122] The first instant messaging application server forwards the search result data sent by the second instant messaging application server to the client of the first instant messaging application. The client of the first instant messaging application receives the search result data returned by the first instant messaging application server and displays the identification information of the sub-application in the search result data on the sub-application display interface. In some embodiments, the identification information of the sub-application may include a mini-program icon, name, description, etc. In other embodiments, the sub-application information displayed on the sub-application display interface may also include the descriptive information of "N colleagues have used it".

[0123] In another embodiment, when the second application server obtains the identification information of the sub-application containing a large amount of data in the search results based on the search key information in the sub-application search request, if the search results are directly forwarded to the client of the first application as search result data all at once through the first application server, the client of the first application cannot display all the search result data on one page.

[0124] Based on this, pagination control information can be set. This information limits the maximum number of sub-application identifiers that can be included in the search results data returned by the second application server each time. The pagination control information can be determined based on the maximum number of sub-application identifiers that can be displayed per page. For example, the pagination control information can be set to 20, meaning that the search results data returned by the second application server each time can contain a maximum of 20 sub-application identifiers. The pagination control information can be set by the first application server or by the client of the first application. The sub-application search request forwarded by the first application server to the second application server can carry the pagination control information.

[0125] The search results data forwarded by the second application server to the client of the first application server can only contain the identifier information and offset information of the number of sub-applications limited by the pagination control information. The search results obtained by the second application server based on the search key information can be stored on the second application server for later use when supplementing search results. The offset information is the position identifier of the first sub-application identifier that is included in the search results corresponding to the search key information but not included in the search results data. For example, when the pagination control information is 20, the search results data can include the identifier information of the 1st to 20th sub-applications found. Assuming the position identifier of the first sub-application identifier not included in the search results data is 21, then the offset information is 21.

[0126] For example, if the user enters the search keyword "customer", the second instant messaging application server searches the sub-application database based on the search keyword in the received sub-application search request, and the search results include identification information for 98 sub-applications. If the pagination control information in the sub-application search request is 20, the second instant messaging application server sends the search results data containing the identification information of sub-applications 1 to 20 to the first instant messaging application server. The search results data also includes offset information 21.

[0127] The first instant messaging application server forwards the search result data sent by the second instant messaging application server to the client of the first instant messaging application. For example... Figure 10 As shown, the client of the first instant messaging application receives search result data returned by the server of the first instant messaging application and displays the identification information of the sub-application in the search result data on the sub-application display interface. Since the search result data includes offset information, a "Next Page" indicator is displayed on the sub-application display interface; if the search result data does not include offset information, the "Next Page" indicator is not displayed on the sub-application display interface.

[0128] Optionally, users can... Figure 10 In the sub-application display interface shown, select the sub-application of interest as the target sub-application, click the identifier of the target sub-application, and enter the operation to launch the target sub-application. The client of the first application responds to the launch operation triggered by the identifier of the target sub-application, obtains the data of the target sub-application from the second application server, and displays the running interface of the target sub-application based on the data of the target sub-application.

[0129] Step S209: The client of the first application receives the sub-application supplementary search results operation entered by the target account in the sub-application display interface.

[0130] For example, when a user clicks Figure 10 The "Next Page" indicator shown triggers a sub-application supplementary search result operation. This operation allows the primary application server to return more sub-application search results. By displaying these additional search results, users can view all the sub-application search results.

[0131] In step S210, the client of the first application sends a request for supplementary search results from the sub-application to the server of the first application.

[0132] Specifically, in response to the sub-application's supplementary search results action triggered by the target account through the sub-application's display interface, the client of the first application sends a supplementary search results request to the first application server, which then forwards the request to the second application server. The supplementary search results request contains key search information and offset information.

[0133] In step S211, the first application server sends a supplementary search result request to the second application server.

[0134] In step S212, the second application server obtains the identification information of the sub-application from the search results corresponding to the search key information based on the offset information in the received supplementary search result request, and generates supplementary search data based on the obtained identification information of the sub-application.

[0135] The first application server forwards the supplementary search results request sent by the client of the first application to the second application server. The supplementary search results request may contain search keywords, pagination control information, and offset information. Assume the supplementary search results request contains the search keyword "client," pagination control information of 20, and offset information of 21. The second application server uses the search keyword "client" in the supplementary search results request to find the search results saved since the last search. It then retrieves the identifiers of 20 sub-applications (positions 21 to 40) from the search results. Based on the retrieved sub-application identifiers, it generates supplementary search data. The supplementary search data also includes new offset information of 41, where 41 is the position identifier of the first sub-application identifier not included in the supplementary search data.

[0136] In step S213, the second application server sends supplementary search data to the first application server.

[0137] In step S214, the first application server sends supplementary search data to the client of the first application.

[0138] The first application server forwards the supplementary search data sent by the second application server to the client of the first application.

[0139] In step S215, the client of the first application receives the supplementary search data returned by the first application server and displays the identification information of the sub-applications in the supplementary search data.

[0140] The client of the first application receives supplementary search data returned by the server of the first application, and displays the identification information of the sub-application of the second application from the supplementary search data on the sub-application display interface. Figure 10 The sub-application display interface shown displays the identification information of the sub-applications on the next page.

[0141] Optionally, users can select an application of interest as a target application from the sub-application identifiers displayed on the next page of the sub-application display interface, and then click on the target application's identifier to input a launch operation to start the target application. The client of the first application responds to the launch operation triggered by the target application's identifier, retrieves the target application's data from the second application server, and displays the target application's running interface based on the target application's data.

[0142] If the user clicks the "Next Page" icon again, the interaction process between the first application server, the second application server, and the client of the first application can be executed according to steps S209 to S215. Finally, the identification information of the sub-application on the new page is displayed on the sub-application display interface of the client of the first application. The detailed process will not be described here.

[0143] The above embodiment includes a search entry point in the first application. During the control process of running sub-applications across applications, the client of the first application can search for sub-applications of the second application across applications, which effectively improves the convenience of running sub-applications across applications and promotes the further promotion and use of sub-applications.

[0144] Considering that related technologies cannot statistically analyze the usage of sub-applications running across applications within a single application, users cannot understand the usage of these sub-applications. Therefore, in some embodiments, the client of the first application can also display the identifiers of recently used sub-applications to the user in the sub-application display interface for selection. In this process, the interaction between the client of the first application, the first application server, and the second application server can be as follows: Figure 3 As shown, it includes the following steps:

[0145] Step S301: The client of the first application receives the sub-application recommendation list retrieval operation triggered by the sub-application display interface.

[0146] In some embodiments, the sub-application display interface can be understood as Figure 6 The workbench interface is shown. When a user clicks the "Recently Used" or "Colleagues Using" button on the workbench interface, the client of the first application receives a sub-application recommendation list retrieved by the target account.

[0147] In other embodiments, the sub-application display interface can be understood as... Figure 7 The sub-application search interface is shown. The user clicks... Figure 7 In the "Recently Used" or "Colleagues Using" areas of the sub-application search interface shown, the client of the first application receives a sub-application recommendation list retrieval operation triggered by the target account.

[0148] In step S302, the client of the first application sends a request to the first application server to obtain the sub-application recommendation list.

[0149] The client of the first application responds to the sub-application recommendation list retrieval operation triggered by the target account through the sub-application display interface by sending a sub-application recommendation list retrieval request to the first application server. The sub-application recommendation list retrieval request contains the identification information of the target account.

[0150] In step S303, the first application server obtains the list of sub-applications used by the target account within a set time period based on the received sub-application recommendation list retrieval request.

[0151] The first application server receives a request from the client of the first application to retrieve a sub-application recommendation list. Based on the identifier information of the target account in the request, it retrieves the list of recently used sub-applications corresponding to that target account. Optionally, the first application server stores a list of recently used sub-applications for each account. The first application server retrieves the list of recently used sub-applications for the target account from the list of recently used sub-applications for each account based on the identifier information of the target account. The list of recently used sub-applications for each account is generated by the first application server based on recorded sub-application launch event information. This sub-application launch event information is recorded by the first application server when an account launches a sub-application. Taking the target account as an example, each time the target account launches a sub-application, the client of the first application sends a sub-application launch event to the first application server. The first application server records the sub-application launch event information based on the received event, including the identifier information of the launched target sub-application, the identifier information of the target account, and the launch time.

[0152] The first application server, at set intervals, generates and saves a list of recently used sub-applications for each account based on the recorded sub-application launch events. Alternatively, upon receiving a request to retrieve a sub-application recommendation list for a target account, the first application server generates a list of recently used sub-applications for the target account based on the recorded sub-application launch events. This list includes the identifiers of at least one sub-application sorted by its most recent launch time; or, in other words, the identifiers are sorted by their most recent launch time, or by the time difference between their most recent launch time and the time the list was generated, in ascending order. Optionally, the identifiers can also be sorted by the number of times the sub-application has been used and its most recent launch time.

[0153] In step S304, the first application server sends a list of sub-applications corresponding to the target account within a set time period to the client of the first application.

[0154] In step S305, the client of the first application displays the identification information of the sub-applications in the sub-application list used within a set time period on the sub-application display interface.

[0155] In some embodiments, the sub-application recommendation list retrieval request instructs the user to retrieve sub-applications that a target account has launched within a set time period. For example, a user in Figure 6 Clicking the "Recently Used" button in the workbench interface triggers a sub-application recommendation list retrieval operation by the target account. The client of the first application sends a sub-application recommendation list retrieval request to the first application server, specifying the sub-applications launched by the target account within a set time period. The first application server retrieves the recently used sub-application list corresponding to the target account based on the target account's identifier information in the request. This list includes identifiers of sub-applications launched by the target account within the set time period, which can be one month, three months, or six months. The first application server then sends the recently used sub-application list to the client of the first application, which displays the identifiers of these sub-applications in the corresponding display area on the sub-application display interface. Figure 7 As shown, the client of the first application displays the identification information of the sub-applications in the list of recently used sub-applications in the recently used area.

[0156] In other embodiments, the sub-application recommendation list retrieval request instructs the retrieval of sub-applications launched by each account in an account group associated with a target account within a set time period. For example, a user in Figure 6Clicking the "Colleagues are using" button on the workbench interface triggers a sub-application recommendation list retrieval operation from the target account. The client of the first application sends a sub-application recommendation list retrieval request to the first application server. This request instructs the server to retrieve the sub-applications launched by each account in the account group associated with the target account within a set time period. Based on the target account's identifier information in the sub-application recommendation list retrieval request, the first application server determines the account group associated with the target account. This account group corresponds to the user's team and includes the accounts of the user's colleagues. The first application server uses the recently used sub-application list corresponding to this account group as the recently used sub-application list for the target account. This recently used sub-application list includes the identifier information of each sub-application launched by each account in the account group associated with the target account within the set time period. The identifier information of the sub-applications in the recently used sub-application list is sorted by the number of accounts using each sub-application within the set time period and the most recent launch time. The first application server sends the recently used sub-application list for the target account to the client of the first application, and the client displays the identifier information of the sub-applications in the recently used sub-application list in the corresponding display area on the sub-application display interface. Figure 8 As shown, the client of the first application displays the identification information of the sub-applications in the list of recently used sub-applications in the area where colleagues are using the application.

[0157] If the user is Figure 7 In the interface shown, clicking on the area where colleagues are using the application will display the following on the client side: Figure 9 The interface shown displays the identifiers of recently used sub-applications in the area where colleagues are using the application. This embodiment of the application, by statistically analyzing sub-applications running across applications and displaying recently used sub-applications on the interface, allows users to understand the usage of sub-applications running across applications.

[0158] In some embodiments, if the first application server does not obtain the list of sub-applications used within a set time period corresponding to the target account, or if the list of sub-applications used within a set time period corresponding to the target account is empty, the first application server may return a notification that no relevant sub-applications were found to the client of the first application. In this case, the recently used area or the area where colleagues are using the first application client may be a blank area, without displaying any content.

[0159] In other embodiments, the first application server receives a sub-application recommendation list retrieval request from a client of the first application. The sub-application list returned to the client of the first application within a set time period may include identification information of sub-applications launched within the set time period by an associated account corresponding to the target account in the second application. Here, the associated account is an account in the second application. For example, a user triggers a sub-application recommendation list retrieval operation on the sub-application display interface, requesting a list of recently used sub-applications corresponding to the target account. If the first application server does not obtain a list of recently used sub-applications corresponding to the target account, it can determine an associated account of the target account in the second application. The target account and its associated account can be understood as accounts used by the same user in the first and second applications respectively. The first application server sends a sub-application recommendation list retrieval request to the second application server. This request includes the identification information of the associated account corresponding to the target account. The second application server retrieves the list of recently used sub-applications corresponding to the associated account based on the identification information of the associated account. The retrieval process is similar to that described above, where the first application server retrieves the list of recently used sub-applications corresponding to the target account, and will not be repeated here. The second application server sends the list of recently used sub-applications corresponding to the associated account to the first application server. The first application server then sends the list of recently used sub-applications corresponding to the associated account as the list of recently used sub-applications corresponding to the target account to the client of the first application. The client of the first application displays the identification information of the sub-applications in the recently used area of ​​the sub-application display interface.

[0160] Users can select an application of interest from the identifiers of recently used applications displayed in the recent applications section as the target application. They can then click on the target application's identifier and enter a command to launch it. The client of the first application, responding to the launch command triggered by the target application's identifier, retrieves the target application's data from the second application server and displays the target application's running interface based on the displayed data. In this embodiment, users can also quickly launch a target application by clicking on recently used applications displayed on the sub-application display interface and entering a launch command. In summary, users can launch target sub-applications from different sub-application display interfaces, making cross-application use of sub-applications more convenient and faster.

[0161] Optionally, the list of sub-applications used within a set time period sent by the first application server to the client of the first application may include the identification information and offset information of a number of sub-applications limited by pagination control information. The pagination control information limits the maximum number of sub-application identification information entries included in the list of sub-applications used within the set time period, and can be determined based on the maximum number of sub-application identification information entries that can be displayed on each page. The offset information is the position marker of the first sub-application identification information recently used by the target account but not included in the list of sub-applications used within the set time period, so as to facilitate the subsequent retrieval of the identification information of recently used sub-applications displayed on the next page. The specific process is similar to the process of obtaining sub-application search result data described above, and will not be repeated here.

[0162] In some embodiments, during the process of a user launching a target sub-application in the sub-application display interface, the interaction process between the client of the first application, the first application server, and the second application server can be as follows: Figure 4 As shown, it includes the following steps:

[0163] Step S401: The client of the first application receives the sub-application launch operation input by the target account for the target sub-application.

[0164] The target sub-application is a sub-application of the second application. As mentioned above, the sub-application display interface shows the sub-application's identifier information, indicating that this sub-application includes a sub-application of the second application. Users can... Figures 6-10 In any of the sub-application display interfaces shown in the images, select the sub-application of interest as the target sub-application. When the user clicks on the identifier of the selected target sub-application, the client of the first application will receive the sub-application launch operation input by the target account for the target sub-application.

[0165] In step S402, the client of the first application sends a sub-application launch event to the first application server.

[0166] The sub-application launch event includes the identifier of the target sub-application being launched, the identifier of the target account, and the time the sub-application was launched.

[0167] In step S403, the client of the first application sends a request to the second application server to launch a sub-application.

[0168] The second application server, acting as the server for the target sub-application, stores the data of the target sub-application. Before, after, or simultaneously with sending a "start sub-application" event to the first application server, the client of the first application sends a "start sub-application" request to the second application server to retrieve the target sub-application data from the second application server.

[0169] Step S404: If the first application server determines that the target sub-application corresponding to the received launch sub-application event is not included in the list of faulty sub-applications, then the information of the launch sub-application event is recorded.

[0170] The first application server determines whether the target sub-application is included in the list of faulty sub-applications based on the identification information of the target sub-application contained in the received sub-application launch event. The list of faulty sub-applications includes sub-applications that are confirmed to be unable to run properly in the first application or sub-applications that are prohibited from running in the first application.

[0171] In some embodiments, if the first application server determines that the target sub-application is included in the list of faulty sub-applications, the first application server may send an interception notification to the client of the first application (i.e., the client corresponding to the target account) to interrupt the startup of the target sub-application. Upon receiving the interception notification from the first application server, the client of the first application interrupts the startup of the target sub-application. If the client of the first application has already received the data of the target sub-application returned by the second application server, it stops loading the data of the target sub-application, interrupts the startup of the target sub-application, and displays the prompt information in the interception notification, such as "Unable to start normally" or "The mini-program cannot run normally."

[0172] In some embodiments, the list of faulty sub-applications may include two sub-lists: a first list of faulty sub-applications and a second list of faulty sub-applications. The first list of faulty sub-applications contains sub-applications that are confirmed to be unable to run normally in the first application, while the second list of faulty sub-applications contains sub-applications that are prohibited from running in the first application. The first application server sequentially determines whether the target sub-application corresponding to the received sub-application launch event is included in the first list of faulty sub-applications and whether the target sub-application corresponding to the received sub-application launch event is included in the second list of faulty sub-applications. The first application server can generate different prompt messages based on whether the target sub-application is included in the first or second list of faulty sub-applications. For example, if the target sub-application is included in the first list of faulty sub-applications, the generated interception notification may include a prompt message indicating that the sub-application cannot run normally. If the target sub-application is included in the second list of faulty sub-applications, the generated interception notification may include a prompt message prohibiting the use of the sub-application.

[0173] For example, if the target sub-application is included in the second list of faulty sub-applications and is a sub-application prohibited from running in the first application, causing the target sub-application to be unable to start, then the following can be displayed: Figure 16 The mini-program's disabled prompt interface is shown below. Figure 16 As shown, the displayed mini-program disabled prompt interface will tell the user "Cannot open mini-program" and display the message "This mini-program has been set by the administrator to be prohibited from being opened in this application".

[0174] For example, if the target sub-application is included in the first list of faulty sub-applications and is determined to be unable to run in the first application, causing the target sub-application to fail to start normally, then a message can be displayed related to... Figure 16 Similar mini-program failure prompts may appear. These prompts may display "Cannot open mini-program" and the message "This mini-program has been confirmed to be unable to function properly in the first application."

[0175] If the first application server determines that the target sub-application is not included in the list of faulty sub-applications, it records the sub-application startup event information, including the target sub-application's identifier, the target account's identifier, and the startup time. Based on the recorded sub-application startup event information, the first application server can sort the target account's most recently used sub-applications. When the first application's client requests a list of sub-applications used within a set time period, the server sorts the identifiers of the target account's most recently used sub-applications by their most recent startup time and generates a list, which is then sent to the first application's client.

[0176] In step S405, the second application server obtains the data of the target sub-application based on the identification information of the target sub-application included in the sub-application launch request.

[0177] Step S406: The second application server sends the target sub-application data to the client of the first application.

[0178] In step S407, the client of the first application runs the target sub-application based on the data received from the target sub-application.

[0179] If the client of the first application does not receive the interception notification sent by the first application server, it retrieves the data of the target sub-application from the second application server and runs the target sub-application based on the data, displaying as shown below. Figure 11 The target sub-application "XX Customer Training" is shown in the running interface.

[0180] In other embodiments, users can add sub-applications to the workbench while the sub-application is running for easy future use. Users can also remove sub-applications from the workbench. During this process, the interaction between the first application server, the second application server, and the client of the first application is as follows: Figure 5 As shown, it may include the following steps:

[0181] Step S501: The client of the first application receives the operation of adding the sub-application to the quick access area entered by the target account in the running interface of the target sub-application.

[0182] The quick access area can be understood as a workbench, and adding a sub-application to the quick access area is the same as adding a sub-application to the workbench.

[0183] For example, a user can open the target sub-application by clicking the icon of the target sub-application in the client of the target account's first instant messaging application. Figure 11 The target sub-application's running interface is shown. Figure 11 In the shown interface, when the user clicks the three dots in the upper right corner, these dots represent the settings button. In response, the client of the first application displays several function buttons, including an "Add to Workbench" button, on the target sub-application's interface. When the user clicks the "Add to Workbench" button, the client of the first application receives the user's input in the target sub-application's interface indicating that the sub-application has been added to the quick access area.

[0184] In step S502, the client of the first application sends a request to the first application server to add a sub-application.

[0185] The sub-application addition request includes the identification information of the target sub-application to be added to the target account's workbench and the identification information of the target account.

[0186] In step S503, the first application server adds the target sub-application to the storage area corresponding to the quick access area of ​​the target account based on the identification information of the target sub-application and the identification information of the target account in the sub-application addition request.

[0187] Step S504: The first application server sends a notification to the client of the first application that the sub-application has been successfully added.

[0188] The first application server obtains the identification information of the target sub-application and the target account from the sub-application addition request. Based on the identification information of the target sub-application and the target account, it adds the target sub-application to the storage area corresponding to the workbench of the target account and returns a notification of successful addition of the sub-application to the client of the first application.

[0189] In step S505, the client of the first application displays information on the running interface of the target sub-application that the target sub-application has been added to the workbench.

[0190] When the client of the first application receives a notification from the server of the first application that the sub-application has been successfully added, the client displays the information that the target sub-application has been added to the workbench on the running interface of the target sub-application.

[0191] For example, such as Figure 12 As shown, the client of the first application displays a message box indicating that the target sub-application has been added to the workbench.

[0192] Step S506: The client of the first application sends a personal workbench data acquisition request to the first application server.

[0193] After receiving the notification from the first application server that the sub-application has been successfully added, the client of the first application sends a personal workbench data retrieval request to the first application server. The personal workbench data retrieval request includes the identification information of the target account.

[0194] In step S507, the first application server obtains the identification information of the target account in the received personal workbench data acquisition request and retrieves the list of sub-applications from the storage area corresponding to the target account's workbench.

[0195] This list of sub-applications includes identification information for all sub-applications that the target account has added to the workbench.

[0196] In step S508, the first application server sends a list of sub-applications to the client of the first application.

[0197] In step S509, the client of the first application associates and stores the received list of sub-applications with the account group workbench data of the target account.

[0198] The client of the first application saves the received list of sub-applications and the target account's account group workbench data to the storage space corresponding to the target account's workbench on the terminal device, thereby updating the data saved in the storage space corresponding to the target account's workbench on the terminal device. This terminal device is the one with the client of the first application installed, and the sub-applications in the target account's account group workbench are the sub-applications set up by the administrator of the team to which the user corresponding to the target account belongs. For example... Figure 6 As shown, when the client of the first application displays the workbench interface of the target account, group applications and personal mini-programs are displayed in the workbench interface. Among them, the sub-applications in the group applications include the sub-applications in the account group workbench, and the personal mini-programs include the sub-applications in the list of sub-applications sent by the first application server based on the personal workbench data retrieval request.

[0199] Optionally, for sub-applications already added to the workbench, users can also remove them from the workbench. Specifically, for sub-applications already added to the workbench, if the user... Figure 11 Clicking the settings button in the shown interface will cause the first application's client to respond to the user's action by displaying multiple function buttons, including a "Remove from Workbench" button, on the target sub-application's interface. Figure 13 As shown. When the user clicks the "Remove from Workbench" button, the client of the first application receives the operation of removing the sub-application from the workbench entered by the target account in the running interface of the target sub-application.

[0200] The client of the first application receives the operation of removing the sub-application from the workbench entered by the target account in the running interface of the target sub-application, and sends a sub-application removal request to the first application server. The sub-application removal request includes the identification information of the second target sub-application and the identification information of the target account.

[0201] The first application server receives a sub-application removal request from the first application client. Based on the identifier information of the second target sub-application and the identifier information of the target account in the sub-application removal request, the server deletes the second target sub-application from the storage area corresponding to the target account's workbench and sends a sub-application removal success notification to the first application client. Upon receiving the sub-application removal success notification from the first application server, the first application client displays information indicating that the target sub-application has been removed from the workbench on the target sub-application's running interface. For example, as... Figure 14 As shown, the client of the first application displays a message box indicating that the target sub-application has been removed from the workbench.

[0202] After receiving the notification of successful sub-application removal from the first application server, the client of the first application can send a personal workbench data retrieval request to the first application server. This request includes the target account's identification information. Upon receiving the request, the first application server retrieves the current sub-application list from the storage area corresponding to the target account's workbench, based on the target account's identification information, and sends this list back to the client. The client then associates and stores the current sub-application list with the target account's account group workbench data.

[0203] In the control process of running sub-applications across applications, as described in the above embodiments, sub-applications of the second application can be added or removed from the first application's workbench via the client of the first application. For frequently used sub-applications, users can add them to their personal workbench, allowing them to quickly find the sub-application in the workbench interface the next time they use it, thereby further improving the efficiency of running sub-applications across applications.

[0204] In another embodiment of this application, the control method for running sub-applications across applications may further include Figure 5 The interaction process between the terminal device and the first application server and the second application server is shown below. Figure 5 As shown, it includes the following steps:

[0205] Step S501: The client of the first application receives a trigger operation from the target account to open the sub-application display interface.

[0206] In step S502, the client of the first application sends an information retrieval request to the first application server, indicating that it needs to obtain the identification information of the sub-application of the second application.

[0207] Step S503: The first application server receives an information retrieval request.

[0208] Step S504: The first application server sends an information retrieval message request to the second application server to obtain the identification information of the sub-application of the second application.

[0209] Step S505: The second application server receives an information retrieval message request sent by the first application server to obtain the identification information of the sub-application of the second application.

[0210] Step S506: The second application server obtains information from the sub-application of the second application to obtain the identification information of the sub-application that made the message request.

[0211] In step S507, the second application server sends the identification information of the sub-application to the first application server.

[0212] In step S508, the first application server sends the identification information of the sub-application to the client of the first application.

[0213] Step S509: The client of the first application displays the sub-application display interface.

[0214] In step S510, the client of the first application receives the target account's identification information for the target sub-application in the sub-application of the second application, triggering the launch of the target sub-application.

[0215] In step S511, the client of the first application obtains the data of the target sub-application from the second application server and displays the running interface of the target sub-application based on the data of the target sub-application.

[0216] The interaction process in steps S501 to S511 can be executed with reference to the interaction process in the foregoing embodiments, and will not be repeated here.

[0217] The embodiments of this application may also include the following implementation methods:

[0218] In another embodiment, the information retrieval request is a sub-application search request; based on the information retrieval request, the identification information of the sub-application of the second application is obtained from the second server, and the specific process is as follows:

[0219] The first application server forwards a sub-application search request to the second application server; the sub-application search request contains key search information. The first application server receives the search result data returned by the second application server; the search result data is obtained by the second application server based on the key search information in the sub-application search request; the search result data includes at least one sub-application identifier.

[0220] The first application server sends the identification information of the sub-application of the second application to the target client, specifically: sending search result data to the target client.

[0221] In another embodiment, the information retrieval request is a sub-application recommendation list retrieval request; based on the information retrieval request, the identification information of the sub-applications of the second application is obtained from the second server, and the specific process is as follows:

[0222] The first application server, based on the sub-application recommendation list retrieval request sent by the target client, sends a sub-application recommendation list retrieval message to the second application server. The sub-application recommendation list retrieval request includes the identifier information of the target account. The sub-application recommendation list retrieval message includes the identifier information of the associated account corresponding to the target account; the associated account is an account of the second application. The first application server receives a list of sub-applications used within a set time period returned by the second application server. This list of sub-applications used within a set time period is a list of sub-applications used within a set time period by the associated account, obtained by the second application server based on the identifier information of the associated account. This list includes the identifier information of at least one sub-application sorted by its most recent launch time. The first application server then sends the identifier information of the second application's sub-applications to the target client, specifically: sending the list of sub-applications used within a set time period to the target client.

[0223] In another embodiment, the information retrieval message is a sub-application search request, which contains key search information; the identification information of the sub-application requesting the information retrieval message is obtained from the sub-application of the second application and sent to the first application server, as follows:

[0224] The second application server searches its sub-application database based on the search keywords in the sub-application search request and obtains search results data. The second application server then sends the search results data to the first application server. The search results data includes at least one sub-application identifier.

[0225] In another embodiment, the information retrieval message is a sub-application recommendation list retrieval message, which contains the identification information of the associated account corresponding to the target account; the target account is the target account associated with the target client; the identification information of the sub-application requesting the information retrieval message is obtained from the sub-application information of the second application and sent to the first application server, as follows:

[0226] The second application server retrieves the associated account's list of sub-applications used within a specified time period based on the associated account's identification information in the sub-application recommendation list. The list of sub-applications used within the specified time period includes the identification information of at least one sub-application sorted by the most recent launch time. The second application server then sends the associated account's list of sub-applications used within the specified time period to the first application server.

[0227] While this application provides operational steps for the methods shown in the above embodiments or accompanying drawings, more or fewer operational steps may be included in the above methods based on conventional methods or without inventive effort. For steps that do not logically have a necessary causal relationship, the execution order of these steps is not limited to the execution order provided in the embodiments of this application. In actual processing or when the device executes the above methods, they may be executed sequentially or in parallel as shown in the embodiments or accompanying drawings.

[0228] In the above embodiments, the control method for running sub-applications across applications executed by the client of the first application, or in other words, the control method for running sub-applications across applications executed by the terminal device that has the client of the first application installed, such as... Figure 17 As shown, the following steps may be included:

[0229] Step S1701: In response to the triggering operation of the target account opening the sub-application display interface, the sub-application display interface is displayed, and the identification information of the sub-application is displayed on the sub-application display interface.

[0230] The sub-application may include a sub-application of the second application. The identification information of the sub-application of the second application is obtained by the first application server associated with the first application from the second application server associated with the second application and sent to the client of the first application.

[0231] Step S1702: In response to the target sub-application launch operation triggered by the identification information of the target sub-application in the sub-application of the second application, the target sub-application data is obtained from the second application server and the target sub-application running interface is displayed according to the target sub-application data.

[0232] In some embodiments, in response to a target sub-application launch operation triggered by the identification information of the target sub-application in a sub-application of the second application, data of the target sub-application is obtained from the second application server, and the running interface of the target sub-application is displayed based on the data of the target sub-application. If, during this process, some unknown fault occurs, causing the target sub-application to fail to start, the running interface of the target sub-application will not be displayed normally, and at this time, the following will be displayed: Figure 15 The shown is the troubleshooting interface for the mini-program. Figure 15 As shown, when the aforementioned special circumstances occur, the displayed mini-program fault reporting interface will prompt the user that "the mini-program cannot run normally," and provide a feedback input box that reads "Please describe the scenario and manifestation of the problem," allowing the user to report the scenario and manifestation of the mini-program's malfunction. This feedback input box can be limited to 200 characters. The displayed mini-program fault reporting interface also includes an image upload box for users to upload screenshots of the mini-program malfunction. This image upload box can limit the upload to a maximum of four screenshots. The feedback information from the mini-program fault reporting interface can be sent to the first application server, allowing the backend personnel of the first application server to perform corresponding follow-up maintenance work and add the mini-program to the list of faulty sub-applications.

[0233] For example, the sub-application display interface in step S1701 can be Figure 6 The workbench interface is shown. In some embodiments, when the client of the first application receives a trigger operation to open the sub-application display interface of the target account, it can send a workbench data retrieval request to the first application server. The workbench data retrieval request carries the identification information of the target account. When the first application server receives the workbench data retrieval request from the client of the first application, it locates the storage area corresponding to the workbench of the target account in the first application server or the database corresponding to the first application server based on the identification information of the target account in the workbench data retrieval request. It then sends the data stored in the storage area corresponding to the workbench of the target account to the client of the first application, including the identification information of the sub-applications in the account group workbench of the account group to which the target account belongs and the identification information of the sub-applications added to the workbench by the user corresponding to the target account. When the client of the first application receives the data returned by the first application server, it displays the identification information of the sub-applications in the account group workbench. Figure 6 The group application area in the workbench interface shown displays the identifiers of the sub-applications that the user has added to the workbench. Figure 6 The personal mini-program area in the workbench interface shown.

[0234] In other embodiments, prior to the launch of the target sub-application triggered by the identification information of the target sub-application in a sub-application of the second application, the method further includes:

[0235] In response to a sub-application search operation triggered by a target account through the sub-application display interface, a sub-application search request is sent to the first application server. The sub-application search request includes search key information corresponding to the sub-application search operation, so that the first application server can send the sub-application search request to the second application server when the target account is searching for a sub-application of the second application based on the search key information.

[0236] The system receives search result data returned by the first application server and displays the identification information of the sub-application of the second application in the search result data on the sub-application display interface. The search result data is obtained by the second application server based on the search key information after receiving the sub-application search request forwarded by the first application server and sending it to the first application server.

[0237] Optionally, the search results data includes the identification information and offset information of a number of sub-applications limited by pagination control information; the pagination control information is used to limit the maximum number of sub-application identification information items included in the search results data returned by the second application server each time; the offset information is the position identifier of the first sub-application identification information item included in the search results corresponding to the search key information but not included in the search results data; the search results corresponding to the search key information are the search results obtained by the first application server based on the search key information; after displaying the identification information of the sub-applications of the second application in the search results data on the sub-application display interface, the method further includes:

[0238] In response to a sub-application supplementary search result operation triggered by the target account through the sub-application display interface, a supplementary search result request is sent to the first application server, so that the first application server sends the supplementary search result request to the second application server; the supplementary search result request contains search key information and offset information;

[0239] The system receives supplementary search data returned by the first application server and displays the identification information of the second application's sub-application in the supplementary search data on the sub-application display interface. The supplementary search data is obtained by the second application server from the search results corresponding to the search key information based on the offset information, after receiving the supplementary search result request forwarded by the first application server, and then sending it to the first application server.

[0240] In other embodiments, prior to the launch of the target sub-application triggered by the identification information of the target sub-application in a sub-application of the second application, the method further includes:

[0241] In response to the target account's request to retrieve the sub-application recommendation list triggered by the sub-application display interface, a sub-application recommendation list retrieval request is sent to the first application server; the sub-application recommendation list retrieval request contains the target account's identification information;

[0242] Receive a list of sub-applications used within a set time period corresponding to the target account, returned by the first application server based on the target account's identification information; the list of sub-applications used within the set time period includes the identification information of at least one sub-application sorted by its most recent launch time;

[0243] The sub-application display interface shows the identification information of the sub-applications in the list of sub-applications used within a set time period.

[0244] Optionally, the sub-application recommendation list retrieval request indicates that the target account has launched sub-applications within a set time period; the sub-applications used within the set time period list includes the identification information of the sub-applications launched by the target account within the set time period; or, the sub-application recommendation list retrieval request indicates that the target account's associated account group's sub-applications have launched sub-applications within the set time period; the sub-applications used within the set time period list includes the identification information of the sub-applications launched by the target account's associated account group within the set time period; the identification information of the sub-applications in the sub-applications used within the set time period list is sorted according to the number of accounts that used each sub-application within the set time period and the most recent launch time; or, the sub-applications used within the set time period list includes the identification information of the sub-applications launched by the associated account of the target account in the second application within the set time period; the associated account is the account of the second application.

[0245] In some embodiments, the first application is a team instant messaging application, and the second application is a personal instant messaging application; the above method may further include:

[0246] In response to the target user's action of adding a sub-application to the quick access area in the target sub-application's running interface, a sub-application add request is sent to the first application server; the sub-application add request contains the identification information of the target sub-application;

[0247] Upon receiving a notification from the first application server that the sub-application has been successfully added, the system displays information indicating that the target sub-application has been added to the quick access area.

[0248] Optionally, the above method may further include:

[0249] In response to the target user's action of removing the sub-application from the quick access area in the target sub-application's running interface, a sub-application removal request is sent to the first application server; the sub-application removal request contains the identification information of the target sub-application;

[0250] Upon receiving a notification from the first application server indicating that the sub-application has been successfully removed, the system displays information indicating that the target sub-application has been removed from the quick access area.

[0251] In one optional embodiment, in response to a target sub-application launch operation triggered by the identification information of the target sub-application in a sub-application of the second application, data of the target sub-application is obtained from the second application server, and the running interface of the target sub-application is displayed based on the data of the target sub-application, including:

[0252] In response to the operation of launching the target sub-application, a launch sub-application event is sent to the first application server;

[0253] If an interception notification is received from the first application server, the startup of the target sub-application is interrupted, and information about the target sub-application being included in the list of faulty sub-applications is displayed.

[0254] If no interception notification is received from the first application server, the data of the target sub-application is obtained from the second application server, and the running interface of the target sub-application is displayed based on the data of the target sub-application.

[0255] In the above embodiments, the control method for running sub-applications across applications executed by the first application server, such as... Figure 18 As shown, the following steps may be included:

[0256] Step S1801: Receive an information retrieval request sent by the target client, indicating that the identification information of the sub-application of the second application is to be obtained.

[0257] The target client is the client of the first application; the first application server is the server associated with the first application.

[0258] Step S1802: Based on the information acquisition request, obtain the identification information of the sub-application of the second application from the second server.

[0259] The second application server is the server associated with the second application.

[0260] Step S1803: Send the identification information of the sub-application of the second application to the target client so that the target client can display the identification information of the sub-application of the second application on the sub-application display interface.

[0261] In some embodiments, the aforementioned information acquisition request may be a workbench data acquisition request, which carries the identification information of the target account. When the first application server receives the workbench data acquisition request from the client of the first application, it locates the storage area corresponding to the workbench of the target account in the database of the first application server or the database corresponding to the first application server based on the identification information of the target account in the workbench data acquisition request. The server then sends the data stored in the storage area corresponding to the workbench of the target account to the client of the first application, including the identification information of the sub-applications in the workbench of the account group to which the target account belongs and the identification information of the sub-applications added to the workbench by the user corresponding to the target account.

[0262] In other embodiments, the aforementioned information retrieval request may be a sub-application search request. Based on the information retrieval request, the identification information of the sub-applications of the second application is retrieved from the second server, including:

[0263] Forward the sub-application search request to the second application server; the sub-application search request contains key search information;

[0264] Receive search result data returned by the second application server; the search result data is obtained by the second application server based on the search key information in the sub-application search request; the search result data includes at least one sub-application identification information;

[0265] Send the identification information of the sub-application of the second application to the target client, including:

[0266] Send search result data to the target client.

[0267] In an optional embodiment, the search result data includes the identification information and offset information of a number of sub-applications limited by pagination control information; the pagination control information is used to limit the maximum number of sub-application identification information included in the search result data returned by the second application server each time; the offset information is the position identifier of the first sub-application identification information included in the search result corresponding to the search key information but not included in the search result data; the search result corresponding to the search key information is the search result obtained by the first application server based on the search key information; the information retrieval request is a supplementary search result request; after sending the identification information of the sub-applications of the second application to the target client, the above method further includes:

[0268] The supplementary search result request received from the target client is sent to the second application server; the supplementary search result request contains key search information and offset information.

[0269] Supplementary search data is returned to the target client so that the target client can display the identification information of the sub-application of the second application in the supplementary search data on the sub-application display interface; the supplementary search data is obtained by the second application server from the search results corresponding to the search key information based on the offset information, after receiving the supplementary search result request forwarded by the first application server, and then sending it to the first application server.

[0270] In other embodiments, the information retrieval request may be a sub-application recommendation list retrieval request; based on the information retrieval request, obtaining the identification information of the sub-applications of the second application from the second server includes:

[0271] Based on the sub-application recommendation list retrieval request sent by the target client, a sub-application recommendation list retrieval message is sent to the second application server; the sub-application recommendation list retrieval request contains the identification information of the target account; the sub-application recommendation list retrieval message contains the identification information of the associated account corresponding to the target account; the associated account is the account of the second application;

[0272] Receive the list of sub-applications used within a set time period returned by the second application server; the list of sub-applications used within a set time period is obtained by the second application server based on the identification information of the associated account, and includes the identification information of at least one sub-application sorted by the most recent startup time.

[0273] Send the identification information of the sub-application of the second application to the target client, including:

[0274] Send a list of sub-applications to the target client for a set time period.

[0275] In one optional embodiment, the first application is a team instant messaging application, the second application is a personal instant messaging application, and the method further includes:

[0276] Receive a sub-application add request sent by the target client; the sub-application add request contains the identification information of the target sub-application to be added to the quick access area of ​​the target account; the target account is the account associated with the target client;

[0277] Based on the identification information of the target sub-application in the sub-application addition request, the target sub-application is added to the storage area corresponding to the quick access area of ​​the target account, and a notification of successful addition of the sub-application is returned to the target client.

[0278] In one optional embodiment, the above method includes:

[0279] Receive the launch event for the sub-application sent by the target client;

[0280] If the target sub-application corresponding to the start sub-application event is included in the list of faulty sub-applications, an interception notification to interrupt the start of the target sub-application is sent to the target client, along with information that the target sub-application is included in the list of faulty sub-applications; the list of faulty sub-applications includes sub-applications that are used in the first application server and are experiencing failures.

[0281] If the target sub-application corresponding to the launch sub-application event is not included in the list of faulty sub-applications, then the information of the launch sub-application event is recorded.

[0282] In the above embodiments, the control method for running sub-applications across applications executed by the first application server, such as... Figure 19 As shown, the following steps may be included:

[0283] Step S1901: Receive an information retrieval message request sent by the first application server to obtain the identification information of the sub-application of the second application.

[0284] The information retrieval message request is a message request generated by the first application server based on the information retrieval request sent by the target client of the first application; the first application server is the server associated with the first application; the second application server is the server associated with the second application.

[0285] Step S1902: Obtain the identification information of the sub-application that made the message request from the sub-application of the second application and send it to the first application server, so that the first application server sends the identification information of the sub-application of the second application to the target client.

[0286] In one optional embodiment, the above method includes:

[0287] Based on the information retrieval request forwarded by the first application server, the identification information of the sub-application of the second application is obtained; the information retrieval request is sent by the first application server to the second application server after the target client sends it to the first application server, and is used to indicate the information retrieval request to obtain the identification information of the sub-application of the second application.

[0288] Send the identification information of the sub-application of the second application to the second application server, so that the second application server forwards the identification information of the sub-application of the second application to the target client after receiving it.

[0289] In some embodiments, the information retrieval message may be a sub-application search request, which includes key search information; retrieving the identification information of the sub-application requesting the information retrieval message from the sub-application of the second application and sending it to the first application server includes:

[0290] The search results data are obtained by searching the sub-application database of the second application based on the search keywords in the sub-application search request.

[0291] The search results data is sent to the first application server; the search results data includes the identification information of at least one sub-application.

[0292] In an optional embodiment, the search result data includes the identification information and offset information of a number of sub-applications limited by pagination control information; the pagination control information is used to limit the maximum number of sub-application identification information included in the search result data returned by the second application server each time; the offset information is the position identifier of the first sub-application identification information included in the search result corresponding to the search key information but not included in the search result data; the search result corresponding to the search key information is the search result obtained by the first application server based on the search key information; the information retrieval request is a supplementary search result request; after sending the search result data to the first application server, the above method further includes:

[0293] Receive a supplementary search result request sent by the first application server; the supplementary search result request contains key search information and offset information;

[0294] Supplementary search data is obtained from the search results corresponding to the search keywords based on the offset information in the supplementary search results request;

[0295] The supplementary search data will be sent to the first application server.

[0296] In an optional embodiment, the information retrieval message may be a sub-application recommendation list retrieval message, which contains the identification information of the associated account corresponding to the target account; the target account is the target account associated with the target client; retrieving the identification information of the sub-application requesting the information retrieval message from the sub-application information of the second application and sending it to the first application server includes:

[0297] Based on the identification information of the associated account in the sub-application recommendation list, obtain the list of sub-applications used by the associated account within a set time period. The list of sub-applications used within the set time period includes the identification information of at least one sub-application sorted by the most recent launch time.

[0298] Send the list of sub-applications used by the associated account within the specified time period to the first application server.

[0299] Based on the same inventive concept, this application also provides a control device for running sub-applications across applications, which can be deployed in a terminal device. Since this device corresponds to the control method for running sub-applications across applications applied to the client of the first application in this application, and the principle of solving the problem by this device is similar to that of the method, the implementation of this device can refer to the implementation process of the above method embodiments, and repeated details will not be elaborated further.

[0300] Figure 20This illustration shows a schematic diagram of a control device for running sub-applications across applications, according to an embodiment of this application. This control device for running sub-applications across applications is applied to the client of a first application, such as... Figure 20 As shown, it includes: a sub-application display unit 2001 and a sub-application launch unit 2002; wherein,

[0301] The sub-application display unit 2001 is used to display the sub-application display interface in response to a trigger operation that the target account opens the sub-application display interface. The sub-application display interface displays the identification information of the sub-application. The sub-application includes the sub-application of the second application. The identification information of the sub-application of the second application is obtained by the first application server associated with the first application from the second application server associated with the second application and sent to the client of the first application.

[0302] The sub-application startup unit 2002 is used to respond to the startup operation of the target sub-application triggered by the identification information of the target sub-application in the sub-application of the second application, obtain the data of the target sub-application from the second application server, and display the running interface of the target sub-application based on the data of the target sub-application.

[0303] In an optional embodiment, the sub-application display unit 2001 is further configured to:

[0304] In response to a sub-application search operation triggered by a target account through the sub-application display interface, a sub-application search request is sent to the first application server. The sub-application search request includes search key information corresponding to the sub-application search operation, so that the first application server can send the sub-application search request to the second application server when the target account is searching for a sub-application of the second application based on the search key information.

[0305] The system receives search result data returned by the first application server and displays the identification information of the sub-application of the second application in the search result data on the sub-application display interface. The search result data is obtained by the second application server based on the search key information after receiving the sub-application search request forwarded by the first application server and sending it to the first application server.

[0306] In an optional embodiment, the search result data includes the identification information and offset information of a number of sub-applications limited by pagination control information; the pagination control information is used to limit the maximum number of sub-application identification information items included in the search result data returned by the second application server each time; the offset information is the position identifier of the first sub-application identification information item included in the search result corresponding to the search key information but not included in the search result data; the search result corresponding to the search key information is the search result obtained by the first application server based on the search key information; the sub-application display unit 2001 is further used for:

[0307] In response to a sub-application supplementary search result operation triggered by the target account through the sub-application display interface, a supplementary search result request is sent to the first application server, so that the first application server sends the supplementary search result request to the second application server; the supplementary search result request contains search key information and offset information;

[0308] The system receives supplementary search data returned by the first application server and displays the identification information of the second application's sub-application in the supplementary search data on the sub-application display interface. The supplementary search data is obtained by the second application server from the search results corresponding to the search key information based on the offset information, after receiving the supplementary search result request forwarded by the first application server, and then sending it to the first application server.

[0309] In an optional embodiment, the sub-application display unit 2001 is further configured to:

[0310] In response to the target account's request to retrieve the sub-application recommendation list triggered by the sub-application display interface, a sub-application recommendation list retrieval request is sent to the first application server; the sub-application recommendation list retrieval request contains the target account's identification information;

[0311] Receive a list of sub-applications used within a set time period corresponding to the target account, returned by the first application server based on the target account's identification information; the list of sub-applications used within the set time period includes the identification information of at least one sub-application sorted by its most recent launch time;

[0312] The sub-application display interface shows the identification information of the sub-applications in the list of sub-applications used within a set time period.

[0313] In one optional embodiment, the sub-application recommendation list retrieval request instructs the retrieval of sub-applications launched by the target account within a set time period; the sub-application list used within the set time period includes identification information of the sub-applications launched by the target account within the set time period; or

[0314] The sub-application recommendation list retrieval request instructs the user to retrieve sub-applications launched by each account in the account group associated with the target account within a specified time period; the sub-applications used within the specified time period list includes the identifiers of sub-applications launched by each account in the account group associated with the target account within the specified time period; the identifiers of the sub-applications in the sub-applications used within the specified time period are sorted by the number of accounts that used each sub-application within the specified time period and the most recent launch time; or

[0315] The list of sub-applications used within a set time period includes the identifier information of sub-applications launched by the associated account of the target account within the set time period in the second application; the associated account is the account of the second application.

[0316] In an optional embodiment, the sub-application launch unit 2002 is specifically used for:

[0317] In response to the operation of launching the target sub-application, a launch sub-application event is sent to the first application server;

[0318] If an interception notification is received from the first application server, the startup of the target sub-application is interrupted, and information about the target sub-application being included in the list of faulty sub-applications is displayed.

[0319] If no interception notification is received from the first application server, the data of the target sub-application is obtained from the second application server, and the running interface of the target sub-application is displayed based on the data of the target sub-application.

[0320] Based on the same inventive concept, this application also provides another control device for running sub-applications across applications, which is deployed in the first application server. Since this device corresponds to the control method for running sub-applications across applications applied to the first application server in this application embodiment, and the principle by which this device solves the problem is similar to that of the method, the implementation of this device can refer to the implementation process of the above-described method embodiments, and repeated details will not be elaborated further.

[0321] Figure 21 This illustration shows a schematic diagram of another control device for running sub-applications across applications, provided in an embodiment of this application. This control device is applied to a first application server, such as... Figure 21 As shown, it includes: a first request receiving unit 2101, a first request response unit 2102, and a first request feedback unit 2103; wherein,

[0322] The first request receiving unit 2101 is used to receive an information acquisition request sent by the target client, which indicates that the identification information of the sub-application of the second application is to be obtained; the target client is the client of the first application; the first application server is the server associated with the first application;

[0323] The first request response unit 2102 is used to obtain the identification information of the sub-application of the second application from the second server according to the information acquisition request; the second application server is the server associated with the second application.

[0324] The first request feedback unit 2103 is used to send the identification information of the sub-application of the second application to the target client so that the target client can display the identification information of the sub-application of the second application on the sub-application display interface.

[0325] In an optional embodiment, the information retrieval request is a sub-application search request; the first request response unit 2102 is specifically used for:

[0326] Forward the sub-application search request to the second application server; the sub-application search request contains key search information;

[0327] Receive search result data returned by the second application server; the search result data is obtained by the second application server based on the search key information in the sub-application search request; the search result data includes at least one sub-application identification information;

[0328] The first request feedback unit 2103 is specifically used for:

[0329] Send search result data to the target client.

[0330] In an optional embodiment, the information retrieval request is a sub-application recommendation list retrieval request; the first request response unit 2102 is specifically used for:

[0331] Based on the sub-application recommendation list retrieval request sent by the target client, a sub-application recommendation list retrieval message is sent to the second application server; the sub-application recommendation list retrieval request contains the identification information of the target account; the sub-application recommendation list retrieval message contains the identification information of the associated account corresponding to the target account; the associated account is the account of the second application;

[0332] Receive the list of sub-applications used within a set time period returned by the second application server; the list of sub-applications used within a set time period is obtained by the second application server based on the identification information of the associated account, and includes the identification information of at least one sub-application sorted by the most recent startup time.

[0333] The first request feedback unit 2103 is specifically used for:

[0334] Send a list of sub-applications to the target client for a set time period.

[0335] In one optional embodiment, the first application is a team instant messaging application, the second application is a personal instant messaging application, and the first request receiving unit 2101 is further configured to:

[0336] Receive a sub-application add request sent by the target client; the sub-application add request contains the identification information of the target sub-application to be added to the quick access area of ​​the target account; the target account is the account associated with the target client.

[0337] The first request response unit 2102 is further configured to: add the target sub-application to the storage area corresponding to the shortcut area of ​​the target account based on the identification information of the target sub-application in the sub-application add request.

[0338] The first request feedback unit 2103 is also used to return a success notification of adding the sub-application to the target client.

[0339] Based on the same inventive concept, this application also provides another control device for running sub-applications across applications, which is deployed in a second application server. Since this device corresponds to the control method for running sub-applications across applications applied to a second application server in this application embodiment, and the principle by which this device solves the problem is similar to that of the method, the implementation of this device can refer to the implementation process of the embodiments of the above method; repeated details will not be elaborated further.

[0340] Figure 22 This illustration shows a schematic diagram of another control device for running sub-applications across applications, provided in an embodiment of this application. This control device is applied to a second application server, such as... Figure 22 As shown, it includes: a second request receiving unit 2201 and a second request response unit 2202; wherein,

[0341] The second request receiving unit 2201 is used to receive an information acquisition request sent by the first application server to obtain the identification information of the sub-application of the second application; the information acquisition request is an information acquisition request sent by the target client of the first application received by the first application server; the first application server is a server associated with the first application; the second application server is a server associated with the second application.

[0342] The second request response unit 2202 is used to obtain information from the sub-application of the second application, obtain the identification information of the sub-application requesting the message, and send it to the first application server, so that the first application server sends the identification information of the sub-application of the second application to the target client.

[0343] In an optional embodiment, the information acquisition message is a sub-application search request, which contains key search information; the second request response unit 2202 is specifically used for:

[0344] The search results data are obtained by searching the sub-application database of the second application based on the search keywords in the sub-application search request.

[0345] The search results data is sent to the first application server; the search results data includes the identification information of at least one sub-application.

[0346] In an optional embodiment, the information retrieval message is a sub-application recommendation list retrieval message, which contains the identification information of the associated account corresponding to the target account; the target account is the target account associated with the target client; the second request response unit 2202 is specifically used for:

[0347] Based on the identification information of the associated account in the sub-application recommendation list, obtain the list of sub-applications used by the associated account within a set time period. The list of sub-applications used within the set time period includes the identification information of at least one sub-application sorted by the most recent launch time.

[0348] Send the list of sub-applications used by the associated account within the specified time period to the first application server.

[0349] Based on the same inventive concept, this application also provides an electronic device. In one embodiment, the electronic device may be a terminal device associated with the client of the first application, such as... Figure 1 The terminal device 100 is shown. In this embodiment, the electronic device can be structured as follows: Figure 23 As shown, it includes components such as: communication component 210, memory 220, display unit 230, camera 240, sensor 250, audio circuit 260, Bluetooth module 270, and processor 280.

[0350] The communication component 210 is used to communicate with the server. In some embodiments, it may include a Wi-Fi (Wireless Fidelity) module, which is a short-range wireless transmission technology. Electronic devices can use the Wi-Fi module to help users send and receive information.

[0351] The memory 220 can be used to store software programs and data. The processor 280 executes various functions of the terminal device 100 and performs data processing by running the software programs or data stored in the memory 220. The memory 220 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. The memory 220 stores the operating system that enables the terminal device 100 to run. In this application, the memory 220 may store the operating system and various applications, and may also store code for executing the control method for running sub-applications across applications according to the embodiments of this application.

[0352] The display unit 230 can also be used to display information input by the user or information provided to the user, as well as various menus of the terminal device 100, in a graphical user interface (GUI). Specifically, the display unit 230 may include a display screen 232 disposed on the front of the terminal device 100. The display screen 232 may be configured as a liquid crystal display, a light-emitting diode, or the like. The display unit 230 can be used to display payment interfaces, etc., as shown in the embodiments of this application.

[0353] The display unit 230 can also be used to receive input digital or character information and generate signal inputs related to user settings and function control of the terminal device 100. Specifically, the display unit 230 may include a touch screen 231 disposed on the front of the terminal device 100, which can collect touch operations of the user on or near it, such as clicking a button, dragging a scroll box, etc.

[0354] The touchscreen 231 can be placed over the display screen 232, or the touchscreen 231 and the display screen 232 can be integrated to realize the input and output functions of the terminal device 100. After integration, it can be referred to as a touch display screen. In this application, the display unit 230 can display the application program and the corresponding operation steps.

[0355] Camera 240 can be used to capture still images, which users can then send to a backend server or other game users via a cloud gaming client. There can be one or multiple cameras 240. An object is projected onto a photosensitive element through a lens, generating an optical image. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then transmitted to a processor 280 to be converted into a digital image signal.

[0356] The terminal device may also include at least one sensor 250, such as an accelerometer 251, a proximity sensor 252, a fingerprint sensor 253, and a temperature sensor 254. The terminal device may also be equipped with other sensors such as a gyroscope, barometer, hygrometer, thermometer, infrared sensor, light sensor, and motion sensor.

[0357] Audio circuitry 260, speaker 261, and microphone 262 provide an audio interface between the user and terminal device 100. Audio circuitry 260 converts received audio data into electrical signals, which are then transmitted to speaker 261, where they are converted into sound signals for output. Terminal device 100 may also be equipped with volume buttons for adjusting the volume of the sound signal. Conversely, microphone 262 converts collected sound signals into electrical signals, which are received by audio circuitry 260, converted into audio data, and then output to communication component 210 for transmission to, for example, another terminal device 100, or to memory 220 for further processing.

[0358] Bluetooth module 270 is used to exchange information with other Bluetooth devices that also have Bluetooth modules via the Bluetooth protocol. For example, a terminal device can establish a Bluetooth connection with a wearable electronic device that also has a Bluetooth module through Bluetooth module 270, thereby exchanging data.

[0359] The processor 280 is the control center of the terminal device, connecting various parts of the terminal through various interfaces and lines. It executes software programs stored in the memory 220 and calls data stored in the memory 220 to perform various functions and process data. In some embodiments, the processor 280 may include one or more processing units; the processor 280 may also integrate an application processor and a baseband processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the baseband processor mainly handles wireless communication. It is understood that the baseband processor may not be integrated into the processor 280. In this application, the processor 280 can run the operating system, applications, user interface display and touch response, as well as the cross-application sub-application control method of this embodiment. Furthermore, the processor 280 is coupled to the display unit 230.

[0360] In another embodiment, the electronic device may be a server, such as... Figure 1 The first application server 200 or the first application server 300 shown. In this embodiment, the structure of the electronic device can be as follows: Figure 24 As shown, it includes a memory 1501, a communication module 1503, and one or more processors 1502.

[0361] The memory 1501 is used to store computer programs executed by the processor 1502. The memory 1501 may mainly include a program storage area and a data storage area. The program storage area may store the operating system and programs required to run game functions, etc.; the data storage area may store various game information and operation instruction sets, etc.

[0362] Memory 1501 may be volatile memory, such as random-access memory (RAM); memory 1501 may also be non-volatile memory, such as read-only memory, flash memory, hard disk drive (HDD), or solid-state drive (SSD); memory 1501 is any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. Memory 1501 may be a combination of the above-described memories.

[0363] Processor 1502 may include one or more central processing units (CPUs) or digital processing units, etc. Processor 1502 is used to implement the above-described control method for running sub-applications across applications when calling computer programs stored in memory 1501.

[0364] The communication module 1503 is used to communicate with other terminal devices or back-end servers.

[0365] This application does not limit the specific connection medium between the memory 1501, the communication module 1503, and the processor 1502 as described above. This disclosure embodiment... Figure 24 The memory 1501 and the processor 1502 are connected via a bus 1504, and the bus 1504 is in Figure 24 The connections between other components are shown in bold lines only and are not intended to be limiting. The 1504 bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 24 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0366] The memory 1501 stores a computer storage medium, which stores computer-executable instructions for implementing the cross-application running sub-application control method of this application embodiment. The processor 1502 is used to execute the above-described cross-application running sub-application control method.

[0367] This application also provides a computer storage medium storing computer-executable instructions for implementing the control method for running sub-applications across applications according to any embodiment of this application.

[0368] In some possible implementations, various aspects of the cross-application sub-application control method provided in this application can also be implemented as a program product, which includes program code. When the program product is run on a computer device, the program code is used to cause the computer device to perform the steps of the cross-application sub-application control method according to the various exemplary embodiments of this application described above. For example, the computer device can perform actions such as... Figure 17 The flowchart of the control method for cross-application running sub-applications shown in steps S1701 to S1702 can be executed as follows; or, the following can be executed: Figure 18 The flowchart of the control method for cross-application running sub-applications shown in steps S1801 to S1803 can be executed as follows: Figure 19 The flowchart shows the control method for cross-application running sub-applications in steps S1901 to S1903.

[0369] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0370] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A control method for running sub-applications across applications, characterized in that, The method, applied to a client of the first application, includes: In response to a triggering operation that the target account opens the sub-application display interface, the sub-application display interface is displayed, and the sub-application display interface displays the identification information of the sub-application; the sub-application includes a sub-application of the second application; the identification information of the sub-application of the second application is obtained by the first application server associated with the first application from the second application server associated with the second application and sent to the client of the first application; In response to a sub-application search operation triggered by a target account through the sub-application display interface, a sub-application search request including search key information corresponding to the sub-application search operation is sent to the first application server. Additionally, the search results data returned by the first application server is received, and the identification information of the sub-application of the second application in the search results data is displayed on the sub-application display interface. The search results data is obtained by the second application server based on the search key information after receiving the sub-application search request forwarded by the first application server, and then sent to the first application server. The search results data includes identification information and offset information of a number of sub-applications limited by pagination control information. The offset information is the position identifier of the first sub-application identification information included in the search results corresponding to the search key information but not included in the search results data. In response to a sub-application supplementary search result operation triggered on the sub-application display interface, a supplementary search result request is sent to the first application server, the supplementary search result request including the search key information and the offset information; The system receives supplementary search data returned by the first application server and displays the identification information of the sub-application of the second application in the supplementary search data on the sub-application display interface. The supplementary search data is obtained by the second application server from the search results corresponding to the search key information based on the offset information and sent to the first application server after receiving the supplementary search result request forwarded by the first application server. In response to a target sub-application launch operation triggered by the identification information of the target sub-application in a sub-application of the second application, data of the target sub-application is obtained from the second application server, and the running interface of the target sub-application is displayed based on the data of the target sub-application.

2. The method according to claim 1, characterized in that, Prior to the launch of the target sub-application triggered by the identification information of the target sub-application in a sub-application of the second application, the method further includes: In response to a sub-application recommendation list retrieval operation triggered by a target account through the sub-application display interface, a sub-application recommendation list retrieval request is sent to the first application server; the sub-application recommendation list retrieval request contains the identification information of the target account; The system receives a list of sub-applications used within a set time period corresponding to the target account, returned by the first application server based on the target account's identification information; the list of sub-applications used within the set time period includes identification information of at least one sub-application sorted by its most recent launch time. The identification information of the sub-applications in the sub-application list used within the set time period is displayed on the sub-application display interface.

3. The method according to claim 2, characterized in that, The sub-application recommendation list retrieval request indicates the retrieval of sub-applications launched by the target account within a set time period; the sub-application list used within the set time period includes the identification information of the sub-applications launched by the target account within the set time period; or The sub-application recommendation list retrieval request indicates the retrieval of sub-applications launched by each account in the account group associated with the target account within a set time period; the sub-applications used within the set time period list includes the identification information of sub-applications launched by each account in the account group associated with the target account within the set time period; the identification information of the sub-applications in the sub-applications used within the set time period list is sorted according to the number of accounts that used each sub-application within the set time period and the most recent launch time; or The list of sub-applications used within the set time period includes the identification information of sub-applications launched by the associated account of the target account within the set time period in the second application; the associated account is the account of the second application.

4. The method according to claim 1, characterized in that, The first application is a team instant messaging application, and the second application is a personal instant messaging application; the method further includes: In response to the target account's operation of adding a sub-application to the quick access area in the target sub-application's running interface, a sub-application add request is sent to the first application server; the sub-application add request contains the identification information of the target sub-application; Upon receiving a notification from the first application server indicating that the sub-application has been successfully added, the system displays information indicating that the target sub-application has been added to the quick access area.

5. A control method for running sub-applications across applications, characterized in that, Applied to a first application server, the method includes: The system receives a sub-application search request sent by a target client, instructing the user to obtain the identification information of a sub-application of a second application; the target client is a client of a first application; the first application server is a server associated with the first application; the sub-application search request contains key search information. The system forwards the sub-application search request to the second application server and receives the search result data returned by the second application server. The second application server is the server associated with the second application. The search result data is obtained by the second application server based on the search key information in the sub-application search request. The search result data includes the identification information and offset information of a number of sub-applications limited by pagination control information. The offset information is the position identifier of the first sub-application identification information that is included in the search results corresponding to the search key information but not included in the search result data. The search results data are sent to the target client so that the target client displays the search results data on the sub-application display interface; The supplementary search result request received from the target client is sent to the second application server; the supplementary search result request includes the search key information and the offset information; Supplementary search data is returned to the target client so that the target client displays the identification information of the sub-application of the second application in the supplementary search data on the sub-application display interface; the supplementary search data is obtained by the second application server from the search results corresponding to the search key information based on the offset information and sent to the first application server.

6. A control method for running sub-applications across applications, characterized in that, Applied to a second application server, the method includes: The system receives a sub-application search request from a first application server to obtain the identification information of a sub-application of a second application; the sub-application search request is a sub-application search request sent by a target client of the first application received by the first application server, and the sub-application search request includes key search information; the first application server is a server associated with the first application; the second application server is a server associated with the second application. The search is performed based on the search key information in the sub-application search request, and the obtained search result data is sent to the first application server so that the first application server sends the search result data to the target client. The search result data includes the identification information and offset information of a number of sub-applications limited by pagination control information. The offset information is the position identifier of the first sub-application identification information that is included in the search results corresponding to the search key information but not included in the search result data. The system receives a supplementary search result request sent by the target client and forwarded by the first application server. The supplementary search result request includes the search key information and the offset information. Based on the offset information, the system obtains supplementary search data from the search results corresponding to the search key information. The supplementary search data is returned to the first application server, so that the first application server forwards the supplementary search data to the target client, so that the target client displays the identification information of the sub-application of the second application in the supplementary search data on the sub-application display interface.

7. A control device for running sub-applications across applications, characterized in that, The device, used in a client application of the first application, includes: The sub-application display unit is used to display the sub-application display interface in response to a trigger operation that opens the sub-application display interface by a target account. The sub-application display interface displays the identification information of the sub-application. The sub-application includes a sub-application of a second application. The identification information of the sub-application of the second application is obtained by the first application server associated with the first application from the second application server associated with the second application and sent to the client of the first application. In response to a sub-application search operation triggered by a target account through the sub-application display interface, a sub-application search request including search key information corresponding to the sub-application search operation is sent to the first application server. Additionally, the search results data returned by the first application server is received, and the identification information of the sub-application of the second application in the search results data is displayed on the sub-application display interface. The search results data is obtained by the second application server from the sub-application search request forwarded by the first application server, based on the search key information, and sent to the first application server. It includes the identification information and offset information of a number of sub-applications limited by pagination control information. The offset information is the position identifier of the first sub-application identification information included in the search results corresponding to the search key information but not included in the search results data. In response to a sub-application supplementary search result operation triggered on the sub-application display interface, a supplementary search result request is sent to the first application server, the supplementary search result request including the search key information and the offset information; The system receives supplementary search data returned by the first application server and displays the identification information of the sub-application of the second application in the supplementary search data on the sub-application display interface. The supplementary search data is obtained by the second application server from the search results corresponding to the search key information based on the offset information and sent to the first application server after receiving the supplementary search result request forwarded by the first application server. The sub-application launch unit is used to respond to the launch operation of the target sub-application triggered by the identification information of the target sub-application in the sub-application of the second application, obtain the data of the target sub-application from the second application server, and display the running interface of the target sub-application based on the data of the target sub-application.

8. A control device for running sub-applications across applications, characterized in that, The device, applied to a first application server, includes: The first request receiving unit is configured to receive a sub-application search request sent by a target client, indicating that the target client is a client of the first application; the first application server is a server associated with the first application; and the sub-application search request contains key search information. The first request response unit is configured to forward the sub-application search request to the second application server and receive the search result data returned by the second application server; the second application server is a server associated with the second application, and the search result data is obtained by the second application server based on the search key information in the sub-application search request; the search result data includes the identification information and offset information of a number of sub-applications limited by pagination control information, and the offset information is the position identifier of the first sub-application identification information included in the search results corresponding to the search key information but not included in the search result data; The first request feedback unit is used to send the search result data to the target client so that the target client displays the search result data on the sub-application display interface; The first request response unit is further configured to send the received supplementary search result request from the target client to the second application server; the supplementary search result request includes the search key information and the offset information; The first request feedback unit is further configured to return supplementary search data to the target client, so that the target client displays the identification information of the sub-application of the second application in the supplementary search data on the sub-application display interface; the supplementary search data is obtained by the second application server from the search results corresponding to the search key information based on the offset information and sent to the first application server.

9. A control device for running sub-applications across applications, characterized in that, The device, applied to a second application server, includes: The second request receiving unit is configured to receive a sub-application search request sent by the first application server to obtain the identification information of a sub-application of the second application; the sub-application search request is a sub-application search request sent by the target client of the first application received by the first application server, and the sub-application search request includes key search information; the first application server is a server associated with the first application; the second application server is a server associated with the second application. The second request response unit is used to perform a search based on the search key information in the sub-application search request, and send the obtained search result data to the first application server so that the first application server sends the obtained search result data to the target client. The search result data includes the identification information and offset information of a number of sub-applications limited by pagination control information. The offset information is the position identifier of the first sub-application identification information that is included in the search results corresponding to the search key information but not included in the search result data. The second request receiving unit is further configured to receive a supplementary search result request sent by the target client and forwarded by the first application server, wherein the supplementary search result request includes the search key information and the offset information; The second request response unit is further configured to obtain supplementary search data from the search results corresponding to the search key information based on the offset information; The supplementary search data is returned to the first application server, so that the first application server forwards the supplementary search data to the target client, so that the target client displays the identification information of the sub-application of the second application in the supplementary search data on the sub-application display interface.

10. A computer-readable storage medium storing a computer program therein, characterized in that: When the computer program is executed by a processor, it implements the method of any one of claims 1 to 4, the method of claim 5, or the method of claim 6.

11. An electronic device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program that can run on the processor, and when the computer program is executed by the processor, it implements the method of any one of claims 1 to 4, the method of claim 5, or the method of claim 6.

Images