KR102624933B1 - Apparatus for notifing work schedule - Google Patents

Abstract

The present invention relates to a work schedule reminder device, wherein the work schedule reminder device includes a memory; and a processor electrically connected to the memory, wherein the processor creates a work chat room in which a task instructor and a task processor participate, and is a task message that can be classified independently from other messages under the control of the task instructor and has a deadline. Inserts an object into the work chat room, registers the work object in a work object database, searches the work object database in order of arrival of the deadline, and determines whether to create a reminder for the work object, In the process of creating the reminder, the reminder count of the work object is updated, and the reminder can be inserted as a conversation message in the work chat room by ensuring that the reminder includes at least a task summary and the reminder count.

Description

Work schedule reminder device {APPARATUS FOR NOTIFING WORK SCHEDULE}

The present invention relates to work schedule notification technology, and more specifically, to technology that can effectively provide information about work schedules according to work progress stages.

In general, groupware refers to a structure that includes software or software to support group work in which members of a company, etc., cooperate with each other to perform work in a workplace connected by computers. This mainly applies to software systems used by members of companies, institutions, and organizations to improve work efficiency by collaborating with each other in a computer-connected workplace.

Groupware allows computer users within a company to computerize tasks such as document preparation, approval, and document storage through personal computers connected to a communication network such as a LAN. Groupware combines business software such as a joint writing system using a word processor, numerical calculation, and database, and communication functions such as e-mail, electronic bulletin board, electronic approval, data sharing, messenger, and electronic meeting support are added.

The messenger function is being emphasized for efficient use of groupware. A messenger is an application that transmits messages containing text or graphics between users, and can be implemented as a chat room in which multiple users participate. In one embodiment, the Internet messenger may include a mobile messenger executed in a mobile environment (e.g., a mobile phone) and may include, for example, KakaoTalk, Line, WeChat, Facebook Messenger, etc. In addition, such Internet messengers are increasingly being used in a variety of ways in the management and progress of work.

Japanese Patent Application No. 2001-385042 (December 18, 2001)

According to an embodiment of the present invention, it is intended to display the current stage of work or progress of work at a glance. In addition, for the reminders sent for the task in question, the cumulative number of times the reminder has been provided will be changed to be displayed along with the reminder message, so that the current task progress, whether the deadline has arrived, the status of notification provision, etc. can be easily checked.

Among embodiments, the calendar reminder device may include memory; and a processor electrically connected to the memory.

The processor creates a work chat room in which a task instructor and a task processor participate, inserts a work object with a deadline into the work chat room as a work message that can be classified independently from other messages under the control of the task instructor, and the task object registers in the work object database, searches the work object database in the order of arrival of the deadline, determines whether to create a reminder for the work object, and determines the number of reminders for the work object in the process of creating the reminder. and the reminder can be inserted as a conversation message in the work chat room so that the reminder includes at least a work summary and the number of reminders.

The processor may determine whether to generate the reminder by detecting whether the deadline of the work object arrives within a specific period according to the occurrence of a deadline detection event.

The processor may generate the deadline detection event according to entry into the work chat room or update of the work object or periodically.

The processor may determine the creation of the reminder with respect to work objects currently in progress, excluding work objects whose status is in the completed state in the work object database.

The processor may update the status of the task object and reset the number of reminders according to the task progress of the task indicator or the task processor.

The processor may detect a reminder that was inserted in the past of the work object in the work chat room and modify the corresponding conversation message.

The processor may detect a reminder that was inserted in the most recent past of the task object.

The processor may modify the conversation message corresponding to the reminder inserted in the most recent past to include the processing progress of the task object as an effect of performing the reminder.

The processor may provide the reminder to the user terminal through a push notification independent of the work chat room during the insertion process of the reminder.

The processor may directly check the work object and process the work object without participation in the work chat room through the push notification.

The disclosed technology can have the following effects. However, since it does not mean that a specific embodiment must include all of the following effects or only the following effects, the scope of rights of the disclosed technology should not be understood as being limited thereby.

According to an embodiment of the present invention, the current progress of a task or the progress of a task can be displayed at a glance. In addition, for reminders sent for a given task, the cumulative number of times the reminder has been provided can be changed to be displayed along with the reminder message, making it easy to check the progress of the task, whether the deadline has arrived, and the status of notification provision.

1 is a diagram illustrating a work schedule reminder system according to the present invention.
FIG. 2 is a diagram illustrating the system configuration of the work schedule reminder device of FIG. 1.
FIG. 3 is a diagram illustrating the functional configuration of the work schedule reminder device of FIG. 1.
Figure 4 is a flowchart explaining the work schedule reminder method according to the present invention.
Figure 5 is a diagram explaining a work chat room according to the present invention.
Figure 6 is a flowchart explaining another embodiment of the work schedule reminder method according to the present invention.

Since the description of the present invention is only an example for structural or functional explanation, the scope of the present invention should not be construed as limited by the examples described in the text. In other words, since the embodiments can be modified in various ways and can have various forms, the scope of rights of the present invention should be understood to include equivalents that can realize the technical idea. In addition, the purpose or effect presented in the present invention does not mean that a specific embodiment must include all or only such effects, so the scope of the present invention should not be understood as limited thereby.

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

