Reminding method based on task processing and electronic equipment

Abstract

The embodiment of the invention provides a reminding method based on task processing and electronic equipment. In the method, after a user downloads a file, a suspension ball corresponding to the file is displayed in a preview interface of the file, and operation guidance is performed on the user. According to the method and the device, the file can be stored in a self-defined storage path by operating a suspension ball option, so that subsequent management is facilitated, and personalized storage of the file is realized. Wherein in the file preview interface, the floating ball is displayed on the top, and the user can execute related operation based on the guidance of the floating ball at any time, so that the experience brought to the user by the task guidance prompt is improved.

Description

Reminder method and electronic device based on task processing

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on October 25, 2022, with application number 202211311331.8 and application name “Task processing-based reminder method and electronic device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of smart terminal technology, and in particular to a reminder method and electronic device based on task processing. Background Art

[0003] With the development of terminal technology, electronic devices have become indispensable tools in all aspects of people's daily lives. The functions of various applications on electronic devices have also been gradually improved, providing users with various intelligent services and bringing great convenience to their work and life.

[0004] However, when a user uses an electronic device, how the electronic device can remind the user based on task processing so that the user can complete related operations conveniently is a problem that needs to be solved urgently.

[0005] Summary of the Invention

[0006] To address the above technical issues, embodiments of the present application provide a task-based reminder method and electronic device. In this method, a floating ball displayed on top guides the user through the task. The user can perform related operations at any time based on the guidance of the floating ball, thus improving the user experience of task guidance prompts.

[0007] In a first aspect, an embodiment of the present application provides a task-based reminder method. The method includes: an electronic device displays a first interface, the first interface including a received first file; the electronic device receives a first operation on the first file; the first operation is used to download the first file; when the first file is downloaded, the electronic device displays a second interface; the second interface includes a preview interface of the first file and a first floating window, the first floating window includes a first option; the electronic device stores the first file in a directory of a target folder in response to the second operation on the first option, the target folder is a folder with custom permissions, and the target folder is different from the system folder; the electronic device displays a third interface, the third interface is an interface of a file management application, the third interface includes the target folder and the system folder; the electronic device displays the first file under the target folder in response to the third operation on the target folder.

[0008] The first floating window corresponds to the first file and is used to guide related operations of the first file.

[0009] It should be noted that, on the preview interface of the first file, the first floating window will not disappear automatically.

[0010] Exemplarily, the first operation may be a click operation on the first file, and the electronic device may download the first file based on the user's click operation in the third-party application interface; the first operation may also be an operation in which the user clicks on the menu of the first file and clicks the save button in the menu, and the electronic device downloads the first file based on the user's manual operation of saving the first file.

[0011] For example, the first option may be a button for storing the first file separately, such as "Copy to", "Save as", or "Move to". The second operation may be an operation of clicking the first option or double-clicking the first option to confirm the selection of the first option.

[0012] Exemplarily, the third operation is an operation of viewing the target folder.

[0013] Among them, the system folder is the default file storage directory for third-party applications. Files received by the terminal device through third-party applications can be saved to the system folder directory according to the default path. Usually, the default path of third-party applications is complex and obscure, and difficult for ordinary users to master. The target folder is different from the system folder. Both the target folder and the system folder are displayed on the interface of the file management application. The user has customized permissions for the target folder. For example, the user can operate under the target folder to create a new folder, delete a folder, rename a folder, etc., and can also create multiple levels of subdirectories as needed. The target folder can be named "My Folder" or "My Files", etc. The user can store the first file to a customized path in the target folder. When the user opens the interface of the file management application, he can find the desired file in the target folder according to the customized path. This method does not require the user to master the obscure and complex default path to achieve file search, making file search more convenient and quick, and improving the user experience.

[0014] The floating balls displayed on the preview screens of different files correspond to different files and are used to guide users to perform related operations on the corresponding files. That is, on the preview screen of the first file, a floating window corresponding to the first file is displayed, guiding users to perform operations related to the first file; on the preview screen of the second file, a floating window corresponding to the second file is displayed, guiding users to perform operations related to the second file.

[0015] In this way, after the user downloads a file, a floating window corresponding to the file will be displayed in the file preview interface to guide the user. Among them, the user can save the file to a custom storage path by operating the floating window option for subsequent management, thereby realizing personalized storage of the file. Among them, in the file preview interface, the floating window is displayed at the top, and the user does not need to complete the relevant considerations and perform the relevant operations in a short time. When necessary, the user only needs to perform the relevant operations according to the guidance of the function options in the floating ball. In this way, the user will not have the problem of not knowing how to perform relevant operations on the file because he cannot find the guidance of the function options.

[0016] According to the first aspect, the method further includes: the electronic device closing the preview interface of the first file and canceling the display of the first floating window in response to a fourth operation on the preview interface of the first file.

[0017] Exemplarily, the fourth operation is an operation of closing the preview interface.

[0018] In this way, the first floating window corresponding to the first file will disappear only when the preview interface of the first file is closed, and the user will not have the problem of not knowing how to perform related operations on the file due to not being able to find the guidance of the function options.

[0019] According to the first aspect, or any implementation of the first aspect above, after canceling the display of the first floating window, the method also includes: the electronic device displays a fourth interface in response to the fifth operation on the first file; the fourth interface includes a preview interface of the first file and the first floating window.

[0020] Exemplarily, the fifth operation may be an operation of opening the first file in a third-party application.

[0021] Therefore, after the first file is opened again, the first floating window corresponding to the first file will still be displayed to guide the user in operation.

[0022] According to the first aspect, or any implementation of the first aspect above, the first floating window is a first floating ball.

[0023] According to the first aspect, or any implementation of the first aspect above, the initial form of the first floating ball is a folded state; the method also includes: the electronic device responds to a sixth operation on the first floating ball, and the form of the first floating ball is adjusted to an expanded state; wherein, when the first floating ball is in the expanded state, a first option is displayed on the first floating ball.

[0024] Exemplarily, the sixth operation may be a click operation.

[0025] In this way, the initial form of the floating ball corresponding to the file is a folded state, which occupies a smaller area in the terminal interface and does not interrupt the user's viewing experience of the file.

[0026] According to the first aspect, or any implementation of the first aspect above, in response to the seventh operation on the first floating ball, or the eighth operation received, or when no user operation is received within a set time, the shape of the first floating ball is adjusted from the expanded state to the folded state.

[0027] In this way, the shape of the floating ball used to guide the user's operation can be adjusted according to the user's needs, and will not affect the user's viewing of the file preview content.

[0028] According to the first aspect, or any implementation of the first aspect above, the first floating window also includes a second option; the method also includes: the electronic device displays a fifth interface in response to an eighth operation on the second option; the fifth interface includes a preview interface of the first file and a first sharing window, the first sharing window includes icons of multiple sharing objects, and the icons of the multiple sharing objects include an icon of the first object; the electronic device sends the first file to the first object in response to the received ninth operation.

[0029] Exemplarily, the second option may be a sharing option.

[0030] In this way, the user can open the sharing window by clicking the share option on the floating ball and share the file with the target object of the user's choice, realizing resource sharing and enriching the terminal's functions. Compared with the process of users actively searching for files and then sharing them, this embodiment directly opens the sharing window by clicking the share option on the floating ball, thereby sharing files more conveniently and quickly, improving the efficiency of resource sharing and enhancing the user experience.

[0031] According to the first aspect, or any implementation of the first aspect above, the first floating window also includes a third option; the method also includes: the electronic device displays a sixth interface in response to a ninth operation on the third option; the sixth interface includes a print preview interface and a print option for the first file; and in response to a tenth operation on the print option, sending an instruction to print the first file to the printing device.

[0032] Exemplarily, the third option may be a print option.

[0033] In this way, the user can open the print preview interface by clicking the print option on the floating ball and complete the print operation for the relevant file. Compared with the method of completing the file printing operation based on the sharing window, this embodiment directly opens the print window by clicking the print option on the floating ball, which is more convenient and efficient, improves the efficiency of file printing, and enhances the user experience.

[0034] According to the first aspect, or any implementation of the first aspect above, the first floating window also includes a fourth option; the method also includes: the electronic device displays a seventh interface in response to the tenth operation on the fourth option; the seventh interface includes a preview interface and prompt information of the first file, and the prompt information is used to indicate that the first file has been saved to the desktop card; the electronic device displays the desktop in response to the received eleventh operation; the desktop includes a desktop card, and the desktop card includes an icon control of the first file; the electronic device displays a preview interface of the first file in response to the twelfth operation on the icon control of the first file.

[0035] Exemplarily, the fourth option may be a save to desktop option.

[0036] In this way, the user can add the file to the desktop file management card by operating the Save to Desktop option on the floating ball, so that when the user wants to view the file content later, the user does not need to open the corresponding third-party application again to find the corresponding file. The user can directly click the file icon in the desktop file management card to view the file content. The operation is more convenient and efficient, which improves the user experience.

[0037] According to the first aspect, or any implementation of the first aspect above, the first interface is an interface of a third-party application.

[0038] According to the first aspect, or any implementation of the first aspect above, the method also includes: the electronic device displays an eighth interface; the eighth interface includes a schedule reminder notification, and the schedule reminder notification includes schedule information and a fifth option; the electronic device responds to the thirteenth operation on the fifth option, cancels the display of the schedule reminder notification, and displays a second floating window, and the second floating window includes a sixth option; the electronic device responds to the fourteenth operation on the sixth option, and displays a ninth interface; the ninth interface is used to execute matters that match the schedule information.

[0039] Exemplarily, the fifth option may be to add a floating ball option.

[0040] The sixth option matches the schedule content, and the ninth interface also matches the schedule content. For example, for a meeting schedule, the sixth option may be the "Join Now" option, and the ninth interface may be the meeting application interface; for a ticket purchase schedule, the sixth option may be the "Buy Now" option, and the ninth interface may be the ticket purchase application interface.

[0041] The floating balls corresponding to different schedule reminders are used to guide users to perform related operations on different schedules. That is, the floating window corresponding to the first schedule is used to guide users to perform related operations on the first schedule, and the floating window corresponding to the second schedule is used to guide users to perform related operations on the second schedule.

[0042] In this way, the terminal device can use the floating ball to remind the user of the schedule, so as to guide the user to perform operations corresponding to the schedule, making it more convenient for the user to handle related schedules.

[0043] According to the first aspect, or any implementation of the first aspect above, the method further includes: the electronic device cancels display of the second floating window in response to a fourteenth operation on the sixth option.

[0044] According to the first aspect, or any implementation of the first aspect above, the second floating window includes a seventh option; the method also includes: the electronic device displays the tenth interface in response to the fifteenth operation on the seventh option; the tenth interface includes schedule information and a second sharing window, the second sharing window includes icons of multiple sharing objects, and the icons of the multiple sharing objects include an icon of the second object; the electronic device sends the schedule information to the second object in response to the received sixteenth operation.

[0045] Exemplarily, the seventh option may be a sharing option.

[0046] In this way, the user can open the sharing window by clicking the share option on the floating ball and share the schedule with the target recipient of the user's choice, thus realizing schedule sharing and enriching the terminal's functions. Compared with the process of users actively searching for schedules and then sharing them, this embodiment directly opens the sharing window by clicking the share option on the floating ball, thereby sharing schedules more conveniently and quickly, improving the efficiency of resource sharing and enhancing the user experience.

[0047] According to the first aspect, or any implementation of the first aspect above, the method further includes: the electronic device cancels display of the second floating window in response to a fifteenth operation on the seventh option.

[0048] According to the first aspect, or any implementation of the first aspect above, the method further includes: the electronic device cancels display of the second floating window in response to the fifteenth operation on the seventh option; and the electronic device continues to display the second floating window after sending the schedule information to the second object.

[0049] According to the first aspect, or any implementation of the first aspect above, the second floating window includes an eighth option; the method further includes: the electronic device cancels display of the second floating window in response to a sixteenth operation on the eighth option.

[0050] Exemplarily, the eighth option is a cancel option.

[0051] According to the first aspect, or any implementation of the first aspect above, the schedule reminder notification includes schedule reminder information displayed in the form of an alarm clock, schedule reminder information displayed in the form of a banner notification, and schedule notification information displayed in the notification center or on the lock screen interface.

[0052] According to the first aspect, or any implementation of the first aspect above, the schedule information includes: meeting schedule information, entertainment schedule information, and transaction schedule information.

