CN106572234A - Method and device for establishing to-do list in terminal - Google Patents

Abstract

Provided are a method and a device for creating to-do items on a terminal. The method includes: (A) acquiring from one or more applications the to-do items for creating the to-do items; (B) creating corresponding to-do items based on the acquired to-do items; (C) creating the to-do items Items are stored in the terminal's local storage. By adopting the method and device for creating to-do items in a terminal according to the exemplary embodiments of the present invention, users can quickly create and store to-do items without entering different applications to set up to-do items. In addition, it is also helpful to quickly view the to-do items and set the reminder time for the to-do items, so as to prevent users from forgetting to deal with the to-do items accordingly.

Description

Method and device for creating to-do list at terminal

technical field

The present invention generally relates to the field of portable terminals, and more specifically, relates to a method and device for creating to-do items on a terminal.

Background technique

With the continuous development of electronic communication technology, electronic equipment is becoming more and more popular. Electronic devices can provide users with services through various pre-installed or subsequent applications. In addition to basic call and text message functions, current electronic devices generally have additional functions such as cameras, video playback, Internet access, and to-do reminders.

For the reminder function of to-do items, various applications for setting to-do items (for example, memo, calendar or alarm clock) are generally installed on electronic devices, and users need to enter different applications to manually set to-do items, but the above-mentioned to-do items The process of setting to-do items is cumbersome, and the user also needs to enter different applications to view the set to-do items.

Contents of the invention

Aspects of the present invention are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Therefore, an object of the exemplary embodiments of the present invention is to propose a method and an apparatus capable of creating a to-do item at a terminal.

An aspect of an exemplary embodiment of the present invention provides a method for creating a to-do item at a terminal, the method comprising: (A) acquiring from one or more applications a pending event for creating a to-do item; (B) Create a corresponding to-do item based on the acquired event to be processed; (C) store the created to-do item in a local storage device of the terminal.

Optionally, after step (B), the method may further include: creating a reminder time for the to-do items.

Optionally, the pending event may be a pending event generated natively by the application itself and/or a pending event generated according to the user's operation of setting a predetermined item in the application as a to-do item.

Optionally, step (A) may include: receiving a broadcast message indicating the event to be processed from the one or more applications, wherein the broadcast message may include content of the event to be processed, wherein the step ( B) may include: creating a corresponding to-do item based on the content of the event to be processed.

Optionally, the pending events natively generated by the application itself may include any one of the following items: missed calls, unread messages, unread emails, alarm clocks, memo items, and reminder items.

Optionally, the method may further include: (D) receiving a first operation from the user for setting the predetermined item as a to-do item; (E) in response to the first operation, obtaining a (F) generating a broadcast message including the content of the event to be processed, the content of the event to be processed includes content describing the predetermined item.

Optionally, an icon for viewing the created to-do items may be floatingly displayed on the uppermost layer of the screen.

Optionally, the first operation may include a dragging operation, and the dragging operation may be: dragging the predetermined item to the area where the icon is located, or dragging the icon to the area where the predetermined item is located Area.

Optionally, after step (C), the method may further include: (G) reminding the to-do items when the current time reaches the reminder time of the to-do items.

Optionally, the step of creating a reminder time for the to-do item may include: automatically generating a reminder time for the to-do item, or setting a reminder time for the to-do item based on a user's manual operation.

Optionally, the step of setting a reminder time for the to-do item based on the user's manual operation may include: (H1) receiving a second operation of the user on the created to-do item; (H2) displaying the (H3) receiving the user’s drag operation, the drag operation is: dragging the to-do item to a predetermined position on the displayed time axis; (H4) responding to the The dragging operation sets the reminder time of the to-do item to the time corresponding to the predetermined location.

Optionally, step (H2) may include: in response to the second operation, displaying a time axis for setting reminder time in a predetermined area of the screen.

Optionally, step (H2) may include: in response to the second operation, displaying the to-do items on the first screen of the terminal, and displaying a time axis for setting reminder time on the second screen of the terminal.

Optionally, after step (B), the method may further include: (I) receiving a user's selection operation for selecting the to-do item; (J) in response to the selection operation, running the The application from which the pending events of the to-do items come to present a user interface for processing predetermined items corresponding to the to-do items.

Optionally, the first operation may further include the operation of setting the processing that needs to be performed on the predetermined item in the future, and the content of the event to be processed may also include the processing information, wherein, step (J) may further include: responding to The selection operation is to run the application from which the event to be processed for creating the to-do item comes from, so as to present a user interface for the processing.

Another aspect of the exemplary embodiment of the present invention provides a device for creating a to-do item at a terminal, the device comprising: a pending event acquisition unit, which acquires a pending event for creating a to-do item from one or more applications a to-do item creating unit, which creates a corresponding to-do item based on the acquired event to be processed; a storage unit, which stores the created to-do item in a local storage device of the terminal.

Optionally, the device may further include: a reminder time creation unit, which creates a reminder time for the to-do items.

Optionally, the pending event may be a pending event generated natively by the application itself and/or a pending event generated according to the user's operation of setting a predetermined item in the application as a to-do item.

Optionally, the to-be-processed event acquisition unit may receive a broadcast message indicating the to-be-processed event from the one or more applications, wherein the broadcast message may include the content of the to-do event; the to-do item creation unit A corresponding to-do item may be created based on the content of the pending event.

Optionally, the pending events natively generated by the application itself may include any one of the following items: missed calls, unread messages, unread emails, alarm clocks, memo items, and reminder items.

Optionally, the to-be-processed event acquiring unit may further include: a first receiving unit, configured to receive a first user operation for setting the predetermined item as a to-do item; a content acquiring unit, in response to the first operation, acquiring the Describe the content of the predetermined item; the message generation unit generates a broadcast message including the content of the event to be processed, and the content of the event to be processed includes the content used to describe the predetermined item.

Optionally, the device may further include: a floating display unit, floating and displaying an icon for viewing the created to-do items on the top layer of the screen.

Optionally, the first operation may include a dragging operation, and the dragging operation may be: dragging the predetermined item to the area where the icon is located, or dragging the icon to the area where the predetermined item is located Area.

Optionally, the device may further include: a to-do item reminder unit, configured to remind the to-do item when the current time reaches the reminder time of the to-do item.

Optionally, the reminder time creation unit may automatically generate a reminder time for the to-do item, or set a reminder time for the to-do item based on a manual operation of the user.