Terms such as “first” and “second” are used to distinguish one component from another component, and the scope of rights should not be limited by these terms. For example, a first component may be named a second component, and similarly, the second component may also be named a first component.

When a component is referred to as being “connected” to another component, it should be understood that it may be directly connected to the other component, but that other components may exist in between. On the other hand, when a component is referred to as being “directly connected” to another component, it should be understood that there are no other components in between. Meanwhile, other expressions that describe the relationship between components, such as "between" and "immediately between" or "neighboring" and "directly neighboring" should be interpreted similarly.

Singular expressions should be understood to include plural expressions unless the context clearly indicates otherwise, and terms such as “comprise” or “have” refer to implemented features, numbers, steps, operations, components, parts, or them. It is intended to specify the existence of a combination, and should be understood as not excluding in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

For each step, identification codes (e.g., a, b, c, etc.) are used for convenience of explanation. The identification codes do not explain the order of each step, and each step clearly follows a specific order in context. Unless specified, events may occur differently from the specified order. That is, each step may occur in the same order as specified, may be performed substantially simultaneously, or may be performed in the opposite order.

The present invention can be implemented as computer-readable code on a computer-readable recording medium, and the computer-readable recording medium includes all types of recording devices that store data that can be read by a computer system. . Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage devices. Additionally, the computer-readable recording medium can be distributed across computer systems connected to a network, so that computer-readable code can be stored and executed in a distributed manner.

All terms used herein, unless otherwise defined, have the same meaning as commonly understood by a person of ordinary skill in the field to which the present invention pertains. Terms defined in commonly used dictionaries should be interpreted as consistent with the meaning they have in the context of the related technology, and cannot be interpreted as having an ideal or excessively formal meaning unless clearly defined in the present application.

1 is a diagram illustrating a work schedule reminder system according to the present invention.

Referring to FIG. 1, the work schedule reminder system 100 may include a user terminal 110 and a work schedule reminder device 130.

In an embodiment of the present invention, a plurality of users may be included in one or more user groups. One or more user groups may be referred to as a first user group, a second user group, etc. One user may be included in one or more user groups.

The first user terminal 110a may correspond to the first user's terminal. The second user terminal 110b may correspond to the second user's terminal, the third user terminal 110c may correspond to the third user's terminal, and the fourth user terminal 110d may correspond to the fourth user's terminal.

Here, the first to fourth users may jointly participate in one or more tasks as task participants. At this time, the work may include tasks with a set deadline or periodic notes with a set recording period (i.e., note objects). In one embodiment, a task may correspond to the periodic creation of a note object.

According to an embodiment of the present invention, recording notes may be included among individual tasks instructed by the task manager. In the embodiment of the present invention, a note that is instructed to be written by a task instructor and written by a task handler is referred to as a note object. The note refers to the progress of the instructed task, the results of the instructed task, or detailed contents, etc. It can be self-entered text, a file object, a file link, etc.

And, here, the note object can be entered periodically until the end of the task. A note object that is periodically recorded in relation to the instructions of the relevant task until the end of the task may be specifically referred to as a periodic note.

Additionally, when a note object is required to be created or updated periodically, the period in which the note object must be recorded may be referred to as a note recording period. For example, in the case of a specific note object, if it is required to be written once every two weeks, the task handler must repeatedly enter periodic notes about the processing or progress of the task once every two weeks. In this case, the note recording cycle for each cycle is 2 weeks.

Additionally, whenever a note recording cycle arrives, the signal or message provided by the work schedule reminder device 130 to notify work participants, including the work handler, of the arrival or expiration of the deadline is referred to as a note reminder for each cycle.

For a specific task, one or more of the first to fourth users may be a task instructor, and one or more other users may be a task processor. Work participants, excluding work instructors and work handlers, can be classified as work related.

For example, there is a joint project in which the first to fourth users participate, and there may be one or more sub-tasks included or dependent on the project, and these sub-tasks are large and small that arise in the process of promoting the project. Tasks may be referred to as tasks or notes in embodiments of the present invention.

Here, the step-by-step classification of the progress or status of a project or task, each task or note, or periodic note can be referred to as a work progress stage.

For example, the task progress stage is the normal stage until a certain period of time has elapsed since the task was started, the imminent stage when the deadline for the task is imminent after a certain period of time has elapsed, and the delayed stage when the deadline for the task has already passed. It can be classified as:

As another example, work progress stages can be divided into in progress, confirmation, supplementation, and completion of supplementation according to the PDCA cycle. The PDCA cycle is known as a systematic and efficient work management technique to increase work performance and performance. P means establishing a plan, that is, setting a goal for a task or project and establishing specific strategies and action plans to realize it. And D means work performance (do), that is, actually carrying out work in accordance with regulations, guidelines, standards, etc. for matters for which a plan has been established. And C is confirmation, which is the stage where D's work performance results are checked, analyzed and evaluated to check for differences from the initially set goals and find areas to improve or correct. And A stands for act, which reflects the problems and points of improvement identified in the previous step C and executes what is necessary for improvement and supplementation, such as modifying existing work performance results or reprocessing work details. This is the step.