[0053] For example, the entertainment schedule information may include a schedule for watching movies and TV series, a schedule for watching live broadcasts, and the like.

[0054] For example, the transaction schedule information may include ticket purchase schedule, etc.

[0055] According to the first aspect, or any implementation of the first aspect above, the second floating window is a second floating ball; the initial form of the second floating ball is a folded state; the method also includes: the electronic device responds to the seventeenth operation on the second floating ball, and the form of the second floating ball is adjusted to an expanded state; wherein, when the second floating ball is in the expanded state, a sixth option is displayed on the first floating ball.

[0056] According to the first aspect, or any implementation of the first aspect above, the method further includes: the electronic device responds to the thirteenth operation on the fifth option, setting the schedule reminder again after N minutes, where N is a positive integer.

[0057] In this way, the user can make the terminal device remind the user of the schedule N minutes later with one operation, and can also make the terminal device display the floating ball corresponding to the schedule reminder to remind the user of the schedule in real time.

[0058] In a second aspect, embodiments of the present application provide an electronic device. The electronic device includes: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory and, when executed by the one or more processors, cause the electronic device to perform the task-based reminder method of the first aspect and any one of the first aspects.

[0059] The second aspect and any implementation of the second aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the second aspect and any implementation of the second aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0060] In a third aspect, embodiments of the present application provide a computer-readable storage medium comprising a computer program, which, when executed on an electronic device, causes the electronic device to execute the task-based reminder method of the first aspect and any one of the first aspects.

[0061] The third aspect and any implementation of the third aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the third aspect and any implementation of the third aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0062] In a fourth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed, enables a computer to execute the task-based reminder method according to the first aspect or any one of the first aspects.

[0063] The fourth aspect and any implementation of the fourth aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the fourth aspect and any implementation of the fourth aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0064] In a fifth aspect, the present application provides a chip comprising a processing circuit and a transceiver pin. The transceiver pin and the processing circuit communicate with each other via an internal connection path, and the processing circuit executes the task-based reminder method according to the first aspect or any one of the first aspects to control the receiving pin to receive a signal and to control the transmitting pin to send a signal.

[0065] The fifth aspect and any implementation of the fifth aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the fifth aspect and any implementation of the fifth aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] FIG1 is a schematic diagram showing a hardware structure of an electronic device;

[0067] FIG2 is a schematic diagram illustrating a software structure of an electronic device;

[0068] FIG3a is a schematic diagram illustrating an exemplary application scenario;

[0069] FIG3 b is a schematic diagram illustrating an exemplary application scenario;

[0070] FIG4 is a schematic diagram illustrating an exemplary application scenario;

[0071] FIG5 is a schematic diagram illustrating an exemplary application scenario;

[0072] Figures 6a-6b are schematic diagrams illustrating exemplary adjustment of the morphology of a suspended ball;

[0073] FIG7 is a schematic diagram showing an exemplary embodiment of adjusting the position of a suspension ball;

[0074] 8a-8b are schematic diagrams showing exemplary scenes of the floating ball disappearing;

[0075] FIG9 is a schematic diagram illustrating an exemplary application scenario;

[0076] Figures 10a to 10d are schematic diagrams illustrating exemplary application scenarios of the suspended ball;

[0077] FIG11 is a schematic diagram showing an exemplary creation of a new schedule;

[0078] FIG12 is a schematic diagram showing an exemplary schedule reminder;

[0079] Figures 13a to 13e are schematic diagrams illustrating exemplary addition of suspended balls;

[0080] FIG14 is a schematic diagram illustrating an exemplary application scenario;

[0081] Figures 15a-15c are schematic diagrams showing exemplary adjustment of the shape of the suspended ball;

[0082] Figures 16a to 16d are schematic diagrams illustrating exemplary application scenarios of the suspended ball;

[0083] FIG17 is a schematic diagram illustrating an exemplary application scenario;

[0084] FIG18 is a schematic diagram illustrating an exemplary application scenario;

[0085] FIG19 is a schematic diagram showing an exemplary application scenario. DETAILED DESCRIPTION

[0086] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0087] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0088] In the description and claims of the embodiments of this application, the terms "first" and "second" are used to distinguish different objects, rather than to describe a specific order of objects. For example, the terms "first target object" and "second target object" are used to distinguish different objects, rather than to describe a specific order of objects.

[0089] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0090] In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more. For example, "multiple processing units" means two or more processing units; "multiple systems" means two or more systems.

[0091] The task-processing-based reminder method provided in the embodiments of the present application can be applied to mobile phones, tablet computers, wearable devices, in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), and other terminal devices. The embodiments of the present application do not impose any restrictions on the specific type of terminal device. For ease of explanation, the following application scenarios are explained using a mobile phone as an example.

[0092] As shown in Figure 1, a schematic diagram of the structure of an electronic device 100 is shown. Optionally, the electronic device 100 can be a terminal, which can also be called a terminal device. The terminal can be an electronic device such as a cellular phone or a tablet computer, which is not limited in this application. It should be understood that the electronic device 100 shown in Figure 1 is only an example of an electronic device, and the electronic device 100 can have more or fewer components than shown in the figure, can combine two or more components, or can have different component configurations. The various components shown in Figure 1 can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0093] The electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195. The sensor module 180 may include a pressure sensor, a gyroscope sensor, an acceleration sensor, a temperature sensor, a motion sensor, an air pressure sensor, a magnetic sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

[0094] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (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). The 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 100. 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 110 may further include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory.

[0097] The USB interface 130 is an interface that complies with USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100 and to transfer data between the electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as AR devices.

[0098] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also provide power to the electronic device via the power management module 141.

[0099] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to provide power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160.

[0100] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0101] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0102] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 100. The mobile communication module 150 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc.

[0103] The wireless communication module 160 can provide wireless communication solutions for application on the electronic device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication technology (NFC), infrared technology (IR), etc.

[0104] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150 , and antenna 2 is coupled to wireless communication module 160 , so that electronic device 100 can communicate with the network and other devices through wireless communication technology.

[0105] Electronic device 100 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0106] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than one.

[0107] The electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

[0108] The ISP processes data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then passed to the ISP for processing and transformed into a visible image. The ISP can also perform algorithmic optimization for image noise, brightness, and skin tone. It can also optimize parameters such as exposure and color temperature of the captured scene. In some embodiments, the ISP can be located within camera 193.

[0109] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0110] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function.

[0111] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121, such as enabling the electronic device 100 to implement the reminder method based on task processing in the embodiment of the present application. The internal memory 121 may include a program storage area and a data storage area. Among them, 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 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 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.

[0112] The electronic device 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0113] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

[0114] Speaker 170A, also known as a "horn," is used to convert audio electrical signals into sound signals. Electronic device 100 can listen to music or make hands-free calls through speaker 170A. In some embodiments, electronic device 100 can be provided with multiple speakers 170A.

[0115] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or a voice message, the user can place the receiver 170B close to the ear to hear the voice.

[0116] Microphone 170C, also known as "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to the microphone 170C to input the sound signal into the microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the source of sound, realize directional recording function, etc.

[0117] The headphone jack 170D is used to connect a wired headphone and can be the USB interface 130 or a 3.5mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0118] Specifically in the technical solution provided in the embodiment of the present application, the sensor module 180 needs to include at least a touch sensor and a pressure sensor.

[0119] Among them, the pressure sensor is used to sense the pressure signal and convert the pressure signal into an electrical signal. In some implementations, the pressure sensor can be set on the display screen 194. There are many types of pressure sensors, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor can be a device comprising at least two parallel plates with conductive material. When a force acts on the pressure sensor, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the intensity of the touch operation based on the pressure sensor. The electronic device 100 can also calculate the position of the touch based on the detection signal of the pressure sensor. In some implementations, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions.

[0120] Among them, the touch sensor is also called a "touch panel". The touch sensor can also be set on the display screen 194, and the touch sensor and the display screen 194 form a touch screen, also called a "touch screen". The touch sensor is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event, for example, it can include touch event types such as sliding, clicking, and long pressing. Visual output related to the touch operation can be provided through the display screen 194. In other implementations, the touch sensor can also be set on the surface of the electronic device 100, which is different from the position of the display screen 194. Specifically, in the technical solution provided in the embodiment of the present application, when the user touches or taps the touch screen, the touch sensor will monitor the user's operation behavior, and the electronic device 100 will receive data collected by the touch sensor in the touch screen, and will perform matching operations in response to the operation behavior.

[0121] In the electronic device 100, the gyroscope sensor can be used to determine the motion posture of the electronic device 100. In some embodiments, the gyroscope sensor can be used to determine the angular velocity of the electronic device 100 around three axes (i.e., the x, y, and z axes). The acceleration sensor can detect the magnitude of the acceleration of the electronic device 100 in various directions (generally three axes). When the electronic device 100 is stationary, the acceleration sensor can detect the magnitude and direction of gravity. The acceleration sensor can also be used to identify the posture of the electronic device, which is applied to applications such as switching between horizontal and vertical screens and pedometers.

[0122] Keys 190 include a power button (also known as a power button), a volume button, and the like. Keys 190 may be mechanical keys or touch-sensitive keys. Electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of electronic device 100.

[0123] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or touch vibration feedback. For example, touch operations on different applications (such as taking photos, playing audio, etc.) can correspond to different vibration feedback effects.

[0124] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0125] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present application, the Android system with a layered architecture is used as an example to illustrate the software structure of the electronic device 100.

[0126] FIG2 is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present application.

[0127] The layered architecture of electronic device 100 divides the software into several layers, each with a clear role and division of labor. Layers communicate with each other via software 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 libraries, and the kernel layer.

[0128] The application layer can include a series of application packages.

[0129] As shown in FIG2 , the application package may include desktop manager, file management, calendar, conference, settings, music, WLAN and other applications, which are not listed here one by one and are not limited in this application.

[0130] Among them, the desktop manager can be used to manage and display the icons of applications installed in electronic devices; the file management application can be used to achieve unified management of various files in the operating system, including but not limited to unified management of pictures, audio, documents, videos, compressed packages and other files; the settings application can be used to provide users with operation entrances corresponding to relevant settings.

[0131] In addition, the application package can also include applications such as camera, gallery, Bluetooth, call, map, navigation, music, video, short message, etc.

[0132] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions. In some implementations, these programming interfaces and programming frameworks can be described as functions.

[0133] As shown in Figure 2, the application framework layer may include functions such as the view system, content provider, resource manager / file resource manager, window manager, input manager, card service manager, etc., which are not listed here one by one and this application does not impose any restrictions on this.

[0134] The view system includes visual controls, such as controls for displaying text and images. The view system can be used to build applications. A display interface can consist of one or more views.

[0135] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0136] In actual applications, the resource manager and the file resource manager can be one and the same. Figure 2 takes the resource manager as an example. Specifically, the resource manager is used to provide various resources for the application, such as localized strings, icons, images, layout files, video files, etc.

[0137] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.

[0138] The input manager is used to manage touch events and implement the dispatch of touch events.

[0139] The card service manager is used to manage desktop cards, including but not limited to creating, modifying, and deleting them.

[0140] Android Runtime includes core libraries and a virtual machine. Android Runtime is responsible for scheduling and management of the Android system.

[0141] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0142] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0143] The system library can include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (e.g., OpenGL ES), and a 2D graphics engine (e.g., SGL).

[0144] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0145] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0146] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0147] It is understandable that the 2D graphics engine mentioned above is a drawing engine for 2D drawing.

[0148] In addition, it is understood that the kernel layer in the Android system is the layer between hardware and software. The kernel layer includes at least display drivers, camera drivers, sensor drivers, Wi-Fi drivers, Bluetooth drivers, etc.

[0149] It is understood that the layers in the software structure shown in FIG2 and the components contained in each layer do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer layers than shown, and each layer may include more or fewer components, and this application does not limit this.

[0150] It is understandable that in order to implement the reminder method based on task processing in the embodiment of the present application, the electronic device includes hardware and / or software modules corresponding to the execution of each function. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of this application.

[0151] The following explains the task processing-based reminder method provided in the embodiment of the present application in combination with the file management scenario and the schedule reminder management scenario.

[0152] (1) File management scenario

[0153] Typically, people use various apps to exchange information. For example, they can use chat apps, email apps, and other third-party apps to send documents, audio, video, images, audio, installation packages, and compressed files. In traditional Android systems, the paths used by terminal devices to store received files are complex and obscure, and different apps may not always store the same files.

