Event management method, computer program and computing device

Abstract

To provide a computer program for executing an event management method, an event management method, and a computing device.SOLUTION: A computer program stored in a computer-readable recording medium for executing an event management method on a computer includes the steps of: generating an event-associated message for participation in a predetermined event based on an input of a host user; transmitting the event-associated message to a guest user belonging to a first chat room through the first chat room, to which the host user belongs; transmitting a remittance request message to the guest user based on an input of the guest user responding to the event-associated message; and determining whether remittance requested by the remittance request message has been processed.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an event management method performed by a computing device, a computer program, and a computing device. Specifically, the present invention relates to an event management method performed by a user device of a host user (hereinafter referred to as a "host user device") and / or a server, a computer program stored on a computer-readable recording medium for causing a computing device to execute the event management method, and a computing device that executes the event management method. [Background technology]

[0002] Recently, the use of instant messenger applications as a means of communication between users has been increasing. Instant messenger applications support communication through group chat rooms, which are groups of two or more users. Group chat rooms are sometimes used as a means of announcing various events (such as impromptu meet-ups, regular meetings, seminars, etc.) to the multiple users who belong to the chat room.

[0003] If a specific event requires a participation fee (membership fee), only users who have paid the fee can be allowed to participate in the event. Therefore, the user who hosts the event (host user) needs to confirm whether users who have applied to participate in the event (guest users) have paid the fee. This requires efficient management of the remittance of membership fees for events announced via instant messenger applications. Summary of the Invention [Problem to be solved by the invention]

[0004] The present invention aims to provide an event management method for creating an event and managing membership fees by a user device and / or a server.

[0005] Another object of the present invention is to provide a method for participating in an event, in which a user applies to participate in the event and pays the participation fee via a messenger application installed on the user device.

[0006] Another object of the present invention is to provide a computing device for carrying out the event management method or event participation method according to the present invention.

[0007] Another object of the present invention is to provide a program stored on a computer-readable recording medium for executing the event management method or event participation method according to the present invention.

[0008] The technical problems of the present invention are not limited to the above-mentioned technical problems, and other technical problems not mentioned above will be clearly understood by a person having ordinary knowledge in the technical field to which the present disclosure pertains (hereinafter referred to as "a person skilled in the art") from the following description. [Means for solving the problem]

[0009] According to one aspect of the present invention, there is provided an event management method, comprising: a computer program stored on a computer-readable recording medium for execution by a computer; the method including the steps of: generating an event linkage message regarding participation in a predetermined event based on input from a host user; transmitting the event linkage message to a guest user device of a guest user belonging to a first chat room via the first chat room to which the host user belongs; transmitting a remittance request message to the guest user device based on the guest user's input regarding the event linkage message; and confirming whether the remittance requested by the remittance request message has been processed by the guest user device.

[0010] In the computer program according to the present invention, the event linkage message or the remittance request message may include information regarding a cost for participating in the predetermined event or a remittance deadline.

[0011] In the computer program according to the present invention, the remittance request message may be transmitted to the guest user device via a second chat room to which the guest user belongs, and the second chat room may be different from the first chat room.

[0012] In the computer program according to the present invention, the step of transmitting the remittance request message may include the steps of generating a second chat room to which the host user and the guest user belong, and transmitting the remittance request message via the second chat room.

[0013] The computer program according to the present invention may further include transmitting a subsequent message to the guest user device based on whether the remittance has been processed.

[0014] In the computer program according to the present invention, if the remittance has not been processed, the subsequent message may be a reminder message.

[0015] In the computer program according to the present invention, if the remittance is processed, the subsequent message may be a remittance confirmation message.

[0016] In the computer program according to the present invention, the remittance confirmation message may include approval information for approving participation in the predetermined event.

[0017] The computer program according to the present invention may provide the host user device with information regarding whether the remittance requested by the remittance request message has been processed.

[0018] According to another aspect of the present invention, an event management method performed by a computing device including at least one processor includes the steps of generating an event linkage message regarding participation in a predetermined event based on input from a host user; transmitting the event linkage message to a guest user device of a guest user belonging to a first chat room to which the host user belongs via the first chat room to which the host user belongs; transmitting a money transfer request message to the guest user device based on the guest user's input regarding the event linkage message; and confirming whether the money transfer requested by the money transfer request message has been processed by the guest user device.

[0019] According to another aspect of the present invention, a computing device includes at least one processor, which generates an event linkage message regarding participation in a predetermined event based on input from a host user, transmits the event linkage message to a guest user device of a guest user belonging to a first chat room to which the host user belongs via the first chat room to which the host user belongs, transmits a money transfer request message to the guest user device based on the guest user's input regarding the event linkage message, and can confirm whether the money transfer requested by the money transfer request message has been processed by the guest user device.

[0020] In the computing device according to the present invention, the event linkage message or the remittance request message may include information regarding a cost for participating in the predetermined event or a remittance deadline.

[0021] In the computing device according to the present invention, the remittance request message may be transmitted to the guest user device via a second chat room to which the guest user belongs, the second chat room being different from the first chat room.

[0022] In the computing device according to the present invention, a second chat room may be created to which the host user and the guest user belong, and the remittance request message may be transmitted through the second chat room.

[0023] In a computing apparatus according to the present invention, the processor may transmit a subsequent message to the guest user device based on whether the remittance was processed.

[0024] In a computing device according to the present invention, if the remittance has not been processed, the subsequent message may be a reminder message.

[0025] In a computing device according to the present invention, if the remittance has been processed, the subsequent message may be a remittance confirmation message.

[0026] In a computing device according to the present invention, the remittance confirmation message may include authorization information authorizing participation in the predetermined event.

