File sending method, device, apparatus, and storage medium

Abstract

The application discloses a file sending method and device, equipment and storage medium, and belongs to the computer technical field. Through the scheme provided in the application, the calling identifier of the target micro application is provided in the session interface of the application, and the file selection interface can be displayed in the case where the calling identifier is triggered. The file selection interface displays the files in the target session, that is, the files shared in the target session. Direct file selection in the file selection interface can quickly send the files to the target micro application for processing by the target micro application. Through the above process, the operation process of sending files to the target micro application is simplified, and the efficiency of human-computer interaction is improved.

Description

File sending methods, devices, equipment, and storage media Technical Field

[0001] This application relates to the field of computer technology, and in particular to a file sending method, apparatus, device, and storage medium. Background Technology

[0002] With the development of internet technology, more and more users are sharing files through social networking applications. In some cases, it is necessary to process files obtained through social networking applications, such as editing spreadsheets or images.

[0003] In related technologies, when searching for files from social media applications, it is often necessary to view the chat history of the social media application and find the file to be processed within the chat history. When processing the file, it is also necessary to find the target application's option among multiple application options and send the file to the target application through that option. When editing the file in the target application, it is also necessary to manually switch the social media application to the target application to process the file.

[0004] However, since chat logs include not only files but also a large amount of chat text, finding files in the chat logs takes a lot of time, and finding the target application to import from multiple application options also requires a rather complicated process, making the file sending process rather complicated and the efficiency of human-computer interaction relatively low. Summary of the Invention

[0005] This application provides a file sending method, apparatus, device, and storage medium, which can improve the efficiency of human-computer interaction. The technical solution is as follows:

[0006] On the one hand, a file sending method is provided, the method comprising:

[0007] The application displays the session interface of the target session, which includes the call identifier of the target micro-application, which runs on the application and is used to process files;

[0008] In response to the triggering of the call identifier of the target micro-application, a file selection interface of the target session is displayed, in which at least one file of the target session is displayed;

[0009] In response to any one of the at least one files being selected, the file is sent to the target micro-application.

[0010] On the one hand, a file sending method is provided, the method comprising:

[0011] The application selection interface is displayed in the application, which includes at least one candidate micro-application, and the at least one candidate micro-application runs on the application.

[0012] In response to the selection of a target micro-application among the at least one candidate micro-applications, a session selection interface for the application is displayed, the session selection interface including at least one session in the application, the target micro-application being used for file processing;

[0013] In response to the selection of a target session in the at least one session, a file selection interface for the target session is displayed, wherein at least one file of the target session is displayed in the file selection interface;

[0014] In response to any one of the at least one files being selected, the file is sent to the target micro-application.

[0015] In one possible implementation, displaying the file selection interface for the target session in response to the selection of the at least one session includes:

[0016] In response to the selection of a target session in the at least one session, the target file types supported by the target micro-application are determined;

[0017] At least one target file is determined from at least one file in the target session, wherein the file type of the target file is the target file type;

[0018] The at least one target file is displayed in the file selection interface of the target session.

[0019] In one possible implementation, in response to the selection of a target session in the at least one session, determining the target file types supported by the target micro-application includes:

[0020] In response to the selection of a target session in at least one session, the target micro-application sends an application interface call request to the application. The application interface call request is used to call the file retrieval interface of the application. The application interface call request carries the file filtering parameters of the target micro-application, which are used to indicate the target file types supported by the target micro-application.

[0021] Based on the file filtering parameters of the target micro-application, the target file type of the target micro-application is determined.

[0022] In one possible implementation, the application interface call request also carries the upper limit of the number of files that can be retrieved, and the method further includes:

[0023] The maximum number of files that can be retrieved is displayed in the file selection interface.

[0024] In one possible implementation, displaying the at least one target file in the file selection interface of the target session includes any of the following:

[0025] When the target file type is video and / or image, the at least one target file is displayed as a thumbnail in the file selection interface;

[0026] When the target file type is a reference file type, the at least one target file is displayed in a list in the file selection interface, and the reference file type is a file type other than video and image.

[0027] In one possible implementation, sending the file to the target microapplication in response to the selection of any one of the at least one file includes:

[0028] In response to the selection of any one of the at least one files, the cache state of the file is determined, the cache state indicating whether the file is stored on the electronic device running the application;

[0029] If the file is cached, the file is sent to the target micro-application.

[0030] In one possible implementation, the file selection interface includes a confirmation control, and sending the file to the target micro-application when the file's cache status is cached includes:

[0031] If the file is cached, a selection indicator will be displayed at the location of the file in the file selection interface;

[0032] In response to a click on the confirmation control in the file selection interface, the file is sent to the target micro-application.

[0033] In one possible implementation, the method further includes:

[0034] If the file's cache status is "caching in progress", the file is sent to the target micro-application in response to the file's cache status changing from "caching in progress" to "cached".

[0035] In one possible implementation, the method further includes:

[0036] If the file is not cached, download the file.

[0037] If the cache status of the file changes from uncached to cached, the file is sent to the target micro-application.

[0038] In one possible implementation, the method further includes:

[0039] The download progress of the file is displayed in the file selection interface.

[0040] In one possible implementation, the method further includes:

[0041] If the file cannot be downloaded successfully, a prompt message will be displayed to indicate that the file cannot be downloaded.

[0042] In one possible implementation, sending the file to the target micro-application includes:

[0043] The file information of the file is sent to the target micro-application, and the file information includes the storage location of the file on the electronic device running the application.

[0044] In one possible implementation, the method further includes any of the following:

[0045] Displays the progress of sending the file to the target micro-application;

[0046] If the file is successfully sent to the target micro-application, a success message is displayed, indicating that the file has been sent to the target micro-application.

[0047] In one possible implementation, after the method responds to the selection of any one of the at least one files and sends the file to the target micro-application, the method further includes:

[0048] The target micro-application displays a file processing interface, which includes the file.

[0049] On one hand, a file sending device is provided, the device comprising:

[0050] A session interface display module is used to display the session interface of the target session in the application. The session interface includes the call identifier of the target micro-application, which runs on the basis of the application and is used to process files.

[0051] The first file selection interface display module is used to display the file selection interface of the target session in response to the triggering of the call identifier of the target micro-application, wherein at least one file in the target session is displayed in the file selection interface;

[0052] A first sending module is configured to send the file to the target microapplication in response to the selection of any one of the at least one files.

[0053] In one possible implementation, the first file selection interface display module is configured to, in response to the triggering of the call identifier of the target micro-application, determine the target file type supported by the target micro-application; determine at least one target file from at least one file in the target session, wherein the file type of the target file is the target file type; and display the at least one target file in the file selection interface of the target session.

[0054] In one possible implementation, the first file selection interface display module is configured to respond to the triggering of the call identifier of the target micro-application, wherein the target micro-application sends an application interface call request to the application, the application interface call request being used to call the file acquisition interface of the application, the application interface call request carrying file filtering parameters of the target micro-application, the file filtering parameters being used to indicate the target file types supported by the target micro-application; and the target file type of the target micro-application is determined based on the file filtering parameters of the target micro-application.

[0055] In one possible implementation, the application interface call request also carries the maximum number of files that can be retrieved, and the first file selection interface display module is further used to display the maximum number of files that can be retrieved in the file selection interface.

[0056] In one possible implementation, the first file selection interface display module is configured to perform any of the following:

[0057] When the target file type is video and / or image, the at least one target file is displayed as a thumbnail in the file selection interface;

[0058] When the target file type is a reference file type, the at least one target file is displayed in a list in the file selection interface, and the reference file type is a file type other than video and image.

[0059] In one possible implementation, the first sending module is configured to, in response to the selection of any one of the at least one files, determine the cache state of the file, the cache state indicating whether the file is stored on the electronic device running the application; and if the cache state of the file is cached, send the file to the target micro-application.

[0060] In one possible implementation, the file selection interface includes a confirmation control, and the first sending module is configured to display a selection marker at the location of the file in the file selection interface when the file's cache status is cached; and to send the file to the target micro-application in response to a click operation on the confirmation control in the file selection interface.

[0061] In one possible implementation, the first sending module is further configured to send the file to the target micro-application in response to the file's cache status changing from being cached to being cached, provided that the file's cache status is currently being cached.

[0062] In one possible implementation, the first sending module is further configured to download the file when the file's cache status is uncached, and send the file to the target micro-application when the file's cache status changes from uncached to cached.

[0063] In one possible implementation, the device further includes:

[0064] The first download progress display module is used to display the download progress of the file in the file selection interface.

[0065] In one possible implementation, the device further includes:

[0066] The first prompt information display module is used to display a prompt information when the file is not successfully downloaded, the prompt information being used to indicate that the file cannot be downloaded.

[0067] In one possible implementation, the first sending module is configured to send file information of the file to the target micro-application, the file information including the storage location of the file on the electronic device running the application.

[0068] In one possible implementation, the device further includes any of the following:

[0069] The first sending progress display module is used to display the sending progress of sending the file to the target micro-application;

[0070] The first success message sending module is used to display a success message when the file is successfully sent to the target micro-application. The success message is used to indicate that the file has been sent to the target micro-application.

[0071] In one possible implementation, the device further includes:

[0072] The first file processing interface display module is used to display the file processing interface of the target micro-application, wherein the file processing interface includes the file.

[0073] On one hand, a file sending device is provided, the device comprising:

[0074] An application selection interface display module is used to display an application selection interface in an application. The application selection interface includes at least one candidate micro-application, and the at least one candidate micro-application runs on the application.

[0075] A session selection interface display module is used to display the session selection interface of the application in response to the selection of a target micro-application in the at least one candidate micro-application. The session selection interface includes at least one session in the application, and the target micro-application is used for processing files.

[0076] The second file selection interface display module is used to display the file selection interface of the target session in response to the selection of the target session in the at least one session. The file selection interface displays at least one file of the target session.

[0077] The second sending module is configured to send the file to the target microapplication in response to the selection of any one of the at least one files.

[0078] In one possible implementation, the second file selection interface display module is configured to, in response to the selection of a target session in the at least one session, determine the target file type supported by the target micro-application; determine at least one target file from at least one file in the target session, wherein the file type of the target file is the target file type; and display the at least one target file in the file selection interface of the target session.

[0079] In one possible implementation, the second file selection interface display module is configured to, in response to the selection of a target session in the at least one session, send an application interface call request to the application, the application interface call request being used to call the application's file retrieval interface, the application interface call request carrying file filtering parameters of the target micro-application, the file filtering parameters being used to indicate the target file types supported by the target micro-application; and determine the target file type of the target micro-application based on the file filtering parameters of the target micro-application.

