File collection method and apparatus, and electronic device

Abstract

Disclosed in the embodiments of the present application are a file collection method and apparatus, and an electronic device. The method comprises: inputting and submitting file collection configuration information, and displaying a first letter writing page, wherein mail content including the file collection configuration information is displayed in the first letter writing page, and a first piece of mail including the mail content is generated by means of filling a mail template on the basis of the input file collection configuration information; in response to a first trigger operation, sending to one or more mail contacts the first mail including the mail content; and in response to a second trigger operation, displaying a file collection interface, wherein a file attachment included in a second piece of mail is displayed in the file collection interface, and the second mail is a piece of mail that is sent by any of the mail contacts and related to the file collection configuration information. The step of inputting and submitting file collection configuration information, and displaying a first letter writing page comprises: inputting and submitting the file collection configuration information, and displaying a file collection manner selection page, wherein at least a mail collection manner option is displayed in the file collection manner selection page; and in response to a trigger operation on the mail collection manner option, displaying the first letter writing page.

Description

A document collection method, apparatus and electronic device

[0001] Cross-reference of related applications

[0002] This disclosure is based on and claims priority to Chinese Patent Application No. 2025100550781, filed on January 14, 2025, the entire contents of which are hereby incorporated in whole. Technical Field

[0003] This application relates to the fields of information technology (IT) infrastructure and data processing technology, and in particular to a document collection method, apparatus and electronic device. Background Technology

[0004] With the advent of the digital age, a large amount of business and work data exists in the form of electronic documents. How to effectively and conveniently collect, summarize, classify, and retrieve these documents is a crucial issue. Common document collection methods typically include collecting data via email attachments, online form tools, and online storage services. Especially with email, the current email sender-receiver relationship is usually one-to-one. For a single sender, if a user needs to collect the recipient's reply, they need to constantly search their inbox and summarize attachment information, resulting in low efficiency and a poor user experience. Therefore, there is a need to provide an email-based document collection method to improve the efficiency and user experience of viewing reply documents. Summary of the Invention

[0005] The purpose of this application is to provide a file collection method, apparatus, and electronic device to solve the problems of low file collection efficiency and poor user experience in the prior art.

[0006] To solve the above-mentioned technical problems, the embodiments of this application are implemented as follows:

[0007] In a first aspect, an embodiment of this application provides a document collection method, the method comprising:

[0008] Input and submit the file collection configuration information, and the first email compose page will be displayed. The first email compose page displays the email content containing the file collection configuration information; wherein, the first email containing the email content is generated by filling an email template based on the input file collection configuration information.

[0009] In response to a first triggering operation, a first email containing the email content is sent to one or more email contacts;

[0010] In response to the second triggering operation, a file collection interface is displayed, which displays file attachments contained in a second email, wherein the second email is an email sent by any of the email contacts that is related to the file collection configuration information;

[0011] The process of inputting and submitting file collection configuration information and displaying the first email composing page includes:

[0012] Enter and submit the file collection configuration information, and display the file collection method selection page, which at least displays the email collection method option;

[0013] In response to the user's trigger action on the email collection method option, the first compose email page is displayed.

[0014] Secondly, this application provides a document collection method, the method comprising:

[0015] Receive and display the first email;

[0016] In response to the sixth trigger operation, a second compose email page is displayed, which displays email content related to the file collection configuration information of the first email; wherein, the first email containing the email content is generated by filling an email template based on the input file collection configuration information;

[0017] In response to the seventh trigger operation, a second email is sent to the sender of the first email, the second email carrying file attachments related to the file collection configuration information.

[0018] Thirdly, embodiments of this application provide a document collection device, the device comprising:

[0019] The first display module is configured to input and submit file collection configuration information and display a first composing page, in which email content containing the file collection configuration information is displayed; wherein, the first email containing the email content is generated by filling an email template based on the input file collection configuration information;

[0020] The email sending module is configured to send a first email containing the email content to one or more email contacts in response to a first trigger operation.

[0021] The second display module is configured to display a file collection interface in response to a second trigger operation. The file collection interface displays file attachments contained in a second email, and the second email is an email sent by any of the email contacts that is related to the file collection configuration information.

[0022] The first display module is further configured to: input and submit file collection configuration information, display a file collection method selection page, wherein the file collection method selection page displays at least an email collection method option; and display the first compose email page in response to a trigger operation on the email collection method option.

[0023] Fourthly, embodiments of this application provide a document collection device, the device comprising:

[0024] The email receiving module is configured to receive and display the first email.

[0025] The third display module is configured to display a second composing page in response to a sixth trigger operation. The second composing page displays email content related to the file collection configuration information of the first email. The first email containing the email content is generated by filling an email template based on the input file collection configuration information.

[0026] The email sending module is configured to send a second email to the sender of the first email in response to a seventh trigger operation. The second email carries file attachments related to the file collection configuration information.

[0027] Fifthly, embodiments of this application provide an electronic device, including a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps of the file collection method provided in the above embodiments.

[0028] Sixthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the file collection method provided in the above embodiments.

[0029] In a seventh aspect, embodiments of this application provide a computer program product, the computer program product including a computer program, which, when executed by a processor, implements the steps of the file collection method provided in the above embodiments.

[0030] As can be seen from the technical solutions provided by the above embodiments of this application, the embodiments of this application display a first composing page by inputting and submitting file collection configuration information. The first composing page can display email content containing the file collection configuration information. The first email containing the email content is generated by filling an email template based on the input file collection configuration information. In response to a first trigger operation, a first email containing the email content is sent to one or more email contacts. In response to a second trigger operation by the user, a file collection interface is displayed. The file collection interface can display file attachments contained in a second email. The second email can be an email related to the file collection configuration information sent by any email contact. The process of inputting and submitting file collection configuration information and displaying the first composing page includes: inputting and submitting file collection configuration information, displaying a file collection method selection page, which at least displays an email collection method option; and displaying the first composing page in response to a trigger operation on the email collection method option. In this way, in response to the file collection configuration information input and submitted by the user, the first compose page containing the email content of the file collection configuration information can be quickly displayed. Then, when the user inputs the first trigger operation, the first email can be sent to more than one email contact to improve email sending efficiency. When the user inputs the second trigger operation, the file collection interface containing file attachments is displayed. By linking the second email with the file collection configuration information, the user can easily view all file attachments corresponding to the file collection configuration information, which helps to improve the intuitiveness of file collection and enhance the user experience. Attached Figure Description

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

[0032] Figure 1 is a flowchart illustrating a document collection method according to this application;

[0033] Figure 2 is a schematic diagram of the document collection configuration information in this application;