[0027] A computing apparatus according to the present invention may provide information to a host user device regarding whether the remittance requested by the remittance request message has been processed.

[0028] According to another aspect of the present invention, a method for participating in an event via a messenger application installed on a guest user device includes the steps of receiving an event linking message regarding participation in a predetermined event transmitted from the host user to the guest user via a first chat room to which the host user and the guest user belong; receiving an input from the guest user regarding the event linking message; receiving a remittance request message transmitted to the guest user based on the input from the guest user; and receiving a subsequent message transmitted to the guest user based on whether the remittance requested by the remittance request message has been processed.

[0029] In the event participation method according to the present invention, the event linkage message or the remittance request message may include information regarding a cost for participating in the predetermined event or a remittance deadline.

[0030] In the event participation method according to the present invention, the remittance request message may be received via a second chat room to which the guest user belongs, and the second chat room may be different from the first chat room.

[0031] In the event participation method according to the present invention, the remittance request message may be received via a second chat room created to include the host user and the guest user.

[0032] In the event participation method according to the present invention, the remittance request message may be received via the first chat room.

[0033] In the event participation method according to the present invention, if the remittance has not been processed, the subsequent message may be a reminder message.

[0034] In the event participation method according to the present invention, if the remittance is processed, the subsequent message may be a remittance confirmation message.

[0035] In the event participation method according to the present invention, the remittance confirmation message may include approval information for approving participation in the predetermined event.

[0036] According to another aspect of the present invention, a guest user device includes at least one processor that performs an event participation method via a messenger application, wherein the processor can perform the following steps: receiving an event-linked message regarding participation in a predetermined event transmitted from the host user to the guest user via a first chat room to which the host user and the guest user belong; receiving input from the guest user regarding the event-linked message; receiving a remittance request message transmitted to the guest user based on the guest user's input; and receiving a subsequent message sent to the guest user based on whether the remittance requested by the remittance request message has been processed.

[0037] A computer program stored on a computer-readable recording medium according to another aspect of the present invention may be a computer program for executing an event participation method according to the present invention.

[0038] The above briefly summarized features of the present disclosure are merely exemplary embodiments of the following detailed description of the present disclosure and are not intended to limit the scope of the present disclosure. [Effects of the Invention]

[0039] According to the present invention, there is provided an event management method for generating an event and managing membership fees by a user device and / or a server.

[0040] Furthermore, the present invention provides a method for participating in an event, in which a user applies to participate in the event and pays the participation fee through a messenger application installed on the user device.

[0041] The present invention also provides a computing device for performing the event management method or event participation method according to the present invention.

[0042] According to the present invention, there can also be provided a program stored on a computer-readable recording medium for executing the event management method or event participation method according to the present invention.

[0043] The effects obtained by the present disclosure are not limited to those described above, and other effects not described above will be clearly understood by those skilled in the art from the following description. [Brief explanation of the drawings]

[0044] [Figure 1] 1 illustrates a system in which an event management or participation method according to an embodiment of the present invention is performed; [Figure 2] 1 is a block diagram illustrating an example of a user device and a server performing an event management method or event participation method according to an embodiment of the present invention. [Figure 3] 1 is a diagram illustrating an event management method according to an embodiment of the present invention; [Figure 4] 1 is a diagram illustrating a method for participating in an event according to an embodiment of the present invention; [Figure 5] 10A and 10B are diagrams illustrating examples of an event linkage message and a remittance request message according to the present invention. [Figure 6] 10A and 10B are diagrams illustrating an example of a reminder message and a remittance confirmation message transmitted according to an embodiment of the present invention. [Figure 7] 10 is a diagram illustrating an example of a list of guest users that can be provided to a host user by the event management method of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0045] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present disclosure will be described in detail below with reference to the accompanying drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be embodied in various different forms and is not limited to the embodiments described herein.

[0046] In describing the embodiments of the present disclosure, if it is determined that a specific description of a known configuration or function may obscure the gist of the present disclosure, the detailed description thereof will be omitted. In addition, in the drawings, parts that are not related to the description of the present disclosure will be omitted, and similar parts will be designated by similar reference numerals.

[0047] In this disclosure, when a component is referred to as being "coupled," "coupled," or "connected" to another component, this includes not only a direct connection, but also an indirect connection where another component is interposed between them. Furthermore, when a component is referred to as "including" or "having" another component, this does not mean that the other component is excluded, but that the other component can further be included, unless otherwise specified.

[0048] In this disclosure, terms such as "first" and "second" are used only to distinguish one component from another component, and do not limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0049] In this disclosure, components that are distinguished from one another are used to clearly describe the characteristics of each component and do not necessarily mean that the components are separate. In other words, multiple components may be integrated into a single hardware or software unit, or a single component may be distributed into multiple hardware or software units. Therefore, unless otherwise specified, such integrated or distributed embodiments are also included within the scope of this disclosure.

[0050] In this disclosure, the components described in various embodiments are not necessarily essential components, and some of them may be optional components. Therefore, an embodiment consisting of a subset of the components described in one embodiment is also within the scope of this disclosure. Furthermore, an embodiment including other components in addition to the components described in various embodiments is also within the scope of this disclosure.

[0051] In addition, in this specification, the term "network" may be a concept that includes both wired and wireless networks. In this case, the term "network" may refer to a communication network through which data is exchanged between devices and systems, and between devices, and is not limited to a specific network.

[0052] Furthermore, in this specification, the term "device" may refer to not only mobile devices such as smartphones, tablet PCs, wearable devices, and head-mounted displays (HMDs), but also fixed devices such as PCs and home appliances with display capabilities. For example, the device may be a computing device operable on a server, a vehicle, or an Internet of Things (IoT) device. In other words, in this specification, the term "device" may refer to a device capable of executing the method according to the present invention, and is not limited to a specific type.

