KR20200004911A - Apparatus for managing conference records object and method performing the same - Google Patents

Abstract

The present invention relates to an apparatus for managing a conference record object which comprises: a conference record object creating unit, which receives conference records including the date and time, details, and participants in a conference from a user, being capable of granting a specific authority to the user, and generating a conference record object having a sharing link for an electronic check; and a conference record object sharing unit, which allows the user to designate at least one target for sharing through the specific authority, thereby receiving a request for sharing the conference records on the conference record object and, in accordance with the request for sharing the conference records, which can 1) generate a sharing chat room, in which at least one target for sharing participates and participation is possible through the conference record object, and provide the sharing link, 2) grant an authority to check the conference record object to the at least one target for sharing, and 3) make at least a part of the conference record object to be indicated in a specific area of the sharing chat room, thereby sharing the conference record object.

Description

Apparatus and method for managing meeting minutes {APPARATUS FOR MANAGING CONFERENCE RECORDS OBJECT AND METHOD PERFORMING THE SAME}

The present invention relates to a meeting minutes object management technology, and more particularly, to a meeting minutes object management apparatus and method that can improve the communication efficiency associated with a business meeting by sharing and managing the meeting minutes object based on the chat room.

The Internet messenger corresponds to an application for transferring a message including text or graphics between users, and may be implemented as a chat room engaged by a plurality of users. In one embodiment, the Internet messenger may include a mobile messenger performed in a mobile environment (eg, a mobile phone), and may include, for example, KakaoTalk, Line, WeChat, and Facebook Messenger.

As the number of users who use the Internet messenger is rapidly increasing, applications that are used in a mobile environment are being developed in various ways. Among them, the minutes management program is used by many users.

Korean Patent Registration No. 10-1182535 (registered on September 6, 2012) relates to a conference management system based on an online network, and, based on an online network (eg, an intranet network), a conference call procedure for each conference caller. (E.g., preparation of meeting materials, reservation of necessary resources for proceedings, procedure for convening meeting participants, preparation of meeting minutes and delivery procedures, etc.) Systematic modules that can guide the procedure, computerized modules that can guide the process of preparing non-conference notices and feedbacks by attendees are systematically arranged.

Korean Patent Laid-Open Publication No. 10-2002-0057331 (published on July 11, 2002) relates to an internet conferencing system that provides active communication and convenience among members through the Internet and a method of operating the same. Create a meeting proposal implemented on the web, email the list of meeting proposals to the mobile terminal and the user's computer of the person who registered as a member in the meeting solution, and use the mobile server and web of the meeting solution over the Internet on the mobile terminal and the user's computer. After connecting to the server and logging in as a member, you can connect the mobile server and web server of the solution to the mobile terminal and user computer of the person registered as a member, and the meeting progress window where you can participate through the mail of the mobile terminal and the user computer. To communicate your comments as text data and attachments After conducting an internet meeting by displaying this text data and attachments in the meeting progress window of the mobile solution and web server of the meeting solution, the meeting solution saves the meeting record in progress to the database, and the meeting coordinator The result data is displayed in the conference result window of the mobile server and web server and stored in the database.

Korean Patent Registration No. 10-1182535 (2012.09.06. Registration) Korean Unexamined Patent Publication No. 10-2002-0057331 (published Jul. 11, 2002)

One embodiment of the present invention is to provide a meeting object management apparatus and method that can improve the communication efficiency associated with a business meeting by sharing and managing the meeting minutes object based on the chat room.

An embodiment of the present invention is to provide a meeting minutes object management apparatus and method that can provide a shared link for the electronic inquiry of the meeting minutes object to support sharing the minutes even to non-users.

In an embodiment, the apparatus for managing meeting minutes includes: a meeting minutes object generation unit configured to receive a meeting minutes including meeting contents from a user and generate a meeting minutes object associated with the user, and to the meeting minutes object including at least one shared person from the user. And a meeting minutes object sharing unit associated with the meeting minutes object and generating a shared chat room associated with the at least one subject to share the meeting minutes object when the request for sharing the meeting minutes is received.

The meeting minutes object generation unit may grant or release the right to modify the generated meeting minutes object to the user according to the presence or absence of a shared chat room associated with the generated meeting minutes object.

The meeting object generation unit may provide a sharing link for an electronic inquiry of the meeting object when a sharing link request associated with the meeting object is received from the user.

The meeting minutes object generation unit may determine the validity of the shared link based on the validity period or the number of validity included in the shared link request.

The meeting minutes object generating unit generates a reservation chat room associated with the at least one meeting expected participant at a specific time before the meeting date and time if the received meeting minutes further include a meeting minutes reservation request including at least one meeting expected participant and a meeting date and time. To provide a notification message through the reservation chat room.

When the meeting object generation unit receives a response from the user to the notification message provided through the reserved chat room, the user may grant the user the right to modify the meeting minutes regardless of the presence of the reserved chat room associated with the meeting object.

The meeting minutes object generation unit requests a modification to the meeting minutes object to a user who is granted the correcting authority at a specific time after the meeting date, and when the meeting minutes object is modified by the corresponding user, the reservation chat room. You can inform.

The meeting minutes object sharing unit grants the at least one subject to be inquired about the meeting minutes object according to the meeting minutes sharing request, and displays the at least one portion of the meeting minutes object in a specific area of the shared chat room. Can share.

