KR-102964569-B1 - APPARATUS AND METHOD FOR MANAGING GROUP MENTION BASED ON USER BEHAVIOR CONDITIONS BY MENTION TYPE

KR102964569B1KR 102964569 B1KR102964569 B1KR 102964569B1KR-102964569-B1

Abstract

The present invention relates to a group mention management device and method based on user behavior conditions by mention type, wherein the device comprises: a user mention receiving unit that receives a user mention including a user identifier and user information for one or more users forming a user group; an unread count calculating unit that identifies the user identifier to distinguish the mention type of the user mention and calculates the number of unreads of the user mention that have not yet been read by the user based on the user information; and an unread count processing unit that determines user behavior conditions for deducting the number of unreads according to the mention type and detects user behavior associated with the user mention to determine whether to deduct the number of unreads.

Inventors

최재호

Assignees

델타피디에스 주식회사

Dates

Publication Date: 20260513
Application Date: 20221007

Claims (11)

A custom mention receiver that receives a custom mention containing a custom identifier and custom information for one or more users forming a user group; An unread count calculation unit that identifies the above-mentioned user-specified identifier to distinguish the mention type of the above-mentioned user-specified mention, independently assigns user behavior conditions according to the mention type, and calculates the number of unreads of the above-mentioned user-specified mention that have not yet been read by the corresponding user based on the above-mentioned user-specified information; and A group mention management device based on user behavior conditions by mention type, comprising: a user behavior processing unit that determines the user behavior condition for deducting the number of unreads according to the mention type, monitors user behavior when the user behavior condition is determined for each user-specified mention to detect user behavior associated with the user-specified mention, and determines whether to deduct the number of unreads based on the existence of the user behavior.
In paragraph 1, the above unread count calculation unit A group mention management device based on user behavior conditions by mention type, characterized by identifying the user identifier to determine the user information when the user-specified mention is entered, and determining the designated target user of the user-specified mention by comparing the user information with previously stored user information.
In paragraph 1, the above unread count calculation unit A group mention management device based on user behavior conditions by mention type, characterized by determining the mention type of the user-specified mention based on the number of repetitions of a unit-specified command constituting the user-specified identifier.
In paragraph 1, the above unread count processing unit A group mention management device based on user behavior conditions by mention type, characterized by maintaining the number of unread messages for the user in the case where the detection of the user behavior satisfying the user behavior condition fails for a preset time based on the input time of the user-specified mention.
In paragraph 1, the above unread count processing unit A group mention management device based on user behavior conditions by mention type, characterized in that when the above-mentioned user-specified mention is entered as a conversation message within a chat room in which one or more of the above-mentioned users included in the user group participate, the act of entering a response message by the said user within the chat room is included in the user behavior condition.
In paragraph 1, the above unread count processing unit A group mention management device based on user behavior conditions by mention type, characterized by including a specific behavior required by the system message in the user behavior condition when the user identifier is used for a system message associated with the user group.
In paragraph 1, the above unread count processing unit A group mention management device based on user behavior conditions by mention type, characterized by including, respectively, the act of creating a note chat room associated with the work note and the act of inputting a response message within the said note chat room in the user behavior conditions when the said user identifier is used for a work note associated with the said user group.
In paragraph 1, the above unread count processing unit A group mention management device based on user behavior conditions by mention type, characterized by independently assigning user behavior conditions according to the mention type for each strategy map associated with the above user group.
In paragraph 1, A group mention management device based on user behavior conditions by mention type, further comprising: a mention reminder management unit that generates a reminder message according to a preset reminder period for a user-specified mention that has not yet been read by the user and sends it to the user.
In Clause 9, the above-mentioned mention reminder management department A group mention management device based on user behavior conditions by mention type, characterized by providing the reminder message to the user when the detection of the user behavior satisfying the user behavior condition fails, even if the user-specified mention is read by the user according to the mention type.
In a group mention management method based on user behavior conditions by mention type performed in a group mention management device based on user behavior conditions by mention type, A step of receiving a custom mention containing a custom identifier and custom information for one or more users forming a user group through a custom mention receiver; A step of identifying the user-specified identifier through an unread count calculation unit to distinguish the mention type of the user-specified mention, independently assigning user behavior conditions according to the mention type, and calculating the number of unreads of the user-specified mention that have not yet been read by the user based on the user-specified information; and A group mention management method based on user behavior conditions by mention type, characterized by including: a step of determining the user behavior condition for deducting the number of unread mentions according to the mention type through an unread mention processing unit, and when the user behavior condition is determined for each user-specified mention, monitoring the user behavior to detect the user behavior associated with the user-specified mention and determining whether to deduct the number of unread mentions according to the existence of the user behavior.