Optionally, the reminder time creating unit may include: a second receiving unit, receiving a second operation of the user on the created to-do list; a display unit, responding to the second operation to display a time axis for setting the reminder time; a third receiving unit The unit receives a user's drag operation, and the drag operation is: drag the to-do item to a predetermined position on the displayed time axis; the reminder time setting unit responds to the drag operation and drags the to-do item The reminder time of the to-do item is set as the time corresponding to the predetermined location.

Optionally, the display unit may display a time axis for setting reminder time in a predetermined area of the screen in response to the second operation.

Optionally, in response to the second operation, the display unit may display the to-do items on the first screen of the terminal, and display a time axis for setting reminder time on the second screen of the terminal.

Optionally, the device may further include: a fourth receiving unit, configured to receive a user's selection operation for selecting the to-do item; an application running unit, responsive to the selection operation, to run the The application from which the pending event of the to-do list is presented to present a user interface for processing a predetermined item corresponding to the to-do list.

Optionally, the first operation may further include the operation of setting the processing that needs to be performed on the predetermined item in the future, and the content of the event to be processed may further include the processing information, wherein, when the fourth receiving unit receives the user's When the selection operation of the to-do item is selected, the application running unit may, in response to the selection operation, run the application from which the event to be processed for creating the to-do item comes from, so as to present a user interface for the processing .

Using the method and device for creating to-do items at the terminal according to the exemplary embodiments of the present invention, the user can quickly create and store to-do items, and No need to go into separate apps to set up to-dos. In addition, it is also helpful to quickly view the to-do items and set the reminder time for the to-do items, so as to prevent users from forgetting to deal with the to-do items accordingly.

Description of drawings

The above and other objects, features and advantages of exemplary embodiments of the present invention will become more apparent through the following detailed description in conjunction with the accompanying drawings, wherein:

FIG. 1 shows a flowchart of a method for creating a to-do item at a terminal according to an exemplary embodiment of the present invention;

Fig. 2 shows a flow chart of the steps of receiving the broadcast message from the one or more applications according to a user operation according to an exemplary embodiment of the present invention;

FIG. 3 and FIG. 4 respectively show schematic diagrams in which the first operation is a selection operation according to an exemplary embodiment of the present invention;

FIG. 5 shows a schematic diagram of floating and displaying the icon on the screen of the terminal in a transparent state;

Fig. 6 shows a schematic diagram in which the first operation is a drag operation according to an exemplary embodiment of the present invention;

Fig. 7 shows a schematic diagram of creating a to-do item according to an exemplary embodiment of the present invention;

Fig. 8 shows a flow chart of the steps of an example of processing a created to-do item according to an exemplary embodiment of the present invention;

Fig. 9 shows a flow chart of the steps of another example of processing a created to-do item according to an exemplary embodiment of the present invention;

FIG. 10 and FIG. 11 respectively show schematic diagrams of prompt information displayed on a screen of a terminal according to an exemplary embodiment of the present invention;

FIG. 12 shows a flow chart of the steps of setting the reminder time of the to-do item based on the user's manual operation according to an exemplary embodiment of the present invention;

Fig. 13 shows a schematic diagram of manually setting a reminder time for a to-do item according to an exemplary embodiment of the present invention;

Fig. 14 shows a schematic diagram of obtaining the read permission of an application in a terminal according to an exemplary embodiment of the present invention;

FIG. 15 shows a block diagram of a device for creating a to-do item at a terminal according to an exemplary embodiment of the present invention;

FIG. 16 shows a structural diagram of the event-to-be-processed acquisition unit 10 in FIG. 15 according to an exemplary embodiment of the present invention.

detailed description

Exemplary embodiments of the invention will now be described in detail to explain the invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to like parts throughout.

FIG. 1 shows a flow chart of a method for creating a to-do item at a terminal (hereinafter referred to as a method for creating a to-do item) according to an exemplary embodiment of the present invention. Here, as an example, the mobile terminal may be a terminal capable of creating to-do items, such as a smart phone, a tablet computer, a personal digital assistant, and a digital multimedia player.

Referring to FIG. 1 , in step S10 , obtain pending events for creating to-do items from one or more applications.

Optionally, a broadcast message indicating the pending event may be received from the one or more applications. Here, the broadcast message may contain the content of the event to be processed.

As an example, the content of the event to be processed may include content describing the event to be processed, and the content used to describe the event to be processed may refer to an Information that serves as an identifier for the content. For example, the content used to describe the pending event may include at least one of the following items: information indicating the application from which the pending event comes, information contained in the pending event itself (for example, the content), the generation time of the event to be processed, information about the originator corresponding to the event to be processed (for example, the phone number of the originator of the call or message, the email address of the sender of the email), information about the originator of the event to be processed Remarks for the event.

In the first embodiment of step S10, the pending event may be a pending event natively generated by the application itself. As an example, pending events natively generated by the application itself may include any of the following items: missed calls, unread messages, unread emails, alarm clocks, memo items, reminder items (for example, reminder items created in the calendar ).

In this case, take the missed call as an example of the pending event natively generated by the application itself. At this time, the content used to describe the missed call may include at least one of the following items: indicating the source of the missed call The information of the application, the generation time of the missed call, the caller number of the missed call, and the remark information about the missed call.

Preferably, step S10 may further include: screening all pending events natively generated by the one or more applications, and filtering out pending events that can be used to create to-do items from all generated pending events, to Create a backlog with filtered pending events. In this way, users can be effectively prevented from being troubled by too many created to-do items.

Specifically, the step of screening all pending events natively generated by the one or more applications may include: obtaining the content of the pending events included in the broadcast message; to identify pending events for creating todos. At this time, the content of the event to be processed includes information contained in the event to be processed itself. For example, when the event to be processed is an unread message, an unread email, a memo item, or a reminder item, the information contained in itself may refer to the content stored in the message, email, memo item, or reminder item. When the event to be processed is a missed call, the information contained in it may refer to the number of ringing times of the missed call. When the event to be processed is an alarm clock, the information contained in it may refer to the information noted in the label of the alarm clock.

In this case, the step of identifying a pending event for creating a to-do item based on the acquired content of the pending event may include: detecting content satisfying a predetermined condition from the acquired content of the pending event, And the pending event corresponding to the content satisfying the predetermined condition is used as the pending event for creating the to-do item.

