Method, program and computing device for realizing a common message in a messenger

Abstract

A method, a program, and a computing device for implementing a common message in a messenger are provided, which include the steps of: generating, in association with a chat room on the messenger, a common message page in which at least one member of a plurality of users in the chat room is designated to edit a common message at the request of a first user; displaying, as a first message in the chat room, a common message window having common message information including at least management information related to an editing status of the common message; and providing, as the common message is edited by the at least one member, the changed common message information on the common message page.

Description

[Technical Field]

[0001] The present disclosure relates to a method, a program, and a computing device for implementing a common message in a messenger. More specifically, the present disclosure relates to a method, a program, and a computing device for implementing a common message in a messenger, in which multiple users use a messenger to edit a common message through another space linked to a chat room and provide the common message to the chat room. [Background technology]

[0002] An instant messenger is an application that exchanges messages and data in real time over a wired or wireless network and is a type of communication service. The messenger application is installed on a user's device, and the user can communicate with other users through the messenger application. Specifically, the user can enter or edit their own content through an interface provided in a chat room opened in the messenger application, and the content can be displayed in the chat room.

[0003] Meanwhile, the content is edited by a single user and is usually displayed in a chat room as a single message, but the function of multiple users participating in a chat room jointly editing content and expressing it in a single message has not been realized in commercial messenger applications.

[0004] For example, a chat room user may individually create a message for other users in the chat room to notify them of a specific event. However, if the accuracy of the notification message is required, an editing process such as correction and review by other users may be required. When a large number of editing-related messages are exchanged in a chat room, regular messages and editing-related messages may be mixed in the chat room. This makes it difficult for users involved in editing to select only the editing-related messages. Furthermore, users not involved in editing may find it difficult to view the messages they want to view due to unnecessary editing-related messages. In other words, chat rooms cannot be managed efficiently.

[0005] For this reason, there is a demand for messengers to operate a space where multiple users can jointly edit common messages separately from the chat room, and to provide common messages as a single message in the chat room. Summary of the Invention [Problem to be solved by the invention]

[0006] The present disclosure aims to provide a method, program, and computing device for implementing a common message, in which multiple users use a messenger to edit a common message through other spaces linked to a chat room and provide the common message to the chat room.

[0007] The technical problems of the present disclosure are not limited to the above-mentioned technical problems, and other technical problems not described 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 "ordinary engineers") from the following description. [Means for solving the problem]

[0008] According to one aspect of the present disclosure, a method for realizing a common message in a messenger, performed by a computing device including a processor, includes the steps of: generating, in cooperation with a chat room on the messenger, a common message page in which at least one member of a plurality of users of the chat room is designated to edit a common message at the request of a first user; displaying a common message window in the chat room as a first message, the common message window having common message information including at least management information related to the editing status of the common message; and providing the modified common message information to the common message page as the common message is edited by the at least one member.

[0009] According to another embodiment of the present disclosure, the method may further include a step of displaying a common message window in the chat room as a second message, the common message window reflecting the changed management information as a result of the common message being edited by the at least one member.

[0010] According to another embodiment of the present disclosure, the step of generating the common message page further includes setting editing permissions for the common message for each member, and the management information may include member information and work status information indicating the processing status for each member.

[0011] According to another embodiment of the present disclosure, the modified common message information includes the work status information, and providing the modified common message information on the common message page can display the member who processed the edit based on the work status information, or can display the processing status for each member.

[0012] According to another embodiment of the present disclosure, the step of generating the common message page may further include, if at least two of the plurality of users are designated to edit the common message, setting an editing order among the members for the common message, and the management information may include member information and work status information indicating the processing status of each member according to the editing order.

[0013] According to another embodiment of the present disclosure, if the member's edit is approval or review of the common message, the modified common message information includes the management information, and the management information can be modified according to the processing status due to the member's edit.

[0014] According to another embodiment of the present disclosure, if the member's edit is a modification of the common message, the modified common message information includes the modified common message and the management information, and providing the modified common message information on the common message page may include associating the member information of the member who modified the common message with the modified common message and displaying them on the common message page.

[0015] According to another embodiment of the present disclosure, the management information may further include work status information indicating the processing status of each member, and providing the changed common message information to the common message page may further include providing the changed work status information to the common message page in response to changes in work status information of other members other than the member who made the modification.

[0016] According to another embodiment of the present disclosure, the step of generating the common message page further includes displaying the draft message window containing the common message information as a third message on the common message page, the common message information having the common message and the management information, and the draft message window being distinguishable from a message window displaying a chat between the members on the common message page.

[0017] According to another embodiment of the present disclosure, providing the modified common message information to the common message page may include displaying a draft message window including the modified common message information as a fourth message on the common message page.

[0018] According to another embodiment of the present disclosure, the method may further include sharing the common message in the chat room after the designated members have completed editing the common message.

[0019] According to another embodiment of the present disclosure, the step of sharing the common message in the chat room may include displaying a message of the first user or the member who processed the last editing operation as the common message in the chat room.

[0020] According to another aspect of the present disclosure, there is provided a computing device implementing a messenger, the computing device including: a memory storing at least one instruction; and a processor configured to execute the at least one instruction stored in the memory, wherein the processor is configured to: generate a common message page in which at least one member of a chat room on the messenger is designated to edit a common message by a request of a first user belonging to the chat room; display a common message window in the chat room as a first message, the common message window having common message information including at least management information related to an editing status of the common message; and provide the common message information changed as the common message is edited by the at least one member on the common message page.

[0021] A computer-readable recording medium according to another aspect of the present disclosure may include a computer program for executing the method for realizing a common message in a messenger according to the present disclosure.

[0022] The above briefly summarized features of the present disclosure are merely exemplary aspects of the detailed description of the present disclosure that follows and are not intended to limit the scope of the present disclosure. [Effects of the Invention]

[0023] According to the present disclosure, a method for realizing a common message can be provided in which a large number of users use a messenger to edit a common message through another space linked to a chat room and provide the common message to the chat room.

[0024] The present disclosure also provides a computing device for performing the method.

[0025] According to the present disclosure, a program for causing a computing device to execute the method can be provided.

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

