KR102808309B1 - Method and apparatus for groupware service - Google Patents

Abstract

A method and device for groupware service are disclosed. A groupware service method performed on a server according to one embodiment may include a step of generating an attendance event including inviter information, a step of updating attendance information corresponding to the attendance event based on access to the attendance event of at least one inviter included in the inviter information, and a step of providing a notification regarding the attendance status of the attendance event through an area exposed to a terminal of an inviter who has not accessed the attendance event based on the attendance information.

Description

METHOD AND APPARATUS FOR GROUPWARE SERVICE

The following examples relate to methods and devices for groupware services.

Collaborative software, or groupware, is software that allows multiple users to simultaneously work on a single integrated project in separate work environments. Recently, with the development of mobile smart devices, the use of online platform services for communication with other users through networks has increased, and the use of groupware has also increased. Groupware services provide various functions for collaboration and work management by combining services for data exchange and sharing, such as chat, video conferencing, and cloud services. Accordingly, the development of technology for smooth communication and data sharing among multiple parties in a mobile environment is required.

The following examples can provide a groupware service technology that provides notifications regarding attendance events.

Through the examples below, a groupware service technology can be provided that provides attendance status information before accessing an attendance event based on the attendance status of other users for the attendance event, and provides a notification to induce attendance at the attendance event.

However, technical challenges are not limited to the technical challenges described above, and other technical challenges may exist.

A groupware service method performed on a server according to one side includes the steps of: generating an attendance event including inviter information; updating attendance information corresponding to the attendance event based on access to the attendance event by at least one inviter included in the inviter information; and providing a notification regarding the attendance status of the attendance event through an area exposed to a terminal of an inviter who has not accessed the attendance event based on the attendance information.

The step of providing the above notification may include at least one of the steps of providing the notification to a terminal of an inviter who has not accessed the attendance event if the attendance rate based on the attendance information is equal to or greater than a predetermined threshold attendance rate; and the step of providing the notification to a terminal of an inviter who has not accessed the attendance event if the number of non-attendees based on the attendance information is equal to or less than a predetermined threshold number of non-attendees.

The step of providing the above notification may include the step of setting a step condition based on the attendance information; the step of determining whether the step condition is satisfied based on the update of the attendance information; and the step of providing a notification mapped to the satisfied step condition when it is determined that the step condition is satisfied.

The above step-by-step condition includes a plurality of conditions to which a judgment order is assigned, and a condition of lower priority according to the judgment order is judged when a condition of higher priority is satisfied, and the intensity of a notification mapped to a condition of lower priority may be greater than the intensity of a notification mapped to a condition of higher priority.

The above attendance event may further include start time information, and the step condition may include a step condition based on the attendance information and the start time.

The step of providing the above notification may include a step of providing the notification to a terminal of an inviter who has not accessed the attendance event if the attendance rate included in the attendance information is greater than or equal to a first threshold attendance rate set in advance; and a step of providing an additional notification regarding the attendance status to a terminal of an inviter who has not accessed the attendance event if the attendance rate included in the attendance information is greater than or equal to a second threshold attendance rate set in advance, wherein the second threshold attendance rate is greater than the first threshold attendance rate.

The step of providing the above notification may include a step of providing the notification to a terminal of an inviter who has not accessed the attendance event if the number of non-attendees included in the attendance information is less than or equal to a first threshold number of non-attendees set in advance; and a step of providing an additional notification regarding the attendance status to a terminal of an inviter who has not accessed the attendance event if the number of non-attendees included in the attendance information is less than or equal to a second threshold number of non-attendees set in advance, wherein the second threshold number of non-attendees is less than the first threshold number of non-attendees.

The step of updating the above attendance information may include the step of identifying an attendance target among the inviters included in the inviter information; and the step of updating the attendance information based on an inviter identified as the attendance target among the inviters.

The step of identifying the above-mentioned attendance target may include at least one of the steps of identifying the attendance target among the invitees based on the status information of the invitees included in the inviter information; and the step of identifying the attendance target among the invitees based on the attendance options of the invitees included in the inviter information.

The above attendance event may further include start time information, and the step of providing the notification may include the step of providing the notification to a terminal of an inviter of the attendance event based on the attendance information and the start time.

The step of providing the above notification may include at least one of the steps of providing a visual indication for notifying an attendance rate based on the attendance information; the step of providing a visual indication for notifying at least one of the number of attendees and the number of non-attendees based on the attendance information; the step of providing a list of attendees who have connected to the attendance event; the step of providing a visual indication for indicating whether each invitee is present based on the attendance information; and the step of providing a signal requesting attendance at the attendance event.

Based on the above attendance information, the method may further include a step of providing an auditory signal regarding the attendance status of the attendance event.

The above attendance event may include at least one of group chat, video conferencing, voting, and surveys.

A groupware service method performed on a terminal according to one side includes the steps of: receiving an attendance event including a user account logged into the terminal as an inviter from a groupware server; providing an interfacing object for requesting attendance to the attendance event; determining a status of the attendance event based on whether an attendance request for the attendance event is received through the interfacing object; and displaying a notification regarding the attendance status of the attendance event received for the attendance event in a non-attendance status.

The step of determining the status of the above attendance event may include the step of determining the status of the received attendance event to a non-attendance status; and the step of changing the status of the attendance event to an attendance status when an attendance request is received through the interfacing object.