[0080] In one possible implementation, the application interface call request also carries the maximum number of files that can be retrieved, and the second file selection interface display module is further used to display the maximum number of files that can be retrieved in the file selection interface.

[0081] In one possible implementation, the second file selection interface display module is configured to perform any of the following:

[0082] When the target file type is video and / or image, the at least one target file is displayed as a thumbnail in the file selection interface;

[0083] When the target file type is a reference file type, the at least one target file is displayed in a list in the file selection interface, and the reference file type is a file type other than video and image.

[0084] In one possible implementation, the second sending module is configured to, in response to the selection of any one of the at least one files, determine the cache state of the file, the cache state indicating whether the file is stored on the electronic device running the application; and if the cache state of the file is cached, send the file to the target micro-application.

[0085] In one possible implementation, the file selection interface includes a confirmation control, and the second sending module is configured to display a selection marker at the location of the file in the file selection interface when the file's cache status is cached; and to send the file to the target micro-application in response to a click operation on the confirmation control in the file selection interface.

[0086] In one possible implementation, the second sending module is further configured to send the file to the target microapplication in response to the file's cache status changing from being cached to being cached, if the file's cache status is currently being cached.

[0087] In one possible implementation, the second sending module is further configured to download the file when the file's cache state is uncached, and send the file to the target micro-application when the file's cache state changes from uncached to cached.

[0088] In one possible implementation, the method further includes:

[0089] The second download progress display module is used to display the download progress of the file in the file selection interface.

[0090] In one possible implementation, the device further includes:

[0091] The second prompt message display module is used to display a prompt message when the file is not successfully downloaded, the prompt message indicating that the file cannot be downloaded.

[0092] In one possible implementation, the second sending module is used to send file information of the file to the target micro-application, the file information including the storage location of the file on the electronic device running the application.

[0093] In one possible implementation, the device further includes any of the following:

[0094] The first sending progress display module is used to display the sending progress of sending the file to the target micro-application;

[0095] The first success message sending module is used to display a success message when the file is successfully sent to the target micro-application. The success message is used to indicate that the file has been sent to the target micro-application.

[0096] In one possible implementation, the device further includes:

[0097] The first file processing interface display module is used to display the file processing interface of the target micro-application, wherein the file processing interface includes the file.

[0098] On one hand, a computer device is provided, the computer device including one or more processors and one or more memories, the one or more memories storing at least one computer program, the computer program being loaded and executed by the one or more processors to implement the file sending method.

[0099] On one hand, a computer-readable storage medium is provided, wherein at least one computer program is stored in the computer-readable storage medium, the computer program being loaded and executed by a processor to implement the file sending method.

[0100] On one hand, a computer program product or computer program is provided, which includes program code stored in a computer-readable storage medium. A processor of a computer device reads the program code from the computer-readable storage medium and executes the program code, causing the computer device to perform the above-described file sending method.

[0101] The solution provided in this application provides a call identifier for the target micro-application within the application's session interface. When this call identifier is triggered, a file selection interface is displayed, showing files from the target session—that is, files shared within the target session. By directly selecting a file from this interface, the file can be quickly sent to the target micro-application for processing. This process simplifies the workflow for sending files to the target micro-application and improves the efficiency of human-computer interaction. Attached Figure Description

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

[0103] Figure 1 is a schematic diagram of an implementation environment provided in an embodiment of this application;

[0104] Figure 2 is a flowchart of a file sending method provided in an embodiment of this application;

[0105] Figure 3 is a flowchart of a file sending method provided in an embodiment of this application;

[0106] Figure 4 is a schematic diagram of a session selection interface provided in an embodiment of this application;

[0107] Figure 5 is a schematic diagram of a session interface provided in an embodiment of this application;

[0108] Figure 6 is a schematic diagram of another session interface provided in an embodiment of this application;

[0109] Figure 7 is a schematic diagram of another session interface provided in an embodiment of this application;

[0110] Figure 8 is a schematic diagram of a file selection interface provided in an embodiment of this application;

[0111] Figure 9 is a schematic diagram of another file selection interface provided in an embodiment of this application;

[0112] Figure 10 is a flowchart of a file sending method provided in an embodiment of this application;

[0113] Figure 11 is a flowchart of a file sending method provided in an embodiment of this application;

[0114] Figure 12 is a schematic diagram of a display interface provided in an embodiment of this application;

[0115] Figure 13 is a flowchart of a file sending method provided in an embodiment of this application;

[0116] Figure 14 is a schematic diagram of a file sending device provided in an embodiment of this application;

[0117] Figure 15 is a schematic diagram of a file sending device provided in an embodiment of this application;

[0118] Figure 16 is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0119] Figure 17 is a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

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

[0121] It should be noted that the information (including but not limited to user equipment information, user personal information, etc.), data (including but not limited to data used for analysis, data stored, data displayed, etc.) and signals (including but not limited to signals transmitted between user terminals and other devices) involved in this application have all been fully authorized by the user or relevant parties, and the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.

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

[0123] To provide a clearer explanation of the technical solutions provided in the embodiments of this application, some terms involved in the embodiments of this application will be explained below.

[0124] Mini-applications, also known as WeChat Mini Programs, are a type of application that can be used without downloading or installing. They realize the dream of "applications at your fingertips," allowing users to open the application simply by scanning a QR code or searching for it. In some embodiments, mini-applications are also referred to as embedded applications.

[0125] Service providers: Third-party application providers and service providers that provide users with third-party applications and related services. Service providers include, but are not limited to, application agents, technical support service providers, and hardware service providers engaged in related businesses by third-party application providers.

[0126] Figure 1 is a schematic diagram of an implementation environment provided by an embodiment of this application. Referring to Figure 1, the implementation environment may include a terminal 110 and a server 140.

[0127] Terminal 110 is connected to server 140 via a wireless or wired network. Optionally, terminal 110 may be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. Terminal 110 has applications installed and running that support file sending and receiving as well as micro-application invocation.

[0128] Server 140 is a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, Content Delivery Network (CDN), and big data and artificial intelligence platforms. Server 140 provides background services for applications running on terminal 110.

[0129] Optionally, terminal 110 refers to one of a plurality of terminals. This application embodiment only uses terminal 110 as an example for illustration.

[0130] After introducing the implementation environment of the file sending method provided in the embodiments of this application, the application scenarios of the file sending method provided in the embodiments of this application will be introduced below. It should be noted that in the following description, the terminal is the terminal 110 in the above implementation environment, and the server is the server 140 in the above implementation environment.

[0131] The file sending method provided in this application embodiment can be applied to scenarios where various types of files are processed. For example, the file sending method provided in this application embodiment can be applied to scenarios where images are processed, or where videos are processed, or where documents are processed, or where compressed files are processed, and so on.

[0132] Taking the file sending method provided in this application embodiment as an example in a scenario involving image processing, users can engage in conversations through social applications running on their terminals. During these conversations, file sharing may occur; for example, a user might share an image with another user. In some cases, users need to process the files shared during the conversation. Using the technical solution provided in this application embodiment, in response to the user's operation, the terminal can directly launch a micro-application within the conversation interface. This micro-application runs on top of the application and is an image processing application used to process images. This conversation interface is also the conversation interface of the target conversation. The terminal displays a file selection interface for the target conversation. This file selection interface is used to select images to be sent to the micro-application, i.e., images to be processed by the micro-application. The file selection interface displays at least one image from the target conversation, where at least one image refers to an image shared by the user in the target conversation. When any image is selected through the file selection interface, the terminal sends the selected image to the micro-application, which then processes the image. In some embodiments, the micro-application processes the image by drawing on it, adding graphics, cutting out the image, or changing parameters such as contrast, brightness, and color temperature. When a user needs to perform these processing steps on an image in a conversation, the image processing functions provided by the micro-application can achieve this quickly and efficiently.

[0133] It should be noted that the above description is based on the application of the file sending method provided in the embodiments of this application to the scenario of image processing. In other scenarios, the process of applying the technical solution provided in the embodiments of this application belongs to the same inventive concept as described above, and will not be repeated here.

[0134] In addition, the file sending method provided in this application embodiment can be applied not only to the scenarios of processing images, videos, documents, and compressed files, but also to scenarios of processing other types of files. This application embodiment does not limit this application.

[0135] After introducing the implementation environment and application scenarios of the embodiments of this application, the file sending method provided by the embodiments of this application will be described below. Referring to Figure 2, taking the terminal as the executing subject as an example, the method includes:

[0136] 201. The terminal displays the session interface of the target session in the application. The session interface includes the call identifier of the target micro-application, which runs on the basis of the application and is used to process files.

[0137] The application refers to an application that supports conversational functionality, such as an instant messaging application within a social application, or other types of social applications. A target conversation refers to a conversation between the currently logged-in account on the application and at least one other account. The target micro-application running on the application means that the target micro-application is a sub-application of the application; correspondingly, the application is the parent application of the target micro-application. The parent application can run independently on the terminal, while the sub-application cannot run independently on the terminal; the sub-application's operation depends on the parent application, or in other words, the sub-application runs on the basis of the parent application. File processing includes operations such as editing file content, converting file formats, and sharing files. The target micro-application and the application are provided with backend services by different servers. In some embodiments, the server providing backend services for the target micro-application is also referred to as the service provider of the target micro-application. In some embodiments, the micro-application is also referred to as a mini-program, which can run on the application's client without downloading. In some embodiments, the target micro-application is a file processing application.

[0138] 202. In response to the triggering of the call identifier of the target micro-application, the terminal displays a file selection interface for the target session, which displays at least one file from the target session.

[0139] The file selection interface is used to select the file to be sent to the target micro-application. At least one file in the target session refers to a file sent during the target session. This file may be sent from the currently logged-in account on the application to another account, or it may be sent from another account to the currently logged-in account on the application. This application embodiment does not limit this.

[0140] 203. In response to the selection of any one of the at least one files, the terminal sends that file to the target micro-application.

[0141] The process of selecting a file from at least one file is also the process of selecting a file to send to the target micro-application.

[0142] The solution provided in this application provides a call identifier for the target micro-application within the application's session interface. When this call identifier is triggered, a file selection interface is displayed, showing files from the target session—that is, files shared within the target session. By directly selecting a file from this interface, the file can be quickly sent to the target micro-application for processing. This process simplifies the workflow for sending files to the target micro-application and improves the efficiency of human-computer interaction.

