Micro-end generation method and apparatus, computer device, and storage medium

Abstract

The present disclosure provides a micro-end generation method and apparatus, a computer device, and a storage medium. When applied to a client side, the method comprises: in response to a micro-end acquisition request for a plurality of sub-applications in an application program, acquiring sub-application micro-ends respectively corresponding to the plurality of sub-applications; displaying the plurality of sub-application micro-ends on a terminal interface of the client side; and in response to a trigger operation for a target sub-application micro-end among the plurality of sub-application micro-ends, starting the application program, and displaying in the application program a display interface of a target sub-application corresponding to the target sub-application micro-end, wherein the target sub-application micro-end is any one of the plurality of sub-application micro-ends.

Description

Micro-terminal generation method, device, computer equipment and storage medium

[0001] This application claims priority to Chinese Patent Application No. 202311159628.1 filed on September 8, 2023, and the contents of the above-mentioned Chinese patent application disclosure are hereby incorporated by reference in their entirety as a part of this application. Technical Field

[0002] The present disclosure relates to a micro-terminal generation method, apparatus, computer equipment and storage medium. Background Art

[0003] With the development of technology, applications have more and more sub-services. This can lead to a problem of deep entry points for these sub-services, requiring users to perform multiple operations within the application to find the corresponding sub-service. To alleviate this problem, sub-services can be added to desktop shortcuts to access them.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure at least provide a micro-terminal generation method, apparatus, computer equipment and storage medium.

[0006] In a first aspect, an embodiment of the present disclosure provides a method for generating a micro-client, which is applied to a user terminal and includes:

[0007] In response to micro-client acquisition requests for multiple sub-applications in the application, acquire sub-application micro-clients corresponding to the multiple sub-applications respectively;

[0008] Displaying multiple sub-application micro-clients on the terminal interface of the user terminal;

[0009] In response to a triggering operation on a target sub-application micro-terminal among the multiple sub-application micro-terminals, the application is started, and the display interface of the target sub-application corresponding to the target sub-application micro-terminal is displayed in the application; wherein the target sub-application micro-terminal is any sub-application micro-terminal among the multiple sub-application micro-terminals.

[0010] In a second aspect, an embodiment of the present disclosure further provides a micro-client generation method, which is applied to a server and includes:

[0011] In response to a micro-client generation operation for at least one sub-application in an application, obtaining a first parameter corresponding to the application and a second parameter corresponding to each of the sub-applications;

[0012] Generate a sub-application micro-terminal corresponding to the sub-application based on the first parameter, the second parameter of each sub-application, and the constructed micro-terminal code module;

[0013] The sub-application micro-client corresponding to the sub-application is stored.

[0014] In a third aspect, the present disclosure also provides a micro-terminal generation device, which is applied to a user terminal and includes:

[0015] A first acquisition module is configured to respond to micro-client acquisition requests for multiple sub-applications in an application program and acquire sub-application micro-clients corresponding to the multiple sub-applications respectively;

[0016] A display module, configured to display multiple sub-application micro-clients on the terminal interface of the user terminal;

[0017] The startup module is used to start the application in response to a trigger operation on a target sub-application micro-client among the multiple sub-application micro-clients, and to display a display interface of the target sub-application corresponding to the target sub-application micro-client in the application.

[0018] In a fourth aspect, an embodiment of the present disclosure further provides a micro-client generation device, which is applied to a server and includes:

[0019] A second acquisition module is configured to, in response to a micro-client generation operation for at least one sub-application in the application, acquire a first parameter corresponding to the application and a second parameter corresponding to each of the sub-applications;

[0020] A generation module, configured to generate a sub-application micro-terminal corresponding to the sub-application based on the first parameter, the second parameter of each sub-application, and the constructed micro-terminal code module;

[0021] The storage module is used to store the sub-application micro-terminal corresponding to the sub-application.

[0022] In a fifth aspect, an embodiment of the present disclosure further provides a computer device, comprising: a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the steps of the above-mentioned first aspect, or any possible implementation of the first aspect, or the steps of the above-mentioned second aspect, or any possible implementation of the second aspect are executed.

[0023] In a sixth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the processor executes the steps of the above-mentioned first aspect, or any possible implementation of the first aspect, or executes the above-mentioned second aspect, or any possible implementation of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the embodiments. The drawings herein are incorporated into and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and, together with the specification, are used to illustrate the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure and should not be regarded as limiting the scope. For those of ordinary skill in the art, other relevant drawings can be obtained based on these drawings without inventive effort.

[0025] FIG1 shows a flow chart of a micro-terminal generation method provided by an embodiment of the present disclosure;

[0026] FIG2 shows a schematic diagram of a terminal interface in the micro-terminal generation method provided by an embodiment of the present disclosure;

[0027] FIG3a shows a schematic diagram of a terminal interface in the micro-terminal generation method provided by an embodiment of the present disclosure;

[0028] FIG3 b shows a schematic diagram of a terminal interface in the micro-terminal generation method provided by an embodiment of the present disclosure;

[0029] FIG4 shows a schematic diagram of a terminal interface in the micro-terminal generation method provided by an embodiment of the present disclosure;

[0030] FIG5 is a flow chart showing the processing logic of a target sub-application micro-terminal including a shortcut function in the micro-terminal generation method provided by an embodiment of the present disclosure;

[0031] FIG6 shows a flowchart of another micro-terminal generation method provided by an embodiment of the present disclosure;

[0032] FIG7 shows a schematic structural diagram of a micro-terminal generating device provided by an embodiment of the present disclosure;

[0033] FIG8 shows a schematic structural diagram of another micro-terminal generating device provided by an embodiment of the present disclosure;

[0034] FIG9 shows a schematic structural diagram of a computer device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] In order to make the purpose, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. The components of the embodiments of the present disclosure generally described and shown in the drawings herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure provided in the drawings is not intended to limit the scope of the disclosure for which protection is sought, but merely represents selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of the present disclosure.

[0036] With the development of technology, applications have an increasing number of sub-services. These sub-services often have a deep entry point problem, requiring users to perform multiple operations within the application to find the corresponding sub-service. To alleviate this problem, sub-services can be added as desktop shortcuts to access them. However, this approach has compatibility issues between sub-services and desktop systems, resulting in sub-services being unable to start after being added to the desktop, reducing the efficiency of sub-service usage.

[0037] Based on this, the present disclosure provides a micro-terminal generation method, device, computer equipment and storage medium, which obtains sub-application micro-terminals corresponding to multiple sub-applications respectively in response to trigger operations for multiple sub-applications in an application, and displays multiple sub-application micro-terminals on the terminal interface of the user terminal, thereby realizing the creation of multiple sub-application micro-terminals on the terminal interface and improving the creation efficiency of sub-application micro-terminals, so that it can respond to the trigger operation for the target sub-application micro-terminal among the multiple sub-application micro-terminals, start the application, and display the display interface of the target sub-application corresponding to the target sub-application micro-terminal in the application. Here, by constructing a corresponding sub-application micro-terminal for each sub-application, after the user terminal has installed the sub-application micro-terminal, it can trigger the sub-application micro-terminal and pull up the application while directly displaying the display interface of the target sub-application, thereby realizing the use of the sub-application and improving the use efficiency of the sub-application.

[0038] At the same time, the sub-application micro-terminal in the present disclosure is used to start the application, and the application is installed on the terminal interface and is compatible with the terminal interface, so that the display interface of the target sub-application corresponding to the target sub-application micro-terminal can be displayed in the application, alleviating the sub-application startup problem caused by compatibility issues and ensuring the efficiency of sub-application use.

[0039] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, it does not need to be further defined or explained in subsequent drawings.

[0040] The term "and / or" herein simply describes an association relationship, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, the simultaneous existence of A and B, and the existence of B alone. In addition, the term "at least one" herein refers to any combination of at least two of any one or more of a plurality of items. For example, "at least one of A, B, and C" can represent any one or more elements selected from the set consisting of A, B, and C.