[0034] Figure 3 is a schematic diagram of a file collection interface in this application;

[0035] Figure 4 is a flowchart illustrating another document collection method of this application;

[0036] Figure 5 is a schematic diagram of the link address information in this application;

[0037] Figure 6 is a schematic diagram of the data collection for this application.

[0038] Figure 7 is a schematic diagram of the task information list page of this application;

[0039] Figure 8 is a flowchart illustrating another document collection method of this application;

[0040] Figure 9 is a flowchart illustrating another document collection method of this application;

[0041] Figure 10 is a schematic diagram of a document collection system according to this application;

[0042] Figure 11 is a schematic diagram of the first email of this application;

[0043] Figure 12 is a schematic diagram of the file attachments uploaded by the second terminal in this application;

[0044] Figure 13 is a schematic diagram of a document collection device according to this application;

[0045] Figure 14 is a schematic diagram of another document collection device according to this application;

[0046] Figure 15 is a schematic diagram of the structure of an electronic device according to this application. Detailed Implementation

[0047] This application provides a document collection method, apparatus, and electronic device.

[0048] As shown in Figure 1, this embodiment of the specification provides a file collection method. The execution subject of this method is a first terminal, which can be a certain terminal device such as a mobile phone or tablet computer, or a computer device such as a laptop computer or desktop computer. The method specifically includes the following steps:

[0049] In step S102, the file collection configuration information is entered and submitted, and the first compose page is displayed.

[0050] The first email composing page can display email content containing file collection configuration information, as shown in Figure 2. The file collection configuration information can include relevant information for collecting file attachments, such as file title, file content description, format template file to be uploaded, collection category file type (whether it is standard naming, file type), file upload deadline, file save directory, whether to create uploader directory, and collection mode, etc.

[0051] In implementation, the first terminal in the embodiments of this specification can be a file collection terminal, and the file upload terminal can be a second terminal, with one first terminal corresponding to multiple second terminals. Preset file collection configuration information can be set in the email front-end of the first terminal (i.e., the client, which is the interface directly interacting with the user and used to display page effects). The file collection configuration information displayed in the email front-end can be encapsulated as task information parameters. By filling in the preset file collection configuration information, users can create file collection requests (or file collection tasks) according to their needs to ensure that files that better meet their requirements are collected, thereby achieving highly customized configuration when users create tasks, improving user experience and the accuracy of file collection.

[0052] In step S104, in response to the first triggering operation, a first email containing email content is sent to one or more email contacts.

[0053] In implementation, after the first terminal obtains the file collection configuration information, which includes the file collection identifier and the task identifier, generated based on the file collection request, it can construct a file collection email (i.e., the first email) based on the file collection configuration information sent by the file collection server. Upon receiving the user's first trigger operation for the first email, it generates an email sending instruction based on the file collection email. Then, it can transmit the email sending instruction to the mailbox server to trigger the mailbox server to send the file collection email to multiple second terminals (i.e., terminals corresponding to email contacts).

[0054] The file collection configuration information in the file collection server can include a file collection identifier and a task identifier. The file collection identifier identifies that the current email is for file collection and can be added to the email attachment, body, or subject. The task identifier, which can be a task ID, can be used to mark different file collection requests. A single user on the same terminal may issue multiple different file collection requests; the task identifier can distinguish these requests, thus ensuring the accuracy of file collection.

[0055] In step S106, in response to the second triggering operation, a file collection interface is displayed. This file collection interface can display file attachments contained in the second email, which can be an email sent by any email contact related to file collection configuration information.

[0056] In practice, the file collection server can extract file attachments contained in the second email and construct a file collection interface based on the extracted file attachments, so as to display the file collection interface when a second trigger operation is received from the user.

[0057] The file collection data sent by the file collection server (i.e., the file collection interface containing file attachments in the second email) can be used to represent the correspondence between the file collection email and multiple file attachments. The file collection interface can be displayed in the form of a file collection list, a graph database, or a database query method.

[0058] Here, the system accesses the file collection email directory on the first terminal's email front-end and retrieves the email list page corresponding to the current file collection request. This email list page stores an aggregated list of the first email and multiple second emails. As shown in Figure 3, taking the file collection interface displayed as a file collection list as an example, when a user receives file collection data on the first terminal, they can access the file collection email directory on the first terminal's email front-end and retrieve the email list page corresponding to the current file collection request. Each email list page stores an aggregated list of the initiating email (i.e., the first email) and reply emails (i.e., multiple second emails) for the file collection request, allowing the user to view them at any time.

[0059] This specification provides a file collection method. In response to user-inputted and submitted file collection configuration information, a first composing page is displayed, showing email content containing the file collection configuration information. In response to a user's first trigger operation, a first email containing the configuration information is sent to one or more email contacts. In response to a user's second trigger operation, a file collection interface is displayed, showing file attachments from a second email. The second email can be an email related to the file collection configuration information sent to any email contact. This method allows for quick display of the first composing page containing the configuration information in response to user input. Furthermore, upon user input of the first trigger operation, the first email can be sent to one or more email contacts, improving email sending efficiency. Upon user input of the second trigger operation, the file collection interface displaying file attachments is shown. By establishing the association between the second email and the file collection configuration information, users can easily view all file attachments corresponding to the configuration information, improving the intuitiveness of file collection and enhancing the user experience.

[0060] In practical applications, the specific processing method for displaying the first compose page in response to the file collection configuration information input and submitted by the user in step S102 can be varied. Here is another optional processing method, as shown in Figure 4, which can specifically include the following steps S1022 to S1024.

[0061] In step S1022, file collection configuration information is entered and submitted, and the file collection method selection page is displayed. The file collection method selection page may display at least the email collection method option.

[0062] In implementation, in response to the file collection configuration information input and submitted by the user, the file collection method can be identified based on the task. The file collection method can include email collection method, short link collection method, etc.

[0063] For example, a link address generation request can be generated and sent to a short link server to trigger the short link server to generate link address information for communication between the first terminal and multiple second terminals. The file collection server can generate a link address generation request based on this task identifier and send the request to the short link server. The short link server then generates unique link address information corresponding to the task and returns it to the email front-end page of the first terminal.

[0064] The link address information generated by the short link server can be the link address information of a mini-program QR code (such as a WeChat mini-program) or the link address information of a webpage (such as a webpage link address based on email sharing).

[0065] The file collection method selection page shown in Figure 5 displays email collection method options and short link collection method options.