A server providing a groupware service according to one side includes at least one processor that generates an attendance event including inviter information, updates attendance information corresponding to the attendance event based on access to the attendance event by at least one inviter included in the inviter information, and provides a notification regarding the attendance status of the attendance event through an area exposed to a terminal of an inviter who has not accessed the attendance event based on the attendance information.

The processor may perform at least one of the following operations: providing the notification to a terminal of an invitee who has not accessed the attendance event if the attendance rate based on the attendance information is equal to or greater than a predetermined threshold attendance rate; and providing the notification to a terminal of an invitee who has not accessed the attendance event if the number of non-attendees based on the attendance information is equal to or less than a predetermined threshold number of non-attendees.

The processor, in providing the notification, sets a step condition based on the attendance information, determines whether the step condition is satisfied based on an update of the attendance information, and, when it is determined that the step condition is satisfied, provides a notification mapped to the satisfied step condition.

A terminal receiving a groupware service according to one side receives an attendance event including a user account logged into the terminal as an inviter from a groupware server, provides an interfacing object for requesting attendance to the attendance event, determines the status of the attendance event based on whether an attendance request for the attendance event is received through the interfacing object, and includes at least one processor for displaying a notification regarding the attendance status of the received attendance event for the attendance event in a non-attendance state.

FIG. 1 is a drawing illustrating an overview of a system for groupware service according to one embodiment.
FIG. 2a is a flowchart of the operation of a groupware service method performed on a server according to one embodiment.
FIG. 2b is a diagram illustrating an operation of providing a notification based on step-by-step conditions according to one embodiment.
Figure 3 is a flowchart of the operation of a groupware service method performed in a terminal according to one embodiment.
FIGS. 4A to 4C are diagrams illustrating notifications regarding attendance status of an attendance event provided to a terminal according to one embodiment.
FIG. 5a is a drawing illustrating a web screen output to a terminal executing a groupware web according to one embodiment.
FIG. 5b is a drawing illustrating an app screen output to a terminal running a groupware app according to one embodiment.
Figure 6 is an example diagram of the hardware configuration of a system for groupware service according to one embodiment.

Specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only and may be implemented in various forms. Accordingly, the actual implemented form is not limited to the specific embodiments disclosed, and the scope of the present disclosure includes modifications, equivalents, or alternatives included in the technical idea described in the embodiments.

Although the terms first or second may be used to describe various components, such terms should be construed only for the purpose of distinguishing one component from another. For example, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component.

When it is said that a component is "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but there may also be other components in between.

Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, the terms "comprises" or "has" and the like are intended to specify the presence of a described feature, number, step, operation, component, part, or combination thereof, but should be understood to not preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning they have in the context of the relevant art, and will not be interpreted in an idealized or overly formal sense unless explicitly defined herein.

Hereinafter, embodiments will be described in detail with reference to the attached drawings. In describing with reference to the attached drawings, identical components are given the same reference numerals regardless of the drawing numbers, and redundant descriptions thereof will be omitted.

FIG. 1 is a drawing illustrating an overview of a system for groupware service according to one embodiment.

Referring to FIG. 1, a system (100) for a groupware service according to one embodiment may include a terminal (110), a server (120), and a network (130). The specific hardware configuration of the server (120) and the terminal (110) is described in detail below.

A server (120) according to one embodiment may include a server providing a groupware service that provides a function for collaboration of one or more users through a network (130). The groupware service is not limited to a business collaboration service and may include a service that provides a communication function for sharing information between multiple terminals (110). For example, the groupware service may include a social network service, which is a media service for sharing information through a network (130), and/or an instant messaging service, which is a real-time communication service of multiple users through a network (130).

According to one embodiment, the groupware service may include a special purpose instant messenger service. For example, the special purpose instant messenger service may include an instant messenger service that supports communication between users belonging to a specific group (e.g., a company, a team, a meeting). The special purpose instant messenger service may include an instant messenger service that is provided as a group unit including a plurality of users. An instant messenger service that is provided as a group unit may mean a service that provides a communication space that all or some of the users belonging to the group can access, or a service that transmits and receives media so that all or some of the user accounts belonging to the group can share.

The server (120) may be linked to an application (hereinafter, “app”) related to a groupware service executed on a terminal (110) for a user interface (UI), function, operation, or service, or to a web related to a groupware service.

The terminal (110) may include, for example, a personal computer (PC), a netbook, a notebook, a personal digital appliance (PDA), a smartphone, a wearable device, and various devices performing similar functions.

The terminal (110) can be driven by an app (hereinafter, “groupware app”) related to a groupware service provided by the server or a web (hereinafter, “groupware web”) related to a groupware service provided by the server. A user can use the groupware service provided by the server (120) by executing the groupware app or groupware web on the terminal (110). A user can create a user account by signing up for the groupware service through the groupware app or groupware web. The groupware service can be used through the terminal (110) logged in with the created user account.

According to one embodiment, the groupware service may include a communication function. The communication function may include a function capable of performing data communication such as chat, call, media sharing, and video conferencing between terminals (110) connected to the communication space. The communication space is a virtual space that supports communication of multiple terminals (110) through a network (130), and may include, for example, a shared folder capable of sharing uploaded media files, a chat room, and/or a virtual video conferencing space that shares a camera view of a connected terminal (110) and supports a voice communication function.