[0143] Steps 201-203 above are a simplified description of the embodiments of this application. The technical solutions provided by the embodiments of this application will be explained more clearly below with reference to some examples. Referring to Figure 3, the method includes:

[0144] 301. The terminal displays the application's session selection interface, which includes multiple candidate sessions.

[0145] The session selection interface is provided by the application for selecting sessions. Multiple candidate sessions represent conversations between the currently logged-in account and several other accounts. In some embodiments, the application is a social application, a dedicated application supporting micro-applications, an email application, or a game application, etc. Social applications include instant messaging applications, SNS (Social Network Service) applications, or live streaming applications, etc. In the case of an instant messaging application, this session selection interface is also referred to as the application's main interface.

[0146] For example, referring to Figure 4, the terminal displays the session selection interface 401 of the application, which includes multiple candidate sessions 402.

[0147] 302. In response to the selection of a target session among the multiple candidate sessions, the terminal displays the session interface of the target session in the application. The session interface includes the call identifier of the target micro-application, which runs on the application and is used to process files.

[0148] The target session's interface is also referred to as the chat interface, through which users can chat with other users. In some embodiments, the target micro-application is identified by a micro-application invocation control, which allows for quick invocation of the target micro-application. The type of the target micro-application is related to the type of the file to be processed.

[0149] In one possible implementation, in response to a click operation on a target session among multiple candidate sessions, the terminal determines the number of times the target micro-application is invoked within a target time period. If the number of invocations of the target micro-application within the target time period meets the invocation count condition, the terminal displays the invocation identifier of the target micro-application in the session interface while displaying the session interface.

[0150] The requirement that the number of calls to the target micro-application within the target time period meets the call count condition means that the number of calls to the target micro-application within the target time period is greater than or equal to the call count threshold. The target time period is set by technical personnel according to the actual situation, and this application embodiment does not limit it. For example, the target time period may be set to 3 days or 5 days.

[0151] In this implementation, if the number of times the target micro-application is called within the target time period is greater than or equal to the number of times it is called, it means that the target micro-application is called frequently and the user uses the target micro-application frequently. Therefore, the call identifier of the target micro-application is displayed in the session interface so that the user can directly call the target micro-application in the session interface, thereby improving the efficiency of human-computer interaction.

[0152] In one possible implementation, in response to a click operation on a target session among a plurality of candidate sessions, the terminal obtains the micro-application configuration information corresponding to the target session. This micro-application configuration information indicates the micro-applications that are bound to the target session. If the micro-application configuration information of the target session indicates a binding relationship between the target micro-application and the target session, the terminal displays the call identifier of the target micro-application in the session interface while simultaneously displaying the session interface.

[0153] The micro-application configuration information is added by the user for the target session. For example, if the user configures multiple micro-applications for the target session, the terminal generates the micro-application configuration information based on the user's configuration of multiple micro-applications for the target session.

[0154] In this implementation, users can configure micro-applications displayed in the session interface for the target session themselves, which enriches user choices and enhances user autonomy.

[0155] In one possible implementation, in response to a click operation on a target session among a plurality of candidate sessions, the terminal determines the type of the target session. If the type of the target session is a target type, the terminal displays the session interface and simultaneously displays the invocation identifier of the target micro-application in the session interface; the target micro-application is a micro-application bound to the target type.

[0156] The type of the target session is determined by the user who creates the target session. The target type is set by the technician according to the actual situation. For example, the technician can set the target type to a work session. When the target session type is a work session, the terminal can display the target micro-application that is bound to the work session in the session interface, making it convenient for the user to call the micro-application.

[0157] Next, we will explain the display location of the call identifier of the target micro-application in the session interface.

[0158] In some embodiments, the session interface includes a first functional area, a second functional area, and a third functional area. The first functional area displays the session name, a return control, and a session information viewing control for the target session. The return control controls the terminal to display a session selection interface, and the session information viewing control displays relevant account information, such as the account's nickname, contact information, and type. The second functional area is the session display area, where the content of the target session is displayed. The third functional area includes a session input area and function controls. The session input area is used to input session content, and the function controls have different functions depending on the settings of the technician; for example, the function controls provide the function of sending files in the target session. Of course, the above description of the session interface is only one possible form. In other possible implementations, the session interface may have other forms, which are not limited in this application. The call identifier of the target micro-application can be displayed in the first, second, or third functional area. For example, referring to Figure 5, the terminal displays the session interface 501 of the target session, which includes a first functional area 502, a second functional area 503, and a third functional area 504.

[0159] The following describes how the terminal displays the call identifier of the target micro-application in the first, second, and third functional areas, respectively.

[0160] In some embodiments, when the number of times the target micro-application is invoked within a target time period is greater than or equal to a threshold, the terminal displays the invocation identifier of the target micro-application in the first functional area of ​​the session interface of the target session. In this case, the invocation identifier of the target micro-application is an invocation control of the target micro-application, which is displayed as an icon of the target micro-application. Clicking the invocation control can trigger the launch of the target micro-application.

[0161] If the number of times the target micro-application is called within the target time period is greater than or equal to the call count threshold, it means that the target micro-application is called frequently and users use it frequently. Since the first functional area is prominently located, displaying the call identifier of the target micro-application in the first functional area makes it convenient for users to directly call the target micro-application, thus improving the efficiency of human-computer interaction.

[0162] For example, referring to Figures 4 and 5, in response to a click operation on a target session 403 among multiple candidate sessions 402, the terminal displays the session interface 501 of the target session, and the call identifier 505 of the target micro-application is displayed in the first functional area 502 of the session interface 501.

[0163] In some embodiments, when any party in the target session shares the target micro-application within the target session, the terminal displays the invocation identifier of the target micro-application in a second functional area of ​​the session interface of the target session. Sharing the target micro-application within the target session means sending the invocation identifier of the target micro-application within the target session, allowing all participants in the target session to launch the target micro-application by triggering the invocation identifier. In this case, the invocation identifier of the target micro-application is an invocation card displaying a promotional image of the target micro-application, including its name and functional description. Clicking the invocation card triggers the launch of the target micro-application.

[0164] In this scenario, users can share the target micro-application within the target session. After sharing, the invocation identifier of the target micro-application will be displayed in the session interface of the target session. All participants in the target session can quickly launch the target micro-application through the invocation identifier, resulting in high efficiency of human-computer interaction.

[0165] For example, referring to Figures 4 and 6, in response to a click operation on a target session 403 among multiple candidate sessions 402, the terminal displays the session interface 601 of the target session, and the call identifier 602 of the target micro-application is displayed in the second functional area 603 of the session interface 601.

[0166] In some embodiments, in response to a click operation on a function control in the third functional area of ​​the session interface, the terminal displays a function display pop-up window corresponding to the function control, which includes a micro-application selection control. In response to a click operation on the micro-application selection control, the terminal displays a micro-application display pop-up window, which includes call identifiers for multiple candidate micro-applications, including the target micro-application. In this case, the call identifier for the target micro-application is a call control for the target micro-application, and the call control is displayed as an icon of the target micro-application. Clicking the call control triggers the launch of the target micro-application.

[0167] In this case, the application provides a function control in the third function control, through which the user can trigger the call control to display the target micro-application, resulting in high efficiency of human-computer interaction.

[0168] For example, referring to Figures 4 and 7, in response to a click operation on a target session 403 among multiple candidate sessions 402, the terminal displays a session interface 701 for the target session. This session interface 701 includes a third functional area 702, which includes functional controls 703. In response to a click operation on the functional control 703, the terminal displays a function display pop-up window 704, which includes a micro-application selection control 705. In response to a click operation on the micro-application selection control 705, the terminal displays a micro-application display pop-up window 706, which includes a call identifier 707 for the target micro-application.

[0169] 303. In response to the triggering of the call identifier of the target micro-application, the terminal displays a file selection interface for the target session, which displays at least one file from the target session.

[0170] In this context, at least one file in the target session refers to a file shared in the target conversation, and the file selection interface is used to display the files in the target session.

[0171] In one possible implementation, in response to the triggering of the call identifier of the target micro-application, the terminal filters multiple messages in the target session based on a target format to obtain at least one file in the target session. The target format includes both text message and voice message formats. In some embodiments, the text message format is SQLite (a lightweight database format), and the voice message format is AMR (an audio format) or AUD (a variant of AMR). That is, during the process of filtering multiple messages in the target session based on the target format, the terminal can identify messages other than those in the target format as files in the target session. The terminal then displays at least one file from the target session in a file selection interface.

[0172] In one possible implementation, if the application stores files received in a session in a file database, in response to the triggering of the target micro-application's call identifier, the terminal queries the file database based on the identifier of the target session to obtain at least one file from the target session. The terminal then displays at least one file from the target session in a file selection interface.

[0173] It should be noted that the terminal can obtain at least one file in the target session through any of the above methods, and this application embodiment does not limit this. The following describes the process by which the terminal filters at least one file in the target session based on the target file types supported by the target micro-application.

[0174] In one possible implementation, in response to a call identifier of the target micro-application being triggered, the terminal determines the target file types supported by the target micro-application. The terminal determines at least one target file from at least one file in the target session, the target file being of the specified file type. The terminal displays the at least one target file in a file selection interface within the target session. The target file types supported by the target micro-application are determined based on the interaction between the target micro-application and the application.

[0175] In this implementation, before displaying the file selection interface, the terminal filters the files in the target session according to the file types supported by the target micro-application. Only the target files supported by the target micro-application are displayed in the file selection interface, thereby avoiding subsequent misoperations in the file selection interface and improving the efficiency of human-computer interaction.

[0176] To provide a clearer explanation of the above embodiments, the following description is divided into two parts.

[0177] Part 1: In response to the triggering of the call identifier of the target micro-application, the terminal determines the target file types supported by the target micro-application.

[0178] In one possible implementation, in response to the triggering of the call identifier of the target micro-application, the target micro-application sends an application interface call request to the application. This request invokes the application's file retrieval interface and carries file filtering parameters indicating the target file types supported by the target micro-application. The terminal determines the target file type of the target micro-application based on these file filtering parameters.

[0179] The file retrieval interface is an interface provided by the application to the micro-application, used to retrieve files from the application. In some embodiments, before the target micro-application can call the file retrieval interface, it needs to request permission from the application to do so. Once the application grants permission, the target micro-application can retrieve files from the application through the file retrieval interface. In some embodiments, the file filtering parameters of the target micro-application are provided by the service provider to the target micro-application. These parameters are associated with the functionality of the target micro-application. Since the functionality of the target micro-application may be updated with version updates, the file filtering parameters will also be updated accordingly. The service provider can update the file filtering parameters when updating the version of the target micro-application. For example, if the previous version of the target micro-application supported image editing, then the file filtering parameters of that version indicated that the supported file type was image. If the current version of the target micro-application supports both image and video editing, then the file filtering parameters of that version indicate that the supported file types are both image and video.

