KR101739794B1 - To-do management method based on schedule - Google Patents

Abstract

A method for managing a to-do task based on a schedule is performed in a message server connected to one or more user terminals which are mutually communicated through a messenger. The method for managing a to-do task based on a schedule comprises the steps of: (a) receiving a to-do task, in which a deadline date can be designated from now or from the future, and a to-do item containing a deadline date from the user terminal; (b) on the basis of the to-do item, updating a message thread corresponding to a chat room related to the user, and a to-do item set related to the message thread; and (c) updating a deadline schedule list of to-do tasks, such that the message thread and the to-do item set can access the to-do item, on the basis of the deadline date of the to-do item. One embodiment of the present invention is to provide a method for managing to-do task based on a schedule which sets a specific date as a deadline date and can request doing a to-do task to a specific user. In addition, the method displays deadline dates of each to-do item on a calendar according to the progress of the to-do task, and can classify to-do tasks according to deadline dates.

Description

{TO-DO MANAGEMENT METHOD BASED ON SCHEDULE}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a task management technique, and more particularly, to a schedule-based task management method capable of requesting a specific user to perform tasks based on a deadline.

The Internet instant messenger corresponds to an application for delivering a message including characters or graphics between users, and can be implemented as a chat room participated by a plurality of users. In one embodiment, an Internet messenger may include a mobile messenger performed in a mobile environment (e.g., a mobile phone) and may include, for example, a kakao chat, a line, a wichat, a facebook messenger.

The Internet Messenger can inform the user whether the message of the other party is confirmed and the other party's participation in the chat room in order to support the communication of the user to the other party through the message. As the number of users using the Internet Messenger is rapidly increasing, applications used in a mobile environment are being developed in a wide variety of ways. Of these, a to-do management program is used by many users.

Korean Patent Laid-Open No. 10-2015-0070744 relates to a schedule management system and method using a division factor using a mobile terminal. It divides the types of schedule management according to conditions by using a division factor, It is a technology that makes use of management more systematically. That is, the schedule management system is a schedule management system for managing a schedule according to a person or a task through a mobile device. The schedule management system includes a network management processing means for processing a contact schedule based on an address book based on an address book stored through a mobile device, An alarm setting processing means for setting an alarm in association with the human network management processing means and the task information processing means, an always-on human network management processing means, And an interface connection means including an information processing means and an alarm setting processing means.

Korean Patent Registration No. 10-0663494 relates to a task management method using a mobile communication terminal. It is determined whether a preset time has been reached, and when a predetermined time has been reached, an unfinished task And displays an item of an unfinished task according to the result of the check.

Korean Patent Publication No. 10-2015-0070744 (published on June 25, 2015) Korean Registered Patent No. 10-0663494 (Registered on Dec. 22, 2006)

An embodiment of the present invention is to provide a schedule-based task management method capable of requesting a specific user to set a specific date by setting a deadline.

An embodiment of the present invention is to provide a schedule-based task management method capable of displaying the deadline of each task item on the calendar according to the progress status of tasks and classifying task items by deadline.

An embodiment of the present invention provides a schedule-based task management method capable of sorting a plurality of task items included in a task schedule set in order according to a setting of a user, analyzing a task progress status, do.

An embodiment of the present invention provides a schedule-based task management method capable of adding a corresponding task item to a message thread related to a specific chat room based on users associated with the generated task item.

Among the embodiments, the schedule-based task management method is performed in a message server connected to at least one user terminals communicating with each other via a messenger. The method comprises the steps of: (a) receiving a to-do item that includes a to-do list and a to-do list that can specify a to-do list currently or later from the user terminal; (b) Updating a task item set associated with the thread and the message thread; and (c) updating the task thread and the to-do item set based on the deadline of the task item, Gt;

The method includes the steps of: (d) if the reference unit time is changed, checking whether the progress status of each task item is changed during the reference progress status period, and providing a notification message to at least one of the task creator and the task processor through the messenger Step < / RTI >

The step (a) may include a step of requesting confirmation of the to-do list and setting a progress status of the task item to a first start state for waiting for a response.

The step (c) may include updating a to-do list schedule schedule included in the to-do list schedule list and associated with the to-do creator, to-do list, or to-do item designated by the to-do item. The step (c) may include reflecting a to-do associator for accessing the corresponding to-do item of the to-do item set in the to-do set deadline set.

In one embodiment, the method comprises the steps of providing a to-do item in a to-do item set associated with a to-do associate in the to-do list schedule set if a to-do list schedule set for a particular date in the to-do list schedule list is requested .

The method comprises the steps of, when a task schedule designated by a task creator, a to-do list processor or a to-do referrer is requested, the to-do item in the to-do item set and the to-do item set in the to- And providing the to-do progress information statistically summarizing the progress status of the process step-by-step regarding the included to-do.