According to one embodiment, the groupware service may include a schedule management function. The schedule management function may include a function for creating and registering a schedule and notifying a schedule. The schedule may include time information and/or participant information involved in the schedule. The time information of the schedule may include a start time of the schedule and/or an end time of the schedule. The participant information involved in the schedule may include user information to share the schedule and/or user information to participate in the schedule. The schedule management function may include a function for sharing the schedule with other user accounts. The schedule may include an attendance event that is executed with the attendance of one or more user accounts. The attendance event may include, for example, at least one of a group chat, a group call, a group video call, a video conference, a survey, and a vote. The attendance event is described in detail below.

In addition, groupware services may include functions such as e-mail for collaboration, electronic approval, bulletin board, user attendance management, and user search.

FIG. 2a is a flowchart of the operation of a groupware service method performed on a server according to one embodiment.

Referring to FIG. 2a, a groupware service method performed on a server according to one embodiment may include a step (210) of generating an attendance event including inviter information.

An attendance event is an event in which multiple user accounts connect, and may include, for example, at least one of a group chat, a group call, a group video call (e.g., a video conference), a survey, and a poll. The inviter information may include information about at least one user who has requested to attend the attendance event. For example, the inviter information may include a list including an identifier of at least one user account that has requested to attend the attendance event.

According to one embodiment, an attendance event can be created by a request from a terminal. The terminal requesting the creation of an attendance event can be a terminal logged in with a user account registered to a groupware service. The terminal requesting the creation of an attendance event can select an inviter of the attendance event. The inviter can include at least one user account registered to the groupware service. The user account selected as the inviter can include an account registered to the user account requesting the creation of the attendance event or an account included in the same group.