[0027] [Figure 1] 1 is a diagram illustrating a system in which a method for realizing a common message in a messenger according to an embodiment of the present disclosure is implemented. [Figure 2] 1 is a block diagram illustrating a user device and a server that executes a method for realizing a common message in a messenger according to an embodiment of the present disclosure. [Figure 3] 1 is a block diagram illustrating a user device and a server that executes a method for realizing a common message in a messenger according to an embodiment of the present disclosure. [Figure 4] 1 is a flowchart illustrating a method for realizing a common message in a messenger according to an embodiment of the present disclosure. [Figure 5] FIG. 10 illustrates an example of a common message generated by a first member. [Figure 6] FIG. 10 illustrates an example of a common message generated by a first member. [Figure 7] FIG. 10 illustrates an example of a common message generated by a first member. [Figure 8] FIG. 10 illustrates an example of a common message generated by a first member. [Figure 9] FIG. 10 illustrates an example of a common message generated by a first member. [Figure 10] FIG. 10 illustrates an example of a common message generated by a first member. [Figure 11] FIG. 10 is a diagram illustrating an example of editing of a common message by second and third members. [Figure 12] FIG. 10 is a diagram illustrating an example of editing a common message by second and third members. [Figure 13]FIG. 10 is a diagram illustrating an example of editing a common message by second and third members. [Figure 14] FIG. 10 is a diagram illustrating an example of a common message modification by a first member. [Figure 15] FIG. 10 is a diagram illustrating an example of a common message modification by a first member. [Figure 16] FIG. 10 is a diagram illustrating an example of a common message modification by a first member. [Figure 17] FIG. 10 illustrates an example of members' approval of a common message and sharing of the common message in a chat room. [Figure 18] FIG. 10 illustrates an example of members' approval of a common message and sharing of the common message in a chat room. [Figure 19] FIG. 10 illustrates an example of members' approval of a common message and sharing of the common message in a chat room. [Figure 20] FIG. 10 is a diagram illustrating an example of a common message modification by a member who does not create the common message. [Figure 21] FIG. 10 is a diagram illustrating an example of a common message modification by a member who does not create the common message. DETAILED DESCRIPTION OF THE INVENTION

[0028] 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.

[0029] In describing the embodiments of the present disclosure, if it is determined that a detailed 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.

[0030] 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 exists 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 component can further include the other component, unless otherwise specified.

[0031] 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 called a second component in another embodiment, and similarly, a second component in one embodiment may be called a first component in another embodiment.

[0032] In this disclosure, each of the phrases "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B, C or combination thereof" can include any or all possible combinations of the items listed together in that phrase.

[0033] In this disclosure, components that are distinguished from one another are used to clearly describe the respective features 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, even if not otherwise specified, such integrated or distributed embodiments are also included within the scope of this disclosure.

[0034] In this disclosure, the components described in various embodiments are not necessarily essential components, and some 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.

[0035] 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 can be exchanged between devices and systems, and between devices, and is not limited to a specific network.

[0036] Furthermore, in this specification, a computing device or a device may be a mobile device such as a smartphone, a tablet PC, a wearable device, a laptop, or an HMD (Head Mounted Display). A device may also be a fixed device such as a PC or a home appliance with a display function. As another example, a computing device or a device may be a computing device capable of operating as a server or an IoT (Internet of Things) device. That is, in this specification, a device may refer to an apparatus capable of performing a method according to the present disclosure and is not limited to a specific type.

[0037] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0038] FIG. 1 is a diagram illustrating a system in which a method for realizing a common message in a messenger according to an embodiment of the present disclosure is implemented.

[0039] A system according to the present disclosure may include one or more user devices 100 a , 100 b , 100 c and a server 200 connected via a network 300 .

[0040] Each of the user devices 100a to 100c is also called a client or a user terminal, and can connect to the server 200 via the network 300 to send and receive data to and from other user devices or servers.

[0041] The method for realizing a common message in a messenger according to the present disclosure may be performed using a messenger service provided in conjunction with various online services. The messenger service may be a communication service provided by an instant messenger provider, social media, community sites, online games, portal sites, shopping malls, etc. Specifically, an instant messenger provider may provide a messenger service as a basic function, and social media, community sites, online games, etc. may provide a messenger service for user communication by adding it to the basic functions of their respective services. In the present disclosure, a messenger service does not simply include communication via an instant messenger but also broadly includes communication services additionally provided by various services. A service that at least implements the method for realizing a common message applicable to communication between users according to the present disclosure may be considered to implement a messenger service, regardless of its basic form. Hereinafter, an instant messenger will be described as an example of a messenger service that implements the method for realizing a common message according to the present disclosure, but this does not exclude the application of the method to various services that implement the messenger service, regardless of its basic form.

[0042] A client module for using the messenger service may be installed in each of the user devices 100a, 100b, and 100c. A server module for supporting the messenger service may be installed in the server 200. In the present disclosure, an application installed on a user device may refer to a client module installed in each of the user devices 100a, 100b, and 100c for using the instant messenger service. The application may include a function for at least some users participating in a chat room to create and collaboratively edit a common message on a common message page operated as a separate space in conjunction with the chat room. Specifically, the multiple user devices 100a to 100c have the same built-in messenger application, and users can access the messenger service through at least one of the multiple user devices 100a to 100c.

[0043] The server 200 can provide services such as a messenger application. A user who uses the service can connect to the server 200 that provides the service by inputting predetermined connection information (ID and password) through a user device. The server 200 can identify and authenticate the connected user through the connection information input from the user device. The server 200 can also collect, accumulate, store, and query information about the identified user, and facilitate data transmission and reception between the identified users.

[0044] The server 200, like the user devices 100a to 100c, may open a separate common message page in the chat room at the request of at least some users, and may execute a function in the application to assist users who have joined the common message page to edit common messages on the common message page.

[0045] 2 and 3 are block diagrams illustrating a user device and a server that perform a method for realizing a common message in a messenger according to an embodiment of the present disclosure.

[0046] 2, the user device 100 may include a communication unit 110, a sensor unit 120, an input unit 130, an output unit 140, a memory 150, and a processor 160. The user devices 100a to 100c may further include other components or modules related to the operation and function of the device, and are not limited to the above-described embodiments.

[0047] The communication unit 110 can exchange data with the server 200 or other user devices via a network. The communication unit 110 can include all kinds of wired / wireless communication modules that can communicate with the outside.

[0048] The sensor unit 120 may include multiple sensor modules that detect user position information, object images, motion, biological morphology / signals, and environment.