[0066] In this way, the first terminal can send the generated link address information to multiple second terminals. The first terminal can share the link address information with multiple second terminals by copying the link or accessing the mini-program through the generated link address information (web link or mini-program QR code). Each second terminal can click to enter, and then the second terminal can upload the task information through the email front-end page and display it on the email front-end page by obtaining the task identifier.

[0067] In step S1024, in response to the triggering operation on the email collection method option, the first compose page is displayed.

[0068] In practical applications, the file attachments in the second email displayed in the file collection interface can be associated with file attachments obtained by filtering the file attachments in emails sent by email contacts according to preset specifications.

[0069] In addition, the download of the file attachments contained in the second email is related to the file retrieval method in the email metadata of the second email.

[0070] The file attachments are obtained by the file collection server through filtering out non-compliant or expired file attachments according to preset file format specifications.

[0071] In implementation, the first terminal can filter file attachments in emails sent by email contacts according to preset specification requirements, so as to filter out files that do not meet the preset specification requirements (such as expired files that do not meet the preset time requirements), and standardize the file attachments obtained after filtering according to the preset naming method of the first terminal, so as to obtain the file attachments contained in the second email displayed in the file collection interface.

[0072] In practical applications, the first email composing page can be associated with a page generated based on file-collected configuration information and preset email templates.

[0073] Here, the first email compose page can display email content containing file collection configuration information. This first email, containing the file collection configuration information, is generated by filling an email template based on the input file collection configuration information. In implementation, after receiving the file collection configuration information from the file collection server, the first terminal can construct the first email based on that configuration information, generate an email sending instruction based on the constructed first email, and then send the email sending instruction to the email server. Specifically, the first email can be constructed in the email client of the first terminal. Users can click on email sharing on the first terminal to jump to the email client. The email client can obtain the corresponding preset email template through a task identifier and fill the email template according to the user's input file configuration information to generate the first email. During the jump, the first terminal can request the file collection server to obtain the corresponding preset email template based on the task identifier. For example, it can fill in the sender, multiple recipients, title, uploaded attachment information, and adjust the email body content according to the email template to generate the first email. The email client of the first terminal then displays the first email compose page to the user, who can adjust the body content of the first email according to other preset rules.

[0074] Since the file collection email is constructed based on the file collection configuration information, and the email sending instruction is generated based on the first email, both the first email and the email sending instruction carry a file collection identifier and a task identifier. Correspondingly, the second email determined by the second terminal is also an email that matches the file collection identifier and the task identifier, and the file attachments in the ultimately collected second email are also files that match the file collection identifier and the task identifier, thereby achieving targeted file collection and improving the accuracy and reliability of file collection.

[0075] In practical applications, there are many ways to generate the first email. The following is another optional processing method, as shown in Figure 4, which may include the following steps S402.

[0076] In step S402, a first email is generated in response to the email content editing operation entered on the first compose page.

[0077] The email content editing function can be used to edit the body of the first email.

[0078] In practical applications, after receiving the second email, a task information list page can be generated. The task information list page can be displayed in various ways. The following is another optional processing method, as shown in Figure 4, which can specifically include the following steps S404.

[0079] In step S404, in response to the third triggering operation, a task information list page is displayed. This task information list page can display task information for the file collection task corresponding to each first email.

[0080] In practice, users can trigger a file collection query request (i.e., the third trigger operation) to the file collection server.

[0081] The file collection query request may include one or more parameters such as user identifier, file collection time, file collection identifier, and task identifier. In other words, a file collection query request can be generated using any one of the following parameters: user identifier, file collection time, file collection identifier, or task identifier.

[0082] In this way, users can access the email front-end page of the first terminal in real time and request the file collection server to obtain file collection list information and task information by using any one of the parameters: user identifier, file collection time, file collection identifier, or task identifier. This allows users to quickly view the information of each reply email (i.e., the second email) under the same sender email by retrieving the sending email (i.e., the first email) through the first terminal.

[0083] In response to a third triggering operation, an email task list page is displayed, which displays an email aggregation list corresponding to each of the first emails. The email aggregation list includes the first emails and the second emails corresponding to the first emails.

[0084] As shown in Figure 6, the file collection server can obtain file collection data in the form of a file collection list, such as the initiator task created by the user, the name of the task to be participated in, the task deadline, the number of users to be submitted, and the number of files to be submitted, through the file collection server. Based on the file collection query request of the first terminal, the above file collection list is fed back to the first terminal as a task information list page.

[0085] As shown in Figure 7, the file collection server can also obtain detailed task information through the task identifier to generate a task information list page.

[0086] In practical applications, task information may include the deadline for collecting the second email, the number of email contacts, and the file attachments contained in the second email.

[0087] In practical applications, after receiving the second email, an upload result feedback page can also be generated. The display method of the upload result feedback page can be varied. The following provides another optional processing method, as shown in Figure 4, which can specifically include the following steps S406.

[0088] In step S406, in response to the fourth trigger operation, an upload result feedback page is displayed. This page can display upload result information for the file attachments included in the second email.

[0089] In practical applications, after receiving the second email, an attachment download feedback page can also be generated. The display method of the attachment download feedback page can be varied. The following provides another optional processing method, as shown in Figure 4, which can specifically include the following steps S408.

[0090] In step S408, in response to the fifth trigger operation, the attachment download feedback page is displayed. This page can display download result information for the file attachments contained in the second email.

[0091] This specification provides a file collection method. In response to user-inputted and submitted file collection configuration information, a first composing page is displayed, showing email content containing the file collection configuration information. In response to a user's first trigger operation, a first email containing the configuration information is sent to one or more email contacts. In response to a user's second trigger operation, a file collection interface is displayed, showing file attachments from a second email. The second email can be an email related to the file collection configuration information sent to any email contact. This method allows for quick display of the first composing page containing the configuration information in response to user input. Furthermore, upon user input of the first trigger operation, the first email can be sent to one or more email contacts, improving email sending efficiency. Upon user input of the second trigger operation, the file collection interface displaying file attachments is shown. By establishing the association between the second email and the file collection configuration information, users can easily view all file attachments corresponding to the configuration information, improving the intuitiveness of file collection and enhancing the user experience.

[0092] As shown in Figure 8, this embodiment of the specification provides a file collection method. The executing entity of this method can be a second terminal, which can be a certain terminal device such as a mobile phone or tablet computer, or a computer device such as a laptop computer or desktop computer. The method specifically includes the following steps:

[0093] In step S802, the first email is received and displayed.

[0094] In practice, a first terminal can initiate a file collection task by sending a first email to multiple second terminals via an email server. The multiple second terminals can then return a second email containing attachments to the files to be collected to the first terminal via the email server. The description of the first email can be found in step S104 above and will not be repeated here.