[0041] It is understandable that before using the technical solutions disclosed in the various embodiments of this disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved in this disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0042] For example, in response to a user's active request, a prompt message is sent to the user to clearly inform the user that the operation requested will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the electronic device, application, server, storage medium, or other software or hardware that performs the operations of the disclosed technical solution based on the prompt message.

[0043] As an optional but non-limiting implementation, in response to receiving a user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. Furthermore, the pop-up window may also contain a selection control for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0044] It is understandable that the above notification and user authorization process are merely illustrative and do not limit the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0045] To facilitate understanding of this embodiment, a micro-terminal generation method disclosed in an embodiment of the present disclosure is first introduced in detail. The execution subject of the micro-terminal generation method provided in the embodiment of the present disclosure is generally a computer device with certain computing capabilities. The computer device includes, for example: a terminal device or a server or other processing device. The terminal device can be a user equipment (UE), a mobile device, a user terminal, a personal digital assistant (PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc. In some possible implementations, the micro-terminal generation method can be implemented by a processor calling computer-readable instructions stored in a memory.

[0046] The following describes the micro-terminal generation method provided by the embodiment of the present disclosure by taking the execution subject as the user terminal as an example.

[0047] 1 is a flowchart of a method for generating a micro-client according to an embodiment of the present disclosure. The method includes steps S101 to S103, wherein:

[0048] S101, in response to micro-client acquisition requests for multiple sub-applications in an application, obtain sub-application micro-clients corresponding to the multiple sub-applications respectively.

[0049] S102, displaying multiple sub-application micro-terminals on the terminal interface of the user terminal.

[0050] S103 , in response to a triggering operation on a target sub-application micro-client among the multiple sub-application micro-clients, starting the application program and displaying a display interface of the target sub-application corresponding to the target sub-application micro-client in the application program.

[0051] S101 to S103 are described in detail below.

[0052] For S101 and S102:

[0053] An application can be any program installed on the user side. For example, multiple sub-applications can be selected in the application, micro-terminal acquisition requests for the multiple sub-applications can be initiated, and then the sub-application micro-terminals corresponding to the multiple sub-applications can be obtained in response to the micro-terminal acquisition requests for the multiple sub-applications. For example, multiple sub-applications can be selected in the sub-application directory of the application. After obtaining the sub-application micro-terminals corresponding to the multiple sub-applications, the multiple sub-application micro-terminals can be displayed on the terminal interface of the user side, wherein the micro-terminal identifier and micro-terminal name of the sub-application micro-terminal can be displayed on the terminal interface. As shown in Figure 2, Figure 2 shows multiple applications, such as calendar, weather, calculator, news, etc., and also shows multiple sub-application micro-terminals, such as micro-terminal 1, micro-terminal 2, etc., each sub-application micro-terminal includes a micro-terminal identifier 21 and a micro-terminal name 22.

[0054] Before obtaining the sub-application micro-clients corresponding to the multiple sub-applications in the application in response to micro-client acquisition requests, the method also includes: determining and displaying multiple candidate sub-applications in the application based on historical interaction data; and generating micro-client acquisition requests for the multiple sub-applications in response to triggering of multiple sub-applications in the multiple candidate sub-applications.

[0055] Historical interaction data may include operational data related to user operations within an application within a preset time period. For example, historical interaction data may include user browsing history within the application, historical browsing types, frequently used sub-applications, and so on. Historical interaction data is obtained after user authorization. The preset time period may be, for example, a week or a day. Frequently used sub-applications include sub-applications with statistically high access frequencies. For example, frequently used sub-applications may be sub-applications within a historically accessed sub-application that have been accessed more than a threshold number of times.

[0056] During implementation, multiple candidate sub-applications within an application can be determined based on historical interaction data. For example, candidate sub-applications can be determined based on frequently used sub-applications in the historical interaction data, such as determining frequently used sub-applications as candidate sub-applications, or randomly selecting multiple sub-applications from the frequently used sub-applications as candidate sub-applications. Alternatively, candidate sub-applications can be determined based on historical records indicated by the historical interaction data, where the historical records may include historical sub-applications accessed by the user within a preset time period, and multiple historical sub-applications within the historical records can be determined as candidate sub-applications.

[0057] The multiple sub-applications are at least some of the candidate sub-applications among the multiple candidate sub-applications, and for the triggering operation of the multiple sub-applications in the multiple candidate sub-applications, a micro-terminal acquisition request for the multiple sub-applications is initiated. Exemplarily, a one-key generated function button can be set on the display page displaying the multiple candidate sub-applications, and the function button can be triggered to select all the candidate sub-applications as the multiple sub-applications, and initiate a micro-terminal acquisition request for the multiple sub-applications. Alternatively, a selection button can be set on the display page displaying the multiple candidate sub-applications, and at least some of the candidate sub-applications can be selected from the multiple candidate sub-applications to initiate a micro-terminal acquisition request. Alternatively, a target operation such as a long press operation on a blank area can be performed on the display page displaying the multiple candidate sub-applications, and all the candidate sub-applications can be regarded as multiple sub-applications, and micro-terminal acquisition requests for the multiple sub-applications can be initiated, etc. In response to the micro-terminal acquisition request for the multiple sub-applications, the sub-application micro-terminals corresponding to the multiple sub-applications can be obtained.

[0058] Referring to FIG3a , FIG3a shows the main display page of an application. Common functions and common applets (i.e., common sub-applications) can be displayed on the main display page. Common functions can include historical records, applets, etc. Common applets can include, for example, mini-games, shopping malls, etc. After determining multiple candidate sub-applications based on the historical records, you can long-press the “history” button shown in FIG3a to treat all candidate sub-applications in the historical records as multiple sub-applications, and generate a micro-client acquisition request for multiple sub-applications with one click to obtain the sub-application micro-clients of the multiple sub-applications contained in the historical records. Alternatively, you can tap the “history” button shown in FIG3a to display a display interface as shown in FIG3b , which shows multiple candidate sub-applications contained in the historical records, including sub-application 1, sub-application 2, and sub-application 3; and FIG3b also shows a function button 30 that can be generated with one click, so that all candidate sub-applications in the historical records can be treated as multiple sub-applications. By triggering the function button 30, a micro-client acquisition request for multiple sub-applications is generated to obtain the sub-application micro-clients of the multiple sub-applications contained in the historical records. Among them, after displaying multiple candidate sub-applications contained in the historical records, multiple candidate sub-applications can also be selected to determine multiple sub-applications of the micro-client to be obtained, so as to subsequently obtain the sub-application micro-client of the selected multiple sub-applications.

[0059] In an optional embodiment, in response to micro-client acquisition requests for multiple sub-applications in an application, acquiring sub-application micro-clients corresponding to the multiple sub-applications respectively includes:

[0060] In response to a micro-client acquisition request for any sub-application in the application, determine and display a recommended sub-application; after selecting a sub-application from the recommended sub-application, generate a micro-client acquisition request for any sub-application and the selected sub-application; in response to the micro-client acquisition request for any sub-application and the selected sub-application, obtain the sub-application micro-client corresponding to each of the any sub-application and the selected sub-application.

[0061] When using any sub-application, a user can initiate a micro-client acquisition request for that sub-application. In response to this micro-client acquisition request for any sub-application within the application, recommended sub-applications are determined and displayed. Recommended sub-applications may include sub-applications in historical records, frequently used sub-applications, and so on. The method for determining recommended sub-applications can be set based on actual needs, and the number of recommended sub-applications determined can be one or more. By displaying recommended sub-applications, users can select a sub-application from the recommended sub-applications.

[0062] After the user selects a sub-application from the recommended sub-applications, a micro-client acquisition request is generated for any sub-application and the selected sub-application; in response to the micro-client acquisition request for any sub-application and the selected sub-application, the sub-application micro-clients corresponding to the any sub-application and the selected sub-application are acquired.

[0063] During implementation, each sub-application may correspond to an application identifier, and the micro-terminal acquisition request may carry application identifiers corresponding to multiple sub-applications respectively. The micro-terminal acquisition request is sent to the server, and the server obtains the application identifiers corresponding to the multiple sub-applications respectively by parsing the micro-terminal acquisition request; the server determines the storage addresses of the sub-application micro-terminals corresponding to the multiple sub-applications respectively from the storage area based on the application identifiers corresponding to the multiple sub-applications respectively obtained by parsing, so that the user terminal can obtain the sub-application micro-terminals corresponding to the multiple sub-applications respectively from the storage address.

[0064] Here, by setting up multiple methods, the acquisition operation of sub-application micro-clients of multiple sub-applications is realized, thereby improving the acquisition efficiency and creation efficiency of sub-application micro-clients.

[0065] For S103:

[0066] When multiple sub-application micro-clients are displayed on the terminal interface, a user can trigger any of the multiple sub-application micro-clients, and the triggered sub-application micro-client is the target sub-application micro-client. In response to the triggering operation on the target sub-application micro-client on the terminal interface, the application is launched. After the application is launched, the display interface of the target sub-application corresponding to the target sub-application micro-client can be determined based on the application identifier indicated by the target sub-application micro-client, and the display interface of the target sub-application can be displayed.

[0067] In an optional embodiment, in response to a triggering operation on a target sub-application micro-client among the multiple sub-application micro-clients, starting the application and displaying a display interface of the target sub-application corresponding to the target sub-application micro-client in the application specifically includes:

[0068] Step a1: In response to a triggering operation on a target sub-application micro-terminal among the multiple sub-application micro-terminals, generate target summary information corresponding to the target sub-application micro-terminal based on an information generation rule indicated by the target sub-application terminal.

[0069] Step a2: transmit the target summary information to the application.

[0070] Step a3: In response to the application receiving the target summary information, the application is started, and based on the target summary information, a display interface of the target sub-application corresponding to the target sub-application micro-client is displayed in the application.

[0071] In response to a triggering operation on a target sub-application mini-terminal on the terminal interface, a target summary information schema corresponding to the target sub-application mini-terminal is generated based on the information generation rules indicated by the target sub-application terminal. The information generation rules can be set on the target sub-application mini-terminal, and the content of the information generation rules is application-dependent. Different applications can set different information generation rules, so the information generation rules are not specifically limited here.

[0072] After obtaining the target feed information schema, the target feed information can be passed to the application. For example, the deep link technology carried by the user end can be used to pass the schema to the specified application, that is, the specified application is the application to which the target sub-application micro-end belongs.

[0073] In response to the application receiving the target summary information, the application is started, and based on the identification string indicated by the target summary information, the router is routed to the specified target sub-application, and then the display interface of the target sub-application is displayed in the application.

[0074] The target sub-application micro-client includes the application identifier and the target sub-application's application identifier. By utilizing the application's launch capability, the application is launched, allowing the application to determine the target sub-application to be displayed based on the target summary information and display the target sub-application's display interface. This configuration allows the target sub-application micro-client to have a small package size, reducing resource usage and improving user-side installation efficiency. Furthermore, by generating rules based on information indicated by the target sub-application terminal, the target summary information corresponding to the target sub-application micro-client is generated; and by transmitting the target summary information to the application, the target sub-application can be accessed, resulting in a relatively simple launch logic for the target sub-application.

[0075] Taking into account that a sub-application on an application can have multiple functions, in order to improve the efficiency of triggering the multiple functions of the sub-application, a shortcut function can be set on the sub-application micro-terminal so that the user can directly enter the functional interface of the target sub-application, thereby improving the display diversity of the target sub-application and the display efficiency of the multiple functions of the target sub-application.

[0076] In an optional embodiment, in response to a triggering operation on a target sub-application micro-client on the terminal interface, starting the application and displaying a display interface of the target sub-application corresponding to the target sub-application micro-client in the application includes:

[0077] In one embodiment, in response to a first trigger operation on the target sub-application micro-client, the application is started and the main display page of the target sub-application is displayed in the application.

[0078] In another embodiment, in response to a second trigger operation on the target sub-application micro-client, a function operation page is displayed; the function operation page is used to display at least one sub-application function in the target sub-application.

[0079] Among them, the function operation page includes a function identifier of at least one sub-application function. Subsequently, the application can be started in response to a trigger operation of any function identifier on the function operation page, and a sub-display page matching the function identifier of the target sub-application can be displayed in the application.

[0080] During implementation, if the target sub-application micro-client has a shortcut function, different trigger operations can be performed on the target sub-application micro-client to display different pages. For example, the first trigger operation can be a tap operation, and the second trigger operation can be a long press operation. Alternatively, the first trigger operation can be a single click operation, and the second trigger operation can be a double click operation, etc.

[0081] In response to a first trigger operation on a target sub-application micro-client on a terminal interface, the application is launched and a main display page of the target sub-application is displayed in the application. The main display page may include function identifiers corresponding to multiple functions, so that the target operation can be performed on the main display page and a lower-level function page, i.e., a sub-display page displaying the sub-application function, is displayed.

[0082] In response to a second trigger operation on the target sub-application micro-client on the terminal interface, a function operation page containing at least one function identifier is displayed. The function identifier displayed on the function operation page can be fixed or variable, such as changing over time or with historical interaction data. Different sub-applications can contain different function identifiers, so the specific content of the function identifier can be set as needed and is not limited by this disclosure. In response to a trigger operation on the function identifier on the function operation page, the application is launched, and a sub-display page of the sub-application function matching the function identifier of the target sub-application is displayed within the application.

[0083] As shown in Figure 4, Figure 4a shows a terminal interface, which displays the target sub-application micro-client. A first trigger operation on the target sub-application micro-client displays the target sub-application's main display page, as shown in Figure 4b. A second trigger operation on the target sub-application micro-client displays a function operation page containing sub-application functions, as shown in Figure 4c. The function operation page includes Function 1 and Function 2. Furthermore, in response to a trigger operation on a sub-application function, such as tapping Function 1 to launch the application, a sub-display page matching the target sub-application's sub-application function is displayed within the application, as shown in Figure 4d, which includes Sub-Display Page 1 corresponding to Function 1.

[0084] Here, different pages can be displayed for different trigger operations of the target sub-application micro-client, thereby improving the display diversity of the target sub-application.

[0085] The parameter adding methods of the shortcut function include static adding method and dynamic adding method. In the static adding method, the function identifier contained in the function operation page is fixed, and the display efficiency of the function operation page is high in this method; in the dynamic adding method, the function identifier contained in the function operation page can be changed, and the display of the function operation page in this method is diverse and flexible.

[0086] If the shortcut function parameter addition method is dynamic, the dynamic addition method is used to add the function parameters of the shortcut function. The function parameters are used to indicate the function identifier and the display location of the function identifier included in the function operation page. The function parameters may also indicate relevant information about the sub-application function on the function operation page, such as preview information of the sub-application function under a preset function type. Therefore, the type and display location of the function identifier corresponding to the shortcut function in the dynamic addition method can be updated as needed.

[0087] In one embodiment, in response to a second trigger operation on the target sub-application micro-terminal, the sub-application function to be displayed of the target sub-application micro-terminal can be determined based on the trigger time of the second trigger operation; and a function operation page containing the sub-application function to be displayed is displayed.

[0088] Taking into account that users have different needs at different times, it is possible to respond to a second trigger operation on the target sub-application micro-terminal on the terminal interface and determine the sub-application function currently to be displayed on the target sub-application micro-terminal based on the trigger time of the second trigger operation. Each sub-application function corresponds to a function identifier, and at least one function identifier currently included in the function operation page is obtained. For example, when the target sub-application is a news sub-application, the function operation page of the target sub-application micro-terminal in the morning time period may include a sub-application function of news recommendation, and the target sub-application micro-terminal in the evening time period may include a sub-application function of news summary, etc. For another example, when the target sub-application is a shopping mall, if the mall has a limited-time event, the sub-application function of the limited-time event included in the function operation page of the target sub-application micro-terminal can be determined during the event period corresponding to the limited-time event, and so on.

[0089] Furthermore, a function operation page including the sub-application functions to be displayed can be displayed, achieving the effect of displaying different sub-application functions at different times, thereby improving the display diversity and flexibility of the function operation page.

[0090] In another embodiment, the display of the function operation page in response to the second trigger operation on the target sub-application micro-terminal may include: obtaining preview information of the sub-application function of the preset function type in the target sub-application in response to the second trigger operation on the target sub-application micro-terminal; generating and displaying the function operation page containing the preview information of the sub-application function.

[0091] During implementation, the preset function type can be flexibly determined based on demand. For example, if the application is a news application, the preset function type may be a hot topic function type; for another example, if the application is a shopping application, the preset function type may be an item recommendation function type, etc. The preview information may be real-time recommended content for a sub-application function. For example, for a sub-application function of the hot topic function type, the preview information may include the latest hot news information at the current time; for a sub-application function of the item recommendation function type, the preview information may include information about recommended items determined based on historical user interaction data, etc.

[0092] After obtaining the preview information, a function operation page including the preview information of the sub-application function can be generated and displayed. For example, if the function operation page includes sub-application function 1 and sub-application function 2, where sub-application function 1 is a preset function type, the function operation page will display: the function identifier and preview information of sub-application function 1, and the function identifier of sub-application function 2. The preview information of sub-application function 1 can be located in the area surrounding the function identifier, such as the preview information is located to the left of the function identifier.

[0093] During implementation, the application can be launched by triggering the function identifier or preview information of the sub-application function on the function operation page, and the sub-display page corresponding to the sub-application function in the application can be displayed. If preview information for the sub-application function exists, the preview information can be displayed on the sub-display page, such as by displaying the preview information in a floating layer; or the preview information can be displayed in a preset display area of ​​the sub-display page.

[0094] In another embodiment, the display of the function operation page in response to the second trigger operation on the target sub-application micro-terminal may further include: in response to the second trigger operation on the target sub-application micro-terminal, determining the sub-application function to be displayed of the target sub-application micro-terminal based on the trigger time of the second trigger operation; when there is a sub-application function of a preset function type among the sub-application functions to be displayed, obtaining preview information of the sub-application function of the preset function type; generating a function operation page that displays the sub-application function to be displayed and the preview information of the sub-application function of the preset function type. The specific process of the content of this embodiment can be referred to the description of the above embodiment and will not be described in detail here.

[0095] The static addition method involves writing the shortcut function's parameters into a specific file within the sub-application mini-client during the sub-application mini-client's generation process. The dynamic addition method involves writing parameter configuration logic into a specific file within the sub-application mini-client during the generation process. This parameter configuration logic indicates the acquisition method and target storage address for the function parameters, so that the shortcut function's parameters are retrieved from the server's target storage address according to the indicated acquisition method. This indicates that with the dynamic addition method, the function parameters stored at the target storage address can be updated as needed.

[0096] Exemplarily, in conjunction with the dynamic addition process, the process of determining the sub-application function to be displayed currently included in the target sub-application micro-client based on the trigger time of the second trigger operation is described. For example, based on the parameter configuration logic indicated by the target sub-application micro-client and the trigger time of the second trigger operation, the function parameters of the shortcut function that match the trigger time are obtained from the target storage address of the server. The function parameters can indicate the current sub-application function to be displayed. The function parameters can be obtained from different target storage addresses at different trigger times.

[0097] After initiating the second trigger operation on the target sub-application micro-terminal on the terminal interface, the parameter adding method of the target sub-application micro-terminal can be determined first. That is, in response to the second trigger operation on the target sub-application micro-terminal on the terminal interface, the parameter adding method of the target sub-application micro-terminal is determined.

[0098] If the parameters for the shortcut function are statically added to the target sub-application micro-client, a function operation page containing the sub-application function is generated and displayed based on the function parameters of the shortcut function contained in the target sub-application micro-client. In this case, the function identifier contained in the function operation page is fixed, and since there is no need to obtain function parameters from the server, the determination and display of the function operation page in this case is simpler and more efficient.

[0099] If the shortcut function parameters are added dynamically in the target sub-application micro-client, the shortcut function parameters can be retrieved from the server based on the parameter configuration logic indicated by the target sub-application micro-client. Based on the retrieved parameters, a function operation page containing the sub-application function to be displayed is generated and displayed. In this case, the function identifier contained in the function operation page can be updated, which can increase the flexibility of function identifier display and enhance the user experience.

[0100] In an optional embodiment, before launching the application, the method further includes: initiating an asynchronous request for obtaining function parameters; in response to the asynchronous request, obtaining the function parameters of the shortcut function from the server based on the parameter configuration logic indicated by the target sub-application micro-client, and caching the function parameters to a first cache module, wherein the function parameters are used to indicate the sub-application functions contained in the function operation page.

[0101] When the parameter adding method of the shortcut function of the target sub-application micro-terminal is dynamic addition, an asynchronous request is initiated to obtain the function parameters. Since an asynchronous request is initiated, the asynchronous request process is carried out in parallel with the process of starting the application.

[0102] The function parameter is used to indicate the sub-application function contained in the function operation page, and can also indicate the placement location of the sub-application function.

[0103] In one scenario, in response to a first trigger operation on a target sub-application micro-client on a terminal interface, the first aspect initiates an asynchronous request for obtaining function parameters; in response to the asynchronous request, based on the parameter configuration logic indicated by the target sub-application micro-client, the function parameters of the shortcut function are obtained from the server and cached in a first cache module. The second aspect launches an application and displays the main display page of the target sub-application in the application. The first and second aspects are executed in parallel, and the function parameters obtained by the first aspect are used for the next initiation of a second trigger operation on the target sub-application micro-client on the terminal interface.

[0104] In another case, in response to a second trigger operation on the target sub-application micro-client on the terminal interface, a function operation page containing at least one sub-application function is displayed; wherein the sub-application function contained in the function operation page displayed this time is determined based on the function parameters cached by the first cache module, and the function parameters cached by the first cache module are obtained by the previous asynchronous request. And in response to the trigger operation on the sub-application function in the function operation page, the first aspect initiates an asynchronous request for obtaining the function parameters; in response to the asynchronous request, based on the parameter configuration logic indicated by the target sub-application micro-client, the function parameters of the shortcut function are obtained from the server, and the function parameters are cached to the first cache module. The second aspect starts the application and displays the sub-display page that matches the triggered sub-application function in the application.

[0105] By setting an asynchronous request here, you can execute the application startup operation while obtaining the function parameters, alleviate the interference of the asynchronous request process on the application startup, improve the application startup efficiency, and thus ensure the efficiency of the target sub-application.

[0106] In an optional embodiment, the user terminal includes a first cache module and a second cache module, the first cache module is used to cache function parameters obtained based on asynchronous requests, and the second cache module is used to cache function parameters corresponding to the current function operation page. Before starting the application, the method further includes:

[0107] When function parameters are cached in the first cache module and no function parameters are cached in the second cache module, the function parameters cached in the first cache module are added to the second cache module, and an updated function operation page is generated based on the newly added function parameters in the second cache module.

[0108] When function parameters are cached in the first cache module and function parameters are cached in the second cache module, determine whether version information of the function parameters in the first cache module is consistent with the version information of the function parameters in the second cache module; if they are inconsistent, use the function parameters in the first cache module to update the second cache module, and generate an updated function operation page based on the updated function parameters in the second cache module.

[0109] When no function parameters are cached in the second cache module, the current function operation page is represented as the initial page without the sub-application function. If function parameters are cached in the first cache module and no function parameters are cached in the second cache module, the function parameters cached in the first cache module can be added to the second cache module, and an updated function operation page can be generated based on the newly added function parameters in the second cache module, so that the next time a second trigger operation is triggered on the target sub-application micro-client on the terminal interface, the updated function operation page can be displayed.

[0110] When function parameters are cached in the first cache module and function parameters are cached in the second cache module, determine whether the version information of the function parameters in the first cache module is consistent with the version information of the function parameters in the second cache module; if they are inconsistent, it indicates that the function parameters on the server have been updated, so the function parameters in the first cache module are used to update the second cache module, and based on the updated function parameters in the second cache module, an updated function operation page is generated so that the next time the second trigger operation for the target sub-application micro-client on the terminal interface is triggered, the updated function operation page is displayed. If they are consistent, it indicates that the function parameters on the server have not been updated, that is, there is no need to update the function operation page.

[0111] Referring to FIG5 , the processing logic of the target sub-application micro-client including the shortcut function is exemplified in conjunction with FIG5 , wherein the parameter addition method of the shortcut function is dynamic addition. After the first trigger operation is initiated for the target sub-application micro-client on the terminal interface, or after the trigger operation is initiated for the sub-application function on the function operation page, the following process is performed:

[0112] Step 51: Asynchronously request shortcut configuration information.

[0113] The specific process is: initiate an asynchronous request, respond to the asynchronous request, obtain the function parameters of the shortcut function from the server based on the parameter configuration logic indicated by the target sub-application micro-client, and cache the function parameters to the first cache module.

[0114] Step 52: Read shortcut request information from the cache.

[0115] The specific process is: obtaining the function parameters cached by the first cache module, and obtaining the function parameters cached by the second cache module, wherein the function parameters are associated with version information.

[0116] Step 53: Determine whether the shortcut needs to be displayed. If so, execute step 54; if not, execute step 58, that is, execute the pull-up logic.

[0117] It is determined whether the first cache module and the second cache module have cached function parameters. If neither of them has cached function parameters, there is no need to display the shortcut. If at least one cache module has cached function parameters, the shortcut needs to be displayed.

[0118] Step 54: Determine whether the shortcut has been displayed. If so, execute step 56; if not, execute step 55.

[0119] The specific process is as follows: determining whether the cached function parameters exist in the second cache module, and if so, determining that the shortcut has been displayed, and executing step 56. If not, determining that the shortcut has not been displayed, and executing step 55.

[0120] Step 55: Execute the shortcut logic of adding, and after executing step 55, execute step 58, that is, execute the pull-up logic.

[0121] The specific process is: adding the function parameters cached in the first cache module to the second cache module, and generating an updated function operation page based on the newly added function parameters in the second cache module. After the updated function operation page is generated, step 58 is executed.

[0122] Step 56: Determine whether the shortcut needs to be updated. If so, execute step 57; if not, execute step 58.

[0123] Since the first cache module is used to cache function parameters obtained based on asynchronous requests, and the second cache module is used to cache function parameters corresponding to the current function operation page, the first cache module caches the most recently retrieved function parameters, while the second cache module caches the currently displayed function parameters. Therefore, the need to update the shortcut can be determined based on the data cached by the first cache module and the data cached by the second cache module.

[0124] The specific process is as follows: determine whether the data cached in the first cache module is consistent with the data cached in the second cache module. If they are consistent, there is no need to update the shortcut; if they are inconsistent, the shortcut needs to be updated. For example, if the version information of the function parameters cached in the first cache module is the same as the version information of the function parameters cached in the second cache module, there is no need to update the shortcut. Alternatively, if the latest version information of the function parameters cached in the first cache module is the same as the version information of the function parameters cached in the first cache module, there is no need to update the shortcut.

[0125] Step 57: Execute the update shortcut logic.

[0126] The specific process is: using the function parameters in the first cache module to update the second cache module, and generating an updated function operation page based on the updated function parameters in the second cache module.

[0127] Step 58: Execute the pull-up logic.

[0128] The specific process is: start the application and display the main display page of the target sub-application in the application. Alternatively, start the application and display the sub-display page that matches the sub-application function of the target sub-application in the application.

[0129] In business scenarios, there is a need for sub-applications to push content. Based on this, a push function can be set up on the sub-application micro-client.

[0130] In an optional embodiment, when the target sub-application micro-terminal has a push function, the target sub-application micro-terminal includes a push identifier and a template identifier, and the method further includes: receiving and displaying push content sent by the server according to the push identifier, wherein the server is used to generate the push content using the push template indicated by the template identifier; in response to a trigger operation for the push content, starting the application, and displaying the display interface of the target sub-application corresponding to the target sub-application micro-terminal in the application.

[0131] Each sub-application micro-client is assigned a push identifier, and the server can deliver push content based on the push identifier. The server receives and displays push content delivered by the server based on the push identifier, where the server generates push content using the push template indicated by the template identifier. During implementation, a technician can enter push information into the server, which then adds the push information to the push template indicated by the template identifier, generates push content, and delivers it to the sub-application micro-client corresponding to the push identifier.

[0132] In response to a trigger operation for pushing content, the application is started and the display interface of the target sub-application corresponding to the target sub-application micro-client is displayed in the application. If the target sub-application micro-client has a shortcut function, the main display interface of the target sub-application corresponding to the target sub-application micro-client can be displayed in the application.

[0133] Based on the same inventive concept, as shown in FIG6 , another method for generating a micro-client is provided in an embodiment of the present disclosure, which is applied to a server and specifically includes S601 to S603, wherein:

[0134] S601, in response to a micro-client generation operation for at least one sub-application in an application, obtaining a first parameter corresponding to the application and a second parameter corresponding to each of the sub-applications;

[0135] S602: Generate a sub-application micro-client corresponding to the sub-application based on the first parameter, the second parameter of each sub-application, and the constructed micro-client code module;

[0136] S603: Store the sub-application micro-client corresponding to the sub-application.

[0137] In this method, a first parameter corresponding to the application and a second parameter corresponding to each sub-application are obtained by performing a micro-terminal generation operation for at least one sub-application in the application. Based on the first parameter, the second parameter of each sub-application, and a constructed micro-terminal code module, a sub-application micro-terminal corresponding to the sub-application is generated. Since the micro-terminal code module contains the basic code required to generate the micro-terminal, the micro-terminal code module can be used to more easily generate the sub-application micro-terminal based on the first and second parameters. Furthermore, the second parameters of different sub-applications can be used to generate sub-application micro-terminals for different sub-applications under the application, resulting in high micro-terminal generation efficiency. At the same time, the sub-application micro-terminals corresponding to the sub-applications are stored so that the user terminal can pull the sub-application micro-terminals of multiple sub-applications as needed, thereby improving micro-terminal deployment efficiency.

[0138] The following describes S601-S603 in detail.

[0139] In S601, for each sub-application in the application, a first parameter of the application and a second parameter of the sub-application are obtained. The first parameter and the second parameter are basic parameters required by the micro-end code module. For example, the first parameter may include an application identifier, and the second parameter may include an application identifier of the sub-application.

[0140] In S602, during implementation, the micro-terminal code module includes the basic code required to build the micro-terminal, and the basic code includes basic parameters related to the application and sub-application. The basic parameters are replaced with the first parameter and the second parameter, and the micro-terminal code module including the first parameter and the second parameter is processed, such as packaged, to obtain the sub-application micro-terminal corresponding to the sub-application. The sub-application micro-terminal corresponding to the sub-application is stored. Feedback information including the storage address of the sub-application micro-terminal can also be sent to the sub-application creator, so that the sub-application creator can obtain the sub-application micro-terminal according to the storage address indicated by the feedback information, and verify the obtained sub-application micro-terminal to improve the security of the sub-application micro-terminal.

[0141] In an optional embodiment, the sub-application micro-terminal corresponding to the sub-application is generated based on the first parameter, the second parameter of each sub-application and the constructed micro-terminal code module, including: when it is determined that the second parameter contains the functional parameter corresponding to the preset function, preprocessing the micro-terminal code module to generate a processed micro-terminal code module, wherein the preset function includes a shortcut function and / or a push function; based on the first parameter, the second parameter, and the processed micro-terminal code module, generating the sub-application micro-terminal corresponding to the sub-application.

[0142] The preset functions include a shortcut function and a push function. The second parameter may include the function parameters of the shortcut function and / or the function parameters of the push function. The micro-terminal code module contains a code block that matches the preset function. When it is determined that the second parameter contains the function parameter corresponding to the preset function, the micro-terminal code module is preprocessed, that is, the code block corresponding to the preset function is processed to generate a processed micro-terminal code module; then, based on the first parameter, the second parameter, and the processed micro-terminal code module, a sub-application micro-terminal corresponding to the sub-application is generated.

[0143] In the case where the preset function includes a shortcut function, the preprocessing of the micro-terminal code module to generate a processed micro-terminal code module includes: determining a parameter adding method, and the parameter adding method includes a static adding method and a dynamic adding method.

[0144] When the parameter adding method indicates a static adding method, based on the function parameters corresponding to the shortcut function, the first code block corresponding to the shortcut function in the micro-terminal code module is replaced with parameters to generate a processed micro-terminal code module.

[0145] When the parameter adding method is indicated as a dynamic adding method, parameter configuration logic is generated, and based on the parameter configuration logic, the parameters of the first code block corresponding to the shortcut function in the micro-terminal code module are replaced to generate a processed micro-terminal code module, and the parameter configuration logic is used to obtain the function parameters corresponding to the shortcut function.

[0146] The parameter adding method is specified by the creator of the sub-application. For example, the second parameter may include a parameter indicator indicating the parameter adding method. If the parameter indicator is a first preset value such as 0, the parameter adding method is a static adding method. If the parameter indicator is a second preset value such as 1, the parameter adding method is a dynamic adding method.

[0147] When the parameter adding method is indicated as a static adding method, the function parameters corresponding to the shortcut function contained in the second parameter can be used to replace the parameters of the first code block corresponding to the shortcut function in the micro-terminal code module to generate a processed micro-terminal code module, so that the parameters of the processed micro-terminal code module can be replaced based on the first parameter and other parameters in the second parameter except the function parameters, and the micro-terminal code block after parameter replacement can be processed to generate a sub-application micro-terminal.

[0148] When the parameter addition method is indicated as dynamic addition, parameter configuration logic is generated. Based on the parameter configuration logic, the parameters of the first code block corresponding to the shortcut function in the micro-end code module are replaced to generate a processed micro-end code module. The parameter configuration logic is used to obtain the function parameters corresponding to the shortcut function. The parameter configuration logic can be flexibly configured according to the application scenario. In this case, the function parameter in the second parameter serves as a prompt, that is, the presence of the function parameter indicates that the sub-application has a shortcut function.

[0149] Here, a shortcut function is created in the sub-application micro-client, so that after the subsequent user client installs the sub-application micro-client, the main display page of the sub-application micro-client or the sub-display page of the lower-level sub-application function can be displayed as needed, thereby improving the use efficiency of the sub-application and thus improving the user experience.

[0150] In the case where the preset function includes a push function, the micro-terminal code module is preprocessed to generate a processed micro-terminal code module, including: obtaining a second code block with a push function, a push identifier corresponding to the second code block, and a template identifier of a push template; updating the second code block, the push identifier and the template identifier to the micro-terminal code module to generate a processed micro-terminal code module.

[0151] The function parameters of the push function may include a push indication parameter indicating that the push function is enabled. The presence of the push indication parameter indicates that the push function exists. When the push function exists, a pre-built second code block with a push function, a push identifier corresponding to the second code block, and a template identifier of a push template are obtained from the push platform. The second code block, the push identifier, and the template identifier are updated into the micro-client code module to generate a processed micro-client code module. The processed micro-client code module is then processed so that the resulting sub-application micro-client has the push function.

[0152] Those skilled in the art will understand that in the above-mentioned method of the specific implementation method, the writing order of each step does not mean a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0153] Based on the same inventive concept, a micro-terminal generation device corresponding to the micro-terminal generation method is also provided in the embodiment of the present disclosure. Since the principle of solving the problem by the device in the embodiment of the present disclosure is similar to the above-mentioned micro-terminal generation method in the embodiment of the present disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0154] 7, which is a schematic diagram of the structure of a micro-terminal generation device provided by an embodiment of the present disclosure, the device includes: a first acquisition module 701, a display module 702, and a startup module 703; wherein,