[0154] For example, if a user needs to find a file named "Document 1" received from a chat app, they need to know the chat app's default file save path on Android. For example, the chat app's default file save path on Android is Android > Data > com.tencent.mm > MicroMsg > Download. At this point, the user can use the terminal device's file management app to perform a multi-level search based on the chat app's default file save path on Android to find the file they need, "Document 1."

[0155] If the user does not understand the default file saving path of the chat APP in the Android system, it will be difficult to find the files he needs, resulting in difficulty in finding files and a poor user experience. Therefore, in order to facilitate finding some required files in the terminal device, users usually store these files according to a customized file saving path. In one embodiment, a directory called "My Files" (which can also be named "My Folders", etc.) is added to the file management APP to allow users to store files received by various third-party APPs according to a customized file saving path. Users can add folders or files under the "My Files" target, and sort, share, upload to cloud disks, delete, and multiple-select files or folders. Among them, file types include but are not limited to pictures, videos, documents, audio, compressed packages, etc. For example, the user can store the file "Document 1" directly in "My Files" and can store the file "Document 1" in any folder under the "My Files" directory.

[0156] In a possible implementation, the user can store the relevant files in "My Files" based on the automatic prompt of the terminal device.

[0157] Take the example of a user using the Chat 1 APP to receive a file. In the interface shown in FIG3a (1), when the other party sends a file named "Document 1", the user clicks the control 101 of the file in the chat interface, and the system automatically downloads the file (or the system starts downloading the file after the user clicks the "Receive File" control corresponding to the file), and displays the download progress identifier 102 shown in FIG3a (2) on the interface to show the download progress of the current document. When the file is downloaded, the interface can also display a reminder message of the download completion and the download path, such as the reminder message "Downloaded: / sdcard / Android / data / XXX / yyy / zzz / Document 1.pdf" shown in FIG3a (2). The reminder message disappears after being displayed for a few seconds. When the file is downloaded, the terminal device automatically displays the preview interface of the file, as shown in FIG3a (3). When the file is opened for the first time, a banner notification 103 as shown in FIG3a (3) will pop up on the preview interface of the file. Among them, the banner notification 103 is used to prompt the user that the file has been saved to the file management APP, and its save path is the default file save path corresponding to the chat 1 APP. Continuing to refer to the banner notification 103, the banner notification 103 may include a "share" control 1031 and a "copy to" control 1032. The user clicks the "share" control 1031 to share the file, and the user clicks the "copy to" control 1032 to copy the file and store it in a custom file directory (such as the "my files" related directory). Optionally, the banner notification 103 can also display one or more of the icon, name, type, source, size, and other information of the received file. If the user does not operate the banner notification 103 at this time, the banner notification 103 will automatically disappear after a period of time. For example, if the banner notification 103 is not operated for 5 seconds, the banner notification 103 will disappear and be collected in the drop-down notification bar (or notification center). The interface directly displays the content of document 1, as shown in (4) in Figure 3a.

[0158] After the banner notification 103 disappears on the preview interface of the file, the user can also find the corresponding banner notification 103 in the notification bar. Continuing to refer to (1) in Figure 3b, on the main interface of the terminal device, the user performs a pull-down operation at the top of the interface to open the notification bar. Among them, the notification bar includes a floating window 104 of the notification message of document 1 that has just been received. When the floating window 104 of the notification message of document 1 is expanded and displayed, the floating window 104 of the notification message of document 1 displays the "Share" control and "Copy to" control as shown in (2) in Figure 3b. At this time, the user can also operate the "Share" control and "Copy to" control in the floating window of the notification message of document 1 respectively, so as to realize the sharing and customized storage of document 1 (such as storing it in the relevant directory of "My Files").

[0159] In the above embodiment, only when the file is opened for the first time will the banner notification corresponding to the file be displayed to guide the user to perform relevant operations (such as "share" or "copy to"), and the banner notification will automatically disappear after being displayed for a few seconds. First of all, the display of the banner notification corresponding to the file will interrupt the user's first viewing experience of the file. The display of the banner notification appears to be rather abrupt, and the user may not be able to complete the relevant considerations and perform relevant operations within the short time that the banner notification is displayed. It is very likely that when the user needs to perform the relevant operations guided by the banner notification, the banner notification has disappeared. When the user opens the file again, the banner notification corresponding to the file will not be displayed again. Although the banner notification will be included in the notification center after it disappears, most users do not know how to find the banner notification corresponding to the file again to perform relevant operations. Therefore, although this embodiment can guide users to share files or perform personalized storage for subsequent management, the user experience is not good.

[0160] In another possible implementation, the user may manually store the received related files in "My Files".

[0161] Continuing with the example of a user using the Chat 1 APP to receive a file, when the file is downloaded, the terminal device automatically displays a preview interface of the file, as shown in FIG4 (1). On the preview interface of Document 1, the user clicks the more options control 201. In response to the user's click operation, the terminal device can display an interface as shown in FIG4 (2), in which a function option window 202 is displayed. In the function option window 202, there may be but not limited to a "forward" option, a "floating window" option, a "select other applications to open" option 2021, a "save to mobile phone" option, and a "cancel" option. When the user clicks the "select other applications to open" option 2021, in response to the user's operation, a "select other applications to open" window 203 is displayed in the terminal device interface, as shown in FIG4 (3). In the "select other applications to open" window 203, various applications that can open Document 1 are displayed, including but not limited to browser applications, file management applications, reading applications, WPS Office applications, etc. At this time, the user selects the file management application option 2031 to open the document 1 through the file management application and store the document 1 in the "My Files" related directory of the file management application. After the user clicks the file management application option 2031 and confirms the selection (such as clicking the "Set Default" or "Only Once" option), the interface of the terminal device jumps to the interface of the file management application. At this time, refer to (4) in Figure 4. As shown in (4) in Figure 4, the user clicks the "My Files" option 204 to select the custom storage path of the document 1 step by step, and after the user clicks the confirmation option 205, the document 1 is saved in the corresponding custom directory.

[0162] This operation for implementing the custom storage of files in the "My Files" related directory requires the user to be fully familiar with the operation steps. Moreover, this implementation method does not have any operation guidance and is not suitable for novice users or users with low operating skills.

[0163] To address the above issues and improve the user experience, the present application provides a task-based reminder method. In this method, for file management scenarios, the terminal device can use a floating ball to prompt the user to store files in the "My Files" directory, facilitating subsequent file management and achieving personalized file storage.

[0164] Figure 5 exemplifies an application scenario. In this application scenario, still taking the example of a user using the Chat 1 APP to receive a file, the user can complete the customized storage of the file according to the guidance of the floating ball corresponding to a certain file.

[0165] In the interface shown in FIG5 (1), when the other party sends a file named "Document 1", the user clicks the control 301 of the file in the chat interface, and the system automatically downloads the file (or the system starts downloading the file after the user clicks the "Receive File" control corresponding to the file), and displays the download progress identifier 302 shown in FIG5 (2) on the interface to show the download progress of the current document. When the file is downloaded, the interface can also display a reminder message of the download completion and the download path, such as the reminder message "Downloaded: / sdcard / Android / data / XXX / yyy / zzz / Document 1.pdf" shown in FIG5 (2), which disappears after being displayed for a few seconds. When the file is downloaded, the terminal device automatically displays the preview interface of the file, as shown in FIG5 (3). Among them, when "Document 1" is opened, a floating ball 303 corresponding to "Document 1" is displayed on the preview interface of "Document 1". The floating ball corresponding to "Document 1" is used to guide the user to perform related operations corresponding to "Document 1", which may include but is not limited to: sharing, custom storage (or save as), printing, etc. As shown in (3) of FIG5 , the initial form of the floating ball 303 corresponding to “Document 1” when displayed is folded, and the area occupied in the interface is small, which will not interrupt the user's viewing experience of the file. Among them, when the floating ball corresponding to the file is in a folded state, the display interface of the floating ball may include but is not limited to the floating ball icon (such as “File Management Reminder Floating Ball”). If the user clicks the floating ball 303 corresponding to “Document 1”, the floating ball corresponding to “Document 1” is deformed into an expanded state, and the floating ball 304 corresponding to “Document 1” shown in (4) of FIG5 can be referred to. Among them, when the floating ball corresponding to the file is in an expanded state, the display interface of the floating ball may include but is not limited to the floating ball icon (such as “File Management Reminder Floating Ball”), the file name associated with the floating ball (such as Document 1.pdf), and various function options. For example, as shown in (4) of FIG5 , the function options displayed on the floating ball may include but are not limited to “Share” option, “Save As” option, “Save to Desktop” option, “Print” option, etc., so as to guide the user to perform the operation corresponding to “Document 1”. Among them, the "Share" option is used by users to share "Document 1", the "Save As" option is used by users to customize the storage of "Document 1", the "Save to Desktop" option is used by users to store "Document 1" in the desktop card of the terminal device, and the "Print" option is used by users to print "Document 1".

[0166] As shown in (3) and (4) in FIG5 , the floating ball 303 and the floating ball 304 corresponding to “Document 1” can be displayed on the right border of the interface, and the floating ball 303 and the floating ball 304 corresponding to “Document 1” can be displayed on the left border of the interface. This embodiment of the application does not limit this. Similarly, the floating ball 303 and the floating ball 304 corresponding to “Document 1” can be displayed in the upper half of the right border of the interface, and the floating ball 303 and the floating ball 304 corresponding to “Document 1” can be displayed in the lower half of the right border of the interface. This embodiment of the application does not limit this either.

[0167] The display state of the floating ball corresponding to a certain file can be switched between a folded state and an expanded state at will.

[0168] In an optional embodiment, as shown in (1) in Figure 6a, when the user clicks on the floating ball 304 in the expanded state, for example, when the user clicks on the icon of the floating ball 304 or the user clicks on the blank space of the floating ball 304, the floating ball 304 in the expanded state is retracted to the folded state, as shown by the floating ball 303 displayed on the interface in (2) in Figure 6a.

[0169] In another optional embodiment, as shown in (1) in FIG6b , when the user clicks on a blank area of ​​the interface, the floating ball 304 in the expanded state retracts to the folded state, as shown by the floating ball 303 displayed on the interface in (2) in FIG6b .

[0170] In another optional embodiment, when the floating ball corresponding to a certain file is in an expanded state, if the user does not operate the expanded floating ball, the expanded floating ball 304 will retract into a folded state after a period of time. For example, if the user does not operate the expanded floating ball 304 for 5 seconds, the expanded floating ball 304 will retract into a folded state.

[0171] In another optional embodiment, when the floating ball corresponding to a certain file is in a folded state, if the user does not operate the folded floating ball, the folded floating ball will be retracted to a hidden state after a period of time, as shown in the floating ball 804 in (2) of FIG15c. For example, if the user does not operate the folded floating ball for 5 seconds, the folded floating ball will be retracted to a hidden state. When the floating ball corresponding to a certain file is in a hidden state, if the user clicks on the hidden floating ball, the terminal device adjusts the shape of the floating ball from a hidden state to a folded state in response to the user's operation.

[0172] For example, the display color of the floating ball in the hidden state is different from the display color of the floating ball in the folded state, for example, the display color of the floating ball in the hidden state is lighter than the display color of the floating ball in the folded state. For another example, the display transparency of the floating ball in the hidden state is different from the display transparency of the floating ball in the folded state, for example, the display transparency of the floating ball in the hidden state is higher than the display transparency of the floating ball in the folded state.

[0173] The floating ball corresponding to a file can be moved up and down at will on the interface of the terminal device. Optionally, when the floating ball is in an expanded state or a collapsed state, the user can long-press and drag the floating ball to move it up and down on the interface.

[0174] For example, as shown in Figure 7, when the user long presses the floating ball 303 and moves it downward, the display position of the floating ball 303 on the terminal device interface moves downward. In this way, when the user is viewing the content of the file, if the user feels that the display position of the floating ball affects their viewing experience, they can adjust the display position of the floating ball by long pressing and dragging.

[0175] When the user closes a file, that is, exits file viewing, the floating ball corresponding to the file is no longer displayed.

[0176] As shown in FIG8a, on the preview page of "Document 1", a floating ball 303 corresponding to "Document 1" is displayed. When the user clicks the return option 305 to exit the file view, the preview page of "Document 1" is closed and the floating ball 303 corresponding to "Document 1" is no longer displayed.

