KR102439877B1 - Apparatus and operating method of messenger server providing schedule service - Google Patents

Abstract

According to an exemplary embodiment, a method of operating an instant messenger server includes: generating a schedule dependent on an account of a host in response to a schedule creation request from a host; receiving invitations to be invited to an event; Receiving whether to participate in a schedule from at least one guest included in the invitation target; updating participant information included in the schedule based on whether at least one guest has participated; and synchronizing schedules dependent on accounts of users participating in the schedule based on the updated participant information.

Description

Operation method and apparatus of an instant messenger server that provides scheduling service

The following embodiments relate to a method and apparatus for operating an instant messenger server that provides a schedule service.

The user may participate in a number of various chat rooms through the instant messenger server to share conversations and/or data with other participants. In addition, the instant messenger server may also provide a calendar that allows the user to manage schedules well. However, the calendar provided by the instant messenger server is subordinate to the chat room, and the schedule of the calendar is created in the chat room unit. In addition, it is disclosed to the participants participating in the chat room, and all schedule information is also disclosed regardless of the time when the participants joined the chat room. Due to this, there is a problem in that it is difficult to manage a personal schedule on the instant messaging service.

According to one aspect, an operating method of an instant messenger server providing a schedule service includes: generating a schedule dependent on an account of the host for the instant messaging service in response to a schedule creation request from a host; receiving an invitation to be invited to the schedule based on at least one of a chat room list of the host's account and a friend list of the host's account on the instant messaging service; receiving whether to participate in the schedule from at least one guest included in the invitation target; updating participant information included in the schedule based on whether the at least one guest participates; and synchronizing schedules dependent on accounts of users participating in the schedule based on the updated participant information.

The schedule dependent on the user's account for the instant messaging service may include a schedule registered in a calendar for each user. The user-level calendar may include a plurality of schedules registered through a plurality of chat rooms in which the user participates.

The step of receiving whether to participate in the schedule from the at least one guest may include: determining a chat room to share the schedule with, based on the invitation target; and by sharing the schedule in the chat room, receiving from the at least one guest whether to participate in the schedule.

When the host's schedule creation request is generated through a specific chat room, users participating in the corresponding chat room may be automatically entered as the invitation target.

The method of operating the instant messenger server may include providing a candidate chat room including an invitation target included in the participant information in response to a chatting request related to the schedule; providing a candidate chat room including an attendee from among the invitees included in the participant information in response to the chatting request related to the schedule; generating a new chat room including an invitation target included in the participant information in response to the chat request related to the schedule; And in response to the chatting request related to the schedule, it may further include at least one of the steps of creating a new chat room including the attendees from among the invitees included in the participant information.

The generating of the schedule may include: determining whether the schedule creation request is generated through a general chat room; and tagging identification information of the general chat room to the schedule based on the determination result.

The method of operating the instant messenger server may include: providing an interface for editing a schedule dependent on an account of the host; and as the schedule dependent on the host's account is edited, synchronizing the edited schedule with the at least one schedule dependent on the account of the at least one guest.

The method of operating the instant messenger server may include: in response to a schedule preview request of a user participating in a specific chat room, accessing a schedule dependent on an account of the corresponding user; and providing an interface for searching for a schedule dependent on the corresponding user's account.

The method of operating the instant messenger server may further include, in response to the host's request to share the schedule, sharing the requested schedule to the sharing requested chat room.

The method of operating the instant messenger server may include: receiving an invitation request from a user who does not correspond to the invitation target among users of a chat room in which the schedule is shared; receiving whether to accept the invitation request from the schedule host; and updating the participant information included in the schedule based on whether the host accepts or not.

The method of operating the instant messenger server may further include migrating a schedule dependent on a specific chat room to schedules dependent on users participating in the corresponding chat room.

The method of operating the instant messenger server may include: receiving, from a specific user, a search request based on participant information; extracting at least one schedule corresponding to the search-requested participant information from among a plurality of schedules dependent on the account of the specific user; and providing the extracted at least one schedule.

The method of operating the instant messenger server may include: receiving a schedule preview request through the chat room from a user participating in the chat room of the instant messaging service; and providing a view for preferentially displaying a schedule associated with the chat room among schedules dependent on the user's account.

According to one aspect, a method of operating an instant messenger application for providing a schedule service includes: transmitting a schedule creation request for creating a schedule dependent on a user's account for the instant messaging service to a server; receiving an invitation to be invited to the schedule based on at least one of a chat room list of the user's account and a friend list of the user's account; and receiving, from the server, participant information updated based on whether at least one guest included in the invitation object participates. Based on the updated participant information, schedules dependent on accounts of users participating in the schedule may be synchronized.

The method of operating the application may further include displaying a plurality of schedules registered through a plurality of chat rooms in which the user participates through a calendar for each user.

The method of operation of the application includes: in response to a chatting request related to the schedule, displaying a candidate chat room including an invitee included in the participant information; displaying a candidate chat room including an attendee from among the invitees included in the participant information in response to the chatting request related to the schedule; displaying a new chat room including an invitation target included in the participant information in response to the chat request related to the schedule; And in response to the chatting request related to the schedule, it may further include at least one of displaying a new chat room including an attendee from among the invitees included in the participant information.