[0049] The location information-related sensor may have a module for acquiring the device's two-dimensional position, altitude, and location within an indoor facility. The location information sensor may be, for example, a GPS sensor, a communication access point-based location (address) detection, etc. The communication access point may be, for example, a cellular or WiFi access point (repeater, base station, etc.), or a beacon communication module. The object image-related module may include all kinds of imaging means capable of acquiring still or moving images. Taking a smartphone as an example, the imaging unit may be a camera module provided in the smartphone.

[0050] The motion data-related sensor acquires basic detection values ​​for estimating the user's movements and may include, for example, an acceleration sensor, a gyro sensor module, etc. The biometric data-related sensor may sense a part of the body, such as a fingertip, to acquire fingerprints, veins, blood pressure, pulse, etc., or may recognize the iris through the eye.

[0051] The input unit 130 is an interface for receiving user input and may include various input means. For example, the input unit 130 may include an input means using a pressure sensor, an electrostatic touch sensor, etc. (e.g., a virtual keyboard displayed on a touch screen), mechanical buttons, etc. The user device 100 may acquire information sensed by the sensor or input from the mechanical buttons as input information. The input unit 130 may also include a microphone for receiving voice or sound.

[0052] The output unit 140 can output to the outside information acquired or received by the user device 100, information processed by the user device 100, etc. The output unit 140 can include, for example, a display that outputs visual information, a speaker that outputs audio information, etc.

[0053] The memory 150 can store and manage applications that implement various functions of the user device 100, data generated or transmitted by the processor 160, or an external request.

[0054] Specifically, the memory 150 may store information obtained from a user or generated by the processor 160, such as information obtained through the input unit 130. The memory 150 may store information received from the server 200 or other user devices through the communication unit 110.

[0055] The memory 150 may include a built-in messenger application to implement the common message implementation method according to the present disclosure and general functions of a messenger in the processor 160. The memory 150 may also store and manage various data generated by the processor 160 executing the method. The data may be common message information, i.e., common messages and management information, generated by a user or changed through editing.

[0056] The processor 160 may control the operations of other components within the user device 100. For example, the processor 160 may process information acquired through the input unit 130 and the communication unit 110. The processor 160 may also read and process information and applications stored in the memory 150 as required. The processor 160 may output the processed information through the output unit 140, store it in the memory 150, or transmit it to the outside via the communication unit 110.

[0057] In addition, the processor 160 may separately provide a common message page associated with the chat room in response to a user's request, and perform processing related to a common message requested by a user participating in the common message page.

[0058] 3, the server 200 may include a communication unit 210, a memory 220, and a processor 230. The server 200 may further include other components and modules related to the operation of the server or system, and is not limited to the above-described embodiments.

[0059] The communication unit 210 can exchange data with user devices or other servers connected to the network 300. The communication unit 210 can include all kinds of wired / wireless communication modules that can communicate with the outside.

[0060] The memory 220 may store information received from the outside via the communication unit 210. The memory 220 may store information generated within the server 200.

[0061] The memory 220 may incorporate a software module for implementing the method for implementing a common message according to the present disclosure so that the method is implemented by the processor 230. The memory 220, like the user device 100, may store and manage various data generated by executing the method. The data may be common message information, i.e., common message and management information, generated by the user or changed through editing.

[0062] The processor 230 may control the operations of other components within the server 200. For example, the processor 230 may process information acquired via the communication unit 210. The processor 230 may also read and process information stored in the memory 220. The processor 230 may store the processed information in the memory 220 or transmit it to the outside via the communication unit 210.

[0063] The processor 230 controls a messenger built into the user device 100 and processes data and requests exchanged through the messenger. The processor 230 also performs processing related to the control of opening a common message page requested by a user and editing a common message.

[0064] FIG. 4 is a flowchart illustrating a method for realizing a common message in a messenger according to an embodiment of the present disclosure.

[0065] The method for implementing a common message according to the present disclosure may be implemented by a computing device including at least one of the user device 100 and the server 200, and more specifically, by the processor 160 of the device 100 and the processor 230 of the server 200. However, for ease of description, the terms processors 160 and 230 will be omitted, and the components that perform the steps of the method will be primarily referred to as the user device 100 and / or the server 200. For ease of description, the following description will focus on the user device 100 performing the relevant steps of the method according to the present disclosure. However, unless otherwise specified, the server 200 may also perform substantially the same steps as those described below, and this does not exclude the method being implemented through distributed processing between the user device 100 and the server 200.

[0066] First, in a chat room 402 in which multiple users participate, in response to a request from a first user, the user device 100 generates a common message page associated with the chat room 402 for users of the specified chat room 402 to edit common messages, and can also generate common message information in conjunction with the chat room 402 (S105).

[0067] Step S105 may be performed, for example, by the user device 100 of the first user. Step S105 will be described with reference to the examples shown in FIGS. 5 to 10. FIGS. 5 to 10 are diagrams illustrating an example of a common message being generated by a first member. The first user is A in the subsequent drawings, including FIG. 5, and hereinafter, the terms "first user" and "A" may be used interchangeably. The subsequent drawings assume that the first user A opens a common message page 422, and other users B, C, and M of the chat room 402 participate in the common message page (see 422 in FIG. 9) to edit the common message.

[0068] A user participating in the chat room 402 named "Company" can input content through an input window 404, as illustrated in Figures 5 and 6, and a message window 406 containing the input content can be displayed in the chat room 402.

[0069] To create a common message to notify the seminar on the revised regulations, the first user A can access the service menu through the service menu tab 408 and select a menu to perform processing related to the common message. The service menu can include, for example, a common message menu 410 for common messages that handles processing related to editing the common message, a KEEP menu that saves and manages content attached to the message and content obtained by the user through other routes, etc. The other routes can be, for example, a chat room other than the chat room 402, a content acquisition service of the messenger, a service site other than the messenger, the user device 100, etc.

[0070] In this example, the menu that performs processing related to the common message is called a common message, but as long as it is a function that performs the processing, the menu name and the method of accessing the menu can be modified in various forms without restriction.

[0071] When the first user A accesses the common message menu 410, the user device 100 can provide a host editing interface via the first user A's messenger. The host editing interface can support the first user A in creating a common message and allowing designated users, i.e., members, of the multiple users of the chat room 402 to edit the common message. Some functions of the host editing interface are illustrated in FIGS. 7 and 8.