[0180] For example, in response to a click on the identifier of the target micro-application, the target micro-application sends an application interface call request to the application. This request carries the target micro-application's file filtering parameters and its identifier. The application determines the target micro-application's permission to access the file's interface based on its identifier. If the application determines it has permission, the terminal determines the target file type based on the file filtering parameters. If the application determines it does not have permission, the terminal displays a permission request pop-up in the application. This pop-up includes an authorization control and a denial control. The authorization control confirms granting the target micro-application permission to access the file's interface; the denial control denies granting permission. In response to a click on the authorization control, the application grants the target micro-application permission to access the file's interface. The terminal then determines the target file type based on the target micro-application's file filtering parameters.

[0181] Part Two: The terminal determines at least one target file from at least one file in the target session, wherein the file type of the target file is the target file type.

[0182] In one possible implementation, the terminal filters at least one file in the target session based on the target file type to obtain at least one target file, where the file type of the at least one target file is the target type. Since the target type is a file type supported by the target micro-application, the at least one target file is also a file supported by the target micro-application.

[0183] Part Three: The terminal displays at least one target file in the file selection interface of the target session.

[0184] In some embodiments, the at least one target file in the file selection interface is displayed in reverse chronological order, that is, the most recently received file in the target session is displayed at the beginning of the file selection interface, and the latest received file in the target session is displayed at the end of the file selection interface, which makes it easier for the user to select.

[0185] In one possible implementation, if the target file type is video and / or image, the terminal displays the at least one target file as a thumbnail in the file selection interface.

[0186] The target file type being video and / or image includes three cases: target file type is video, target file type is image, and target file type is both image and video. In the case of a target file type being image, the thumbnail is also a thumbnail of the image. In the case of a target file type being video, the thumbnail is a thumbnail of the video's cover image or a thumbnail of the first frame of the video. In some embodiments, when the target file type is video, the terminal also displays the video duration in the video thumbnail. In some embodiments, when the target file type is both image and video, the terminal also displays a video identifier in the video thumbnail to distinguish it from the image.

[0187] In this situation, since images and videos are visual, displaying them as thumbnails in the file selection interface can intuitively inform you of the content of the selected image or video, reducing the probability of selecting the wrong image or video.

[0188] When the target file type is an image or a video, referring to Figure 8, the terminal displays a file selection interface 801 for the target session. This interface 801 includes multiple thumbnails, each corresponding to an image and video, respectively. For example, thumbnail 802 corresponds to an image, and thumbnail 803 corresponds to a video. In some embodiments, the thumbnail corresponding to a video displays a video identifier and the video's duration.

[0189] In some embodiments, the thumbnails are arranged in reverse chronological order, meaning that at least one file in the file selection interface is arranged from left to right and from top to bottom. For example, the terminal displays the most recently received file in the target session in the upper left corner of the file selection interface, and the latest received file in the target session in the lower right corner of the file selection interface.

[0190] In some embodiments, in response to a press operation on any thumbnail displayed in the file selection interface, the terminal enlarges the thumbnail. Here, a press operation refers to a touch operation on the thumbnail with a touch duration greater than or equal to a duration threshold, which is set by a technician according to actual conditions; this embodiment does not limit this. In this implementation, a function is provided to trigger thumbnail enlargement through a press operation, allowing the user to more clearly understand the content of the thumbnail through the enlarged thumbnail, facilitating selection.

[0191] In one possible implementation, when the target file type is a reference file type, the terminal displays the at least one target file in a list in the file selection interface, where the reference file type is a file type other than video and image.

[0192] The reference file types include documents, compressed files, and executable programs.

[0193] In this implementation, since reference file types may not have visual features, displaying them in a list format can more intuitively inform users of relevant file information, making it easier for them to make selections.

[0194] When the target file type is a reference file type, as shown in Figure 9, the terminal displays the file selection interface 901 of the target session. The file selection interface 901 includes multiple rows, each corresponding to a file, and these multiple rows constitute a list of the files displayed.

[0195] In some embodiments, each line corresponding to a file displays file information, which includes at least one of the following: file icon, file name, file size, file sender, and file reception time. The file icon is associated with the file type. In this implementation, the file information displayed in each line assists the user in file selection, improving the efficiency of human-computer interaction.

[0196] In some embodiments, a file viewing control is also displayed in each line corresponding to the file. In response to clicking the file viewing control, the terminal displays the file content corresponding to that line. In this implementation, clicking the file viewing control can trigger the terminal to display the file content, making it easier for users to select files and improving the efficiency of human-computer interaction.

[0197] In some embodiments, the multiple columns in the list are arranged in reverse chronological order, that is, at least one file in the file selection interface is displayed in a top-to-bottom order, with the column containing the most recently received file at the top and the column containing the earliest received file at the bottom.

[0198] In one possible implementation, when the target file type includes images and / or videos as well as reference file types, the terminal displays the at least one target file in a list in the file selection interface, where the reference file type is a file type other than video and images.

[0199] The target file type includes images and / or videos, and the reference file type includes three cases: the target file type includes images and reference file types, the target file type includes videos and reference file types, and the target file type includes images, videos, and reference file types.

[0200] In some embodiments, the application interface call request also carries the maximum number of files that can be retrieved, and the terminal displays this maximum number of files in the file selection interface.

[0201] The maximum number of files that a target micro-application can retrieve in a single instance refers to the maximum number of files that the target micro-application can retrieve from the application. In some embodiments, this maximum number of files is set by the service provider of the target micro-application, and the maximum number of files that the target micro-application can retrieve may be updated with version updates.

[0202] For example, as shown in Figure 8, the application interface call request also carries the maximum number of files that can be retrieved, and the terminal displays this maximum number of files in the file selection interface 801 804.

[0203] In some embodiments, in addition to displaying the maximum number of files to be acquired in the file selection interface, the terminal can also display the number of selected files in the file selection interface. The number of selected files is the number of files to be sent to the target micro-application. By displaying the number of selected files and the maximum number of files to be acquired, users can intuitively understand the difference between the number of selected files and the maximum number of files to be acquired, making it easier for users to select files.

[0204] 304. In response to the selection of any one of the at least one files, the terminal sends that file to the target micro-application.

[0205] In one possible implementation, in response to the selection of any one of the at least one files, the terminal determines the cache state of that file, which indicates whether the file is stored on the electronic device running the application. If the file's cache state is cached, the terminal sends the file to the target micro-application. The electronic device running the application is also known as the terminal.

[0206] For example, in response to a click on any of the at least one files, the terminal searches for that file in its storage space based on its identifier. The file selection interface includes a confirmation control; if the file is cached (i.e., found in the terminal's storage space), the terminal displays a selection indicator at the file's location in the file selection interface. In response to a click on the confirmation control in the file selection interface, the terminal sends the file to the target micro-application. In some embodiments, the file selection interface also displays the number of selected files.

[0207] For example, if the file type of at least one file includes images and videos, referring to Figure 8, in response to a click on any thumbnail 802 among multiple thumbnails, the terminal searches its storage space based on the identifier of the image corresponding to that thumbnail. If the image corresponding to the thumbnail 802 is found in the terminal's storage space, the terminal displays a selection identifier 806 on the thumbnail 802. The file selection interface 801 includes a confirmation control 805. In response to a click on the confirmation control 805, the terminal sends the image corresponding to the thumbnail 802 to the target micro-application. In some embodiments, the confirmation control 805 displays the number of selected files.

[0208] When the file type of at least one file is a reference file type, referring to Figure 9, in response to a click operation on any row 902 of the multiple rows in the file selection interface 901, the terminal searches its storage space based on the identifier of the file corresponding to that row 902. If the file corresponding to that row 902 is found in the terminal's storage space, the terminal displays a selection identifier 903 at the end of that row 902. The file selection interface 901 includes a confirmation control 904. In response to a click operation on the confirmation control 904, the terminal sends the file corresponding to that row 902 to the target micro-application. In some embodiments, the confirmation control 904 displays the number of selected files.

[0209] It should be noted that the above explanation is based on the case where the file is cached. In other possible implementations, the terminal may also perform the following steps:

[0210] In one possible implementation, if the file's cache status is "caching", in response to the file's cache status changing from "caching" to "cached", the terminal sends the file to the target micro-application.

[0211] In this context, a file's cache status being "cached" means that the terminal is downloading the file, but the download is not yet complete. In some embodiments, the confirmation of the "cached" status is determined by the terminal based on the application's current download thread. That is, it is based on the file's identifier, which is queried within the download thread. If the file is found in the download thread, it indicates that the file's cache status is "cached."

[0212] For example, if the file's cache status is "caching in progress," in response to the file's cache status changing from "caching in progress" to "cached," the terminal displays a selection icon at the file's location in the file selection interface. This file selection interface includes a confirmation control; in response to clicking the confirmation control in the file selection interface, the terminal sends the file to the target micro-application.

[0213] In one possible implementation, if the file is not cached, the terminal downloads the file. If the file's cache status changes from not cached to cached, the terminal sends the file to the target micro-application.

[0214] For example, if a file is not cached (meaning it's not found in the terminal's storage), the terminal sends a download request to the server. This request carries the file's identifier and is used to request the download of that file. Upon receiving the download request, the server retrieves the file's identifier from it and sends the file to the terminal based on that identifier. The terminal then downloads the file. Once the download is complete, the file's cache status changes from uncached to cached. The terminal displays a selection icon next to the file in the file selection interface. This selection interface includes a confirmation control; in response to clicking the confirmation control, the terminal sends the file to the target micro-application.

[0215] Based on the above implementation methods, in some embodiments, the terminal displays the download progress of the file in the file selection interface.

[0216] The download progress can be displayed as a percentage or as a static graphic filled with a dynamic graphic. The dynamic graphic is nested within the static graphic, with one end fixed to the other. The length of the dynamic graphic is directly proportional to the download progress, while the other end of the dynamic graphic expands within the static graphic as the download progress increases. For example, the static graphic could be a blank rectangle, and the dynamic graphic a colored, expandable rectangle; or the static graphic could be a blank circle, and the dynamic graphic a sector whose area changes with the download progress.

[0217] In some embodiments, if the file cannot be downloaded successfully, the terminal displays a prompt message indicating that the file cannot be downloaded.

[0218] The reasons for the unsuccessful download of the file are as follows: 1) The file was actively deleted by the server after its storage time on the server exceeded the storage time threshold. The storage time threshold is set by technical personnel according to the actual situation, such as 7 days, 15 days, or 30 days; 2) The file was actively deleted by the user even though its storage time on the server did not exceed the storage time threshold; 3) The file was actively deleted by the server when it detected abnormal information, including viruses or other information that violates laws and regulations.