[0177] As shown in FIG8b, on the preview page of "Document 1", a floating ball 304 corresponding to "Document 1" is displayed. When the user clicks the return option 305 to exit the file view, the preview page of "Document 1" is closed and the floating ball 304 corresponding to "Document 1" is no longer displayed.

[0178] After the preview page of "Document 1" is closed, the terminal device continues to display the interface of the Chat 1 app. If the user clicks the "Document 1" control again in the Chat 1 app interface to reopen "Document 1" for viewing, the floating ball corresponding to "Document 1" will still be displayed in the preview interface of "Document 1" to guide the user's operation.

[0179] In this way, regardless of whether the floating ball corresponding to a file is expanded or collapsed, once the user closes the file, the corresponding floating ball will disappear. In other words, the floating ball corresponding to a file will only be displayed on the file preview interface to guide the execution of relevant operations, making it easier to manage files later.

[0180] Moreover, since a floating ball corresponding to the file will always be displayed in the file preview interface when the user views the file in the Chat 1 application, the user does not need to complete the relevant considerations and perform the relevant operations in a short period of time. The user only needs to perform the relevant operations according to the guidance of the function options in the floating ball when necessary. In this way, the user will not encounter the problem of not knowing how to perform relevant operations on the file because he cannot find the guidance of the function options.

[0181] Continuing with the scenario shown in FIG5 , after the preview page of “Document 1” is closed, the terminal device continues to display the interface of the Chat 1 APP, as shown in FIG9 (1). In the interface shown in FIG9 (1), when the other party sends a file named “Document 2”, the user clicks the control 401 of the file in the chat interface, and the system automatically downloads the file (or the system starts downloading the file after the user clicks the “Receive File” control corresponding to the file), and displays the download progress identifier 402 shown in FIG9 (2) on the interface to display the download progress of the current document. When the file is downloaded, the interface can also display a reminder message of the download completion and the download path, such as the reminder message “Downloaded: / sdcard / Android / data / XXX / yyy / zzz / Document 2.pdf” shown in FIG9 (2). The reminder message disappears after being displayed for a few seconds. When the file is downloaded, the terminal device automatically displays the preview interface of the file, as shown in FIG9 (3). Among them, when “Document 2” is opened, a floating ball 403 corresponding to “Document 2” is displayed on the preview interface of “Document 2”. The floating ball corresponding to "Document 2" is used to guide the user to perform related operations corresponding to "Document 2", which may include but are not limited to: sharing, custom storage (or save as), printing, etc. As shown in Figure 9 (3), the initial form of the floating ball 403 corresponding to "Document 2" when displayed is a folded state, which occupies a small area in the interface and does not interrupt the user's viewing experience of the file. If the user clicks on the floating ball 403 corresponding to "Document 2", the floating ball corresponding to "Document 2" is deformed into an expanded state, and the floating ball 404 corresponding to "Document 2" shown in Figure 9 (4) can be referred to. In the display interface of the floating ball 404, the icon of the floating ball "File Management Reminder Floating Ball", the file name associated with the floating ball "Document 2.pdf", and various function options (including but not limited to the "Share" option, the "Save as" option, the "Save to Desktop" option, the "Print" option, etc.) can be displayed.

[0182] In this way, the floating balls displayed on the preview screens of different files correspond to different files and are used to guide users to perform related operations on the corresponding files. That is, on the preview screen of the first file, the floating ball corresponding to the first file is displayed to guide users to perform operations related to the first file; on the preview screen of the second file, the floating ball corresponding to the second file is displayed to guide users to perform operations related to the second file.

[0183] The following uses the floating ball corresponding to "Document 1" as an example to explain the possible functional options on the floating ball.

[0184] As shown in (1) of FIG10a, when the floating ball 501 corresponding to "Document 1" is in an expanded state, if the user clicks the "Save As" option 5011 on the floating ball (it can also be the "Copy to" option. The specific form of the option for transferring the file is not limited in this embodiment. The embodiment of this application takes the "Save As" option as an example for explanation), the interface of the terminal device jumps to the interface of the file management application. For example, the interface can jump from (1) of FIG10a to (2) of FIG10a. Among them, the file management application interface shown in (2) of FIG10a includes a "My Files" directory. In the example shown in (2) of FIG10a, the "My Files" directory is in a collapsed state. Continuing to refer to (2) of FIG10a, a prompt box 502 is also popped up in the file management application interface to prompt the user. The prompt box 502 displays the prompt message "Copy 1 item to". When the user sets and / or adjusts the save directory, the prompt message displayed in the prompt box 502 is adjusted accordingly. Exemplarily, when the user clicks the "My Files" option 503, the prompt message displayed in the prompt box 502 is adjusted to "Copy 1 item to my 'My Files'", and the "My Files" directory is expanded, as shown in (3) in Figure 10a. In the example shown in (3) in Figure 10a, it is assumed that there are no other files and folders in the "My Files" directory. Continuing to refer to (3) in Figure 10a, if the user clicks the confirmation option 5021 in the prompt box 502, Document 1 is stored in the root directory of "My Files". At this time, when the user opens the "My Files" directory, the user can view that "Document 1" is stored in the root directory of "My Files", as shown in (4) in Figure 10a.

[0185] The prompt box 502 may also include a cancel option, such as "×", and the user may click the cancel option to cancel the save operation. Optionally, after the user cancels the save operation, the prompt box 502 closes and the terminal interface continues to display the interface of the file management application.

[0186] The file saving process shown in FIG10a is only an example. In fact, the user can also select more levels of directories to save files as needed. It is understandable that other folders and / or other files may exist in the "My Files" directory. If the user wants to save document 1 to a specified folder, for example, to folder 2 in the "My Files" directory, the user can click the icon of folder 2 in the "My Files" directory in the interface shown in FIG10a (2). At this time, the prompt information displayed in the prompt box 502 can be adjusted to "Copy 1 item to 'Folder 2'". In this case, if the user clicks the confirmation option "√" in the prompt box 502, document 1 can be stored in folder 2. Furthermore, when the user opens file 2 in the "My Files" directory, the user can see that "document 1" is stored in the folder 2 directory.

[0187] Similarly, the user can also save "Document 1" to a new file in any directory of "My Files". For related content, please refer to the relevant operations of the file management application, and the embodiments of this application will not be repeated here.

[0188] It's important to note that saving "Document 1" to the "My Files" directory using the Save As option on the floating icon will not affect the storage of "Document 1" in the Chat 1 app's storage path. This means that users can open "Document 1" in both the Chat 1 app and the file management app.

[0189] In this way, the terminal device pulls up the file management application interface through the user operating the Save As option on the floating ball, and stores the relevant files in the customized path, which is convenient for the user to manage files later and improves the user experience.

[0190] As shown in (1) of Figure 10b, when the floating ball 501 corresponding to "Document 1" is in an expanded state, if the user clicks the "Share" option 5012 on the floating ball, a sharing window 504 as shown in (2) of Figure 10b will pop up on the interface. Exemplarily, multiple icons of sharing objects can be displayed in the sharing window 504, which may include icons of other APPs installed on the terminal device, including but not limited to icons of email APPs, chat APPs, browsers, and text messages; it may also include icons of other terminal devices, including but not limited to icons of other mobile phones, icons of other large-screen devices (smart screens), printers, and computers. Users can click to select the object to be shared as needed, and then share the file. The terminal device can share files with other APPs and other devices, making the resource sharing method richer and more diverse.

[0191] For example, assuming that the user needs to share a file via email, when the user clicks the icon of the email APP in the sharing window 504 in the interface shown in (2) of Figure 10b, the interface of the terminal device switches to the interface of sending emails in the email APP. At this time, "Document 1" automatically appears in the attachment bar as an attachment of the email sent this time. Then, the user can enter the information for sending the email on the email sending interface, such as entering the recipient, subject, email body and selecting the importance, and then click the send button to send the email. "Document 1" is then shared as an attachment to the recipient's mailbox. After the user clicks the send button, the interface of the terminal device can also jump from the email sending interface back to the preview interface of "Document 1" and synchronously display the status of the email sending. For example, when the interface of the terminal device just jumps back to the preview interface of "Document 1", the email may be in the process of being sent, and the displayed email sending status may be "Sending email...", indicating that the email has not been sent successfully. When the email is successfully sent, the email sending status prompt disappears and the preview of "Document 1" is directly displayed on the interface. Alternatively, the email sending status prompt switches from "Sending email..." to "Sent" and automatically disappears after a period of display. For example, after displaying "Sent" for three seconds, the email sending status prompt disappears and the preview of "Document 1" is displayed on the interface.

[0192] In this way, the terminal device opens a sharing window by the user's operation of the share option on the floating ball, and shares the file with the target object selected by the user, realizing resource sharing and enriching the terminal's functions. Compared with the process of users actively searching for files and then sharing them, this embodiment directly opens the sharing window by operating the share option on the floating ball, thereby sharing files more conveniently and quickly, improving the efficiency of resource sharing and enhancing the user experience.

[0193] As shown in (1) of FIG10c, when the floating ball corresponding to "Document 1" is in an expanded state, if the user clicks the "Print" option 5013 on the floating ball, a print preview page as shown in (2) of FIG10c will pop up on the interface. If the user confirms that the file is correct, he or she can click the "Print" control to print "Document 1". At this time, under the premise that the terminal device and the printing device are connected, the user can complete the printing operation of "Document 1". Among them, the print preview page shown in (2) of FIG10c is only an illustrative example, and this embodiment does not limit this.

[0194] In this way, the terminal device opens the print preview interface by the user operating the print option on the floating ball and completes the printing operation for the relevant file. Compared with the method of completing the file printing operation based on the sharing window, this embodiment directly opens the print window by operating the print option on the floating ball and completes the file printing from there. The operation is more convenient and efficient, improving the efficiency of file printing and enhancing the user experience.

[0195] As shown in (1) of FIG10d, when the floating ball corresponding to "Document 1" is in an expanded state, if the user clicks the "Save to Desktop" option 5014 on the floating ball, the terminal device saves "Document 1" to the desktop card. At this time, a prompt message "Added to Desktop" 506 may be displayed on the preview interface of "Document 1", as shown in (2) of FIG10d. The prompt message may automatically disappear after being displayed for a period of time, for example, the prompt message automatically disappears after being displayed for 3 seconds. In this way, the user can know whether the operation of adding "Document 1" to the desktop card is successful.

[0196] After the terminal device saves "Document 1" to the desktop card, when the user performs relevant operations to make the terminal device display the desktop, the user can view the picture of "Document 1" in the common file card 507 on the desktop, as shown in (3) in Figure 10d.

[0197] Continuing with FIG10d (3), two files are currently managed in the frequently used file card 507, such as Document 0.pdf and Document 1.pdf. The user can directly view these two files through the two file icons displayed in the frequently used file card 507. When the user clicks the file icon corresponding to "Document 1.pdf", the mobile phone, in response to the user operation, will launch a default or preset APP for users to view PDF format files, and then the APP will access "Document 1.pdf" and display the content in "Document 1.pdf".

[0198] The number of files that can be managed by a frequently used file card can be a system default or set based on user usage habits, and this embodiment does not impose any restrictions on this. When the number of files managed by a frequently used file card reaches a threshold, the user cannot add new files to this frequently used file card. In some implementations, the terminal device can be provided with multiple file management cards, and the user can store the files they need in any file management card according to actual needs.

[0199] In addition, it should be noted that in actual applications, there may be situations where a file management card has not been added to the desktop of the terminal device, or the user wants to add the current file to other file management cards. In order to better meet the user's usage needs, after the user clicks the "Save to Desktop" option on the floating ball, the terminal device may pop up a selection window on the file preview interface in response to the user's operation. Among them, one or more controls may be included in the selection window. These controls include but are not limited to controls for selecting to add the current file to an existing file management card, controls for selecting to create a new file management card, and controls for adding the current file to the newly created file management card, etc. In this way, users can store files in the corresponding file management cards according to their actual needs, so that they can open the files in the corresponding file management cards to view the content.

[0200] It is understood that if the terminal device already has multiple file management cards on its desktop, such as at least two, then the selection window may also provide two controls for selecting to add the current file to an existing file management card, i.e., one specific control for each file management card. In this way, after the user clicks the corresponding control, the terminal device can add the file to the corresponding file management card.