[0053] System and device configuration FIG. 1 is a diagram showing a system in which an event management method or an event participation method according to an embodiment of the present invention is performed.

[0054] A system according to the present invention may include one or more user devices 101 , 102 , 103 and a server 110 connected via a network 104 .

[0055] Each of the user devices 101, 102, 103, which may also be referred to as a client or user terminal, can connect to a server 110 via a network 104 to send and receive data to and from other user devices or servers.

[0056] The event management method or event participation method of the present invention may be performed using an instant messaging service. A client module for using the instant messaging service may be installed in each of the user devices 101, 102, and 103. Also, a server module for supporting the instant messaging service may be installed in the server 110. In this disclosure, a messenger application installed on the user device may refer to the client module installed on each of the user devices 101, 102, and 103 for using the instant messaging service.

[0057] The server 110 may provide a service such as an instant messenger application. A user who uses the service can connect to the server 110 that provides the service by inputting predetermined connection information (ID and password) through a user device. The server 110 can identify the connected user using the connection method input from the user device. The server 110 can also collect, accumulate, store, and query information about the identified user, or support data transmission and reception between the identified users.

[0058] FIG. 2 is a block diagram illustrating a user device and a server that perform an event management method or an event participation method according to an embodiment of the present invention.

[0059] 2(a), the user device 200 may include a processor 210, a memory 220, a transceiver 230, an input unit 240, and an output unit 250. The user device 200 may further include other components related to the operation and function of the device, and is not limited to the above-described embodiments.

[0060] The processor 210 may control the operations of other components within the user device 200. For example, the processor 210 may process information acquired via the input unit 240 and the transceiver unit 230. The processor 210 may also read and process information stored in the memory 220. The processor 210 may output the processed information via the output unit 250, store it in the memory 220, or transmit it to the outside via the transceiver unit 230.

[0061] For example, the processor 210 may receive all information related to an event, such as event creation information, event participation application information, event participation fee remittance information, and event participation approval information, via the transceiver 230 or the input unit 240, or may read the information from the memory 220. After processing the information related to the event, the processor 210 may store the processed information in the memory 220, transmit the processed information to the outside via the transceiver 230, or output the processed information via the output unit 250. The memory 220 may store information received from the server 110 or another user device via the transceiver 230, or information acquired from outside the user device, such as information acquired via the input unit 240 of the user device. The memory 220 may also store information generated within the user device 200. For example, information generated by performing an event management method or an event participation method according to the present invention may be stored in the memory 220. For example, the memory 220 may include a database.

[0062] The transceiver 230 can exchange data with the server 110 or other user devices via a network. The transceiver 230 can include any type of wired or wireless communication module capable of communicating with the outside.

[0063] The input unit 240 may include input means implemented by various sensors, mechanical buttons, etc. provided in the user device 200. The user device 200 may include, for example, input means using a pressure detection sensor, an electrostatic touch sensor, etc. (e.g., a virtual keyboard displayed on a touch screen), mechanical buttons, etc. as the input unit 240. The user device 200 may acquire information detected by the sensors or input from the mechanical buttons as input information.

[0064] The output unit 250 may output information acquired or received by the user device 200, information processed by the user device 200, etc. to the outside. The output unit 250 may include, for example, a display that outputs visual information. Referring to FIG. 2(b), the server 260 may include a processor 280, a memory 270, and a transceiver 290. The server 260 may further include other components related to the operation of the server or system and is not limited to the above-described embodiments.

[0065] The processor 280 may control the operations of other components within the server 260. For example, the processor 280 may process information acquired via the transceiver 290. The processor 280 may also read and process information stored in the memory 270. The processor 280 may store the processed information in the memory 270 or transmit it to the outside via the transceiver 290.

[0066] For example, the processor 280 may receive all information related to an event, such as event creation information, event participation application information, event participation fee remittance information, and event participation approval information, via the transceiver 290 or may read it from the memory 270. After processing the information related to the event, the processor 280 may store the processed information in the memory 270 or transmit it to the outside via the transceiver 290.

[0067] The memory 270 may store information received from the outside via the transceiver 290. The memory 270 may also store information generated within the server 260. For example, information generated by performing an event management method or an event participation method according to the present invention may be stored in the memory 270. For example, the memory 270 may include a database.

[0068] The transceiver 290 can exchange data with a user device or other server connected to the network, and can include any type of wired or wireless communication module capable of communicating with the outside.

[0069] The user devices and / or servers of the present disclosure may be examples of computing devices or apparatuses.

[0070] Event Management Methods In this disclosure, a host user refers to a user who creates, announces, and manages an event, and a guest user refers to a user who is eligible to participate in an announced event.

[0071] An event management method according to one embodiment of the present invention may be performed via a messenger application installed on a host user device.

[0072] FIG. 3 is a diagram illustrating an event management method according to an embodiment of the present invention.

[0073] An event management method according to an embodiment of the present invention may include an event-linked message generation step (S310), an event-linked message transmission step (S320), a remittance request message transmission step (S330), a remittance completion confirmation step (S340), and / or a subsequent message transmission step (S350).

[0074] According to the event management method of the present invention, an event-linked message regarding participation in a predetermined event can be generated based on input from a host user (S310).

[0075] To generate an event, the host user may execute, for example, an event generation function of a messenger application installed on the host user device or a function provided in an individual chat room of the messenger application. When event generation starts, the host user device may receive input of information about the event to be generated from the host user via input unit 240. Once the input of the event information is complete, processor 210 of the user device may generate an event-linked message based on the input information.