[0219] This message indicates that the file cannot be downloaded because it was actively deleted by the server after its storage duration exceeded the storage duration threshold.

[0220] The following describes the method by which the terminal sends the file to the target micro-application in each of the above embodiments.

[0221] In one possible implementation, the terminal sends the file information of the file to the target micro-application, the file information including the storage location of the file on the electronic device running the application.

[0222] In this implementation, the electronic device running the application refers to the terminal. Instead of sending the file directly to the target micro-application, the terminal sends the file's storage location on the terminal, avoiding duplicate storage of the file on the terminal and reducing storage space usage.

[0223] For example, if any of the at least one file is selected, the terminal stores the file information of that file in a cache. The file selection interface includes a confirmation control, and in response to a click on the confirmation control, the terminal sends the cached file information to the target micro-application.

[0224] In some embodiments, the file information includes, in addition to the file's storage location on the electronic device running the application, at least one of the following: the file's name, storage space occupied, creation time, and file type. This information helps the target micro-application process the file.

[0225] In some embodiments, during the process of sending the file to the target micro-application, the terminal displays the sending progress of sending the file to the target micro-application.

[0226] The sending progress can be displayed in two ways: as a percentage of the sending progress or as the number of files sent / the total number of files to be sent.

[0227] When there are multiple files, displaying the file sending progress can intuitively inform the user of the file sending progress, resulting in high efficiency of human-computer interaction.

[0228] In some embodiments, if the file is successfully sent to the target micro-application, the terminal displays a success message indicating that the file has been sent to the target micro-application.

[0229] In some embodiments, when the terminal sends the file information of the file to the target micro-application, and the file is being cached as described above in the implementation, the terminal can also perform the following steps.

[0230] In one possible implementation, if the file is being cached, the terminal determines the cache location of the file and generates file information based on that cache location. The cache location is also the location where the file was stored when the terminal downloaded it. The terminal then sends the file information to the target micro-application.

[0231] In this implementation, when the file is in a cached state, the terminal can send the file information of the file to the target micro-application in advance, thereby improving the efficiency of sending file information.

[0232] 305. The terminal displays the file processing interface of the target micro-application, which includes the file.

[0233] The file processing interface is a functional interface provided by the target micro-application, which displays multiple files sent to the target micro-application.

[0234] In one possible implementation, upon receiving the file, the terminal displays a micro-application launch control on the application's file selection interface. This launch control is used to launch the target micro-application within the application upon triggering a click on it. In response to a click on the launch control, the terminal displays the file processing interface of the target micro-application.

[0235] In some embodiments, the target micro-application receiving the file includes three cases: the first case is that the target micro-application receives the file; the second case is that the cache status of the file is cached and the target micro-application receives the file information of the file; and the third case is that the cache status of the file is being cached, the target micro-application receives the file information of the file, and then the cache status of the file changes from being cached to being cached.

[0236] The display format and position of the micro-application launch control are set by technicians according to the actual situation, and this application embodiment does not limit this.

[0237] In this implementation, when the application successfully sends the file to the target micro-application, the terminal can display a micro-application launch control for secondary confirmation. Clicking the micro-application launch control means that the user confirms the launch of the target micro-application. At this time, the terminal can launch the target micro-application in the application, which reduces the probability of the target micro-application being launched accidentally.

[0238] Furthermore, based on the above implementation, when the application sends file information of the file to the target micro-application, and the file's cache status is "caching," and the cache status changes from "caching" to "cached," the terminal displays a micro-application launch control on the application's file selection interface. This micro-application launch control is used to launch the target micro-application when triggered within the application. In response to clicking the micro-application launch control, the terminal displays the file processing interface of the target micro-application.

[0239] In one possible implementation, when the target micro-application receives the file, the terminal directly displays the file processing interface of the target micro-application.

[0240] In this implementation, once the application successfully sends the file to the target micro-application, the terminal can directly launch the target micro-application within the application without requiring any further user intervention, resulting in high efficiency in human-computer interaction.

[0241] For example, the terminal determines the status of the target micro-application receiving the file. If the target micro-application receives the file, the terminal switches the file processing interface of the target micro-application to the file processing interface.

[0242] Furthermore, based on the above implementation, when the application sends the file information of the file to the target micro-application and the file's cache status is "caching in progress," and the file's cache status changes from "caching in progress" to "cached," the terminal directly displays the file processing interface of the target micro-application.

[0243] The following is a further explanation of the method for displaying the file processing interface of the target micro-application on the terminal in the two embodiments described above.

[0244] In some embodiments, when the application directly sends the file to the target micro-application, the target micro-application displays the file in its file processing interface based on the file's storage location. For example, the target micro-application reads the file based on its storage location and displays an icon for the file in the file processing interface, where the icon points to the file's storage location. In this case, the file icon displayed in the file processing interface acts as a shortcut to the file; in response to clicking the file icon, the target micro-application can load the file into its application for processing based on the file information.

[0245] Based on the above embodiments, optionally, the target micro-application can also display at least one of the following on the file's icon: file name, space occupied, creation time, and file type, thereby providing users with richer information so that users can distinguish and call files.

[0246] In some embodiments, when the application sends file information of a file to the target micro-application, the target micro-application can read the file information and display the file in the file processing interface based on the storage location carried in the file information. For example, the target micro-application can read the file information and display an icon of the file in the file processing interface based on the storage location carried in the file information, with the file icon pointing to the storage location carried in the file information.

[0247] Based on the above embodiments, optionally, if the file information also includes at least one of the file name, space occupied, creation time, and file type, the target micro-application can also display at least one of the file name, space occupied, creation time, and file type on the file icon.

[0248] It should be noted that the terminal can trigger the display of the file processing interface of the target micro-application through any of the above methods, and this application embodiment does not limit this. The method of processing the file through the file processing interface of the target micro-application is described below.

[0249] In one possible implementation, in response to the selection of any file displayed in the file processing interface of the target micro-application, the terminal displays a processing interface for that file, which provides at least one processing tool for processing the file.

[0250] When the file is an image, the image processing interface is used to edit the image, such as drawing on it, adding graphics, or changing parameters like contrast, brightness, and color temperature. Accordingly, the image processing interface provides tools including drawing tools, graphic addition tools, contrast adjustment tools, brightness adjustment tools, and color temperature adjustment tools.

[0251] If the file is a video, the video processing interface is used to edit the video, such as trimming it or adding subtitles. Accordingly, the processing tools provided by the video processing interface include editing tools and subtitle adding tools.

[0252] If the file is a compressed file, the interface for processing compressed files is used to decompress it. Accordingly, the processing tools provided by the video processing interface include decompression tools.

[0253] The flow of the file sending method provided in this application embodiment will be described below with reference to Figure 10 and the above steps 301-305.

[0254] Referring to Figure 10, the micro-application sends an application interface call request to the target application, which carries file filtering parameters for the target micro-application. The application filters at least one file in the target session based on these file filtering parameters to obtain at least one target file. The application then sends the file information of this at least one target file to the target micro-application, which can then perform subsequent processing based on this file information.

[0255] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0256] The solution provided in this application provides a call identifier for the target micro-application within the application's session interface. When this call identifier is triggered, a file selection interface is displayed, showing files from the target session—that is, files shared within the target session. By directly selecting a file from this interface, the file can be quickly sent to the target micro-application for processing. This process simplifies the workflow for sending files to the target micro-application and improves the efficiency of human-computer interaction.

[0257] In addition to steps 301-305 described above, this application embodiment also provides another file sending method. Referring to Figure 11, taking the terminal as the executing entity as an example, the method includes:

[0258] 1101. The terminal displays an application selection interface in the application, which includes at least one candidate micro-application, and the at least one candidate micro-application runs on the application.

[0259] In one possible implementation, in response to a click on the micro-application viewing control, the terminal displays the application selection interface within the application. In some embodiments, the at least one candidate micro-application is a micro-application used by the currently logged-in account of the application, or a micro-application provided by default by the application; this application embodiment does not limit this.

[0260] For example, referring to Figure 12, the terminal displays a display interface 1201 of the target micro-application, which includes a viewing control 1202 for the target micro-application. In response to a click operation on the viewing control 1202, the terminal displays an application selection interface 1203, which includes multiple candidate micro-applications.

[0261] 1102. In response to the selection of a target micro-application among the at least one candidate micro-application, the terminal displays a session selection interface for the application, which includes at least one session in the application, the target micro-application being used for file processing.

[0262] In one possible implementation, in response to a click on a target micro-application among at least one candidate micro-application, the terminal displays a session selection interface for the application, which includes at least one session in the application, that is, at least one session in which the currently logged-in account of the application participates, where the session is a group session or a one-to-one session.

[0263] For example, referring to Figures 4 and 12, in response to a click on a target micro-application 1204 in the application selection interface 1203, the terminal displays the session selection interface 401 of that application.

[0264] 1103. In response to the selection of a target session in the at least one session, the terminal displays a file selection interface for the target session, which displays at least one file from the target session.

[0265] In one possible implementation, in response to a target session being selected in the at least one session, the terminal determines the target file type supported by the target microapplication. The terminal determines at least one target file from at least one file in the target session, the file type of which is the target file type. The terminal displays the at least one target file in the file selection interface of the target session.

[0266] For example, in response to a click operation on a target session within at least one session, the terminal determines the target file types supported by the target micro-application. The terminal then identifies at least one target file from at least one file within the target session, the target file being of the specified file type. The terminal displays the at least one target file in the file selection interface of the target session.

[0267] In one possible implementation, the response to the selection of a target session in the at least one session, determining the target file types supported by the target micro-application includes:

[0268] In response to the selection of a target session in at least one session, the target micro-application sends an application interface call request to the application. This request invokes the application's file retrieval interface and carries file filtering parameters indicating the target file types supported by the micro-application. The terminal determines the target file type of the micro-application based on these file filtering parameters.

[0269] In one possible implementation, the application interface call request also carries the upper limit on the number of files that can be retrieved, and the method further includes:

[0270] The terminal displays the maximum number of files that can be retrieved in the file selection interface.

[0271] In one possible implementation, displaying the at least one target file in the file selection interface of the target session includes any of the following:

[0272] When the target file type is video and / or image, the terminal displays at least one target file as a thumbnail in the file selection interface.

[0273] When the target file type is a reference file type, the terminal displays at least one target file in a list in the file selection interface. The reference file type is a file type other than video and image.

[0274] The methods for displaying the file selection interface in each of the optional embodiments in step 1103 above and the methods for displaying the file selection interface on the terminal in step 303 above belong to the same inventive concept. The implementation process is described in step 303 above and will not be repeated here.

[0275] 1104. In response to the selection of any one of the at least one files, the terminal sends that file to the target micro-application.

[0276] In one possible implementation, in response to any of the at least one file being selected, the terminal determines the cache state of that file, which indicates whether the file is stored on the electronic device running the application. If the file's cache state is cached, the file is sent to the target micro-application.

[0277] In one possible implementation, the file selection interface includes a confirmation control, which, if the file's cache state is cached, includes sending the file to the target micro-application:

[0278] If the file is cached, the terminal displays a selection icon at the file's location in the file selection interface. In response to a click on the confirmation control in the file selection interface, the terminal sends the file to the target micro-application.

[0279] In one possible implementation, the method further includes:

[0280] If the file's cache status is "caching", in response to the file's cache status changing from "caching" to "cached", the terminal sends the file to the target micro-application.

[0281] In one possible implementation, if the file is not cached, the terminal downloads the file. If the file's cache status changes from not cached to cached, the terminal sends the file to the target micro-application.

[0282] In some embodiments, the terminal displays the download progress of the file in the file selection interface.

[0283] In some embodiments, if the terminal does not store the file on the server, it displays a prompt message indicating that the file cannot be downloaded.

[0284] The methods for displaying the file selection interface in each of the optional embodiments in step 1104 above and the methods for displaying the file selection interface on the terminal in step 304 above belong to the same inventive concept. The implementation process is described in step 304 above and will not be repeated here.

[0285] 1105. The terminal displays the file processing interface of the target micro-application, which includes the file.

[0286] The methods for displaying the file selection interface in each of the optional embodiments in step 1105 above and the methods for displaying the file selection interface on the terminal in step 305 above belong to the same inventive concept. The implementation process is described in step 305 above and will not be repeated here.

[0287] The document sending method provided in this application embodiment will be described below with reference to Figure 13, steps 301-305 and 1101-1105 above.

[0288] Referring to Figure 13, the server provides the target micro-application with file filtering parameters and the maximum number of files that can be retrieved. When a user wants to process files in a target session through the target micro-application, the target micro-application can be triggered to retrieve files in the target session using its call identifier. The target micro-application sends an interface call request to the application, which requests a file retrieval interface and includes file filtering parameters. The application filters at least one file in the target session based on these file filtering parameters, obtaining at least one target file. In response to any of the at least one target file being selected, the cache status of the target file is determined. If the target file is not cached, it is downloaded. During the download process, the download progress is displayed. If the target file's cache status changes from not cached to cached, the file information is stored in the cache. The cached file information is sent to the target micro-application, whose service provider obtains this information and can subsequently provide corresponding file processing services based on it.

[0289] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0290] The solution provided in this application provides a call identifier for the target micro-application within the application's session interface. When this call identifier is triggered, a file selection interface is displayed, showing files from the target session—that is, files shared within the target session. By directly selecting a file from this interface, the file can be quickly sent to the target micro-application for processing. This process simplifies the workflow for sending files to the target micro-application and improves the efficiency of human-computer interaction.

[0291] Figure 14 is a schematic diagram of a file sending device provided in an embodiment of this application. Referring to Figure 14, the device includes: a session interface display module 1401, a first file selection interface display module 1402, and a first sending module 1403.

[0292] The session interface display module 1401 is used to display the session interface of the target session in the application. The session interface includes the call identifier of the target micro-application, which runs on the application and is used to process files.

[0293] The first file selection interface display module 1402 is used to display the file selection interface of the target session in response to the triggering of the call identifier of the target micro-application. The file selection interface displays at least one file in the target session.

[0294] The first sending module 1403 is configured to send the selected file to the target microapplication in response to the selection of any one of the at least one files.

[0295] In one possible implementation, the first file selection interface display module 1402 is configured to determine the target file type supported by the target micro-application in response to the triggering of the target micro-application's call identifier. At least one target file is determined from at least one file in the target session, and the file type of the target file is the specified target file type. The at least one target file is then displayed in the file selection interface of the target session.

[0296] In one possible implementation, the first file selection interface display module 1402 is configured to, in response to the triggering of the call identifier of the target micro-application, send an application interface call request to the application. This application interface call request invokes the application's file retrieval interface and carries file filtering parameters of the target micro-application. These file filtering parameters indicate the target file types supported by the target micro-application. Based on these file filtering parameters, the target file type of the target micro-application is determined.

[0297] In one possible implementation, the application interface call request also carries the maximum number of files that can be retrieved, and the first file selection interface display module 1402 is also used to display the maximum number of files that can be retrieved in the file selection interface.

[0298] In one possible implementation, the first file selection interface display module 1402 is configured to perform any of the following:

[0299] If the target file type is video and / or image, the at least one target file is displayed as a thumbnail in the file selection interface.

[0300] When the target file type is a reference file type, the at least one target file is displayed in a list in the file selection interface. The reference file type is a file type other than video and image.

[0301] In one possible implementation, the first sending module 1403 is configured to, in response to the selection of any one of the at least one files, determine the cache state of that file, which indicates whether the file is stored on the electronic device running the application. If the file's cache state is cached, the file is sent to the target micro-application.

[0302] In one possible implementation, the file selection interface includes a confirmation control. The first sending module 1403 is configured to display a selection indicator at the location of the file in the file selection interface if the file's cached state is cached. In response to a click on the confirmation control in the file selection interface, the file is sent to the target micro-application.

[0303] In one possible implementation, the first sending module 1403 is further configured to send the file to the target microapplication in response to the file's cache status changing from being cached to being cached, provided that the file's cache status is currently being cached.

[0304] In one possible implementation, the first sending module 1403 is further configured to download the file if its cached state is uncached, and send the file to the target microapplication if its cached state changes from uncached to cached.

[0305] In one possible implementation, the device further includes:

[0306] The first download progress display module is used to display the download progress of a file in the file selection interface.

[0307] In one possible implementation, the device further includes:

[0308] The first prompt message display module is used to display a prompt message when the file cannot be downloaded successfully. This prompt message indicates that the file cannot be downloaded.

[0309] In one possible implementation, the first sending module 1403 is used to send the file information of the file to the target micro-application, the file information including the storage location of the file on the electronic device running the application.

[0310] In one possible implementation, the device further includes any of the following:

[0311] The first sending progress display module is used to display the sending progress of sending the file to the target micro-application.

[0312] The first success message sending module is used to display a success message when the file is successfully sent to the target micro-application. The success message is used to indicate that the file has been sent to the target micro-application.

[0313] In one possible implementation, the device further includes:

[0314] The first file processing interface display module is used to display the file processing interface of the target micro-application, which includes the file.

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

[0316] The solution provided in this application provides a call identifier for the target micro-application within the application's session interface. When this call identifier is triggered, a file selection interface is displayed, showing files from the target session—that is, files shared within the target session. By directly selecting a file from this interface, the file can be quickly sent to the target micro-application for processing. This process simplifies the workflow for sending files to the target micro-application and improves the efficiency of human-computer interaction.

[0317] Figure 15 is a schematic diagram of a file sending device provided in an embodiment of this application. Referring to Figure 15, the device includes: an application selection interface display module 1501, a session selection interface display module 1502, a second file selection interface display module 1503, and a second sending module 1504.

[0318] The application selection interface display module 1501 is used to display an application selection interface in the application. The application selection interface includes at least one candidate micro-application, and the at least one candidate micro-application runs on the application.

[0319] The session selection interface display module 1502 is configured to display a session selection interface for an application in response to the selection of a target micro-application among the at least one candidate micro-application. The session selection interface includes at least one session in the application, and the target micro-application is used for processing files.

[0320] The second file selection interface display module 1503 is used to display a file selection interface for the target session in response to the selection of the target session in the at least one session. The file selection interface displays at least one file of the target session.

[0321] The second sending module 1504 is configured to send the selected file to the target microapplication in response to the selection of any one of the at least one files.

[0322] In one possible implementation, the second file selection interface display module 1503 is configured to, in response to the selection of a target session in the at least one session, determine the target file type supported by the target microapplication. At least one target file is determined from at least one file in the target session, and the file type of the target file is the specified target file type. The at least one target file is then displayed in the file selection interface of the target session.

[0323] In one possible implementation, the second file selection interface display module 1503 is configured to, in response to the selection of a target session in at least one session, send an application interface call request to the application. This application interface call request invokes the application's file retrieval interface, carrying file filtering parameters of the target micro-application. These parameters indicate the target file types supported by the target micro-application. Based on these file filtering parameters, the target file type of the target micro-application is determined.

[0324] In one possible implementation, the application interface call request also carries the maximum number of files that can be retrieved, and the second file selection interface display module 1503 is also used to display the maximum number of files that can be retrieved in the file selection interface.

[0325] In one possible implementation, the second file selection interface display module 1503 is configured to perform any of the following:

[0326] If the target file type is video and / or image, the at least one target file is displayed as a thumbnail in the file selection interface.

[0327] When the target file type is a reference file type, the at least one target file is displayed in a list in the file selection interface. The reference file type is a file type other than video and image.

[0328] In one possible implementation, the second sending module 1504 is configured to determine the cache state of a file in response to the selection of any one of the at least one file, the cache state indicating whether the file is stored on the electronic device running the application. If the file's cache state is cached, the file is sent to the target micro-application.

[0329] In one possible implementation, the file selection interface includes a confirmation control. The second sending module 1504 is configured to display a selection indicator at the location of the file in the file selection interface if the file's cached state is cached. In response to a click on the confirmation control in the file selection interface, the file is sent to the target micro-application.

[0330] In one possible implementation, the second sending module 1504 is further configured to send the file to the target microapplication in response to the file's cache status changing from being cached to being cached, provided that the file's cache status is currently being cached.

[0331] In one possible implementation, the second sending module 1504 is further configured to download the file if its cached state is uncached, and send the file to the target microapplication if its cached state changes from uncached to cached.