Among the embodiments, the schedule-based task management method can be performed in the message server. The method comprises the steps of: (a) generating first and second user nodes including user information about each of the first and second users, wherein the first and second user nodes are associated with a to- With the first and second to-be-done schedule lists for obtaining to-do progress information statistically summarizing the to-be-done deadline schedule set and the to-be-processed status for each of the user's tasks; (b) Creating a chatting node associated with a message thread corresponding to the chatting room as a child node of each of the first and second user nodes each time a chatting room is created by two users; and (c) And generating a to-do item corresponding to the to-do item and associating it with the chatting node whenever an associated to-do is received.

The method may further include: (d) updating to-do progress information of the first and second to-do list schedule lists based on the to-do item.

The method may further include the step of (e) updating the task progress information related to the to-do list schedule list every time the progress status of the task item is changed.

The step (c) may include inserting a to-do correlator capable of accessing an item corresponding to the to-do list schedule set every time a to-do associated with the message thread is received.

In one embodiment, the method further comprises, when the first user leaves the chat room, deleting an association for the chat node at the first user node and the to-do associator from the to-do list schedule set in the first to- The method comprising the steps of:

Among the embodiments, the schedule-based task management method is performed in a user terminal communicating with itself or another user terminal through a message server. The method includes the steps of: (a) receiving a task schedule list from the message server and providing a task schedule interface that visualizes a date associated with a deadline in the task schedule list in a unit time schedule; (b) Providing a to-do list interface including a to-do list item created based on a to-do list schedule set for the specific date when a specific date is selected through a finishing schedule interface; and (c) And if so, providing a to-do processing interface capable of performing (1) changing the progress status by the processing step or (2) entering the chat room with respect to the task to be performed.

In the step (a), the task item related to the to-do list is organized by time classification through the to-do list schedule interface, and the to-do items specified by the to-do creator, to-do list or to- . The step (a) may include selectively providing a to-do item designated as a to-do creator, a to-do listener, or a to-do referrer through the to-do-close schedule interface.

The step (b) may further include the step of providing a to-do list interface for creating a to-do item to be added to a message thread related to a specific chat room by designating the specific date as a due date when a specific date is selected through the to-do list deadline interface .

The step (c) may include the step of, when the to-do creator of the corresponding task corresponds to the user, changing the task content including the due date related to the task to be performed through the task processing interface.

The disclosed technique may have the following effects. It is to be understood, however, that the scope of the disclosed technology is not to be construed as limited thereby, as it is not meant to imply that a particular embodiment should include all of the following effects or only the following effects.

The schedule-based task management method according to an embodiment of the present invention can set a specific date as a deadline and request a task to a specific user.

The schedule-based task management method according to an embodiment of the present invention displays the deadline of each task item on the calendar according to the progress status of the task, and classifies the task item by the deadline.

The schedule-based task management method according to an embodiment of the present invention can arrange a plurality of task items included in the task schedule set in order according to the setting of the user, analyze the task progress status, and provide the analyzed tasks to the user.

The schedule-based task management method according to an embodiment of the present invention can add a corresponding task item to a message thread related to a specific chat room based on users associated with the created task item.

1 is a diagram illustrating a task management system according to an embodiment of the present invention.
2 is a block diagram illustrating the message server of FIG.
3 is a flowchart illustrating a task management process performed by the message server shown in FIG.
FIG. 4 is a diagram illustrating a schedule-based task management method performed by the message server shown in FIG. 1. FIG.
5 is a block diagram illustrating the user terminal of FIG.
6 is a diagram illustrating a request for a request in a messenger's calendar implemented by the user terminal of FIG.
FIG. 7 is a diagram illustrating requesting a specific user to make a request based on a date selected in the calendar implemented by the user terminal in FIG.
FIG. 8 is a diagram illustrating messenger to-do items implemented by the user terminal of FIG.
FIG. 9 is a diagram illustrating a to-do item list associated with a schedule implemented by the user terminal of FIG.
FIG. 10 is a diagram illustrating a chat room of a messenger implemented by a user terminal in FIG.

The description of the present invention is merely an example for structural or functional explanation, and the scope of the present invention should not be construed as being limited by the embodiments described in the text. That is, the embodiments are to be construed as being variously embodied and having various forms, so that the scope of the present invention should be understood to include equivalents capable of realizing technical ideas. Also, the purpose or effect of the present invention should not be construed as limiting the scope of the present invention, since it does not mean that a specific embodiment should include all or only such effect.

Meanwhile, the meaning of the terms described in the present application should be understood as follows.

The terms "first "," second ", and the like are intended to distinguish one element from another, and the scope of the right should not be limited by these terms. For example, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

It is to be understood that when an element is referred to as being "connected" to another element, it may be directly connected to the other element, but there may be other elements in between. On the other hand, when an element is referred to as being "directly connected" to another element, it should be understood that there are no other elements in between. On the other hand, other expressions that describe the relationship between components, such as "between" and "between" or "neighboring to" and "directly adjacent to" should be interpreted as well.

It is to be understood that the singular " include " or "have" are to be construed as including the stated feature, number, step, operation, It is to be understood that the combination is intended to specify that it does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