[0076] FIG. 5 is a diagram showing an example of an event linkage message and a remittance request message according to the present invention.

[0077] The chat window 510 on the left side of FIG. 5 is an example of a chat window on the host user side for generating an event. For example, as shown in the chat window 510 on the left side of FIG. 5, the host user can execute an event generation function provided in a messenger application or an individual chat room and then input event-related information 511. The event-related information may include, for example, the name, date, location, fee, and due date of the event (meeting). After inputting all the event-related information, the host user can instruct the generation of an event-linked message by, for example, clicking a button such as "Meeting Announcement" shown in FIG. 5. Upon receiving the host user's input instructing the generation of an event-linked message, the processor 210 of the user device can generate an event-linked message based on the event-related information input by the host user.

[0078] The event link message generated in step S310 may be transmitted to guest users belonging to the first chat room via the first chat room, where the first chat room may be a chat room in which a host user and one or more guest users participate.

[0079] The processor 210 of the host user device can transmit the generated event linkage message to other user devices (guest user devices) connected to the network via the transceiver 230.

[0080] 5 is an example of a chat window on the guest user side that has received an event-linked message 521. As shown in FIG. 5, the transmitted event-linked message 521 is displayed in the chat window 520 on the guest user side, thereby notifying the guest users belonging to the first chat room.

[0081] The event-linked message 521 may include information about the event entered by the host user. The event-linked message 521 is also a means for receiving input of the guest user's intention to participate, and may include, for example, an "Apply to Participate" button. However, the event-linked message 521 is not limited to this, and may include a link related to applying to participate or a guide regarding applying to participate instead of the "Apply to Participate" button.

[0082] As shown in FIG. 5, when an event-linked message 521 is provided to a guest user, an input regarding participation in the event can be received from the guest user. For example, a guest user who wishes to participate in the event can input their intention to participate by clicking the "Apply to Participate" button in the event-linked message 521. If a participation application-related link is provided instead of the "Apply to Participate" button, the guest user can click the link and input their intention to participate by following the predetermined procedure required by the site connected to the link. Alternatively, as shown by reference numeral 522 in FIG. 5, the guest user can input their intention to participate in the event by using a reply (comment) function to the event-linked message 521. The method for inputting their intention to participate in the event announced by the event-linked message 521 is not limited to the above example, and various methods can be used to input their intention to participate.

[0083] When a guest user inputs their intention to participate in a particular event, information about the event and / or information about the guest user can be transmitted to the host user who created the event.

[0084] If the guest user provides input in response to the transmitted event link message, a message requesting the guest user to remit money, i.e., a remittance request message, can be transmitted based on the input (S330). At this time, the guest user's input can include an intention to participate in the event.

[0085] The processor 210 of the host user device may receive information about the guest user who has input their intention to participate in the event and / or information about the event via the transceiver 230. The processor 210 may generate a remittance request message based on the information about the event. The remittance request message may be, for example, a message displaying the event participation fee and a deadline for payment of the fee, and requesting that the fee be remitted by the deadline.

[0086] The remittance request message can be sent to guest users who have expressed their intention to participate in the event. At this time, the received information about the guest users can be used. The remittance request message can be displayed in the chat room of the guest users who have expressed their intention to participate, thereby encouraging them to remit the membership fee.

[0087] The chat window 530 on the right side of Figure 5 is an example of a chat window on the guest user's side displaying a transmitted remittance request message 531. As shown in Figure 5, the remittance request message 531 may include information about the event and may include content encouraging the remittance of the membership fee. The remittance request message 531 may also include information about the account to which the remittance is to be sent. If a remittance and payment service is available via the messenger application, the remittance request message 531 may include a "Pay" button or link to perform the remittance service.

[0088] The remittance request message 531 may be transmitted through a second chat room different from the first chat room through which the event-linked message 521 is transmitted. For example, the first chat room through which the event-linked message 521 is transmitted may include both guest users who will be participating in the event and those who will not. If the remittance request message 531 were transmitted through the first chat room through which the event-linked message 521 was transmitted, it would be inappropriate because it would require even guest users who will not be participating in the event to remit their membership fees. Furthermore, even if communication through the first chat room is active and the transmitted remittance request message 531 is displayed in the chat window for a short time, it is also inappropriate to transmit the remittance request message 531 through the first chat room. For example, for the reasons described above, the remittance request message 531 may be transmitted through a second chat room different from the first chat room through which the event-linked message 521 is transmitted.

[0089] The second chat room to which the remittance request message 531 is transmitted may be an existing chat room in which a guest user who has expressed an intention to participate in the event is participating. Alternatively, the processor 210 of the host user device or the guest user device may create a second chat room including the guest user who has expressed an intention to participate in the event, and transmit the remittance request message 531 through the created second chat room. In this case, the processor 210 of the host user device may use the received information about the guest user to identify the guest user who has expressed an intention to participate in the event. The second chat room may be a chat room including both the guest user and the host user. Alternatively, for example, the second chat room may include a plurality of guest users who have expressed an intention to participate in the event and a host user.

[0090] Alternatively, the remittance request message 531 may be transmitted through the first chat room to which the event-linked message 521 was transmitted. As described above, if there is no need to transmit the remittance request message 531 and the event-linked message 521 through different chat rooms, the remittance request message 531 and the event-linked message 521 may be transmitted through the same chat room. For example, if the number of guest users participating in the first chat room is less than a certain number or is within a certain range on the social graph, or if the remittance request message 531 can be constantly displayed in the chat window separately from the chat room communication (for example, if the remittance request message 531 is fixedly displayed at the top of the chat window when using a notification function provided by a messenger application), the event-linked message 521 and the remittance request message 531 may be transmitted through the same chat room.