[0201] It should be pointed out that when a user stores a file in a file management card (such as a frequently used file card) based on the Save to Desktop option on the floating ball, it will not trigger the file's save. When a user clicks on the file icon in the desktop card to view a file, the terminal device opens the file stored in the third-party application storage path. Exemplarily, when a user clicks on the "Save to Desktop" option on the floating ball, the terminal device responds to the user's operation, calls the corresponding service, instance, or function / interface, obtains the relevant information of "Document 1" from the third-party application storage path where "Document 1" is located, generates a corresponding file icon, and adds the file icon to the desktop card, while establishing a shortcut between the file icon and the storage path of "Document 1".

[0202] In this way, the terminal device adds the file to the desktop file management card through the user's operation of the Save to Desktop option on the floating ball. Although the file will not be saved separately, when the user wants to view the file content later, the user does not need to open the corresponding third-party application again to find the corresponding file. The user can directly click the file icon in the desktop file management card to view the file content. The operation is more convenient and efficient, which improves the user experience.

[0203] In an optional embodiment, when the floating ball corresponding to a file is in an expanded state, if the user clicks on any function option (such as a share option, a save as option, a save to desktop option, a print option, etc.), the shape of the floating ball does not change and remains in an expanded state.

[0204] In another optional embodiment, when the floating ball corresponding to a file is in an expanded state, if the user clicks on any function option (such as a share option, a save as option, a save to desktop option, a print option, etc.), the shape of the floating ball changes and retracts to a folded state.

[0205] In the above embodiment, the chat application is used as an example to explain the reception of files. The terminal device can also receive files in the email application, or receive files by the user clicking a download link in the browser interface, or receive files in the interface of other APPs. When the terminal device receives the file, the floating ball corresponding to the file can be displayed in the file preview interface. Furthermore, the user can perform related operations on the files received in different APPs according to the function guidance of the floating ball, which facilitates the user to centrally and orderly save and manage the files received by different APPs, facilitates the user to find files from different sources, and improves the user experience.

[0206] After the user uses the Save As function provided by the floating ball to store a file in the "My Files" related directory, the user can open the file management app and click the "My Files" target folder in the file management app interface to find the desired file in the "My Files" related directory. This method stores the file in the directory of the target folder for which the user has customized permissions. Therefore, the desired file can be found in the target folder according to the customized path. The user does not need to master the obscure and complex default path for storing files to achieve file search, making file search more convenient and quick, and improving the user experience.

[0207] It should be pointed out that in the above embodiment, the file type is a PDF file as an example for explanation. The types of the files mentioned above can be documents, pictures, audio, compressed packages, etc., which are not limited in this embodiment. For example, regarding the above-mentioned picture types, their file formats include but are not limited to JPG, PNG, BMP, GIF, RAW, etc.; video types, their file formats include but are not limited to MP4, AVI, MOV, RMVB, MKV, etc.; document types, their file formats include but are not limited to DOC, PPT / PPTX, XLS, TXT, PDF, EPUB, etc.; audio types, their file formats include but are not limited to MP3, WAV, M4A, FLAC, AAC, etc.; compressed packages, their file formats include but are not limited to ZIP, RAR, 7Z, etc.

[0208] (2) Schedule reminder management scenario

[0209] Currently, more and more users are accustomed to setting schedule reminders on their devices. Setting a schedule reminder is like setting an alarm for important schedules, reminding users not to miss these events in their busy work and life. Users can create, modify, and delete schedules in the relevant interface of the calendar application. For example, schedule information includes at least: schedule name, schedule date, schedule start and end times, etc.

[0210] For example, as shown in FIG11 (1), the user clicks on the icon of the calendar application. In response to the user's operation, the terminal device displays the interface of the calendar application, as shown in FIG11 (2). In addition to displaying calendar information, schedule information can also be displayed in the interface of the calendar application. If the user needs to create a new schedule, he can click on the schedule addition control in the calendar application interface after selecting the schedule date, as shown in FIG11 (2). In response to the user clicking on the schedule addition control, the terminal device can display the schedule creation editing interface as shown in FIG11 (3). Continuing to refer to FIG11 (3), when the user creates a new schedule, he needs to add a schedule name, set the start time and end time of the schedule, select the repetition mode and reminder method of the schedule reminder, etc. The schedule creation editing interface shown in FIG11 (3) is only an exemplary demonstration, and the embodiment of the present application does not limit this. After the user completes setting the information related to the new schedule, click the confirmation option, and the terminal device can complete the creation operation of the schedule reminder. Furthermore, when the time reaches a period of time before the schedule start time, or when the time reaches the schedule start time, the terminal device will give the user a corresponding schedule reminder.

[0211] The method of schedule reminder is related to the user's settings and the display status of the terminal device.

[0212] In one possible scenario, the terminal device can provide a schedule reminder in the form of an alarm clock. As shown in (1) in Figure 12, the schedule reminder interface displays the schedule name, schedule start and end time, continue reminder method, and close reminder method. Among them, the continue reminder method can be "Remind in 5 minutes" 601, and the close reminder method can be to slide left or right to close the reminder control. For example, as shown in (1) in Figure 12, in the schedule reminder, the schedule name is "Second Meeting" and the schedule start and end time is 10:25-11:25 in the morning.

[0213] In this scenario, if the user clicks "Remind in 5 minutes," the terminal device will remind the user again five minutes later. If the user slides to close the reminder control, the terminal device will no longer remind the user. Therefore, this schedule reminder method may be a one-time reminder, and the user may still forget the schedule reminder after closing it. This schedule reminder method may also remind the user again after 5 minutes, but the reminder timing may still be inaccurate, causing the user to click the "Remind in 5 minutes" control again to adjust the schedule reminder time.

[0214] In one possible scenario, the terminal device can display notification information corresponding to the schedule reminder in the lock screen interface to remind the user of the schedule. As shown in (2) in Figure 12, a notification message 602 is displayed in the lock screen interface of the terminal device. Among them, the notification message 602 displays the receiving time, schedule name, and schedule start and end time of the notification message. If the user deletes the notification message 602, the user will not be able to view the notification message for the schedule reminder again. Therefore, this schedule reminder method can only be a one-time reminder, and the user may still forget after the notification message is deleted.

[0215] In one possible scenario, the terminal device displays any interface (non-lock screen interface, non-screen off interface), and the schedule reminder can be displayed in the form of a banner notification. As shown in Figure 12 (3), a banner notification 603 is displayed on the main interface of the terminal device. Among them, the banner notification 603 disappears after being displayed for a period of time, for example, disappears after being displayed for 5 seconds. The user can also make the banner notification 603 disappear by swiping up. Before the banner notification 603 disappears, the user can click "Remind in 5 minutes", and the terminal device will remind the user of the schedule again in five minutes.

[0216] In this case, if the user clicks "Remind in 5 minutes", the terminal device will remind the user again in five minutes; if the user does not take any action or swipes up to close the banner notification, the terminal device will no longer remind the user. Therefore, this schedule reminder method may be a one-time reminder, and the user may still forget it after closing the schedule reminder. This schedule reminder method may also remind the user again after 5 minutes, but the reminder timing may still be inaccurate, causing the user to click the "Remind in 5 minutes" control again to adjust the schedule reminder time.

[0217] In one possible scenario, schedule reminder notifications (including banner notifications or notifications on the lock screen) may be included in the Notification Center, where users can find the corresponding schedule reminders. However, if schedule reminders are included in the Notification Center, users will not be aware of them and will need to actively check for them, which may not achieve the desired reminder effect.

[0218] To solve the above problems and improve the user experience, the present application provides a reminder method based on task processing. In this method, for the schedule reminder management scenario, the terminal device can use a floating ball to remind the user of the schedule, guiding the user to perform the corresponding operations of the schedule, making it more convenient for the user to handle the relevant schedule.

[0219] Figure 13a shows an example of an application scenario. As shown in (1) in Figure 13a, the terminal device can make schedule reminders in the form of an alarm clock. In the schedule reminder interface, the schedule name, schedule start and end time, continue reminder mode, and close reminder mode are displayed. Among them, the function options corresponding to the continue reminder mode include the "Remind in 5 minutes" function option and the function option of whether to add a floating ball. The closing reminder mode can be to swipe left or right to close the reminder control. For example, as shown in (1) in Figure 13a, in the schedule reminder, the schedule name is "Second Meeting" and the schedule start and end time is 10:25-11:25 in the morning.

[0220] If the user needs the terminal device to remind the user of the schedule again after 5 minutes, and at the same time hopes to display a floating ball corresponding to the schedule reminder on the interface of the terminal device (non-lock screen interface, non-off screen interface), the user can click the add floating ball option 701 to make the add floating ball option selected, as shown in (2) in Figure 13a. At this time, the user clicks the "Remind in 5 minutes" option 702, and the schedule reminder interface displayed by the terminal device in the form of an alarm clock is closed and will be displayed to the user again after 5 minutes. At the same time, when the user operates the terminal device to display any interface (non-lock screen interface, non-off screen interface), a floating ball corresponding to the schedule reminder is displayed on the interface of the terminal device. Among them, the floating ball is used to remind the user of the schedule. For example, when the user operates the terminal device to display the main interface, a floating ball 703 corresponding to the schedule reminder is displayed on the main interface, as shown in (2) in Figure 13a. For detailed explanation of the floating ball corresponding to the schedule reminder, please refer to the following.

[0221] If the user does not click on the "Add Floating Ball" option 701, leaving it unselected, then when the user clicks on the "Remind in 5 minutes" option 702, the schedule reminder interface displayed on the terminal device in the form of an alarm clock will be closed and will be displayed to the user again after 5 minutes. At the same time, when the user operates the terminal device to display any interface, the floating ball corresponding to the schedule reminder will not be displayed on the terminal device interface.

[0222] Figure 13b shows an application scenario as an example. In this application scenario, the example of using an alarm clock to remind a schedule is still used for explanation. As shown in (1) in Figure 13b, the terminal device can use an alarm clock to remind a schedule. In the schedule reminder interface, the schedule name, schedule start and end time, continue reminder mode, and close reminder mode are displayed. Among them, the function options corresponding to the continue reminder mode include the "Remind in 5 minutes" function option and the function option of adding a floating ball. The closing reminder mode can be to swipe left or right to close the reminder control. For example, as shown in (1) in Figure 13b, in this schedule reminder, the schedule name is "Second Meeting" and the schedule start and end time is 10:25-11:25 in the morning.

[0223] If the user needs the terminal device to remind the user of the schedule again after 5 minutes, the user can click the "Remind in 5 minutes" option; if the user needs to display the floating ball corresponding to the schedule reminder on the terminal device interface as a real-time reminder, the user can click the "Add floating ball" option 704. When the user clicks the "Add floating ball" option 704, in response to the user's operation, the schedule reminder interface displayed by the terminal device in the form of an alarm clock is closed, and will not be displayed to the user again after 5 minutes. At the same time, when the user operates the terminal device to display any interface (non-lock screen interface, non-screen off interface), the floating ball corresponding to the schedule reminder is displayed on the terminal device interface. Among them, the floating ball is used to remind the user of the schedule. For example, when the user operates the terminal device to display the main interface, the main interface displays a floating ball 703 corresponding to the schedule reminder, which can be shown in (2) in Figure 13b. For detailed explanations of the floating ball corresponding to the schedule reminder, please refer to the following.

[0224] If the user clicks the "Remind in 5 minutes" option, the schedule reminder interface displayed in the form of an alarm clock on the terminal device will be closed and will be displayed to the user again in 5 minutes. At the same time, when the user operates the terminal device to display any interface, the floating ball corresponding to the schedule reminder will not be displayed on the terminal device interface.

[0225] FIG13c shows an example of an application scenario, in which a schedule reminder using a lock screen notification is used as an example for explanation. As shown in FIG13c (1), when the terminal device displays the lock screen interface, the terminal device can provide a schedule reminder to the user in the form of a lock screen notification. It should be noted that when the terminal device is in the lock screen state, the user can delete the lock screen notification by setting operations (such as swiping left and clicking the delete option), but cannot operate other options on the notification. After the terminal device is unlocked, the user can operate other options on the notification.