[0155] The first acquisition module 701 is configured to respond to micro-client acquisition requests for multiple sub-applications in an application program and acquire sub-application micro-clients corresponding to the multiple sub-applications respectively;

[0156] A display module 702 is configured to display multiple sub-application micro-clients on the terminal interface of the user terminal;

[0157] The startup module 703 is configured to start the application in response to a trigger operation on a target sub-application micro-client among the multiple sub-application micro-clients, and display a display interface of the target sub-application corresponding to the target sub-application micro-client in the application.

[0158] In one possible implementation, before responding to micro-client acquisition requests for multiple sub-applications in the application and acquiring the sub-application micro-clients corresponding to the multiple sub-applications, the first acquisition module 701 is further configured to:

[0159] Determine multiple candidate sub-applications in the application based on historical interaction data and display them;

[0160] In response to triggering of multiple sub-applications among the multiple candidate sub-applications, micro-client acquisition requests for the multiple sub-applications are generated.

[0161] In one possible implementation, the startup module 703, in response to a triggering operation on a target sub-application micro-client on the terminal interface, starts the application and displays a display interface of the target sub-application corresponding to the target sub-application micro-client in the application, is configured to:

[0162] In response to a first triggering operation on the target sub-application micro-client, starting the application and displaying a main display page of the target sub-application in the application;