The generating of the schedule may include transmitting, to the server, information for tagging identification information of the general chat room to the schedule when the schedule creation request is generated through a general chat room.

The method of operating the application may include: transmitting a request for sharing the schedule to the server through the instant messaging service; receiving an invitation request from a user who does not correspond to the invitation target among users of the chat room in which the schedule is shared; receiving an input of whether to accept the invitation request; and transmitting, to the server, information for updating participant information included in the schedule, based on the acceptance or not.

The method of operating the application includes: receiving a schedule preview request through a chat room in which the user participated; and displaying a view that preferentially displays a schedule associated with the chat room among schedules dependent on the user's account.

1 is a view for explaining a method of operating an instant messenger server that provides a schedule service according to an exemplary embodiment;
2 is a flowchart illustrating a method of operating an instant messenger server that provides a schedule service according to an exemplary embodiment;
3 is a diagram illustrating a screen of a calendar on which a schedule is displayed, according to an exemplary embodiment;
4 is a view for explaining a method of receiving an invitation to be invited to a schedule according to an embodiment;
5 is a view for explaining a method of requesting a chat with a participant in a schedule according to an embodiment;
6 is a view for explaining a method of receiving an input whether to participate in a schedule according to an embodiment;
7 is a diagram for describing a process in which a host shares a schedule with participants, according to an exemplary embodiment;
8 is a view for explaining a method of providing at least one schedule corresponding to search-requested participant information, according to an embodiment;
9 is a view for explaining a method of performing a schedule preview according to an exemplary embodiment;
10 is a diagram illustrating a schedule reminder screen according to an exemplary embodiment;

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Like reference numerals in each figure indicate like elements. Various modifications may be made to the embodiments described below. It should be understood that the embodiments described below are not intended to limit the embodiments, and include all modifications, equivalents, and substitutions thereto.

Terms used in the examples are only used to describe specific examples, and are not intended to limit the examples. The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present specification, terms such as “comprise” or “have” are intended to designate that a feature, number, step, input, component, part, or combination thereof described in the specification exists, but one or more other features It should be understood that this does not preclude the possibility of addition or existence of numbers, steps, inputs, 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 to which the embodiment belongs. Terms such as those defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

In addition, in the description with reference to the accompanying drawings, the same components are assigned the same reference numerals regardless of the reference numerals, and the overlapping description thereof will be omitted. In the description of the embodiment, if it is determined that a detailed description of a related known technology may unnecessarily obscure the gist of the embodiment, the detailed description thereof will be omitted.

1 is a diagram for explaining a method of operating an instant messenger server that provides a schedule service according to an exemplary embodiment. Referring to FIG. 1 , operations performed by an instant messenger server (hereinafter, 'server') providing an instant messaging service according to an embodiment in a host domain 101 and a guest domain 102 are shown. is shown

In an embodiment, a 'host' may correspond to a user who creates a schedule dependent on his/her own account among users using the instant messaging service. The host may select or determine who will be invited to the event from among other users using the instant messenger server. In this case, an invitation target invited to the corresponding schedule by the host may correspond to a 'guest'. The host domain may be a service area provided through an application installed in the terminal of the host, and the guest domain may be a service area provided through an application installed in the terminal of the guest.

The host terminal and the guest terminal may be driven by an application installed in each terminal. In each terminal, for example, an instant messenger application that provides a service for managing schedules dependent on the host's account to the user may be installed. The corresponding application may include an application providing a social networking service or an instant messaging service. A terminal according to an embodiment includes, for example, a personal computer (PC), a netbook, a notebook, a personal digital appliance (PDA), a smart phone, a wearable device, and various user display devices performing similar functions. can do.

The server interworks with an instant messenger application installed in the terminal of the host for a user interface (UI), function, operation, or service provided by the host domain 101 , and is provided by the guest domain 102 . For a user interface (UI), a function, an operation, or a service, it may be linked with an instant messenger application installed in the guest's terminal.

The server may include a first server providing a scheduling service and a second server providing an instant messaging service. For example, the first server may provide services of schedule creation 110 , schedule invitation 120 , schedule price registration 130 , and news 140 . In addition, the second server may provide services of chat rooms (103, 106), chat rooms with me (104, 107), and my drawer (105). The first server and the second server may be implemented on a single server or may be implemented as separate servers. Through the interworking between the first server and the second server, the schedule service and the instant messaging service may be linked.

The host domain 101 may include, for example, a general chat room 103 , a chat room with me 104 , and a drawer 105 . The general chat room 103 may correspond to a general type of chat room in which the user participates in order to chat with at least one other person. The chat room 104 with me is a chat room of a predetermined type for a conversation with the user himself, and can be distinguished from the general chat room 103 . My drawer 105 may refer to a storage service interworking with an instant messaging service.

The host may transmit a schedule creation request to the server through a general chat room 103 , a chat room with me 104 , or a drawer 105 . Although not shown in the drawing, according to an embodiment, an application installed on the terminal of the host may transmit a schedule creation request to the server through a user interface separately provided for a schedule service.