In other words, when work instructions are created by the work instructor (Plan, P), the work progress stage of the work becomes 'in progress'. In addition, if the task handler processes the task in accordance with the task instructions and uploads the task processing content as a result (Do, D), the work progress stage of the task becomes 'Confirming'.

Additionally, for a task that is 'being confirmed', the task manager can check the task processing content (Check, C) and terminate the task. In this case, the work progress stage of the task may be 'ended'. On the other hand, after the work instructor confirms the work processing content, he or she may request work supplementation for the work processing content. In this way, when a request for work supplementation or a work supplementation instruction is created by the work instructor, the work progress stage of the corresponding work becomes 'in progress'.

When the task processor supplements the task processing content corresponding to the content of the task supplementation instruction (Act, A), and the task supplementation content is uploaded by the task processor, or the uploaded task supplementation content is confirmed by the task instructor , the work progress stage of the relevant task can be set to ‘supplement complete’. And each task can be classified and arranged according to the stage of work progress.

The work schedule reminder device 130 may correspond to a computing device that can be connected to at least one user terminal 110 through a network. In one embodiment, the work schedule reminder device 130 may manage at least one user group in which other users associated with one user are members, that is, work participants.

In one embodiment, the work schedule reminder device 130 may be connected to the user terminal 110 through a shared folder agent installed on the user terminal 110. Here, the shared folder agent corresponds to an agent program, which is software that, when installed on the user terminal 110, allows the user terminal 110 and the work schedule reminder device 130 to interact with each other under the approval of the user terminal 110. .

Folders or files subject to sharing may be located in a shared folder provided by the work schedule reminder device 130, but are not limited thereto. Folders or files subject to sharing may be located in a shared folder provided by the work schedule reminder device 130 or in the personal folder of the file sharer.

The user terminal 110 corresponds to a computing device that can be connected to the work schedule reminder device 130 through a network, and may be, for example, a terminal implemented as a desktop, laptop, tablet PC, or smartphone.

In one embodiment, at least one of the user terminals 110 may be a mobile terminal and may be connected to the work schedule reminder device 130 through cellular communication or Wi-Fi communication. In another embodiment, at least one of the user terminals 110 may be a desktop and may be connected to the work schedule reminder device 130 via the Internet.

FIG. 2 is a diagram illustrating the system configuration of the work schedule reminder device of FIG. 1.

Referring to FIG. 2 , the work schedule reminder device 130 may include a processor 210, a memory 230, a user input/output unit 250, and a network input/output unit 270.

The processor 210 can execute a work schedule display procedure according to an embodiment of the present invention, and manage the memory 230 that is read or written in this process, and the volatile memory and non-volatile memory in the memory 230. Synchronization times between memories can be scheduled.

The processor 210 can control the overall operation of the work schedule reminder device 130 and is electrically connected to the memory 230, the user input/output unit 250, and the network input/output unit 270 to control data flow between them. can do. The processor 210 may be implemented as a CPU (Central Processing Unit) of the work schedule reminder device 130. More specific operation details of the processor 210 will be described in detail later with reference to FIG. 3.

The memory 230 may be implemented as a non-volatile memory such as a solid state disk (SSD) or a hard disk drive (HDD) and may include an auxiliary memory device used to store all data required for the work schedule reminder device 130. , may include a main memory implemented as volatile memory such as RAM (Random Access Memory). In this way, the memory 230 can be implemented as volatile and non-volatile memory, and if implemented as a non-volatile memory, it can be implemented to be connected through a hyperlink.

The user input/output unit 250 includes an environment for receiving user input and an environment for outputting specific information to the user, for example, a mouse, trackball, touch pad, graphic tablet, scanner, touch screen, keyboard, or pointing. It may include an input device that includes or is connected to an adapter such as a device, and an output device that includes an adapter such as a monitor or touch screen. In one embodiment, the user input/output unit 250 may correspond to a computing device connected through a remote connection, and in such case, the work schedule reminder device 130 may function as a server.

The network input/output unit 270 includes an environment for connecting to the user terminal 120 through a network and may include, for example, an adapter for LAN (Local Area Network) communication.

The work schedule reminder device 130 can receive various user signals through the user input/output unit 250 or the network input/output unit 270.

FIG. 3 is a diagram illustrating the functional configuration of the work schedule reminder device of FIG. 1.

Referring to FIG. 3, the work schedule reminder device 130 may perform a work schedule reminder method through the processor 210. To this end, the processor 210 may be implemented including a series of functional modules that perform each operation step. Specifically, the processor 210 may include a work chat room management unit 310, a work object creation unit 330, and a reminder management unit 350.

However, the processor 210 according to an embodiment of the present invention does not need to include all of the above components at the same time, and some of the above components may be omitted depending on each embodiment, and the processor 210 may include the above components. Some or all of the components may be optionally included.