[0163] In response to a second trigger operation on the target sub-application micro-client, a function operation page is displayed; the function operation page is used to display at least one sub-application function in the target sub-application.

[0164] In one possible implementation, the startup module 703, in response to the second triggering operation on the target sub-application micro-client, is configured to:

[0165] In response to the second triggering operation on the target sub-application micro-client, determining a sub-application function to be displayed of the target sub-application micro-client based on a triggering time of the second triggering operation;

[0166] Display a function operation page including the sub-application function to be displayed.

[0167] In one possible implementation, the starting module 703, when displaying the function operation page in response to the second triggering operation on the target sub-application micro-client, is configured to:

[0168] In response to the second triggering operation on the target sub-application micro-client, obtaining preview information of a sub-application function of a preset function type in the target sub-application;

[0169] Generate and display the function operation page containing preview information of the sub-application function.

[0170] In a possible implementation, before starting the application, the starting module 703 is further configured to:

[0171] Initiate an asynchronous request to obtain function parameters;

[0172] In response to the asynchronous request, based on the parameter configuration logic indicated by the target sub-application micro-client, the function parameters of the shortcut function are obtained from the server, and the function parameters are cached to the first cache module, wherein the function parameters are used to indicate the sub-application function included in the function operation page.

[0173] In one possible implementation, the user terminal includes a first cache module and a second cache module, wherein the first cache module is used to cache function parameters obtained based on asynchronous requests, and the second cache module is used to cache function parameters corresponding to the current function operation page;