[0072] 7, the first user A can input a title of the shared message. The user device 100 can also provide a member designation UI 412, an authority setting UI 414, and an order setting UI 416.

[0073] Using the member designation UI 412, the first user A can select at least some of the users of the chat room 402 who will be involved in editing the common message as members of the common message page 422. In this example, the first user A selects himself as well as users B, C, and M of the chat room 402 as members. Hereinafter, for convenience of explanation, the first user A and the other users B, C, and M may be referred to as the first member and the other members while the common message page 422 is activated.

[0074] When the first member A turns on the permission setting in the permission setting UI 414, the user device 100 may provide a function for granting editing privileges for the common message to the selected members A to C and M via the permission setting UI 414. The editing privileges may relate to a series of tasks belonging to the editing of the common message. For example, the tasks may include editing the common message, reviewing the common message, and approving the common message. Each task may be set to be processed subsequent to a specific task. For example, editing may be performed spontaneously after creating or modifying the common message, or may be performed with reference to reviews by other members. Review and approval may be performed after creating or modifying the common message. In the present disclosure, editing tasks are exemplified as the above-listed tasks, but may be categorized into various tasks. In the present disclosure, creation of a common message is described as not being included in the editing privileges provided in the permission setting UI 414. However, creation is an editing task specific to the member who opened the common message page 422, and therefore may be a type of editing task of the opening member. It is merely omitted from the editing privilege options.

[0075] In the present disclosure, editing authority is divided into modification authority, review authority, and approval authority in connection with the illustrated operations. The modification authority, for example, may permit a member to modify a common message created by a first member A, so that the modified common message is displayed as the common message currently being edited on the common message page 422. The modification authority may also permit a member to re-modify an already modified common message, so that the re-modified common message is displayed as the common message currently being edited on the common message page 422.

[0076] Review permissions may, for example, not allow modification permissions for created or modified common messages, but may allow members to attach review comments to common messages so that members with modification permissions can modify the common messages.

[0077] Approval rights may, for example, allow members to agree to share or transmit a common message in a chat room. Approval rights may not include modification or editing rights.

[0078] In this example, the first member A assigns himself / herself the authority to edit / approve, assigns the authority to edit / review / approve to other members, for example, the second and third members C, and assigns the authority to review / approve to the fourth member M. Members B, C, and M, who are assigned multiple authorities, can perform editing tasks corresponding to each authority.

[0079] If the first member A turns off the authority setting, the user device 100 may, for example, grant the same edit / review / approval authority to all members.

[0080] When the first member A turns on the work order setting in the order setting UI 416, the user device 100 can provide a function to set the order of members for the common message editing work via the order setting UI 416.

[0081] An editing task can include at least one of the tasks of correction, review, or approval, as exemplified above. As shown in FIG. 7, when the task order is set from the first member A to the fourth member M, the same task in the editing task can be processed in the set member order. For example, approval of a common message can be performed in the order of the second member B, the third member C, and the fourth member M. The member task order can also be applied to preceding and succeeding tasks in the editing task process. In the case of the member authority and task order exemplified in FIG. 7, when the third member C performs a preceding task, such as attaching a review to a common message, correction, which is a type of succeeding task, can be requested from the first and second members A and B in the set order, without being requested from the third and fourth members C and M. Review, another succeeding task, can only be requested from the second member B.

[0082] Meanwhile, the order setting UI 416 may provide a function to change the work order of members A to C and M by, for example, a dragging action of the first member A.

[0083] When the first member A turns off the work order setting, the user device 100 may, for example, allow any member to freely perform editing work after creating a common message.

[0084] Once the above settings are complete, the user device 100 can provide the first member A with a function for inputting a common message to be generated on a common message page 422, as another function of the host editing interface. The first member A can input the common message through an input area 418, as shown in FIG. 8 . The first member A can also input various content, such as text, images, icons, and audio, into the input area 418 through a content menu key 420. After inputting the common message, the first member A can touch and input upload 422, which causes the user device 100 to generate common message information including the common message and management information.

[0085] 9, the user device 100 may generate a common message page 422 provided as a separate space while linking with the chat room 402. When the common message page 422 is generated, the user device 100 of the first member A may generate common message information and transmit the common message information to the server 200. The common message information may be generated and managed in association with the chat room 402. The user devices 100 of the second to fourth members B, C, and M may provide the common message page 422 to the corresponding members based on the generated common message information. The common message information will be described in detail in step S110.

[0086] Referring again to FIG. 4, the user device 100 can display a draft message window (see 424a in FIG. 9) on the common message page 422 and a common message window (see 446a in FIG. 10) in the chat room 402 based on the common message information (S110).

[0087] First, the common message information may include management information related to the common message being edited and the editing status of the common message. The common message being edited may be displayed on the common message page 422 in a form similar to a message window for normal chat between members, for example, the chat bubble 430 of the first member A, as shown in Fig. 9. For example, the common message being edited may be displayed through a draft message window 424a that is distinct from the chat bubble 430.

[0088] The management information is additional information for processing the editing status of the common message, and can be generated based on the settings for members, editing authority, and work order, and the status of real-time editing work. For example, the management information can be generated based on the settings and the status of editing work to include member information, current status information, work status information, and change information.

[0089] Member information is generated based on the designated members A to M and can be displayed in the information area 438 (hereinafter abbreviated as "information area") of the common message page as shown in Figure 9. Also, similar to the member UI (members displayed in the circle UI) illustrated in Figure 9, the member information can be arranged based on the work order set by the order setting. In this example, the member information is provided in the information area 438, but is not limited thereto and may be displayed in other parts of the common message page 422.

[0090] The current status information 440 may include a general status regarding the status of the editing work. For example, the current status information 440 may be expressed in terms indicating that editing of the common message is in progress from the time the common message is created until completion, and may be expressed in terms indicating that editing is complete after editing is complete. When editing is in progress, the term representing the current status information 440 may be expressed as "under review," as illustrated in the information area 438 of FIG. 9. When editing is complete, the term related to the current status information 440 may be expressed, for example, as "completed" in the information area 438.

[0091] The work status information 442, 444 may be information indicating the real-time processing status of each member's editing work. Specifically, the work status information may indicate the processing status of each member's editing work based on the member's editing authority set by the authority setting. Furthermore, the work status information may indicate the work processing status of each member based on the member's work order set by the order setting. When a member's editing work is processed, the work status information may be updated to reflect the real-time processing status of each member.