The meeting minutes object sharing unit may further receive at least one meeting minutes sharing request about the meeting minutes object from at least one user who has the inquiry right, and the at least one subject included in each of the at least one meeting minutes sharing request. The presence or absence of a previously created shared chat room may be detected to determine whether to reshare the meeting minutes object.

The meeting minutes object sharing unit includes the at least one non-user based on a received e-mail address or a mobile number associated with each of the at least one non-user, when the received meeting minutes sharing request includes at least one non-user designated as a share target. The user may be provided with a shared link for electronic inquiry of the minutes object.

When the specific chat participant participating in the shared chat room exits the shared chat room, the meeting minutes object sharing unit may release the inquiry right on the meeting minutes object granted to the specific chat participant.

The meeting minutes object sharing unit releases the association between the meeting minutes object and the shared chat room or the reserved chat room when all chat participants participating in the shared chat room or the reserved chat room exit the corresponding shared chat room or the reserved chat room, and whether there is a chat room associated with the meeting minutes object. It is possible to determine whether to delete the minutes from the memory according to.

The meeting minutes object management apparatus may receive a task including a task content, a task creator, and a task processor through the shared chat room to generate a task object associated with the shared chat room, and may include text or media in a message thread associated with the shared chat room. The apparatus may further include a business object processing unit for adding the business object corresponding to an independent business message object distinguished from the message object as a business message.

The work object processing unit may update a predetermined work processing state on the work processing diagram and update the message thread by reflecting a request from one of the work creator and the work processor and a response from the other.

The meeting object sharing unit may provide a list of business objects related to at least one business object generated in association with the shared chat room through the shared chat room.

Among the embodiments, the meeting object management method is performed by the meeting object management apparatus connected to at least one user terminal. The meeting minutes object management method includes: a meeting minutes object generation step of receiving a meeting minutes including meeting contents from a user and generating a meeting minutes object associated with the user, and a meeting minutes sharing request for the meeting minutes object including at least one subject from the user. And a meeting minutes object sharing step associated with the meeting minutes object to generate a shared chat room associated with the at least one share object to share the meeting minutes object.

The disclosed technique can have the following effects. However, since a specific embodiment does not mean to include all of the following effects or only the following effects, it should not be understood that the scope of the disclosed technology is limited by this.

Apparatus and method for managing meeting minutes object according to an embodiment of the present invention can improve the communication efficiency associated with the business meeting by sharing and managing the meeting minutes object based on the chat room.

Apparatus and method for managing meeting minutes object according to an embodiment of the present invention can support sharing minutes for non-users by providing a sharing link for electronic inquiry of meeting minutes object.

1 is a view for explaining a meeting object management system according to an embodiment of the present invention.
FIG. 2 is a block diagram illustrating an apparatus for managing meeting minutes in FIG. 1.
3 is a flowchart illustrating a process of sharing the minutes object by the minutes object management apparatus of FIG.
FIG. 4 is a diagram illustrating an example of a process of receiving the minutes by the minutes object messaging agent installed in the user terminal by the minutes object management apparatus of FIG. 1.
FIG. 5 is a diagram illustrating an example of a process of generating a meeting object through the meeting object object messaging agent installed in a user terminal by the apparatus for managing meeting minutes in FIG. 1.
FIG. 6 is a diagram illustrating an embodiment of a process of sharing the minutes object object through the minutes object messaging agent installed in the user terminal.

Description of the present invention is only an embodiment for structural or functional description, the scope of the present invention should not be construed as limited by the embodiments described in the text. That is, since the embodiments may be variously modified and may have various forms, the scope of the present invention should be understood to include equivalents capable of realizing the technical idea. In addition, the objects or effects presented in the present invention does not mean that a specific embodiment should include all or only such effects, the scope of the present invention should not be understood as being limited thereby.

On the other hand, the meaning of the terms described in the present application should be understood as follows.

Terms such as "first" and "second" are intended to distinguish one component from another component, and the scope of rights should not be limited by these terms. For example, the first component may be named a second component, and similarly, the second component may also be named a first component.

When a component is referred to as being "connected" to another component, it should be understood that there may be other components in between, although it may be directly connected to the other component. On the other hand, when a component is referred to as being "directly connected" to another component, it should be understood that there is no other component in between. On the other hand, other expressions describing the relationship between the components, such as "between" and "immediately between" or "neighboring to" and "directly neighboring to", should be interpreted as well.

Singular expressions should be understood to include plural expressions unless the context clearly indicates otherwise, and terms such as "comprise" or "have" refer to a feature, number, step, operation, component, part, or feature thereof. It is to be understood that the combination is intended to be present and does not exclude in advance the possibility of the presence or addition of one or more other features or numbers, steps, operations, components, parts or combinations thereof.

In each step, an identification code (e.g., a, b, c, etc.) is used for convenience of explanation, and the identification code does not describe the order of each step, and each step clearly indicates a specific order in context. Unless stated otherwise, they may occur out of the order noted. That is, each step may occur in the same order as specified, may be performed substantially simultaneously, or may be performed in the reverse order.

The present invention can be embodied as computer readable code on a computer readable recording medium, and the computer readable recording medium includes all kinds of recording devices in which data can be read by a computer system. . Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. Generally, the terms defined in the dictionary used are to be interpreted as being consistent with the meaning in the context of the related art, and should not be interpreted as having an ideal or excessively formal meaning unless explicitly defined in the present application.