The work chat room management unit 310 can create a work chat room in which work participants participate. Here, task participants may include task instructors and task handlers. First, the work chat room management unit 310 receives user information about one or more users from the user terminal 110 through the user input/output unit 250, and stores, manages, and updates the user information of users participating in the work. .

In addition, when the work chat room management unit 310 receives a request from a user to create a user group for a work chat room, it creates a user group and provides the name of each user group, classification criteria for the user group, information on members, etc., and matching information for each user group. You can store and manage information about chat room identification information, user group classification or affiliation, and permission management for each user or each user group.

The work chat room management unit 310 may use the user information collected through the above-described process and the user group information created using the same to create a work chat room in which some or all of the work participants participate.

In addition, if the user's user group varies depending on the user's affiliation or position, the work chat room management unit 310 sets identification information for the user group matching according to affiliation, department, or position, or creates a user group for each individual user. If specified, information about the specified user group can be saved.

The work chat room management unit 310 may provide or use previously collected user information when managing work schedules for each user or setting different deadlines for tasks, etc.

In an embodiment of the present invention, the user is a task participant including a task processor who will process the task according to the task processing content required through the task, a task instructor who instructs the task processor to process the task, and other task related personnel. It can be.

The work object creation unit 330 may create a work object under the control of a work instructor. That is, the work object creation unit 330 can receive work-related information or data from a work instructor, etc. and create one or more work objects. Here, the task object may include a task creator requesting the task, a task handler performing the task, and task content, and may further include at least one of the task deadline, whether points are provided, and all matters related to the task content. .

Additionally, the work object creation unit 330 may provide a user interface (UI) for creating work objects. At this time, the user interface for creating work objects may be provided through a work chat room. The user may input a user signal requesting the creation of a work object and/or a user signal containing schedule information for the task through the user interface provided in the work chat room. Additionally, data such as business data required for creating a work object can also be uploaded through the user interface for creating a work object.

The work object creation unit 330 may create a work object according to user signals and work data input through the user interface of the work chat room. The work object creation unit 330 may create a work object using work instructions, work deadline or work schedule information, work participant information, etc., and store the input information and work object in the memory 230. Additionally, the work object creation unit 330 can manage the input information and work objects by registering them in the work object database.

The work object creation unit 330 may insert the created work object into the work chat room, and in this case, the work object may be displayed as a work message in the work chat room. Additionally, work messages can be classified and managed independently from other messages, such as conversation messages displayed in work chat rooms.

The work object creation unit 330 can extract and manage information about work schedules and work deadlines from work objects related to work instructed by the work instructor. In addition, the work object creation unit 330 can also set or store information about permissions to access, open, and edit chat rooms, files, tasks, tasks, etc. for each user.

If a user who does not have access to a specific task is invited as a participant in a work chat room or as a task participant, the user can temporarily gain access to the task. In these cases, access to work may be limited. For example, access to the task may be possible only through a work chat room, and access to other tasks, other chat rooms, or other note objects may restrict access to subtasks, other tasks, or other notes that are dependent or connected to them. .

Or, limited rights to the work, such as restrictions on the content of the rights, such as allowing access to and viewing the work but not modifying or editing it, or access only until a specified period of time or before the deadline for the work has expired. This can be exemplified by time restrictions, etc.

In addition, the work object creation unit 330 stores various documents, data, and materials (hereinafter referred to as work materials) that can be created by each user in relation to work instructions or processing in the memory 230 and determines the presence or absence of the corresponding materials. You can check and manage. And, if a work chat room is created in relation to the uploaded work data, the work data with the chat room information inserted can be provided to the user terminal 110.

The reminder management unit 350 can perform operations to create and manage reminders about work objects. For example, the reminder management unit 350 may search for work objects in the work object database in order of arrival of deadlines and determine whether to create a reminder for the work objects. When it is decided to create a reminder, the reminder management unit 350 may update the number of reminders for each work object during the reminder creation process. At this time, the number of reminders may be accumulated and counted for each work object, and may be increased by 1 by the reminder management unit 350 each time a reminder creation operation is performed.

Additionally, the reminder management unit 350 can insert the reminder as a conversation message in the work chat room by ensuring that the reminder includes at least a work summary, deadline, and number of reminders. Therefore, participants in the relevant work chat room can share the progress of each work object through reminders displayed as conversation messages.

The reminder management unit 350 can collect and accumulate information on schedules for each task object and manage the due date and deadline for each task. Alternatively, the reminder management unit 350 may determine whether the deadline is imminent and determine whether to create a reminder. In addition, the reminder management unit 350 may create and send a reminder or notification that notifies the arrival or expiration of a deadline or informs of a future schedule corresponding to a preset work processing deadline or work supplementation deadline.

The reminder management unit 350 can create a reminder according to the task object and provide it to the task processor. At this time, the reminder may be sent directly to the user terminal 110 in the form of a text message, multimedia message, or push notification related to a task or periodic note, or may be provided in the form of a conversation message through a work chat room.

Here, the work chat room manager 310 can provide information for creating a reminder to the reminder manager 350, and the reminder manager 350 can determine when to insert the reminder as a conversation message in the work chat room.