In one example, the predetermined condition may include not having a predetermined keyword. For example, when the pending event natively generated by the application itself is an unread message, the content of the pending event contained in the broadcast message includes the content of the unread message. At this time, it can be detected whether the content of the unread message contains The predetermined keywords (for example, winning prizes, invoices, promotions), if the content of the unread message contains the above keywords, it is considered that the unread message is an advertisement push message, and it is generally considered that it is not necessary to create an advertisement for this type of unread message. Todo, that is, identifying the unread message as a pending event that cannot be used to create a todo. If the content of the unread message does not contain the above keywords, it is considered that the unread message may be useful to the user. At this time, the unread message can be identified as a pending event that can be used to create a to-do item.

In another example, the predetermined condition may further include that the number of ringing times of missed calls reaches a predetermined number. Incoming calls that reach the predetermined number of times may be nuisance calls, so it is not necessary to create a to-do item for the missed call, that is, the missed call is identified as a pending event that cannot be used to create a to-do item. If the number of rings of the missed call reaches a predetermined number of times, it is considered that the missed call may be a useful call for the user. At this time, the missed call can be identified as a pending event that can be used to create a to-do item.

In the second embodiment of step S10, the pending event may be a pending event generated according to the user's operation of setting a predetermined item in the application as a to-do item. As an example, the predetermined item may include any one of the following items: received calls, read messages, read emails, and images captured within a predetermined time. Preferably, the user's operation will not change the state of the predetermined item in the application, for example, setting the predetermined item in the application as a to-do item according to the user's operation will not change the read message to an unread message.

In this case, a broadcast message indicating the event to be processed may be received from the one or more applications according to the user's operation of setting a predetermined item in the application as a to-do item. The step of receiving the broadcast message from the one or more applications according to the user's operation of setting a predetermined item in the application as a to-do item will be described in detail below with reference to FIG. 2 .

Fig. 2 shows a flow chart of the steps of receiving the broadcast message from the one or more applications according to a user operation according to an exemplary embodiment of the present invention.

As shown in FIG. 2 , in step S101 , a first user operation for setting the predetermined item as a to-do item is received.

In the first embodiment of step S101, the first operation may be a selection operation. In this case, before step S101, the method for creating a to-do list according to an exemplary embodiment of the present invention may further include: displaying the option of setting pending events while displaying the predetermined items on the screen of the terminal, at this time, the first An operation may be a selection operation of the Set pending events option.

The process of setting the predetermined item as a pending event through the option of setting pending events displayed on the screen of the terminal will be described below with reference to FIGS. 3 and 4 .

FIG. 3 and FIG. 4 respectively show schematic diagrams in which the first operation is a selection operation according to an exemplary embodiment of the present invention.

As shown in FIG. 3 , while displaying the predetermined item (for example, a read message) on the screen of the terminal, an option for setting pending events (selection box as shown in FIG. 3 ) is also displayed. When setting the selection operation (for example, click operation) of the event option to be processed, it indicates that the predetermined item will be set as a to-do item (as shown in FIG. 4 ).

In the second embodiment of step S101, the first operation may be a drag operation. In this case, the method for creating a to-do item according to an exemplary embodiment of the present invention may further include: presenting an entry for viewing the created to-do item in the form of an icon on the screen. Preferably, an icon for viewing the created to-do list can be floatingly displayed on the top layer of the screen. For example, the icon can be floatingly displayed at any position on the screen in a transparent state. FIG. 5 shows a schematic diagram of floating and displaying the icon on the screen of the terminal in a transparent state. In this case, the dragging operation may be: drag the predetermined item to the area where the icon is located, or drag the icon to the area where the predetermined item is located, and continue to hold down the icon so that the icon stays in the area where the predetermined item is located for a predetermined time.

The process of setting the predetermined item as an event to be processed by dragging an icon will be described below with reference to FIG. 6 .

Fig. 6 shows a schematic diagram in which the first operation is a drag operation according to an exemplary embodiment of the present invention.

As shown in Figure 6, the predetermined item (for example, read message) is displayed on the screen of the terminal, and an icon for viewing the created to-do item is displayed floatingly on the top layer of the screen, if the In the dragging operation of dragging the icon to the area where the scheduled item is located, and continue to press the icon to make the icon stay in the area where the scheduled item is located for a predetermined time, at this time, it indicates that the follow-up will Set the scheduled item as a to-do item.

In step S102, in response to the first operation, content used to describe the predetermined item is acquired.

In the case where the first operation of step S101 is a first embodiment of a selection operation, content for describing the predetermined item may be acquired in response to the selection operation.

Similarly, in the case of the second embodiment in which the first operation in step S101 is a drag operation, content for describing the predetermined item may be acquired in response to the drag operation.

As an example, the content used to describe the predetermined item may include at least one of the following items: information indicating the application from which the predetermined item comes, information contained in the predetermined item itself (for example, the content of the read message ), information about the originator corresponding to the predetermined item (for example, the phone number of the originator of the incoming call or message, the email address of the sender of the email), and information about the processing that needs to be performed on the predetermined item in the future.

In the first embodiment of step S102, only the information contained in the predetermined item itself may be obtained. In this case, a to-do item may be created and subsequent operations may be performed based only on the acquired information contained in the predetermined item itself. It should be understood that at this time other information other than the above-mentioned information that needs to be processed on the predetermined item in the future may also be acquired according to needs.

In the second embodiment of step S102, the information contained in the scheduled item itself and the information that needs to be processed on the scheduled item in the future can be obtained. In this case, a to-do item may be created and subsequent operations may be performed based only on the acquired information contained in the scheduled item itself and the information that needs to be processed on the scheduled item in the future. It should be understood that the present invention is not limited thereto, and the above information other than the information contained in the predetermined item itself and the information that needs to be processed on the predetermined item in the future can also be obtained according to needs.

For example, when the predetermined item is a read email, the information contained in the predetermined item itself may refer to the content of the read email, and the processing method that needs to be performed on the predetermined item in the future may be any of the following items: Reply to the email, forward the message, view the email again, store the email, and retrieve relevant information (eg, URLs) contained in the email. Correspondingly, the processed information may indicate a determined processing method that needs to be performed on the predetermined item in the future.