The server may create a schedule dependent on the host's account for the instant messaging service in response to the host's schedule creation request ( 110 ). In this case, the calendar including the schedule is subordinated to the account of the host, not the chat room, and individual schedule(s) included in the calendar may also be subordinated to the account of the host. That the schedule depends on the account may mean that the corresponding schedule is registered in a calendar for a specific account (or a calendar for each user). For example, when a schedule depends on an account, even if a plurality of schedules are created through a plurality of chat rooms, they may be registered in the same calendar for the host's account. On the other hand, when a schedule is subordinate to a chat room, when a plurality of schedules are generated through a plurality of chat rooms, each schedule is registered in a different calendar for the corresponding chat room.

When the schedule is created, the host may invite guests of the created schedule by selecting an invitation target with whom the schedule is to be shared ( S120 ). In this case, the invitation target may be a specific chat room or an individual user. For example, the host may receive invitations to an event on the instant messaging service based on the host's account's list of chat rooms and/or the host's account's list of friends. In order to receive an invitation target from the host, a picker interface including a chat room list and/or a friend list in the host domain may be provided through the host's terminal. According to an embodiment, when a schedule creation is requested through a general chat room, the chat room or participants of the chat room may be automatically entered as invitation targets.

Although not shown in the drawings, the step of receiving the invitation may be included in the step of generating the schedule. For example, an interface for receiving an invitation input in response to a schedule creation request from the host may be provided to the terminal of the host, and a schedule may be generated after input of the invitation target is completed.

The server may receive whether to participate in the corresponding schedule from at least one guest included in the invitation target. For example, the server may temporarily register a schedule 130 in the guest's personal calendar in response to the host's schedule invitation 120 , and notify the guest's terminal that there is an invited schedule through the news 140 . Guests can enter whether or not to participate in the invited event. The tentatively registered schedule in the guest's personal calendar may be a schedule dependent on the guest's account. Although not shown in the drawing, according to an embodiment, the invitation/change notification may be provided through a chat room in which the host and the guest participate.

The server may update participant information included in the schedule dependent on the host's account based on whether the guest participates. The participant information may include information on invitees, and/or information on responses (eg, attendance, non-attendance, and undefined responses) of invitees.

In this case, the server may synchronize schedules dependent on accounts of users participating in the corresponding schedule based on the updated participant information. For example, you can synchronize schedules that depend on the host's account with those that depend on the guest's account. The server may update the participant information included in the schedule dependent on the guest's account. According to an embodiment, the server may synchronize schedules dependent on accounts of invitees invited to the schedule, or synchronize schedules dependent on accounts of participants who have expressed their intention to participate among the invitees.

According to an embodiment, the schedule dependent on the host's account may be shared through a chat room. For example, as the invitation target is determined, the server may automatically determine the chat room 106 to share the schedule based on the invitation target. For example, the server determines a 1:1 chat room between an individual user included in the invitee and the host as the chat room to share the calendar with, or a group chat room between users included in the invitee and the host as the chat room to share the calendar with. can be determined as Alternatively, the server may receive a chat room to share the schedule from the terminal of the host. For example, the server may recommend a plurality of candidate chat rooms to share the schedule to the user, and determine the chat room to share the schedule according to the user's selection.

The server may share the shared schedule with the determined chat room 106 in response to the host's schedule sharing request. Since the server shares the schedule in the chat room 106 , the host and the guest can check each other's schedule through the chat room 106 .

According to an embodiment, 'invite' is an action for designating users to share a schedule on a schedule service, and 'share' is an action for transmitting a message for sharing a schedule through a messaging service. The subject of 'invite' and the subject of 'share' may be the same or different. For example, after a schedule S is created by designating an invitation target to a user A and a user B, the schedule S may be shared to a group chat room G in which the user A, the user B, and the user C are participating. In this case, the user C is not invited to the schedule S, but may receive the schedule S shared through the group chat room G.

Not all users of chat rooms with shared schedules are eligible for invitation. As will be described in detail below, in this case, a user who does not correspond to an invitation target among users of a chat room with a shared schedule may transmit an invitation request to the host to invite them. Users who are not invited can participate in the event as a guest if an invitation request is accepted from the host of the event.

When the server shares a schedule in the chat room 106, the schedule may be provisionally registered as a personal calendar of the guest (130). A schedule provisionally registered as a guest's personal calendar may be created as a guest's schedule when the guest inputs whether to participate in the corresponding schedule. In this case, the server may generate at least one schedule dependent on the account of the at least one guest based on the schedule dependent on the account of the host.

For example, when the guest selects whether to participate in the corresponding schedule, not to attend, or to be undecided, the server may update the participant information of the corresponding guest from participant information included in the corresponding schedule. The server may synchronize the schedule of the host with at least one schedule dependent on at least one guest based on the updated participant information.