[0095] In step S804, in response to the sixth trigger operation, a second compose email page is displayed. This second compose email page can display email content related to the file collection configuration information of the first email; the first email containing this content is generated by filling an email template based on the input file collection configuration information.

[0096] In step S806, in response to the seventh trigger operation, a second email is sent to the sender of the first email. The second email may contain file attachments related to file collection configuration information.

[0097] In practice, the second terminal can extract the corresponding second email containing the file attachments to be collected based on the file collection identifier and task identifier of the first email, and generate a file upload instruction based on the second email. This file upload instruction is used to instruct the second email to be sent to the first terminal.

[0098] After the second terminal generates a file upload instruction based on the second email, it can send the file upload instruction to the email server to trigger the email server to send the second email to the first terminal.

[0099] After receiving the first email from the email server, any second terminal can extract a second email containing file attachments based on the file collection identifier and task identifier carried in the first email. This second email can have two parts: the file attachments and the email body. After extracting the second email, the second terminal can generate a file upload command based on the extracted second email, thereby sending the corresponding file attachments to the first terminal through the email server, thus realizing file collection.

[0100] This specification provides a file collection method. By receiving and displaying a first email, and responding to a user's sixth trigger operation, a second compose page is displayed. The second compose page can display email content related to file collection configuration information from the first email. Responding to a user's seventh trigger operation, a second email is sent to the sender of the first email. The second email can carry file attachments related to the file collection configuration information. Thus, responding to the user's sixth trigger operation, the second compose page containing email content related to the file collection configuration information from the first email can be quickly displayed. Furthermore, upon the user's seventh trigger operation, the second email carrying file attachments related to the file collection configuration information can be quickly sent to the sender of the first email. By establishing the association between the second email and the file collection configuration information, the sender of the first email can easily view all file attachments corresponding to the file collection configuration information, improving the intuitiveness of file collection and enhancing the user experience.

[0101] In practical applications, after sending the second email, a file upload page can also be generated. The display method of the file upload page can be varied. The following provides another optional processing method, as shown in Figure 9, which can specifically include the following steps S902 to S906.

[0102] In step S902, in response to the eighth trigger operation, the file upload page is displayed. The file upload page can display the file upload task corresponding to the file collection configuration information of the first email.

[0103] In step S904, in response to the ninth trigger operation, the file attachment carried in the second email is uploaded to the preset storage location.

[0104] In addition, in practical applications, after uploading file attachments, the second terminal can also generate an upload result feedback page. The display method of the upload result feedback page can be varied. The following provides another optional processing method, as shown in Figure 9, which can specifically include the following steps S906.

[0105] In step S906, in response to the tenth trigger operation, an upload result feedback page is displayed. This page can display upload result information for the file attachments included in the second email.

[0106] In practice, the second terminal can send a file upload query request to the file collection server.

[0107] The file upload query request may include one or more parameters such as the user identifier of the first terminal user, the user identifier of the second terminal user, the file collection time, the file collection identifier, and the task identifier. In other words, the file collection query request can be generated by any one of the user identifier, the file collection time, the file collection identifier, or the task identifier.

[0108] The second terminal can receive the upload result feedback page generated from the file collection data based on the file upload query request sent by the file collection server.

[0109] Specifically, users on the second terminal can access their email client page in real time and request file upload list information and upload task information from the file collection server using any one of the following parameters: user identifier, file collection time, file collection identifier, or task identifier. The file collection data based on the file upload query request can also include upload result information, including information on successfully uploaded file attachments, information on failed file attachments, and the reasons for failure for the identified file attachments. An upload result feedback page can be generated based on the obtained upload result information.

[0110] In practical applications, after uploading file attachments, the second terminal can also generate an attachment download feedback page. The display method of the attachment download feedback page can be varied. The following provides another optional processing method, as shown in Figure 9, which can specifically include the following steps S908.

[0111] In step S908, in response to the eleventh trigger operation, the attachment download feedback page is displayed.

[0112] The attachment download feedback page can display the download results information of the file attachments contained in the second email by the sender.

[0113] In practical applications, the second terminal can also recall the second email. There are various ways to recall the second email. The following is another optional processing method, as shown in Figure 9, which can specifically include the following steps S910.

[0114] In step S910, in response to the twelfth trigger operation, the second email is withdrawn.

[0115] During implementation, the second terminal may send emails by mistake (i.e., the email receiving end information of the second terminal is incorrect). In this case, the second terminal can send a recall request to the email server (i.e., the twelfth trigger operation). The email server can determine the second email to be recalled based on the recall request and send the file collection identifier and task identifier of the second email to be recalled to the file collection server.

[0116] Furthermore, based on preset recall rules, it can be determined whether to recall the second email. For example, if the first terminal has already received the second file sent by the second terminal and downloaded it to the corresponding folder, then recalling it is meaningless and can be considered an unreasonable recall operation that does not comply with the preset recall rules. If the first terminal has received the second file sent by the second terminal but has not downloaded it to the corresponding folder, then the recall operation is reasonable and can be considered to comply with the preset recall rules. In this way, by setting recall rules, it is beneficial to save resources and improve resource utilization.

[0117] If the withdrawal request from the second terminal meets the preset withdrawal rules, then based on the file collection identifier and task identifier corresponding to the withdrawal request, the information related to the second email corresponding to the withdrawal request in the file upload information is deleted, and the file collection data (i.e. file attachments) is updated based on the file collection identifier and task identifier corresponding to the withdrawal request.

[0118] Based on the file collection identifier and task identifier corresponding to the withdrawal request, after deleting the information related to the second email corresponding to the withdrawal request in the file upload information, the association between the first email and the second email corresponding to the withdrawal request is deleted, and the file attachments are updated based on the deleted association. This helps to improve the accuracy of file collection data, thereby improving the accuracy and reliability of file collection.

[0119] This specification provides a file collection method. By receiving and displaying a first email, and responding to a user's sixth trigger operation, a second compose page is displayed. The second compose page can display email content related to file collection configuration information from the first email. Responding to a user's seventh trigger operation, a second email is sent to the sender of the first email. The second email can carry file attachments related to the file collection configuration information. Thus, in response to the user's sixth trigger operation, the second compose page containing email content related to the file collection configuration information from the first email can be quickly displayed. Furthermore, upon the user's seventh trigger operation, the second email containing file attachments related to the file collection configuration information can be quickly sent to the sender of the first email. By establishing the association between the second email and the file collection configuration information, the sender of the first email can easily view all file attachments corresponding to the file collection configuration information, improving the intuitiveness of file collection and enhancing the user experience.