When the predetermined item is a received call, the information contained in the predetermined item itself may refer to the content of the received call (for example, the phone number of the originator of the incoming call), and the processing method for the predetermined item in the future It can be any of the following items: replying the incoming call, saving the phone number of the originator of the incoming call, forwarding the phone number of the originator of the incoming call.

In step S103, a broadcast message including the content of the event to be processed is generated, and the content of the event to be processed includes content for describing the predetermined item.

Returning to Figure 1, in the third embodiment of step S10, pending events can also be pending events generated natively by the application itself and pending events generated according to the user's operation of setting a predetermined item in the application as a to-do item .

In step S20, a corresponding to-do item is created based on the acquired event to be processed.

In the case of the first embodiment of the above step S10 in which the application itself natively generates the event to be processed, the content of the event to be processed contained in the broadcast message can be obtained, and the corresponding event can be created according to the content of the event to be processed to-do list. Here, the content of the to-do item includes the content of the event to be processed.

The process of creating a to-do item will be described below with reference to FIG. 7 by taking the event to be processed as a missed call as an example.

Fig. 7 shows a schematic diagram of creating a to-do item according to an exemplary embodiment of the present invention.

In the first embodiment shown in FIG. 7 , it is assumed that the event to be processed is a missed call, if the content of the missed call includes information indicating the application (for example, a call application) from which the missed call Generation time, caller number of the missed call, and remark information about the missed call, based on the content of the above missed call, a message containing the generation time of the missed call, the caller number of the missed call, and the message of the missed call will be created accordingly. Icon and the to-do item about the remark information content of the missed call, as an example, can present this to-do item on the terminal interface (in the form of list) as shown in Figure 7, and present this item to-do item at the same time The content contained in the task.

Specifically, the method for creating a to-do item according to an exemplary embodiment of the present invention may further include: after receiving the selection operation of the user's to-do item, running the Apply to process the todo.

The steps of an example of processing the created to-do item will be described in detail below with reference to FIG. 8 .

Fig. 8 shows a flowchart of an example of steps for processing created to-do items according to an exemplary embodiment of the present invention.

Referring to FIG. 8, in step S201, a user's selection operation for selecting a to-do item is received. As an example, the selection operation may include a click operation.

In step S202, in response to the selection operation, run the application from which the to-do event for creating the to-do item comes from, so as to present a user interface for processing a predetermined item corresponding to the to-do item. Specifically, in response to the selection operation, determine the application from which the event to be processed comes from according to the information contained in the content of the to-do item indicating the application from which the event to be processed comes from, and then run the the application to present a user interface of the application.

In the first embodiment in which the event to be processed shown in FIG. 7 is a missed call, at this time, if a selection operation (for example, a click operation) for selecting the missed call to-do item by the user is received, then Run the application (that is, the call application) from which the missed call is indicated by the information indicating the application from which the missed call is from running on the terminal, so as to present the user interface of the application from which the missed call comes from on the screen of the terminal, For example, a user interface of a call application is presented on the terminal.

In the case of the second embodiment in which the event to be processed is generated according to the user operation in step S10 above, the content of the event to be processed contained in the broadcast message can be obtained, and a corresponding event can be created according to the content of the event to be processed to-do list. Here, the content of the to-do item includes the content of the event to be processed.

In the first embodiment of step S102 of acquiring only the information contained in the scheduled item itself, a to-do item may be created based only on the acquired information contained in the scheduled item itself. In this case, if a user's selection operation for selecting the to-do item is received, in response to the selection operation, according to the application contained in the content of the to-do item indicating that the predetermined item comes from The information determines the application from which the predetermined item comes, and then runs the application from which the predetermined item comes to present a user interface of the application.

For example, referring to FIG. 7, in the second embodiment shown in FIG. 7, it is assumed that the predetermined item is a read message (for example, the read message shown in FIG. 6), if the content of the pending event Including information indicating the application (for example, SMS application) from which the read message comes and information contained in the read message itself (for example, the content of the read message), then correspondingly create a to-do item containing the content of the read message , as an example, the to-do item may be presented on the interface of the terminal (in the form of a list) as shown in FIG. 7 , and the content contained in the to-do item may be presented at the same time. At this time, if a user's selection operation (for example, a click operation) for selecting a to-do item is received, the application from which the read message is indicated by the information indicating the application from which the read message comes will be run on the terminal ( That is, the default SMS application) to present the user interface of the default SMS application on the screen of the terminal.

In step S102, in the second embodiment of obtaining the information contained in the scheduled item itself and the information that needs to be processed on the scheduled item in the future, the acquired information contained in the scheduled item itself and the information that needs to be processed in the future can be processed Create a to-do list with information describing the processing to be performed on a scheduled item.

Optionally, the content of the event to be processed may further include the type of the scheduled item, specifically, the type of the scheduled item contained in the broadcast message and the information of the scheduled item itself may be obtained, and according to Based on the acquired type of the scheduled item, the user’s operation determines the way to process the scheduled item in the future, and then generates information including the information contained in the scheduled item itself and the determined processing method that needs to be performed on the scheduled item in the future way to do.

As an example, the type of the scheduled item may refer to the type of the application from which the scheduled item comes. Here, it should be understood that the method for creating a to-do item according to an exemplary embodiment of the present invention may further include: presetting the scheduled item The corresponding relationship between the type of application the item comes from and the way to process the scheduled item in the future, and then according to the user's operation, based on the acquired type of the scheduled item, it is determined that the scheduled item needs to be processed in the future The processing method, and the processing information indicates the determined processing method that needs to be performed on the predetermined item in the future. For example, when the predetermined item is a received call, the type of the predetermined item is a call application type at this time, and the processing method for the received call set in advance for the call application type may include: storing the received call The calling number of the incoming call, the calling number of replying the incoming call, and forwarding the received call.

The steps of another example of processing the created to-do item will be described in detail below with reference to FIG. 9 .

Fig. 9 shows a flow chart of another example of steps for processing created to-do items according to an exemplary embodiment of the present invention.

In this example, the first operation in step S101 may also include the operation of setting the processing that needs to be performed on the predetermined item in the future, and correspondingly, the content of the event to be processed included in the generated broadcast message may also include the processing Information.

Specifically, referring to FIG. 9 , in step S210 , a first operation for setting the processing that needs to be performed on the predetermined item in the future is received from the user.

In step S220, in response to the first operation, content used to describe the predetermined item is acquired. Optionally, the content used to describe the predetermined item may include the information of the predetermined item itself and the type of the predetermined item.