If the guest does not input a response to the tentatively registered schedule for a predetermined period of time, the date specified in the tentatively registered schedule has elapsed, or the guest enters not to register the corresponding schedule, the tentatively registered schedule may be deleted. . According to an embodiment, when the guest refuses to participate in the corresponding schedule, the guest's schedule detail screen may indicate that the corresponding schedule has been rejected, and the schedule temporarily registered in the guest's personal calendar may be deleted.

When an event is created that is dependent on the guest's account by the guest choosing to participate in that event, invitations and/or change notifications made by the host to the event are displayed in a predetermined UI (e.g., What's New in the Event View feature) may be notified to the guest through the UI, etc. (140). For example, when a schedule is edited through an interface for editing a schedule dependent on an account of the host, the server may synchronize the edited schedule with at least one schedule dependent on the account of at least one guest.

In addition, the guest may set a reminder for the schedule through the guest's chat room 107 with me ( 150 ). An example of a screen provided to a terminal of a host and/or a guest when a reminder for a schedule is set will be described later with reference to FIG. 10 . According to an embodiment, a reminder for a schedule may be automatically transmitted to a chat room with me without a guest setting.

According to an embodiment, the server may determine whether the schedule creation request occurs through the general chat room, and if it occurs in the general chat room, the server may tag the schedule with identification information of the corresponding chat room. The identification information of the chat room tagged in the schedule can be used in various ways. For example, a function for requesting a chat with a participant of a schedule may be provided, and at this time, the corresponding chat room may be automatically recommended based on identification information of the chat room tagged with the corresponding schedule.

According to an embodiment, even when a schedule creation is requested through a general chat room, at least some of the users participating in the corresponding chat room may not be invited to the corresponding schedule. In other words, access to the schedule may be granted by invitation to the schedule and acceptance of the invitation regardless of the chat room in which the schedule creation is requested.

Hereinafter, terms used in the present specification may be briefly summarized as shown in [Table 1] below.

Here, 'ownership' may refer to the ownership right to subordinate the schedule to one's own calendar and to make changes, and through the host's ownership right for the first schedule created through the schedule creation request and schedule invitation The guest's right to own the generated second schedule may be different.

According to an embodiment, the right to create a schedule may vary depending on the schedule creator and the type of chat room as shown in [Table 2] below.

Classification of chat rooms Write permission chat room with me the user general chat room all participants open chat room All participants (or moderators) corporate chat room the company

Also, according to an embodiment, the host may have editing rights related to all schedules that depend on the host's account, such as editing schedules, deleting schedules, invitations to schedules, and setting reminders, for example. In contrast, a guest may only have some editing rights for events that are dependent on their (guest) account, and does not have invitation rights to events. For example, the guest can edit only the schedule title or description of the schedule, and even if the guest's schedule is edited, it is not synchronized with the host's schedule and other guests' schedules. Although not shown in the figure, the server For example, it is possible to provide a function of migrating a schedule dependent on a chat room in which 5 users participate) to schedules dependent on users participating in a chat room to share a schedule. For example, if a schedule dependent on a chat room already exists, schedules dependent on the accounts of participants may be created based on the schedule. In this case, the participant who created the schedule dependent on the chat room may become the host, and the remaining participants may become the guests.

2 is a flowchart illustrating a method of operating an instant messenger server that provides a schedule service according to an exemplary embodiment. Referring to FIG. 2 , an instant messenger server (hereinafter, 'server') according to an exemplary embodiment generates a schedule dependent on an account of the host in response to a schedule creation request of the host ( 210 ). In this case, the schedule dependent on the host's account may be displayed, for example, as shown in the screen shown in FIG. 3 below.

The server receives an invitation to be invited to the schedule (220). The server may receive information about an invitation target to be invited based on a chat room list of the host's account and/or a friend list of the host's account on the instant messaging service through the terminal of the host. The information about the invitation target may include information about the chat room (eg, the identifier of the chat room, the identifier of the chat room participant, etc.) or the identifier of the individual user.

A process in which the server receives the invitation object will be described with reference to FIG. 4 below, for example. According to an embodiment, an invitation target may be automatically input in the terminal of the host. For example, when the host's schedule creation request is generated through a specific chat room, users participating in the corresponding chat room may be automatically entered as invitation targets. Hosts can edit automatically entered invitees.

The server determines a chat room to share the schedule based on the invitation target (230). The server may provide, for example, a candidate chat room based on participant information in response to a chat request related to the schedule. A method for the server to determine a chat room to share a schedule will be described in detail with reference to FIG. 5 below.

The server receives whether to participate in the schedule from at least one guest included in the invitation target by sharing the schedule in the chat room (240). A method for the server to receive whether to participate in the schedule from the guest will be described in detail with reference to FIG. 6 below.

The server updates participant information included in the schedule based on whether at least one guest participates ( 250 ).

3 is a diagram illustrating a screen of a calendar on which a schedule is displayed, according to an exemplary embodiment. Referring to FIG. 3 , according to an exemplary embodiment, a monthly view screen 310 of a calendar in which schedules dependent on the host's account are displayed and a list view screen in which only a list of schedules included in the monthly view screen 310 is displayed. 330 is shown.