[0120] As shown in Figure 10, this embodiment of the specification provides a file collection system, which may include a first terminal, a second terminal, a file collection server, an email server, and an email front-end.

[0121] In response to a file collection request sent by a first terminal, file collection configuration information carrying a file collection identifier and a task identifier is generated and sent to the first terminal, so that the first terminal can construct a file collection email (i.e., the first email) based on the file collection configuration information and send the file collection email to multiple second terminals through an email server. The second terminals are used to determine the second email (the second email) containing the file attachments to be collected, which corresponds to the file collection email, based on the file collection identifier and the task identifier.

[0122] Specifically, in response to a file collection request sent by a first terminal, a method can be used to generate file collection configuration information carrying a file collection identifier and a task identifier, and send the file collection configuration information to the first terminal. This method can be to directly generate the file collection configuration information carrying the file collection identifier and the task identifier after parsing and processing the file collection request, or to parse and process the file collection request, add the task identifier and the file collection identifier sequentially, and finally generate the file collection configuration information.

[0123] In practical applications, the first terminal can construct a file collection email based on file collection configuration information carrying file collection identifiers and task identifiers, as shown in Figure 11.

[0124] The system receives file upload information sent by the email server and generates file collection data based on the file upload information and the obtained file attachments to be collected within a preset time period. The file upload information may be information related to the second email generated by the email server based on the file collection identifier and task identifier after the email server sends the second email to the first terminal based on the file upload instruction. The file upload instruction may be an instruction generated by the second terminal based on the second email.

[0125] The preset time period can be determined based on the file upload deadline in the file collection configuration information set by the first terminal.

[0126] In this embodiment, the file collection email sent by the first terminal and the second emails uploaded by multiple second terminals are both stored in the email server. The relevant information of the file collection email and the multiple second emails is stored in the file collection server. After receiving each second email uploaded by a second terminal, the email server initiates a file upload service via a file upload command, thereby sending the second email to the first terminal. After the second email is sent to the first terminal, the email server can generate file upload information related to the second email based on the file collection identifier and task identifier. This allows the file collection server to promptly obtain information related to the target email address and associate the file collection email with the corresponding second email using the file collection identifier and task identifier.

[0127] Within a preset time period, file collection data is generated based on file upload information and the acquired file attachments to be collected. A database between file collection emails and file attachments can be built based on the file upload information and the acquired file attachments to be collected. Alternatively, the mapping relationship between file collection emails and file attachments can be obtained by aggregating the file upload information and the acquired file attachments to be collected.

[0128] The file collection server can parse the file collection request sent by the first terminal and obtain file collection parameters including task information.

[0129] After receiving a file collection request from the first terminal, the file collection server parses the request to obtain file collection parameters. These parameters include at least task information and may also include: first user information corresponding to the first terminal, second user information corresponding to the second terminal, a preset email template to be uploaded, and the file type of the attachments to be collected. The task information includes at least the main task information, which may include: task description, task configuration, and task deadline. The preset email template to be uploaded may be the format information of a template file to be uploaded.

[0130] The file collection server can generate first file collection configuration information, including task identifiers, based on the task information in the file collection parameters.

[0131] The task identifiers include: the main task identifier and the associated task identifiers.

[0132] In implementation, the file collection server can generate a main task identifier corresponding to the file collection request based on the main task information in the file collection parameters. Based on the main task identifier, the first user information corresponding to the first terminal, the second user information corresponding to the second terminal, the preset email template to be uploaded, and the file type of the file attachment to be collected, it can generate an associated task identifier corresponding to the file collection request. Finally, based on the main task identifier and the associated task identifier, the file collection parameters can be stored in different collection information tables, and the first file collection configuration information including the task identifier can be obtained based on the collection information tables.

[0133] In this way, the file collection server can add a file collection identifier to the first file collection configuration information and generate file collection configuration information carrying the file collection identifier and the task identifier.

[0134] The file collection server can send file collection configuration information, which includes file collection identifiers and task identifiers, to the first terminal.

[0135] The file collection server can construct an email set based on file collection emails acquired within a preset time period and multiple secondary emails. Based on the file collection identifier and task identifier of the file collection emails, it can use a pre-trained feature extraction model to extract key features from the email set and determine the email metadata of each email in the email set.

[0136] The email metadata includes: email attachment information, email type, types of attachments in the email, and email download address.

[0137] The feature extraction model can adopt the existing BERT (Bidirectional Encoder Representations from Transformers) model, or it can be used to fine-tune the large model based on the prompt information, which can be constructed based on the file collection identifier and task identifier.

[0138] The file collection server can determine the correspondence between each file collection email and the file attachments in the second email based on the email metadata of each email. It then generates file collection data based on this correspondence between each file collection email and its attachments.

[0139] In addition, the file collection server can also receive the file collection identifier and task identifier corresponding to the withdrawal request sent by the email server. The withdrawal request can be a request sent by the second terminal to the email server. The withdrawal request is used to trigger the email server to determine the corresponding second email based on the withdrawal request.

[0140] If the withdrawal request from the second terminal meets the preset withdrawal rules, then based on the file collection identifier and task identifier corresponding to the withdrawal request, the information related to the second email corresponding to the withdrawal request in the file upload information is deleted, and the file collection data is updated based on the file collection identifier and task identifier corresponding to the withdrawal request.

[0141] Based on the file collection identifier and task identifier corresponding to the withdrawal request, the file collection server can delete the information related to the second email corresponding to the withdrawal request in the file upload information. This can remove the association between the file collection email and the second email corresponding to the withdrawal request, and update the file collection data based on the deleted association. This helps improve the accuracy of the file collection data, thereby improving the accuracy and reliability of the file collection.

[0142] In practical applications, in addition to the possibility of emails being sent by mistake, the second terminal may also need to send additional emails. That is, for the file collection email sent by the first terminal, if the data in the second email returned by the user through the second terminal is insufficient, it is necessary to return a second email corresponding to the file collection email through the second terminal a second time or more. In this case, the method of returning the second email by the second terminal is the same each time.

[0143] The file collection server can perform format processing operations on the information of file collection emails and file attachments in the file collection data based on preset file format specifications (i.e. preset specification requirements) to obtain the format-processed file collection emails and file attachment information.

[0144] The format processing operations may include one or more of the following: deleting information from file attachments that do not meet the requirements for file collection emails, deleting information from file attachments that have exceeded the retention period, and modifying the naming convention of file attachments.