In step S230, a broadcast message including the content of the event to be processed is generated. At this time, the content of the event to be processed may include the information of the predetermined item itself and the processed information.

In step S240, a to-do item is created based on the event to be processed. Here, the content of the to-do list includes the information of the predetermined item itself and the information of the processing.

In step S250, a user's selection operation for selecting the to-do item is received. As an example, the selection operation may be a click operation.

In step S260, in response to the selection operation, run the application from which the event to be processed for creating the to-do item comes from, so as to present a user interface for the processing. Specifically, in response to the selection operation, the application from which the to-be-processed event comes can be determined according to the information of the predetermined item itself and the information of the processing included in the content of the to-do item and the user interface that needs to be processed on the predetermined item in the future, and then run the application from which the event to be processed comes from, so as to present the user interface on the screen of the terminal.

Referring to FIG. 7, in the second embodiment in which the predetermined item shown in FIG. 7 is a read message, if the content of the event to be processed includes the information contained in the read message itself (for example, the content of the read message) and Information about what needs to be done with the read message in the future, as an example, what needs to be done with the read message in the future can be any of the following: reply to the message, forward the message, view the message again, store the message, Extract the relevant information contained in the message (for example, phone number,) and store the extracted relevant information, then a piece of content containing the read message will be created accordingly (for example, the phone number contained in the read message) and The to-do items that need to be processed (for example, store the phone number extracted from the read message) in the future, for example, can be displayed on the interface of the terminal as shown in Figure 7 (in the form of a list) The to-do item is displayed, and the content contained in the to-do item is displayed at the same time.

In the above-mentioned second embodiment in which the event to be processed shown in FIG. 7 is to store relevant information extracted from the read message (for example, the phone number contained in the read message), at this time if the user selects the The selection operation (for example, click operation) of the to-do item will run the application from which the pending event is indicated by the information indicating the application from which the pending event comes from (that is, run the application used to store the read message) on the terminal. application of the included phone number) to present on the screen of the terminal a user interface corresponding to the manner in which it is determined that the predetermined item needs to be processed in the future, for example, presenting a user interface for storing the phone number on the screen of the terminal to process the read message accordingly (for example, store the phone number).

Optionally, in this case, the method for creating a to-do item according to an exemplary embodiment of the present invention may further include: during the process of creating a to-do item, displaying prompt information on the screen, the prompt information is used to remind the user that the current At what stage in the process of creating a todo is the action of setting the fetched pending event as a todo.

The process of displaying prompt information on the screen of the terminal is described below with reference to FIG. 10 and FIG. 11 .

Fig. 10 and Fig. 11 respectively show schematic diagrams of displaying prompt information on a screen of a terminal according to an exemplary embodiment of the present invention.

As shown in Figures 10 and 11, in this example, taking the predetermined item as an example of a read message, as an example, the created to-do items can be presented in the form of a reminder list, and when the user operates the After the predetermined item is set as a to-do item, a prompt message may be displayed on the screen to remind the user that the predetermined item is being set as a to-do item (for example, the predetermined item is being added to the reminder list). After success, a prompt message indicating that the scheduled item has been set as a to-do item (for example, the scheduled item has been added to the reminder list) is displayed on the screen.

Returning to Fig. 1, in step S30, the created to-do list is stored in the local storage device of the terminal.

Optionally, the method for creating a to-do item according to an exemplary embodiment of the present invention may further include a step of: creating a reminder time for the to-do item.

In one example, reminder times for to-do items can be automatically generated.

Specifically, as long as there is a to-do item in the local storage device of the terminal, a reminder time can be automatically created for the to-do item. As an example, the reminder time can be automatically created according to default settings or custom settings.

In another example, a reminder time can be set for the to-do item based on the user's manual operation.

The steps of setting the reminder time for the to-do item based on the user's manual operation will be described in detail below with reference to FIG. 12 .

Fig. 12 shows a flow chart of the steps of setting a reminder time of a to-do item based on a user's manual operation according to an exemplary embodiment of the present invention.

As shown in FIG. 12 , in step S401 , a second user operation on the created to-do item is received. As an example, the second operation may include a long press operation.

In step S402, a time axis for setting reminder time is displayed in response to the second operation.

In case the terminal has one screen, a time axis for setting a reminder time may be displayed on a predetermined area of the screen in response to the second operation.

In the case where the terminal has two screens (for example, the terminal includes a first screen and a second screen), the first screen may be a main screen arranged in front of the terminal (i.e., facing the direction of the user), and the second screen may be The side screen on the side of the terminal (for example, the left or right side of the terminal) is set. At this time, in response to the second operation, the to-do item is displayed on the first screen of the terminal, and the to-do item is displayed on the second screen of the terminal. A timeline for setting reminder times.

In step S403, a user's drag operation is received. Here, the dragging operation may be: dragging the to-do item to a predetermined position on the displayed time axis.

In step S404, the reminder time of the to-do item is set as the time corresponding to the predetermined location in response to the dragging operation.

The process of setting the reminder time of the to-do item on the terminal will be described in detail below with reference to FIG. 13 .

Fig. 13 shows a schematic diagram of manually setting a reminder time for a to-do item according to an exemplary embodiment of the present invention.

As shown in FIG. 13 , in this example, the terminal has only one screen, at this time, a time axis for setting reminder time may be displayed in a predetermined area of the screen (for example, the right side of the screen). The time axis shown in FIG. 13 is a 24-hour time axis, and the start time of the time axis is the current time when the user executes the operation of setting the reminder time of the to-do items. Specifically, when receiving the user's second operation (for example, a long press operation) on the created to-do item, the time axis in the above-mentioned form is displayed on the right side of the screen; When the item is dragged to a predetermined position on the displayed time axis (for example, the 12th hour after the current time), in response to the drag operation, the reminder time of the to-do item is set to be the same as the The time corresponding to the predetermined location (that is, set the reminder time of the to-do item to be the 12th hour after the current time).

Optionally, the method for creating a to-do item according to an exemplary embodiment of the present invention may further include: reminding the to-do item when the current time reaches the reminder time of the to-do item.

Optionally, reminding the to-do items includes performing sound reminders and vibration reminders on the to-do items and/or displaying the icons differently. As an example, the differential display of the icon may be any of the following items: changing the display color of the icon, flashing the icon, or displaying the icon between a plurality of predetermined display colors at predetermined time intervals At least one of displaying is performed in a switching manner.