[0091] Whether the event-linked message 521 and the remittance request message 531 are transmitted through the same chat room or through different chat rooms may be preset or may be set by the host user. Alternatively, whether the same chat room or different chat rooms is used may be determined depending on the characteristics of the chat room. For example, in the case of an open chat room with no restrictions on chat room participation qualifications, it may be determined that the event-linked message 521 and the remittance request message 531 are transmitted through different chat rooms. Alternatively, in the case of a group chat room with restrictions on participation qualifications or determined to be likely to be shared only by a small number of users, such as an alumni association, it may be determined that the event-linked message 521 and the remittance request message 531 are transmitted through the same chat room. Alternatively, whether the event-linked message 521 and the remittance request message 531 are transmitted through the same chat room or different chat rooms may be determined based on a combination of two or more of the above embodiments.

[0092] The guest user who receives the remittance request message 531 can process the requested remittance, for example, by using a remittance and payment service supported by the messenger application, or by processing the remittance through a banking application separate from the messenger application.

[0093] For example, a guest user can execute a remittance and payment service supported by the messenger application and process the remittance using the service by clicking the "Pay" button included in the remittance request message 531. Also, even if information such as an account number is not displayed in the remittance request message 531, clicking the "Pay" button included in the remittance request message 531 can automatically specify the account number linked to the remittance request message 531, and remittance to the linked account number can be performed.

[0094] The processor 210 of the host user device may check whether the remittance requested by the transmitted remittance request message has been processed (S340).

[0095] When a remittance is processed using a remittance and payment service supported by a messenger application, whether the requested remittance has been processed can be confirmed by transmitting and receiving data between the messenger application and the remittance and payment service.

[0096] When a remittance is processed using a banking application separate from the messenger application, the processor may check information regarding whether the requested remittance has been processed based on information obtained through the guest user's operation, which may be, for example, remittance processing information generated by the banking application.

[0097] Alternatively, the processor 210 of the host user device can continuously monitor the account to which the money is being transferred, and if a membership fee is transferred to that account, identify the guest user who transferred the membership fee, thereby confirming whether a transfer transaction has been made by the guest user.

[0098] The processor 210 of the host user device may check whether the remittance requested by the remittance request message has been processed, and then transmit a subsequent message to the guest user based on the processing (S350).

[0099] The confirmation of whether the remittance has been processed is not limited to the above method, and various other methods can be used. For example, the host user can confirm whether the remittance has been processed by receiving the account history associated with the event-linked message entered when the event-linked message was generated. Alternatively, the host user can confirm whether the remittance has been processed by analyzing a remittance-related message received from a mobile banking official account (OA) via a messenger. If the remittance has not been processed by the guest user device in response to the remittance request message, the processor 210 of the host user device can generate a reminder message as a subsequent message and transmit the reminder message to the guest user device for which the remittance has not been processed in response to the remittance request message. If the remittance has been processed by the guest user device in response to the remittance request message, the processor 210 of the host user device can generate a remittance confirmation message as a subsequent message and transmit the remittance confirmation message to the guest user device for which the remittance has been processed in response to the remittance request message.

[0100] FIG. 6 is a diagram illustrating an example of a reminder message and a remittance confirmation message transmitted according to an embodiment of the present invention.

[0101] For example, as shown in the chat window 610 on the left side of Figure 6, the reminder message 611 can be transmitted by resending the remittance request message to a guest user whose remittance in response to the remittance request message has not been processed. The reminder message 611 can be transmitted through the same chat room as the remittance request message 531 was transmitted.

[0102] However, without being limited to the above example, the reminder message 611 may be transmitted via a chat room different from the chat room in which the remittance request message 531 was transmitted, or a separate chat room may be created for transmitting the reminder message 611.

[0103] The format of the reminder message 611 is not limited to the example shown in FIG. 6, and any type of information that reminds a user to pay the membership fee for a particular event can be included in the reminder message according to the present invention.

[0104] As shown in FIG. 6, part or all of the reminder message 611 may be the same as the remittance request message 531, and the description of the same content or function is the same as the description of the remittance request message 531, so it will be omitted below.

[0105] Also, for example, as shown in the chat window 620 on the right side of Figure 6, a remittance confirmation message 621 can be sent to the guest user whose remittance has been processed. The remittance confirmation message 621 can be sent through the same chat room as the remittance request message 531 was sent in.

[0106] However, without being limited to the above example, the remittance confirmation message 621 may be transmitted via a chat room different from the chat room in which the remittance request message 531 was transmitted, or a separate chat room may be created for transmitting the remittance confirmation message 621.

[0107] The format of the remittance confirmation message 621 is not limited to the example shown in FIG. 6, and any type of information that confirms that the fee for a particular event has been paid may be included in the remittance confirmation message 621 according to the present invention.

[0108] As shown in FIG. 6, the remittance confirmation message 621 may include brief information about the linked event and information confirming that the remittance of the event fee has been paid. The remittance confirmation message 621 may also include approval information that approves participation in the event. For example, the remittance confirmation message 621 may include a QR code (registered trademark) as the approval information. The QR code included in the remittance confirmation message 621 may be used to confirm information about the event or to check authorization to enter the event venue.

[0109] As described with reference to Figures 3, 5, and 6, a host user can create an event and efficiently manage the payment of the event participation fee. Furthermore, according to the present invention, the host user can receive information regarding whether the remittance requested by the remittance request message has been processed. For example, the host user can efficiently manage whether the remittance process has been completed by managing a list of guest users who have expressed their intention to participate in a particular event.