At the top of the monthly view screen 310, for example, the month (July) corresponding to today (July 24, 2018) may be displayed in the form of a calendar. Also, a schedule list corresponding to today or a date selected by the user may be displayed at the bottom of the monthly view screen 310 . On the monthly view screen 310 , a mark such as ● may be displayed under a date having a schedule. For example, if there is no schedule for today or the date selected by the user, a phrase such as "There is no schedule" may be displayed.

The schedule list may include information such as a title of each schedule (eg, 'weekly report preparation', 'platform sector weekly meeting', etc.), start date and time, end date and time, location, and the like. In this case, buttons (eg, an attend button, a non-attendance button, and a tentative button) through which the user can select whether to attend may be displayed in the list of schedules. Also, in the schedule list, profile information including a profile picture 315 of a host of the corresponding schedule may be displayed.

The monthly view screen 310 may include an icon 311 for creating a schedule, an icon 313 for a calendar search, and/or an icon 317 for switching a calendar view mode.

When a user (eg, a host) selects the icon 311 , a writing form (refer to the screen 410 of FIG. 4 ) for creating a schedule may be displayed on the user's terminal. In the writing form, the user can input the title of the schedule and set the start date and time and the end date and time of the schedule. When the user taps a place field included in the creation form, a user interface screen for searching for a place may be provided.

In addition, by selecting the reminder setting item for the schedule included in the filling form, the user can set the reminder time for the schedule, for example, 5 minutes ago, 15 minutes ago, 1 hour ago, 1 day ago, etc. can be set. Reminders may be set for a plurality of time zones.

In addition, the writing form may include an icon (not shown) for repeat setting. By selecting the icon for repeat setting, the user can set the schedule to be repeated every day, week, month, year, etc.

When the user (eg, the host) selects the icon 313 , a calendar search menu may be displayed on the user's terminal. When the user selects the icon 317 , the calendar displayed on the monthly view screen 310 is folded, and only the schedule list can be displayed like the list view screen 330 .

4 is a diagram for explaining a method of receiving an invitation to be invited to a schedule according to an exemplary embodiment. Referring to FIG. 4 , a screen 410 showing a form for creating a schedule by the host, an entry screen 430 for invitation when the host's schedule creation request is generated through the host's calendar, and a schedule creation request by the host An entry screen 450 for an invitation when created through this specific chat room, and a screen 470 on which an input for an invitation is completed are shown.

The host according to an embodiment may input an invitation to be invited to the schedule by selecting the invitation icon 415 included in the screen 410 . In this case, the invitation target may be an individual user or a specific chat room.

For example, when the host's schedule creation request is generated through the host's calendar, the screen 430 may be displayed on the host's terminal. The host may select an invitation target to be invited to the schedule from among the individual users displayed on the screen 430 . When the host's schedule creation request is generated through a specific chat room, a screen 450 may be displayed on the host's terminal. The host may select an invitation target to be invited to a schedule among users participating in the corresponding chat room displayed on the screen 450 . When the host's schedule creation request is generated through a specific chat room as shown in screen 450, the host's terminal can automatically input users participating in the corresponding chat room as invitation targets to be invited to a schedule dependent on the host's account. .

When the selection of the invitation target is completed through the screen 430 and/or the screen 450 , the finally selected invitation target may be displayed as shown in the screen 470 . For example, when the number of invitees is 3 or 5 or more, the number of invitees exceeding 3 or 5 may be displayed with a '+' mark. When '+' is selected, an interface for searching the invitation objects through scrolling may be provided while the invitation objects that have been omitted are displayed. Alternatively, when '+' is selected, a separate interface for displaying invitees at once may be provided.

5 is a diagram for explaining a method of requesting a chat with a participant in a schedule according to an embodiment. Referring to FIG. 5 , a screen 510 for viewing details of a schedule, a screen 530 for requesting a chat with a participant of a schedule, and a screen 550 in which a preview of the schedule is displayed in the form of a message in the chat room are shown.

For example, as shown on the screen 510 , five people are designated as invitees for the schedule, and the host may select the chat icon 515 included on the screen 510 . In response to the chatting request, the server may provide (or recommend) a candidate chat room based on participant information including the host and guests who have accepted the invitation of the schedule as shown in the screen 530 . In this case, the candidate chat rooms may be chat rooms in which five users are participating.

According to one embodiment, the recommendation order of the chat room may be set in various ways. For example, i) a chat room containing only invitees (eg, 5 people) is placed first, or ii) a chat room containing invitees (eg, 5 people) is the most recently sent and received chat room. It can be set such as arranging a chat room, or iii) placing a chat room containing only attendees (eg, people who have indicated attendance among invitees) first.

Alternatively, when the host selects the chat icon 515 included in the screen 510 , the server may create a new chat room based on participant information in response to the chatting request. For example, a new chat room composed of participants of a certain schedule may be created.

6 is a diagram for describing a method of receiving an input of whether to participate in a schedule according to an exemplary embodiment. Referring to FIG. 6 , a screen 610 for viewing details of a schedule, a screen 630 indicating whether to participate in a schedule, and a screen 650 for viewing details of a participant are shown according to an embodiment.