43 is a diagram illustrating a meeting minutes object management system according to an embodiment of the present invention.

Referring to FIG. 1, the meeting object management system 100 includes a meeting object management apparatus 110 and a user terminal 120, which may be connected through a network.

The meeting object management apparatus 110 may be connected to the user terminal 120 to receive the meeting minutes, and correspond to a computing device capable of managing the meeting minutes object based on the received meeting minutes. The minutes object management apparatus 110 may manage at least one member group in which a user associated with the user terminal 120 is included as a member. The minutes object management apparatus 110 may manage message threads grouping messages transmitted from member groups configured through at least one user terminal 120, and in one embodiment, the message threads are sent to a chat room of an Internet messenger. Can be implemented.

The user terminal 120 may correspond to a computing device connected to the meeting object management apparatus 110 and may be implemented as, for example, a desktop, a notebook, a tablet PC, or a smartphone. In one embodiment, the first user terminal 120a may correspond to a mobile terminal, and may be connected to the work object processing apparatus 110 through cellular communication or Wi-Fi communication. In another embodiment, the second user terminal 120b may correspond to a desktop and may be connected to the meeting object management apparatus 110 through the Internet.

FIG. 2 is a block diagram illustrating an apparatus for managing meeting minutes in FIG. 1.

Referring to FIG. 2, the apparatus for managing meeting minutes 110 may include a meeting object object generation unit 210, a meeting object object sharing unit 220, a business object processing unit 230, a memory unit 240, and a controller 250. Can be interconnected.

The meeting record object generating unit 210 may receive a meeting record including the meeting contents from the user. In one embodiment, the minutes may further include at least one of the meeting name, the date and time of the meeting and at least one meeting participant. More specifically, the meeting minutes object generation unit 210 may receive the minutes through the meeting minutes object messaging agent installed in the user terminal 120 associated with the user. In an embodiment, when the minutes object messaging agent is installed in the user terminal 120 by the user, the user terminal 120 and the minutes object management device 110 are connected to each other through a network with the approval of the user terminal 120. Corresponds to the agent program, which is software that is possible In one embodiment, the minutes object management apparatus 110 may provide the minutes object messaging agent to the user terminal 120 through a web page operated by the same operator, through an online app store operated by another operator You can also provide

When a meeting record is received from a user, the meeting object generation unit 210 generates a meeting record object associated with the corresponding user. In one embodiment, the meeting minutes object may include at least one of a meeting name, meeting date and time, meeting contents, and at least one meeting participant classified as a user or a non-user included in the received meeting minutes.

The meeting minutes object generating unit 210 may grant or release the right to modify the generated meeting minutes object according to the presence or absence of a shared chat room associated with the generated meeting minutes object. In one embodiment, when a meeting object object associated with a specific user is created, the meeting object object generator 210 may grant the user the right to modify the meeting minutes object, and the meeting minutes object according to a specific user's request for sharing the meeting minutes. When an associated shared chat room is opened, you can revoke the edit rights granted to that user.If there is no shared chat room associated with the meeting minutes object (for example, the shared chat room has been deleted by the user or participated in the shared chat room) If all participants leave the chat room), the user can be given permission to modify the meeting minutes object again.

The agenda object generating unit 210 may provide the generated agenda object to at least one specific user who has the authority to inquire about the corresponding agenda object through the agenda object messaging agent. In one embodiment, the meeting minutes object generation unit 210 may preferentially grant the right of inquiry to the meeting minutes object only to the user (the user who provided the minutes) associated with the meeting minutes object in the process of generating the meeting minutes object. When the meeting minutes object is shared by the user in the step of, the inquiry authority for the meeting minutes object may be granted to at least one specific user designated as a share target in the sharing process.

When the meeting object generation unit 210 receives a sharing link request associated with the meeting object object from the user, the meeting record object generation unit 210 may provide a sharing link for an electronic inquiry of the corresponding meeting record object. In one embodiment, the meeting object generation unit 210 may receive a request for generating a shared link associated with the meeting minutes in the process of receiving the meeting minutes from the user, or separately after generating the meeting minutes object according to the meeting minutes.

In one embodiment, the meeting minutes object generation unit 210 may generate a sharing link corresponding to a hyperlink connecting a web documented meeting minutes reading document for viewing the corresponding meeting minutes object according to the sharing link request, and the generated sharing The link can be stored in association with the corresponding minutes object. In one embodiment, the meeting minutes object generation unit 210 may provide a shared link of the meeting minutes object through a shared chat room associated with the meeting minutes object.

Accordingly, in one embodiment, the meeting minutes object generation unit 210 may support a non-subscriber who has not subscribed to the meeting minutes object messaging agent to view the web documented minutes view document on the web connected through a shared link. Subscribers subscribed to the object messaging agent can also access the minutes view document through the share link to print, manage minutes, etc.

The minutes recording unit 210 may determine the validity of the shared link based on the validity period or the number of valid times included in the shared link request. In one embodiment, the meeting minutes object generation unit 210 may receive the validity period or the validity number of the shared link to be generated in the process of receiving the shared link request, and according to the received validity period or the validity count You can limit the validity of an electronic query of an object. For example, when the shared link request includes a validity period of three months or ten valid times, the meeting minutes object generation unit 210 performs an electronic inquiry of the meeting minutes object for three months from when the shared link request is received. Alternatively, the electronic query of the minutes can be restricted until the total of 10 cumulative views are counted. The minutes object generation unit 210 may set a default value (for example, an expiration date = 1 month) to the validity period or the validity frequency, and is selected by the user within a specific validity candidate or within a specific validity range. The validity period or the number of validity periods may be received, and even after the validity is determined, the setting may be changed so that the validity is not determined according to the user's request (for example, validity period = unlimited).