For example, the reminder management unit 350 checks whether all tasks or periodic note records instructed to the task processor have been completed and, if so, when they were completed, based on the upload status of the task data, and then gives instructions to the task processor. If the requested content has not been processed, a reminder before the deadline can be inserted into the work chat room in which the task handler participates. The timing of the reminder's creation and insertion into the work chat room may depend on user settings, for example, 1 day, 3 days, or a week before the due date.

If the deadline expires without the requested task being completed, the reminder management unit 350 may provide a reminder or notification indicating the expiration of the deadline again to the terminal of the task handler and/or task instructor. Additionally, providing a reminder may be repeated until the task is completed.

The reminder management unit 350 can set the work progress stage of the task into two or more stages depending on whether the deadline of the work object is approaching or has passed. The reminder management unit 350 may set the work progress stage of each task according to the work instructions and supplementation instructions input from the user terminal 120, or the schedule in which work processing or work supplementation will be performed.

For example, the reminder management unit 350 may set the work progress stage of the work object to the normal stage once the work object is initiated, and then change the work progress stage to the imminent stage when the preset period elapses. Additionally, when the deadline calculated according to the task deadline has passed, the reminder management unit 350 may change the task progress stage of the task object to the delayed stage. When the work progress stage of the work object becomes, for example, an imminent stage, the reminder management unit 350 may generate a reminder and send it to the task handler, etc., or provide it as a conversation message through a work chat room in which the task handler participates.

Additionally, the reminder management unit 350 may determine whether to create a reminder by detecting whether the deadline of the work object arrives within a specific period according to the occurrence of a deadline detection event. Here, the deadline detection event may correspond to an operation signal that causes the reminder management unit 350 to start calculating the remaining period until the deadline for each work object. That is, the reminder management unit 350 may initiate an operation to determine the creation of a reminder associated with the corresponding work object according to the occurrence of a deadline detection event.

Additionally, the reminder management unit 350 may generate a deadline detection event according to entry into a work chat room or update of a work object, or periodically. The reminder management unit 350 can determine whether to create a reminder by forcibly generating a deadline detection event when a user associated with a work object, such as a work indicator, enters a work chat room or an update of the work object is performed. Even when there is no special event, the reminder management unit 350 may generate a deadline detection event at a preset period to determine whether to create a reminder.

Additionally, the reminder management unit 350 may determine the creation of a reminder for work objects currently in progress, excluding work objects whose status in the work object database is completed. The reminder management unit 350 is an operation triggered by the occurrence of a deadline detection event and can search for work objects currently in progress among work objects registered in the work object database, and determines the deadline of each work object based on the search time. The creation of a reminder can be determined depending on the remaining period.

In this case, the reminder management unit 350 may determine the creation of the reminder in various ways by additionally considering the remaining period until the deadline, the elapsed period from the most recent reminder creation date, and the importance of the work object.

Additionally, the reminder management unit 350 may update the status of the task object and reset the number of reminders according to the progress of the task of the task instructor or task handler. For example, in the case of a task, when the status changes from 'in progress', 'confirming', or 'complementing' to 'completed', the reminder management unit 350 can initialize the number of reminders for the work object associated with the task. In the case of a plan (schedule), when the state is changed to 'normal' by recording a note, the reminder management unit 350 can initialize the number of reminders for the work object associated with the note. Here, initializing the reminder count may mean setting the reminder count to 0, but it is not necessarily limited to this, and of course, the initialization value may vary depending on the operating environment.

Additionally, the reminder management unit 350 can detect a reminder that was inserted in the past of a work object in a work chat room and modify the corresponding chat message. Reminders created by the reminder management unit 350 may include various information about work objects. For example, the reminder may further include information about the remaining period until the deadline based on the current time, the elapsed time from the start date to the current time, the time of provision of the previous reminder, work progress status, etc.

Accordingly, the reminder management unit 350 may determine the items to be included in the reminder in relation to the work object at the current point in time at which the creation of the reminder has been decided, collect information on the items, and then create the reminder. Reminders generated by the reminder management unit 350 may be provided in the form of conversation messages through a work chat room, and basically, reminders inserted as conversation messages may be composed of static items whose contents do not change. However, if necessary, the reminder management unit 350 can detect reminders that were inserted in the past in the work chat room and update the corresponding chat message by modifying it based on the current time. At this time, modification of past reminders may be limited to cases where the corresponding reminder was created including at least one editable item.

For example, the reminder management unit 350 may detect a reminder that was inserted in the past in a work chat room and update it by modifying the number of reminders in the corresponding conversation message to the accumulated number based on the current time. Through this, business participants in the work chat room can easily check the latest information on the cumulative number of reminded reminders at the current time from the reminders distributed in conversation messages at all times.

Additionally, the reminder management unit 350 can detect a reminder that was inserted in the most recent past of a work object. The reminder management unit 350 can separately store and manage information about reminders inserted for each work chat room. The reminder management unit 350 may create and manage a reminder history for each work object. That is, the reminder management unit 350 can detect the most recently inserted reminder in the work chat room according to the reminder management method, and collect information about the number of reminders associated with the reminder, conversation messages, status of work objects, etc. .