[0145] Here, the file attachments are obtained by the file collection server through filtering out non-compliant and expired file attachments according to preset file format specifications. In implementation, the file collection server can filter file attachments according to preset file format specifications, removing non-compliant and expired attachments. After filtering, the file attachments are automatically renamed according to their different groups and the file naming method in the file collection configuration information of the first terminal, and all renamed files are transferred to the file directory specified by the first terminal.

[0146] The file collection server can send the formatted file collection email and file attachment information to the first terminal, triggering the first terminal to perform corresponding formatting operations on the collected file attachments.

[0147] In practical applications, for multiple file collection requests sent by the first terminal, a summary of file attachments can be obtained through a file collection server, and the collected file attachments can be shared based on the obtained summary information. Specifically, firstly, the file fingerprint can be used to determine whether the first terminal stores the file attachments corresponding to the current file collection request. If so, the file attachments corresponding to the current file collection request can be used as the file attachments to be collected, and the file corresponding to the current file collection request can be copied to the corresponding file directory to complete a file collection task for the second terminal. If the file attachments corresponding to the current file collection request are not stored, a file collection request can be initiated.

[0148] The file collection server can respond to a file collection request sent by the first terminal and generate file collection configuration information carrying a file collection identifier and a task identifier.

[0149] In addition, after the first terminal sends the link address information to multiple second terminals, it can also send file upload prompts to the second terminals via email, SMS, or other communication methods, thereby further improving the efficiency of file collection.

[0150] The first terminal can collect file attachments based on link address information and file collection configuration information, enabling it to quickly and accurately obtain file attachments, thereby improving file collection efficiency.

[0151] In response to the email sending command from the first terminal, the email server sends a file collection email to multiple second terminals. This triggers each second terminal to retrieve a second email containing the file attachments to be collected, based on the file collection identifier and task identifier of the first email, and then generates a file upload command based on the second email. As shown in Figure 12, the second terminals can upload the file attachments corresponding to the first email through the file upload page shown in Figure 11.

[0152] The email server responds to the file upload command from each second terminal, receives the second email uploaded by each second terminal, and sends the second email to the first terminal.

[0153] The email server determines the corresponding file collection identifier and task identifier based on the second email, generates file upload information related to the second email based on the determined file collection identifier and task identifier, and sends the file upload information to the file collection server to trigger the file collection server to generate file collection data based on the file upload information and the obtained file attachments to be collected within a preset time period.

[0154] In summary, specific embodiments of this subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing can be advantageous.

[0155] The above describes a file collection method provided by one or more embodiments of this specification. Based on the same idea, one or more embodiments of this specification also provide an apparatus, as shown in FIG13. The file collection apparatus includes: a first display module 1301, an email sending module 1302, and a second display module 1303, wherein...

[0156] The first display module 1301 is configured to input and submit file collection configuration information and display a first email writing page, in which email content containing the file collection configuration information is displayed; wherein, the first email containing the email content is generated by filling an email template based on the input file collection configuration information;

[0157] Email sending module 1302 is configured to send a first email containing the email content to one or more email contacts in response to a first trigger operation;

[0158] The second display module 1303 is configured to display a file collection interface in response to a second trigger operation. The file collection interface displays file attachments contained in a second email, wherein the second email is an email sent by any of the email contacts that is related to the file collection configuration information.

[0159] The first display module 1301 is further configured to: input and submit file collection configuration information, display a file collection method selection page, wherein the file collection method selection page displays at least an email collection method option; and display the first compose email page in response to a trigger operation on the email collection method option.

[0160] Those skilled in the art will understand that the above-described document collection device can be used to implement the document collection method described above, and the detailed description therein should be similar to the method description in the above-described method section. To avoid being cumbersome, it will not be repeated here.

[0161] This specification provides a file collection device. In response to user-inputted and submitted file collection configuration information, it displays a first composing page, which can display email content containing the file collection configuration information. In response to a user's first trigger operation, it sends a first email containing the email content to one or more email contacts. In response to a user's second trigger operation, it displays a file collection interface, which can display file attachments from a second email. The second email can be an email related to the file collection configuration information sent to any email contact. This allows for quick display of the first composing page containing the file collection configuration information in response to user input and submission. Furthermore, upon user input of the first trigger operation, the first email can be sent to one or more email contacts, improving email sending efficiency. Upon user input of the second trigger operation, the file collection interface displaying file attachments allows users to easily view all file attachments corresponding to the file collection configuration information by establishing a relationship between the second email and the file collection configuration information. This enhances the intuitiveness of file collection and improves the user experience.

[0162] The above describes a file collection method provided by one or more embodiments of this specification. Based on the same idea, one or more embodiments of this specification also provide an apparatus, as shown in FIG14. The file collection apparatus includes: an email receiving module 1401, a third display module 1402, and an email sending module 1403, wherein...

[0163] Email receiving module 1401 is configured to receive and display the first email;

[0164] The third display module 1402 is configured to display a second composing page in response to a sixth trigger operation. The second composing page displays email content related to the file collection configuration information of the first email. The first email containing the email content is generated by filling an email template based on the input file collection configuration information.

[0165] The email sending module 1403 is configured to send a second email to the sender of the first email in response to a seventh trigger operation. The second email carries file attachments related to the file collection configuration information.

[0166] Those skilled in the art will understand that the above-described document collection device can be used to implement the document collection method described above, and the detailed description therein should be similar to the method description in the above-described method section. To avoid being cumbersome, it will not be repeated here.

[0167] This specification provides a file collection device that receives and displays a first email. In response to a user's sixth trigger operation, a second composing page is displayed. This second composing page can display email content related to file collection configuration information from the first email. In response to a user's seventh trigger operation, a second email is sent to the sender of the first email. This second email can carry file attachments related to the file collection configuration information. Thus, in response to the user's sixth trigger operation, a second composing page containing email content related to the file collection configuration information from the first email can be quickly displayed. Furthermore, upon the user's seventh trigger operation, a second email containing file attachments related to the file collection configuration information can be quickly sent to the sender of the first email. By establishing the association between the second email and the file collection configuration information, the sender of the first email can easily view all file attachments corresponding to the file collection configuration information, improving the intuitiveness of file collection and enhancing the user experience.

[0168] Based on the same idea, one or more embodiments of this specification also provide an electronic device, as shown in FIG15.

[0169] The electronic device 1100 includes, but is not limited to, components such as: a radio frequency unit 1101, a network module 1102, an audio output unit 1103, an input unit 1104, a sensor 1105, a display unit 1106, a user input unit 1107, an interface unit 1108, a memory 1109, a processor 1110, and a power supply 1111. Those skilled in the art will understand that the electronic device structure shown in FIG15 does not constitute a limitation on the electronic device; the electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements. In the embodiments of this application, the electronic device includes, but is not limited to, mobile phones, tablet computers, laptop computers, PDAs, in-vehicle terminals, wearable devices, and pedometers.