When the user selects the edit button 611 included in the screen 610, an edit menu for editing related to the schedule may be displayed on the user's screen.

According to an embodiment, the allowable range and reflection target of modification of each field of the schedule may be determined as shown in [Table 3] below according to whether the owner of the schedule is a host or a guest.

The host can modify and/or delete all fields in the schedule. The schedule modified and/or deleted by the host may be reflected in the schedule of all participants including the host and guest. For example, when the host cancels the invitation to the schedule for the corresponding guest, the server may notify the corresponding guest of the cancellation of the schedule. If the host edits the event and then saves it, a confirmation pop-up may appear on the host's screen, such as "Editing the event resets the availability response and sends a rescheduling notification. Are you sure you want to edit the event?"

In contrast, the guest can only modify some fields. For example, a guest can edit an event's title, reminder, and description fields. The schedule modified by the guest may be reflected only in the schedule that is dependent on the user's (guest) account. For example, if a guest edits an event and then saves it, a confirmation pop-up like "Edits will only be reflected in my calendar" may appear on the guest's screen.

On the screen 610, buttons (an attend button, a non-attendance button, and/or a tentative button) may be displayed for displaying a response to attend the event to which the user is invited. The user may change a status value (eg, attendance, non-attendance, or tentative) for the attendance response until the schedule ends. In this case, the schedule may be displayed on the calendar regardless of whether the user responds. When the user selects the download icon 613 displayed on the screen 610, a schedule to which the user is invited may be stored in the basic calendar of the user's terminal. Also, when the user selects the delete icon 615 displayed on the screen 610, the schedule to which the user is invited may be deleted. In this case, if the corresponding user is the host, schedule cancellation may be notified to the participants by deletion of the schedule. Also, if the corresponding user is a guest, the corresponding schedule may be removed only from the guest's own calendar by deleting the schedule.

When the user selects the schedule sharing icon 617 displayed on the screen 610, the schedule can be shared in the chat room. The user may share the schedule with uninvited participants by selecting the share schedule icon 617 .

When the user responds to attend on the screen 610 , the selected button interface may be displayed differently from other unselected button interfaces as shown on the screen 630 . According to a response of at least one user included in the invitation target, the number of people who have selected to attend/not attend/can't attend may be displayed as shown in the screen 630 . In this case, the guest who did not respond may be counted as selecting the tentative choice.

When participation is finally determined, the user may check detailed information about the participant through the screen 650 . The screen 650 may display the number of participants and profile information of the participants for each type of participation response. In this case, the add friend button 655 may be displayed together with the participants who are not friends among the participants.

7 is a diagram for describing a process in which a host shares a schedule with participants according to an exemplary embodiment. Referring to FIG. 7 , a process of sharing a schedule by a user X (eg, a host) selecting a schedule sharing icon 715 included in the detailed schedule view screen 710 according to an embodiment is illustrated. As described above, the user X may select a schedule sharing target by selecting the schedule sharing icon 715 ( 720 ). The schedule sharing target may be individual users or chat rooms. When the selection of the sharing target is completed, a certain speech bubble may be transmitted to a chat room (eg, a one-to-one chat room or a group chat room) of the selected sharing target ( 730 ). At this time, when a schedule speech bubble is selected from the terminal of user Y corresponding to the invitation among users of the chat room to which the schedule is shared, a schedule detail screen may be displayed ( 740 ).

In addition, among users of the chat room to which the schedule is shared, an uninvited notification alert such as, for example, "I am a member not invited to the schedule" may be displayed on the terminal of user Z who does not correspond to the invitation target (750). . In this case, the user Z, who does not correspond to the invitation target, may transmit an invitation request to invite the user X who has selected to share the schedule to the schedule. The invitation request of user Z may be displayed as an invitation request notification in news of user X, who is the host of the schedule ( 760 ). According to an embodiment, the invitation request message may be transmitted to a chat room in which the host is participating.

The server may receive an input from the user X whether to accept the invitation request, and update participant information included in the schedule based on whether the user X accepts or not. As the participant information is updated, user Z is confirmed as an invitation request friend, and accordingly, a detailed schedule screen may be displayed on user Z's terminal ( 740 ). When the participant information is updated, the schedules of the host and guest(s) may be synchronized.

8 is a diagram for describing a method of providing at least one schedule corresponding to search-requested participant information, according to an embodiment. Referring to FIG. 8 , a schedule search entry screen 810 , a screen 830 indicating a search page, and a screen 850 indicating a search result are shown.

When the user selects the search icon 815 included in the search entry screen 810 , a search page such as the screen 830 may be provided. In this case, the search page such as the screen 830 may include a search window 831 for inputting a search target such as a title, a place, a memo, an invitation member name, and the like. Also, the search page may include an item 833 of 'find as a friend with you'. In this case, the search as a companion item 833 may perform a function of searching for a schedule including a schedule host and/or a schedule participant.