[0174] Before starting the application, the starting module 703 is further configured to:

[0175] If function parameters are cached in the first cache module and no function parameters are cached in the second cache module, add the function parameters cached in the first cache module to the second cache module, and generate an updated function operation page based on the newly added function parameters in the second cache module;

[0176] When function parameters are cached in the first cache module and function parameters are cached in the second cache module, determine whether version information of the function parameters in the first cache module is consistent with the version information of the function parameters in the second cache module; if they are inconsistent, use the function parameters in the first cache module to update the second cache module, and generate an updated function operation page based on the updated function parameters in the second cache module.

[0177] In a possible implementation, when the target sub-application micro-client has a push function, the target sub-application micro-client includes a push identifier and a template identifier, and the apparatus further includes a push module 704 configured to:

[0178] receiving and displaying push content issued by a server according to a push identifier, wherein the server is configured to generate the push content using a push template indicated by the template identifier;

[0179] In response to a triggering operation for the pushed content, the application is started, and a display interface of the target sub-application corresponding to the target sub-application micro-client is displayed in the application.

[0180] In one possible implementation, the startup module 703, in response to a triggering operation on a target sub-application micro-client among the multiple sub-application micro-clients, starts the application and displays a display interface of the target sub-application corresponding to the target sub-application micro-client in the application, is configured to:

[0181] In response to a triggering operation on a target sub-application micro-terminal among the plurality of sub-application micro-terminals, generating target summary information corresponding to the target sub-application micro-terminal based on an information generation rule indicated by the target sub-application terminal;

[0182] passing the target feed information to the application;

[0183] In response to the application receiving the target summary information, the application is started, and based on the target summary information, a display interface of the target sub-application corresponding to the target sub-application micro-client is displayed in the application.

[0184] In one possible implementation, the first acquisition module 701, in response to micro-client acquisition requests for multiple sub-applications in an application program, is configured to:

[0185] In response to a micro-client acquisition request for any sub-application in the application, determine and display a recommended sub-application; after selecting a sub-application from the recommended sub-application, generate a micro-client acquisition request for any sub-application and the selected sub-application; in response to the micro-client acquisition request for any sub-application and the selected sub-application, obtain the sub-application micro-client corresponding to each of the any sub-application and the selected sub-application.

[0186] 8, which is a schematic diagram of the structure of a micro-terminal generation device provided in an embodiment of the present disclosure, the device includes: a second acquisition module 801, a generation module 802, and a storage module 803; wherein,

[0187] A second acquisition module 801 is configured to, in response to a micro-client generation operation for at least one sub-application in an application, acquire a first parameter corresponding to the application and a second parameter corresponding to each of the sub-applications;