Description

Apparatus and Method for Managing Group Mentions Based on User Behavior Conditions by Mention Type The present invention relates to a technology for managing user mentions within a group, and more specifically, to a technology that effectively supports work performance by enabling mentions to be smoothly shared among work participants participating in a joint project or work. Traditionally, various methods have been provided to share users' messages or mentions in order to enhance work efficiency through multi-party communication. And, various interfaces such as web pages, shared folder systems, chat rooms, and clouds can be used to share these messages, mentions, and comments. For example, an internet messenger is an application that allows users to share messages or mentions containing text or graphics, and can be implemented as a chat room in which multiple users participate. Recently, as the scale of projects has grown, there is a trend of increasingly diverse utilization of such internet messengers for the management and progress of work. However, conventional technology had the problem of being difficult to identify users who must check the mentions when providing mentions, and it was difficult to distinguish the number of mentions accumulated for each user and the importance and weight among those mentions. FIG. 1 is a drawing illustrating a group mention management system according to the present invention. Figure 2 is a diagram illustrating the system configuration of the group mansion management device of Figure 1. Figure 3 is a diagram illustrating the functional configuration of the group mansion management device of Figure 1. FIG. 4 is a flowchart illustrating a group mention management method based on user behavior conditions according to the present invention. FIGS. 5 and 6 are drawings illustrating an embodiment of the management process of a group mansion according to the present invention. FIG. 7 is a drawing illustrating a user-specified mention and a user-unspecified mention according to the present invention. FIG. 8 is a drawing illustrating an embodiment of the process of deducting the number of unread mentions according to the present invention. FIG. 9 is a drawing illustrating an embodiment of a group mention management method according to the present invention. FIG. 10 is a drawing illustrating another embodiment of a group mention management method according to the present invention. The description of the present invention is merely an example for structural or functional explanation, and therefore the scope of the present invention should not be interpreted as being limited by the examples described in the text. That is, since the examples are subject to various modifications and may take various forms, the scope of the present invention should be understood to include equivalents capable of realizing the technical concept. Furthermore, the objectives or effects presented in the present invention do not imply that a specific example must include all of them or only such effects; therefore, the scope of the present invention should not be understood as being limited by them. Meanwhile, the meaning of the terms described in this application should be understood as follows. Terms such as "first," "second," etc., are intended to distinguish one component from another, and the scope of rights shall not be limited by these terms. For example, the first component may be named the second component, and similarly, the second component may be named the first component. When it is stated that one component is "connected" to another component, it should be understood that it may be directly connected to that other component, or that there may be other components in between. Conversely, when it is stated that one component is "directly connected" to another component, it should be understood that there are no other components in between. Meanwhile, other expressions describing the relationships between components, such as "between" and "exactly between," or "adjacent to" and "directly adjacent to," should be interpreted in the same way. A singular expression should be understood to include a plural expression unless the context clearly indicates otherwise, and terms such as "include" or "have" are intended to specify the existence of the implemented features, numbers, steps, actions, components, parts, or combinations thereof, and should be understood not to preclude the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof. In each step, identifiers (e.g., a, b, c, etc.) are used for convenience of explanation and do not describe the order of the steps; the steps may occur differently from the specified order unless a specific order is clearly indicated in the context. That is, the steps may occur in the same order as specified, may be performed substantially simultaneously, or may be performed in the reverse order. The prese