In each step, the identification code (e.g., a, b, c, etc.) is used for convenience of explanation, the identification code does not describe the order of each step, Unless otherwise stated, it may occur differently from the stated order. That is, each step may occur in the same order as described, may be performed substantially concurrently, or may be performed in reverse order.

The present invention can be embodied as computer-readable code on a computer-readable recording medium, and the computer-readable recording medium includes any type of recording device that stores data that can be read by a computer system . Examples of the computer-readable recording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like, and also implemented in the form of a carrier wave (for example, transmission over the Internet) . In addition, the computer-readable recording medium may be distributed over network-connected computer systems so that computer readable codes can be stored and executed in a distributed manner.

The task expressed in the present invention can be defined as an object to which a task creator (or a task donor) instructs, commands, or asks a task acceptor (task acceptor). For convenience, the present specification may be expressed as an instruction, an instruction, or a request.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs, unless otherwise defined. Commonly used predefined terms should be interpreted to be consistent with the meanings in the context of the related art and can not be interpreted as having ideal or overly formal meaning unless explicitly defined in the present application.

1 is a diagram illustrating a task management system according to an embodiment of the present invention.

Referring to FIG. 1, a task management system 100 includes a message server 110 and a user terminal 120, which may be connected through a network.

The message server 110 may be connected to the user terminal 120 and may manage a message thread grouped with messages transmitted from the at least one user terminal 120. In one embodiment, the message thread may be implemented in a chat room or a chat room of an Internet messenger. In another embodiment, the message thread may be implemented via a posting of an online bulletin board. For example, the message server 110 may manage a plurality of message threads, and each of the message threads may include a plurality of user terminals 120. The message server 110 may manage a plurality of user terminals 120 for each of the message threads.

The user terminal 120 corresponds to a computing device connected to the message server 110, and may be implemented, for example, as a desktop, a notebook, a tablet PC, or a smart phone. In one embodiment, the first user terminal 120a may correspond to a mobile terminal and may be connected to the message server 110 via cellular or Wi-Fi communication. In another embodiment, the second user terminal 120b may correspond to a desktop and may be connected to the message server 110 via the Internet.

2 is a block diagram illustrating the message server of FIG.