[0332] In one possible implementation, the method further includes:

[0333] The second download progress display module is used to display the download progress of the file in the file selection interface.

[0334] In one possible implementation, the device further includes:

[0335] The second prompt message display module is used to display a prompt message when the file cannot be downloaded successfully. This prompt message indicates that the file cannot be downloaded.

[0336] In one possible implementation, the second sending module 1504 is used to send the file information of the file to the target micro-application, the file information including the storage location of the file on the electronic device running the application.

[0337] In one possible implementation, the device further includes any of the following:

[0338] The first sending progress display module is used to display the sending progress of sending the file to the target micro-application.

[0339] The first success message sending module is used to display a success message when the file is successfully sent to the target micro-application. The success message is used to indicate that the file has been sent to the target micro-application.

[0340] In one possible implementation, the device further includes:

[0341] The first file processing interface display module is used to display the file processing interface of the target micro-application, which includes the file.

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

[0343] The solution provided in this application provides a call identifier for the target micro-application within the application's session interface. When this call identifier is triggered, a file selection interface is displayed, showing files from the target session—that is, files shared within the target session. By directly selecting a file from this interface, the file can be quickly sent to the target micro-application for processing. This process simplifies the workflow for sending files to the target micro-application and improves the efficiency of human-computer interaction.

[0344] This application provides a computer device for performing the above-described method. This computer device can be implemented as a terminal or a server. The structure of the terminal will be described below:

[0345] Figure 16 is a schematic diagram of a terminal provided in an embodiment of this application. The terminal 1600 can be a smartphone, tablet computer, laptop computer, or desktop computer.

[0346] Typically, terminal 1600 includes one or more processors 1601 and one or more memories 1602.

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

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

[0349] In some embodiments, the terminal 1600 may also optionally include a peripheral device interface 1603 and at least one peripheral device. The processor 1601, memory 1602, and peripheral device interface 1603 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1603 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency circuit 1604, a display screen 1605, a camera assembly 1606, an audio circuit 1607, and a power supply 1608.

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

[0351] The radio frequency (RF) circuit 1604 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 1604 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 1604 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 1604 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc.

[0352] Display screen 1605 is used to display a user interface (UI). This UI may include graphics, text, icons, video, and any combination thereof. When display screen 1605 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 1601 for processing. In this case, display screen 1605 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard.

[0353] The camera assembly 1606 is used to capture images or videos. Optionally, the camera assembly 1606 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal.

[0354] The audio circuit 1607 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, and convert the sound waves into electrical signals that are input to the processor 1601 for processing, or input to the radio frequency circuit 1604 to realize voice communication.

[0355] The power supply 1608 is used to supply power to the various components in the terminal 1600. The power supply 1608 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery.

[0356] In some embodiments, the terminal 1600 further includes one or more sensors 1609. The one or more sensors 1609 include, but are not limited to: an accelerometer 1610, a gyroscope 1611, a pressure sensor 1612, an optical sensor 1613, and a proximity sensor 1614.

[0357] Accelerometer 1610 can detect the magnitude of acceleration on the three coordinate axes of a coordinate system established with terminal 1600.

[0358] The gyroscope sensor 1611 can detect the orientation and rotation angle of the terminal 1600. The gyroscope sensor 1611 can work in conjunction with the accelerometer sensor 1610 to collect the user's 3D movements on the terminal 1600.

[0359] The pressure sensor 1612 can be installed on the side bezel of the terminal 1600 and / or on the lower layer of the display screen 1605. When the pressure sensor 1612 is installed on the side bezel of the terminal 1600, it can detect the user's grip signal on the terminal 1600, and the processor 1601 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 1612. When the pressure sensor 1612 is installed on the lower layer of the display screen 1605, the processor 1601 can control the operable controls on the UI interface based on the user's pressure operation on the display screen 1605.

[0360] An optical sensor 1613 is used to collect ambient light intensity. In one embodiment, a processor 1601 can control the display brightness of a display screen 1605 based on the ambient light intensity collected by the optical sensor 1613.

[0361] The proximity sensor 1614 is used to detect the distance between the user and the front of the terminal 1600.

[0362] Those skilled in the art will understand that the structure shown in FIG16 does not constitute a limitation on the terminal 1600, and may include more or fewer components than shown, or combine certain components, or employ different component arrangements.

[0363] The aforementioned computer equipment can also be implemented as a server. The structure of a server is described below:

[0364] Figure 17 is a schematic diagram of a server structure provided in an embodiment of this application. The server 1700 can vary considerably depending on its configuration or performance. It may include one or more Central Processing Units (CPUs) 1701 and one or more memories 1702. The one or more memories 1702 store at least one computer program, which is loaded and executed by the one or more processors 1701 to implement the methods provided in the various method embodiments described above. Of course, the server 1700 may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The server 1700 may also include other components for implementing device functions, which will not be elaborated upon here.

[0365] In an exemplary embodiment, a computer-readable storage medium is also provided, such as a memory including a computer program that can be executed by a processor to perform the file sending method described above. For example, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0366] In an exemplary embodiment, a computer program product or computer program is also provided, which includes program code stored in a computer-readable storage medium. A processor of a computer device reads the program code from the computer-readable storage medium and executes the program code, causing the computer device to perform the file sending method described above.

[0367] In some embodiments, the computer program involved in the present application embodiments may be deployed and executed on a computer device, or executed on multiple computer devices located in one location, or executed on multiple computer devices distributed in multiple locations and interconnected through a communication network. Multiple computer devices distributed in multiple locations and interconnected through a communication network may constitute a blockchain system.

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

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

Claims

1. A method for sending files, characterized in that, The method includes: displaying a session interface of a target session in an application, the session interface including a call identifier of a target micro-application, the target micro-application running on the application, and the target micro-application being used to process files; in response to the call identifier of the target micro-application being triggered, displaying a file selection interface of the target session, the file selection interface displaying at least one file in the target session; in response to any file being selected among the at least one file, sending the file to the target micro-application; when the target micro-application receives the file, displaying a micro-application launch control on the file selection interface; in response to a triggering operation of the micro-application launch control, displaying a file processing interface of the target micro-application, the file processing interface displaying the file sent to the target micro-application; and in response to a selection operation of any file displayed on the file processing interface, displaying a processing interface for the selected file, the processing interface providing at least one processing tool for processing the selected file.

2. The method according to claim 1, characterized in that, The step of displaying the file selection interface of the target session in response to the triggering of the call identifier of the target micro-application includes: determining the target file type supported by the target micro-application in response to the triggering of the call identifier of the target micro-application; determining at least one target file from at least one file in the target session, wherein the file type of the target file is the target file type; and displaying the at least one target file in the file selection interface of the target session.

3. The method according to claim 2, characterized in that, The step of determining the target file type supported by the target micro-application in response to the triggering of the target micro-application's call identifier includes: in response to the triggering of the target micro-application's call identifier, the target micro-application sends an application interface call request to the application, the application interface call request being used to call the application's file retrieval interface, the application interface call request carrying the target micro-application's file filtering parameters, the file filtering parameters being used to indicate the target file type supported by the target micro-application; and determining the target file type of the target micro-application based on the target micro-application's file filtering parameters.

4. The method according to claim 3, characterized in that, The application interface call request also carries the upper limit number of files that can be retrieved, and the method further includes: displaying the upper limit number of files that can be retrieved in the file selection interface.

5. The method according to claim 2, characterized in that, Displaying the at least one target file in the file selection interface of the target session includes any of the following: when the target file type is video and / or image, displaying the at least one target file in the file selection interface as a thumbnail; when the target file type is a reference file type, displaying the at least one target file in the file selection interface as a list, wherein the reference file type is a file type other than video and image.

6. The method according to claim 1, characterized in that, The step of sending the file to the target micro-application in response to the selection of any one of the at least one files includes: determining the cache state of the file in response to the selection of any one of the at least one files, the cache state being used to indicate whether the file is stored on the electronic device running the application; and sending the file to the target micro-application if the cache state of the file is cached.

7. The method according to claim 6, characterized in that, The file selection interface includes a confirmation control. When the file is cached, sending the file to the target micro-application includes: displaying a selection marker at the location of the file in the file selection interface when the file is cached; and sending the file to the target micro-application in response to a click operation on the confirmation control in the file selection interface.

8. The method according to claim 6, characterized in that, The method further includes: if the cached state of the file is "caching", in response to the cached state of the file changing from "caching" to "cached", sending the file to the target micro-application.

9. The method according to claim 6, characterized in that, The method further includes: downloading the file when the file's cache status is uncached; and sending the file to the target micro-application when the file's cache status changes from uncached to cached.

10. The method according to claim 9, characterized in that, The method further includes displaying the download progress of the file in the file selection interface.

11. The method according to any one of claims 1-10, characterized in that, Sending the file to the target micro-application includes sending the file information of the file to the target micro-application, wherein the file information includes the storage location of the file on the electronic device running the application.

12. The method according to any one of claims 1-10, characterized in that, The method further includes any one of the following: displaying the sending progress of sending the file to the target micro-application; and, if the file is successfully sent to the target micro-application, displaying a sending success message, wherein the sending success message is used to indicate that the file has been sent to the target micro-application.

13. A method for sending files, characterized in that, The method includes: displaying an application selection interface in an application, the application selection interface including at least one candidate micro-application, all of which run on top of the application; in response to a target micro-application being selected among the at least one candidate micro-application, displaying a session selection interface of the application, the session selection interface including at least one session in the application, the target micro-application being used to process files; in response to a target session being selected among the at least one session, displaying a file selection interface for the target session, the file selection interface displaying at least one file from the target session; in response to any file being selected among the at least one file, sending the file to the target micro-application; when the target micro-application receives the file, displaying a micro-application launch control on the file selection interface; in response to a triggering operation of the micro-application launch control, displaying a file processing interface of the target micro-application, the file processing interface displaying the file sent to the target micro-application; in response to a selection operation of any file displayed on the file processing interface, displaying a processing interface for the selected file, the processing interface providing at least one processing tool for processing the selected file.

14. The method according to claim 13, characterized in that, The step of displaying a file selection interface for the target session in response to the selection of the target session includes: determining the target file type supported by the target micro-application in response to the selection of the target session; determining at least one target file from at least one file in the target session, wherein the file type of the target file is the target file type; and displaying the at least one target file in the file selection interface of the target session.