The server can provide information about the attendance event to a terminal (hereinafter, the inviter's terminal) logged in with a user account included in the inviter information of the attendance event. For example, a message notifying the creation of the attendance event can be transmitted to the inviter's terminal. For example, the attendance event can be registered as a schedule corresponding to the user account included in the inviter.

In one embodiment, an attendance event may include start time information. The start time may include time information at which the attendance event is set to start or be activated.

A groupware service method performed on a server according to one embodiment may include a step (220) of updating attendance information corresponding to an attendance event based on access to at least one attendee event included in inviter information.

The attendance information may include information indicating whether the invitee is present. For example, the attendance information may include information indicating whether each invitee is an attendee or a non-attendee. For example, the attendance information may include a list of invitees who attended the attendance event and a list of invitees who did not attend (or did not attend) the attendance event. For example, the attendance information may include at least one of an attendance rate and a number of non-attendees. For example, information including at least one of an attendance rate and a number of non-attendees may be obtained from the attendance information.

If at least one inviter's terminal included in the inviter information connects to the event, the attendance information can be updated. If a connection request is received from the inviter's terminal and the event is connected, the inviter can be displayed as an attendee in the attendance information. If a connection request is not received, the inviter can be displayed as a non-attendee in the attendance information.

For example, if the terminal of the first inviter connects to the attending event, the attendance information may be updated so that the first inviter changes from a non-attendee to an attendee. For example, if the terminal of the first inviter connects to the attending event, the attendance information may be updated so that the first inviter is deleted from the list of non-attendees and added to the list of attended invitees. For example, if the terminal of the first inviter connects to the attending event, the attendance rate and/or the number of non-attendees may be updated as the first inviter attends.

The step (220) of updating attendance information according to an embodiment may include a step of identifying an attendance target among invitees included in the inviter information, and a step of updating the attendance information based on an invitee identified as an attendance target among the invitees. The attendance target may include all or part of the invitees to be provided as attendance information regarding attendance. The attendance information may include information indicating whether an invitee who is an attendance target will attend, and may not include information indicating whether an invitee who is not an attendance target will attend.

According to one embodiment, the step of identifying the attendee may include a step of identifying the attendee among the invitees based on the status information of the invitees included in the inviter information. The status information of the invitee may include a status for determining whether the invitee is available to attend the attending event, for example, the invitee's service connection status, status regarding whether he or she is participating in another attending event or another schedule, and attendance status regarding commuting and vacation.

For example, a server that provides a business groupware service for corporate members can store attendance information of users including invitees. Attendance information can be entered by users through a groupware app or groupware web. For example, users can enter whether they are coming to work, whether they are leaving work, and whether they are using annual leave. The server can register the entered information as the user's attendance information.

According to one embodiment, the server may identify invitees who are available to attend the attendance event as attendees based on the status information of the invitees. For example, the server may identify invitees who are at work at the time when the attendance event is activated as attendees. Invitees who are not at work at the time when the attendance event is activated, are off work, or are on vacation may not be identified as attendees. For example, the server may identify users who are connected to the service and/or invitees who do not have other schedules at the time when the attendance event is activated as attendees.

According to one embodiment, the step of identifying the attendees may include a step of identifying the attendees among the invitees based on the attendance options of the invitees included in the invitee information. The attendance options are values set with respect to the attendance types of the attendance events, and may include, for example, mandatory attendance options and optional attendance options. An invitee set with a mandatory attendance option may correspond to an invitee who must attend the attendance event. An invitee set with an optional attendance option may correspond to an invitee who can choose whether to attend the attendance event. The attendance options of the invitees may be set by a user who created the attendance event, or may be set automatically depending on the attendance event and the invitees. The server may identify an invitee set with a mandatory attendance option as an attendance target based on the attendance options of the invitees.

In one embodiment, an attendance event may be set up to receive a response from an invitee as to whether or not to attend. Invitees who respond that they will not attend the attendance event may be excluded from the attendance target.

A groupware service method performed on a server according to an embodiment may include a step (230) of providing a notification regarding the attendance status of an attendance event through an area exposed to a terminal of an invitee who has not accessed the attendance event based on attendance information. As an example, the notification regarding the attendance status may be provided through a screen area of an app or web that is constantly displayed on a terminal that executes an app or web regarding the groupware service. As an example, the notification regarding the attendance status may be provided through a pop-up window displayed on a terminal that executes an app or web regarding the groupware service.

According to one embodiment, the step of providing a notification (230) may include a step of providing a visual display for notifying an attendance rate based on attendance information. The attendance rate may be included in the attendance information, and the attendance rate may be calculated based on information regarding the attendance of invitees included in the attendance information. For example, a ratio value of the current number of attendees to the total number of invitees of an attendance event may be visually displayed on a terminal of a non-attendee invitee who has executed a groupware app or groupware web.

According to one embodiment, the step of providing a notification (230) may include a step of providing a visual indication to indicate the number of absentees based on the attendance information. The number of absentees may be included in the attendance information, or the number of absentees may be obtained based on information regarding the attendance of invitees included in the attendance information. For example, a visual indication indicating that there are n absentees in the current attendance event may be visually displayed on a terminal of an absent invitee who has executed a groupware app or groupware web.

According to one embodiment, the step of providing a notification (230) may include a step of providing a list of attendees who have connected to the attendance event. For example, a list of invitees to the attendance event may be output to a terminal of a non-attendee invitee who has run a groupware app or groupware web.

According to one embodiment, the step (230) of providing a notification may include a step of providing a visual indication indicating whether each invitee has attended based on attendance information. For example, a list of invitees for an attendance event may be output to a terminal of a non-attendee invitee who has run a groupware app or groupware web, and whether each invitee has attended may be indicated through the list of invitees.

According to one embodiment, the step of providing a notification (230) may include a step of providing a signal requesting attendance at an attendance event. For example, a visual indication guiding attendance of an invited attendee to an invited attendance event may be output to a terminal of a non-attendee invitee who has run a groupware app or groupware web.

According to one embodiment, the step of providing a notification (230) may include a step of providing an auditory signal regarding the attendance status. For example, an auditory signal may be output to a terminal of a non-attendee invitee who has run a groupware app or a groupware web to inform of the attendance rate and/or the number of non-attendees of the invited attendance event. For example, a notification sound may be output together with a visual display to inform of the attendance status of the invited attendance event to a terminal of a non-attendee invitee who has run a groupware app or a groupware web.

Even if the user does not request information about the attendance event or access the attendance event, the user can be notified about the attendance status of the invited attendance event when the groupware app or groupware web is run. By providing a notification about the attendance status of the attendance event to a user who has not yet attended the attendance event, the user can be induced to attend the attendance event.

An example of a groupware app or groupware web screen that provides notifications regarding attendance status according to an embodiment of the present invention is described below.

According to one embodiment, the step of providing a notification (230) may include a step of providing a notification based on a condition regarding attendance information. If it is determined that the condition regarding the attendance information is satisfied, the notification may be provided. For example, the step of providing a notification (230) may include a step of providing a notification to a terminal of an invitee who has not accessed the attendance event if the attendance rate based on the attendance information is equal to or greater than a predetermined threshold attendance rate (e.g., 70%). In addition, for another example, the step of providing a notification (230) may include a step of providing a notification to a terminal of an invitee who has not accessed the attendance event if the number of non-attendees based on the attendance information is equal to or less than a predetermined threshold number of non-attendees (e.g., 1 person).

According to one embodiment, the step (230) of providing a notification may include a step of providing a notification based on a step-by-step condition regarding attendance information. This is described above with reference to FIG. 2b.

FIG. 2b is a diagram illustrating an operation of providing a notification based on step-by-step conditions according to one embodiment.

Referring to FIG. 2b, a server according to an embodiment may provide a notification regarding the attendance status of an attendance event to a terminal of an invitee who has not accessed the attendance event, including a step (240) of setting a step condition based on attendance information, a step (250) of determining whether the step condition is met based on an update of the attendance information, and a step (260) of providing a notification mapped to the met step condition when it is determined that the step condition is met.

The step condition may include multiple conditions with a judgment order. A condition with a lower priority according to the judgment order may be judged when a condition with a higher priority is satisfied. For example, if the step condition includes a first condition and a second condition, and the first condition has a higher judgment order than the second condition, if the first condition is judged to be satisfied after the first condition is judged to be satisfied, the second condition may be judged.

The attendance information for determining the step-by-step condition according to one embodiment may include at least one of the attendance rate and the number of non-attendees. According to one embodiment, the attendance rate and the number of non-attendees may be obtained from the attendance information. For example, the attendance rate may be obtained as the number of attendees compared to the total number of invitees from information indicating whether each invitee included in the attendance information will attend. For example, the number of non-attendees may be obtained from information indicating whether each invitee included in the attendance information will attend. For example, the step-by-step condition may include a first condition in which the attendance rate is greater than or equal to a first threshold attendance rate and a second condition in which the attendance rate is greater than or equal to a second threshold attendance rate. The second threshold attendance rate may be a value greater than the first threshold attendance rate, and the first condition may have a higher judgment order than the second condition. For example, the step-by-step condition may include a third condition in which the number of non-attendees is less than or equal to the first threshold non-attendees and a fourth condition in which the number of non-attendees is less than or equal to the second threshold non-attendees. The second critical number of absentees may be a smaller value than the first critical number of absentees, and the third condition may have a higher order of judgment than the fourth condition. For example, the step conditions may include a fifth condition in which the attendance rate is 70% or higher and a sixth condition in which the number of absentees is 1. The fifth condition may have a higher order of judgment than the sixth condition.

According to one embodiment, the step conditions may include step conditions based on attendance information and start time. As described above, the attendance event may include start time information. For example, the step conditions may include a seventh condition that the remaining time until the start time of the attendance event is 10 minutes or less, a fifth condition that the attendance rate is 70% or more, and a sixth condition that the number of non-attendees is 1. The judgment order may be in the order of the seventh condition, the fifth condition, and the sixth condition.

In one embodiment, the intensity of a notification mapped to a condition of lower priority may be greater than the intensity of a notification mapped to a condition of higher priority. The intensity of a notification may be determined by the number and size of visual indicators provided as a notification, whether special effects (e.g., color change, animation effect, etc.) are added to the visual indicators, the type of guidance text provided as a notification, and whether an auditory signal is added. For example, a notification mapped to a first condition may include a notification that adds a visual indicator to indicate the attendance status. A notification mapped to a second condition, which is lower priority than the first condition, may include a notification that adds a visual indicator to indicate the attendance status and a notification that displays a guidance text requesting attendance. In this case, a notification mapped to a second condition, which is lower priority, may provide a greater number of visual indicators than a notification mapped to a first condition, which is higher priority. In addition, for example, a notification mapped to a second condition, which is lower priority, may include a notification that adds a visual indicator to indicate the attendance status and output a notification sound. In this case, the notification mapped to the second priority condition may be an auditory signal added to the notification mapped to the first priority condition.

For example, step (260) may include a step of providing a notification to a terminal of an invitee who has not accessed an attendance event if the attendance rate based on the attendance information is equal to or greater than a first threshold attendance rate, and a step of providing an additional notification regarding the attendance status to a terminal of an invitee who has not accessed an attendance event if the attendance rate based on the attendance information is equal to or greater than a second threshold attendance rate. The second threshold attendance rate may be a value greater than the first threshold attendance rate. The additional notification mapped to the condition that the attendance rate is equal to or greater than the second threshold attendance rate may include a notification to which another visual indicator is added, an auditory signal is added, or a special effect is added to emphasize the previously provided notification.

For example, step (260) may include a step of providing a notification to a terminal of an invitee who has not accessed the attendance event if the number of non-attendees based on the attendance information is less than or equal to a first threshold number of non-attendees, and a step of providing an additional notification regarding the attendance status to a terminal of an invitee who has not accessed the attendance event if the number of non-attendees based on the attendance information is less than or equal to a second threshold number of non-attendees. The second threshold number of non-attendees may be a value smaller than the first threshold number of non-attendees. The additional notification mapped to the condition that the number of non-attendees is less than or equal to the second threshold number of non-attendees may include a notification in which another visual indicator is added to the notification mapped to the condition that the number of non-attendees is less than or equal to the first threshold number of non-attendees, an auditory signal is added, or a special effect is added to emphasize the previously provided notification.

Figure 3 is a flowchart of the operation of a groupware service method performed in a terminal according to one embodiment.

Referring to FIG. 3, a groupware service method performed in a terminal according to an embodiment may include a step (310) of receiving an attendance event including a user account logged into the terminal as an inviter from a groupware server. As described above, the attendance event may include inviter information including at least one user account. The terminal may correspond to a terminal of an inviter logged in with one of the user accounts included in the inviter information of the attendance event.

A groupware service method performed in a terminal according to one embodiment may include a step (320) of providing an interfacing object for requesting attendance at an attendance event. The interfacing object is an object that transmits a signal generated through interaction with a user to a server, and may include, for example, a button, an input window, etc. As an example, an interfacing object for requesting attendance at an attendance event may include a button that transmits a user's attendance request for the attendance event to the server when receiving a selection input from a user.

A groupware service method performed on a terminal according to one embodiment may include a step (330) of determining a status of an attendance event based on whether an attendance request for an attendance event is received through an interfacing object. The status of the attendance event is a status indicating whether a user account attends the attendance event, and may include an attendance status in which the user account has attended the attendance event, and a non-attendance status in which the user account has not attended the attendance event.

The step (330) of determining the status of an attendance event according to an embodiment may include a step of determining the status of the received attendance event as a non-attendance status. Before an attendance request is received through an interfacing object, the status of the attendance event may be determined as a non-attendance status. The step (330) of determining the status of the attendance event may include a step of changing the status of the attendance event to an attendance status and a step of transmitting the changed status of the attendance event to a server when an attendance request is received through the interfacing object. When an attendance request is received through the interfacing object, the user's terminal may access the attendance event. When accessing the attendance event, the status of the attendance event may be determined as an attendance status.

A groupware service method performed on a terminal according to an embodiment may include a step of displaying a notification regarding the attendance status of an attended event received for an attended event in a non-attendance state. As described above, the notification regarding the attendance status of an attended event may include at least one of an attendance rate of the attended event, the number of non-attendees, a list of attendees, information indicating whether each invitee is present, and a signal requesting attendance at the attended event. In addition, as an example, the notification regarding the attendance status of an attended event may be provided as an auditory signal.

According to one embodiment, a notification regarding the attendance status of an attendance event may be provided visually. For example, referring to FIG. 4A, a schedule notification window (401) including information regarding an attendance event may be displayed through a screen of an app or web regarding a groupware service running on a terminal. The information regarding the attendance event may include a title, time information, and location of the attendance event. The schedule notification window (401) may include a notification indicator (410) regarding the attendance status of the attendance event. For example, the notification indicator (410) regarding the attendance status may display the number of attendees among the total number of invitees. The information regarding the attendance event may include an interfacing object (420) for requesting attendance to the attendance event. The interfacing object (420) may be implemented as a button that receives a selection input from a user. When an input for selecting the interfacing object (420) is received, the terminal may request a server to connect to the attendance event.

For example, referring to FIG. 4b, a schedule notification window (402) displayed through a screen of an app or web regarding a groupware service running on a terminal may include an attendee list (430). The attendee list (430) may include an identifier of a user account that has accessed an attending event and/or a profile of the user account. As an example, the attendee list (430) may be displayed in response to an input of selecting or mouse-overing a notification indicator (410) regarding the attendance status of an attending event. Unlike as illustrated in FIG. 4b, a full invitee list may be provided, and the full invitee list may include a profile of a user account corresponding to each invitee and an indication indicating whether or not to attend.

For example, referring to FIG. 4c, a schedule notification window (403) displayed through a screen of a groupware app or groupware web running on a terminal may include a guidance text (440) requesting attendance at an attendance event. For example, if all invitees except the user of the terminal are determined to have attended the attendance event, a guidance text (440) requesting attendance at the attendance event may be output on the terminal in addition to a notification display (410) regarding the attendance status.

FIG. 5a is a drawing illustrating a web screen output to a terminal executing a groupware web according to one embodiment.

Referring to the screen (501) of Fig. 5a, a schedule notification window (510) including information about an attendance event may be displayed through an area exposed on the terminal. As described above in Figs. 4a to 4c, the schedule notification window (510) may include a notification mark regarding the attendance status.

According to one embodiment, the schedule notification window (510) may be constantly displayed on the groupware web screen. For example, when a chat function is executed on the groupware web, a list of chat rooms in which the user account participates and chat messages sent and received in the connected chat room may be displayed through the area (520), and a chat window for entering a chat message may be displayed. When a function other than the chat function (e.g., a schedule management function, etc.) is executed on the groupware web, a list of chat rooms related to the chat function and an interface related to the schedule management function other than the chat window may be output through the area (520). Meanwhile, even if the interface screen displayed on the area (520) changes due to the execution of another function, the schedule notification window (510) may be displayed in the same location.

FIG. 5b is a drawing illustrating an app screen output to a terminal running a groupware app according to one embodiment.

Referring to screen (502) of Fig. 5b, a schedule notification window (530) including information about an attendance event may be displayed through an area exposed on the terminal. As described above in Figs. 4a to 4c, the schedule notification window (530) may include a notification indicator regarding the attendance status.

According to one embodiment, the schedule notification window (530) may be displayed on the groupware app screen where the schedule management function is executed. Unlike the web screen of FIG. 5A, in the case of an app screen displayed through a mobile terminal having a relatively narrow display area, the schedule notification window (530) may not be constantly displayed on the app screen. For example, when a function other than the schedule management function (e.g., a chat function, etc.) is executed in the groupware app, the schedule notification window (530) may be displayed temporarily through a pop-up window or the like when the status of the attendance event changes and then disappears. For example, when an attendance event including a user account as an inviter is created, a schedule notification window may be displayed through a pop-up window to notify the creation of the attendance event. For example, when the attendance information of the attendance event is changed, a schedule notification window may be displayed through a pop-up window to notify the creation of the attendance event. For example, when the start time of the attendance event is approaching, a schedule notification window may be displayed through a pop-up window to notify the creation of the attendance event.

Figure 6 is an example diagram of the hardware configuration of a system for groupware service according to one embodiment.

Referring to FIG. 6, a system according to one embodiment (e.g., system (100) of FIG. 1) may include a terminal (110) (e.g., terminal (110) of FIG. 1) and a server (120) (e.g., server (120) of FIG. 1) connected via a network (130).

The terminal (110) according to one embodiment may be a mobile terminal implemented as a computer device. For example, the terminal (110) may communicate with a server (120) and/or other electronic devices through a network (130) using a wireless or wired communication method.

A server (120) according to an embodiment may be implemented as a computer device or a plurality of computer devices that communicate with a terminal (110) and/or another server through a network (130) to provide commands, codes, files, contents, services, etc. The communication method is not limited, and may include a communication method utilizing a communication network (e.g., a mobile communication network, wired Internet, wireless Internet, broadcasting network) that the network (130) may include, and a short-range wireless communication method between devices. For example, the network (130) may include any one or more of a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), a broadband network (BBN), and the Internet.