[0188] A generating module 802 is configured to generate a sub-application micro-terminal corresponding to the sub-application based on the first parameter, the second parameter of each sub-application, and the constructed micro-terminal code module;

[0189] The storage module 803 is configured to store the sub-application micro-client corresponding to the sub-application.

[0190] In one possible implementation, the generation module 802, when generating the sub-application micro-terminal corresponding to the sub-application based on the first parameter, the second parameter of each sub-application, and the constructed micro-terminal code module, is configured as follows:

[0191] If it is determined that the second parameter includes a function parameter corresponding to a preset function, preprocessing the micro-terminal code module to generate a processed micro-terminal code module, wherein the preset function includes a shortcut function and / or a push function;

[0192] Based on the first parameter, the second parameter, and the processed micro-terminal code module, a sub-application micro-terminal corresponding to the sub-application is generated.

[0193] In one possible implementation, when the preset function includes a shortcut function, the generation module 802, when preprocessing the micro-terminal code module and generating the processed micro-terminal code module, is configured as follows:

[0194] Determine a parameter adding method, wherein the parameter adding method includes a static adding method and a dynamic adding method;

[0195] When the parameter adding mode indicates a static adding mode, performing parameter replacement on the first code block corresponding to the shortcut function in the micro-terminal code module based on the function parameters corresponding to the shortcut function to generate a processed micro-terminal code module;

[0196] When the parameter adding method is indicated as a dynamic adding method, parameter configuration logic is generated, and based on the parameter configuration logic, the parameters of the first code block corresponding to the shortcut function in the micro-terminal code module are replaced to generate a processed micro-terminal code module, and the parameter configuration logic is used to obtain the function parameters corresponding to the shortcut function.

[0197] In one possible implementation, when the preset function includes a push function, the generation module 802, when preprocessing the micro-terminal code module and generating the processed micro-terminal code module, is configured as follows:

[0198] Acquire a second code block with a push function, a push identifier corresponding to the second code block, and a template identifier of a push template;

[0199] The second code block, the push identifier and the template identifier are updated into the micro-end code module to generate a processed micro-end code module.

[0200] For descriptions of the processing flow of each module in the device and the interaction flow between each module, reference can be made to the relevant descriptions in the above method embodiment, which will not be described in detail here.

[0201] Based on the same technical concept, the embodiment of the present disclosure also provides a computer device. Referring to Figure 9, it is a structural diagram of the computer device 900 provided in the embodiment of the present disclosure, including a processor 901, a memory 902, and a bus 903. Among them, the memory 902 is used to store execution instructions, including a memory 9021 and an external memory 9022; the memory 9021 here is also called an internal memory, which is used to temporarily store the calculation data in the processor 901, as well as the data exchanged with the external memory 9022 such as a hard disk. The processor 901 exchanges data with the external memory 9022 through the memory 9021. When the computer device 900 is running, the processor 901 communicates with the memory 902 through the bus 903, so that the processor 901 executes the following instructions:

[0202] In response to micro-client acquisition requests for multiple sub-applications in the application, acquire sub-application micro-clients corresponding to the multiple sub-applications respectively;

[0203] Displaying multiple sub-application micro-clients on the terminal interface of the user terminal;

[0204] In response to a triggering operation on a target sub-application micro-client among the multiple sub-application micro-clients, the application is started, and a display interface of the target sub-application corresponding to the target sub-application micro-client is displayed in the application.

[0205] Alternatively, the processor 901 executes the following instructions:

[0206] In response to a micro-client generation operation for at least one sub-application in an application, obtaining a first parameter corresponding to the application and a second parameter corresponding to each of the sub-applications;

[0207] Generate a sub-application micro-terminal corresponding to the sub-application based on the first parameter, the second parameter of each sub-application, and the constructed micro-terminal code module;

[0208] The sub-application micro-client corresponding to the sub-application is stored.

[0209] The present disclosure also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, executes the steps of the micro-terminal generation method described in the above method embodiment. The storage medium may be a volatile or non-volatile computer-readable storage medium.

[0210] The embodiments of the present disclosure also provide a computer program product, which carries program code. The instructions included in the program code can be used to execute the steps of the micro-terminal generation method described in the above method embodiment. Please refer to the above method embodiment for details, which will not be repeated here.

[0211] The computer program product may be implemented in hardware, software, or a combination thereof. In one embodiment, the computer program product is implemented as a computer storage medium. In another embodiment, the computer program product is implemented as a software product, such as a software development kit (SDK).

[0212] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems and devices described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0214] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0215] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0216] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present disclosure, which are used to illustrate the technical solutions of the present disclosure, rather than to limit them. The scope of protection of the present disclosure is not limited thereto. Although the present disclosure has been described in detail with reference to the above-described embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily conceive of changes to the technical solutions described in the above-described embodiments within the technical scope disclosed in the present disclosure, or replace some of the technical features therein with equivalents. Such modifications, changes, or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure shall be subject to the scope of protection of the claims.

Claims

1. A micro-end generation method, applied to a user end, comprising: In response to micro-client acquisition requests for multiple sub-applications in the application, acquiring sub-application micro-clients corresponding to the multiple sub-applications respectively; Displaying multiple sub-application micro-clients on the terminal interface of the user terminal; In response to a triggering operation on a target sub-application micro-client among the multiple sub-application micro-clients, the application is started, and a display interface of the target sub-application corresponding to the target sub-application micro-client is displayed in the application.