Optionally, the method for creating a to-do item according to an exemplary embodiment of the present invention may further include: receiving a third user operation on the created to-do item; and deleting the to-do item in response to the third operation. As an example, the third operation may include a selection operation and/or a sliding operation for deleting the selected to-do item.

Here, it should be understood that the method for creating a to-do list in an exemplary embodiment of the present invention may be an application installed in a terminal (hereinafter referred to as a to-do list application). As an example, the to-do list according to an exemplary embodiment of the present invention The creation method may further include: setting the read permission of the to-do application to other applications in the terminal except the to-do application. After the to-do application obtains the read permission for an application, it can be obtained from Apps with read permissions get pending events for creating todos.

Referring to FIG. 14 , the process of obtaining the read permission of other applications in the terminal except the to-do application by the to-do application of the present invention is described below.

Fig. 14 shows a schematic diagram of acquiring the read permission of an application in a terminal according to an exemplary embodiment of the present invention.

As shown in FIG. 14 , the screen of the terminal can show the reading permission setting interface of the to-do list application, and other applications in the terminal except the to-do list application are displayed on the reading permission setting interface. The read permission of the selected application is obtained through the selection operation of selecting one or more applications among the other applications.

FIG. 15 shows a block diagram of a device for creating a to-do list at a terminal (hereinafter referred to as a to-do list creation device) according to an exemplary embodiment of the present invention. Here, as an example, the mobile terminal may be a terminal capable of creating to-do items, such as a smart phone, a tablet computer, a personal digital assistant, and a digital multimedia player.

As shown in FIG. 15 , the device for creating to-do items at a terminal according to an exemplary embodiment of the present invention includes a to-do item acquisition unit 10 , a to-do item creation unit 20 and a storage unit 30 .

Specifically, the pending event acquisition unit 10 acquires pending events for creating to-do items from one or more applications. For example, the event to be processed acquiring unit 10 may receive a broadcast message indicating the event to be processed from the one or more applications. Here, the broadcast message may contain the content of the event to be processed.

As an example, the content of the event to be processed may include content describing the event to be processed, and the content used to describe the event to be processed may refer to an Information that serves as an identifier for the content. For example, the content used to describe the pending event may include at least one of the following items: information indicating the application from which the pending event comes, information contained in the pending event itself (for example, the content), the generation time of the event to be processed, information about the originator corresponding to the event to be processed (for example, the phone number of the originator of the call or message, the email address of the sender of the email), information about the originator of the event to be processed Remarks for the event.

In the first embodiment of the pending event acquiring unit 10, the pending event may be a pending event natively generated by the application itself. As an example, pending events natively generated by the application itself may include any of the following items: missed calls, unread messages, unread emails, alarm clocks, memo items, reminder items (for example, reminder items created in the calendar ).

Preferably, the to-be-processed event acquisition unit 10 can also filter all the to-be-processed events natively generated by the one or more applications themselves, and filter out the to-be-processed events that can be used to create to-do items from all the generated to-be-processed events to create a backlog from the filtered pending events. In this way, users can be effectively prevented from being troubled by too many created to-do items.

Specifically, the pending event obtaining unit 10 may obtain the content of the pending event included in the broadcast message, and identify the pending event for creating a to-do item based on the obtained content of the pending event. At this time, the content of the event to be processed includes information contained in the event to be processed itself. For example, the to-be-processed event acquiring unit 10 may detect content satisfying a predetermined condition from the acquired content of the to-do event, and use the to-be-processed event corresponding to the content satisfying the predetermined condition as the event used to create the to-do item. pending events. The predetermined condition may include that there is no predetermined keyword or that the number of ringing times of missed calls reaches a predetermined number of times.

In the second embodiment of the pending event acquiring unit 10, the pending event may be a pending event generated according to an operation of setting a predetermined item in the application as a to-do item by the user. As an example, the predetermined item may include any one of the following items: received calls, read messages, read emails, and images captured within a predetermined time. Preferably, the user's operation will not change the state of the predetermined item in the application, for example, setting the predetermined item in the application as a to-do item according to the user's operation will not change the read message to an unread message.

The process of receiving the broadcast message from the one or more applications according to the user's operation of setting a predetermined item in the application as a to-do item will be described in detail below with reference to FIG. 16 .

FIG. 16 shows a structural diagram of the event-to-be-processed acquisition unit 10 in FIG. 15 according to an exemplary embodiment of the present invention.

As shown in FIG. 16 , the event to be processed acquiring unit 10 may include a first receiving unit 101 , a content acquiring unit 102 and a message generating unit 103 .

Specifically, the first receiving unit 101 receives a user's first operation for setting the predetermined item as a to-do item.

In the first embodiment of the first receiving unit 101, the first operation may be a selection operation. In this case, the display unit may display the option of setting pending events while displaying the predetermined item on the screen of the terminal. At this time, the first operation may be a selection operation of the option of setting pending events.

In the second embodiment of the first receiving unit 101, the first operation may be a drag operation. In this case, the device for creating a to-do item according to an exemplary embodiment of the present invention may further include: a floating display unit that presents an entry for viewing the created to-do item in the form of an icon on the screen. Preferably, the floating display unit can floatingly display icons for viewing the created to-do items on the uppermost layer of the screen. For example, the icon can be floatingly displayed at any position on the screen in a transparent state. In this case, the dragging operation may be: drag the predetermined item to the area where the icon is located, or drag the icon to the area where the predetermined item is located, and continue to hold down the icon so that the icon stays in the area where the predetermined item is located for a predetermined time.

The content acquisition unit 102 acquires content describing the predetermined item in response to the first operation.

In the case of the first embodiment in which the first operation of the first receiving unit 101 is a selection operation, the content acquisition unit 102 may acquire content describing the predetermined item in response to the selection operation.

Similarly, in the case of the second embodiment in which the first operation of the first receiving unit 101 is a drag operation, the content obtaining unit 102 may obtain content describing the predetermined item in response to the drag operation.

As an example, the content used to describe the predetermined item may include at least one of the following items: information indicating the application from which the predetermined item comes, information contained in the predetermined item itself (for example, the content of the read message ), information about the originator corresponding to the predetermined item (for example, the phone number of the originator of the incoming call or message, the email address of the sender of the email), and information about the processing that needs to be performed on the predetermined item in the future.