[0110] FIG. 7 is a diagram illustrating a list of guest users that can be provided to a host user by the event management method of the present invention.

[0111] Specifically, according to the event management method of the present invention, a host user can receive a list of guest users who have expressed their intention to participate in a particular event, i.e., a participant list. For example, the processor 210 of the host user device can receive an event linkage message, generate a participant list including guest users who have expressed their intention to participate, and store the list in memory 220. When a new guest user applies to participate, the participant list can be updated by adding the guest user. Furthermore, when a guest user included in the participant list withdraws their intention to participate, the participant list can be updated by removing the guest user from the participant list or by displaying a separate indication (withdrawal indication) in the participant list.

[0112] Furthermore, according to the event management method of the present invention, the host user can receive a list of guest users who have completed remittance for a specific event, i.e., a remittance list. For example, the processor 210 of the host user device can generate a list including guest users who have been confirmed to have completed remittance as a result of the determination in step S340, and store the list in memory 220. The remittance list can be updated by adding each guest user who has been confirmed to have completed remittance in step S340. Furthermore, if a guest user included in the remittance list cancels a remittance, the remittance list can be updated by removing the guest user from the remittance list or by displaying a separate indication (remittance cancellation indication) in the remittance list.

[0113] Alternatively, the participant list may be updated each time the determination in step S340 confirms that the remittance has been completed. That is, the fact that the guest user has completed the remittance may be recorded on the participant list. In this case, the processor 210 of the host user device may generate the remittance list by reorganizing the participant list to include only guest users who have been recorded as having completed the remittance. For example, as shown in the chat window 710 on the left side of FIG. 7, a remittance list 711 may be provided to the host user.

[0114] Furthermore, according to the event management method of the present invention, the host user can receive a list of guest users who have not completed remittance for a particular event, i.e., a non-remittance list. The non-remittance list can be generated by reorganizing the list to include only guest users who are recorded as having not completed remittance among the guest users included in the participation applicant list in the above example. Alternatively, the non-remittance list can be updated by generating a list identical to the participation applicant list and then excluding guest users whose remittance completion has been confirmed in step S340 from the list or by displaying the list separately. The separately generated non-remittance list can be updated according to situations such as when a participant applicant is added, when remittance is completed, when a participation application is withdrawn, or when a remittance is withdrawn. For example, a non-remittance list 721 can be provided to the host user, as displayed in the chat window 720 on the right side of FIG. 7. The non-remittance list 721 can include additional functions, such as "bulk reminder sending." By executing this function, the host user can send reminder messages to all guest users included in the unremitted recipient list 721 at once. Alternatively, a function may be included that enables a reminder message to be sent to each or only some of the guest users included in the unremitted recipient list 721.

[0115] The host user can receive the above-mentioned lists (e.g., participant applicant list, remitter list, non-remitter list, etc.) using a function that displays the lists. For example, the function can be implemented as a function provided in a messenger application installed on the host user device or in an individual chat room of the messenger application. When the host user executes the function, the processor 210 can read the requested list from the memory 220 and provide it to the host user. For example, the requested list can be provided through a chat window of the chat room. In this case, the chat room in which the list is displayed may be the same chat room as the chat room that transmitted the event-linked message. However, the present invention is not limited to this, and a separate chat room may be created for displaying the list. As a specific example, the non-remitter list 721 can be provided through a chat room that includes only the host user and the first chat room operation staff, if there is a predetermined operation staff of the first chat room to which the host user and the guest user belong. At this time, the above-mentioned lists (participant list, remitter list, non-remitter list, etc.) can be displayed in various forms such as a notification or a pop-up window through a menu.

[0116] Some or all of the steps of the event management method according to an embodiment of the present invention described above with reference to Figure 3 may be performed by the server 260. When each step of the event management method of Figure 3 is performed by the server 260, the above description of the operation of the host user device in that step can be understood to be performed by the server 260. In addition, among the descriptions of the host user device, descriptions that are not related to changes in the entity that performs each step can also be applied to the server 260.

[0117] 3 may be performed by the server 260 based on an input from a host user. For example, when the host user inputs information about an event to be generated through the input unit 240 of the host user device, the information may be transmitted to the server 260. The server 260, having received the information about the event, may generate an event-linked message according to the present invention using the information.

[0118] The event-linked message transmission step (S320) of FIG. 3 may be performed by the server 260. When an event-linked message is generated by a host user device, the server 260 may receive the generated event-linked message and transmit the received event-linked message to at least one guest user device via a messenger application. When an event-linked message is generated by the server 260, the server 260 may transmit the generated event-linked message to at least one guest user device via a messenger application. In this case, the event-linked message may be transmitted via a chat room including a host user and at least one guest user. In this case, the event-linked message may be displayed in a chat window in a format in which the host user transmits the event-linked message to at least one guest user in the same chat room.

[0119] The remittance request message transmission step (S330) of FIG. 3 may be performed by the server 260. The server 260 may receive information including an intention to participate in a specific event from a guest user device. The information may include information about the event and information about the guest user who expressed the intention to participate. The server 260 may identify the event and the guest user based on the received information. The server 260 may also transmit a remittance request message related to the event to the guest user via a messenger application. The remittance request message may be generated by the host user device or may be generated by the server 260 based on information about the event. The server 260 may store the generated remittance request message in memory 270, and later, upon receiving an intention to participate from the guest user, read the related remittance request message from memory 270 and transmit it to the guest user device. Alternatively, the server 260 may generate and transmit a related remittance request message to the guest user device upon receiving an intention to participate from the guest user. The information about the event or the remittance request message may be stored in the memory 270 of the server 260 along with event identification information. As described above, the remittance request message can be transmitted through a chat room that includes a guest user. To this end, the server 260 can create or identify a chat room that includes a guest user and then transmit the remittance request message through the chat room. For example, the server 260 can create a chat room that includes a host user and a guest user and transmit the remittance request message through the chat room. In this case, the remittance request message can be displayed in the chat window of the host user and / or the chat window of the guest user in a form in which the host user transmits the remittance request message to at least one guest user that is included in the same chat room.