[0170] The processor 1110 is configured to: input and submit file collection configuration information, display a first email composing page, wherein the first email composing page displays email content containing the file collection configuration information; wherein the first email containing the email content is generated by filling an email template based on the input file collection configuration information; in response to a first trigger operation, send a first email containing the email content to one or more email contacts; in response to a second trigger operation, display a file collection interface, wherein the file collection interface displays file attachments contained in a second email, wherein the second email is an email related to the file collection configuration information sent by any of the email contacts; wherein the step of inputting and submitting file collection configuration information and displaying the first email composing page includes: inputting and submitting file collection configuration information, displaying a file collection method selection page, wherein the file collection method selection page displays at least an email collection method option; and in response to a trigger operation on the email collection method option, display the first email composing page.

[0171] Furthermore, the file attachments in the second email displayed in the file collection interface are associated with file attachments obtained by filtering file attachments in emails sent by the email contact according to preset specifications. These file attachments are obtained by the file collection server filtering out non-compliant and expired file attachments according to preset file format specifications.

[0172] In addition, the download of the file attachments contained in the second email is related to the file retrieval method in the email metadata of the second email.

[0173] Furthermore, the first email writing page is related to the page generated based on the file collection configuration information and the preset email template.

[0174] The processor 1110 is also configured to generate the first email in response to an email content editing operation entered on the first compose page.

[0175] The processor 1110 is also configured to: in response to a third trigger operation, display an email task list page, wherein the email task list page displays an email aggregation list corresponding to each of the first emails, the email aggregation list containing the first emails and the second emails corresponding to the first emails.

[0176] The processor 1110 is also configured to: access the file collection email directory of the email front-end of the first terminal, obtain the email list page corresponding to the current file collection request, wherein the email list page stores an aggregated list of the first email and multiple second emails.

[0177] The processor 1110 is also configured to: in response to a third trigger operation, display a task information list page, wherein the task information list page displays task information for a file collection task corresponding to each of the first emails.

[0178] In addition, the task information includes the deadline for collecting the second email, the number of email contacts, and the file attachments contained in the second email.

[0179] The processor 1110 is also configured to: in response to a fourth trigger operation, display an upload result feedback page, wherein the upload result feedback page displays upload result information of the file attachments contained in the second email.

[0180] The processor 1110 is also configured to: in response to a fifth trigger operation, display an attachment download feedback page, wherein the attachment download feedback page displays download result information for the file attachments contained in the second email.

[0181] One or more embodiments of this specification also provide another electronic device.

[0182] The processor 1110 is configured to: receive and display a first email; in response to a sixth trigger operation, display a second compose page, wherein the second compose page displays email content related to the file collection configuration information of the first email; wherein the first email containing the email content is generated by filling an email template based on the input file collection configuration information; and in response to a seventh trigger operation, send a second email to the sender of the first email, wherein the second email carries file attachments related to the file collection configuration information.

[0183] The processor 1110 is configured to: in response to an eighth trigger operation, display a file upload page, wherein the file upload page displays a file upload task corresponding to the file collection configuration information corresponding to the first email; and in response to a ninth trigger operation, upload the file attachments carried in the second email to a preset storage location.

[0184] The processor 1110 is also configured to: in response to the tenth trigger operation, display an upload result feedback page, wherein the upload result feedback page displays upload result information of the file attachments contained in the second email.

[0185] The processor 1110 is also configured to: in response to an eleventh trigger operation, display an attachment download feedback page, wherein the attachment download feedback page displays the download result information of the file attachments contained in the second email by the sender.

[0186] The processor 1110 is also configured to: recall the second email in response to the twelfth trigger operation.

[0187] It should be understood that, in this embodiment, the radio frequency unit 1101 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink data from the base station and processes it with the processor 1110; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 1101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc. Furthermore, the radio frequency unit 1101 can also communicate with networks and other electronic devices through a wireless communication system.

[0188] The electronic device provides users with wireless broadband internet access through network module 1102, such as helping users send and receive emails, browse web pages, and access streaming media.

[0189] The audio output unit 1103 can convert audio data received by the radio frequency unit 1101 or the network module 1102 or stored in the memory 1109 into audio signals and output them as sound. Furthermore, the audio output unit 1103 can also provide audio output related to specific functions performed by the electronic device 1100 (e.g., call signal reception sound, message reception sound, etc.). The audio output unit 1103 includes a speaker, a buzzer, and a receiver, etc.

[0190] Input unit 1104 is used to receive audio or video signals. Input unit 1104 may include a graphics processing unit (GPU) 11041 and a microphone 11042. GPU 11041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on display unit 1106. The image frames processed by GPU 11041 can be stored in memory 1109 (or other storage medium) or transmitted via radio frequency unit 1101 or network module 1102. Microphone 11042 can receive sound and process such sound into audio data. The processed audio data can be converted into a format that can be transmitted to a mobile communication base station via radio frequency unit 1101 in telephone call mode.

[0191] The electronic device 1100 also includes at least one sensor 1105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 11061 according to the ambient light level, and the proximity sensor can turn off the display panel 11061 and / or backlight when the electronic device 1100 is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used to identify the posture of the electronic device (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. The sensor 1105 may also include a fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc., which will not be described in detail here.

[0192] The display unit 1106 is used to display information input by the user or information provided to the user. The display unit 1106 may include a display panel 11061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0193] User input unit 1107 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of electronic devices. Specifically, user input unit 1107 includes a touch panel 11071 and other input devices 11072. Touch panel 11071, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 11071). Touch panel 11071 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to processor 1110, which receives and executes commands from processor 1110. In addition, touch panel 11071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 11071, the user input unit 1107 may also include other input devices 11072. Specifically, other input devices 11072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, joysticks, etc., which will not be described in detail here.

[0194] [Correction 28.01.2026 based on Rule 91] Furthermore, the touch panel 11071 may cover the display panel 11061. When the touch panel 11071 detects a touch operation on or near it, it transmits the information to the processor 1110 to determine the type of touch event. Subsequently, the processor 1110 provides corresponding visual output on the display panel 11061 according to the type of touch event. Although in FIG. 15, the touch panel 11071 and the display panel 11061 are shown as two separate components to implement the input and output functions of the electronic device, in some embodiments, the touch panel 11071 and the display panel 11061 may be integrated to implement the input and output functions of the electronic device. Specific details are not limited here.