According to one embodiment, the server (120) may provide a file for installing a groupware app to a terminal (110) connected through a network (130). In this case, the terminal (110) may install the groupware app using the file provided from the server (120). In addition, the terminal (110) may connect to the server (120) and receive services or content provided by the server (120) under the control of an operating system (OS) and at least one program (e.g., a browser or an installed application) included in the terminal (110). For example, when the terminal (110) transmits a service request message to the server (120) through the network (130) under the control of an application, the server (120) may transmit a code corresponding to the service request message to the terminal (110), and the terminal (110) may configure and display a screen according to the code under the control of the application, thereby providing content to the user.

According to one embodiment, the terminal (110) and the server (120) may include a memory (611, 621), a processor (613, 623), a communication module (615, 625), and an input/output interface (617, 627).

The processor (613, 623) according to one embodiment can perform at least one operation described above with reference to FIGS. 1 to 5. For example, the processor (613) can perform at least one operation included in the groupware service method performed in the terminal (110) described above with reference to FIG. 3, and the processor (623) can perform at least one operation included in the groupware service method performed in the server (120) described above with reference to FIGS. 2A and 2B. The processor (613, 623) can be configured to process commands of a computer program by performing basic arithmetic, logic, and input/output operations. The commands can be provided to the processor (613, 623) by the memory (611, 621) or the communication module (615, 625).