[0120] The remittance processing confirmation step (S340) of FIG. 3 may be performed by the server 260. When the remittance is processed using a remittance and payment service supported by the messenger application, the server 260 may confirm whether the remittance has been processed by receiving data related to the remittance from the remittance and payment service. When the remittance is processed using a banking application other than the messenger application, the server 260 may confirm whether the remittance has been processed based on remittance processing information input by the guest user. Alternatively, the server 260 may confirm whether the remittance has been processed by receiving the history of the account identified by the information related to the event. Alternatively, the server 260 may confirm whether the remittance has been processed by analyzing a remittance-related message received from an official mobile banking account, etc., via the messenger application. The server 260 may store the result of confirming whether the remittance has been processed in the memory 270 so that the result can be used later to generate an event-related list.

[0121] The subsequent message transmission step (S350) of FIG. 3 may be performed by the server 260. If the remittance request message has not been processed in step S340, the server 260 may transmit a reminder message to the guest user. Alternatively, if the remittance request message has been processed in step S340, the server 260 may transmit a remittance confirmation message to the guest user. The subsequent message may be generated by the host user device or the server 260. The server 260 may store the generated subsequent message in memory 270 and, depending on the confirmation result of whether the remittance has been processed, may later read the related subsequent message from memory 270 and transmit it to the guest user device. Alternatively, the server 260 may generate the related subsequent message and transmit it to the guest user device when it is confirmed whether the remittance has been processed. If the information included in the subsequent message (e.g., the QR code included in the remittance confirmation message) is different for each guest user, the subsequent message or the information included in the subsequent message may be generated after it is confirmed whether the remittance has been processed. The subsequent message may be stored in memory 270 of server 260 along with the event identification information.

[0122] The above-mentioned lists (participant list, remitter list, non-remittee list, etc.) or information required for generating the lists may be stored in the memory 270 of the server 260. In addition, operations performed by the host user device related to generating and updating lists may be performed by the server 260, thereby generating lists or updating lists stored in the memory 270. Upon a request from the host user, the server 260 may read or generate the lists (participant list, remitter list, non-remittee list, etc.) from the memory 270 and transmit them to the host user device. The transmitted lists may be displayed via the output unit 250 of the host user device in various forms, such as a notification or a pop-up window via a menu.

[0123] How to participate in the event The event participation method according to one embodiment of the present invention may be performed by a messenger application installed on a guest user device.

[0124] Hereinafter, the event participation method according to the present invention will be described with reference to FIG.

[0125] FIG. 4 is a diagram for explaining a method for participating in an event according to an embodiment of the present invention.

[0126] The method for participating in an event according to an embodiment of the present invention may include receiving an event-linked message (S410), receiving a guest user input (S420), receiving a remittance request message (S430), and / or receiving a follow-up message (S440).

[0127] The event participation method of Fig. 4 may be performed on a guest user device. The event participation method of Fig. 4 may include steps corresponding to the steps of the event management method of Fig. 3. In the following description of the event participation method of Fig. 4, portions that overlap with the description of the event management method of Fig. 3 will be omitted.

[0128] According to the event participation method of the present invention, a guest user device can receive an event linkage message (S410). Specifically, the guest user device can receive an event linkage message regarding participation in a predetermined event transmitted to the guest user via a first chat room to which the host user and the guest user belong. For example, the processor 210 of the guest user device can receive the event linkage message transmitted from the host user device via the transceiver 230. The received event linkage message 521 can be provided to the guest user by being displayed on the output unit 250 of the guest user device, as shown by reference numeral 520 in FIG. 5.

[0129] The guest user device can receive (S420) an input from the guest user in response to the received event linked message 521. For example, the guest user can apply to participate in the event of the event linked message 521 via the input unit 240 of the guest user device, and the guest user device can receive the application to participate as an input.

[0130] When a guest user inputs an application to participate in a particular event, the guest user device may receive a remittance request message for the event (S430). For example, the processor 210 of the guest user device may receive the remittance request message for the event via the transceiver 230. The received remittance request message 531 may be provided to the guest user by being displayed on the output unit 250 of the guest user device, as shown by reference numeral 530 in FIG. 5.

[0131] A guest user who receives a remittance request message can process the remittance using various remittance and / or payment methods. As described above, the event management method of the present invention can transmit a subsequent message depending on whether the guest user has processed the remittance requested by the remittance request message.

[0132] The guest user device may receive the subsequent message (S440). For example, if the remittance is completed, the processor 210 of the guest user device may receive a remittance confirmation message 621 as the subsequent message via the transceiver 230. For example, if the remittance is not completed, the processor 210 of the guest user device may receive a reminder message 611 as the subsequent message via the transceiver 230.

[0133] Although not shown, the guest user device may display a list of received remittance request messages that have not yet been processed. Remittance request messages received by each guest user and / or whether or not the remittance has been processed may be managed as a list. The list may be stored or managed in the memory of the guest user device. Alternatively, the list may be stored or managed in the memory of the server 260. The list may be displayed via the output unit 250 of the guest user device in various forms, such as a notification in the messenger application or a pop-up window through a menu.