[0195] Interface unit 1108 serves as an interface for connecting external devices to electronic device 1100. For example, external devices may include a wired or wireless headphone port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 1108 can be used to receive input from external devices (e.g., data, power, etc.) and transmit the received input to one or more components within electronic device 1100, or it can be used to transmit data between electronic device 1100 and external devices.

[0196] The memory 1109 can be used to store software programs and various data. The memory 1109 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 1109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0197] The processor 1110 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 1109, and by calling data stored in the memory 1109, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. The processor 1110 may include one or more processing units; preferably, the processor 1110 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 1110.

[0198] The electronic device 1100 may also include a power supply 1111 (such as a battery) for supplying power to various components. Preferably, the power supply 1111 can be logically connected to the processor 1110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system.

[0199] Preferably, this application embodiment also provides an electronic device, including a processor 1110, a memory 1109, and a computer program stored in the memory 1109 and executable on the processor 1110. When the computer program is executed by the processor 1110, it implements the various processes of the above-described file collection method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0200] This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, this computer program implements the various processes of the above-described file collection method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0201] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the various processes of the above-described file collection method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here.

[0202] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0203] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.

[0204] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0205] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0206] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0207] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0208] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0209] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0210] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0211] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A document collection method, the method comprising: Input and submit the file collection configuration information, and the first email compose page will be displayed. The first email compose page displays the email content containing the file collection configuration information; wherein, the first email containing the email content is generated by filling an email template based on the input file collection configuration information. In response to a first triggering operation, a first email containing the email content is sent to one or more email contacts; In response to the second triggering operation, a file collection interface is displayed, which displays file attachments contained in a second email, wherein the second email is an email sent by any of the email contacts that is related to the file collection configuration information; The process of inputting and submitting file collection configuration information and displaying the first email composing page includes: Enter and submit the file collection configuration information, and display the file collection method selection page, which at least displays the email collection method option; In response to a trigger action on the email collection method option, the first compose email page is displayed.

2. The method according to claim 1, wherein, The file attachments in the second email displayed in the file collection interface are associated with the file attachments obtained by filtering the file attachments in emails sent by the email contact according to preset specifications.

3. The method according to claim 1, wherein, The file attachments are obtained by the file collection server through filtering out non-compliant and expired file attachments according to preset file format specifications.

4. The method according to claim 1, wherein, The download of the file attachments contained in the second email is associated with the file retrieval method in the email metadata of the second email.

5. The method according to claim 1, wherein, The first email writing page is related to the page generated based on the file collection configuration information and the preset email template.

6. The method according to claim 5, wherein, Before sending a first email containing the email content to more than one email contact in response to the first triggering operation, the method further includes: The first email is generated in response to the email content editing operation entered on the first compose page.

7. The method according to claim 1, wherein, The method further includes: In response to a third triggering operation, an email task list page is displayed, which displays an email aggregation list corresponding to each of the first emails. The email aggregation list includes the first emails and the second emails corresponding to the first emails.

8. The method according to claim 1, wherein, The file collection display interface includes: Access the file collection email directory in the email frontend of the first terminal, obtain the email list page corresponding to the current file collection request, and the email list page stores an aggregated list of the first email and multiple second emails.

9. The method according to claim 1, wherein, The method further includes: In response to the third triggering operation, a task information list page is displayed, which shows the task information of the file collection task corresponding to each of the first emails.

10. The method according to claim 9, wherein, The task information includes the deadline for collecting the second email, the number of email contacts, and the file attachments contained in the second email.

11. The method according to claim 1, wherein, The method further includes: In response to the fourth trigger operation, an upload result feedback page is displayed, which shows the upload result information of the file attachments contained in the second email.

12. The method according to claim 1, wherein, The method further includes: In response to the fifth trigger operation, an attachment download feedback page is displayed, which shows the download results for the file attachments contained in the second email.

13. A document collection method, the method comprising: Receive and display the first email; In response to the sixth trigger operation, a second compose email page is displayed, which displays email content related to the file collection configuration information of the first email; wherein, the first email containing the email content is generated by filling an email template based on the input file collection configuration information; In response to the seventh trigger operation, a second email is sent to the sender of the first email, the second email carrying file attachments related to the file collection configuration information.

14. The method according to claim 13, wherein, The method further includes: In response to the eighth trigger operation, a file upload page is displayed, which shows the file upload task corresponding to the file collection configuration information corresponding to the first email; In response to the user's ninth trigger operation, the file attachment carried in the second email is uploaded to a preset storage location.

15. The method according to claim 13, wherein, The method further includes: In response to the tenth trigger operation, an upload result feedback page is displayed, which shows the upload result information of the file attachments contained in the second email.

16. The method according to claim 13, wherein, The method further includes: In response to the eleventh trigger operation, an attachment download feedback page is displayed, which shows the download result information of the file attachments contained in the second email by the sender.

17. The method according to claim 13, wherein, The method further includes: In response to the twelfth triggered action, the second email was retracted.

18. A document collection device, the device comprising: The first display module is configured to input and submit file collection configuration information and display a first composing page, in which email content containing the file collection configuration information is displayed; wherein, the first email containing the email content is generated by filling an email template based on the input file collection configuration information; The email sending module is configured to send a first email containing the email content to one or more email contacts in response to a first trigger operation. The second display module is configured to display a file collection interface in response to a second trigger operation. The file collection interface displays file attachments contained in a second email, and the second email is an email sent by any of the email contacts that is related to the file collection configuration information. The first display module is further configured to: input and submit file collection configuration information, display a file collection method selection page, wherein the file collection method selection page displays at least an email collection method option; and display the first compose email page in response to a trigger operation on the email collection method option.

19. A document collection device, the device comprising: The email receiving module is configured to receive and display the first email. The third display module is configured to display a second composing page in response to a sixth trigger operation. The second composing page displays email content related to the file collection configuration information of the first email. The first email containing the email content is generated by filling an email template based on the input file collection configuration information. The email sending module is configured to send a second email to the sender of the first email in response to a seventh trigger operation. The second email carries file attachments related to the file collection configuration information.

20. A file transfer device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as claimed in any one of claims 1 to 12, or implements the method as claimed in any one of claims 13 to 17.

21. A computer-readable storage medium storing a computer program thereon, the computer program, when executed by a processor, implementing the method as claimed in any one of claims 1 to 12, or implementing the method as claimed in any one of claims 13 to 17.

22. A computer program product comprising a computer program that, when executed by a processor, implements the method as claimed in any one of claims 1 to 12, or implements the method as claimed in any one of claims 13 to 17.

Images