The memory (611, 621) is a computer-readable recording medium and may be a volatile memory or a nonvolatile memory. The memory (611, 621) according to one embodiment may store information for the groupware service described above through FIGS. 1 to 5. For example, the memory (621) may store information about a user account subscribed to the groupware service described above and data shared between user accounts. For example, the memory (611) may store information about an attendance event included as an invitee.

According to one embodiment, a memory (611) may include code for a groupware app installed and driven on a terminal (110) by files provided from a server (120) through a network (130).

A memory (621) according to one embodiment can store a program implementing operations included in the groupware service method performed in the server (120) described above through FIGS. 1 to 5.

A communication module (615, 625) according to one embodiment may provide a function for a terminal (110) and a server (120) to communicate with each other via a network (130), and may provide a function for communicating with other electronic devices or other servers.

For example, a request generated by a processor (613) of a terminal (110) according to a program code for a groupware app stored in a recording device such as a memory (611) may be transmitted to a server (120) via a network (130) under the control of a communication module (615).

For example, control signals, commands, contents, files, etc. provided under the control of the processor (623) of the server (120) may be received by the terminal (110) through the communication module (615) of the terminal (110) via the communication module (625) and the network (130).

The input/output interface (617, 627) may be a means for interfacing with the input/output device (617). For example, the input device may include a device such as a keyboard or a mouse, and the output device may include a device such as a display for displaying a communication session of an application. As another example, the input/output interface (617) may be a means for interfacing with a device that integrates input and output functions, such as a touchscreen. As a more specific example, the processor (613) of the terminal (110) may use data provided by the server (120) to display a service screen or content on the display through the input/output interface (617) while processing a command of a computer program loaded into the memory (611). An input received from a user through the input/output device (617) may be provided in a form that can be processed by the processor (613) of the terminal (110) through the input/output interface (617).