Additionally, the reminder management unit 350 may modify the conversation message corresponding to the reminder inserted in the most recent past so that it includes the processing progress of the work object as an effect of performing the reminder. When the most recent reminder is detected, the reminder management unit 350 can add new information along with the existing information of the corresponding conversation message. At this time, the new information added may include work processing details related to the work object since the most recent reminder. For example, if the task object has been completed by the task processor who confirmed the reminder, the reminder management unit 350 adds a message indicating that the task object has been completed to the previously inserted conversation message as new information and sends the corresponding conversation message. can be modified.

Additionally, the reminder management unit 350 may provide a drop-down list of the processing progress of the work object while modifying the conversation message corresponding to the most recently inserted reminder. Through this, work participants in the work chat room can effectively check the work processing status of work objects in the conversation messages of each reminder provided at various points in time.

For example, in a work chat room, a chat message providing an existing reminder may be displayed as is, and content newly added by the reminder management unit 350 may be displayed as a drop-down menu at the bottom of the chat message. By selecting the drop-down menu of the corresponding conversation message, work participants can effectively check the progress of work processing related to the work object as information continuously added after the reminder. In addition, the most recent business processing information can be displayed along with a conversation message through the drop-down menu, and when the drop-down menu is activated according to the user's selection, the business processing information from the time of the reminder to the present is sorted in chronological order. can be displayed.

Additionally, the reminder management unit 350 may provide a reminder to the user terminal 110 through a push notification independent of the work chat room during the reminder insertion process. The reminder management unit 350 can basically provide a reminder as a conversation message through a work chat room, but it can also provide a reminder by providing a push notification directly to the user terminal 110. Additionally, the reminder management unit 350 may simultaneously provide conversation messages and push notifications as needed.

Additionally, the reminder management unit 350 can directly check the work object and process the work object without participation in the work chat room through push notification. For example, the reminder management unit 350 adds a hyperlink regarding the work object to the push notification provided directly to the user terminal 110, and when the user checks the push notification, the reminder management unit 350 adds the hyperlink to the work object through the hyperlink. Details may be provided. In other words, users can easily check work progress without access to the work chat room.

Additionally, the reminder management unit 350 can create a work progress bar using work schedule or deadline information. That is, the reminder management unit 350 can convert information about work deadlines or deadlines into the form of messages or signals such as progressive bars, reminders, alarms, or push notifications. Here, the progressive bar representing the schedule of work is referred to as a work progressive bar.

In general, a progressive bar is a widget that displays a period of time or the progress of a specific process, or shows the user that the process is in progress. Therefore, the task progress bar according to an embodiment of the present invention visualizes how much time has passed since the task associated with one task object was started according to a predetermined schedule and how much time remains until the task deadline, that is, the task deadline. .

The work progressive bar is created and updated for each work object, and can have the start date (work start date) and deadline (task deadline) of the work schedule corresponding to the work object as the start and end points of the work progressive bar.

In other words, the task progress bar visualizes how much time has passed at the current point in the entire timeline from the start date of a specific task to the deadline of the task, and the flow of time in task units. The task progressive bar indicates how much time has passed from the start date of the task to the present in real time through the position of the scroll bar. The position of the scroll bar is continuously updated based on the current time, and a new task object is created or a task object is reset. It can be updated every time.

In addition, when the reminder management unit 350 provides a task object and/or a task progress bar corresponding to the task object to the display of the user terminal 110 through a task chat room, the reminder management unit 350 displays a task object and/or a task progress bar corresponding to the task object in a color corresponding to the task progress stage set for the task object. It can be displayed as . When displaying each task or progressive bar through a work chat room, the reminder management unit 350 changes the color, size, brightness, background color, border color, font, shade, and color of the task or progressive bar according to the task progress stage of each task object. By applying different colors, blinking, etc., each task can be displayed to visually distinguish each task progress stage. When setting the work progress stage of a work object, the reminder management unit 350 may preset a display method, such as a color, corresponding to each work progress stage.

In addition, these differential display methods, such as colors, can be applied at any time when displaying the relevant task object and task progressive bar. When the user terminal 110 accesses the work database through a work chat room, cloud, intranet, shared folder, etc., the reminder management unit 350 displays each work object and work progress bar in color for each work progress stage to create a list. can be provided.

Additionally, the reminder and the work progress bar provided with the reminder can also be displayed in a display method corresponding to the work progress stage, such as the imminent stage. Here, changing the display method may include applying different colors, sizes, brightness, background colors, border colors, fonts, shading, boldness, blinking, etc. to icons, task names, file names, etc.

In addition, even when the user uploads the relevant work object to a web page accessible to work participants, etc., the reminder management unit 350 can display the icon, file name, thumbnail, etc. corresponding to the relevant work object along with the work progress bar. Task objects and task progress bars can be displayed in colors corresponding to the task progress stage.

Figure 4 is a flowchart explaining the work schedule reminder method according to the present invention.