2, the message server 110 includes a task item receiving unit 210, a task item set updating unit 220, a deadline schedule list updating unit 230, a change notification providing unit 240, A task progress information providing unit 260, a task item processing unit 270, and a control unit 280. [

The message server 110 may be connected to at least one user terminal 120 to perform a task management method. Here, each of the first to third user terminals 120a, 120b, and 120c may be associated with a to do constructor, to do handler, and to do referer with respect to the first to-do item. Meanwhile, the first to third user terminals 120a, 120b, and 120c may be associated with a to-do referrer, to do constructor, and to-do handler with respect to the second to-do item. That is, each of the plurality of user terminals 120 may correspond to a task generator, a task processor, or a task reference for each of a plurality of task items, and is not limited to one of task generator, task processor and task reference . In one embodiment, the first user terminal 120a is associated with both the to-do generator and to-do handler with respect to the third to-do item so that one user terminal 120 acts as a to-do generator and to- Can be performed. That is, the user terminal 120 can process a task for himself / herself for a specific task item, and can communicate with himself / herself.

The to-do item receiving unit 210 receives a to-do item including a to-do list and a to-do list to which the to-do list can be currently or later designated from the user terminal 120. [ In one embodiment, the to-do item receiving unit 210 may set the initial state to wait for a response by requesting confirmation of the to-do process from the to-be-processed item processing step by step.

When the to-do item is received, the to-do item set update unit 220 updates the to-do item set associated with the message thread and the message thread corresponding to the chat room associated with the corresponding user and the to-do organizer of the created to-do item. The to-do item set updating unit 220 can update a to-do set when a to-do item is created or updated. When the to-do item including the deadline is created, the to-do item set update unit 220 can add the created to-do item to the to-do item set of the chat room associated with the set to-do list processor, You can manage it with other included items. In one embodiment, if the to-do list in the to-do item blocks the user, the to-do item set update unit 220 deletes the to-do item according to the user's selection without adding the to-do item to the to-do item set .

The deadline schedule list updating unit 230 can update the to-do list deadline list of the user so that the message thread and the set of task items can access the corresponding task item based on the deadline of the task item. More specifically, the to-do list schedule list updating unit 230 may classify a to-do item designated by the user as a to-do creator, a to-do list, or a to-do referrer according to the due date, can do.

The to-do-deadline schedule list updating unit 230 can update the to-doze schedule set associated with the deadline date of the to-do item included in the to-do list schedule list and designating the user as a to-do creator, to-do- When the to-do item is designated as a to-do creator, a to-do list, or to-do referrer, the to-be-finishing schedule list updating unit 230 determines a finishing schedule of the to-do item, Items can be added to update the to-do list schedule set.

In one embodiment, the to-do-close schedule list updating unit 230 may reflect the to-do associates for accessing the corresponding to-do items in the to-do item set in the do-not-over schedule set. Here, the task associator corresponds to a pointer that can be accessed by the task item.

When the reference unit time is changed, the change notification unit 240 checks whether the progress status of the to-do item has been changed during the reference progress status period. If the change has not been made, the change notification provider 240 notifies at least one of the to- Can be provided. Here, the step-by-step progress state of the to-do item may include "new", "doing", "done", "confirm", and "unprocessable" in five states in total. The change notification unit 240 may include one of a fixed mode and a variable mode as a reference progress status period. Herein, the fixed method recognizes a case where the progress state is not changed for a predetermined period, and the variable method is a process in which the progress state is changed during a certain period of the entire period based on the date from the day of issuing the task to the deadline It is understood that it is not. For example, when the reference progress status period is set to a fixed mode, the change notification provider 240 maintains the initial start status for 5 days for a specific task item, or maintains the status for 3 days, and if there is no change, A notification message can be provided to at least one of the to-do creator and the to-do-handler. When the reference progress status period is set in a variable manner, the change notification provider 240 determines whether the initial start status is a full start status for a specific to-do item whose creation date is April 12, 2016 and the due date is set to May 12, The notification message may be provided to at least one of the to-do creator and the to-do-handler through the messenger. The change notification unit 240 can receive and set a specific period for each progress state from the user or maintain the predetermined period.

In one embodiment, the change notification providing unit 240 may include at least one of a progress status, a task history, and a deadline as a notification message. For example, the change notification unit 240 may provide one of a progress notification message or a notification message including a to-do list and a due date, or may provide both to at least one of a to-do creator and a to-do listener. For example, a progress step by step notification message may include "A specific favor is on hold for the first time" or "A specific favor is on hold for 1/10 of the first time" You can do this, and the notification message, which includes the task history and the due date, Things to do: Clean up, deadline: April 17, 2016 ".

The to-do item remover 250 can provide a to-do item in a to-do item set associated with a to-do associate when a to-do list schedule set for a particular date in the to-do list schedule list is requested. In one embodiment, the task item supplier 250 may provide task items in order of their respective deadlines.

When a task schedule designated by a task creator, a task processor, or a to-do referrer is requested, the task progress information providing unit 260 displays a task task information item and a task item in the task item set through the to- It is possible to provide the to-do progress information statistically summarizing the progress status of the processing steps pertaining to the tasks included in the set. Here, the step-by-step progress state of the to-do item may include "new", "doing", "done", "confirm", and "unprocessable" in five states in total. &Quot; New " is a newly created task item, which indicates a task item that has not received a response from the task processor. &Quot; In Progress " indicates a state in which the to-do list processor is processing a corresponding item in a state in which a response to the to-do item is received from the to-do list processor. &Quot; Completed " indicates a state in which the to-do-agent completes the to-do item and waits for a response to the task completion from the to-do generator. &Quot; OK " indicates that the to-do creator has confirmed the completed task of the to-do list processor. &Quot; Unprocessable " indicates a state in which a specific friend blocks a user and can not receive a to-do item. &Quot; All " means the total number of to-do items associated with a particular friend, except for the " unprocessable " The task progress information providing unit 260 may receive a selection of at least one task progress state from the user terminal 120 to which the task progress information providing unit 260 belongs. More specifically, the task progress information providing unit 260 may update the progress status of the task item when receiving a response to the task progress status of the task task from the task creator or task task manager.

In one embodiment, task progress information providing 260 may provide a chat room associator for entry of a chat room corresponding to a message thread associated with a specified task to allow the messenger to enter a chat room associated with a specific task via a task task list . More specifically, the to-do progress information providing unit 260 provides the to-do list associator to the to-do list creator and the to-do creator so that the to-do list creator and the to-do creator can enter the chat room for processing the to- And a chat room for conversation.

The to-do item processing unit 270 may include a first user and a second user, and may generate first and second user nodes including user information about each of the first and second users. The to-do item processing unit 270 acquires to-do progress schedule information that is statistically summarized with respect to the to-do item deadline schedule and the to-do item deadline schedule, And may be associated with first and second to-do list schedules. The to-do item processing unit 270 generates a chat room node associated with a message thread corresponding to the chat room as a child node of each of the first and second user nodes each time a chat room participated by the first and second users is created . The to-do item processing unit 270 may generate a to-do item corresponding to a to-do item and associate it with a chat room node each time a to-do associated with the message thread is received. In one embodiment, the to-do item processor 270 may insert a to-do correlator that can access the to-do item whenever the to-do associated with the message thread is received. Here, the task associator may include a pointer to access the task item.

The to-do item processing unit 270 can update the to-do progress information of the first and second to-do list deadline lists based on the to-do item. In one embodiment, the to-do item processing unit 270 may update to-do progress information associated with a to-do list schedule list every time the progress status of the to-do item is changed.

When the first user leaves the chat room, the to-do item processing unit 270 can delete the to-do associates from the affinity relationship for the corresponding chat node and the to-do list deadline set in the first to-do list deadline list at the first user node. In one embodiment, when the first user re-enters the chat room after deletion of the association, the to-do item processing unit 270 adds an association to the chat node to the first user node, To the first user. Here, when the first user is reconnected with the chat room node, the to-do items that the first user has confirmed before leaving are records can be maintained.

The control unit 280 controls the overall operation of the message server 110 and includes a task item receiving unit 210, a task item set updating unit 220, a task deadline schedule list updating unit 230, a change notification providing unit 240, The to-do item providing unit 250, the to-do proceeding providing unit 260, and the to-do item processing unit 270. [

3 is a flowchart illustrating a task management process performed by the message server shown in FIG.

Referring to FIG. 3, the task item receiving unit 210 receives a task item including a task and a due date (step S310). In one embodiment, the to-do item receiving unit 210 may set the initial state to wait for a response by requesting confirmation of the to-do process from the to-be-processed item processing step by step.

When the to-do item is received, the to-do item set update unit 220 updates the to-do item set associated with the corresponding user, the to-do creator of the created to-do item, the to-do- (Step S320). When the to-do item including the deadline is created, the to-do item set update unit 220 can add the created to-do item to the to-do item set of the chat room associated with the set to-do list processor, You can manage it with other included items.

The deadline schedule list updating unit 230 may update the to-do list deadline list of the user so that the message thread and the to-do item set can access the to-do item based on the due date of the to-do item (step S330). More specifically, the to-do list schedule list updating unit 230 may classify a to-do item designated by the user as a to-do creator, a to-do list, or a to-do referrer according to the due date, can do.

When the reference unit time is changed, the change notification unit 240 determines whether the progress status of the to-do item is changed during the reference progress status period (step S340).

If the progress status has not been changed during the reference progress status period, the change notification provider 240 may provide a notification message to at least one of the to-do generator and the to-do-handler through the messenger (step S342).

The to-do item remover 250 can provide a to-do item in a to-do item set associated with a to-do associate when a to-do list schedule set for a particular date in the to-do list schedule list is requested. In one embodiment, the to-do-item providing unit 250 may provide to-do items in the order of their respective registration dates, due dates, to-do list name, or chat room order (step S350).

FIG. 4 is a diagram for explaining a chat-room-based task management method performed by the message server shown in FIG. 1;

4A and 4B, the task-item processing unit 270 is connected to the first user terminal 120a and the second user terminal 120b, and generates first and second user nodes including user information about each of the first and second user nodes 120a and 120b To obtain the task progress information in order to statistically summarize the task progress status by the task progress level regarding the work schedule and the work schedule of the tasks to be performed in relation to the task deadline schedule and the task deadline schedule, You can associate it with the deadline schedule lists.

In one embodiment, the to-do item processing unit 270 may include a to-do list schedule list for each of the first and second user terminals 120a and 120b. 4a and 4b only show the second user terminal 120b only for convenience, but do not limit the to-do list to the second user terminal 120b. The to-do item processing unit 270 displays a to-do list in a to-do list, a date, a deadline schedule associated with each date, a number of at least one to-do items designated as a due date by the corresponding date, And the summary information including the information on the to-do-processer and the progress of the task can be additionally managed.

The to-do item processing unit 270 generates the chat room node associated with the message thread corresponding to the chat room as the respective child nodes of the first and second user nodes whenever the chat rooms participated by the first and second users are created . Here, the chat room node # 11 to the chat room node # 21 correspond to the chat room node associated with the first user terminal 120a and the chat room node # 21 to the chat room node # 28 belong to the chat room node associated with the second user terminal 120b . The to-do item processing unit 250 generates to-do items corresponding to to-do items each time a to-do associated with the message thread is received. The chat room node # 21 may generate a chat item associated with the first user terminal 120a and the second user terminal 120b, and the first user and the second user may generate the to-do items associated with each other in the chat room node # 21. In one embodiment, the to-do item processing unit 270 may add to-do items to the to-do table associated with the chat room node as shown in Fig. 4A. The to-do item processing unit 270 can add and manage a to-do item including a to-do list, a to-do list, a to-do list, a due date, and a current status. In another embodiment, the to-do item processing unit 270 may associate a to-do item as a child node of a chat room node, as shown in Fig. 4B. The to-do item processing unit 270 can manage to-do items by associating the to-do items from the chat room nodes in a tree form.

5 is a block diagram illustrating the user terminal of FIG.

5, the user terminal 120 includes a task finishing interface 510, a task list interface providing unit 520, a task input interface providing unit 530, a task processing interface providing unit 540, An interface updating unit 550, a chat room interface providing unit 560, a task item set updating unit 570, and a control unit 580.

A to-do list interface providing unit 520, a to-do input interface providing unit 530, a to-do processing interface providing unit 540, a to-do interface updating unit 550, and a chat room interface providing unit 550. [ 560 will be described with reference to Figs. 6 to 10 below.

The to-do item set update unit 570 may provide to the message server a to-do creator, a to-do list, and a to-do list for a specific to-do item input via the to-do interface, and update the to-do item set by the message server.

The control unit 580 controls the overall operation of the user terminal 120 and includes a to-do list interface 510, a to-do list interface unit 520, a task input interface unit 530, Control unit 540, the to-do-interface update unit 550, the interface interface providing unit 560, and the to-do item set updating unit 570.

FIG. 6 is a diagram illustrating a to-do list interface providing part and a to-do list interface providing part shown in FIG. 5 to provide a to-do list on the basis of a deadline, FIG. 6 is a block diagram illustrating a messenger FIG. 8 is a diagram illustrating a request for a request in a calendar. FIG.

6, the to-do-close schedule interface providing unit 510 receives a to-do-close schedule list from the message server 110 and displays a to-do schedule finishing schedule interface that visualizes the dates associated with the due dates in the to- Can be provided. The to-do-finishing schedule interface providing unit 510 can provide the received to-do list to the user based on the finishing schedule. Here, the unit-time schedule may include a monthly schedule.

The to-do-close schedule interface providing unit 510 may provide a calendar 610 to confirm the due date of the to-do item associated with the user.

The calendar 610 may display the date set as the deadline of at least one to-do item designated by the user as a to-do creator, a to-do listener, or a to-do referrer in a different color.

In one embodiment, the to-do list scheduling interface providing unit 510 can visually classify to-do items related to the to-do list schedule list and separately provide the to-do items designated by the to-do creator, to-do- . The to-do-close schedule interface providing unit 510 can display the to-do items designated by the user as a to-do list, a to-do referrer, and to-do creator on the calendar 610 in different colors.

The to-do-close schedule interface providing unit 510 can selectively provide a to-do item designated by the to-do creator, to-do-a-do-do, or to-do referrer through the to-do-close schedule interface. According to the user setting, the to-do-close schedule interface providing unit 510 can display only the to-do items designated by the user as the to-do-cope in different colors on the calendar 610.

In another embodiment, the to-do-close schedule interface providing unit 510 may display each of the calendars 610 in different colors according to the progress of the to-do items. For example, when the to-do item is in a new, busy, or pre-confirmation state, the finishing schedule interface providing unit 510 may display the to-do item in black at the to-do item deadline, State, it may be grayed out or not displayed on the item deadline.

The to-do list interface provider 520 may provide a to-do list 620 that includes at least one to-do item whose date is set as the deadline, when the user selects a date displayed in a different color in the calendar 610.

The to-do list 620 may provide at least one to-do item that is placed at the bottom of the calendar 610 and that has a specified date as a due date, with each progress status. In one embodiment, the to-do list interface provider 520 provides the to-do progress status of the to-do items included in the to-do list 620 to the user using the in-progress processing badge 622 and the in- . The progress process badge 622 consists of a total of four pieces per task item, and each circle may correspond to "new", "doing", "done", and "confirmation" respectively from the left. For example, if the progress process badge 622 is painted second from the left, it can be determined that the current progress process is " in progress ". Progress processing period 624 may include a task creation date and to-do-due date of the task item.

7 is a flowchart illustrating a process of generating a to-do item through a to-do list interface, and Fig. 7 is a flowchart illustrating a process of creating a to-do item through a calendar interface implemented by the user terminal shown in Fig. As shown in FIG.

7, when a specific date is selected through the to-do list interface, the to-do list interface unit 530 may designate a specific date as a due date and generate a to-do item that can be added to a message thread related to a specific chat room.

The to-do list interface providing unit 530 may provide a to-do list specifying button 710, a to-do list check box 720, a asking creating box 730, and a to-do list specifying button 740. The to-do list input unit 530 allows the to-do creator to specify a to-do list currently or later through the to-do list specifying button 710, and confirms the specifying of the to-do list through the to-do list check box 720 can do. The task input interface providing unit 530 can input the task details via the asking creation field 730. [ The task input interface providing unit 530 provides a to-do task specifying button 740 so that task task creators can reset the to-do period. In one embodiment, task input interface providing 530 allows a task generator via task input interface to generate a task item that includes a task, a task processor, and a due date.

FIG. 8 is a diagram for explaining that the task processing interface providing unit 540 shown in FIG. 5 provides a task processing interface according to whether or not task items are received, and FIG. 8 is a block diagram of the messenger implemented by the user terminal shown in FIG. To-do item.

8, when the to-do item is selected from the message server 110, the to-do-processing interface providing unit 540 can provide a to-do processing interface capable of changing the progress status of each task, have. In one embodiment, the to-do-processing interface providing unit 540 may include a due date related to a to-do item through a to-do processing interface when the to-do creator of the to-do item corresponds to the user.

The to-do processing interface providing unit 540 includes a task name 810, a task progress status 820, a chat button 830, a favorite add button 840, a task item modification button 850, an OK button 860, , And a receipt confirmation list 870. [

The to-do processing interface providing unit 540 can provide the information of the to-do item through the to-do name 810 and the do-through status 820 and moves to the chat room associated with the to-do item through the chat button 1030 . In one embodiment, the to-do-processing interface providing unit 540 determines whether a to-do item corresponding to a specific task item is associated with a to-do item included in a task set received from the message server 110 Can be visually provided to the chat room. For example, when a user accesses a chat room through a chat button 830 provided in a specific task item window of a messenger to create a message, the task processing interface providing unit 540 provides an association The relationship can be provided visually.

The to-do-processing interface providing unit 540 can arrange the to-do item at the top of the to-do item list in the chat room through the favorite add button 840, The set contents can be modified. In addition, the to-do creator can arbitrarily complete a specific to-do item through the confirmation button 860 of the to-do processing interface providing unit 540.

In one embodiment, the to-do processing interface 540 may provide different buttons to the do-not-constructor and do-it-handler, respectively, in accordance with the to-do progress state 820 of the to-do item. For example, the to-do-processing interface providing unit 540 provides a modify and delete button to the to-do creator when the to-do-proceed status 820 is "new", so that the to-do creator can be modified and deleted And provide a do-not-care button to the to-do-handler so that the to-do-handler can change the status. The to-do-processing interface providing unit 540 provides a correction and confirmation button to the to-do creator so that the to-do can be corrected and the to-do can be confirmed when the in-progress state 820 is " in progress & Button to allow the to-do creator to be notified of completion of the to-do when the to-do-doer completes a specific task. When the to-do-proceeding state providing unit 820 is 'done', the to-do-processing interface providing unit 540 provides the to-do creator with a solution and confirmation button so that the to-do creator checks the completed to- To decide whether to re-complete or to complete.

In one embodiment, the to-do-processing interface providing unit 540 receives a to-be-sent message from the message server 110 to the users included in the chat room, As shown in FIG. For example, the to-do-processing interface provider 540 may output a message " unread " next to the name Kwak Seung-hoon if Kwak Seung-hun does not read the to-do message.

9 is a diagram illustrating a task interface update unit updating the processing step-by-step interface; and FIG. 9 is a diagram illustrating a task item list associated with a schedule implemented by the user terminal in FIG.

9, the task interface update unit 550 provides a to-do list associated with a corresponding user and a schedule through the message server 110, and whenever the to-do listener changes the to-do progress status of the task item, And can update the task interface according to the processing step.

The to-do list interface 550 may provide to-do list sorting criteria 910, to-do list information 920, a to-do list 930, a progress processing badge 932, and a progress processing period 934.

The to-do list interface 550 updates the to-do list based on the to-do list sorting criterion 910 by providing the to-do list by classifying the to-do items specified by the user as to-do creator, to-do list or to- You can provide a to-do list. The to-do list interface update unit 550 may provide a to-do list sorting criterion 910 based on the settings received from the user.

The to-do list interface update unit 550 may set the to-do list sorting criteria 910 in order of registration date or due date in relation to the schedule of to-do items. When the to-do list sorting criteria 910 is set in order of registration date, the to-do list interface update unit 550 can sort the to-do list in order of registration date of each to-do item.

In an embodiment, the to-do list interface 550 may set the to-do list sorting criterion 910 in the order of the to-do list name of the to-do item and the conversation order. When the to-do list sorting criteria 910 is set in order of the to-do list name, the to-do list interface 550 updates the to-do list by arranging the to-do list in the order of name of to-do list of all to-do items associated with the user, When the list sorting criterion (910) is set in the order of the chat rooms, the to-do list can be sorted according to the chat rooms associated with the respective to-do items, or the to-do lists can be sorted by the to- have.

Task list information 920 provides information about the user and the task items associated with the schedule. For example, the to-do list interface 550 may classify a plurality of to-do items according to their to-do progress statuses, and can sort and display a plurality of to-do items by their to-do progress status through the to-do list information 920 have. For example, a to-do item, which is a state before a to-do process is received from a to-do processor, is classified as a " new " item, and a to-do item is classified as a to- When completed, it is classified as "done". Items for which the to-do creator has confirmed completion of the to-do handler are classified as "OK".

The to-do list 930 may sort the to-do items associated with the user according to a predetermined to-do list sorting criterion 910 and provide them with the progress status of each to-do item. In one embodiment, the task interface update unit 550 may provide the task progress status of the task item to the corresponding user using the progress processing button 932 and the progress processing period 934.

The progress process badge 932 consists of a total of four, and each circle may correspond to "new", "doing", "done", and "confirmation" from the left. For example, if the progress process badge 932 is painted second from the left, it can determine that the current progress process is " in progress ".

The progress processing period 934 includes a task item registration date and a task item registration deadline for each task item.

FIG. 10 is a diagram illustrating a chat room interface providing unit in FIG. 5 to provide a chat room interface associated with a specific user, and FIG. 10 is a view illustrating a chat room of a messenger implemented by a user terminal in FIG.

In FIG. 10, the chat room interface provider 560 may provide a chat room associated with a particular user, and may provide a message thread and a to-do item associated with the user and a particular friend, respectively.

The chat room interface providing unit 560 may provide to-do item set information 1010, a chat room 1020, and an exit button 1030. [

The to-do item set information 1010 provides information on a to-do item set associated with the friend. For example, the chat room interface providing unit 560 may classify and provide a plurality of task items according to the task progress status, sort the plurality of task items by the task progress status through the task item set information 1010, . For example, a to-do item, which is a state before a to-do process is received from a to-do processor, is classified as a " new " item, and a to-do item is classified as a to- When completed, it is classified as "done". Items for which the to-do creator has confirmed completion of the to-do handler are classified as "OK".

The chat room interface providing unit 560 may provide a to-do message and a chat message to the user through a chat window 1020 associated with a specific friend.

The exit button 1030 may allow a user to exit a chat room associated with a particular friend. When the user leaves the chat room using the exit button 1030, the association of the user node to the chat room node is cut off, and the to-do items designated by the user as the to-do creator, to-do- The reference can be changed to unspecified.

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

100: to-do management system
110: message server 120: user terminal
120a: first user terminal 120b: second user terminal
210: to-do item receiving unit 220: to-do item set updating unit
230: Deadline schedule list update unit 240: Change notification schedule update unit
250: Task Item Offering 260: Task Information Provisioning
270: to-do item processing unit 280:
510: Deadline Schedule Interface Offering
520: Task List Interface Offering
530: To-do input interface provided
540: to-do processing interface providing unit 550: to-do interface updating unit
560: Room interface providing unit 570: To-do item set updating unit
580:

Claims (17)

1. A schedule-based task management method performed by a message server connected to at least one user terminals communicating with each other via a messenger,
(a) receiving a to-do item that includes a to-do and a to-do character to which a to-do handler can be currently or later designated from the user terminal;
(b) updating a message thread corresponding to a chat room associated with the user based on the to-do item and a to-do item set associated with the message thread; And
(c) updating the to-do list of the corresponding user so that the message thread and the to-do item set can access the to-do item based on the to-do item of the to-do item,
The step (a)
And a step of requesting confirmation of the to-do list and setting the status to a first start status in which a response is to be waited for.
The method according to claim 1,
(d) if the reference unit time is changed, checking whether the progress status of each task item is changed during the reference progress status period, and providing a notification message to at least one of the task creator and the to-do listener through the messenger Based on the task management information.
delete 2. The method of claim 1, wherein step (c)
And updating a to-do list schedule schedule included in the to-do schedule schedule list and associated with a to-do item designated by the to-do creator, to-do list or to-do referrer, .
2. The method of claim 1, wherein step (c)
And reflecting the to-do associator for accessing the to-do item of the to-do item set to the to-do finish schedule set.
The method according to claim 1,
Further comprising the step of providing a to-do item in a to-do item set associated with a to-do associate in said to-do set schedule set if a to-do set schedule set for a particular date in said to-do list schedule list is requested Based task management.
The method according to claim 1,
If a to-do list designated by the to-do creator, the to-do list or to-do referrer is requested, the to-do item included in the to-do item set and the to-do item included in the corresponding to-do item set And providing the task progress information statistically summarizing the progress status of each processing step in the schedule-based task management step.
1. A schedule-based task management method performed by a message server,
(a) generating first and second user nodes including user information about each of the first and second users to create a deadline schedule, a deadline schedule for accessing each item to be associated with the deadline schedule, With the first and second to-be-scheduled schedule lists for acquiring to-do-progress information statistically summarizing the process-by-process progress status of the set and the user's tasks;
(b) creating a chat room node associated with a message thread corresponding to the chat room as a child node of each of the first and second user nodes whenever chat rooms participated by the first and second users are created ;
(c) generating a to-do item corresponding to the to-do item and associating it with the chatting node each time a to-do associated with the message thread is received;
(d) updating to-do progress information of the first and second to-do list deadline lists based on the to-do item; And
(e) updating to-do progress information related to the to-be-finished schedule list every time the progress status of the task item is changed.
delete delete 9. The method of claim 8, wherein step (c)
Inserting a to-do correlator capable of accessing a corresponding item in the to-do list schedule set every time a to-do associated with the message thread is received.
delete 1. A schedule-based task management method performed by a user terminal communicating with itself or another user terminal via a message server,
(a) receiving a deadline schedule list from the message server and providing a deadline schedule interface that visualizes a date associated with a deadline in the deadline schedule list in a unit time schedule;
(b) providing a to-do list interface including a to-do item generated based on a predetermined to-do list of a predetermined date when a specific date is selected through the to-do list deadline interface; And
(c) providing a to-do processing interface capable of performing (1) a change of a progress state according to a processing step or (2) an entering of a chat room when the to-do item is selected through the to-do list interface ,
The step (a)
Based on a to-do item associated with the to-do list, through the to-do list schedule interface, and separately providing a to-do item designated by the to-do creator, to-do list, or to- .
delete delete 14. The method of claim 13, wherein step (b)
And providing a to-do list interface for creating a to-do item to be added to a message thread related to a specific chat room by designating the specific date as a due date character when a specific date is selected through the to-do list deadline interface Schedule - based task management.
14. The method of claim 13, wherein step (c)
When the to-do creator of the corresponding to-do item corresponds to the user, performing a change of to-do contents including a due date related to the to-do item through the to-do processing interface .

Images