For example, when receiving a search request based on participant information (participant B, C, D, etc.) from a specific user A, the server responds to the requested participant information among a plurality of schedules dependent on the specific user's account At least one schedule may be extracted and provided. If the last 5 schedules corresponding to participants B, C, and D exist, the server may provide the 5 schedules as a search result. According to an embodiment, when each schedule is distinguished by color, the server may search for the schedule by filtering according to a designated color.

The final schedule search result may be provided in the form of a list divided by month as shown in the screen 850 . In this case, the at least one schedule corresponding to the search-requested participant information may include, for example, information such as month, date, date, day, title, time, and place. The searched schedules may be displayed sequentially or in reverse order based on the schedule closest to today.

9 is a diagram for describing a method of performing a schedule preview according to an exemplary embodiment. Referring to FIG. 9 , a schedule preview screen 910 displayed in a chat room with me and a schedule preview screen 930 displayed in a general chat room are illustrated, according to an exemplary embodiment.

For example, when a user participating in a specific chat room requests a schedule preview, the server may provide schedule preview screens 910 and 930 by accessing a schedule dependent on the user's account. In this case, the server may provide the user with an interface for searching for a schedule dependent on the corresponding user's account.

A function for previewing the user's latest schedule (for example, today's schedule) is provided on the schedule preview screen 910 , and the user's schedule is quickly navigated (for example, on the schedule preview screen 930 ) , search by date) may be provided.

Alternatively, when a preview of the schedule is requested through the general chat room, schedules related to the chat room among the schedules subordinate to the user (eg, schedules in which the corresponding chat rooms are tagged, schedules related to members participating in the corresponding chat rooms) etc.) may be provided with a schedule preview view that preferentially displays the schedule compared to other schedules.

10 is a diagram illustrating a schedule reminder screen according to an exemplary embodiment. Referring to FIG. 10 , reminder screens 1010 and 1030 displayed in various forms in a chat room are shown.

A user according to an embodiment may set a reminder for a schedule through a chat room with me and/or a general chat room. When a reminder for a schedule is set, the user's terminal contains, for example, a reminder time notice ("There is a schedule in 15 minutes"), schedule start month/day, schedule title, schedule start to end time, location , a reminder screen 1010 including reminder information such as a button to enter the detailed schedule view screen may be displayed.

According to an embodiment, the schedule may be displayed as shown in the reminder screen 1030 after being divided by type of schedule, such as a company schedule and a personal schedule.

Although not shown in the drawings, the instant messenger server according to an embodiment includes a processor and a communication interface. The instant messenger server may further include a memory. The processor, communication interface, and memory may be coupled to each other via a communication bus. The instant messenger server may be, for example, a cloud server or a user device performing the same or similar function.

The processor may perform at least one method described above with reference to FIGS. 1 to 10 or an algorithm corresponding to the at least one method. The processor may execute a program and control the instant messenger server. The program code executed by the processor may be stored in the memory.

The embodiments described above may be implemented by a hardware component, a software component, and/or a combination of a hardware component and a software component. The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium. The hardware display device described above may be configured to operate as one or more software modules to perform the input of an embodiment, and vice versa.

As described above, although the embodiments have been described with reference to the limited drawings, various modifications and variations are possible from the above description by those of ordinary skill in the art. For example, the described techniques are performed in an order different from the described method, and/or the described components of the system, structure, display device, circuit, etc. are combined or combined in a different form than the described method, or other configuration. Substituted or substituted for elements or equivalents may achieve appropriate results. Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

Claims (20)