Referring to FIG. 4, the work schedule reminder device 130 may create a work chat room in which a work instructor and a work handler participate (step S410). A work instructor or work handler may request the work schedule reminder device 130 to create a work chat room through the user terminal 110. Additionally, the work schedule reminder device 130 can receive information necessary for creating a work chat room from the user terminal 110. The work schedule reminder device 130 can set participation rights while creating a work chat room, and thus only users with limited rights related to work objects can enter the work chat room.

Additionally, the work schedule reminder device 130 may insert a work object with a deadline as a work message into the work chat room under the control of the work instructor (step S420). A task object may include information about task participants such as task creator, task instructor, and task handler, as well as task content, and can be created by including at least one of the following: task deadline, whether points are provided, and all other matters related to task content. there is.

Here, the task deadline can be set based on the work schedule information for the task input by the user. For example, when a user who requests the creation of a work object directly enters the deadline for the work object, the deadline may be set as the deadline for the work object. Alternatively, when a specific point in time is designated and stored as the start date of the work object and the progress period of the work object is input, the work schedule reminder device 130 can calculate and set the work deadline of the work object. If the start date of the work object is January 1, 2021, and the processing deadline for the work object is 2 weeks, the work deadline for the work object can be set to January 15.

Meanwhile, the creation of a work object and the creation of a work chat room do not necessarily have a precedence relationship, and the order may be changed. In particular, a work chat room may be created first, and then work objects may be created through a user interface provided through the work chat room. Additionally, work messages about work objects can be implemented to be classified independently from other messages, and through this, work participants in a work chat room can distinguish work messages from everyday conversation messages.

Additionally, the work schedule reminder device 130 can manage work objects by registering them in the work object database (step S430). The work object database may correspond to a dedicated database for registering, storing, and managing work objects. The work object database can operate in conjunction with the local DB or memory 230 of the work schedule reminder device 130 and can provide a logical storage space.

Additionally, the work schedule reminder device 130 may search for work objects in the work object database in order of arrival of the deadline and determine whether to create a reminder for the work object (step S440). The work schedule reminder device 130 may initiate a reminder creation operation according to the occurrence of a deadline detection event.

Additionally, when a reminder is created, the work schedule reminder device 130 may cumulatively count and update the number of reminders for the corresponding work object (step S450). The number of reminders can be managed for each work object and can be initialized according to the progress of the work object.

Additionally, the work schedule reminder device 130 may insert the reminder as a conversation message in the work chat room by ensuring that the reminder includes at least a work summary, deadline, and number of reminders (step S450). The work schedule reminder device 130 may provide a reminder directly to the user terminal 110 through a push notification, separately from providing a reminder through a work chat room.

Figure 5 is a diagram explaining a work chat room according to the present invention.

Referring to FIG. 5, the work schedule reminder device 130 may create a work chat room 500 in which users related to a specific work object, that is, work participants such as work instructors and work handlers, participate. Work participants can participate in the chat room 500 through their user terminal 110 and can freely exchange conversations about work as well as everyday conversations.

Meanwhile, the work chat room 500 may be created in association with a specific work object, and may correspond to a chat room in which only users associated with the work object can participate in a limited manner. A work object may include at least one task or note. In the case of FIG. 5, work objects associated with the work chat room 500 can be exemplified as task 1, task 2, and note object 3. Additionally, user A may correspond to a task instructor, and user B and user C may correspond to task processors.

Through the work chat room 500, conversation messages 501, 503, and 505 may be transmitted, work such as tasks or note objects may be shared, or file objects related to work may be transmitted.

Here, when user A shares task 1 through the work chat room 500, icon 1 510 corresponding to task 1 may be displayed through the chat window of the work chat room 500. At this time, the work deadline, work progress stage, etc. may be displayed together as work information related to Task 1.

Additionally, if the work progress stage of Task 1 is an imminent stage, icon 1 510 corresponding to Task 1 may be expressed in a color corresponding to the imminent stage. Additionally, a work progressive bar corresponding to task 1 may be displayed through the work chat room 500 along with task 1. At this time, the task progressive bar may be displayed and included in the conversation message regarding Task 1.

In addition, as a certain period of time elapses after Task 1 is started and the work progress stage of Task 1 becomes imminent, a reminder 530 notifying this may be transmitted through the work chat room 500.

Additionally, the reminder 530 may include user-specified information designating A and B as task handlers for Task 1. In Figure 5, user-specified information may be displayed as '@A,B'. Additionally, the reminder 530 may optionally display a work deadline or a work progress bar as work information for Task 1.

Additionally, the reminder 530 may display the number of reminders 550 along with the reminder message. In Figure 5, the number of reminders 550 may be displayed as '[2]'. In other words, the reminder may indicate that it is the second reminder since the corresponding work object was started.

Additionally, as shown in FIG. 5B, the reminder message included in the reminder 530a may include user-specified information 570a, a task summary 580, and the number of reminders 550a. As another example, the reminder message included in the reminder 530b may further include a reminder point in time (date and time) 585.

