Mail management method and electronic equipment
By automatically counting and displaying the reply status of the first email, the problem of users needing to frequently check the reply status of emails is solved, and the human-computer interaction efficiency and intelligence of email management are improved.
Patent Information
- Application Number
- CN202510102687.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2021-06-11
- Publication Date
- 2025-04-25
AI Technical Summary
In daily work and business transactions, users need to frequently check email replies, resulting in low human-computer interaction efficiency and low intelligence.
By automatically counting and displaying the reply status of the first email, users do not need to manually check the received emails one by one, improving the human-computer interaction efficiency and the intelligence of email data.
It realizes the reply status of the first email without manual verification, and improves the intelligence of human-computer interaction efficiency and email management.
Smart Images

Figure CN119892778A_ABST
Abstract
Description
[0001] This application is a divisional application. The application number of the original application is 202110654171.6, and the original application date is June 11, 2021. The entire contents of the original application are incorporated into this application by reference. Technical Field
[0002] The present application relates to the field of computer technology, and in particular to an email management method and electronic device. Background Art
[0003] Electronic mail (abbreviated as mail) is a communication method that provides information exchange by electronic means and is a widely used service on the Internet. Through email, users can contact another user in any corner of the world. In the course of daily work and business dealings, the emails sent by users (such as publishers) often require the recipients of the emails to process and reply in time. Users are also required to regularly check the reply status of the first emails they have sent and urge the recipients who have not processed them.
[0004] However, the user's mailbox may receive a large number of other emails every day. If the user confirms whether the recipient has completed the reply to the first email by checking the received emails one by one, it will inevitably lead to low human-computer interaction efficiency and low intelligence. Summary of the invention
[0005] The embodiments of the present application provide an email management method and an electronic device, which automatically count and display the reply status of a first email, thereby eliminating the need for manual verification of received emails one by one, thereby improving the efficiency of human-computer interaction and the intelligence level of email data.
[0006] In order to achieve the above purpose, the embodiment of the present application adopts the following technical solution:
[0007] In a first aspect, an embodiment of the present application provides an email management method, the method also includes: an electronic device sends a first email to an email receiving device; the first email is an email configured with time limit information, and the time limit information is used to instruct the email receiving device to remind it to handle the first email; the electronic device receives a reply email to the first email from the email receiving device; the electronic device counts the reply status corresponding to the first email; the electronic device displays the reply status corresponding to the first email in the task management interface of the email application, wherein the reply status includes the reply status of at least one reply email corresponding to the first email.
[0008] In the above embodiment, after the electronic device sends the first email, it can not only count the reply emails in real time, but also display the reply status in the task management interface of the email application. In this way, for the first email with time limit information, that is, the email that needs to urge the recipient to handle it in time, the user does not need to check whether there is a reply email to the first email from the massive amount of emails received. There is no need to manually count the handling status corresponding to the first email. Thus, the efficiency of human-computer interaction is improved.
[0009] In combination with the first aspect, in a possible implementation manner, the method further includes:
[0010] The electronic device receives an email and parses the email header of the email to obtain a reply chain of the email;
[0011] Confirm that the source email indicated by the reply chain is the first email, and determine that the email is a reply email to the first email.
[0012] In the above embodiment, the recognition accuracy of the reply email corresponding to the first email is improved.
[0013] In combination with the first aspect, in a possible implementation, the task management interface further includes: a processing status of a second email, wherein the second email is an email received by the electronic device and has time limit information, and the processing status includes processed and unprocessed. In combination with the first aspect, in a possible implementation, the reply status includes a reply ratio chart and / or a reply ratio;
[0014] The electronic device counts the number of the reply emails and the total number of receiving mailboxes corresponding to the first email, and determines a reply ratio chart and / or a reply proportion.
[0015] Exemplarily, the reply status may be a reply ratio graph, that is, a graph representing the ratio between the number of receiving mailboxes that have replied to the first email and the number of all receiving mailboxes corresponding to the first email.
[0016] As another example, the reply status may also be a reply ratio, that is, a numerical value representing the ratio between the number of receiving mailboxes that have replied to the first email and the number of all receiving mailboxes corresponding to the first email.
[0017] As another example, the reply status may also include a reply ratio chart and a reply percentage.
[0018] In conjunction with the first aspect, in a possible implementation manner, the task management interface also includes a task item corresponding to the first email, and the method further includes:
[0019] When the electronic device receives an operation on the task item, it displays reply details of the first email; wherein the reply details include information indicating whether the receiving mailbox corresponding to the first email has replied.
[0020] In combination with the first aspect, in a possible implementation manner, the time limit information includes a reminder time point; and the method further includes:
[0021] When the system time reaches the reminder time point, the electronic device displays the task item of the first email on the top in the task management interface and / or displays a to-do mark corresponding to the task item of the first email.
[0022] For example, when the system time reaches the reminder time point, the task item of the first email can be displayed at the top of the task management interface. Thus, the user is reminded to pay attention to the sent first email and avoid the sent first email being forgotten. In this way, even if the receiving mailbox has not completed the reply to the first email, the user can also urge it to be handled in a targeted manner.
[0023] As another example, when the system time reaches the reminder time point, a to-do mark can be displayed for the task item corresponding to the first email. Thus, the user is reminded to pay attention to the sent first email, so as to avoid the sent first email being forgotten. In this way, even if the receiving mailbox has not completed the reply to the first email, the user can also urge it to be done in a targeted manner.
[0024] As another example, when the system time reaches the reminder time point, in the task management interface, the task item of the first email is displayed on top and a to-do mark is displayed for the task item corresponding to the first email.
[0025] In addition, in some possible embodiments, the user can also set a preset reminder time point that is different from the reminder time point. In this way, when the system time reaches the preset reminder time point, in the task management interface, the task item of the first email will be displayed at the top and / or a to-do mark will be displayed for the task item corresponding to the first email.
[0026] In combination with the first aspect, in a possible implementation manner, the time limit information includes a reminder time point; and the method further includes:
[0027] When the system time reaches the reminder time point, the electronic device displays the first email on the top of the outbox interface of the email application and / or displays a to-do mark corresponding to the first email.
[0028] Exemplarily, when the system time reaches the reminder time point, the first email is displayed at the top in the outbox interface of the email application.
[0029] As another example, when the system time reaches the reminder time point, a to-do mark is displayed corresponding to the first email in the outbox interface of the email application.
[0030] In addition, in some possible embodiments, the user can also set a preset reminder time point that is different from the reminder time point. In this way, when the system time reaches the preset reminder time point, the first email will be displayed at the top in the outbox interface of the email application and / or a to-do mark will be displayed corresponding to the first email.
[0031] In conjunction with the first aspect, in a possible implementation manner, the time limit information includes a deadline; and the method further includes:
[0032] When the system time exceeds the deadline and no reply email is received from at least one receiving mailbox to the first email, the electronic device displays an overdue mark for the task item corresponding to the first email in the task management interface, and / or displays the task item of the first email at the top in the task management interface.
[0033] Exemplarily, when the system time exceeds the deadline and no reply email is received from at least one receiving mailbox to the first email, an overdue mark is displayed for the task item corresponding to the first email in the task management interface.
[0034] As another example, when the system time exceeds the deadline and no reply email is received from at least one receiving mailbox to the first email, in the task management interface, an overdue mark is displayed for the task item corresponding to the first email, and the task item of the first email is displayed at the top.
[0035] In addition, in some possible embodiments, the user may also set a preset overdue reminder time different from the deadline. Thus, when the system time exceeds the overdue reminder time and no reply email is received from at least one receiving mailbox to the first email, the electronic device displays an overdue mark for the task item corresponding to the first email in the task management interface, and / or displays the task item of the first email at the top in the task management interface.
[0036] In combination with the first aspect, in a possible implementation, the time limit information includes a deadline; the method also includes: when the system time exceeds the deadline and no reply email is received from at least one receiving mailbox to the first email, the electronic device displays an overdue mark corresponding to the first email in the outbox interface of the email application, and / or displays the first email at the top in the outbox interface.
[0037] In combination with the first aspect, in a possible implementation, the method further includes: reminding the first email through a calendar application or an alarm application in the electronic device to prompt the user to check the reply status of the first email.
[0038] In the above embodiment, even if the user does not start the mail application, the user can be reminded in time.
[0039] In combination with the first aspect, in a possible implementation, before the reminder of the first email is issued through the calendar application or the alarm application in the electronic device, the method also includes: configuring a schedule reminder in the calendar application and / or configuring an alarm reminder in the alarm application according to the time limit information.
[0040] In a second aspect, an embodiment of the present application provides an electronic device, the electronic device comprising one or more processors, one or more memories and a wireless communication module; the one or more memories and the wireless communication module are coupled to the one or more processors;
[0041] The one or more memories are used to send a first email to an email receiving device; the first email is an email configured with time limit information, and the time limit information is used to instruct the email receiving device to remind it to handle the first email; receive a reply email to the first email from the email receiving device; count the reply status corresponding to the first email; and display the reply status corresponding to the first email in the task management interface of the email application, wherein the reply status includes the reply status of at least one reply email corresponding to the first email.
[0042] In combination with the second aspect, in a possible implementation, the one or more memories are also used to receive an email, parse the reply chain of the email from the email header of the email; confirm that the source email indicated by the reply chain is the first email, and determine that the email is a reply email to the first email.
[0043] In combination with the second aspect, in a possible implementation, the task management interface further includes: the one or more memories are also used for the processing status of received emails with time limit information, wherein the processing status includes processed and not processed.
[0044] In conjunction with the second aspect, in a possible implementation, the reply status includes a reply ratio diagram and / or a reply proportion;
[0045] The one or more memories are further used to count the number of reply emails and the total number of receiving mailboxes corresponding to the first email, and determine a reply ratio chart and / or a reply proportion.
[0046] In combination with the second aspect, in a possible implementation method, the task management interface also includes a task item corresponding to the first email, and the one or more memories are also used to display the reply details of the first email when an operation on the task item is received; wherein the reply details include information indicating whether the receiving mailbox corresponding to the first email has been replied.
[0047] In combination with the second aspect, in a possible implementation method, the time limit information includes a reminder time point; when the system time reaches the reminder time point, the one or more memories are also used to display the task item of the first email at the top and / or display a to-do mark corresponding to the task item of the first email in the task management interface.
[0048] In combination with the second aspect, in a possible implementation method, the time limit information includes a reminder time point; when the system time reaches the reminder time point, the one or more memories are also used to display the first email at the top of the outbox interface of the email application and / or display a to-do mark corresponding to the first email.
[0049] In combination with the second aspect, in a possible implementation method, the time limit information includes a deadline; when the system time exceeds the deadline and no reply email is received from at least one receiving mailbox to the first email, the one or more memories are also used to display an overdue mark for the task item corresponding to the first email in the task management interface, and / or to display the task item of the first email at the top in the task management interface.
[0050] In combination with the second aspect, in one possible implementation, the time limit information includes a deadline; when the system time exceeds the deadline and no reply email is received from at least one receiving mailbox to the first email, the one or more memories are also used to display an overdue mark corresponding to the first email in the outbox interface of the email application, and / or to display the first email at the top in the outbox interface.
[0051] In combination with the second aspect, in a possible implementation, the one or more memories are also used to remind the first email through a calendar application or an alarm application in the electronic device, so as to prompt the user to check the reply status of the first email.
[0052] In combination with the second aspect, in a possible implementation, the one or more memories are further used to configure a schedule reminder in a calendar application and / or configure an alarm reminder in an alarm application according to the time limit information.
[0053] In a third aspect, an embodiment of the present application provides a computer storage medium, including computer instructions, which, when executed on an electronic device, enables the electronic device to execute the method described in the first aspect and any possible design thereof.
[0054] In a fourth aspect, an embodiment of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the method described in the first aspect and any possible design thereof.
[0055] It can be understood that the electronic device described in the second aspect and any possible design method provided above, the computer storage medium described in the third aspect, and the computer program product described in the fourth aspect are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0056] Figure 1 A schematic diagram of a system architecture provided for an embodiment of the present application;
[0057] Figure 2 A schematic diagram of the hardware architecture of an electronic device provided in an embodiment of the present application;
[0058] Figure 3 A display schematic diagram of an email sending terminal provided in an embodiment of the present application;
[0059] Figure 4 Another display schematic diagram of an email sending terminal provided in an embodiment of the present application;
[0060] Figure 5 Another display schematic diagram of an email sending terminal provided in an embodiment of the present application;
[0061] Figure 6 Another display schematic diagram of an email sending terminal provided in an embodiment of the present application;
[0062] Figure 7 A display schematic diagram of an email receiving terminal provided in an embodiment of the present application;
[0063] Figure 8 Another display schematic diagram of an email receiving terminal provided in an embodiment of the present application;
[0064] Fig. 9 Another display schematic diagram of an email receiving terminal provided in an embodiment of the present application;
[0065] Fig.10 Another display schematic diagram of an email receiving terminal provided in an embodiment of the present application;
[0066] Fig.11 Another display schematic diagram of an email receiving terminal provided in an embodiment of the present application;
[0067] Fig. 12A Another display schematic diagram of an email receiving terminal provided in an embodiment of the present application;
[0068] Fig. 12B Another display schematic diagram of an email receiving terminal provided in an embodiment of the present application;
[0069] Fig.13 Another display schematic diagram of an email sending terminal provided in an embodiment of the present application;
[0070] Fig.14 Another display schematic diagram of an email sending terminal provided in an embodiment of the present application;
[0071] Fig.15 Another display schematic diagram of an email sending terminal provided in an embodiment of the present application;
[0072] Fig.16 Another display schematic diagram of an email sending terminal provided in an embodiment of the present application;
[0073] Fig.17 Another display schematic diagram of an email sending terminal provided in an embodiment of the present application;
[0074] Fig.18 A schematic diagram of the architecture of the mail application provided in the embodiment of the present application;
[0075] Fig.19 An interaction diagram of functional modules for implementing time limit information configuration provided in an embodiment of the present application;
[0076] Fig. 20 A flowchart of the steps of sending an email in the email creation method provided in an embodiment of the present application;
[0077] Fig.21 An interactive diagram for centralized display of tasks by the first device in the method provided in an embodiment of the present application;
[0078] Fig. 22 An interaction diagram of the functional modules for implementing internal reminders in the email application provided in an embodiment of the present application;
[0079] Fig.23 An interaction diagram of the functional modules for implementing other application reminders provided in an embodiment of the present application;
[0080] Fig.24 An interaction diagram of functional modules for implementing task status monitoring of a sent first email provided in an embodiment of the present application;
[0081] Fig.25 An interaction diagram of functional modules for implementing a reminder for a received first email provided in an embodiment of the present application;
[0082] Fig.26 A flowchart of the steps of reminding a received first device provided in an embodiment of the present application;
[0083] Fig. 27 A schematic diagram of the composition of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION
[0084] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.
[0085] The implementation of this embodiment will be described in detail below with reference to the accompanying drawings.
[0086] Figure 1 A system architecture diagram provided for an embodiment of the present application includes two electronic devices, namely a first device and a second device, and one or more servers. Among them, the first device and the second device can install an email application (application, APP). The first device and the second device can obtain email services from the corresponding server through the email APP. For example, the first device and the second device log in to the user's mailbox through the email APP, and then send and receive emails through the server corresponding to the logged-in mailbox (hereinafter referred to as: the corresponding server).
[0087] It is understandable that in the process of sending and receiving emails, the first device and the second device can play different roles. For example, the first device can be an email sending end, that is, it plays the role of sending emails; the second device can be an email receiving end, that is, it plays the role of receiving emails. In this way, the first device can send emails to the second device through the corresponding server. The second device can also receive emails sent by the first device through the corresponding server.
[0088] For another example, the first device may be an email receiving terminal, and the second device may be an email sending terminal. In this way, the second device may send an email to the first device through a corresponding server. At the same time, the first device may also receive an email sent by the second device through a corresponding server.
[0089] Exemplarily, the electronic device (for example, the first device or the second device) in the embodiments of the present application can be a mobile phone, a tablet computer, a desktop computer, a handheld computer, a notebook computer (laptop), an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), an augmented reality (AR)\virtual reality (VR) device, etc., which can be installed with the above-mentioned email application. The embodiments of the present application do not impose any special restrictions on the specific form of the electronic device.
[0090] Among them, the operating system of the electronic device can be Android, Hongmeng system, IOS system or other operating systems. The embodiment of the present application does not limit the type of operating system of the electronic device.
[0091] In the present application embodiment, Figure 2 Taking the first device or the second device as an electronic device 200 (such as a mobile phone) as an example, the structure of the electronic device provided in the embodiment of the present application is illustrated. Figure 2 As shown, the electronic device 200 (such as a mobile phone) may include: a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an earphone interface 270D, a sensor module 280, a button 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc.
[0092] Among them, the above-mentioned sensor module 280 may include sensors such as pressure sensor, gyroscope sensor, air pressure sensor, magnetic sensor, acceleration sensor, distance sensor, proximity light sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor and bone conduction sensor.
[0093] It is to be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 200. In other embodiments, the electronic device 200 may include more or fewer components than shown in the figure, or combine some components, or separate some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
[0094] The processor 210 may include one or more processing units, for example, the processor 210 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.
[0095] The controller may be the nerve center and command center of the electronic device 200. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.
[0096] The processor 210 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. The memory may store instructions or data that the processor 210 has just used or cyclically used. If the processor 210 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 210, and thus improves the efficiency of the system.
[0097] In some embodiments, the processor 210 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.
[0098] It is understandable that the interface connection relationship between the modules shown in this embodiment is only a schematic illustration and does not constitute a structural limitation on the electronic device 200. In other embodiments, the electronic device 200 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.
[0099] The charging management module 240 is used to receive charging input from a charger. The charger can be a wireless charger or a wired charger. While the charging management module 240 charges the battery 242, it can also power the electronic device through the power management module 241.
[0100] The power management module 241 is used to connect the battery 242, the charging management module 240 and the processor 210. The power management module 241 receives input from the battery 242 and / or the charging management module 240, and supplies power to the processor 210, the internal memory 221, the external memory, the display screen 294, the camera 293, and the wireless communication module 260. In some embodiments, the power management module 241 and the charging management module 240 can also be set in the same device.
[0101] The wireless communication function of the electronic device 200 can be implemented through the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, the modem processor and the baseband processor. In some embodiments, the antenna 1 of the electronic device 200 is coupled with the mobile communication module 250, and the antenna 2 is coupled with the wireless communication module 260, so that the electronic device 200 can communicate with the network and other devices through wireless communication technology.
[0102] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device 200 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of the antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.
[0103] The mobile communication module 250 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 200. The mobile communication module 250 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 250 can receive electromagnetic waves from the antenna 1, and perform filtering, amplification, etc. on the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation.
[0104] The mobile communication module 250 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some functional modules of the mobile communication module 250 can be set in the processor 210. In some embodiments, at least some functional modules of the mobile communication module 250 can be set in the same device as at least some modules of the processor 210.
[0105] The wireless communication module 260 can provide wireless communication solutions for application in the electronic device 200, including WLAN (such as (wirelessfidelity, Wi-Fi) network), Bluetooth (bluetooth, BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), nearfield communication technology (nearfield communication, NFC), infrared technology (infrared, IR), etc.
[0106] The wireless communication module 260 may be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 2, modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 210. The wireless communication module 260 may also receive signals to be sent from the processor 210, modulate the frequencies of the signals, amplify the signals, and convert the signals into electromagnetic waves for radiation via the antenna 2.
[0107] The electronic device 200 implements the display function through a GPU, a display screen 294, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 210 may include one or more GPUs, which execute program instructions to generate or change display information.
[0108] The display screen 294 is used to display images, videos, etc. The display screen 294 includes a display panel.
[0109] The electronic device 200 can realize the shooting function through the ISP, the camera 293, the video codec, the GPU, the display screen 294 and the application processor. The ISP is used to process the data fed back by the camera 293. The camera 293 is used to capture a static image or a video. In some embodiments, the electronic device 200 may include 1 or N cameras 293, where N is a positive integer greater than 1.
[0110] The external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 200. The external memory card communicates with the processor 210 through the external memory interface 220 to implement a data storage function, such as storing music, video and other files in the external memory card.
[0111] The internal memory 221 may be used to store computer executable program codes, which include instructions. The processor 210 executes various functional applications and data processing of the electronic device 200 by running the instructions stored in the internal memory 221. For example, in an embodiment of the present application, the processor 210 may execute the instructions stored in the internal memory 221, and the internal memory 221 may include a program storage area and a data storage area.
[0112] The program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 200 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 221 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.
[0113] The electronic device 200 can implement audio functions such as music playing and recording through the audio module 270, the speaker 270A, the receiver 270B, the microphone 270C, the headphone jack 270D, and the application processor.
[0114] The button 290 includes a power button, a volume button, etc. The button 290 can be a mechanical button. It can also be a touch button. The motor 291 can generate a vibration prompt. The motor 291 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. The indicator 292 can be an indicator light, which can be used to indicate the charging status, power changes, messages, missed calls, notifications, etc. The SIM card interface 295 is used to connect the SIM card. The SIM card can be connected to and separated from the electronic device 200 by inserting it into the SIM card interface 295 or pulling it out from the SIM card interface 295. The electronic device 200 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 295 can support Nano SIM cards, Micro SIM cards, SIM cards, etc.
[0115] In order to make the description of the following embodiments clear and concise, a brief introduction to the relevant concepts or technologies is first given:
[0116] In daily work and business dealings, emails are often used to publish tasks, troubleshoot affairs, and notify events. Among them, emails used to publish tasks or troubleshoot affairs often require the recipient to reply to the email after handling the relevant matters. For example, if the publisher publishes a task to the recipient via email, the recipient needs to feedback the processing results of the task to the publisher via email after handling the task.
[0117] For the convenience of description, all emails that require the recipient to handle and reply are called first emails.
[0118] However, the recipient's mailbox, which is also the receiving mailbox of the first email, receives a large number of other emails every day. Obviously, the display position of the first email in the receiving mailbox will be replaced by the new email. This also means that if the recipient does not immediately process and reply to the first email, the first email may be ignored by the recipient.
[0119] In view of the above problems, an embodiment of the present application provides an email management method. The publisher's mailbox (i.e., the publishing mailbox) sends a first email carrying time limit information to a receiving mailbox. In addition, the receiving mailbox reminds the recipient to handle the first email in time according to the time limit information carried in the first email. This prevents the recipient from forgetting to handle the first email, thereby improving the human-computer interaction efficiency and the intelligence level of email.
[0120] For ease of understanding, the implementation process of the method provided in the embodiment of the present application is introduced by way of example in conjunction with the accompanying drawings. In addition, in the example, the first device is the sender of the first email, and the second device is the receiver of the first email. Among them, the second device logs in to the receiving mailbox of the first email, and can also be called an email receiving device.
[0121] Take the example of a user creating and publishing a first email through a first device (such as mobile phone 1). In the example, the first device is the email sending end of the first email, and can create the first email and send it to the second device.
[0122] After mobile phone 1 starts the mail APP, mobile phone 1 can display the following Figure 3 The interface shown in (a) is the mailbox interface 304 of user A (also called the first interface of the mail application). The mailbox interface 304 includes different mails received by the mailbox of user A, and each mail is arranged in chronological order.
[0123] For example, Figure 3 As shown in (a) in FIG. 3 , user A's mailbox received an email with the subject "Please check the activity photos" (referred to as: email 1), an email with the subject "Attendance sheet for March" (referred to as email 2), and an email with the subject "Investigation of transaction A" (referred to as email 3). Among them, email 1 was sent most recently, and email 2 was sent earlier than email 1 but later than email 3. Therefore, email 1 is displayed at the top in the mailbox interface 304, and emails 2 and 3 are displayed after it.
[0124] In addition, the mailbox interface 304 also includes controls for creating new emails, such as: Figure 3 The control 301 shown in (a) .
[0125] For example, after the mobile phone 1 receives an operation of the user on the control 301, such as a click operation, the following may be displayed: Figure 3 The email editing interface shown in (b) in FIG.
[0126] The above-mentioned email editing interface includes an input field for configuring the receiving mailbox, such as: Figure 3 (b) shows the recipient input box 302.
[0127] In some embodiments, the user can enter an email address in the recipient input box 302, so that the mobile phone 1 can obtain the email address entered by the user and display the email address entered by the user or the email name corresponding to the email address in the recipient input box 302. It can be understood that both the email address and the email name corresponding to the email address refer to the same email address.
[0128] In addition, the recipient input box 302 may also include a control for searching the mailbox address book, such as Figure 3The control 3021 shown in (b) in FIG. 1 is shown. After the mobile phone 1 receives the user's click operation on the control 3021, the email address book interface can be displayed. The email address book interface includes multiple email addresses and email names corresponding to each email address. The user can select an email address in the email address book interface, and the mobile phone 1 can obtain the email address selected by the user according to the user's selection operation in the email address book interface. The email name corresponding to the email address is displayed in the recipient input box 302.
[0129] When creating the first email, the mailbox configured by the user in the recipient input box 302 is the receiving mailbox of the first email, and is also the mailbox that needs to actually process and reply to the first email.
[0130] For example, when creating the first email with the subject "Please complete task item B" (referred to as email 4), mobile phone 1 receives the email addresses of user B and user C entered by the user in the recipient input box 302, and displays the email names of user B and user C in the recipient input box 302. In this scenario, the email addresses of user B and user C are the email addresses that need to be actually processed and replied to email 4.
[0131] In addition, the email editing interface also includes a "Bcc / CC, sender" input field, a "Subject" input field, and an "Email body" editing area. The functions and implementations of the above-mentioned "Bcc / CC, sender" input field, "Subject" input field, and "Email body" editing area can refer to related technologies and will not be repeated here.
[0132] In addition, in the embodiment of the present application, the email editing interface also includes a function entry for configuring time limit information, such as a reminder bar 303. In this way, the mobile phone 1 can configure time limit information for the first email being edited according to the user's operation on the reminder bar 303.
[0133] The time limit information may include one or more of a reminder cycle, a deadline, a reminder time point, etc. The time limit information may indicate a processing period for the first email.
[0134] The reminder cycle is a parameter indicating the time interval between two adjacent reminders, and is used to implement cyclic reminders. The deadline is the last time limit for the receiving mailbox (for example, the mailboxes of user B and user C) to process and reply to the first email. The reminder time point is the time for a single reminder to process the first email. The reminder time point is valid if the receiving mailbox has not processed and replied to the first email.
[0135] For example, if the reminder time of Email 4 is 10:25 AM on April 30, if the time reaches 10:25 AM on April 30 and user C's mailbox has not replied to Email 4, then user C's mailbox will automatically be reminded according to the reminder time. For another example, if user B's mailbox has replied to Email 4 before 10:25 AM on April 30, then user B's mailbox will not be reminded.
[0136] Exemplarily, the reminder bar 303 includes a control for setting time limit information, such as: Figure 3 The reminder configuration 304 shown in (b) of FIG. 1 is a diagram showing a reminder configuration 304. The user can set a time limit for the first email being edited (e.g., email 4) by operating the "reminder configuration" control. In this way, the mobile phone 1 can configure the time limit for the first email being edited according to the user's operation on the reminder configuration 304.
[0137] For example, after receiving the user's click operation on the reminder configuration 304, the mobile phone 1 may display an input box for inputting the time limit information. In this way, the user may input the time limit information in the input box, such as inputting the time limit information in the input box through a virtual keyboard. In this way, the mobile phone 1 may obtain the time limit information input by the user.
[0138] In addition, in other examples, different types of time limit information may be configured through different controls in the reminder bar 303 .
[0139] Exemplarily, the reminder bar 303 includes a control (also referred to as a first control) for setting a reminder period, for example, Figure 4 The period configuration 401 shown in (a) in FIG. 4 is shown in FIG. 4. Thus, the user can set the reminder period by operating the period configuration 401. In this way, the mobile phone 1 can configure the reminder period for the first email being edited according to the user's operation on the period configuration 401.
[0140] In a possible implementation, after the mobile phone 1 receives the user's operation on the period configuration 401, such as a click operation, Figure 4 As shown in (b) of FIG. 4 , a first selection box 402 may be displayed. The first selection box 402 includes a plurality of optional cycle parameters (also referred to as configuration items for characterizing a cycle). Thus, the mobile phone 1 may configure a reminder cycle for the first email being edited according to the user's selection operation of the cycle parameters, such as a click operation.
[0141] For example, the first selection box 402 may include optional periodic parameters such as "None", "10 minutes", "1 hour", "1 day", and "1 week". Taking the case where the user clicks on the periodic parameter "None" as an example, mobile phone 1 receives a selection operation for the periodic parameter "None", which indicates that the user indicates that email 4 does not require periodic reminders. Taking the case where the user clicks on the periodic parameter "1 day" as an example, after mobile phone 1 receives a selection operation for the periodic parameter "1 day", a reminder cycle of reminding every other day can be configured for email 4. This means that after receiving email 4 and identifying the reminder cycle, the receiving mailbox (for example, the mailbox of user B and user C) will remind email 4 every other day until the receiving mailbox completes the reply to email 4. When mobile phone 1 receives a selection operation for other periodic parameters, the same applies to the above, which will not be repeated here.
[0142] Also illustratively, the reminder bar 303 includes a control for setting a deadline (also referred to as a second control), for example, Figure 5 The deadline configuration 501 shown in (a) above is shown in FIG. 1 . Thus, the user can set a deadline by operating the deadline configuration 501. Thus, the mobile phone 1 can configure a deadline for the first email being edited according to the user's operation on the deadline configuration 501.
[0143] In a possible implementation, after the mobile phone 1 receives an operation for the deadline configuration 501, such as a click operation, Figure 5 As shown in (b) of FIG. 5 , a second selection box 502 may be displayed. The second selection box 502 includes a plurality of optional dates and optional time points (ie, configuration items for determining a deadline). According to the user's operation in the second selection box 502, the mobile phone 1 configures a deadline for the first email being edited.
[0144] Taking the example that the user slides to combine April 30, morning and 10:30 in the second selection box 502 and clicks "OK" in the second selection box 502, mobile phone 1 can configure April 30 10:30 am as the deadline of email 4 based on the user's above operation.
[0145] As another example, when the time limit information includes both the deadline and the reminder time point, the reminder bar 303 includes a control for setting the deadline and a control for setting the reminder time point (also referred to as a third control). Figure 6 As shown in (a) in FIG. 1 , it includes a deadline configuration 501 and a reminder time configuration 601 .
[0146] In some embodiments, the implementation of configuring the deadline through deadline configuration 501 can refer to the above-mentioned embodiment and will not be described in detail here.
[0147] In addition, the user can operate the reminder time configuration 601 to set a reminder time point. In this way, the mobile phone 1 can configure a reminder time point for the first email being edited according to the user's operation on the reminder time configuration 601.
[0148] In a possible implementation, after the mobile phone 1 receives the user's click operation on the reminder time configuration 601, a third selection box may be displayed. The third selection box includes a plurality of optional time parameters (also referred to as configuration items for determining the reminder time point). In this way, the mobile phone 1 can configure the reminder time point for the first email being edited according to the user's operation on the time parameter, such as a click operation.
[0149] In some embodiments, the time parameter may be a specific time point or a time interval from a deadline.
[0150] When the time parameter is a specific time point, the mobile phone 1 can directly configure a reminder time point for the first email being edited according to the user's operation on the time parameter.
[0151] For example, the configuration items included in the third selection box can refer to Figure 5 The example shown in (b) is not described in detail here. For example, the time parameters displayed in the third selection box may include 10:10 on April 30, 2021, 10:25 on April 30, 2021, etc. When mobile phone 1 receives the user's click operation on April 30, 2021 at 10:25, 10:25 on April 30, 2021 is directly configured as the reminder time point of the first email.
[0152] In the case where the time parameter is the time interval between the deadline and the e-mail, the mobile phone 1 can configure a reminder time point for the first email being edited based on the user's operation on the time parameter and the configured deadline.
[0153] for example, Figure 6 As shown in (b) in the figure, the third selection box 602 may include multiple time parameters such as "None", "On time", "5 minutes ago", "10 minutes ago", and "15 minutes ago". Taking the case where the user selects the time parameter "None" as an example, mobile phone 1 receives the user's click operation on the time parameter "None". In this scenario, it indicates that the user does not configure a reminder time point for Email 4. Taking the case where the user selects the time parameter "On time" as an example, mobile phone 1 receives a click operation on the time parameter "On time", and based on the click operation, the deadline can be configured as the reminder time point of Email 4. For example, when the deadline is 10:30 on April 30, 2021, mobile phone 1 receives a click operation on "On time", then 10:30 on April 30, 2021 is determined as the reminder time point.
[0154] Taking the user's selection of the time parameter "5 minutes ago" as an example, mobile phone 1 receives the user's selection operation for the time parameter "5 minutes ago". Based on the selection operation, 5 minutes before the deadline is configured as the reminder time point of email 4. For example, when the deadline is 10:30 on April 30, 2021, mobile phone 1 receives the click operation for "5 minutes ago", then 10:25 on April 30, 2021 is determined as the reminder time point.
[0155] Similarly, when the user clicks on the time parameter "10 minutes ago", mobile phone 1 receives the click operation on the time parameter "10 minutes ago". 10 minutes before the deadline is configured as the reminder time point of email 4. For example, when the deadline is 10:30 on April 30, 2021, mobile phone 1 receives the click operation on "10 minutes ago", then 10:20 on April 30, 2021 is determined as the reminder time point. And so on.
[0156] In addition, when the time limit information includes both the deadline and the reminder period, the reminder column 303 may include the deadline configuration 501 and the period configuration 401. In some embodiments, the implementation of configuring the deadline through the deadline configuration 501 and configuring the reminder period through the period configuration 401 can refer to the above embodiments, which will not be repeated here.
[0157] In some scenarios, different types of time limit information can also be configured through the same control in the reminder bar 303. Figure 3 For example, the reminder configuration 304 shown in (b) of FIG. 1 can set different types of time limit information for the first email being edited according to different operations of the user on the reminder configuration 304. For example, when the mobile phone 1 receives the operation 1 on the reminder configuration 304, such as sliding operation, it can display Figure 4 The first selection box 402 shown in (b) of FIG. 1 is used to configure a reminder period for the first email being edited. When the mobile phone 1 receives an operation 2 for the reminder configuration 304, such as a double-click operation, the mobile phone 1 may display Figure 5 The second selection box 502 shown in (b) of FIG. 1 is used to configure a deadline for the first email being edited. When the mobile phone 1 receives a third operation on the reminder configuration 304, such as a long press operation, the display Figure 6 Of course, when the mobile phone 1 receives the fourth operation on the reminder configuration 304, such as a click operation, it can also directly display an input box for receiving time limit information to receive the time limit information input by the user.
[0158] Of course, switching the function of reminder configuration 304 through different operations is only one possible implementation method. In actual implementation, the function of the reminder configuration 304 control can also be switched through the first selection window. That is, when mobile phone 1 receives an operation for reminder configuration 304, the first selection window is displayed. Among them, the first selection window includes options for configuring the reminder cycle, options for configuring the deadline, and options for configuring the reminder time point. Mobile phone 1 can configure the reminder cycle, deadline, or reminder time point for the first email being edited based on the user's selection operation on different options in the first selection window, such as a click operation. For example, when mobile phone 1 receives a user operation on the option in the first selection window for configuring the reminder cycle, it is displayed Figure 4 The first selection box 402 shown in (b) of FIG. 1 is used to configure a reminder period for the first email being edited. When the mobile phone 1 receives the user's operation on the option for configuring the deadline in the first selection window, the display Figure 5 The second selection box 502 shown in (b) of FIG. 1 is used to configure a deadline for the first email being edited. When the mobile phone 1 receives the user's operation on the option for configuring a reminder time point in the first selection window, the display Figure 6 The third selection box 602 shown in (b) in FIG. 1 is used to configure a reminder time point for the first email being edited.
[0159] After completing the configuration of the time limit information, if the mobile phone 1 receives the email sending instruction, the first email configured with the time limit information is sent to the corresponding receiving mailbox. Figure 6 After the control 603 shown in (a) is operated, the email 4 with the configured time limit information can be sent to the mailboxes of user B and user C.
[0160] In an embodiment of the present application, after the first email is sent to a receiving mailbox, the receiving mailbox can automatically remind the recipient based on the time limit information carried in the first email.
[0161] Take the second device (such as mobile phone 2) to log in to the mailbox of user B (that is, the receiving mailbox of mail 4) as an example. In the example, the second device is the mail receiving end of the first mail and can receive the first mail sent by the first device.
[0162] After mobile phone 2 logs into user B's mailbox, it can display the following information: Figure 7 The mailbox interface 702 shown in (a) of FIG. 702 is a display interface of the mail APP in the normal mode.
[0163] It should be noted that the mailbox logged in by the second device can also be called the current mailbox. For example, after mobile phone 2 logs in to user B's mailbox, the current mailbox corresponding to mobile phone 2 is user B's mailbox.
[0164] In addition, the mailbox interface 702 includes different emails received in the current mailbox, and each email is arranged in order of the time when it was sent.
[0165] Exemplarily, the mailbox interface 702 includes an email with the subject "Please complete task item B" (referred to as: Email 4), an email with the subject "Attendance sheet for March" (referred to as: Email 2), and an email with the subject "Investigation of transaction A" (referred to as: Email 3). Among them, Email 4 was sent most recently, and Email 2 was sent earlier than Email 4 but later than Email 3. Therefore, Email 4 is displayed at the top in the mailbox interface 702, and Email 2 and Email 3 are displayed thereafter. Understandably, thereafter, after receiving a new email, the new email will be displayed at the top, and the display positions of other emails (for example, Email 2, Email 3, and Email 4) will also be adjusted accordingly. In this way, once an email is not processed in a timely manner, it may be submerged in many new emails.
[0166] In some embodiments, after mobile phone 2 logs into user B's mailbox, it can also display Figure 7 The mailbox interface 703 shown in (b) in FIG. 703 is the display interface of the mail APP in the reminder mode. Among them, the mailbox interface 703 also includes mail 2, mail 3 and mail 4. Similarly, mail 2, mail 3 and mail 4 are also sorted according to the corresponding sending time order.
[0167] Different from the mailbox interface 702, when the mobile phone 2 displays the received first mail (such as mail 3 and mail 4) in the mailbox interface 703, it can also display prompt information 1 corresponding to the first mail to remind the user to pay attention to the first mail. For example, the prompt information 1 can be a special mark, such as Figure 7 In this way, among the many emails in the mailbox, the user is reminded to pay attention to the first email received by the mailbox.
[0168] In some embodiments, the prompt message 1 may be displayed continuously in the mailbox interface 703. Thus, the first mail is distinguished from other mails.
[0169] In other embodiments, when user B's mailbox has not replied to the first email, prompt message 1 may be displayed for the first email in the mailbox interface 703. When user B's mailbox has replied to the first email, prompt message 1 may be canceled from being displayed for the first email in the mailbox interface 703.
[0170] In other words, in the above embodiment, from the time the first email is displayed on the mailbox interface 703, the prompt message 1 may be displayed corresponding to the first email, until the mobile phone 2 receives a reply operation to the first email, and then cancels the prompt message 1 displayed corresponding to the first email. Thus, the first email that has not been replied to and other emails in the mailbox can be accurately distinguished.
[0171] For example, Figure 8 As shown in (a) of FIG. 7 , the user can click on the email 4 in the mailbox interface 703. The mobile phone 2 can receive the user's click operation on the email 4. In response to the click operation on the email 4, the mobile phone 2 can display the following Figure 8 The details interface of email 4 shown in (b) of FIG. The details interface of email 4 includes controls for replying emails, such as control 801 and control 802. The control 801 is used to instruct the creation of a reply email that only replies to the sender (that is, the mailbox where email 4 is published). The control 802 is used to instruct the creation of a reply email that replies to all persons (that is, the mailbox where email 4 is published and other receiving mailboxes involved in email 4).
[0172] Then, when mobile phone 2 receives a user click operation on control 801 or control 802, an email reply interface can be displayed. While displaying the above-mentioned email reply interface, the user can create a reply email to email 4. In this way, mobile phone 2 can receive relevant data of the reply email, such as the recipient, sender, subject, email body, etc. of the reply email. And after mobile phone 2 receives the user's operation on the send control, the reply email is sent. Among them, the above-mentioned send control is a control in the email reply interface for triggering the sending of a reply email. It can be understood that in the above process, the operation received by mobile phone 2 is also a reply operation to email 4. Afterwards, when mobile phone 2 displays the mailbox interface 703 again, the prompt information 1 of email 4 can be canceled in the mailbox interface 703.
[0173] In other embodiments, the mobile phone 2 may receive an operation of the user on the prompt information 1, such as long pressing the mark 701, to cancel the prompt information 1 displayed in the corresponding email 4. Thus, the user can manually confirm the completion of the reply. In this way, after the user completes the matters assigned by the first email by non-email reply, the user can cancel the reminder on his own, avoiding excessive reminders affecting the user's experience.
[0174] It is understandable that canceling the display of prompt information 1 corresponding to the first email is only a way to prompt that the first email has been replied. In other embodiments, when the user's mailbox has replied to the first email, prompt information 2 (also called the fifth prompt information) corresponding to the first email can be displayed in the mailbox interface 703 to replace the prompt information 1 corresponding to the first email. The prompt information 2 is used to indicate that the reply to the first email has been completed, such as Figure 8 The mark 803 shown in (c) in FIG.
[0175] Of course, if the current mailbox corresponding to the mobile phone 2 has not replied to the first email, a prompt message 1 is displayed corresponding to the first email in the mailbox interface 703. In this way, the mailbox interface 703 can distinguish which first emails need to be processed and which first emails have been processed.
[0176] In general, in the reminder mode, the email APP can display reminder information 1, and after replying to the first email in the current mailbox, display reminder information 2 (or cancel the display of reminder information 1) and other status reminder methods, so that the user can open the mailbox interface 703 and pay attention to the first email to be processed, thereby preventing the user from forgetting the first email in the mailbox. At the same time, it also improves the human-computer interaction efficiency of email reply.
[0177] In some embodiments, when mobile phone 2 starts the email APP, the reminder mode of the email APP is started by default. In other embodiments, when mobile phone 2 receives a user click operation on the email APP icon, an option window may be displayed. The above-mentioned option window includes options representing the normal mode and options representing the reminder mode. When mobile phone 2 receives a user operation on the option representing the normal mode, such as a click operation, the normal mode of the email APP is started. When mobile phone 2 receives a user operation on the option representing the reminder mode, such as a click operation, the reminder mode of the email APP is started.
[0178] Of course, no matter whether the second device enables the normal mode or reminder mode of the mail APP, after the current mailbox corresponding to the second device receives the mail, it will identify whether the mail carries time limit information. When it is identified that it carries time limit information, the mail can be determined as the first mail. And implement a processing reminder for the first mail according to the time limit information to urge the user to handle the first mail in time. Among them, the above-mentioned processing reminder can be a reminder inside the mail APP, such as a fixed-point reminder or overdue reminder realized by one or a combination of timed top display, timed mail notification, prompt information change, etc. Of course, the above-mentioned processing reminder can also be a reminder from other APPs, such as an alarm reminder or a calendar reminder.
[0179] Take the example that the second device (i.e., mobile phone 3) logs into the mailbox of user C and identifies the first email. Fig. 9As shown in (a) of FIG. 1 , after the mobile phone 3 starts the mail APP, it logs into the mailbox of user C and displays the mailbox interface 902. Among them, the mailbox interface 902 includes the mail with the theme of the promotional brochure (referred to as mail 5), mail 3 and mail 4. It can be understood that the above mail 3, mail 4 and mail 5 are all mails received by the mailbox of user C. Therefore, when the mobile phone 3 logs into the mailbox of user C, mail 3, mail 4 and mail 5 will be synchronized to the mailbox, and the above mail 3, mail 4 and mail 5 will be displayed on the mailbox interface 902.
[0180] In the process of synchronizing emails 3, 4, and 5 to the mailbox, mobile phone 3 determines whether emails 3, 4, and 5 carry time limit information by parsing emails 3, 4, and 5. Among them, emails 3 and 4 carry time limit information, while email 5 does not carry time limit information. Therefore, in the reminder mode of starting the email APP, according to the time limit information identified from emails 4 and 3, prompt information 1 is displayed for email 3 in the mailbox interface 902, and prompt information 1 is displayed for email 4. Fig. 9 As shown in (a) in the figure, in the mailbox interface 902, both the mail 3 and the mail 4 are displayed with a corresponding mark 701.
[0181] In addition, the time limit information carried in the first email may include one or more of: a reminder cycle, a deadline, a reminder time point, etc. Of course, different types of time limit information will result in different reminder types.
[0182] For example, when the time limit information carried by the first email includes a deadline, the mobile phone 3 can implement an overdue reminder for the first email according to the deadline. The overdue reminder is used to warn the user that the first email has exceeded the processing deadline.
[0183] For example, when mobile phone 3 parses the deadline carried in email 4 as 10:30 on April 30, if the system time of mobile phone 3 has not reached the deadline and user C's mailbox has not replied to email 4 (for example, mobile phone 3 has not received the user's reply operation to email 4), then Fig. 9 As shown in (a), in the mailbox interface 902, the mark 701 continues to be displayed for the corresponding email 4. If the system time exceeds the deadline, such as the system time reaches 10:31, and the user C's mailbox has not replied to the email 4, then in the mailbox interface 902, the prompt message 3 (also called the second prompt message) is displayed for the corresponding email 4. Among them, the above prompt message 3 is used to remind the user that the first email has exceeded the processing period. The above prompt message 3 can be a prompt character, such as the text "overdue". In addition, the above prompt message 3 can also be a special mark, such as, Fig. 9 The mark 901 shown in (b) in FIG. In the embodiment of the present application, the presentation form of the prompt information 3 is not specifically limited.
[0184] As another example, when the time limit information carried by the first email includes a reminder time point, the mobile phone 3 can implement a fixed-point reminder for the first email according to the reminder time point. The fixed-point reminder is used to remind the user to handle the first email in advance or in time. The fixed-point reminder may include a combination of one or more of displaying the first email on top, sending an email notification for the first email, and adjusting the display form of the prompt information 1 corresponding to the first email.
[0185] For example, the first email can be displayed on top. For another example, an email notification can be sent to the first email. For another example, the display form of the prompt information 1 corresponding to the first email can be adjusted. The display form includes the shape and dynamic and static state of the prompt information 1.
[0186] As an example, when mobile phone 3 parses the reminder time carried in email 4 as 10:25 on April 30, if the system time of mobile phone 3 reaches 10:25, and user C's mailbox has not replied to email 4, then the email APP icon on the main screen of mobile phone 3 can display a reminder message, such as Fig.10 The reminder bubble 1001 shown in (a) of FIG. 1 is used to remind the user that there is a first email to be processed in the mailbox. The reminder bubble 1001 can also be used to indicate to the user the number of first emails to be processed. For example, the number 1 is displayed in the reminder bubble 1001, indicating that there is a first email to be processed in the mailbox. Afterwards, when the mobile phone 3 receives the user's operation on the icon of the email APP, such as clicking the operation, Fig.10 As shown in (b) of FIG. 1 , the mailbox interface 902 is displayed. At this time, the displayed mailbox interface 902 also includes reminder information, such as Fig.10 The reminder bubble 1002 shown in (b) in FIG.
[0187] As another example, when the system time of the mobile phone 3 reaches 10:25, the email 4 can also be displayed on top. Fig.10 As shown in (b), the display position of email 4 is located before other emails, so as to realize the top reminder for email 4.
[0188] As another example, when the system time reaches 10:25, the prompt information 1 corresponding to the email 4 may be changed from the static mark 701 to the dynamic mark 701. The prompt information 1 corresponding to the email 4 may also be changed from the mark 701 to other graphics or text. Understandably, the prompt information 1 before the change may also be called the fourth prompt information, which is used to prompt that the first email is an email that needs to be processed and replied. The prompt information 1 changed to the dynamic or other graphics or text form may also be called the first prompt information, which is used to indicate that the first email is to be processed.
[0189] In addition, in the normal mode, when the first email is received, the mobile phone 3 may not display the prompt information 1 corresponding to the first email. When the system time of the mobile phone 3 reaches the reminder time point, the prompt information 1 corresponding to the first email is displayed. At this time, the displayed prompt information 1 also becomes the first prompt information.
[0190] It is understandable that the reminder time point indicates the time of a single reminder, while the reminder cycle indicates the time of multiple reminders. Exemplarily, when the time limit information includes the reminder cycle, the mobile phone 3 can implement a fixed-point reminder for the first email according to the reminder cycle.
[0191] For example, the reminder cycle carried in the email 4 is parsed by the mobile phone 3 as a reminder every 12 hours. Then, starting from the parsed reminder cycle, a reminder is given every 12 hours. The implementation form of the reminder can refer to the reminder form corresponding to the reminder time point, such as a notification reminder and / or a top reminder.
[0192] As another example, when the time limit information carried by the first email includes a deadline and a reminder time point, mobile phone 3 can send a notification reminder and / or a top reminder for the first email when the system time reaches the reminder time point and the mailbox of user C has not replied to the first email. Mobile phone 3 can send an overdue reminder for the first email when the system time exceeds the deadline and the mailbox of user C has not replied to the first email.
[0193] For example, when the time limit information carried by the first email includes a deadline and a reminder cycle, the mobile phone 3 can send a notification reminder and / or a top reminder for the first email in each reminder cycle until the system time reaches the deadline. When the system time exceeds the deadline, the mobile phone 3 sends an overdue reminder for the first email.
[0194] The handling reminder mentioned in the above example is a reminder inside the mail APP. In the embodiment of the present application, the handling reminder for the first mail can also be a reminder implemented by other APPs. In this way, even if the mobile phone 3 does not start the mail APP, it can remind the user to handle the first mail.
[0195] For example, calendar reminders can be implemented by a calendar APP. Fig.11As shown in (a), mobile phone 3 receives the user's operation on the icon of the calendar APP, such as clicking, and displays the calendar interface 1102. Among them, the calendar interface 1102 includes the reminder item corresponding to the first email, for example, the reminder item corresponding to email 4 is "Reply to email <Please complete task item B>". In addition, the calendar interface 1102 also includes the start time corresponding to the reminder item. Among them, the above-mentioned start time can be determined according to the time limit information of the first email. As an example, when the time limit information includes a reminder time point, the above-mentioned start time can be a period of time after the reminder time point. For example, when the reminder time point of email 4 is 10:25 on April 30, 2021, the start time of the task item corresponding to email 4 can be from 10:25 on April 30, 2021 to 10:30 on April 30, 2021.
[0196] As another example, when the time limit information includes a reminder time point and a deadline, the start time may be the time period between the reminder time point and the deadline. For example, if the reminder time point of Email 4 is 10:25 on April 30, 2021, and the deadline of Email 4 is 10:30 on April 30, 2021, the start time of the task item corresponding to Email 4 may be from 10:25 on April 30, 2021 to 10:30 on April 30, 2021.
[0197] In this way, when the system time of mobile phone 3 reaches 10:25 on April 30, 2021, the fixed-point reminder is first executed. For example, a notification box is displayed on the current interface of mobile phone 3 (such as the home screen). The notification box is used to remind the user of the first email to be processed, such as Fig.11 The notification box 1101 shown in (b) in FIG. The notification box 1101 includes content that needs to be handled by the user.
[0198] Afterwards, when the system time reaches 10:30 on April 30, 2021, the mobile phone 3 executes an overdue reminder. For example, a notification box is displayed on the current interface (eg, home screen) of the mobile phone 3. At this time, the displayed notification box is used to remind the user that the first email has expired.
[0199] As another example, the alarm reminder can also be realized by the clock APP. For example, when the system time of the mobile phone 3 reaches the reminder time point or the time indicated by the reminder cycle, an alarm reminder box is displayed on the current interface of the mobile phone 3 (such as the main screen), such as Fig. 12A The reminder box 1201 is shown. Alternatively, when the system time of the mobile phone 3 reaches the reminder time point or the time indicated by the reminder cycle, the mobile phone 3 can ring, vibrate, and other types of reminders. Alternatively, the mobile phone 3 can display an alarm reminder box and ring, vibrate, and remind, which is not specifically limited in this embodiment.
[0200] In addition, the mailbox logged in by the second device (such as mobile phone 2 and mobile phone 3) can receive multiple emails with time limit information. In order to facilitate the management of the above multiple emails with time limit information, the second device can centrally display the corresponding task items, thereby prompting the user to process the above emails.
[0201] Understandably, the first email refers to all emails with time limit information. That is, the first email can be an email sent by the device or an email received by the device. In order to distinguish the description, the first email received by the device can also be called the second email.
[0202] Taking mobile phone 3 as an example, when mobile phone 3 receives the first operation of the user, it displays Fig. 12B The task processing interface 1202 shown in (a) in the figure. Among them, the task processing interface 1202 may include task items representing the received second email. For example, task item 1203 corresponding to email 4, and task item 1204 corresponding to email 3. The task items can be arranged in the time sequence corresponding to the second email. As an example, the above time sequence can be the sending time sequence corresponding to the second email. Among them, the above sending time can be parsed from the second email. As another example, the above time sequence can be the order in which the second email is received in the mailbox of user C. In the task processing interface 1202, the processing status of the second email is also displayed at each task item. For example, the processing status of email 4 is displayed at task item 1203, such as displaying the characters "not processed". The processing status of email 3 is displayed at task item 1204, such as displaying the characters "not processed".
[0203] As an example, the first operation that triggers the mobile phone 3 to display the task processing interface 1202 may be: the mobile phone 3 receives the user's operation on the first email displayed in the mailbox interface 902, such as double-clicking the prompt information 1 corresponding to the first email.
[0204] As another example, the first operation that triggers the mobile phone 3 to display the task processing interface 1202 may also be: when the mobile phone 3 receives a click operation of the user on the first email displayed in the mailbox interface 902, the second selection window is displayed. The second selection window includes an option for viewing the task processing interface and an option for viewing the email body. When the mobile phone 3 receives the user's selection of the option for viewing the task processing interface, it is determined that a specific operation made by the user has been received.
[0205] In some other embodiments, the task processing interface 1202 may be popped up when the system time of the mobile phone 3 reaches the reminder time point or the deadline.
[0206] In addition, in the embodiment of the present application, a reminder for the first email can be implemented in the task processing interface 1202 according to the time limit information of the first email.
[0207] For example, when the system time of mobile phone 3 reaches the reminder time point corresponding to the first email, the task item corresponding to the first email is displayed at the top in the task processing interface 1202. Fig. 12B As shown in (b) of FIG. 1 , the task item 1203 corresponding to the email 4 is displayed on the top. In addition, a prompt message 4 can be displayed at the task item 1203. The prompt message 4 can be a mark for prompting that the email 4 is to be done, such as the mark 1205. Thus, a timed reminder for the first email is implemented in the task processing interface 1202.
[0208] In another exemplary embodiment, when the system time of mobile phone 3 exceeds the deadline corresponding to the first email, prompt information 5 (also called third prompt information) is displayed at the task item of the first email. Prompt information 5 is used to remind that the first email is overdue. For example, when the system time exceeds the deadline corresponding to email 4, in the task processing interface 1202, Fig. 12B As shown in (c) in FIG. 1 , a mark 1206 is displayed at the task item 1203 .
[0209] In addition, it should be noted that the above reminders are all made on the premise that user C’s mailbox has not replied to the first email.
[0210] That is, for the second device, after sending a reply email to the first email, the second device no longer issues a processing reminder for the first email.
[0211] At the same time, for the first device, after receiving the reply email to the sent first email, the first device can also automatically count the reply emails corresponding to the first email. When the first email corresponds to multiple receiving mailboxes, the user does not need to check which receiving mailboxes have been replied and which have not been replied, thereby improving the efficiency of human-computer interaction. In addition, the first device can also treat each sent first email as a task item for management.
[0212] For example, user B's mailbox has replied to email 4, but user C's mailbox has not replied to email 4. When the mailbox that published email 4 (that is, user A's mailbox) receives the reply email sent by user B's mailbox, Fig.13 As shown in (a) of FIG. 1 , the mailbox interface 304 of the mobile phone 1 includes a reply email from user B to email 4. Email 4 is the first email with time limit information configured. Therefore, when the mobile phone 1 receives the user's operation on the reply email, such as a click operation, Fig.13As shown in (b) of FIG. 1 , a third selection window 1301 may be displayed. The third selection window 1301 includes two options: task management and email body.
[0213] Taking the example of the user selecting task management in the third selection window 1301, the mobile phone 1 receives the operation of the user clicking the task management option, which means that the user wants to view the reply status of email 4, which can also be called the reply status. Among them, the reply status can be the reply statistics of email 4, that is, the reply status can represent the correlation between the number of receiving mailboxes that have replied to email 4 and the number of all receiving mailboxes corresponding to email 4. For example, the reply status can be displayed in the form of statistical results such as a reply ratio chart and a reply percentage. The above operation for triggering the display of the task management interface can also be called an operation on the task management option.
[0214] Taking the example of the user selecting the email body in the third selection window 1301, the mobile phone 1 receives the user's operation of clicking the email body option, indicating that the user wants to view the actual content of the reply email.
[0215] In addition, when the mobile phone 1 receives the operation of selecting task management by the user, the mobile phone 1 displays the following Fig.13 The task management interface shown in (c) (also called the third interface of the mailbox) is shown in FIG. 1. When the mobile phone 1 receives the operation of the user selecting the body of the email, the mobile phone 1 displays the content interface corresponding to the reply email.
[0216] The task management interface includes a task item corresponding to the first email published by user A's mailbox. The task item includes information representing the reply status of the first email, that is, the task status, such as Fig.13 Completion information 1302 shown in (c).
[0217] For example, email 4 corresponds to two receiving mailboxes, and only one receiving mailbox replied to email 4. Fig.13 As shown in (c) in the task management interface, the task item 1303 corresponding to the email 4 may display the corresponding completion information 1302, such as a reply ratio of 1 / 2 and a reply ratio graph representing 1 / 2.
[0218] For another example, the first email (referred to as email 6) with the subject "Checking Transaction C" published by the current mailbox corresponds to a receiving mailbox, and the receiving mailbox has replied to email 6. Fig.13 As shown in (c) in the task management interface, the task item 1304 corresponding to the email 6 may display the corresponding completion information 1302, such as a reply ratio of 1 / 1 and a reply ratio graph representing 1 / 1.
[0219] For another example, the first email (referred to as email 7) with the subject "Please process task item D" published by the current mailbox corresponds to four receiving mailboxes, and three of the four receiving mailboxes have replied to email 7. Fig.13 As shown in (c) in the task management interface, the task item 1305 corresponding to the email 7 may display the corresponding completion information 1302, such as a value of 3 / 4 reply ratio and a reply ratio graph representing 3 / 4.
[0220] Through the display of the task management interface, users can directly and quickly understand the response status of the receiving mailbox to each first email without manual statistics. This improves the efficiency of human-computer interaction and is more accurate. Its advantages are particularly obvious when multiple first emails are published.
[0221] In addition, when the mobile phone 1 receives an operation on a task item, such as a click operation, the reply details of the first email corresponding to the task item can also be displayed.
[0222] For example, Fig.14 As shown in (a) of FIG. 1 , after receiving a click operation on the task item for email 4 (ie, task item 1303), as shown in FIG. Fig.14 As shown in (b) in the figure, reply details 1401 are displayed, such as reply details 1401 including: user B's mailbox has replied to email 4, while user C's mailbox has not yet received a reminder of email 4. In some embodiments, the above reminder can exist in the form of an image symbol or a character. In this way, the user can also more accurately grasp the reply status of user B's mailbox and user C's mailbox to email 4. The user does not need to check all the reply emails received about email 4 one by one. While enhancing the intelligence of the mailbox, the user's experience is improved.
[0223] In addition to the user actively checking the reply status of the first email, the mobile phone 1 can also actively remind the user to check the reply status of the sent first email.
[0224] As an implementation method, mobile phone 1 can remind the user to check the reply status of the sent first email according to the time limit information configured when the first email is created, so as to prevent the sent first email from being forgotten. For example, when email 4 is created, the time limit information is configured, then mobile phone 1 can automatically remind the user based on the configured time limit information, so as to prevent the user from forgetting the sent email 4.
[0225] The method of reminding the user to check the reply status of the first email may be a reminder inside the email APP or a reminder outside the email APP.
[0226] The following uses the time limit information including reminder time point and deadline as an example to introduce the reminders within the Mail APP.
[0227] When the system time reaches the reminder time point, the email APP itself can make a timed notification. For example, the task item corresponding to the first email can be displayed on the top and / or marked as needing attention in the task management interface. For another example, the first email can be displayed on the top and / or marked as needing attention in the outbox interface of the email application.
[0228] For example, take the reminder time of Email 4 as 10:25 am on April 30. After the system time reaches 10:25 am on April 30, if mobile phone 1 receives the user's operation of opening the email APP, it will display the following Fig.15 The mailbox interface 304 shown in (a) above. The mailbox interface 304 displays reminder information, such as a reminder bubble 1501. The reminder bubble 1501 is used to remind the user that there are to-do items in the mailbox. In addition, the reminder bubble 1501 can also be used to remind the user of the number of to-do items in the mailbox. For example, the number 1 is displayed in the reminder bubble 1501, indicating that there is a to-do item in the current mailbox. In addition, the mailbox interface 304 also includes controls for switching mailbox folders, such as control 1502. The above controls correspond to the inbox icon of the mailbox interface 304. The user can view the to-do items prompted by the reminder bubble 1501 by operating the control 1502, such as clicking on it.
[0229] After mobile phone 1 receives a click operation on control 1502, it displays the following Fig.15 The folder interface 1504 shown in (b) of FIG. The folder interface 1504 includes options corresponding to the inbox, options corresponding to unread mails, options corresponding to sent mails, and options corresponding to task management. When the mobile phone 1 receives the user's operation on the option corresponding to the inbox, the mailbox interface 304 is displayed. When the mobile phone 1 receives the user's operation on the option corresponding to the unread mail, the folder of the unread mail is displayed. When the mobile phone 1 receives the user's operation on the option corresponding to the sent mail, the folder of the sent mail is displayed.
[0230] The option corresponding to task management displays reminder information, such as reminder bubble 1503. Reminder bubble 1503 is used to remind that the to-do item is a first email that needs to be paid attention to. For example, the number 1 is displayed in reminder bubble 1503, indicating that the to-do item is a first email that needs to be paid attention to.
[0231] Afterwards, mobile phone 1 receives an operation on an option corresponding to task management, such as a click operation. Fig.15As shown in (c) in the figure, mobile phone 1 can display a task management interface. The above operation of triggering the display of the task management interface can also be an operation of the task management option. In the task management interface, the task item 1303 corresponding to email 4 is pinned to the top, and a to-do mark, such as mark 1505, is displayed corresponding to email 4, and the mark 1505 is used to remind the user that he needs to pay attention to the reply status of email 4.
[0232] In addition, when the system time reaches the reminder time point, among the receiving mailboxes corresponding to the first email, there is at least one receiving mailbox that has not replied to the first email, then the email APP can also issue an overdue notification reminder.
[0233] For example, the deadline for email 4 is 10:30 am on April 30. After the system time reaches 10:31 am on April 30, there is at least one receiving mailbox that has not replied to email 4, for example, user C's mailbox has not replied to email 4. Fig.16 As shown, in the task management interface, the task item corresponding to the email 4 is displayed at the top, and a mark indicating overdue is displayed at the task item, for example, the character "overdue" is displayed.
[0234] As another example, the first email may be displayed on top and / or marked as overdue in the outbox interface of the mobile phone 1 .
[0235] In addition, when the reminder time point corresponding to the first email arrives, the reply email to the first email can be arranged before other emails in the mailbox interface 304, so as to facilitate the user to check the actual reply to the first email.
[0236] In a possible implementation, other applications other than the email APP can also remind based on the time limit information. For example, an alarm clock application can remind the user. For another example, a calendar application can remind the user. In this way, even if the user does not enter the email APP, the user can be reminded in time. This prevents the user from ignoring the first email that has been sent. The specific implementation is similar to the implementation of the second device reminder, and will not be repeated here.
[0237] As another implementation, the mobile phone 1 can also set a reminder time for the first email according to the user's operation, and then remind the user to check the reply status of the sent first email according to the reminder time.
[0238] It can be understood that the principle of reminding the user to check the reply status of the first email according to the prompt time is the same as the aforementioned principle of reminding the user to check the reply status of the first email according to the time limit information.
[0239] Take the above reminder time as an example, including the preset reminder time point and the preset overdue reminder time point. When the system time reaches the preset reminder time point, the email APP itself can make a notification reminder or other applications can make a reminder. When the system time exceeds the overdue reminder time point, there is at least one receiving mailbox in the receiving mailbox corresponding to the first email that has not replied to the first email, then the email APP can also make an overdue notification reminder.
[0240] In addition, in some embodiments, the pre-prompt time point and the reminder time point in the time limit information may be different time points. The overdue prompt time point and the final time limit in the time limit information may be different time points.
[0241] In addition, the electronic devices (first device and second device) can both create and send first emails, and receive first emails sent by other devices. In order to facilitate the management of sent first emails and received first emails, in some embodiments, the task items corresponding to the received first emails and the task items corresponding to the sent first emails can be displayed separately through different interfaces. For example, through Fig. 12B The task processing interface 1202 shown in the figure displays the task item corresponding to the first email received. Fig.13 The task management interface shown in (c) displays the task items corresponding to the first email that has been sent.
[0242] In other embodiments, the task items corresponding to the received first emails and the task items corresponding to the sent first emails can also be displayed through the same interface. Fig.17 As shown, the task item list in the task management interface 1701 can be divided into two sub-items, namely, the "assigned tasks" sub-item and the "received tasks" sub-item. The task items corresponding to all the first emails sent from the mailbox of user A can be displayed under the "assigned tasks" sub-item. The task items corresponding to all the first emails received by the mailbox of user A can also be displayed under the "received tasks" sub-item.
[0243] The software systems of the first device and the second device can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system of the layered architecture as an example to exemplify the software structure of the first device and the second device.
[0244] The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system library, and the kernel layer.
[0245] The application layer may include a series of application packages, such as mail, camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.
[0246] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.
[0247] The application framework layer may include a view system, a notification manager, an Http request, a synchronization manager, an account manager, a device manager, etc., and the embodiments of the present application do not impose any restrictions on this.
[0248] The above view system can be used to build the display interface of the application. Each display interface can be composed of one or more controls. Generally speaking, controls can include interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc.
[0249] The Notification Manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction. For example, the Notification Manager is used to notify download completion, message reminders, etc. The Notification Manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, a vibration is made, an indicator light flashes, etc.
[0250] The above sync manager (syncmanager) is used to synchronize files corresponding to applications, for example, synchronizing email data received by an email APP.
[0251] The system library and kernel layer below the application framework layer can be called the underlying system. The underlying system includes an underlying display system for providing display services. For example, the underlying display system includes a display driver in the kernel layer and a surface manager in the system library.
[0252] Exemplarily, the method provided in the embodiment of the present application can be executed in a mail application (mail application) of an electronic device (such as a first device and a second device).
[0253] like Fig.18 As shown, the email application of the electronic device may include a business layer, a protocol layer, a control layer and a storage layer.
[0254] The business layer corresponding to the electronic device includes business function modules that can be implemented by the email APP. In the embodiment of the present application, it can include account login, email receiving & identification, email display, email writing & sending, email reminder, task management, etc.
[0255] Among them, account login includes POP account login, IMAP account login, Exchange account login, etc. Mail reception includes account information synchronization, folder information synchronization and mail information synchronization. Of course, the implementation of the above account login and mail reception can refer to the introduction in the relevant technology, and will not be repeated here.
[0256] The above-mentioned email display, in addition to displaying the account list, folder list and email list, will also display the task item list corresponding to the first email that has been published in the task management interface or display the task item list corresponding to the first email that has been received in the task processing interface.
[0257] In addition, email writing & sending includes: time limit configuration (refer to the time limit information configuration process in the above embodiment), email writing and email sending. In addition, in addition to the regular email reminder, email reminders can also be based on time limit information for fixed-point reminders, overdue reminders and marking status. Finally, task management includes centralized display of tasks, task status refresh and task statistics.
[0258] Of course, the realization of the aforementioned functions requires the support of the corresponding control layer of the electronic device.
[0259] In an embodiment of the present application, the control layer corresponding to the electronic device may include a login control module, a receiving control module, a display control module, a sending control module, an email identification module, a reminder control module, and a task management control module. Among them, the login control module can support the implementation of account login. The receiving control module can support the implementation of email reception. The display control module can support the implementation of email display. The sending control module can support the implementation of email writing and sending. The reminder control module can support the implementation of email reminders. The task management control module can support the implementation of task management.
[0260] It is not difficult to understand that in the process of implementing the control layer support function, it is also necessary to follow the mailbox protocol provided by the protocol layer corresponding to the first device. The mailbox protocol provided by the protocol layer corresponding to the first device includes Internet Mail Access Protocol (IMAP), Exchange Active Sync (EAS), Post Office Protocol Version 3 (POP3), Simple Mail Transfer Protocol (SMTP) and Multipurpose Internet Mail Extensions (MIME) Information Protocol (MIMEMessage Protocol for short).
[0261] For example, when the IMAP protocol is followed, the login control module can implement IMAP account login. When the EAS protocol is followed, the login control module can implement EAS account login. When the POP3 protocol is followed, the login control module can implement POP account login. In addition, when the IMAP protocol (or POP3 protocol) is followed to implement IMAP account login (or POP account login), the sending control module can send the generated email data according to the SMTP protocol.
[0262] For another example, before sending the email data, the sending control module needs to construct the email header and email body (including the email body and email attachments) of the email in accordance with the provisions of the MIMEMessage protocol.
[0263] In addition, after the first email is edited, the fields and data corresponding to the first email are stored in the storage layer corresponding to the first device. When the first device determines that the first email needs to be sent, the fields and data corresponding to the first email are obtained from the storage layer and encapsulated according to the MIMEMessage protocol. After the first email is sent, the first email will still be stored locally, that is, the field data corresponding to the first email in the storage layer will not be deleted.
[0264] The storage layer corresponding to the above electronic device may include an account table, a folder table, an email header table, an email body table, and an attachment table. Among them, the account table is used to store the information of the mailbox account. The folder table is used to store the folder information under each mailbox account (inbox, outbox, sent emails, pending emails, draft box, etc.). The email header table is used to store the metadata of the email (recipient, sender, cc, subject, summary, etc.). The email body table is used to store the text content of the email. The attachment table is used to store the attachment part of the email data.
[0265] In the embodiment of the present application, the above-mentioned mail header table is also used to store time limit information, so as to encapsulate the time limit information into the mail header. It can be understood that the first device encapsulating the time limit information into the mail header will not cause the mail to be filtered.
[0266] Of course, in some embodiments, the first device may also encapsulate the time limit information in the body of the email, which is not specifically limited.
[0267] After receiving the email, the receiving control module also needs to parse the corresponding email header and email body (including email body and email attachments) according to the MIMEMessage protocol and store them in the storage layer.
[0268] In addition, the mail application of the electronic device can also interact with the application framework layer of the electronic device to obtain the required system support.
[0269] The following continues to describe the implementation principle of the email application provided in the embodiment of the present application.
[0270] When the electronic device receives an operation of creating a new email from the user (e.g., receiving a user click on control 301), the display control module can call the view system to display the email editing interface. In the embodiment of the present application, the sending control module can receive the time limit information and email data (e.g., including email metadata, email body, and email attachments) configured by the user, and configure them to the first email being edited.
[0271] As an implementation method, the sending control module may include a time limit configuration submodule, an email writing submodule and a sending control submodule. Fig.19 As shown, the email application running process provided by the embodiment of the present application is as follows:
[0272] S1, the time limit configuration submodule receives the time limit information configured by the user.
[0273] In some embodiments, the time limit configuration submodule may receive information transmitted by controls in the reminder bar. For example, the controls in the reminder bar may include a combination of one or more of controls for setting a reminder period, a control for setting a deadline, and a control for setting a reminder time point.
[0274] When receiving the user's operation on the control for setting the reminder cycle, the time limit configuration submodule displays the first selection box by calling the view system. In this way, the time limit configuration submodule can obtain the configured reminder cycle according to the user's operation in the first selection box.
[0275] When receiving the user's operation on the control for setting the deadline, the deadline configuration submodule displays the second selection box by calling the view system. In this way, the deadline configuration submodule can obtain the configured deadline according to the user's operation in the second selection box.
[0276] When receiving the user's operation on the control for setting the reminder time point, the time limit configuration submodule displays the third selection box by calling the view system. In this way, the time limit configuration submodule can obtain the configured reminder time point according to the user's operation in the second selection box.
[0277] S2, the time limit configuration submodule stores the time limit information in the corresponding email header table.
[0278] In some embodiments, the received time limit information may also be converted into a standard format, such as a format required by iCalendar, and the time limit information after the format conversion is written into the mail header table of the storage layer.
[0279] In other embodiments, the time limit information may also be stored in the email body table, so that the time limit information can be easily encapsulated into the email body.
[0280] S3, the email writing submodule receives the email data edited by the user.
[0281] In some embodiments, the email writing submodule can receive email data entered by the user in the recipient input box, the "BCC / CC, Sender" input field, the "Subject" input field, the "Email Body" editing area, and the email attachment adding area. For example, the receiving email address entered by the user in the recipient input box. Another example is the CC email address and the sending email address entered by the user in the "BCC / CC, Sender" input field. Another example is the email subject entered by the user in the "Subject" input field. Another example is the email body entered by the user in the "Email Body" editing area. Another example is the email attachment added by the user in the email attachment adding area.
[0282] S4, the email writing submodule stores the received email data into corresponding tables respectively.
[0283] In some embodiments, the corresponding tables may be a mail header table, a mail body table, and an attachment table of a storage layer. Exemplarily, a receiving mailbox, a sending mailbox, a cc mailbox, a subject, a summary, etc. may be stored in the mail header table. The mail body may be stored in the mail body table. The mail attachment may be stored in the attachment table.
[0284] It is understandable that there is no necessary order between the above S1 and S3. At the same time, before the email is sent, the time limit information and email data stored in the storage layer can be modified. In some embodiments, if the user does not cooperate with the time limit information, only S3 and S4 can be included.
[0285] S5, when the sending control submodule receives the user's email sending operation, it queries and obtains the time limit information and email data configured by the user in the email editing interface from the storage layer.
[0286] In some embodiments, after the data corresponding to the first email being edited is stored in the storage layer, it will be associated with the folder of the email to be sent. In this way, after the sending control submodule receives the user's email sending operation, it can search for the table item associated with the folder of the email to be sent from the email header table, the email body table, and the attachment table, thereby obtaining the time limit information and email data configured by the user in the email editing interface. That is, the fields and data of the first email are obtained.
[0287] S6, the sending control submodule constructs the first email.
[0288] In some embodiments, the sending control submodule obtains the fields and data of the first email from the storage layer according to the specification of the MIMEMessage protocol, and constructs the email header and email body (including the email body and email attachments) of the first email.
[0289] Among them, the MIMEMessage protocol is the email format standard, which includes the email header specification (refer to rfc4021) and the email body specification.
[0290] In the embodiment of the present application, the specification of the email header in the MIMEMessage protocol is improved to achieve the encapsulation of the time limit information into the email header.
[0291] In some embodiments, the first device may add a reminder field to the email header. The reminder field may include one or more of a field representing a reminder time point (e.g., ReminderTime), a field representing a deadline (EndTime), and a field representing a reminder period. In this way, after receiving the time limit information, it may be written into the corresponding field of the email header according to the type of the time limit information.
[0292] For example, the email header with added reminder time and deadline is as follows:
[0293] Return-Path:<mlemos@acm.org>
[0294] To:Manuel Lemos<mlemos@linux.local>
[0295] Subject:Testing Manuel lemos'MIME E-mail composing and sending PHPclass:HTML massage
[0296] From:mlemos:<mlemos@acm.org>
[0297] Reply-To:<mlemos@acm.org>
[0298] Sender: mlemos@acm.org
[0299] Remindertime:300 / / 5 minutes before the deadline
[0300] EndTime:2021xxxxx
[0301] MIME-Version:1.0
[0302] Content-Type:multipart / mixed;
[0303] Among them, the reminder time point (Remindertime:300) and the deadline (EndTime:2021xxxx) in the above email header are newly added fields, and the other parts are an example of a regular email header. The above deadline can refer to the standard format of the date. For example, after 18:30:00 on September 1, 2012 is converted into the standard time format, it becomes 20120901T183000.
[0304] As another example, the email header with added reminder period and deadline is as follows:
[0305] Return-Path:<mlemos@acm.org>
[0306] To:Manuel Lemos<mlemos@linux.local>
[0307] Subject:Testing Manuel lemos'MIME E-mail composing and sending PHPclass:HTML massage
[0308] From:mlemos:<mlemos@acm.org>
[0309] Reply-To:<mlemos@acm.org>
[0310] Sender: mlemos@acm.org
[0311] RRULE:FREQ=MONTHLY;INTERVAL=2;BYADY=29 / / 29th of every other month
[0312] EndTime:2021xxxxx
[0313] MIME-Version:1.0
[0314] Content-Type:multipart / mixed;
[0315] Among them, the reminder period (RRULE:FREQ=MONTHLY;INTERVAL=2;BYADY=29) and deadline (EndTime:2021xxxx) in the above email header are newly added fields, and the other parts are an example of a regular email header.
[0316] The above reminder cycle can be configured according to the iCalendar specification. iCalendar, referred to as "iCal", is a standard for "Calendar Data Exchange" (RFC 2445), which provides a common data format for storing calendar information, such as events, appointments, to-do items, etc. It not only allows users to send meetings or to-do items via email, but also allows independent use without being limited to a certain transmission protocol. It can support the setting of repeated reminders.
[0317] It can be understood that RRULE, Remindertime and EndTime are only example fields for storing time limit information. In other embodiments, other fields may be defined for storing time limit information. In the embodiments of the present application, the field format for storing time limit information is not specifically limited.
[0318] That is, if Fig. 20 As shown, the method provided by the embodiment of the present application may include: obtaining email content data from the storage layer. Among them, the email content data includes email header related data and email body related data. The email header related data includes the recipient address, the recipient address, the cc address, the email subject, the time limit information in a standard format, etc. The email body related data includes the email body, the email attachments, etc. According to the email header related data, in accordance with the provisions of the MIMEMessage protocol, construct an email header with time limit information, that is, the email header of the first email. According to the email body related data, in accordance with the provisions of the MIMEMessage protocol, construct the email body of the first email. It can be understood that after the email header and email body of the first email are constructed, the complete first email is obtained.
[0319] In addition, the sending control submodule can also use the corresponding mail transfer protocol to send the first mail through the corresponding server. For example, when the mail APP logs in to the IMAP account, the sending control submodule can send the first mail through the SMTP server according to the SMTP protocol. For another example, when the mail APP logs in to the POP account, the sending control submodule can send the first mail through the SMTP server according to the SMTP protocol.
[0320] In addition, after the first email is created, the electronic device starts managing the first email. Each first email corresponds to a task item. The task item has a task status, and the task status can be the reply status of the receiving mailbox to the first email. If all the receiving mailboxes have replied to the first email, the task status is completed. If there is a receiving mailbox that has not replied to the first email, the task is incomplete.
[0321] In the embodiment of the present application, task management can be divided into parts such as centralized task display, task status refresh and task statistics.
[0322] In some embodiments, Fig.21 As shown, after the sending control module writes the obtained time limit information into the storage layer, the specific indicator bit in the storage layer changes from the first mark to the second mark. After the task management control module of the electronic device monitors the change of the specific indicator bit in the storage layer, it triggers the query of the first email from the storage layer. Exemplarily, the task management control module can query the table entry with time limit information in the stored email header table. For example, check whether there is a reminder field in the table entry of the email header table. If an entry with time limit information is found, and the corresponding email has been sent (for example, the email has been associated with a folder of sent emails), the task management control module creates a task item based on the email corresponding to the entry (that is, the first email), and displays it in the display control module. Fig.14 In the task management interface shown in (a) of FIG. 1 , after the task management control module of the electronic device completes the search, the specific indication bit in the storage layer can also be restored to the first mark.
[0323] In addition, after the above-mentioned first email is sent, in the embodiment of the present application, the reminder control module can remind the user to pay attention to the reply status of the first email.
[0324] As an implementation method, the reminder control module may include a time monitoring submodule, a fixed-point reminder submodule, and an overdue reminder submodule. For example, the time limit information includes a reminder time point and a deadline. Fig. 22As shown, the time monitoring submodule monitors the changes of the system time and compares the system time with the time limit information stored in the storage layer. If the system time reaches the reminder time indicated by the time limit information, the fixed-point reminder submodule or the overdue reminder submodule initiates an email reminder.
[0325] For example, when the time monitoring submodule monitors that the system time reaches the reminder time point, the fixed-point reminder submodule may be notified to start the fixed-point reminder, thereby reminding the user to pay attention to the published first email.
[0326] As an implementation method, the fixed-point reminder can be a notification reminder and / or a task top reminder. Exemplarily, the fixed-point reminder submodule can call the notification mechanism (NotificationManager) of the application framework layer to complete the notification reminder. Exemplarily, the fixed-point reminder submodule can determine the first email with the smallest difference between the reminder time point and the system time, and mark the first email to indicate that it needs to be displayed on the top. In this way, when the task management control module sorts the task items corresponding to the first email that has been sent, the task items with the top display mark are arranged before other task items to obtain a list of task items. In this way, when the display control module displays the task item list on the task management interface, the task items that reach the corresponding reminder time point can be displayed in the top position.
[0327] Afterwards, when the time monitoring submodule detects that the system time exceeds the deadline and there is at least one receiving mailbox that has not responded, an overdue reminder is issued.
[0328] As an implementation method, the overdue reminder can be a notification reminder, a task top reminder and / or an overdue mark. The overdue reminder submodule can call the notification mechanism (NotificationManager) of the application framework layer to complete the notification reminder. The overdue reminder submodule can determine the first email with the smallest difference between the deadline and the system time, and mark the first email to indicate that it needs to be displayed on the top. In this way, when the task management control module sorts the task items corresponding to the first email that has been sent, the task items with the top display mark are arranged before other task items to obtain a list of task items. The display control module then displays the list of task items on the task management interface. In addition, the fixed-point reminder submodule and the overdue reminder submodule may mark the first email differently, and the reminder control module may further include a marking submodule. In this way, when the marking submodule recognizes that the first email is marked by the overdue reminder submodule, the marking submodule can display the overdue mark corresponding to the first email in the task management interface by calling the view system, such as Fig.16 The characters in "overdue".
[0329] Of course, in other possible embodiments, combined with Fig.23As shown, after the reminder control module of the electronic device detects that an email is stored in the storage layer (e.g., detects that a specific indication bit of the storage layer changes to a second mark), it queries whether the stored email has time limit information. If the time limit information is present, the time limit information can be obtained from the storage layer and passed to other programs (e.g., an alarm clock application or a calendar application) to implement an alarm clock reminder and / or a calendar reminder.
[0330] In some embodiments, the receiving control module may include a receiving submodule and an identifying submodule. Fig.24 As shown, the receiving submodule can receive new emails from the server. For example, when the email APP of the electronic device logs in to an IMAP account (or POP account), the receiving submodule can receive emails through the SMTP server.
[0331] In some embodiments, the receiving submodule may periodically collect new emails from the server according to a predetermined collection period, for example, collecting emails from the corresponding server once every 10 minutes.
[0332] In other embodiments, the receiving submodule may be automatically triggered to receive new emails from the server when the email APP is started.
[0333] In other possible embodiments, the receiving submodule may receive a user's receiving operation. For example, when the user slides down on the mailbox interface, the receiving submodule may receive a new email from the server in response to the received sliding operation.
[0334] After receiving the email, the receiving submodule can also split the email into the email header part, the email body part and the email attachment part, and store them in the email header table, the email body table and the attachment table respectively. At the same time, the identification submodule can also parse the email header of the email. Among them, the email header includes the key header field: References (refer to RFC4021 and RFC2822). References includes a list of message-id records, that is, the reply chain of the email. For example, email B replies to email A, and References can be "MessageA, MessageB". In References, MessageA is the message-id of email A, and MessageB is the message-id of email B. MessageA is the root node of References and is also the source email corresponding to MessageB. Therefore, it can be determined that email B is a reply to email A.
[0335] Therefore, in some embodiments, the identification submodule can obtain the root node of the new email by parsing the References field in the email header, and determine whether the root node of the new email is the first email published by the current mailbox, that is, determine whether the new email is a reply email to the first email.
[0336] If yes, the task status corresponding to the first email is updated through the task management control module. For example, the new email is added to the statistical table corresponding to the first email. Then, according to the number of reply emails in the statistical table and the number of mailboxes receiving the first email, the reply ratio of the first email is determined. Thus, the task status corresponding to the first email is updated. In this way, the user can understand the task completion status of the first email more quickly and conveniently.
[0337] After the task status corresponding to the first email is updated, the display control module may also update the task status of the task item corresponding to the first email in the task management interface.
[0338] In other embodiments, after the identification submodule determines that the root node of the new email is the message-id of the first email, it can also determine whether the new email is a duplicate email in combination with the statistical table corresponding to the first email, thereby improving the accuracy of statistics.
[0339] Exemplarily, the identification submodule can compare the stored emails in the statistical table with the new email. For example, the References field of the stored email and the new email are compared. If the same References field exists between the two, the new email is determined to be a duplicate reply email. There is no need to put the new email into the statistical table, and the task status will not be triggered to update. For example, if the References field of the email stored in the statistical table is "MessageA, MessageB", and the References field of the new email is "MessageA, MessageB", then the new email is determined to be a duplicate email.
[0340] Obviously, the electronic device can also quickly identify the reply email corresponding to the first email that has been sent based on the References field of the received email. When it is necessary to remind the user to pay attention to the first email that has been published, the electronic device can also first use the References field to identify the corresponding reply email and arrange the identified reply email before other emails. This is convenient for the user to check.
[0341] In addition, the electronic device can create a first email, and can also receive a first email sent by other mailboxes. The above identification submodule can also be used to identify whether the received email is the first email sent by other mailboxes. The following description is taken as an example of the electronic device being the email receiving end of the first email.
[0342] As a way to achieve this, Fig.25 As shown, the identification submodule can parse and identify the mail header stored in the storage layer. For example, after parsing the mail header of the received mail according to the provisions of the MIMEMessage protocol, it is determined whether there is a field for storing time limit information in the mail header. If so, it is determined that the first mail sent by other mailboxes is received.
[0343] Exemplarily, the identification submodule may determine whether the new email is the first email by identifying fields such as RRULE and EndTime in the email header.
[0344] Finally, when the identification submodule finds that the first email is received, the marking submodule can display a prompt message 1 corresponding to the first email in the mailbox interface 703 by calling the view system.
[0345] As an example, after the identification submodule determines that the email stored in the storage layer is the first email, the marking submodule can also write a specific mark for the email in the storage layer, wherein the specific mark is used to indicate that the email is the first email. In this way, when the emails received by the user's mailbox are displayed on the mailbox interface 703, for emails with specific marks, prompt information 1 is displayed for the emails in the mailbox interface 703; for emails without specific marks, only the email itself is displayed in the mailbox interface 703.
[0346] After the identification submodule determines that the received email is the first email, the time monitoring submodule in the reminder control module can monitor the system time and compare the system time with the time limit information of the first email. If the monitored system time reaches the reminder time indicated by the time limit information, the fixed-point reminder submodule or the overdue reminder submodule starts the email reminder.
[0347] Take the time limit information as an example of reminder time point and deadline, combined with Fig.26 , the method provided by the embodiment of the present application may include: the time monitoring submodule monitors the system time changes in real time. In addition, the time monitoring submodule is also used to receive operations perceived by the reply control. Among them, the reply control can be a combination of multiple controls, such as, the reply control can include a control for triggering the display of the details interface of the first email, a control for triggering the editing of the reply email, and a control for sending the email. In this way, the time monitoring submodule can promptly detect whether the current mailbox has replied to the first email. For example, when the user operation information transmitted by the control for triggering the display of the details interface of the first email, the control for triggering the editing of the reply email, and the control for sending the email is received in sequence, it can be determined that the first email has been replied.
[0348] If the corresponding current mailbox has replied to the first email, the notification mark submodule adjusts the prompt information corresponding to the first email, for example, replacing the prompt information 1 displayed on the first email with the prompt information 2.
[0349] If the current mailbox has not replied to the first email, it is determined whether the system time has reached the reminder time of the first email. If the reminder time has been reached, a fixed-point reminder is started.
[0350] As an implementation method, the fixed-point reminder can be a notification reminder and / or an email top reminder (for example, Fig.10 shown).
[0351] Exemplarily, the reminder control module may call the notification mechanism (NotificationManager) of the application framework layer to complete the notification reminder.
[0352] For example, the reminder control module can search for the entry corresponding to the first received email in the email header table and obtain the reminder time point. Then, the reminder control module compares the reminder time point with the system time. If the system time reaches the reminder time point, the first email is marked in the storage layer to indicate that the email needs to be displayed at the top. In this way, when arranging the received email list, the display control module arranges the first email marked to be displayed at the top before other received emails, thereby realizing the email top reminder.
[0353] After that, the time monitoring submodule continues to determine whether the system time has reached the deadline. If the system time exceeds the deadline, an overdue reminder (such as Fig. 9 For example, when the time monitoring submodule determines that the system time exceeds the deadline, the marking submodule is notified to change the prompt information 1 corresponding to the first email to prompt information 3.
[0354] Of course, in other possible embodiments, the reminder control module can also pass the time limit information in the storage layer to other programs (such as an alarm application or a calendar application) to implement an alarm reminder and / or a calendar reminder, such as, Fig.11 and Fig. 12A shown.
[0355] The present application also provides an electronic device, which may include: a wireless communication module, a memory, and one or more processors. The wireless communication module, the memory, and the processor are coupled. The memory is used to store computer program code, and the computer program code includes computer instructions. When the processor executes the computer instructions, the electronic device can execute the various steps in the above embodiment. Of course, the electronic device includes but is not limited to the above wireless communication module, the memory, and one or more processors. For example, the structure of the electronic device can refer to Figure 2 The structure shown.
[0356] The present application also provides a chip system, which can be applied to the electronic device in the above embodiment. Fig. 27 As shown, the chip system includes at least one processor 2201 and at least one interface circuit 2202. The processor 2201 may be a processor in the above-mentioned electronic device. The processor 2201 and the interface circuit 2202 may be interconnected via a line. The processor 2201 may receive and execute computer instructions from the memory of the above-mentioned electronic device through the interface circuit 2202. When the computer instructions are executed by the processor 2201, the electronic device may execute the various steps executed by the mobile phone in the above-mentioned embodiment. Of course, the chip system may also include other discrete devices, which are not specifically limited in the embodiments of the present application.
[0357] Through the description of the above implementation methods, technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.
[0358] Each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units.
[0359] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as flash memory, mobile hard disk, read-only memory, random access memory, disk or optical disk.
[0360] The above is only a specific implementation of the embodiment of the present application, but the protection scope of the embodiment of the present application is not limited thereto, and any changes or replacements within the technical scope disclosed in the embodiment of the present application should be included in the protection scope of the embodiment of the present application. Therefore, the protection scope of the embodiment of the present application should be based on the protection scope of the claims.
Claims
1. A mail management method, characterized in that: The method comprises: The electronic device sends a first email to the email receiving device; the first email is an email configured with time limit information, the time limit information is used to instruct the email receiving device to remind the first email, and the time limit information includes a reminder time point; The electronic device receives a reply email to the first email from the email receiving device; The electronic device counts the reply status corresponding to the first email; the electronic device displays the reply status corresponding to the first email in a task management interface of an email application, wherein the reply status includes the status of at least one reply email corresponding to the first email; The method further includes: when the system time of the electronic device reaches the reminder time point, the electronic device displays the first email at the top in the outbox interface of the email application.
2. The method according to claim 1, characterized in that Before the electronic device sends the first email to the email receiving device, the method further includes: The electronic device receives the email content of the first email edited by the user and the time limit information configured for the first email; The sending control module in the electronic device stores the first email into the storage layer of the electronic device; The storage layer changes the specific indication bit from a first mark to a second mark in response to the time limit information of the first mail; The task management control module of the electronic device detects the change of the specific indication bit and searches the storage layer for the first email having the reminder field; After finding the first email with the reminder field, the task management control module creates a task item for the first email, and changes the specific indicator from the second mark to the first mark.
3. The method according to claim 1, characterized in that The outbox interface includes other emails sent later than the first email. After the first email is displayed on the top, the other emails are arranged in the order of sending time.
4. The method according to claim 1, characterized in that Before displaying the reply status corresponding to the first email, the method further includes: In response to the operation on the first email, displaying a third selection window, wherein the third selection window includes a task management option and an email body option; In response to an operation on the task management option, a task management interface of the mail application is displayed.
5. The method according to claim 1, characterized in that The method further comprises: The electronic device receives an email and parses the email header of the email to obtain a reply chain of the email; Confirm that the source email indicated by the reply chain is the first email, and determine that the email is a reply email to the first email.
6. The method according to claim 1, characterized in that The task management interface also includes: a processing status of a second email, wherein the second email is an email received by the electronic device and has time limit information, and the processing status includes processed and not processed.
7. The method according to claim 1, characterized in that The response status includes a response ratio chart and / or a response percentage; The electronic device counts the number of the reply emails and the total number of receiving mailboxes corresponding to the first email, and determines a reply ratio chart and / or a reply proportion.
8. The method according to claim 1, characterized in that The task management interface also includes a task item corresponding to the first email, and the method further includes: When the electronic device receives an operation on the task item, it displays reply details of the first email; wherein the reply details include information indicating whether the receiving mailbox corresponding to the first email has replied.
9. The method according to claim 1, characterized in that The method further comprises: When the system time reaches the reminder time point, the electronic device displays the task item of the first email on the top in the task management interface and / or displays a to-do mark corresponding to the task item of the first email.
10. The method according to claim 1, characterized in that The method further comprises: When the system time reaches the reminder time point, the electronic device displays a to-do mark corresponding to the first email in the outbox interface of the email application.
11. The method according to any one of claims 1, 9 and 10, characterized in that: The time limit information includes a deadline; and the method further includes: When the system time exceeds the deadline and no reply email is received from at least one receiving mailbox to the first email, the electronic device displays an overdue mark for the task item corresponding to the first email in the task management interface, and / or displays the task item of the first email at the top in the task management interface.
12. The method according to any one of claims 1, 9 and 10, characterized in that: The time limit information includes a deadline; and the method further includes: When the system time exceeds the deadline and no reply email is received from at least one receiving mailbox to the first email, the electronic device displays an overdue mark corresponding to the first email in the outbox interface of the email application and / or displays the first email at the top in the outbox interface.
13. The method according to claim 1, characterized in that The method further comprises: The first email is reminded through a calendar application or an alarm clock application in the electronic device to prompt the user to check the reply status of the first email.
14. The method according to claim 13, characterized in that Before reminding the first email through a calendar application or an alarm clock application in the electronic device, the method further includes: According to the time limit information, a schedule reminder is configured in a calendar application, and / or an alarm reminder is configured in an alarm application.
15. An electronic device, characterized in that: The electronic device comprises one or more processors, one or more memories and a wireless communication module; the one or more memories and the wireless communication module are coupled to the one or more processors; The one or more memories are used to store computer program codes, wherein the computer program codes include computer instructions. When the one or more processors execute the computer instructions, the method according to any one of claims 1 to 14 is implemented.
16. A computer storage medium, characterized in that: The method comprises computer instructions, which, when executed on an electronic device, cause the electronic device to execute the method as claimed in any one of claims 1 to 14.