According to one embodiment, the terminal (110) and the server (120) may include other components not shown in FIG. 6. For example, the terminal (110) may be implemented to include at least some of the input/output devices (617) described above, or may further include other components such as a transceiver, a Global Positioning System (GPS) module, a camera, various sensors, a database, etc.

The embodiments described above may be implemented as hardware components, software components, and/or a combination of hardware components and software components. For example, the devices, methods, and components described in the embodiments may be implemented using a general-purpose computer or a special-purpose computer, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing instructions and responding to them. The processing device may execute an operating system (OS) and software applications running on the OS. In addition, the processing device may access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing device is sometimes described as being used alone, but those skilled in the art will appreciate that the processing device may include multiple processing elements and/or multiple types of processing elements. For example, a processing device may include multiple processors, or a processor and a controller. Other processing configurations, such as parallel processors, are also possible.

The software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing device to perform a desired operation or may independently or collectively command the processing device. The software and/or data may be permanently or temporarily embodied in any type of machine, component, physical device, virtual equipment, computer storage medium or device for interpretation by the processing device or for providing instructions or data to the processing device. The software may also be distributed over computer systems connected to a network (130) and stored or executed in a distributed manner. The software and data may be stored on a computer-readable recording medium.

The method according to the embodiment may be implemented in the form of program commands that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may store program commands, data files, data structures, etc., alone or in combination, and the program commands recorded on the medium may be those specially designed and configured for the embodiment or may be those known to and available to those skilled in the art of computer software. Examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute program commands such as ROMs, RAMs, and flash memories. Examples of program commands include not only machine language codes generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.

The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

Although the embodiments have been described with limited drawings as described above, those skilled in the art can apply various technical modifications and variations based on them. For example, even if the described techniques are performed in a different order than the described method, and/or the components of the described system, structure, device, circuit, etc. are combined or combined in a different form than the described method, or are replaced or substituted by other components or equivalents, appropriate results can be achieved.