[0092] As shown in FIG. 9, work status information 442 and 444 may be displayed in the information area 438 and the draft message window 424a. For example, if a first member A creates a common message, the user device 100 may generate work status information 442 and 444 indicating that the first member A is processing the creation of the common message required for the current editing task based on the designated members, editing permissions, and order settings, and that the second to fourth members B to M are waiting for subsequent editing tasks to be processed. The generated work status information 442 and 444 may be visualized. As shown in FIG. 9, the processing status of the first member A who has processed the creation of the common message may be displayed, for example, as "A Created" in the information area 438. Furthermore, the processing status of the first member A may be displayed with the circle A unshaded among the members represented by circles to distinguish it from the members who have not yet processed the message. The processing status of the members who have not yet processed the message, i.e., the second to fourth members B, C, and M, may be displayed, for example, with the circles B, C, and M shaded. Each member can check the order of work performed by the members and the subsequent editing work required of each member through the displayed work status information.

[0093] If the editing operation is to modify a common message, the user device 100 may generate modification information. The modification information may be generated by associating the member information of the member who modified the common message with the modified common message. The generated modification information may be provided, for example, in the information area 438 and the draft message window (e.g., 424b to 424h), examples of which will be described later.

[0094] The modification information, including the modified common message and the modified member, can modify the common message information. The modification information can modify the management information of the common message information, and the modified common message can modify the common message information in relation to the existing common message. For example, the modified common message can replace the existing common message, but the existing common message can be maintained in the draft message windows 424b to 424h already provided on the common message page 422. As another example, not only can the existing common message be maintained in the draft message windows 424b to 424h, but the common message information can also include both the existing common message and the modified common message for history management.

[0095] Meanwhile, the common message and management information being edited can be provided in draft message windows 424a-424h, as shown in FIG. 9. Specifically, the draft message windows 424a-424h can be generated to be distinguished from message windows, such as chat bubbles 430, that display chats between members on the common message page 422. The chat bubbles 430 display regular chats between members on the common message page 422 and can be generated, for example, by entering a message in an input window 432 and touching the transmit key 434. Messages sent via the chat bubbles 430 do not change the common message information. However, common messages or management information changed via the draft message windows 424a-424h can change the common message information. Specifically, members can use an interface associated with the draft message window 424a to perform editing tasks. When members perform editing tasks using the interface, the common message information is changed, and the draft message windows 424b-424h can be generated to reflect the changed common message information. In addition, the common message information is changed each time a member requests an editing operation, and the draft message windows 424b to 424h resulting from the editing operation can be displayed in chronological order. Furthermore, the draft message window 424a can also be generated in chronological order for the chat bubbles 430. This ensures that free chat between members on the common message page 422 does not affect the common message information, and management information including work status information and change information can be checked through the draft message window 424a.

[0096] Unlike the chat bubble 430, the draft message window 424a does not simply output all messages input through the input window 432. If there is a request to output an input message to the draft message window 424a, the draft message window 424a can be generated to include the input message. The interface for the output request can be the common message operation key 436, as shown in FIG. 9. The initial draft message window 424a related to the creation of a common message can be generated without using the common message operation key 436, but draft message windows 424b to 424h related to a member's editing work processed through the common message page 422 can be activated through the common message operation key 436. A member who wishes to officially process an editing work can enter an editing-related message in the input window 432 and perform the editing work using the common message operation key 436. An example related to providing the draft message windows 424b to 424h using the common message operation key 436 will be described later.

[0097] The draft message windows 424a-424h may include a draft area 426 that displays at least a portion of the current shared message, and a reply area 428 that displays the real-time processing status of the shared message work and any additional comments. Taking Fig. 9 as an example, an editing work related to the creation of the first member A is being processed, and work status information including the processing status of the first member A can be displayed in the reply area 428.

[0098] Meanwhile, when the common message page 422 is generated, the user device 100 can be controlled to display a common message window 446a containing common message information in the chat room 402, as shown in Figure 10. The common message information can be linked to the chat room 402, as can be seen from the information area 438 and the common message window 446a in Figure 9. The common message window 446a can be provided in a manner similar to the message window 406 of the chat room 402.

[0099] The common message window 446a can display at least a portion of the common message being edited and can provide at least a portion of the management information. As shown in the example of FIG. 10, the common message window 446a can display "Under Review" as the current status information 440 along with the title of the common message. The common message window 446a can also display "Created by A" indicating the editing work performed by the first member A as the work status information 442, 444. The common message window 446a can also provide the work status information 442, 444 including the real-time processing status of the editing work for each member as a member UI (e.g., members displayed in a circle UI) along with the member information. FIG. 10 illustrates a visual representation for distinguishing the first member A who has performed the editing work from the other members B to M who have not yet performed the editing work.

[0100] The common message window 446a, which indicates that the current status information 440 is editing a common message, can function as an interface that is activated only by members among the participants in the chat room 402. In the example of FIG. 10, the common message window 446a, which displays "under review" as the current status information 440, can be an interface for entering the member's common message page 422. Specifically, a member can access the common message page 422 by touching the common message window 446a for editing. Participants other than members cannot enter the common message window 446a even if they touch the common message window 446a, which displays "under review."

[0101] When a member performs subsequent editing via the common message page 422, a common message window 446b reflecting the changed common message information according to the editing can be displayed in chronological order, separately from the previous common message window. In addition, the common message windows 446a and 446b can also be generated in chronological order for the message window 406.

[0102] Although the present disclosure illustrates an example in which the common message operation key 436 is used to activate a draft message window (e.g., see 424b in FIG. 11 ), the draft message window 424b can be activated in various ways. Furthermore, the present disclosure illustrates an example in which management information is provided in the reply area 428 of the draft message window 424a, but the management information can also be displayed in an area of ​​the common message page 422 different from the draft message window 424a. Furthermore, the present disclosure illustrates that the common message window 446a provides the common message being edited along with management information, but it may also display only the management information. Additionally, the present disclosure illustrates that the management information displayed in the common message window 446a includes current status information, member information, and work status information, but the common message window 446a may also display only the current status information, or only the current status information and member information. The interfaces illustrated in the drawings according to the present disclosure are not limited to the examples shown in the drawings and can be modified in various forms.