In addition, as shown in Figure 5c, the reminder messages included in the reminders 530c and 530d may include custom information 570b, 570c, a task summary 580, a task deadline 590, and the number of reminders 550b, 550c. , when a plurality of users are designated by user designation information 570c, the number of reminders 550c may be individually displayed for each designated user. For example, if task processors A and B are designated by user-specified information 570c, the number of reminders 550c displayed in the reminder 530d will be displayed separately as '[1][2]' for each user. You can. In other words, it may indicate that the corresponding reminder is the first reminder for task processor A and the second reminder for task processor B.

Figure 6 is a flowchart explaining another embodiment of the work schedule reminder method according to the present invention.

Referring to FIG. 6, the work schedule reminder device 130 may first create a work chat room (S610). The work schedule reminder device 130 can create a work chat room in which the work participants participate by using information about the work participants to create the work chat room, and then sends designated work handlers, work directors, etc. from among the work chat room participants. You can also set appropriate permissions.

In addition, the work schedule reminder device 130 can insert a work object with a deadline into the work chat room as a work message that can be classified independently from other messages under the control of the work indicator, and register the work object in the work object database ( Step S620). The progress of work objects registered in the work object database is managed by the work schedule reminder device 130, and notification information can be provided to related users through the reminder.

Thereafter, the work schedule reminder device 130 may search the work object database in order of arrival of the deadline and determine whether to create a reminder for the work object (step S630). The work schedule reminder device 130 may generate a deadline detection event according to entry into a work chat room or update of a work object or periodically, and may determine the creation of a reminder according to the occurrence of the deadline detection event.

The work schedule reminder device 130 may update the reminder count of the work object during the reminder creation process (step S640). If the number of updated reminders is 1, this is the first time a reminder has been created for the corresponding work object, so the reminder may be provided as a conversation message through the chat room (step S650).

If the number of updated reminders is not 1, a reminder has already been created and provided previously, so the work schedule reminder device 130 can detect the previous reminder in the chat room (step S660).

Thereafter, the work schedule reminder device 130 may update the status of the work object associated with the previous reminder according to the work progress of the work instructor or the work handler (step S670).

If the status of the work object has changed, the work schedule reminder device 130 may initialize the number of reminders for the work object (step S690). Here, when the status of a work object is changed, in the case of a task, it may correspond to a change from 'in progress', 'confirming', or 'complementing' to 'completed', and in the case of a plan (schedule), a note is recorded. This may correspond to a case where the status has been changed to ‘normal’. Afterwards, the reminder with the initialized number of times can be transmitted through the chat room.

In contrast, unless the status of the work object has changed, the work schedule reminder device 130 may modify the corresponding conversation message by adding the processing progress for the work object to the previous reminder (step S680).

Although the present invention has been described above with reference to preferred embodiments, those skilled in the art may make various modifications and changes to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. You will understand that you can do it.

100: Work schedule reminder system
110: User terminal 130: Work schedule reminder device
210: Processor 230: Memory
250: user input/output unit 270: network input/output unit
310: Business chat room management unit 330: Work object creation unit
350: Reminder management department

Claims (10)

Memory; and
Including a processor electrically connected to the memory,
The processor is
Create a work chat room in which work managers and work handlers participate,
Inserting a work object with a deadline into the work chat room as a work message that can be classified independently from other messages under the control of the work indicator,
Register the work object in the work object database,
Searching the work object database in the order of arrival of the deadline, determining whether to create a reminder for the work object,
In the process of creating the reminder, the reminder count of the work object is updated,
Insert the reminder into the work chat room as a conversation message so that the reminder message of the reminder includes at least user-specified information, a business summary, and the number of reminders, and the number of reminders is displayed together with the reminder message,
A work schedule reminder device, wherein when the reminder message includes user-specified information and a plurality of users are designated by the user-specified information, the number of reminders is individually displayed for each designated user.
The method of claim 1, wherein the processor
A work schedule reminder device that detects whether the deadline of the work object arrives within a specific period according to the occurrence of a deadline detection event and determines the creation of the reminder.
The method of claim 2, wherein the processor
A work schedule reminder device that generates the deadline detection event according to entry into the work chat room or update of the work object or periodically.
The method of claim 2, wherein the processor
A work schedule reminder device characterized in that it determines the creation of the reminder with respect to work objects currently in progress, excluding work objects whose status is in the completed state in the work object database.
The method of claim 1, wherein the processor
A work schedule reminder device that updates the status of the work object and resets the number of reminders according to the work progress of the work instructor or the work handler.
The method of claim 5, wherein the processor
A work schedule reminder device characterized in that it detects a reminder inserted in the past of the work object in the work chat room and modifies the corresponding conversation message.
The method of claim 6, wherein the processor
A work schedule reminder device, characterized in that detecting a reminder inserted in the most recent past of the work object.
The method of claim 7, wherein the processor
A work schedule reminder device, characterized in that the conversation message corresponding to the reminder inserted in the most recent past is modified to include the processing progress of the work object as an effect of performing the reminder.
The method of claim 1, wherein the processor
A work schedule reminder device that provides the reminder to a user terminal through a push notification independent of the work chat room during the insertion process of the reminder.
The method of claim 9, wherein the processor
A work schedule reminder device characterized in that the work object is directly confirmed and processed through the push notification without participation in the work chat room.