When the meeting minutes object is electronically inquired through the sharing link, the meeting minutes object generation unit 210 may allow the user terminal 120 associated with the user who requested the creation of the corresponding sharing link to check whether the corresponding meeting minutes object is electronically searched.

In an embodiment, the minutes object generator 210 may further provide an inquiry password generated in association with the corresponding shared link in the process of providing the shared link. Here, the inquiry password corresponds to a password for the electronic inquiry of the web documented minutes reading document accessible through the corresponding shared link. The minutes recording unit 210 may randomly generate the inquiry password based on a password generation algorithm or generate a specific password specified by the user.

Minutes object generation unit 210 is a reservation chat room associated with the at least one meeting expected participant at a specific time before the meeting date and time if the received minutes further includes the meeting minutes reservation request and the meeting date and time including at least one meeting expected participant You can create a notification message through the reservation chat room.

More specifically, the meeting minutes object generation unit 210 may generate a meeting minutes object by receiving a meeting minutes reservation request including at least one conference expected participant and a meeting minutes further including a meeting date and time from a user in the process of receiving the minutes. At least one prospective participant received at a specific point in time prior to the meeting date (for example, one hour before the user or three hours by default) can create an associated reserved chat room as a chat participant, You can send a reminder message (for example, the meeting starts in 1 hour ') via the scheduled chat room about the meeting schedule.

In one embodiment, the meeting minutes object generation unit 210 may be a subscriber (eg, a subscriber of the meeting minutes object messaging agent that may be connected through the minutes object messaging agent) or a non-subscriber (eg, the minutes object) under the control of a user. A meeting minutes including at least one conference expected participant may be received. For example, the meeting minutes object generation unit 210 associates and stores user information associated with the user as a meeting participant when the received meeting expected participant is classified as a user, and, in the case of a non-user, associates with the corresponding non-user. Further received e-mail addresses or cell phone numbers can be associated and stored as conference participants.

Meeting minutes object generation unit 210 provides a notification message to the meeting prospective participants classified as subscribers among the at least one meeting expected participants through a reservation chat room, and stored in association with each of the expected meeting participants classified as non-subscribers. Notification messages can be sent via a separate email agent or messaging agent based on email address or mobile phone number.

When the meeting object generation unit 210 receives a response to the notification message provided through the reservation chat room from the user, the meeting minutes object generation unit 210 may grant the user the right to modify the meeting minutes object regardless of the presence of the reservation chat room associated with the meeting minutes object. For example, the meeting minutes object generation unit 210 grants the right to modify the meeting minutes object when the corresponding user (the user who created the minutes object) responds to the meeting content creation button in the notification message provided through the reservation chat room. It can support the completion of the meeting contents in the meeting minutes object, so that the corresponding chat room can facilitate the communication of the meeting from the start of the meeting to the end of the meeting.

The meeting object generation unit 210 requests the user authorized to modify the meeting minutes at a specific time after the meeting date, and if the meeting minutes object is modified by the user, the meeting chat room notifies about the update. Can be. For example, the meeting minutes object generation unit 210 is a notification message for requesting completion of meeting minutes to the associated chat room at an hour after the hour set by the user from the meeting date or 3 hours after the default value (for example, 'complete minutes' You can request the creation of meeting minutes by sending a pop-up message via the meeting minutes object messaging agent.

In the above embodiment, the meeting minutes object generation unit 210 may calculate the period (t) of the meeting minutes creation request to be sent to the user in consideration of the meeting date and time and the number of expected meeting participants based on Equation 1 below. According to the calculated period t, a notification message for requesting the preparation of the minutes may be transmitted to the corresponding user. For example, the meeting minutes object generation unit 210, the time of calculation, April 10, 2017, 5 pm, the scheduled meeting date specified by the user, April 10, 2017, 10 am, the number of the expected meeting participants 5 And c ₀ = 2 (normally notified) to calculate t = 4 (hours) by applying d = 5 (hours), and send a pop-up message regarding a request for creating a minutes every four hours according to the calculated value. Can be. Accordingly, the minutes object generation unit 210 may remind the user about the minutes of creation of the minutes more frequently, the longer the number of meeting minutes has been delayed from the expected date and time of the meeting, the more the number of expected meeting participants is.

[Equation 1]

은 내부의 값에 관해 소수점 이하의 값을 올리는 연산을 의미하며, c₀=0 또는 d=0인 경우에는 알리지 않는 것으로 결정하는 것을 가정함)(Where d is the time difference (time) between the time of calculation and the expected meeting time specified by the user, n is the number of expected meeting participants (persons) specified by the user, and c ₀ is the user or Corresponds to the alert frequency setting index that can be specified by the designer (for example, 0: alerts X, 1: frequent alerts, 2: normal, 3: slow alerts),

Refers to an operation that raises the value below the decimal point with respect to the internal value, and assumes that c ₀ = 0 or d = 0 is not informed.

The meeting record object generating unit 210 may manage at least one meeting record object generated in association with the corresponding user for each user in association with a specific folder. More specifically, the meeting minutes object generating unit 210 may generate at least one folder by the user, and associates the meeting minutes object associated with the user and the shared chat room associated with the meeting minutes object with the specific folder under the control of the user. Can be stored. When a particular folder is selected by the user, the meeting record object generating unit 210 may provide a list of meeting minutes associated with the selected specific folder and a shared chat room associated with the meeting minutes object. In one embodiment, the reminder associated with the shared chat room may be provided. It can provide more business object list. Here, the reminder work object list may include a work summary and a work object access link for a work object determined to be necessary for reminding among work objects created through the corresponding shared chat room.

The minutes object generating unit 210 may manage, including, add, modify, delete, and update the at least one folder from a user through the minutes object messaging agent. For example, the meeting minutes object generation unit 210 may change a specific meeting minutes object associated with a specific folder to be associated with another specific folder according to a user's request, and receive the meeting minutes from a user through a specific folder or pre-generated meeting minutes object. It may also receive a sharing request for.

When the meeting object sharing unit 220 receives a meeting sharing request for a meeting object including at least one share from a user, the meeting record object sharing unit 220 generates a shared chat room associated with the meeting record object and associated with the at least one share. Share. More specifically, the meeting minutes object sharing unit 220 may generate a shared chat room associated with at least one share target designated by the user according to the meeting minutes sharing request received from the user, and the meeting minutes object may be added to the generated meeting chat room. The contents of the meeting and at least one meeting participant may be displayed to share the meeting minutes object with at least one person participating in the shared chat room.

Meeting minutes object sharing unit 220 grants the at least one share target to the corresponding meeting minutes object according to the request to share the minutes, and to display at least a portion of the meeting minutes object in a specific area of the shared chat room You can share objects. More specifically, the meeting minutes object sharing unit 220 may grant the inquiry authority regarding the meeting minutes object only to the specific user who created the meeting minutes before the specific meeting minutes object is shared, and associated with each particular meeting minutes object. At least one share target may further be given the corresponding inquiry right. The meeting minutes object sharing unit 220 displays at least some of the meeting name, meeting date, meeting contents, and at least one meeting participant included in the corresponding meeting minutes object in a specific upper area of the shared chat room generated according to the meeting minutes sharing request. It can be shared about an object.

The minutes meeting object sharing unit 220 may further receive at least one meeting minutes sharing request about the meeting minutes object from at least one user who has the authority to inquire about the minutes object, and is included in each of the at least one meeting minutes sharing request. The presence or absence of a pre-created shared chat room associated with at least one shared object may be detected to determine whether to reshare the meeting minutes object. More specifically, the meeting minutes object sharing unit 220 may generate a meeting minutes object associated with the first user based on the meeting minutes received from the first user, and may grant only the first user an inquiry permission regarding the meeting minutes object. 1 When a user receives a meeting sharing request including a second, third, and fourth user as a share object with respect to the corresponding meeting minutes object, the second, third, and fourth users are given permission to inquire about the meeting minutes object. A shared chat room associated with the second, third, and fourth users may be created and shared about the meeting minutes object. In a later step, the meeting minutes object sharing unit 220 further includes at least one or more meeting minutes sharing request including at least one person with respect to the meeting minutes object from at least one of the first, second, third and fourth users. If there is no shared chat room that is received and associated with the corresponding meeting minutes object and the at least one share target person is associated as a chat participant, the shared chat room may be generated and reshared about the meeting minutes object. Meeting minutes object sharing unit 220 includes a different minutes of sharing about the meeting minutes object from the users authorized to view through the sharing including the first share and at least one reshare for the first share. The sharing request can be received multiple times to share the meeting minutes object with different people.

Whenever a meeting minutes sharing request is received from a user who has permission to view a particular minutes object, there is no shared chat room associated with that particular minutes object and with the same chat participants involved in the meeting minutes sharing request. If not, you can create more shared chat rooms that are associated with that particular meeting object and are associated as chat participants.

Meeting minutes object sharing unit 220 is received in association with each of the at least one non-user if the received meeting minutes sharing request includes at least one non-user (for example, subscribers of the meeting minutes object messaging agent) designated as a share target Based on the e-mail address or the mobile phone number, the message may be provided to the at least one non-user including a sharing link for an electronic inquiry of the meeting minutes object. In one embodiment, meeting minutes object sharing unit 220 is based on additional information (eg, email address, mobile phone number, etc.) associated with the at least one non-user stored as a share in the process of receiving the meeting minutes sharing request. Meeting minutes can also be shared with non-users by sending an electronic message containing a shared link through a separate messaging agent (eg, an email agent or a text messaging agent).

The meeting record object sharing unit 220 may release the inquiry right regarding the meeting record object assigned to the specific chat participant when the specific chat participant participating in the shared chat room leaves the shared chat room.

Meeting minutes object sharing unit 220 When all the chat participants participating in the shared chat room or the reserved chat room leave the shared chat room or the reserved chat room, the association between the meeting minutes object and the shared chat room or the reserved chat room is released, and the chat room associated with the meeting minutes object is disconnected. It is possible to determine whether to delete the meeting minutes object from the memory depending on the presence or absence. For example, the meeting minutes object sharing unit 220 may delete all the specific meeting minutes object by confirming that there are no chat rooms associated with the meeting minutes object when all the chat participants leave all chat rooms associated with the specific meeting minutes object.

The business object processor 230 may receive a task including a task content, a task creator, and a task processor through a shared chat room or a reserved chat room, generate a task object associated with the chat room, and perform a task object operation on the corresponding message thread. Can be processed. In one embodiment, the business object processing unit 230 may receive a task from the user terminal 120 associated with the user participating in the chat room through the shared chat room or the reservation chat room that the meeting minutes object in the meeting minutes object messaging agent is shared Based on the received task, a task object including at least one of a task content, task creator, task processor, task deadline, and evaluation reservation score may be generated, and the task object created in the message thread associated with the chat room may be created. You can add it as a message.

Here, the task creator corresponds to the user associated with the user terminal 120 that created the task, the task processor corresponds to the user designated as the target to process the task by the task creator, the evaluation reservation score is the task When is completed, it means the maximum upper limit of the evaluation score that can be evaluated by the task creator. Accordingly, the task creator can instruct or evaluate the task handler through the task object represented by the task message.

In one embodiment, each of the task creator and task processor may correspond to a chat participant participating in the corresponding shared chat room or reservation chat room. In another embodiment, the business processor may not correspond to a chat participant participating in the shared chat room or the reservation chat room, in which case, the business object processing unit 230 automatically assigns a specific user designated as the business processor to the chat room or You can invite them with the approval of the task creator.

The business object processing unit 230 may update a predetermined work processing state and update an associated message thread in the work processing diagram by reflecting a request from one of the work creator and the work processor and a response from the other. In one embodiment, the business object processing unit 230 may receive a work-related response from the task creator or the task processor through a control interface relating to the business object of the meeting minutes object messaging agent.

Here, the work-related response corresponds to a response about a business object that can be answered from a task creator or a task processor, and in one embodiment, a task acknowledgment, task completion response, and task according to the current task status of the task object. It may include at least one of the evaluation response. When receiving the work related response, the work object processor 220 may determine a current work processing state and update an associated message thread. For example, the work object processing unit 220 may update the current work processing state to 'working' state through a work acknowledgment with respect to a work object in which the current work processing state is 'new' state. In response, the work object in the 'in progress' state can be updated to the 'done' state, and in the work evaluation response, the work object in the 'done' state can be updated to the 'complete' state. The business object processing unit 220 provides the updated business object as a business message through the associated message thread whenever the current business process status is changed, thereby providing the participants of the chat room with the specific meeting minutes and the current work of the corresponding business object. The processing state can be recognized.

In one embodiment, the meeting minutes object sharing unit 220 provides the at least one chat participant participating in the shared chat room or the reserved chat room with a list of business objects related to the chat room and at least one business object generated in association with the chat room. can do. For example, the meeting minutes object sharing unit 220 may provide a chat participant participating in a chat room associated with a specific meeting minutes object through the meeting minutes object messaging agent to provide an interface for inquiring about a business object generated through the chat room. In addition, the interface may provide a list of work objects related to the related work object and a link for searching the work object. The meeting minutes object sharing unit 220 may provide a list of business objects associated with the chat room to the particular user when a specific user is invited to the chat room by the chat participant. Meeting minutes object sharing unit 220 may filter and provide only the business object associated with the user of the business object associated with the chat room.

The memory unit 240 may store data used throughout the operation of the minutes object management apparatus 110 and may include a user memory area, the minutes object memory area, a message thread memory area, and a work object memory area. These memory regions may be implemented as nonvolatile memories and may be implemented to be connected through hyperlinks.

The user memory area is associated with user information. Here, the user information may include at least one of a user's name (conversation name), a messenger ID, a password, a member group belonging to a member, a related member list, and work evaluation point information.

The minutes object memory area can be accessed through user information and associated with the minutes object. In one embodiment, the meeting minutes object memory area associated with a particular meeting minutes object may be accessed through user information associated with each of the particular user who created the particular meeting minutes object and at least one user authorized to view that particular meeting minutes object. have.

The message thread memory area is associated with the message thread associated with the meeting object. In one embodiment, the message thread memory area may include a shared message thread memory area associated with the shared chat room and a reserved message thread area associated with the reserved chat room. The message thread memory area associated with a particular message thread associated with a particular shared chat room may be accessed via user information, depending on whether or not there is permission to query the associated specific meeting minutes object. The work object memory area can be accessed through the message thread and associated with the work object.

The controller 250 may control the overall operation of the minutes object management apparatus 110, and may be configured between the minutes object generating unit 210, the minutes object sharing unit 220, the work object processing unit 230, and the memory unit 240. You can control the data flow. In an embodiment, the controller 250 may be implemented as a central processing unit (CPU) of the meeting object management apparatus 110.

3 is a flowchart illustrating a process of sharing the minutes object by the minutes object management apparatus of FIG.

In FIG. 3, the meeting record object generation unit 210 receives a meeting record including meeting contents from a user and generates a meeting record object associated with the corresponding user (step S310). When the meeting minutes object sharing unit 220 receives a meeting sharing request regarding a meeting object object including at least one share object from the user, the meeting minutes object sharing unit 220 creates a shared chat room associated with the meeting object object and associated with the at least one share object. The object is shared (step S320).

In one embodiment, the minutes object management apparatus 110 may share and manage the minutes object based on the chat room to improve the communication efficiency associated with the business meeting.

FIG. 4 is a diagram illustrating an example of a process of receiving the minutes by the minutes object messaging agent installed in the user terminal by the minutes object management apparatus of FIG. 1.

In FIG. 4, the minutes object management apparatus 110 may provide the minutes object creation interface 400 through the minutes object messaging agent installed in the user terminal 120, and from the user through the minutes object generation interface 400. The minutes can be received to create the minutes object.

Meeting minutes object generation interface 400 is the author display field (410), storage folder check box (420), meeting name input box (430), meeting date and time check box (440), reservation notification selection menu 450, direct sharing selection menu (460) It may include a sharing link creation menu selection menu 470, a meeting content input field 480, and a file upload menu 490.

Minutes object management apparatus 110 may display the user information associated with the user who is currently creating the minutes through the creator display field 410, the minutes to be generated according to the current meeting minutes through the storage folder check box 420 Receive a user selection for a folder to associate and store objects, receive a meeting minutes title from the user via the meeting name input field 430, meetings that have or will be in progress through the meeting date check box 440 Can receive the schedule of.

The minutes object management apparatus 110 may receive a minutes reservation request by the user through the reservation notification selection menu 450. More specifically, the minutes object management apparatus 110 may receive at least one conference expected participant selected by the user and divided into subscribers through the subscriber expected participant check box 452, the non-subscriber expected participant input field 454 Via at least one conference participants entered by the user and separated by the non-subscriber and the email address associated with the non-subscriber can be received. The meeting record object managing apparatus 110 may automatically release the reservation notification selection menu 450 when the meeting date and time selected through the meeting date and time check box 440 correspond to the past based on the current time.

The minutes object management apparatus 110 may receive whether to immediately share the minutes object to be generated according to the minutes through the direct share selection menu 460. The minutes object management apparatus 110 may automatically release the direct sharing selection menu 460 when the reservation notification selection menu 450 is selected by the user. Meeting minutes object management apparatus 110 may be provided to add a share target selection menu that can further receive at least one share target when the direct share selection menu 460 is selected by the user, and through the share target selection menu At least one sharing party information classified as a subscriber or a non-subscriber may be received.

The meeting minutes object management apparatus 110 may receive whether to allow the generation of a shared link about the corresponding meeting minutes object from the user through the sharing link generation selection menu 470, and the meeting minutes object management apparatus 110 may set a meeting. The content input field 480 may receive a meeting content regarding the minutes from the user, and the file upload menu 490 may receive a file to be stored in association with the minutes.

FIG. 5 is a diagram illustrating an example of a process of generating a meeting object through the meeting object object messaging agent installed in a user terminal by the apparatus for managing meeting minutes in FIG. 1.

In FIG. 5, the minutes object management apparatus 110 may provide a minutes object to a user through the minutes minutes providing interface 500 of the minutes object messaging agent installed in the user terminal 120.

The meeting minutes providing interface 500 includes a chat room entry link 510, a work object access link 520, a favorite button 530, a meeting minutes sharing button 540, a work object creation button 550, and a meeting minutes display field 560. It may include.

Meeting minutes object management device 110 may receive a chat room list providing request associated with the meeting minutes object from the user through the chat room entry link 510, the entire chat room (associated chat room generated in association with the corresponding meeting minutes object according to the reception) And a reservation chat room), information regarding at least one chat room associated with a user among all chat rooms, and an entry link.

Meeting minutes object management apparatus 110 may receive a request to provide a list of business objects associated with the meeting minutes object through the business object access link 520, at least generated by the meeting chat object is shared through the shared chat room It can provide information and entry link about one business object.

The minutes object management apparatus 110 may receive a favorite request associated with the corresponding minutes object through the favorite button 530, and give priority to the minutes object according to the reception to be displayed in the user menu first. You can do it.

The minutes object management apparatus 110 may receive a meeting minutes sharing request about the meeting minutes object and at least one shared person from the user through the meeting minutes sharing button 540, and are associated with the corresponding minutes object according to the reception of the minutes. One sharer can create an associated shared chat room as a chat participant and share that meeting minutes object.

Meeting minutes object management apparatus 110 may receive a work object creation request through the work object creation button 550 and immediately generate a work object associated with the meeting minutes object according to the reception.

The minutes object management apparatus 110 may display the contents of the meeting in the corresponding minutes object through the minutes display field 560.

FIG. 6 is a diagram illustrating an embodiment of a process of sharing the minutes object object through the minutes object messaging agent installed in the user terminal.

In FIG. 6, the meeting minutes object management apparatus 110 may share the meeting minutes object through the chat room interface 600 of the meeting minutes object messaging agent installed in the user terminal 120.

The chat room interface 600 includes the main minutes display information column 610, the access link or sharing link providing menu 620, message display field 630, business object creation button 640, multimedia upload menu 650, file upload A menu 660, a chat message input field 670, and a work object progress display field 680 may be included.

Meeting minutes object management device 110 may display the meeting name, the meeting date and time and the contents of the meeting included in the meeting minutes object associated with the chat room through the meeting minutes key information display field 610, according to the user's request (for example , 'More details') can be displayed for the entire contents of the meeting minutes object or connected to provide the meeting minutes object through the meeting minutes providing interface 500.

Meeting minutes object management device 110 is an access link associated with the corresponding minutes (eg, a link that can be accessed through the meeting minutes object messaging agent) or shared link (for example, through the access link or shared link providing menu 620). For example, it may receive a request for provision of a link (accessible on the web without passing through the meeting minutes object messaging agent), and provide a previously created access link or a shared link according to the reception, or a new access if there is no previously created link. Links or shared links can be created and provided.

The minutes object management apparatus 110 may provide a general chatting message represented by a business object and a conversation message represented by a business message through the message display field 630.

Meeting minutes object management device 110 receives a request for the creation of the meeting minutes object and the business object associated with the chat room through the business object creation button 640, the business object including a task creator, a business processor and the work content according to the reception Can be generated.

Meeting minutes object management device 110 may receive the upload request for the multimedia and files through the multimedia upload menu 650 and the file upload menu 660, respectively, and receives the file according to the received message associated with the chat room You can add to the thread as a multimedia message object or provide an access link.

Meeting minutes object management device 110 may receive a conversation from the user through the chat message input field 670, and adds the received conversation as a chat message to the message thread through a chat message between users participating in the chat room. Can support communication.

Meeting minutes object management device 110 may display the progress of the work object generated through the chat room through the work object progress display field 680, and provides a link to access the work object according to the user request can do.

Although described above with reference to a preferred embodiment of the present application, those skilled in the art various modifications of the present application without departing from the spirit and scope of the invention described in the claims below And can be changed.

100: Minutes Object Management System
110: meeting minutes object management device 120: user terminal
210: meeting minutes object generation unit 220: meeting minutes object sharing unit
230: business object processing unit 240: memory unit
250: control unit

Claims (13)

A meeting object object generation unit for receiving meeting minutes including meeting dates, meeting contents, and meeting participants from a user, and granting specific rights to the user, and generating meeting minutes objects having a shared link for an electronic inquiry; And
Receive a meeting minutes sharing request for the meeting minutes object by allowing the user to designate at least one share object through the specific authority, and in accordance with the meeting minutes sharing request: 1) participated by the at least one share person and the meeting minutes object Create a shared chat room that can be participated through and provide the sharing link; and 2) grant the inquiry permission to the at least one subject to the meeting minutes object; and 3) at least a portion of the meeting minutes object in a particular area of the shared chat room. And a meeting minutes object sharing unit for sharing the meeting minutes object.
The method of claim 1, wherein the meeting object generating unit
The meeting minutes object management apparatus, characterized in that granting or canceling the right to modify the generated meeting minutes object according to the presence or absence of a shared chat room associated with the generated meeting minutes object.
The method of claim 2, wherein the meeting object generating unit
The meeting minutes object management apparatus, characterized in that for determining the validity of the shared link based on the validity period or the number of validity included in the shared link request.
The method of claim 1, wherein the meeting object generating unit
If the received minutes further includes a meeting reservation request including at least one meeting expected participant and a meeting date and time, the reservation chat room is generated by creating a reservation chat room associated with the at least one meeting expected participant at a specific time before the meeting date and time. Minutes object management device, characterized in that providing a notification message through.
The method of claim 4, wherein the meeting object generating unit
Meeting minutes object management device, characterized in that if the user receives a response to the notification message provided through the reservation chat room, the user is given the right to modify the meeting minutes object regardless of the presence of the reservation chat room associated with the meeting minutes object .
The method of claim 5, wherein the meeting object generating unit
At a certain time after the meeting date and time, the user who has been granted the right to modify the request for the modification of the meeting minutes object, and if the meeting minutes object is modified by the user, characterized in that notified about the update through the reservation chat room. Minutes object management device.