[0103] Referring again to FIG. 4, based on an editing request from at least one of the first to fourth members A to M, the user device 100 can modify the common message information and display draft message windows 424b to 424h and common message windows 446b to 446d reflecting the modified common message information (S115).

[0104] Step S115 is performed by the user device 100 of the member who requested the editing operation, and the modified common message information can be transmitted to the user devices 100 of the other members via the server 200. Each user device 100 can display new draft message windows 424b-424h and new common message windows 446b-446d based on the common message information. Step S115 will be described with reference to the examples shown in FIGS. 11-16. FIGS. 11-13 are diagrams illustrating an example of editing of a common message by second and third members. FIGS. 14-16 are diagrams illustrating an example of modification of a common message by a first member. Members A-M who requested editing of the user device 100 are displayed in the information field 438 illustrated in FIGS. 11-16. If member C requested editing, "(4:C)" is displayed in the information field 438 illustrated in FIG. 11, indicating that there are four members.

[0105] First, referring to FIG. 11 , according to the editing operation sequence illustrated in FIG. 7 , the second member B can process an operation according to the editing authority granted to him / her via the common message page 422. When the second member B touches the common message operation key 436 for editing, the user device 100 can present operation options 448 according to the second member B's editing authority. Depending on the authority illustrated in FIG. 7 , the second member B's operation options may be, for example, edit, review, or approve. The second member B can process the editing operation by approving the common message created by the first member A without editing or reviewing it. The user device 100 can change the operation status information 442, 444 according to the editing operation processed by the second member B. The changed operation status information may include information that the second member B, who did not process the editing operation, has approved the editing operation. Since the second member B does not modify the common message, change information may not be generated.

[0106] Based on the updated work state information 442, 444, the user device 100 can display a new draft message window 424b separately from the draft message window 424a of the first member A. As shown in FIG. 11 , the reply area 428 of the draft message window 424b can indicate the second member B's "approval." If the second member B enters an additional comment, such as "I understand," while processing the approval, the reply area 428 can also display the additional comment. Because the second member B has not modified the common message, the draft area 426 can indicate that the existing common message remains unchanged. For example, the unaltered text can be displayed in the draft area 426, or only a portion of the existing common message can be displayed, as shown in FIG. 11 .

[0107] The changed work status information 442, 444 can also be provided in other areas of the common message page 422, such as the information area 438. The information area 438 can display a real-time processing status, including the edit work performed and the member who processed the work, based on the changed work status information. For example, the information area 438 can display "B Approved" as the real-time processing status, and the current status information 440 can display "Under Review." Furthermore, the information area 438 can display work status information that distinguishes between members A and B who have processed the edit work and members C and M who have not yet processed the edit work, in order to display the processing status of the edit work for each member. The processed members A and B and the unprocessed members C and M can be distinguished through a member UI visualized as non-shaded and shaded, respectively, as shown in FIG. 11 .

[0108] The third member C, who has checked the editing work of the second member B, can process the work according to the editing authority granted to him / her via the common message page 422. Figure 11 illustrates an example in which the third member C processes the review to guide the direction of correction of the common message through editing work.

[0109] For example, the third member C may input a reply message in the input window 432 and touch the common message operation key 436 for an editing operation related to a review. In response to the touch input, the user device 100 may present operation options 448 according to the editing authority of the third member C, as illustrated in FIG. 7 . The operation options may be, for example, edit, review, or approve. The third member C may process the editing operation by, for example, sequentially touching the “Review” and “Transmit” keys 434. The touch input for the editing operation is not limited to the above example and may be implemented in various ways.

[0110] The user device 100 can change the work status information 442, 444 in the common message information according to the editing work processed by the third member C. The work status information includes the review work of the third member C, and can change the members who have not yet processed the editing work to the first member A to the fourth member M, taking into account the members A, B, and C who will process subsequent editing work, such as correction, approval, and review. The real-time processing status of the first member A and the second member B who have processed the editing work can be switched from processing to not processing. Since the third member C does not modify the common message, change information may not be generated.

[0111] The user device 100 can display a new draft message window 424c based on the changed work state information 442, 444. As shown in FIG. 12, the reply area 428 of the draft message window 424c can show the "review message" of the second member B. The reply area 428 can also show additional comments entered as a reply message by the third member C. Because there are no modifications to the common message by the third member C, for example, the unmodified text can be displayed in the draft area 426, or only a portion of the existing common message can be shown, as shown in FIG. 12.

[0112] The changed work status information 442, 444 can also be displayed in, for example, the information area 438. The information area 438 displays "C Comment" related to the review as a real-time processing status, and the current status information 440 can still display "Under Review." The information area 438 can display the first member A to the fourth member M, who are related to the editing work following the review by the third member C, as unprocessed members.

[0113] The user device 100 can display new common message windows 446b, 446c in the chat room 402 based on the modified common message information.

[0114] 13, the management information changed with the approval of the second member B may be provided in a common message window 446b. Illustratively, the current status information 440 may be displayed as "under review," and the changed work status information 442, 444 in the management information may indicate "B approved" along with the processing members A and B and the unprocessed members C and M. The common message window 446b may also display at least a portion of the common message currently being edited.

[0115] The management information changed in response to the review by the third member C can be provided in a common message window 446c that is different from the common message window 446b of the second member B. The work status information changed in the management information can indicate that all members A to M are in an unprocessed state, along with a "C comment."

[0116] Next, the first member A can use the common message operation key 436 to modify the common message by referring to the review comments of the third member C. As shown in FIG. 14 , the first member A modifies the common message in the input window 450 and selects “Modify” from the operation options 448, which allows the user device 100 to process the modification and editing work of the first member A.

[0117] The user device 100 can change the work status information 442, 444 in the common message information according to the correction and editing work performed by the first member A. The work status information includes the correction work performed by the first member A, and can change the members for whom the editing work has not yet been performed to the second member B to the fourth member M.

[0118] In addition, the user device 100 may generate change information related to the member information of the first member A who modified the modified common message.

[0119] The user device 100 may display a new draft message window 424d based on the changed work status information 442, 444. As shown in FIG. 15, the reply area 428 of the draft message window 424d may indicate "Edit" by the first member A. The draft area 426 of the draft message window 424d may display a modified common message for the changed information. The modified common message may be displayed in its entirety in the draft area 426 so that it can be viewed. As another example, a portion of the modified common message may be displayed in the draft area 426, and a separate window displaying the entire modified common message may be provided by touching the draft message window 424d. In addition, the chat name of the first member A may be displayed around the draft message window 424d generated by the edit, and the name of the member who processed the edit may be displayed in conjunction with the modified common message.