[0134] According to the present invention, it is possible to efficiently manage event openings and event fees. For example, all procedures related to payment of fees can be performed through a messenger application, and various lists related to event participants can be provided, thereby enabling efficient event management. Furthermore, guest users who have registered to participate in an event can receive remittance request messages, reminders, or remittance confirmation messages through the messenger application, thereby efficiently completing the event participation procedures.

[0135] Although the exemplary methods of the present disclosure are expressed as a series of operations for clarity of explanation, this is not intended to limit the order in which the steps are performed, and the steps may be performed simultaneously or in a different order if necessary. To achieve a method according to the present disclosure, other steps may be included in addition to the steps shown, or some steps may be omitted and the remaining steps may be included, or some steps may be omitted and additional other steps may be included.

[0136] The various embodiments of the present disclosure are not intended to enumerate all possible combinations, but are intended to describe representative aspects of the present disclosure, and the matters described in the various embodiments may be applied independently or in combination of two or more.

[0137] Furthermore, methods according to an embodiment of the present invention can be embodied in the form of program instructions executable by various computer devices and recorded on a computer-readable recording medium. The computer-readable recording medium can include, alone or in combination, program instructions, data files, data structures, and the like. The program instructions recorded on the medium may be those specially designed and constructed for the present invention, or those known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape; 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 instructions, such as ROM, RAM, and flash memory. Examples of program instructions include not only machine language code produced by a compiler, but also high-level language code executable by a computer using an interpreter, etc. The hardware devices can be configured to operate as one or more software modules to perform the operations of the present invention, or vice versa.

[0138] Additionally, various embodiments of the present disclosure may be implemented using hardware, firmware, software, or a combination thereof, etc. In the case of a hardware implementation, the implementation may be using one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general processors, controllers, microcontrollers, microprocessors, etc.

[0139] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause operations according to the methods of the various embodiments to be performed on a device or computer system, as well as non-transitory computer-readable media on which such software or instructions, etc., may be stored and executed on a device or computer.

Claims

1. A computer program stored on a computer-readable recording medium for executing an event management method on a computer, generating an event-linked message regarding participation in a given event based on a host user's input; transmitting the event linking message to a guest user device of a guest user who belongs to the first chat room via a first chat room to which the host user belongs; transmitting a remittance request message to the guest user device based on the guest user's input to the event linked message; determining whether the remittance requested by the remittance request message has been processed by the guest user device; and creating a list of the guest users who have not completed the remittance based on whether the remittance has been processed; The list is displayed in the first chat room of the host user, and the computer program includes a function for sending a reminder message to the guest user devices of all of the guest users included in the list displayed in the first chat room at once.

2. The computer program product according to claim 1 , wherein the event linkage message or the remittance request message includes information regarding a cost for participating in the predetermined event or a remittance deadline.

3. the remittance request message is transmitted to the guest user device via a second chat room to which the guest user belongs; The computer program product of claim 1 , wherein the second chat room is different from the first chat room.

4. The step of transmitting the remittance request message includes: creating a second chat room to which the host user and the guest user belong; and transmitting the remittance request message through the second chat room.

5. The computer program of claim 1 , further comprising transmitting a subsequent message to the guest user device based on whether the remittance was processed.

6. 6. The computer program of claim 5, wherein if the remittance is processed, the subsequent message is a remittance confirmation message.

7. The computer program product of claim 6 , wherein the remittance confirmation message includes approval information approving participation in the predetermined event.

8. The computer program product of claim 1 , further comprising: providing information to a host user device regarding whether the remittance requested by the remittance request message has been processed.

9. 1. A method of event management performed by a computing device including at least one processor, comprising: generating an event-linked message regarding participation in a given event based on a host user's input; transmitting the event linking message to a guest user device of a guest user who belongs to the first chat room via a first chat room to which the host user belongs; transmitting a remittance request message to the guest user device based on the guest user's input to the event linked message; determining whether the remittance requested by the remittance request message has been processed by the guest user device; and creating a list of the guest users who have not completed the remittance based on whether the remittance has been processed; The list is displayed in the first chat room of the host user, and the event management method includes a function of sending reminder messages in bulk to the guest user devices of all the guest users included in the list displayed in the first chat room.

10. 1. A computing device including at least one processor, The processor: generating an event-linked message regarding participation in a given event based on the host user's input; Transmitting the event linking message to a guest user device of a guest user who belongs to the first chat room via a first chat room to which the host user belongs; transmitting a remittance request message to the guest user device based on the guest user's input in response to the event linked message; determining whether the remittance requested by the remittance request message has been processed by the guest user device; creating a list of the guest users who have not completed the remittance based on whether the remittance has been processed; The list is displayed in the first chat room of the host user, and the computing device includes functionality for sending a reminder message to the guest user devices of all of the guest users included in the list in the list displayed in the first chat room in bulk.

11. The computing device of claim 10 , wherein the event linkage message or the remittance request message includes information regarding a cost or a remittance deadline for participating in the specified event.

12. the remittance request message is transmitted to the guest user device via a second chat room to which the guest user belongs; The computing device of claim 10 , wherein the second chat room is different from the first chat room.

13. The remittance request message The computing device of claim 10 , further comprising: a second chat room in which the host user and the guest user belong; and communication is transmitted through the second chat room.

14. The processor: The computing device of claim 10 , further comprising: transmitting a subsequent message to the guest user device based on whether the remittance was processed.

15. 15. The computing device of claim 14, wherein if the transfer is processed, the subsequent message is a transfer confirmation message.

16. 16. The computing device of claim 15, wherein the remittance confirmation message includes authorization information authorizing participation in the predetermined event.

17. The computing device of claim 10 , further comprising: a host user device configured to provide information regarding whether the remittance requested by the remittance request message has been processed.

Images