[0226] Among them, on the interface shown in (1) of Figure 13c, the notification 705 corresponding to the schedule reminder is in a folded state. When the user operates the folding option and expands the notification 705, the interface shown in (2) of Figure 13c can be referred to. As shown in (2) of Figure 13c, the schedule name and the schedule start and end time are displayed on the notification 705. For example, as shown in (2) of Figure 13c, in the schedule reminder, the schedule name is "Second Meeting" and the schedule start and end time is 10:25-11:25 am. In addition, the "Remind in 5 minutes" option 7051 and the "Add floating ball" option 7052 are also displayed on the notification 705. When the terminal device is in an unlocked state, as shown in (2) of Figure 13c, the user can operate the "Remind in 5 minutes" option 7051 or the "Add floating ball" option 7052.

[0227] The user clicks the "Remind in 5 minutes" option 7051. In response to the user's operation, the terminal device deletes the notification 705 (ie, no longer displays the notification 705), and then displays the notification to the user again after 5 minutes to remind the user of the schedule.

[0228] In an optional embodiment, if the user clicks on the "Add Floating Ball" option 7052, the terminal device deletes the notification 705 (i.e., no longer displays the notification 705) in response to the user's operation, and displays it to the user again after 5 minutes. At the same time, when the user operates the terminal device to display any interface (non-lock screen interface, non-screen off interface), the floating ball corresponding to the schedule reminder is displayed on the interface of the terminal device. For example, when the user operates the terminal device to display the main interface, a floating ball 703 corresponding to the schedule reminder is displayed on the main interface, as shown in (3) of Figure 13c. For detailed explanations of the floating ball corresponding to the schedule reminder, please see below.

[0229] In this way, the user can make the terminal device remind the user of the schedule in 5 minutes with one operation, and can also make the terminal device display the floating ball corresponding to the schedule reminder to remind the user of the schedule in real time.

[0230] In another optional embodiment, if the user clicks the "Add Floating Ball" option 7052, the terminal device deletes the notification 705 in response to the user's operation (i.e., the notification 705 is no longer displayed). At the same time, when the user operates the terminal device to display any interface (non-lock screen interface, non-screen off interface), the floating ball corresponding to the schedule reminder is displayed on the terminal device's interface. For example, when the user operates the terminal device to display the main interface, the main interface is displayed with a floating ball 703 corresponding to the schedule reminder, as shown in (3) in Figure 13c.

[0231] In this way, when a user is using a terminal device, that is, constantly checking the terminal device interface, if they do not want the terminal device to provide inaccurate reminders at intervals, they can click the "Add Floating Ball" option to have the terminal device only provide schedule reminders via the floating ball on the interface. The terminal device's schedule reminders based on the floating ball will not only not affect the user's other usage experience of the terminal device, but also achieve the effect of providing real-time schedule reminders to the user.

[0232] FIG13d shows an example of an application scenario, in which a schedule reminder using a banner notification is used as an example for explanation. When the terminal device displays any interface (non-lock screen interface, non-screen off interface), the terminal device displays the main interface as an example, as shown in FIG13d (1), and the terminal device can use a banner notification 706 to remind the user of the schedule. The banner notification 706 can automatically disappear after being displayed for a period of time, for example, after being displayed for 5 seconds.

[0233] As shown in (1) in FIG13d , the schedule name and schedule start and end time are displayed on the banner notification 706. For example, as shown in (1) in FIG13d , in the schedule reminder, the schedule name is “Second Meeting” and the schedule start and end time is 10:25-11:25 am. In addition, the banner notification 706 corresponding to the schedule reminder also displays a “Remind in 5 minutes” option 7061 and a “Add floating ball” option 7062. The user can operate the “Remind in 5 minutes” option 7061 or the “Add floating ball” option 7062 on the banner notification 706.

[0234] The user clicks the "Remind in 5 minutes" option 7061. In response to the user's operation, the banner notification 706 is canceled and the banner notification is displayed to the user again after 5 minutes to remind the user of the schedule again.

[0235] In an optional embodiment, if the user clicks on the "Add floating ball" option 7062, the terminal device will respond to the user's operation, cancel the display of the banner notification 706, and display the banner notification to the user again after 5 minutes to remind the user of the schedule again. At the same time, when the user operates the terminal device to display any interface (non-lock screen interface, non-screen off interface), the floating ball corresponding to the schedule reminder is displayed on the interface of the terminal device. For example, when the user operates the terminal device to display the main interface, the main interface is displayed with a floating ball 703 corresponding to the schedule reminder, as shown in (2) in Figure 13d. For detailed explanations of the floating ball corresponding to the schedule reminder, please see below.

[0236] In this way, the user can make the terminal device remind the user of the schedule in 5 minutes with one operation, and can also make the terminal device display the floating ball corresponding to the schedule reminder to remind the user of the schedule in real time.

[0237] In another optional embodiment, if the user clicks the "Add Floating Ball" option 7062, the terminal device cancels the display of the banner notification 706 in response to the user's operation. At the same time, when the user operates the terminal device to display any interface (non-lock screen interface, non-screen off interface), the floating ball corresponding to the schedule reminder is displayed on the terminal device's interface. For example, when the user operates the terminal device to display the main interface, the main interface displays a floating ball 703 corresponding to the schedule reminder, as shown in (2) in Figure 13d.

[0238] In this way, when a user is using a terminal device, that is, constantly checking the terminal device interface, if they do not want the terminal device to provide inaccurate reminders at intervals, they can click the "Add Floating Ball" option to have the terminal device only provide schedule reminders via the floating ball on the interface. The terminal device's schedule reminders based on the floating ball will not only not affect the user's other usage experience of the terminal device, but also achieve the effect of providing real-time schedule reminders to the user.

[0239] Figure 13e shows an example of an application scenario. In this application scenario, the notification corresponding to the schedule reminder is included in the notification center, and the user can also view the schedule reminder in the notification center. As shown in (1) in Figure 13e, a notification message 707 is displayed in the notification center of the terminal device. The schedule name and the schedule start and end time are displayed on the notification message 707. For example, as shown in (1) in Figure 13e, in the schedule reminder, the schedule name is "Second Meeting" and the schedule start and end time is 10:25-11:25 am. In addition, the banner notification 707 corresponding to the schedule reminder also displays a "Remind in 5 minutes" option 7071 and an "Add floating ball" option 7072. The user can operate the "Remind in 5 minutes" option 7071 or the "Add floating ball" option 7072 on the notification message 707.

[0240] The user clicks the "Remind in 5 minutes" option 7071. In response to the user's operation, the notification information 707 in the notification center is canceled and the notification information is displayed to the user again after 5 minutes to remind the user of the schedule again.

[0241] In an optional embodiment, if the user clicks the "Add Floating Ball" option 7072, the terminal device responds to the user's operation, and the notification information 707 in the notification center is canceled. After 5 minutes, the banner notification is displayed to the user to remind the user of the schedule again. At the same time, when the user operates the terminal device to display any interface (non-lock screen interface, non-screen off interface), the floating ball corresponding to the schedule reminder is displayed on the interface of the terminal device. For example, when the user operates the terminal device to display the main interface, the main interface is displayed with a floating ball 703 corresponding to the schedule reminder, as shown in (2) in Figure 13e. For detailed explanations of the floating ball corresponding to the schedule reminder, please see below.

[0242] In this way, the user can make the terminal device remind the user of the schedule in 5 minutes with one operation, and can also make the terminal device display the floating ball corresponding to the schedule reminder to remind the user of the schedule in real time.

[0243] In another optional embodiment, if the user clicks the "Add Floating Ball" option 7072, the terminal device responds to the user's operation and the notification information 707 in the notification center is canceled. At the same time, when the user operates the terminal device to display any interface (non-lock screen interface, non-screen off interface), the floating ball corresponding to the schedule reminder is displayed on the terminal device interface. For example, when the user operates the terminal device to display the main interface, the main interface is displayed with a floating ball 703 corresponding to the schedule reminder, as shown in (2) in Figure 13e.

[0244] In this way, when a user is using a terminal device, that is, constantly checking the terminal device interface, if they do not want the terminal device to provide inaccurate reminders at intervals, they can click the "Add Floating Ball" option to have the terminal device only provide schedule reminders via the floating ball on the interface. The terminal device's schedule reminders based on the floating ball will not only not affect the user's other usage experience of the terminal device, but also achieve the effect of providing real-time schedule reminders to the user.

[0245] The above describes the process of adding a floating ball corresponding to a schedule reminder by combining several possible application scenarios. It should be noted that when the user operates the terminal device to change the terminal device interface, the floating ball corresponding to the schedule reminder will not automatically disappear unless the schedule ends (or the schedule expires).

[0246] The following uses a specific application scenario as an example to explain in detail the floating ball corresponding to the schedule reminder. The same applies to the floating ball corresponding to the schedule reminder in other scenarios, which will not be explained in detail.

[0247] Figure 14 exemplifies an application scenario. A user uses a terminal device to participate in an online conference, and the terminal device displays the online conference interface, which can be referred to as (1) in Figure 14. While the user is participating in the online conference, it is assumed that the terminal device pops up a banner notification 801 to remind the user of the schedule. The schedule reminder corresponding to the banner notification 801 is preset by the user, and is used to remind the user that he needs to attend the second meeting at 10:25-11:25 this morning. In this schedule reminder, the schedule name is "Second Meeting" and the schedule start and end time is 10:25-11:25 in the morning. The banner notification 801 can automatically disappear after being displayed for a period of time, for example, it disappears automatically after being displayed for 5 seconds.

[0248] As shown in (2) of FIG14 , the banner notification 801 displays the schedule name and schedule start and end times. The banner notification 801 also displays a “Remind in 5 minutes” option 8011 and a “Add floating ball” option 8012. The user can operate the “Remind in 5 minutes” option 8011 or the “Add floating ball” option 8012 on the banner notification 801.

[0249] Continuing with reference to FIG14 (2), the user clicks the "Add Floating Ball" option 8012, and the terminal device cancels the display of the banner notification 801 in response to the user's operation. At the same time, the terminal device displays a floating ball 802 corresponding to the schedule reminder on the interface of the terminal device, as shown in FIG14 (3). In this embodiment, the floating ball 802 is used to guide the user to perform operations related to the "Second Meeting" schedule reminder.

[0250] Among them, the user clicking the "Add floating ball" option 8012 can trigger the terminal device to remind the user of the schedule 5 minutes later, or it can not trigger the terminal device to remind the user of the schedule 5 minutes later. This embodiment does not limit this.

[0251] Continuing to refer to FIG14 (3), the initial form of the floating ball 802 corresponding to the "second meeting" schedule reminder is a folded state, which occupies a small area in the interface and will not interrupt the user's experience of using the terminal device. When the floating ball corresponding to the schedule reminder is in a folded state, the display interface of the floating ball may include but is not limited to the floating ball icon (such as the "schedule reminder floating ball"). If the user clicks on the floating ball 802 corresponding to the "second meeting" schedule reminder, the floating ball 802 corresponding to the "second meeting" schedule reminder is deformed into an expanded state, and the floating ball 803 corresponding to the "second meeting" schedule reminder shown in FIG14 (4) can be referred to. When the floating ball corresponding to the schedule reminder is in an expanded state, the display interface of the floating ball may include but is not limited to the floating ball icon (such as the "schedule reminder floating ball"), the schedule name associated with the floating ball (such as the second meeting), and various function options. For example, as shown in (4) in FIG14 , the function options displayed on the floating ball may include but are not limited to a “join meeting” option, a “share” option, a “cancel” option, etc., so as to guide the user to perform the operation corresponding to the “second meeting” schedule reminder. Among them, the “join meeting” option is used to guide the user to join the “second meeting”, the “share” option is used for the user to share the “second meeting” schedule, and the “cancel” option is used for the user to cancel the display of the floating ball corresponding to the “second meeting” schedule reminder.

[0252] As shown in (3) and (4) in FIG14 , the floating balls 802 and 803 corresponding to the “Second Meeting” schedule reminder can be displayed on the right border of the interface, and the floating balls 802 and 803 corresponding to the “Second Meeting” schedule reminder can be displayed on the left border of the interface, and the present embodiment does not limit this. Similarly, the floating balls 802 and 803 corresponding to the “Second Meeting” schedule reminder can be displayed in the upper half of the right border of the interface, and the floating balls 802 and 803 corresponding to the “Second Meeting” schedule reminder can be displayed in the lower half of the right border of the interface, and the present embodiment does not limit this.