[0120] In addition, the changed work status information 442, 444 and the generated change information can also be displayed, for example, in the information area 438. As shown in Fig. 15, the information area 438 can display "A Modification" as a real-time processing status. The information area 438 can display the second member B to the fourth member M, who are involved in the editing work following the modification by the first member A, as unprocessed members.

[0121] 16, the management information changed by the modification of the first member A can be provided in a common message window 446d. For example, the work status information 442, 444 changed in the management information can indicate the processing member A and the unprocessed members B to M together with "A modified."

[0122] Referring back to FIG. 4, if the condition for completing editing of the common message is met, the user device 100 can complete editing of the common message (S120).

[0123] Step S120 and step S125, which will be described later, may be performed by the user device 100 of the member requesting approval for editing completion or sharing of the common message. Steps S120 and S125 will be described with reference to examples shown in FIGS. 17 to 19. FIGS. 17 to 19 are diagrams illustrating an example of members' approval of a common message and sharing of the common message in a chat room. The editing completion condition in the present disclosure is assumed to be when all members with approval authority, excluding the member who created the common message, approve the originally created common message, or when all members, excluding the member who modified the common message, approve the modified common message. The editing completion condition is not limited to the above examples and can be set in various forms.

[0124] 17 and 18, a second member B and a third member C can select "approval" from the operation options 448 illustrated in FIG. 11 to process an editing operation to approve the modified common message illustrated in FIG. 16. The user device 100 can continuously change the work status information 442, 444 according to the member's approval and generate draft message windows 424d, 424e, 424f and common message windows 446c, 446d for each of the changed work status information 442, 444. Matters related to the work status information changed by approval, the generated draft message windows, and the common message windows are substantially the same as those described in FIG. 11, and therefore further details will be omitted. As in FIG. 11, the changed work status information 442, 444 can also be displayed in the information area 438.

[0125] When the fourth member M, who is the last of the members A to M with approval authority, selects "Approve" from the work options 448 illustrated in FIG. 17, the work status information can be changed to a state in which all members have approved the common message and all members' editing work has been completed. The changed work status information can be processed as if there is no member processing the subsequent editing work. The current status information 440 can be displayed as "Completed," as illustrated in the information area 438 of FIG. 18. The draft message window 424f and the common message window 446d approved by the fourth member M can be generated to reflect the changed management information, i.e., editing completion, as shown in FIGS. 18 and 19.

[0126] When the current status information 440 and the work status information are changed as described above, the user device 100 may determine that the edit completion condition is met and determine the edited common message as the final common message.

[0127] Referring back to FIG. 4, the user device 100 may perform a process of sharing the edited common message in the chat room 402 at the request of any of the members (S125).

[0128] As shown in Fig. 18, the user device 100 may provide a shared key 452 adjacent to the draft message window 424f approved by the fourth member M. Exemplarily, when the first member A touches the shared key 452, the user device 100 may display a regular message window containing the final shared message in the chat room 402, as shown in Fig. 19. Although the shared key 452 is exemplified in the present disclosure, the sharing interface may be modified in various ways.

[0129] Meanwhile, for example, the common message may be provided in the chat room 402 as a message window of the first member A who first created the common message. The member who first created the common message may be the member who opened the common message page 422. As another example, the common message may be displayed in the chat room 402 as a message window of the member who performed the last editing operation, for example, the final approval or the last revision operation. In the above example, the chat name of the member who performed the sharing operation may be displayed in the chat room 402, or, depending on the settings, the chat name of another member may be displayed in the chat room 402 instead of the member who performed the sharing operation. The chat name of the other member may be, for example, the member who first created the common message, the member who performed the last editing operation, or the member who performed the last revision operation.

[0130] 20 and 21 are diagrams illustrating an example of a common message being modified by a member who does not create the common message.

[0131] The embodiment related to Figures 20 and 21 is another embodiment of the editing work in step S115 of Figure 4. Specifically, unlike the situation illustrated in Figures 9 to 15, a situation is assumed in which a third member C directly edits the common message created by a first member A using his or her editing authority.

[0132] The third member C can modify the common message generated by the first member A illustrated in FIG. 9 using the modification option 448 described above, and the user device 100 can process the modification (edit) by the third member C.

[0133] The user device 100 can change the work status information 442, 444 in the common message information according to the editing work processed by the third member C. The work status information includes the editing work of the third member C, and in consideration of the members A and B who will process subsequent editing work, such as correction, approval, and review, the members who have not yet processed the editing work can be changed to the first member A, the second member B, and the fourth member M. That is, the real-time processing status of the first member A and the second member B who have processed the editing work can be switched to not yet processed.

[0134] Additionally, the user device 100 may generate change information related to the member information of the third member C who modified the modified common message.

[0135] The user device 100 can display a new draft message window 424g based on the changed work status information 442, 444. As shown in FIG. 20 , the reply area 428 of the draft message window 424g can display the "Edit" of the third member C. The draft area 426 of the draft message window 424g can display a common message correcting the changed information. In addition, the chat name of the third member C is displayed around the draft message window 424g generated by the edit, and the name of the member C who processed the edit can be displayed in conjunction with the common message correcting the changed information.

[0136] In addition, the changed work status information 442, 444 and the generated change information can also be displayed, for example, in the information area 438. As shown in Fig. 15, the information area 438 can display "C Modification" as a real-time processing status. The information area 438 can display the first member A, the second member B, and the fourth member M as unprocessed members related to the editing work following the modification of the third member C.

[0137] Although not shown, similar to FIG. 16, the management information changed by the modification of the third member C can be provided in the common message window.

[0138] Subsequently, similar to step S120, when the first member A, the second member B, and the fourth member M sequentially approve the modified common message of the third member C, the user device 100 may determine that the condition for completing editing of the common message is met. The user device 100 may generate a draft message window 424h and a common message window that reflect the modified current status information 440 and the modified work status information, similar to FIGS. 17 to 19.

[0139] 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 illustrated, 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.

[0140] The various embodiments of the present disclosure are not intended to list 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.