A method of operating an instant messenger server that provides a schedule service, the method comprising:
generating a first schedule dependent on the host's account for an instant messaging service in response to a host's schedule creation request;
receiving an invitation to be invited to the first schedule based on at least one of a chat room list of the host's account and a friend list of the host's account;
synchronizing a first schedule dependent on an account of the host and a second schedule dependent on an account of at least one guest belonging to the invitation target; and
Recommending a chat room in response to a chat request related to the first schedule
including,
The step of creating the first schedule includes:
determining whether the schedule creation request has occurred through a general chat room; and
Based on the determination result, tagging the identification information of the general chat room to the first schedule
including,
The step of recommending the chat room is
When the identification information of the general chat room is tagged in the first schedule, recommending a first chat room based on the tagged identification information
containing,
How an instant messenger server works. According to claim 1,
The schedule dependent on the user's account for the instant messaging service includes a schedule registered in a user-level calendar,
The user-unit calendar includes a plurality of schedules registered through a plurality of chat rooms in which the user participated,
How an instant messenger server works. According to claim 1,
Receiving an invitation to be invited to the first schedule comprises:
determining a second chat room to share the first schedule based on the invitation target;
receiving, by sharing the first schedule with the second chat room, whether to participate in the first schedule, from a user belonging to the invitation target among at least one user participating in the second chat room; and
By sharing the first schedule with the second chat room, an invitation request for the first schedule is received from a user who does not belong to the invitation target among at least one user participating in the second chat room, and transmitted to the terminal of the host step to do
The method of operation of the instant messenger server further comprising a. The method of claim 1,
When the host's schedule creation request is generated through a specific chat room, users participating in the corresponding chat room are automatically entered as the invitation target,
How an instant messenger server works. According to claim 1,
providing a candidate chat room in which the at least one guest is participating in response to the chat request related to the first schedule;
providing, in response to a chatting request related to the first schedule, a candidate chat room in which an attendee of the at least one guest is participating;
in response to the chat request related to the first schedule, recommending a new chat room including the at least one guest; and
Recommending a new chat room including an attendee among the at least one guest in response to the chat request related to the first schedule
A method of operating an instant messenger server, further comprising at least one of: According to claim 1,
when the first schedule dependent on the account of the host is changed, the second schedule dependent on the account of the at least one guest is synchronized with the changed first schedule;
when the second schedule dependent on the account of the at least one guest is changed, the first schedule dependent on the host's account is not synchronized with the changed second schedule;
How an instant messenger server works. According to claim 1,
providing an interface for editing a first schedule dependent on the host's account; and
synchronizing the edited first schedule with a second schedule dependent on the accounts of the at least one guest as the first schedule dependent on the host's account is edited;
The method of operation of the instant messenger server further comprising a. According to claim 1,
in response to a schedule preview request of a user participating in a specific chat room, accessing a schedule dependent on an account of the corresponding user; and
providing an interface for navigating schedules dependent on the corresponding user's account;
The method of operation of the instant messenger server further comprising a. According to claim 1,
In response to the schedule sharing request of the host, sharing the shared first schedule to the sharing requested chat room
The method of operation of the instant messenger server further comprising a. 10. The method of claim 9,
receiving an invitation request from a user who does not correspond to the invitation target among users of the chat room in which the first schedule is shared;
receiving from the host of the first schedule whether to accept the invitation request; and
updating participant information included in the first schedule based on whether the host accepts or not
The method of operation of the instant messenger server further comprising a. According to claim 1,
A step of migrating a schedule dependent on a specific chat room to schedules dependent on users participating in the corresponding chat room
The method of operation of the instant messenger server further comprising a. According to claim 1,
receiving, from a specific user, a search request based on participant information;
extracting at least one schedule corresponding to the search-requested participant information from among a plurality of schedules dependent on the account of the specific user; and
providing the extracted at least one schedule
Method of operation of an instant messenger server further comprising According to claim 1,
receiving a schedule preview request through the chat room from a user participating in the chat room of the instant messaging service; and
providing a view for preferentially displaying a schedule associated with the chat room among schedules dependent on the user's account
The method of operation of the instant messenger server further comprising a. A method of operating an instant messenger application that provides a schedule service installed in a terminal, the method comprising:
sending a schedule creation request to a server for creating a first schedule dependent on the user's account for the instant messaging service;
receiving an invitation to be invited to the first schedule based on at least one of a chat room list of the user's account and a friend list of the user's account;
receiving, from the server, participant information updated based on whether at least one guest included in the invitation object participates; and
In response to the chat request related to the first schedule, displaying a list of recommended chat rooms
including,
The step of creating the first schedule includes:
When the schedule creation request occurs through the general chat room, transmitting information for tagging the identification information of the general chat room to the first schedule to the server
including,
The list of recommended chat rooms is
When the identification information of the general chat room is tagged in the first schedule, including a first chat room based on the tagged identification information,
How an instant messenger application works. 15. The method of claim 14,
Displaying a plurality of schedules registered through a plurality of chat rooms in which the user participated through a user-level calendar
further comprising,
How an instant messenger application works. 15. The method of claim 14,
displaying a candidate chat room in which an invitation included in the participant information is participating in response to a chatting request related to the first schedule;
in response to the chatting request related to the first schedule, displaying a candidate chat room in which the participant is participating from among the invitees included in the participant information;
displaying a new chat room including an invitation target included in the participant information in response to a chatting request related to the first schedule; and
In response to the chat request related to the first schedule, displaying a new chat room including an attendee from among the invitees included in the participant information
The method of operating an instant messenger application, further comprising at least one of. 15. The method of claim 14,
a first schedule dependent on the user's account and a second schedule dependent on the account of at least one guest belonging to the invitation target are synchronized;
when the first schedule dependent on the user's account is changed, the second schedule dependent on the account of the at least one guest is synchronized with the changed first schedule;
when the second schedule dependent on the account of the at least one guest is changed, the first schedule dependent on the user's account is not synchronized with the changed second schedule;
How an instant messenger application works. 15. The method of claim 14,
transmitting a request to share the first schedule to the server through the instant messaging service;
receiving an invitation request from a user who does not correspond to the invitation target among users of the chat room in which the first schedule is shared;
receiving an input of whether to accept the invitation request; and
Transmitting information for updating participant information included in the first schedule to the server based on the acceptance or not
A method of operating an instant messenger application further comprising a. 15. The method of claim 14,
receiving a schedule preview request through a chat room in which the user participated; and
Displaying a view that preferentially displays the schedule associated with the chat room among schedules dependent on the user's account
A method of operating an instant messenger application further comprising a. A computer program stored on a medium in combination with hardware to execute the method of any one of claims 1 to 19.

Images