In the first embodiment of the content obtaining unit 102, the content obtaining unit 102 may only obtain information contained in the predetermined item itself. In this case, a to-do item may be created and subsequent operations may be performed based only on the acquired information contained in the predetermined item itself. It should be understood that, at this time, the content obtaining unit 102 may also obtain the above-mentioned other information as required, except the information that needs to be processed on the predetermined item in the future.

In the second embodiment of the content obtaining unit 102, the content obtaining unit 102 may obtain information contained in the predetermined item itself and information that needs to be processed on the predetermined item in the future. In this case, a to-do item may be created and subsequent operations may be performed based only on the acquired information contained in the scheduled item itself and the information that needs to be processed on the scheduled item in the future. It should be understood that the present invention is not limited thereto, and the content obtaining unit 102 may also obtain the above-mentioned other information as required except the information contained in the predetermined item itself and the information that needs to be processed on the predetermined item in the future.

The message generating unit 103 generates a broadcast message including the content of the event to be processed, and the content of the event to be processed includes content describing the predetermined item.

Returning to FIG. 15 , in the third embodiment of the pending event acquisition unit 10, the pending events can also be the pending events natively generated by the application itself and generated according to the user's operation of setting a predetermined item in the application as a to-do item of pending events.

The to-do item creation unit 20 creates corresponding to-do items based on the acquired events to be processed. For example, the to-do item creating unit 20 may create a corresponding to-do item based on the content of the event to be processed.

Specifically, in the case of the first embodiment in which the application of the above-mentioned pending event acquiring unit 10 natively generates pending events, the pending event creating unit 20 can obtain the content of the pending event included in the broadcast message , and create a corresponding to-do item according to the content of the event to be processed. Here, the content of the to-do item includes the content of the event to be processed.

In this case, the device for creating a to-do item according to an exemplary embodiment of the present invention may further include: a fourth receiving unit and an application running unit.

Specifically, the fourth receiving unit receives a user's selection operation for selecting a to-do item. In response to the selection operation, the application running unit runs the application from which the event to be processed for creating the to-do item comes from, so as to present a user interface for processing a predetermined item corresponding to the to-do item.

Specifically, in response to the selection operation, the application running unit determines the application from which the event to be processed comes from according to the information contained in the content of the to-do item indicating the application from which the event to be processed comes from, Then run the application to present the user interface of the application.

In the case of the above-mentioned second embodiment in which the pending event acquisition unit 10 generates pending events according to user operations, the to-do item creation unit 20 can obtain the content of the pending event contained in the broadcast message, and according to The content of the event to be processed is used to create a corresponding to-do item. Here, the content of the to-do item includes the content of the event to be processed.

In the first embodiment where the content acquiring unit 102 only acquires the information contained in the predetermined item itself, the to-do item creating unit 20 may create the to-do item only based on the acquired information contained in the scheduled item itself.

In this case, if the fourth receiving unit receives a user's selection operation for selecting the to-do item, the application running unit may respond to the selection operation, according to the instruction contained in the content of the to-do item. The information of the application from which the predetermined item comes from determines the application from which the predetermined item comes, and then runs the application from which the predetermined item comes to present the user interface of the application.

In the second embodiment in which the content acquisition unit 102 acquires the information contained in the scheduled item itself and the information that needs to be processed on the scheduled item in the future, the to-do list creation unit 20 may base on the acquired scheduled item itself Create a to-do list containing the information and information that requires future processing on the scheduled item.

Optionally, the content of the event to be processed may further include the type of the scheduled item. Specifically, the to-do item creation unit 20 may obtain the type of the scheduled item and the scheduled item contained in the broadcast message. Its own information, and according to the user's operation, based on the acquired type of the scheduled item, determine the way to process the scheduled item in the future, and then generate a A to-do item that describes how a scheduled item should be processed.

As an example, the type of the predetermined item may refer to the type of the application from which the predetermined item comes. Here, it should be understood that the device for creating a to-do list according to an exemplary embodiment of the present invention may further include: a setting unit, preset The corresponding relationship between the type of the application from which the predetermined item comes and the processing method that needs to be performed on the predetermined item in the future, and then the to-do item creation unit 20 then based on the acquired type of the predetermined item according to the user's operation A future processing method for the predetermined item is determined, and the processing information indicates the determined future processing method for the predetermined item.

In this case, the first operation may further include an operation of setting the processing that needs to be performed on the predetermined item in the future, and correspondingly, the content of the event to be processed included in the generated broadcast message may further include the processing information.

Specifically, when the fourth receiving unit receives a user's selection operation for selecting the to-do item, the application running unit may, in response to the selection operation, run the to-do item for creating the to-do item. from the application to present the user interface for the process.

Specifically, in response to the selection operation, the application running unit may determine the information contained in the event to be processed according to the information of the predetermined item itself and the information of the processing included in the content of the to-do item. Then run the application from which the event to be processed comes from, so as to present the user interface on the screen of the terminal.

In this case, the device for creating a to-do list according to an exemplary embodiment of the present invention may further include: an information prompting unit, which displays prompt information on the screen during the process of creating a to-do list, and the prompt information is used to remind the user that the current At what stage in the process of creating a todo is the action of setting the fetched pending event as a todo.

Since the functions of the to-do item creation unit 20 for creating corresponding to-do items based on the acquired to-do items have been described in detail above with reference to step S20 in FIG. 1 , details are not repeated here.

The storage unit 30 stores the created to-do item in a local storage device of the terminal.

Optionally, the device for creating a to-do item according to an exemplary embodiment of the present invention may further include: a reminder time creation unit, configured to create a reminder time for the to-do item.

In an example, the reminder time creating unit can automatically generate the reminder time of the to-do items.

Specifically, as long as there is a to-do item in the local storage device of the terminal, the reminder time creation unit can automatically create a reminder time for the to-do item. As an example, the reminder time creation unit can automatically set according to default settings or custom settings. Create a reminder time.

In another example, the reminder time creating unit may set a reminder time for the to-do item based on the user's manual operation.

In this case, the reminding time creating unit may include: a second receiving unit, a display unit, a third receiving unit and a reminding time setting unit.

Specifically, the second receiving unit receives the user's second operation on the created to-do item. As an example, the second operation may include a long press operation.

The display unit displays a time axis for setting a reminder time in response to the second operation.