Therefore, other implementations, other embodiments, and equivalents to the claims are also included in the scope of the claims described below.

Claims (19)

In a groupware service method performed on a server,
Steps to create an attendance event including invitee information;
A step of updating attendance information corresponding to the attendance event based on the access of at least one inviter included in the inviter information to the attendance event; and
A step of providing a notification regarding the attendance status of the attendance event through an area exposed to the terminal of an invitee who has not accessed the attendance event based on the attendance information;
The steps to provide the above notification are:
A step of setting step-by-step conditions based on the above attendance information;
A step of determining whether the step-by-step condition is met based on the update of the above attendance information; and
A method comprising: providing a notification mapped to the satisfied step condition, upon determining that the above step condition is satisfied;
In the first paragraph,
The steps to provide the above notification are:
If the attendance rate based on the above attendance information is greater than or equal to a predetermined threshold attendance rate, a step of providing the above notification to the terminal of the inviter who has not accessed the above attendance event; and
If the number of non-attendees based on the above attendance information is less than or equal to a predetermined threshold number of non-attendees, a step of providing the above notification to the terminal of the inviter who did not access the above attendance event
Containing at least one of:
method.
delete In the first paragraph,
The above step condition includes multiple conditions to which a judgment order is given, and a condition of lower priority according to the judgment order is judged when a condition of higher priority is satisfied, and the intensity of a notification mapped to a condition of lower priority is greater than the intensity of a notification mapped to a condition of higher priority.
method.
In the first paragraph,
The above attendance event includes additional start time information,
The above step-by-step conditions are
Including step conditions based on the above attendance information and the above start time,
method.
In the first paragraph,
The steps to provide the above notification are:
If the attendance rate based on the above attendance information is greater than or equal to a predetermined first threshold attendance rate, a step of providing the above notification to the terminal of the inviter who has not accessed the above attendance event; and
If the attendance rate based on the above attendance information is greater than or equal to a second threshold attendance rate determined in advance - the second threshold attendance rate is greater than the first threshold attendance rate - a step of providing an additional notification regarding the attendance status to the terminal of the inviter who has not accessed the above attendance event
Including,
method.
In the first paragraph,
The steps to provide the above notification are:
If the number of non-attendees based on the above attendance information is less than or equal to a first threshold number of non-attendees, a step of providing the above notification to the terminal of the inviter who has not accessed the above attendance event; and
If the number of non-attendees based on the above attendance information is less than or equal to a second threshold number of non-attendees - the second threshold number of non-attendees is smaller than the first threshold number of non-attendees - a step of providing an additional notification regarding the attendance status to the terminal of the inviter who has not accessed the attendance event
Including,
method.
In the first paragraph,
The steps to update the above attendance information are:
A step for identifying the attendees among the invitees included in the above inviter information; and
A step of updating the attendance information based on the invitees identified as the attendees among the invitees above.
Including,
method.
In Article 8,
The steps to identify the above attendees are:
A step of identifying attendees among the invitees based on the status information of the invitees included in the above inviter information; and
A step of identifying attendees among the invitees based on the attendance options of the invitees included in the above inviter information.
Contains at least one of
method.
In the first paragraph,
The above attendance event includes additional start time information,
The steps to provide the above notification are:
A step of providing the notification to the terminal of the inviter of the attendance event based on the above attendance information and the above start time.
Including,
method.
In the first paragraph,
The steps to provide the above notification are:
A step of providing a visual display to indicate the attendance rate based on the above attendance information;
A step of providing a visual display to indicate at least one of the number of attendees and the number of non-attendees based on the above attendance information;
A step for providing a list of attendees who have connected to the above attendance event;
A step of providing a visual indication indicating whether each invitee will attend based on the above attendance information; and
Step for providing a signal requesting attendance at the above attendance event.
Containing at least one of:
method.
In the first paragraph,
The steps to provide the above notification are:
A step of providing an auditory signal regarding the attendance status of the attendance event based on the above attendance information.
Including more,
method.
delete delete A computer program stored on a medium for executing the method of any one of claims 1, 2, 4 to 12 in combination with hardware.
For servers that provide groupware services,
Create an attendance event that includes invitee information,
Based on the access of at least one inviter included in the above inviter information to the above attendance event, the attendance information corresponding to the above attendance event is updated,
Based on the above attendance information, a notification regarding the attendance status of the above attendance event is provided through an area exposed to the terminal of an invitee who has not accessed the above attendance event.
Contains at least one processor,
The above processor,
In providing the above notification,
Set step-by-step conditions based on the above attendance information,
Based on the update of the above attendance information, it is determined whether the above step conditions are met.
A server characterized in that, when the above step condition is determined to be satisfied, a notification mapped to the satisfied step condition is provided.
In Article 16,
The above processor,
In providing the above notification,
If the attendance rate based on the above attendance information is greater than or equal to a predetermined threshold attendance rate, an action of providing the above notification to the terminal of an invitee who has not accessed the above attendance event; and
If the number of non-attendees based on the above attendance information is less than or equal to a predetermined threshold number of non-attendees, an action is taken to provide the above notification to the terminal of the inviter who did not connect to the above attendance event.
Performing at least one of the following:
Server.
delete delete

Images