The method of claim 1, wherein the meeting object sharing unit
The at least one meeting minutes sharing request for the meeting minutes object may be further received from the at least one user who has the inquiry authority, and the pre-generated association is made with at least one share included in each of the at least one meeting minutes sharing request. Meeting minutes object management apparatus characterized in that it detects the presence of a shared chat room to determine whether to re-share the minutes object.
The method of claim 1, wherein the meeting object sharing unit
The meeting minutes object to the at least one non-user based on an e-mail address or a mobile number received in association with each of the at least one non-user, if the received minutes sharing request includes at least one non-user designated as a share target. Meeting minutes object management device, characterized in that for providing a shared link for the electronic query of the.
The method of claim 1, wherein the meeting object sharing unit
The meeting minutes object management apparatus, characterized in that when the specific chat participants participating in the shared chat room exits the shared chat room, the inquiry authority for the meeting minutes object granted to the specific chat participants.
The method of claim 1, wherein the meeting object sharing unit
When all the chat participants participating in the shared chat room or the reserved chat room leave the shared chat room or the reserved chat room, the association record is released from the meeting chat object and the shared chat room or the reserved chat room, and the meeting minutes object is released according to the presence or absence of a chat room associated with the meeting chat object. And determining whether or not to delete from the memory.
The method of claim 1,
The shared chat room may receive a task including a task content, a task creator, and a task processor to generate a task object associated with the shared chat room, and may be independent of a text or media message object in a message thread associated with the shared chat room. And a business object processing unit for adding the business object corresponding to the business message object as a business message.
The method of claim 11, wherein the business object processing unit
And reflecting a request from one of the task creator and the task handler and a response from the other, updating a predetermined task state and updating the message thread.
The method of claim 11, wherein the meeting object sharing unit
The meeting minutes object management device, characterized in that for providing a list of the work object for the at least one work object generated in association with the shared chat room through the shared chat room.

Images