[0253] The display state of the floating ball corresponding to a schedule reminder can be switched between a folded state and an expanded state at will.

[0254] In an optional embodiment, as shown in (1) in Figure 15a, when the user clicks on the floating ball 803 in the expanded state, for example, when the user clicks on the icon of the floating ball 803 or the user clicks on the blank space of the floating ball 803, the floating ball 803 in the expanded state is retracted to the folded state, as shown by the floating ball 802 displayed on the interface in (2) in Figure 15a.

[0255] In another optional embodiment, as shown in (1) of FIG15b , when the user clicks on a blank area of ​​the interface, the floating ball 803 in the expanded state retracts to the folded state, as shown by the floating ball 802 displayed on the interface in (2) of FIG15b .

[0256] In another optional embodiment, when the floating ball 803 corresponding to a schedule reminder is in an expanded state, if the user does not operate the expanded floating ball 803, the expanded floating ball 803 will retract into a folded state after a period of time. For example, if the user does not operate the expanded floating ball 803 for 5 seconds, the expanded floating ball 803 will retract into a folded state.

[0257] In another optional embodiment, as shown in (1) of FIG15c , when the floating ball 802 corresponding to a certain schedule reminder is in a folded state, if the user does not operate the folded floating ball 802, the folded floating ball 802 will retract into a hidden state after a period of time, such as the floating ball 804 shown in (2) of FIG15c . For example, if the user does not operate the folded floating ball 802 for 5 seconds, the folded floating ball 802 will retract into a hidden state. Among them, when the floating ball corresponding to a certain schedule reminder is in a hidden state, if the user clicks on the hidden floating ball, then in response to the user's operation, the terminal device adjusts the shape of the floating ball from the hidden state to the folded state.

[0258] For example, the display color of the floating ball in the hidden state is different from the display color of the floating ball in the folded state, for example, the display color of the floating ball in the hidden state is lighter than the display color of the floating ball in the folded state. For another example, the display transparency of the floating ball in the hidden state is different from the display transparency of the floating ball in the folded state, for example, the display transparency of the floating ball in the hidden state is higher than the display transparency of the floating ball in the folded state.

[0259] The floating ball corresponding to a schedule reminder can be moved up and down on the interface of the terminal device. Optionally, when the floating ball is in an expanded or collapsed state, the user can long-press and drag the floating ball to move it up and down on the interface.

[0260] Continuing with the application scenario shown in FIG14 , as shown in FIG16a (1), when the floating ball 803 corresponding to the schedule reminder of the “second meeting” is in an expanded state, if the user clicks the “join meeting” option 8031 ​​on the floating ball 803, then in response to the user’s operation, the terminal device interface jumps to the application interface matching the “second meeting”. Thus, the user can quickly join the online conference corresponding to the “second meeting” in the interface shown in FIG16a (2), thereby improving the user’s experience and achieving the effect of users quickly joining the meeting.

[0261] Since the floating ball corresponding to the "Second Meeting" schedule reminder is always displayed on the terminal interface, users can flexibly choose the time to immediately join the meeting and implement the function options of the floating ball. Therefore, the display of the floating ball corresponding to the "Second Meeting" schedule reminder provides great convenience for users' operations.

[0262] Among them, the conference application interface shown in (2) in Figure 16a is only an exemplary display and is not limited to this embodiment of the present application.

[0263] In an optional embodiment, after the user clicks the "Join Meeting" option 8031, the terminal device's display interface jumps, and the floating ball 803 is simultaneously removed. That is, the user clicking the "Join Meeting" option can trigger the disappearance of the floating ball. Clicking the "Join Meeting" option can be interpreted as the user having already processed the schedule, so the terminal device can remove the floating ball corresponding to the schedule reminder, avoiding unnecessary display of the floating ball.

[0264] Continuing with the application scenario shown in FIG14 , if the user is unable to attend the meeting and needs someone else to attend the meeting on his or her behalf, the schedule can be shared with other users. As shown in FIG16b (1), when the floating ball 803 corresponding to the "Second Meeting" schedule reminder is in an expanded state, if the user clicks the "Share" option 8032 on the floating ball 803, then in response to the user's operation, the terminal device interface jumps to the calendar schedule interface, which can be shown in FIG16b (2). Among them, the schedule information displayed in the interface shown in FIG16b (2) is the schedule corresponding to the floating ball 803 that needs to be reminded to the user.

[0265] Continuing with FIG16b (2), the terminal device interface further displays a schedule sharing window 805, in which multiple sharing methods are displayed. For example, the sharing methods include but are not limited to "share as picture", "share as text", "share as VCS file", etc.

[0266] As shown in (2) of Figure 16b, for example, when the user clicks the "Share as Picture" option 8501 to share with others through pictures, in response to the user's operation, the terminal device can display the interface shown in (3) of Figure 16b. As shown in (3) of Figure 16b, a schedule picture 806 is displayed in the sharing preview interface. At this time, the user can click the share option 807, and in response to the user's operation, the terminal device pops up a sharing window 808. For example, multiple icons of sharing objects can be displayed in the sharing window 808, which may include icons of other APPs installed on the terminal device, including but not limited to the icon of Douyin APP, the icon of Pailitao APP, the icon of Kuaishou APP, the icon of Bluetooth APP, the icon of WLAN Direct APP, the icon of SMS APP, the icon of Mail APP, the icon of Memo APP, etc. Then, the user can click to select the object to be shared as needed, and then share the schedule picture.

[0267] As shown in (1) of FIG. 16c , for example, when the user clicks the “Share as Text” option 8502 to share with others via text, or when the user clicks the “Share as VCS File” option 8053 to share with others via VCS file, in response to the user’s operation, the terminal device may display an interface as shown in (2) of FIG. 16c . As shown in (2) of FIG. 16c , a sharing window 809 pops up in the interface. For example, multiple icons of sharing objects may be displayed in the sharing window 809, which may include icons of other APPs installed on the terminal device, including but not limited to icons of memo APPs, calendar APPs, club APPs, Bluetooth APPs, WLAN direct connection APPs, SMS APPs, email APPs, chat APPs, etc. Furthermore, the user may click to select the object to be shared as needed, and then share the schedule picture.

[0268] It should be noted that the APPs supporting sharing in the above-mentioned sharing window 808 and sharing window 809 may be the same or different, and this embodiment of the present application does not limit this.

[0269] In this way, the terminal device opens a sharing window by the user clicking the share option on the floating ball and shares the schedule with the target recipient selected by the user, thus realizing schedule sharing and enriching the terminal's functionality. Compared with the process of users actively searching for schedules and then sharing them, this embodiment directly opens the sharing window by clicking the share option on the floating ball, thereby sharing schedules more conveniently and quickly, improving resource sharing efficiency and enhancing the user experience.

[0270] In an optional embodiment, after the user clicks the "Share" option 8032, the terminal device's display interface jumps, and the floating ball 803 is simultaneously removed. In other words, the user clicking the "Share" option can trigger the disappearance of the floating ball. The user clicking the "Share" option can be interpreted as the user having processed the schedule, so the terminal device can remove the floating ball corresponding to the schedule reminder to avoid unnecessary floating ball display.

[0271] In another optional embodiment, the user clicking the "Share" option will not trigger the disappearance of the floating ball. For example, after the user clicks the "Share" option 8032, the display interface of the terminal device jumps, and at the same time the floating ball 803 is undisplayed. When the user completes the sharing operation of the schedule and returns to the interface before the schedule is shared, the floating ball 803 continues to be displayed. Among them, although the user clicking the "Share" option can be understood as the user has processed the schedule, the user may still need to continue to attend the meeting, so the terminal device can continue to display the floating ball corresponding to the schedule reminder to provide user convenience.

[0272] Continuing with the application scenario shown in FIG14 , if the user does not need the terminal device to schedule the “second meeting” for himself, the floating ball corresponding to the “second meeting” schedule reminder can be canceled.

[0273] As shown in (1) in Figure 16d, when the floating ball 803 corresponding to the "Second Meeting" schedule reminder is in the expanded state, if the user clicks the "Cancel" option 8033 on the floating ball 803, then in response to the user's operation, the floating ball 803 on the terminal device interface is canceled, as shown in (2) in Figure 16d.

[0274] It should also be noted that if the schedule corresponding to the floating ball expires (or the schedule ends), the terminal device will cancel the display of the floating ball corresponding to the schedule reminder. In other words, the terminal device determines whether the current time has reached the end time of the schedule, and if so, the floating ball corresponding to the schedule reminder will be canceled.

[0275] In this way, the floating ball corresponding to the schedule reminder is displayed at the top of the terminal device interface. Users can choose to immediately process the schedule, share the schedule, or close the schedule reminder according to their actual situation, without affecting the user's current interface task. Among them, the floating ball will not disappear on the terminal device display interface, and can provide real-time reminders when the user is using the terminal device.

[0276] In the above embodiment, the floating ball display corresponding to the meeting schedule reminder is used as an example to explain the explanation. The same is true for other types of schedule reminders, which will not be detailed here. For example, other types of schedules can be entertainment schedules, ticket purchase schedules, etc., and the terminal applications corresponding to different schedules are not necessarily the same.

[0277] In a possible application scenario, a user pre-creates a schedule named "iQiyi New Drama". The user uses a terminal device to participate in an online conference, and the terminal device displays the online conference interface, which can be shown in (1) in Figure 17. While the user is participating in the online conference, it is assumed that the terminal device pops up a banner notification 901 to remind the user of the schedule. Among them, the schedule reminder corresponding to the banner notification 901 is preset by the user, and is used to remind the user to watch iQiyi New Drama at 10:30 this morning. In this schedule reminder, the schedule name is "iQiyi New Drama" and the schedule start time is 10:30 in the morning.

[0278] As shown in (2) of FIG17 , the schedule name and schedule start time are displayed on the banner notification 901. The banner notification 901 also displays a “Remind in 5 minutes” option 9011 and a “Add floating ball” option 9012. The user can operate the “Remind in 5 minutes” option 9011 or the “Add floating ball” option 9012 on the banner notification 901.

[0279] Continuing to refer to (2) in FIG17 , if the user clicks on the “Add Floating Ball” option 9012, the terminal device cancels the display of the banner notification 901 in response to the user’s operation. At the same time, a floating ball 902 corresponding to the schedule reminder is displayed on the interface of the terminal device, as shown in (3) in FIG17 . In this embodiment, the floating ball 902 is used to guide the user to perform operations related to the schedule reminder of “iQIYI New Drama”. Among them, the user clicking on the “Add Floating Ball” option 9012 can trigger the terminal device to remind the user of the schedule 5 minutes later, or it can not trigger the terminal device to remind the user of the schedule 5 minutes later. This embodiment does not limit this.

[0280] Continuing to refer to (3) in FIG17 , the initial form of the floating ball 902 corresponding to the schedule reminder of “iQiyi New Drama” is a folded state. If the user clicks on the floating ball 902 corresponding to the schedule reminder of “iQiyi New Drama”, the floating ball 902 corresponding to the schedule reminder of “iQiyi New Drama” is transformed into an expanded state. The floating ball 903 corresponding to the schedule reminder of “iQiyi New Drama” can be referred to as (4) in FIG17 . For example, as shown in (4) in FIG17 , the function options displayed on the expanded floating ball may include but are not limited to the “Watch Now” option, the “Share” option, the “Cancel” option, etc., so as to guide the user to perform the operation corresponding to the schedule reminder of “iQiyi New Drama”. Among them, the “Watch Now” option is used to guide the user to watch the new drama in the corresponding APP, the “Share” option is used for the user to share the schedule of “iQiyi New Drama”, and the “Cancel” option is used for the user to cancel the display of the floating ball corresponding to the schedule reminder of “iQiyi New Drama”. For example, when the user clicks the "Watch Now" option, the terminal device interface jumps to the corresponding APP interface so that the user can watch the corresponding drama immediately, and the floating ball corresponding to the "iQiyi New Drama" schedule reminder is canceled.

[0281] It should be noted that when a user clicks the "Share" option, the floating ball corresponding to the "iQiyi New Drama" schedule reminder may disappear, or the floating ball corresponding to the "iQiyi New Drama" schedule reminder may not disappear. This embodiment does not limit this.