15. The method according to claim 14, characterized in that, The step of determining the target file type supported by the target micro-application in response to the selection of a target session in the at least one session includes: in response to the selection of a target session in the at least one session, the target micro-application sends an application interface call request to the application, the application interface call request being used to call the application's file retrieval interface, the application interface call request carrying file filtering parameters of the target micro-application, the file filtering parameters being used to indicate the target file type supported by the target micro-application; and determining the target file type of the target micro-application based on the file filtering parameters of the target micro-application.

16. The method according to claim 15, characterized in that, The application interface call request also carries the upper limit number of files that can be retrieved, and the method further includes: displaying the upper limit number of files that can be retrieved in the file selection interface.

17. The method according to claim 14, characterized in that, Displaying the at least one target file in the file selection interface of the target session includes any of the following: when the target file type is video and / or image, displaying the at least one target file in the file selection interface as a thumbnail; when the target file type is a reference file type, displaying the at least one target file in the file selection interface as a list, wherein the reference file type is a file type other than video and image.

18. The method according to claim 13, characterized in that, The step of sending the file to the target micro-application in response to the selection of any one of the at least one files includes: determining the cache state of the file in response to the selection of any one of the at least one files, the cache state being used to indicate whether the file is stored on the electronic device running the application; and sending the file to the target micro-application if the cache state of the file is cached.

19. The method according to claim 18, characterized in that, The file selection interface includes a confirmation control. When the file is cached, sending the file to the target micro-application includes: displaying a selection marker at the location of the file in the file selection interface when the file is cached; and sending the file to the target micro-application in response to a click operation on the confirmation control in the file selection interface.

20. The method according to claim 18, characterized in that, The method further includes: if the cached state of the file is "caching", in response to the cached state of the file changing from "caching" to "cached", sending the file to the target micro-application.

21. The method according to claim 18, characterized in that, The method further includes: downloading the file when the file's cache status is uncached; and sending the file to the target micro-application when the file's cache status changes from uncached to cached.

22. The method according to claim 21, characterized in that, The method further includes displaying the download progress of the file in the file selection interface.

23. The method according to claim 21, characterized in that, The method further includes: displaying a prompt message if the file cannot be downloaded successfully, the prompt message indicating that the file cannot be downloaded.

24. The method according to claim 13, characterized in that, Sending the file to the target micro-application includes sending the file information of the file to the target micro-application, wherein the file information includes the storage location of the file on the electronic device running the application.

25. The method according to claim 13, characterized in that, The method further includes any one of the following: displaying the sending progress of sending the file to the target micro-application; and, if the file is successfully sent to the target micro-application, displaying a sending success message, wherein the sending success message is used to indicate that the file has been sent to the target micro-application.

26. A file sending device, characterized in that, The device includes: a session interface display module for displaying a session interface of a target session in an application, the session interface including a call identifier of a target micro-application, the target micro-application running on the application, and the target micro-application being used to process files; a first file selection interface display module for displaying a file selection interface of the target session in response to the triggering of the call identifier of the target micro-application, the file selection interface displaying at least one file in the target session; a first sending module for sending a file to the target micro-application in response to the selection of any file among the at least one file; a first file processing interface display module for displaying a micro-application launch control on the file selection interface when the target micro-application receives a file; and displaying a file processing interface of the target micro-application in response to a triggering operation of the micro-application launch control, the file processing interface displaying files sent to the target micro-application; and a module for performing the following steps: in response to the selection operation of any file displayed on the file processing interface, displaying a processing interface for the selected file, the processing interface providing at least one processing tool for processing the selected file.

27. The apparatus according to claim 26, characterized in that, The first file selection interface display module is configured to: in response to the triggering of the call identifier of the target micro-application, determine the target file type supported by the target micro-application; determine at least one target file from at least one file in the target session, wherein the file type of the target file is the target file type; and display the at least one target file in the file selection interface of the target session.

28. The apparatus according to claim 27, characterized in that, The first file selection interface display module is configured to: in response to the triggering of the call identifier of the target micro-application, send an application interface call request to the application, the application interface call request being used to call the file acquisition interface of the application, the application interface call request carrying the file filtering parameters of the target micro-application, the file filtering parameters being used to indicate the target file types supported by the target micro-application; Based on the file filtering parameters of the target micro-application, the target file type of the target micro-application is determined.

29. The apparatus according to claim 28, characterized in that, The application interface call request also carries the maximum number of files that can be retrieved, and the first file selection interface display module is also used to display the maximum number of files that can be retrieved in the file selection interface.

30. The apparatus according to claim 27, characterized in that, The first file selection interface display module is configured to perform any of the following: when the target file type is video and / or image, display the at least one target file in the file selection interface as a thumbnail; when the target file type is a reference file type, display the at least one target file in the file selection interface as a list, wherein the reference file type is a file type other than video and image.

31. The apparatus according to claim 26, characterized in that, The first sending module is configured to: in response to any one of the at least one files being selected, determine the cache state of the file, the cache state indicating whether the file is stored on the electronic device running the application; and if the cache state of the file is cached, send the file to the target micro-application.

32. The apparatus according to claim 31, characterized in that, The file selection interface includes a confirmation control. The first sending module is configured to: display a selection marker at the location of the file in the file selection interface when the file's cache status is cached; and send the file to the target micro-application in response to a click operation on the confirmation control in the file selection interface.

33. The apparatus according to claim 31, characterized in that, The first sending module is further configured to send the file to the target micro-application in response to the file's cache status changing from being cached to being cached, when the file's cache status is currently being cached.

34. The apparatus according to claim 31, characterized in that, The first sending module is further configured to: download the file when the file's cache status is uncached; and send the file to the target micro-application when the file's cache status changes from uncached to cached.

35. The apparatus according to claim 34, characterized in that, The device further includes: a first download progress display module, used to display the download progress of the file in the file selection interface.

36. The apparatus according to any one of claims 26-35, characterized in that, The first sending module is used to send the file information of the file to the target micro-application, the file information including the storage location of the file on the electronic device running the application.

37. The apparatus according to any one of claims 26-35, characterized in that, The device further includes any one of the following: a first sending progress display module, which displays the sending progress of sending the file to the target micro-application; and a first success information sending module, which displays a sending success information when the file is successfully sent to the target micro-application, wherein the sending success information is used to indicate that the file has been sent to the target micro-application.

38. A file sending device, characterized in that, The device includes: an application selection interface display module, used to display an application selection interface in an application, the application selection interface including at least one candidate micro-application, all of which run on the application; a session selection interface display module, used to display a session selection interface of the application in response to the selection of a target micro-application among the at least one candidate micro-application, the session selection interface including at least one session in the application, the target micro-application being used for file processing; and a second file selection interface display module, used to display a file selection interface of the target session in response to the selection of a target session among the at least one session, the file selection interface displaying at least one file from the target session. The system includes: a first file processing interface display module, configured to send a file to the target micro-application in response to the selection of any file among the at least one files; a second sending module, configured to display a micro-application launch control on the file selection interface when the target micro-application receives a file; and a third module, configured to display a file processing interface of the target micro-application in response to a triggering operation of the micro-application launch control, wherein the file processing interface displays the file to be sent to the target micro-application; and a fourth module for performing the following steps: in response to the selection of any file displayed on the file processing interface, displaying a processing interface for the selected file, wherein the processing interface provides at least one processing tool for processing the selected file.

39. The apparatus according to claim 38, characterized in that, The second file selection interface display module is configured to: in response to a target session being selected in the at least one session, determine the target file type supported by the target micro-application; determine at least one target file from at least one file in the target session, wherein the file type of the target file is the target file type; and display the at least one target file in the file selection interface of the target session.

40. The apparatus according to claim 39, characterized in that, The second file selection interface display module is configured to: in response to the selection of a target session in at least one session, send an application interface call request to the application, the application interface call request being used to call the file acquisition interface of the application, the application interface call request carrying file filtering parameters of the target micro-application, the file filtering parameters being used to indicate the target file types supported by the target micro-application; Based on the file filtering parameters of the target micro-application, the target file type of the target micro-application is determined.

41. The apparatus according to claim 40, characterized in that, The application interface call request also carries the maximum number of files that can be retrieved, and the second file selection interface display module is also used to display the maximum number of files that can be retrieved in the file selection interface.

42. The apparatus according to claim 39, characterized in that, The second file selection interface display module is configured to perform any of the following: when the target file type is video and / or image, display the at least one target file in the file selection interface as a thumbnail; when the target file type is a reference file type, display the at least one target file in the file selection interface as a list, wherein the reference file type is a file type other than video and image.

43. The apparatus according to claim 38, characterized in that, The second sending module is configured to: in response to any one of the at least one files being selected, determine the cache state of the file, the cache state indicating whether the file is stored on the electronic device running the application; and if the cache state of the file is cached, send the file to the target micro-application.

44. The apparatus according to claim 43, characterized in that, The file selection interface includes a confirmation control. The second sending module is configured to: display a selection marker at the location of the file in the file selection interface when the file's cache status is cached; and send the file to the target micro-application in response to a click operation on the confirmation control in the file selection interface.

45. The apparatus according to claim 43, characterized in that, The second sending module is further configured to send the file to the target micro-application in response to the file's cache status changing from being cached to being cached, provided that the file's cache status is currently being cached.

46. ​​The apparatus according to claim 43, characterized in that, The second sending module is further configured to: download the file when the file's cache status is uncached; and send the file to the target micro-application when the file's cache status changes from uncached to cached.

47. The apparatus according to claim 46, characterized in that, The device further includes a second download progress display module, used to display the download progress of the file in the file selection interface.

48. The apparatus according to claim 46, characterized in that, The device further includes a second prompt information display module, used to display a prompt information when the file is not successfully downloaded, the prompt information indicating that the file cannot be downloaded.

49. The apparatus according to claim 38, characterized in that, The second sending module is configured to: send the file information of the file to the target micro-application, wherein the file information includes the storage location of the file on the electronic device running the application.

50. The apparatus according to claim 38, characterized in that, The device further includes any one of the following: a first sending progress display module, used to display the sending progress of sending the file to the target micro-application; and a first success information sending module, used to display a sending success information when the file is successfully sent to the target micro-application, wherein the sending success information is used to indicate that the file has been sent to the target micro-application.

51. A computer device, characterized in that, The computer device includes one or more processors and one or more memories, wherein at least one computer program is stored in the one or more memories, and the computer program is loaded and executed by the one or more processors to implement the file sending method as described in any one of claims 1 to 25.

52. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one computer program, which is loaded and executed by a processor to implement the file sending method as described in any one of claims 1 to 25.

53. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the file sending method according to any one of claims 1 to 25.

Images