In case the terminal has one screen, the display unit may display a time axis for setting a reminder time on a predetermined area of the screen in response to the second operation.

In the case that the terminal has two screens (for example, the terminal includes a first screen and a second screen), the display unit displays the to-do items on the first screen of the terminal in response to the second operation, and displays the to-do list on the second screen of the terminal. Displays a timeline for setting reminder times.

The third receiving unit receives a user's dragging operation, and the dragging operation is: dragging the to-do item to a predetermined position on the displayed time axis.

The reminder time setting unit sets the reminder time of the to-do item as the time corresponding to the predetermined position in response to the drag operation.

Optionally, the device for creating a to-do item according to an exemplary embodiment of the present invention may further include: a to-do item reminder unit configured to remind the to-do item when the current time reaches the reminder time of the to-do item .

Optionally, reminding the to-do items by the to-do item reminding unit includes providing sound reminders, vibration reminders and/or distinguishing the icons for the to-do items. As an example, the differential display of the icon may be any of the following items: changing the display color of the icon, flashing the icon, or displaying the icon between a plurality of predetermined display colors at predetermined time intervals At least one of displaying is performed in a switching manner.

Optionally, the device for creating a to-do item according to an exemplary embodiment of the present invention may further include: a third receiving unit, configured to receive a third operation performed by the user on the created to-do item; a deleting unit, responsive to the third operation, to delete the Todo delete. As an example, the third operation may include a selection operation and/or a sliding operation for deleting the selected to-do item.

Here, it should be understood that the device for creating a to-do list according to an exemplary embodiment of the present invention may further include: a permission setting unit, which sets the read permission of the to-do list application to other applications in the terminal except the to-do list application, After the to-do list application obtains the read permission for an application, the pending event for creating the to-do list can be obtained from the application that has obtained the read permission.

By adopting the method and device for creating to-do items in a terminal according to the exemplary embodiments of the present invention, users can quickly create and store to-do items without entering different applications to set to-do items.

In addition, by adopting the method and device for creating to-do items in the terminal according to the exemplary embodiments of the present invention, it is also possible to quickly check the to-do items and set a reminder time for the to-do items, so as to prevent the user from forgetting to deal with the to-do items accordingly.

In addition, it should be understood that each unit in the device for creating a to-do item at a terminal according to an exemplary embodiment of the present invention may be implemented as a hardware component. Those skilled in the art may implement each unit, for example, by using a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC) according to the defined processing performed by each unit.

In addition, the method for creating a to-do item at a terminal according to an exemplary embodiment of the present invention can be implemented as computer codes in a computer-readable recording medium. Those skilled in the art can implement the computer code according to the description of the above method. The above method of the present invention is realized when the computer code is executed in a computer.

While the invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those skilled in the art that changes may be made in form and detail without departing from the spirit and scope of the invention as defined by the claims. various changes.

Claims (16)

1. A method for creating a to-do item at a terminal, the method comprising: (A) Obtain pending events for creating to-do items from one or more applications; (B) Create corresponding to-do items based on the acquired pending events; (C) storing the created to-do item in the local storage device of the terminal. 2. The method according to claim 1, after step (B), the method further comprises: creating a reminder time for the to-do items. 3. The method according to claim 1, wherein the pending event is a pending event natively generated by the application itself and/or a pending event generated according to the user's operation of setting a predetermined item in the application as a to-do item event. 4. The method of claim 3, wherein step (A) comprises: receiving a broadcast message indicating the pending event from the one or more applications, wherein the broadcast message includes a pending event Content, Wherein, step (B) includes: creating a corresponding to-do item based on the content of the event to be processed. 5. The method according to claim 3, wherein the pending events natively generated by the application itself include any one of the following items: missed calls, unread messages, unread emails, alarm clocks, memo items, reminder items. 6. The method of claim 3, further comprising: (D) receiving the user's first operation for setting the predetermined item as a to-do item; (E) acquiring content describing the predetermined item in response to the first operation; (F) Generating a broadcast message including content of the event to be processed, wherein the content of the event to be processed includes content describing the predetermined item. 7. The method according to claim 1 or 6, wherein an icon for viewing the created to-do list is floatingly displayed on the uppermost layer of the screen. 8. The method according to claim 7, wherein the first operation comprises a dragging operation, and the dragging operation is: dragging the predetermined item to the area where the icon is located, or dragging the icon Drag to the area where the scheduled item is located. 9. The method according to claim 2, wherein, after step (C), the method further comprises: (G) reminding the to-do items when the current time reaches the reminder time of the to-do items . 10. The method according to claim 2, wherein the step of creating a reminder time for the to-do item comprises: automatically generating a reminder time for the to-do item, or setting a reminder time for the to-do item based on a user's manual operation. 11. The method according to claim 10, wherein the step of setting a reminder time for the to-do item based on a user's manual operation comprises: (H1) receiving the user's second operation on the created to-do item; (H2) displaying a time axis for setting reminder time in response to the second operation; (H3) receiving a user's dragging operation, the dragging operation being: dragging the to-do item to a predetermined position on the displayed time axis; (H4) Setting the reminder time of the to-do item to the time corresponding to the predetermined position in response to the drag operation. 12. The method according to claim 11, wherein step (H2) comprises: in response to the second operation, displaying a time axis for setting reminder time in a predetermined area of the screen. 13. The method according to claim 11, wherein, step (H2) comprises: in response to the second operation, displaying the to-do items on the first screen of the terminal, and displaying the list for setting reminder time on the second screen of the terminal timeline. 14. The method according to claim 6, said method further comprising after step (B): (1) receiving a user's selection operation for selecting the to-do item; (J) In response to the selection operation, execute the application from which the to-do event for creating the to-do item comes from, so as to present a user interface for processing a predetermined item corresponding to the to-do item. 15. The method according to claim 14, wherein the first operation further comprises an operation of setting the processing that needs to be performed on the predetermined item in the future, and the content of the event to be processed further includes the processing information, Wherein, step (J) further includes: in response to the selection operation, running the application from which the event to be processed for creating the to-do item comes from, so as to present a user interface for the processing. 16. A device for creating a to-do item at a terminal, the device comprising: A pending event acquiring unit, which acquires pending events for creating to-do items from one or more applications; The to-do item creation unit creates corresponding to-do items based on the acquired pending events; The storage unit is configured to store the created to-do item in a local storage device of the terminal.