2. The method according to claim 1, wherein: Before the step of responding to the micro-client acquisition requests for the multiple sub-applications in the application program and acquiring the sub-application micro-clients respectively corresponding to the multiple sub-applications, the method further includes: Determine multiple candidate sub-applications in the application based on historical interaction data, and display them; In response to triggering of multiple sub-applications among the multiple candidate sub-applications, micro-end acquisition requests for the multiple sub-applications are generated.

3. The method according to claim 1, wherein: The method of starting the application program in response to a trigger operation on a target sub-application micro-client among the multiple sub-application micro-clients and displaying a display interface of a target sub-application corresponding to the target sub-application micro-client in the application program comprises: In response to a first trigger operation on the target sub-application micro-client, starting the application program and displaying a main display page of the target sub-application in the application program; In response to a second trigger operation on the target sub-application micro-client, a function operation page is displayed; the function operation page is used to display at least one sub-application function in the target sub-application.

4. The method according to claim 3, wherein: The displaying of a function operation page in response to the second trigger operation on the target sub-application micro-client includes: In response to the second trigger operation on the target sub-application micro-terminal, based on the trigger time of the second trigger operation, determine the sub-application function to be displayed of the target sub-application micro-terminal; Display a function operation page including the sub-application function to be displayed.

5. The method according to claim 3, wherein: The displaying of a function operation page in response to the second trigger operation on the target sub-application micro-client includes: In response to the second trigger operation on the target sub-application micro-end, obtaining the target sub-application micro-end Preview information of sub-application functions of preset function types in the application; Generate and display the function operation page containing preview information of the sub-application function.

6. The method according to claim 3, wherein: Before starting the application, the method further includes: Initiate an asynchronous request to obtain function parameters; In response to the asynchronous request, based on the parameter configuration logic indicated by the target sub-application micro-client, the function parameters of the shortcut function are obtained from the server, and the function parameters are cached to the first cache module, wherein the function parameters are used to indicate the sub-application functions included in the function operation page.

7. The method according to claim 3, wherein: The user terminal includes a first cache module and a second cache module, the first cache module is used to cache the function parameters obtained based on the asynchronous request, and the second cache module is used to cache the function parameters corresponding to the current function operation page; Before starting the application, the method further includes: In a case where the function parameters are cached in the first cache module and the function parameters are not cached in the second cache module, the function parameters cached in the first cache module are added to the second cache module, and an updated function operation page is generated based on the newly added function parameters in the second cache module; In the case where function parameters are cached in the first cache module and function parameters are cached in the second cache module, determine whether version information of the function parameters in the first cache module is consistent with version information of the function parameters in the second cache module; if they are inconsistent, use the function parameters in the first cache module to update the second cache module, and generate an updated function operation page based on the updated function parameters in the second cache module.

8. The method according to any one of claims 1 to 7, wherein: In the case where the target sub-application micro-client has a push function, the target sub-application micro-client includes a push identifier and a template identifier, and the method further includes: Receiving and displaying push content sent by a server according to a push identifier, wherein the server is used to generate the push content using a push template indicated by the template identifier; In response to a triggering operation for the pushed content, the application is started, and a display interface of the target sub-application corresponding to the target sub-application micro-client is displayed in the application.

9. The method according to any one of claims 1 to 7, wherein: The method of starting the application program in response to a trigger operation on a target sub-application micro-client among the multiple sub-application micro-clients and displaying a display interface of a target sub-application corresponding to the target sub-application micro-client in the application program comprises: In response to a trigger operation on a target sub-application micro-terminal among the plurality of sub-application micro-terminals, generating target summary information corresponding to the target sub-application micro-terminal based on an information generation rule indicated by the target sub-application terminal; passing said target feed information to an application; In response to the application receiving the target summary information, the application is started, and based on the target summary information, a display interface of the target sub-application corresponding to the target sub-application micro-client is displayed in the application.

10. The method according to any one of claims 1 to 7, wherein: In response to micro-client acquisition requests for multiple sub-applications in an application, acquiring sub-application micro-clients corresponding to the multiple sub-applications respectively includes: In response to a micro-client acquisition request for any sub-application in the application, determine and display a recommended sub-application; After selecting a sub-application from the recommended sub-applications, generating a micro-client acquisition request for any of the sub-applications and the selected sub-application; In response to the micro-client acquisition request for any one of the sub-applications and the selected sub-application, the sub-application micro-clients corresponding to the any one of the sub-applications and the selected sub-application are acquired.

11. A micro-client generation method, applied to a server, comprising: In response to a micro-client generation operation for at least one sub-application in an application, obtaining a first parameter corresponding to the application and a second parameter corresponding to each of the sub-applications; Generate a sub-application micro-terminal corresponding to the sub-application based on the first parameter, the second parameter of each of the sub-applications, and the constructed micro-terminal code module; The sub-application micro-client corresponding to the sub-application is stored.

12. The method according to claim 11, wherein: The generating a sub-application micro-terminal corresponding to the sub-application based on the first parameter, the second parameter of each sub-application and the constructed micro-terminal code module includes: In the case where it is determined that the second parameter includes a function parameter corresponding to a preset function, preprocessing the micro-end code module to generate a processed micro-end code module, wherein the preset function includes a shortcut function and / or a push function; Based on the first parameter, the second parameter, and the processed micro-end code module, generate The sub-application micro-client corresponds to the sub-application.

13. The method according to claim 12, wherein: In the case where the preset function includes a shortcut function, the preprocessing of the micro-terminal code module to generate a processed micro-terminal code module includes: Determine a parameter adding method, wherein the parameter adding method includes a static adding method and a dynamic adding method; When the parameter adding mode indicates a static adding mode, based on the function parameters corresponding to the shortcut function, the first code block corresponding to the shortcut function in the micro-terminal code module is replaced with parameters to generate a processed micro-terminal code module; When the parameter adding method is indicated as a dynamic adding method, a parameter configuration logic is generated, and based on the parameter configuration logic, the parameters of the first code block corresponding to the shortcut function in the micro-terminal code module are replaced to generate a processed micro-terminal code module, and the parameter configuration logic is used to obtain the function parameters corresponding to the shortcut function.

14. The method according to claim 12, wherein: In the case where the preset function includes a push function, the preprocessing of the micro-end code module to generate a processed micro-end code module includes: Acquire a second code block having a push function, a push identifier corresponding to the second code block, and a template identifier of a push template; The second code block, the push identifier and the template identifier are updated into the micro-end code module to generate a processed micro-end code module.

15. A micro-terminal generation device, applied to a user terminal, comprising: A first acquisition module is configured to respond to micro-client acquisition requests for multiple sub-applications in the application program, and acquire sub-application micro-clients corresponding to the multiple sub-applications respectively; A display module, used to display multiple sub-application micro-clients on the terminal interface of the user terminal; A startup module is used to start the application in response to a trigger operation on a target sub-application micro-client among the multiple sub-application micro-clients, and to display a display interface of the target sub-application corresponding to the target sub-application micro-client in the application.

16. A micro-terminal generation device, applied to a server, comprising: The second acquisition module is configured to, in response to a micro-end generation operation for at least one sub-application in the application, acquire a first parameter corresponding to the application and a second parameter corresponding to each of the sub-applications. Two parameters; A generation module configured to generate a sub-application micro-end corresponding to the sub-application based on the first parameter, the second parameter of each of the sub-applications, and the constructed micro-end code module; The storage module is configured to store the sub-application micro-client corresponding to the sub-application.

17. A computer device comprising: At least one processor, at least one memory and a bus, wherein the at least one memory stores machine-readable instructions executable by the at least one processor, and when the computer device is running, the at least one processor communicates with the at least one memory via the bus, and when the machine-readable instructions are executed by the at least one processor, the steps of the micro-terminal generation method as described in any one of claims 1 to 14 are performed.

18. A computer-readable storage medium, wherein: The computer-readable storage medium stores a computer program, which, when executed by a processor, executes the steps of the micro-terminal generation method as described in any one of claims 1 to 14.

Images