[0282] In a possible application scenario, a user pre-creates a schedule named "Smart Travel Train Tickets". The user uses a terminal device to participate in an online conference, and the terminal device displays the online conference interface, which can be shown in (1) in Figure 18. While the user is participating in the online conference, it is assumed that the terminal device pops up a banner notification 1001 to remind the user of the schedule. Among them, the schedule reminder corresponding to the banner notification 1001 is preset by the user, and is used to remind the user to buy a train ticket at 10:30 this morning. In this schedule reminder, the schedule name is "Smart Travel Train Tickets" and the schedule start time is 10:30 in the morning.

[0283] As shown in (2) of FIG18 , the schedule name and schedule start time are displayed on the banner notification 1001. The banner notification 1001 also displays a “Remind in 5 minutes” option 10011 and a “Add floating ball” option 10012. The user can operate the “Remind in 5 minutes” option 10011 or the “Add floating ball” option 10012 on the banner notification 1001.

[0284] Continuing with reference to (2) in FIG18 , if the user clicks on the “Add Floating Ball” option 10012, the terminal device cancels the display of the banner notification 1001 in response to the user’s operation. At the same time, a floating ball 1002 corresponding to the schedule reminder is displayed on the interface of the terminal device, as shown in (3) in FIG18 . In this embodiment, the floating ball 1002 is used to guide the user to perform operations related to the “Smart Travel Train Ticket” schedule reminder. Among them, the user clicking on the “Add Floating Ball” option 10012 can trigger the terminal device to remind the user of the schedule 5 minutes later, or it can not trigger the terminal device to remind the user of the schedule 5 minutes later. This embodiment does not limit this.

[0285] Continuing to refer to (3) in FIG18 , the initial form of the floating ball 1002 corresponding to the “Smart Travel Train Ticket” schedule reminder is a folded state. If the user clicks on the floating ball 1002 corresponding to the “Smart Travel Train Ticket” schedule reminder, the floating ball 1002 corresponding to the “Smart Travel Train Ticket” schedule reminder is transformed into an expanded state. The floating ball 1003 corresponding to the “Smart Travel Train Ticket” schedule reminder can be referred to as (4) in FIG18 . For example, as shown in (4) in FIG18 , the function options displayed on the expanded floating ball may include but are not limited to a “Buy Now” option, a “Share” option, a “Cancel” option, etc., so as to guide the user to perform the operation corresponding to the “Smart Travel Train Ticket” schedule reminder. Among them, the “Buy Now” option is used to guide the user to purchase train tickets in the corresponding APP, the “Share” option is used for the user to share the “Smart Travel Train Ticket” schedule, and the “Cancel” option is used for the user to cancel the display of the floating ball corresponding to the “Smart Travel Train Ticket” schedule reminder. For example, when the user clicks the "Buy Now" option, the terminal device interface jumps to the corresponding APP interface so that the user can immediately execute the operation of purchasing train tickets, and at the same time the floating ball corresponding to the "Smart Train Ticket" schedule reminder is cancelled.

[0286] It should be pointed out that when the user clicks the "Share" option, the floating ball corresponding to the "Smart Travel Train Ticket" schedule reminder may disappear, or the floating ball corresponding to the "Smart Travel Train Ticket" schedule reminder may not disappear. This embodiment does not limit this.

[0287] In one possible application scenario, a user pre-creates a schedule named "Taobao Live". The user uses a terminal device to participate in an online conference, and the terminal device displays the online conference interface, which can be shown in (1) in Figure 19. While the user is participating in the online conference, it is assumed that the terminal device pops up a banner notification 1101 to remind the user of the schedule. Among them, the schedule reminder corresponding to the banner notification 1101 is preset by the user and is used to remind the user to watch Taobao Live at 10:30 this morning. In this schedule reminder, the schedule name is "Taobao Live" and the schedule start time is 10:30 am.

[0288] As shown in (2) of FIG19 , the schedule name and schedule start time are displayed on the banner notification 1101. The banner notification 1101 also displays a “Remind in 5 minutes” option 11011 and a “Add floating ball” option 11012. The user can operate the “Remind in 5 minutes” option 11011 or the “Add floating ball” option 11012 on the banner notification 1101.

[0289] Continuing to refer to (2) in FIG19 , if the user clicks on the “Add Floating Ball” option 11012, the terminal device cancels the display of the banner notification 1101 in response to the user’s operation. At the same time, a floating ball 1102 corresponding to the schedule reminder is displayed on the interface of the terminal device, as shown in (3) in FIG19 . In this embodiment, the floating ball 1102 is used to guide the user to perform operations related to the “Taobao Live” schedule reminder. Among them, the user clicking on the “Add Floating Ball” option 11012 can trigger the terminal device to remind the user of the schedule 5 minutes later, or it can not trigger the terminal device to remind the user of the schedule 5 minutes later. This embodiment does not limit this.

[0290] Continuing to refer to FIG19 (3), the initial form of the floating ball 1102 corresponding to the "Taobao Live" schedule reminder is a folded state. If the user clicks on the floating ball 1102 corresponding to the "Taobao Live" schedule reminder, the floating ball 1102 corresponding to the "Taobao Live" schedule reminder is deformed into an expanded state, which can be referred to as the floating ball 1103 corresponding to the "Taobao Live" schedule reminder shown in FIG19 (4). For example, as shown in FIG19 (4), the function options displayed on the expanded floating ball may include but are not limited to the "Watch Now" option, the "Share" option, the "Cancel" option, etc., so as to guide the user to perform the operation corresponding to the "Taobao Live" schedule reminder. Among them, the "Watch Now" option is used to guide the user to watch the live broadcast in the corresponding APP, the "Share" option is used for the user to share the "Taobao Live" schedule, and the "Cancel" option is used for the user to cancel the display of the floating ball corresponding to the "Taobao Live" schedule reminder. For example, when the user clicks on the "Watch Now" option, the terminal device interface jumps to the corresponding APP interface so that the user can watch the corresponding live broadcast immediately, and the floating ball corresponding to the "Taobao Live" schedule reminder is canceled.

[0291] It should be pointed out that when a user clicks the "Share" option, the floating ball corresponding to the "Taobao Live" schedule reminder may disappear, or the floating ball corresponding to the "Taobao Live" schedule reminder may not disappear. This embodiment does not limit this.

[0292] The application scenarios described above are merely exemplary. It is understandable that the floating ball corresponding to the schedule reminder can also be applied to other schedule reminder scenarios, and the embodiments of the present application do not make specific limitations.

[0293] This embodiment also provides a computer storage medium, which stores computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned related method steps to implement the reminder method based on task processing in the above embodiment.

[0294] This embodiment further provides a computer program product. When the computer program product is run on a computer, it enables the computer to execute the above-mentioned related steps to implement the reminder method based on task processing in the above-mentioned embodiment.

[0295] In addition, an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer execution instructions, and when the device is running, the processor can execute the computer execution instructions stored in the memory to enable the chip to execute the task processing-based reminder method in the above-mentioned method embodiments.

[0296] Among them, the electronic devices (such as mobile phones, etc.), computer storage media, computer program products or chips provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0297] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0298] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0299] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A task-based reminder method, characterized in that: include: Displaying a first interface, wherein the first interface includes the received first file; receiving a first operation on the first file; The first operation is used to download the first file; When the first file is downloaded, a second interface is displayed; the second interface includes a preview interface of the first file and a first floating window, and the first floating window includes a first option; In response to a second operation on the first option, storing the first file in a directory of a target folder, where the target folder is a folder with custom permissions and is different from a system folder; displaying a third interface, the third interface being an interface of a file management application, the third interface including the target folder and the system folder; In response to a third operation on the target folder, the first file is displayed under the target file.

2. The method according to claim 1, characterized in that Also includes: In response to a fourth operation on the preview interface of the first file, the preview interface of the first file is closed, and the first floating window is undisplayed.

3. The method according to claim 2, characterized in that After canceling the display of the first floating window, the method further includes: In response to a fifth operation on the first file, a fourth interface is displayed; the fourth interface includes a preview interface of the first file and the first floating window.

4. The method according to claim 1, wherein The first floating window is a first floating ball.

5. The method according to claim 4, characterized in that The initial state of the first suspension ball is a folded state; The method further comprises: In response to a sixth operation on the first floating ball, the shape of the first floating ball is adjusted to an expanded state; wherein, when the first floating ball is in the expanded state, the first option is displayed on the first floating ball.

6. The method according to claim 5, characterized in that Also includes: In response to the seventh operation on the first floating ball, or the eighth operation received, or when no user operation is received within a set time, the shape of the first floating ball is adjusted from the expanded state to the folded state.

7. The method according to any one of claims 1 to 6, characterized in that The first floating window further includes a second option; The method further comprises: In response to the eighth operation on the second option, a fifth interface is displayed; the fifth interface includes a preview interface of the first file and a first sharing window, the first sharing window includes icons of multiple sharing objects, the multiple The icons of the shared objects include the icon of the first object; In response to receiving a ninth operation, the first file is sent to the first object.

8. The method according to any one of claims 1 to 6, characterized in that The first floating window further includes a third option; The method further comprises: In response to a ninth operation on the third option, a sixth interface is displayed; the sixth interface includes a print preview interface and a print option for the first file; In response to a tenth operation on the print option, an instruction to print the first file is sent to a printing device.

9. The method according to any one of claims 1 to 6, characterized in that The first floating window further includes a fourth option; The method further comprises: In response to a tenth operation on the fourth option, a seventh interface is displayed; the seventh interface includes a preview interface of the first file and prompt information, the prompt information is used to indicate that the first file has been saved to the desktop card; In response to the received eleventh operation, displaying a desktop; the desktop including a desktop card, the desktop card including an icon control of the first file; In response to a twelfth operation on the icon control of the first file, a preview interface of the first file is displayed.

10. The method according to any one of claims 1 to 6, characterized in that The first interface is an interface of a third-party application.

11. The method according to any one of claims 1 to 6, characterized in that: Also includes: Displaying an eighth interface; the eighth interface includes a schedule reminder notification, the schedule reminder notification including schedule information and a fifth option; In response to a thirteenth operation on the fifth option, canceling the display of the schedule reminder notification and displaying a second floating window, wherein the second floating window includes the sixth option; In response to the fourteenth operation on the sixth option, a ninth interface is displayed; the ninth interface is used to execute items matching the schedule information.

12. The method according to claim 11, characterized in that Also includes: In response to a fourteenth operation on the sixth option, the second floating window is canceled.

13. The method according to claim 11, characterized in that The second floating window includes a seventh option; The method further comprises: In response to a fifteenth operation on the seventh option, a tenth interface is displayed; the tenth interface includes the schedule information and a second sharing window, the second sharing window includes icons of multiple sharing objects, and the icons of the multiple sharing objects include an icon of a second object; In response to the received sixteenth operation, the schedule information is sent to the second object.

14. The method according to claim 13, characterized in that Also includes: In response to a fifteenth operation on the seventh option, the second floating window is canceled.

15. The method according to claim 13, characterized in that Also includes: In response to a fifteenth operation on the seventh option, canceling display of the second floating window; After the schedule information is sent to the second object, the second floating window continues to be displayed.

16. The method according to claim 11, characterized in that The second floating window includes an eighth option; The method further comprises: In response to a sixteenth operation on the eighth option, the second floating window is canceled.

17. The method according to claim 11, characterized in that The schedule reminder notification includes schedule reminder information displayed in the form of an alarm clock, schedule reminder information displayed in the form of a banner notification, and schedule notification information displayed in the notification center or on the lock screen interface.

18. The method according to claim 11, characterized in that The schedule information includes: Meeting schedule information, entertainment schedule information, and transaction schedule information.

19. The method according to claim 11, wherein The second floating window is a second floating ball; the initial state of the second floating ball is a folded state; The method further comprises: In response to the seventeenth operation on the second suspended ball, the shape of the second suspended ball is adjusted to an expanded state; wherein, when the second suspended ball is in the expanded state, the sixth option is displayed on the first suspended ball.

20. The method according to claim 11, wherein Also includes: In response to the thirteenth operation on the fifth option, the schedule reminder is set to be sent again after N minutes, where N is a positive integer.

21. An electronic device, characterized in that: include: one or more processors; Memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and when the computer programs are executed by the one or more processors, the electronic device performs the task-based reminder method according to any one of claims 1 to 20.

22. A computer-readable storage medium comprising a computer program, characterized in that When the computer program is executed on an electronic device, the electronic device is caused to execute the task-based reminder method according to any one of claims 1 to 20.

Images