[0141] Furthermore, methods according to embodiments of the present disclosure may be embodied in the form of program instructions to be executed by various computer devices and recorded on computer-readable media. The computer-readable media may include, alone or in combination, program instructions, data files, data structures, and the like. The program instructions recorded on the media may be those specially designed and constructed for the present disclosure, or may be those well known and available to those of ordinary skill in the computer software arts. Examples of computer-readable 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 code, such as produced by a compiler, but also high-level language code that can be executed by a computer using an interpreter, etc. The hardware devices may be configured to operate as one or more software modules to perform the operations of the present disclosure, or vice versa.

[0142] Furthermore, various embodiments of the present disclosure may be implemented in hardware, firmware, software, or a combination thereof. In the case of a hardware implementation, one or more ASICs (Application Specific Integrated Circuits) may be used. Integrated It can be realized by devices such as Digital Signal Processors (DSPs), Digital Signal Processors (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general processors, controllers, microcontrollers, and microprocessors.

[0143] 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 device, as well as non-transitory computer-readable media on which such software or instructions, etc., are stored and executable on a device or computer.

Claims

1. A method for implementing a common message in a messenger, performed by a computing device including a processor, comprising: generating a common message page in association with the chat room on the messenger, in which at least one member of the plurality of users in the chat room is designated to edit a common message at the request of a first user; displaying a common message window having common message information including at least management information related to an editing state of the common message in the chat room as a first message; and providing modified common message information on the common message page by editing the common message by the at least one member.

2. The method for implementing a common message according to claim 1, further comprising the step of displaying a common message window in the chat room as a second message, the common message window reflecting the changed management information as a result of the common message being edited by the at least one member.

3. The step of generating the common message page further includes setting an editing authority for the common message for each of the members; 2. The method for implementing a common message according to claim 1, wherein the management information includes member information and work status information indicating a processing status of each member.

4. the modified common message information includes the work status information; The common message realization method according to claim 3, wherein providing the changed common message information to the common message page is to display the member who processed the editing based on the work status information, or to display the processing status for each member.

5. The step of generating the common message page further includes, when at least two of the plurality of users are designated to edit the common message, setting an editing order among the members for the common message; 2. The method for implementing a common message according to claim 1, wherein the management information includes member information and work status information indicating the processing status of each member according to the editing order.

6. The common message realization method described in claim 1, wherein when the member's edit is approval or review of the common message, the changed common message information includes the management information, and the management information is changed according to the processing status due to the member's edit.

7. When the member's edit is a modification of the common message, the modified common message information includes the modified common message and the management information; The method for implementing a common message according to claim 1, wherein providing the modified common message information to the common message page includes associating the member information of the member who modified the common message with the modified common message and displaying it on the common message page.

8. The management information further includes work status information indicating the processing status of each member, The method for implementing a common message according to claim 7, wherein providing the changed common message information to the common message page further includes providing the changed work status information to the common message page in response to a change in work status information of other members other than the member who made the modification.

9. the step of generating the common message page further includes displaying a draft message window including the common message information as a third message on the common message page; the common message information includes the common message and the management information, The method of claim 1 , wherein the draft message window is distinct from a message window that displays chats between the members on the common message page.

10. 10. The common message realization method of claim 9, wherein providing the modified common message information to the common message page includes displaying a draft message window including the modified common message information as a fourth message on the common message page.

11. The method of claim 1 , further comprising the step of sharing the common message in the chat room when the designated member has completed editing the common message.

12. 2. The method for realizing a common message according to claim 1, wherein the step of sharing the common message in the chat room includes displaying a message of the first user or the member who performed the last editing work as the common message in the chat room.

13. A program for executing a common message realization method in a messenger on a computer, The method comprises: generating a common message page associated with the chat room on the message, where at least one member of the plurality of users of the chat room is designated to edit a common message at the request of a first user; displaying a common message window having common message information including at least management information related to an editing state of the common message in the chat room as a first message; and providing modified common message information on the common message page by editing the common message by the at least one member.

14. 1. A computing device implementing a messenger, comprising: a memory for storing at least one instruction; a processor for executing the at least one instruction stored in the memory; The processor: generating a common message page in which at least one member of the plurality of users in the chat room is designated to edit a common message at the request of a first user belonging to the chat room on the messenger; displaying a common message window having common message information including at least management information related to an editing state of the common message as a first message in the chat room; a computing device configured to provide modified common message information to the common message page as a result of the common message being edited by the at least one member;

15. 15. The computing device of claim 14, wherein the processor is further configured to display a common message window in the chat room as a second message, the common message window reflecting changed administrative information as a result of the common message being edited by the at least one member.

16. generating the common message page further includes setting an editing authority for the common message for each of the members; The computing device of claim 14 , wherein the management information includes member information and work status information indicating a processing status for each of the members.

17. the changed common message information is the work status information, Providing the modified common message information on the common message page includes: The computing device of claim 16, wherein the computing device displays a member who has processed the edit, or displays a processing status for each member, based on the work status information.

18. generating the common message page further includes, when at least two of the plurality of users are designated to edit the common message, setting an editing order of the members for the common message; The computing device of claim 14 , wherein the management information includes member information and work status information indicating a processing status for each member according to the editing order.

19. The computing device of claim 14 , wherein if the member's edit is an approval or review of the common message, the modified common message information includes the management information, and the management information is modified according to a processing state due to the member's edit.

20. If the member's edit is a modification of the common message, the modified common message information is the modified common message and the management information; The computing device of claim 14, wherein providing the modified common message information to the common message page includes displaying the modified common message in association with member information of the member who modified the common message on the common message page.

21. The management information further includes work status information indicating the processing status of each member, 21. The computing device of claim 20, wherein providing the modified common message information to the common message page further comprises providing the modified work status information to the common message page in response to a change in work status information of another member other than the modifying member.

22. generating the common message page further includes displaying a draft message window including the common message information on the common message page as a third message; the common message information includes the common message and the management information, The computing device of claim 14 , wherein the draft message window is separate from a message window that displays chat between the members on the common message page.

23. 23. The computing device of claim 22, wherein providing the modified common message information to the common message page includes displaying a draft message window including the modified common message information as a fourth message on the common message page.

24. The computing device of claim 14 , wherein the processor is further configured to share the common message with the chat room by completing editing of the common message by the designated members.

25. 25. The computing device of claim 24, wherein sharing the common message in the chat room includes displaying a message of the first user or the member who made the last edit as the common message in the chat room.

Images