KR102140453B1 - Meeting management method and meeting management system using the method - Google Patents

Abstract

Disclosed is a meeting management method capable of automatically generating a virtual account corresponding to a meeting and providing a simple payment service, and a meeting management system using the meeting. Such a meeting management method relates to a meeting management method performed in a meeting management server capable of sending and receiving signals to and from at least one user terminal, generating meeting A using meeting generation information received from the terminal of user A, Storing meeting information including meeting account information for the account of the meeting A, sending account creation information for creating a meeting public account corresponding to the meeting A to a simple payment server, and the simple payment server And changing the meeting account information by using the history change information in the meeting public account received from. Thus, the user can reduce the trouble of changing the meeting account information.

Description

Meeting management method and meeting management system using the same{MEETING MANAGEMENT METHOD AND MEETING MANAGEMENT SYSTEM USING THE METHOD}

The present invention relates to a meeting management method and a meeting management system using the same, and more particularly, to a meeting management method for managing a meeting created online and a meeting management system using the meeting.

Recently, a number of meeting sites online, for example, messenger chat rooms, internet cafes, etc., have been established to manage meetings. That is, when a meeting site is created online, meeting participants can access the meeting site using their respective terminals to check the latest meeting information. In addition, when one of the meeting members is designated as an administrator, the designated administrator can manage the meeting site through his terminal.

On the other hand, since a certain amount of money is required to operate the meeting, a certain amount of membership fees must be provided from the members of the meeting. At this time, the membership fee provided in this way can be managed by depositing in any account opened in the bank. For example, if one of the members of the meeting is designated as a secretary, the designated secretary can receive and manage the membership fee in his or her personal account opened in the bank. However, since one secretary has to manage the membership fees as well as the general operation of the meeting, the personal effort of the secretary is very high.

Therefore, there is a need for a service in which general operations for meetings and dues management of meetings can be performed simultaneously. Korean Patent Publication No. 10-2006-0102944 (published on September 28, 2006) discloses a'community service method combined with internet banking'. Specifically, in this prior document,'a service method that can manage members and membership fees together by opening a bank account linked to the community and designating an initial executive' is proposed. However, this service method has a problem in that it is difficult to use a credit account that is convenient for a user, as well as a general secretary to actually open a bank account to which a membership fee is to be deposited.

Therefore, the present invention was derived to solve this problem, and the problem to be solved by the present invention is to provide a meeting management method that automatically creates a virtual account corresponding to a meeting and provides a simple payment service.

In addition, another problem to be solved by the present invention is to provide a meeting management system using the meeting management method.

The meeting management method according to an embodiment of the present invention relates to a meeting management method performed on a meeting management server capable of sending and receiving signals to and from at least one user terminal, using meeting generation information received from the terminal of the user A Generating meeting A, storing meeting information including meeting account information for the account of meeting A, sending account creation information for creating a meeting public account corresponding to meeting A to a simple payment server And changing the meeting account information using historical change information in the meeting public account received from the simple payment server.

The meeting information may further include meeting member information for members of the meeting A.

The meeting management method may further include including the subscription requester in the meeting member information by using the subscription request information received from a terminal of at least one user (hereinafter referred to as a'subscriber').

The meeting management method may further include transmitting a change in the meeting account information to a terminal of a member of the meeting A.

The meeting member information may further include information about at least one manager having authority to change the meeting information.

The meeting management method may further include changing the meeting information using meeting management information received from the terminal of the administrator.

The meeting member information may further include information on at least one secretary having authority to access and manage the meeting public account.

The meeting management method may further include transmitting payment progress information for performing payment by the meeting public account to the simple payment server using payment request information received from the secretary's terminal. At this time, the details of the change in the public account of the meeting may include changes according to the payment progress information.

The meeting member information may further include information on at least one executive who has permission to consent to payment by the meeting public account. At this time, in the step of transmitting the payment progress information to the simple payment server, when at least one payment agreement information is received from the terminal of the executive, the payment progress information may be transmitted to the simple payment server.

Payment by the meeting public account may include at least one of simple payment, account transfer, and withdrawal through an automated teller machine (ATM).

The meeting management method may further include storing memo information according to the payment progress information in the meeting account information.

The meeting management method may further include transmitting deposit request information for requesting a deposit to the meeting public account to the terminal of the member of the meeting A.

The meeting member information may further include information on at least one secretary who has the authority to request deposit to the meeting public account. In this case, in the step of transmitting the deposit request information, the deposit request information may be transmitted to the terminal of a member of the meeting A by using the membership request information received from the terminal of the secretary.

The meeting management method may further include transmitting the meeting account information to the terminal of the member of the meeting A in response to the information confirmation request signal received from the terminal of the member of the meeting A.

Subsequently, the meeting management method according to another embodiment of the present invention relates to a meeting management method performed in a simple payment server that exchanges signals with a meeting management server, and responds to meeting A in response to account creation information received from the meeting management server. And creating a meeting public account for and transmitting historical change information from the meeting public account to the meeting management server. At this time, the meeting management server generates the meeting A using meeting generation information received from the terminal of user A, stores meeting information including meeting account information for the account of meeting A, and the simple payment server The meeting account information is changed by using the history change information in the meeting public account received from.

The meeting information may further include meeting member information for members of the meeting A.

The meeting member information may further include information on at least one secretary having authority to access and manage the meeting public account.

The meeting management method may further include receiving payment progress information for performing payment by the meeting public account from the meeting management server or the terminal of the secretary. At this time, the details of the change in the public account of the meeting may include changes according to the payment progress information. In addition, the payment progress information may be generated directly at the terminal of the secretary or may be generated at the meeting management server using payment request information generated at the terminal of the secretary.

Payment by the meeting public account may include at least one of simple payment, account transfer, and withdrawal through an automated teller machine (ATM).

Subsequently, the meeting management system according to an embodiment of the present invention includes a meeting management server and a simple payment server.

The meeting management server generates meeting A using meeting generation information received from the terminal of user A, stores meeting information including meeting account information for the account of meeting A, and a meeting corresponding to meeting A Outputs account creation information for creating a public account.

The simple payment server generates the meeting public account by using the account creation information received from the meeting management server, and transmits the change information in the meeting public account to the meeting management server.

The meeting management server changes the meeting account information using historical change information in the meeting public account received from the simple payment server.

The meeting information may further include meeting member information for members of the meeting A. At this time, the meeting management server may transmit a change in the meeting account information to the terminal of the member of the meeting A.

According to the meeting management method and the meeting management system using the same according to the present invention, when a user who wants to create a meeting creates a new meeting on the meeting management server using his terminal, the new meeting is automatically generated in the simple payment server. As the meeting public account linked to the meeting is created, the trouble of the secretary opening the account in the simple payment server may be omitted.

In addition, when the meeting's secretary proceeds with the meeting's public account using his terminal, the meeting management server automatically checks for changes in the meeting's public account as the payment proceeds, and As it is transmitted to the members' terminals, the effort by the secretary to report the contents of the payment to each member of the meeting can be omitted.

1 is a conceptual diagram illustrating a meeting management system according to an embodiment of the present invention.
FIG. 2 is a block diagram showing the meeting management system of FIG. 1 in detail.
FIG. 3 is a flow chart for explaining a method of managing a meeting performed by the meeting management system of FIG. 1.
4 is a conceptual diagram illustrating a process of creating a meeting among the meeting management methods of FIG. 3.
5 is a conceptual diagram illustrating a member registration process among the meeting management methods of FIG. 3.
6 is a conceptual diagram for explaining a meeting management process of the meeting management method of FIG. 3.
7 is a conceptual diagram for explaining a payment process in the meeting management method of FIG. 3.
8 is a conceptual diagram illustrating a payment process different from the payment process of FIG. 7.
FIG. 9 is a conceptual diagram illustrating a deposit request process among the meeting management methods of FIG. 3.
FIG. 10 is a conceptual diagram illustrating a process of changing account information among the meeting management methods of FIG. 3.
FIG. 11 is a conceptual diagram illustrating a memo registration process among the meeting management methods of FIG. 3.
FIG. 12 is a conceptual diagram illustrating an information verification process among the meeting management methods of FIG. 3.

The present invention may be variously modified and may have various forms, and specific embodiments will be illustrated in the drawings and described in detail in the text. However, this is not intended to limit the present invention to a specific disclosure form, and it should be understood that all modifications, equivalents, and substitutes included in the spirit and scope of the present invention are included. In describing each drawing, similar reference numerals are used for similar components. In the accompanying drawings, the dimensions of the structures may be exaggerated than actual ones for clarity of the present invention.

Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from other components. For example, the first component may be referred to as a second component without departing from the scope of the present invention, and similarly, the second component may also be referred to as a first component.

The terms used in the present application are only used to describe specific embodiments, and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, terms such as “include” or “have” are intended to indicate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, or that one or more other features or It should be understood that the presence or addition possibilities of numbers, steps, actions, components, parts or combinations thereof are not excluded in advance. Also, A and B are'connected' and'joined' means that other components C are included between A and B in addition to A and B being directly connected or joined, so that A and B are connected or combined. It includes things.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person skilled in the art to which the present invention pertains. Terms, such as those defined in a commonly used dictionary, should be interpreted as having meanings consistent with meanings in the context of related technologies, and should not be interpreted as ideal or excessively formal meanings unless explicitly defined in the present application. Does not. Also, in the claims of a method invention, the order of each step may be interchanged with each other, unless each step is clearly bound to the order.

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the accompanying drawings.

1 is a conceptual diagram illustrating a meeting management system according to an embodiment of the present invention, and FIG. 2 is a block diagram showing the meeting management system of FIG. 1 in detail.

1 and 2, the meeting management system according to the present embodiment is a meeting management server 200 that can exchange signals with a plurality of user terminals 100 owned by a plurality of users, and User terminals 100 and the meeting management server 100 may include a simple payment server 300 that can exchange signals with each other.

Each of the user terminals 100 is a smart terminal that can exchange signals with the meeting management server 200 and the simple payment server 300 through a wired or wireless communication network including the Internet, a mobile communication network, etc., for example It may be a smartphone or tablet PC. In this embodiment, the user terminals 100 are user terminal A owned by user A, user terminal B owned by user B, user terminal C owned by user C, and user owned by user D Terminal D may be included.

The meeting management server 100 may be a server system that can exchange signals with the user terminals 100 and the simple payment server 300 through the wired/wireless communication network, respectively. The meeting management server 100 may generate an arbitrary meeting using at least one meeting creation information received from at least one of the user terminals 100. For example, the meeting management server 100 may generate meeting 1 by meeting generation information A received from the user terminal A and meeting 2 by meeting generation information B received from the user terminal B. have. The meeting management server 100 generates a random meeting using the random meeting creation information, and then stores the information about the generated meeting (hereinafter referred to as'meeting information') in an internal storage device, The account creation information for generating the meeting public account corresponding to the generated information may be generated and transmitted to the simple payment server 300.

In this embodiment, the meeting information may include meeting member information for members of the meeting, meeting account information for the accounts of the meeting, and meeting setting information for operations and settings of the meeting. At this time, the meeting member information is information about at least one administrator who has permission to change the meeting information, information about an executive who has permission to consent to payment by the meeting public account, and accesses the meeting public account It may include information about at least one secretary who has the authority to manage and request deposits to the public account of the meeting, and member information for members of the meeting. Meanwhile, the meeting information may be included in the meeting creation information provided from the user terminal 100.

In this embodiment, the manager of any meeting can be automatically designated as the user who created the meeting. Meanwhile, there may not be one executive member of the meeting, or one or more users. Also, the secretary of the meeting may be composed of one or more users. At this time, the manager of the meeting may also serve as the secretary. For example, the manager of meeting 1 may be user A, the secretary of meeting 1 may be user A and user B, and the general member of meeting 1 may be user C. In addition, the manager of meeting 2 may be user B, the executive of meeting 2 may be user D, and the secretary of meeting 2 may be user C.

The simple payment server 300 may be a server system that can exchange signals with the user terminals 100 and the meeting management server 200 through the wired/wireless communication network, respectively. The simple payment server 300 may generate the meeting public account using the account creation information received from the meeting management server 200.

The simple payment server 300 receives account details related information including deposit, withdrawal, general payment, and simple payment from the meeting management server 200, the user terminals 100, and other payment-related devices, and If it is determined that the details of the meeting public account have been changed according to the account details related information, the details of the change of information in the meeting public account may be transmitted to the meeting management server 200.

Meanwhile, when the meeting management server 200 receives the change information in the meeting public account from the simple payment server 300, the meeting account is among the meeting information using the change information in the meeting public account. Information can be changed. When the meeting account information is changed, the meeting management server 200 may transmit the changed meeting account information to user terminals 100 owned by members of the meeting.

Hereinafter, a method of managing a meeting performed by the meeting management system will be described in detail using separate drawings.

FIG. 3 is a flow chart for explaining a method of managing a meeting performed by the meeting management system of FIG. 1.

1 to 3, a user terminal 100 owned by an arbitrary user (hereinafter referred to as a'meeting creator') to create a meeting is the meeting management server 200 or a store server (not shown) ) To download and install the meeting management service program, and then run the meeting management service program.

4 is a conceptual diagram illustrating a process of creating a meeting among the meeting management methods of FIG. 3.

1 to 3 and 4, when the user terminal 100 generates meeting generation information for generating meeting A and transmits the generated meeting information to the meeting management server 200, the meeting management server 200 The meeting A may be generated using the meeting generation information (S10). At this time, the meeting management server 200 stores the meeting information for the meeting A included in the meeting creation information in an internal storage device, and the account creation information for generating a meeting public account corresponding to the meeting A It can be sent to the simple payment server 300.

In this embodiment, the meeting information may include meeting member information for members of the meeting A, meeting account information for the accounts of the meeting A, and meeting setting information for operations and settings of the meeting A. At this time, the meeting member information is information about at least one administrator who has permission to change the meeting information, information about an executive who has permission to consent to payment by the meeting public account, and accesses the meeting public account It may include information about at least one secretary who has the authority to manage and request deposits to the public account of the meeting, and member information for members of the meeting A. At this time, the administrator may be automatically registered as the meeting creator.

5 is a conceptual diagram illustrating a member registration process among the meeting management methods of FIG. 3.

1 to 3 and 5, the user terminal 100 owned by at least one user (hereinafter referred to as'subscriber') who wants to join the meeting A generates subscription request information, and When transmitted to the meeting management server 200, the meeting management server 200 may include the subscription requester in the meeting member information among the meeting information (S20). That is, the meeting management server 200 may register the subscription requester as a member of the meeting A, for example, a general member, and also store personal information about the subscription requester.

On the other hand, if the meeting A is a public meeting, member registration is possible by the step S20, but if the meeting A is a private meeting, member registration is not possible by the step S20, and only by an administrative action by the administrator Can be registered. In this case, information on whether the meeting A is a public meeting or a private meeting may be included in the meeting setting information among the meeting information.

6 is a conceptual diagram for explaining a meeting management process of the meeting management method of FIG. 3.

1 to 3 and 6, when the user terminal 100 owned by the owner of the meeting A generates meeting management information for changing the meeting information and transmits it to the meeting management server 200 , The meeting management server 200 may change the meeting information using the meeting management information (S30). For example, the meeting management server 200 may use the meeting management information to change the roles of members of the meeting A or to change the operation method and settings of the meeting A.

7 is a conceptual diagram for explaining a payment process in the meeting management method of FIG. 3.

1 to 3 and 7, the user terminal 100 owned by the secretary of the meeting A sends payment request information to the meeting management server 200 to perform payment by the meeting public account. Upon transmission, the meeting management server 200 may generate payment progress information using the payment request information and transmit it to the simple payment server (S40). In this embodiment, the payment by the public account of the meeting may include at least one of general payment, simple payment, account transfer, and withdrawal through an automated teller machine (ATM).

Meanwhile, the meeting management server 200 does not automatically generate the payment progress information and transmit it to the simple payment server when the payment request information is received, but generates the payment progress information only when a certain payment agreement condition is satisfied. It can also be sent to the simple payment server. For example, the meeting management server 200 is a user terminal 100 owned by the executive of the meeting A and the user terminal 100 owned by the manager of the meeting A whether or not to agree whether or not to proceed with the payment. After requesting, if all the payment agreement information is received from the corresponding user terminal 100 or more than a majority, the payment progress information may be generated and transmitted to the simple payment server 300. Meanwhile, information on the payment agreement conditions may be included in the meeting setting information among the meeting information.

8 is a conceptual diagram illustrating a payment process different from the payment process of FIG. 7.

1 to 3 and 8, in step S40, the user terminal 100 owned by the secretary of the meeting A directly generates the payment progress information without going through the meeting management server 200. It may be transmitted to the simple payment server 300 (S40). At this time, the user terminal 100 may generate the payment progress information only when the payment agreement condition is satisfied and transmit it to the simple payment server 300.

FIG. 9 is a conceptual diagram illustrating a deposit request process among the meeting management methods of FIG. 3.

1 to 3 and 9, the user terminal 100 owned by the secretary of the meeting A generates membership request information for depositing the membership dues and sends them to the meeting management server 200 If so, the meeting management server 200 sends text request, push, SNS, and e-mail to the deposit request information for requesting the deposit to the public account of the meeting to each of the user terminals 100 owned by members of the meeting A It can be transmitted in the form of.

In this embodiment, although the user terminal 100 may generate the membership request information at any point in time and transmit it to the meeting management server 200, the user terminal 100 periodically requests the membership fee every time Information may be generated and transmitted to the meeting management server 200. In addition, the meeting management server 200 may periodically transmit the deposit request information to the user terminals 100 owned by members of the meeting A at certain time points regardless of receiving the membership request information.

On the other hand, when the user terminal 100 generates the membership request information and transmits it to the meeting management server 200, the meeting management server 200 transmits a deposit request message to members of the meeting A, and each member Deposit information for each member may be generated and included in the meeting account information so that it is possible to check whether the deposit has been completed for each member. In addition, the deposit request information provided to members of the meeting A may include information requesting the same deposit amount, but may include information requesting different deposit amounts according to roles of each component. The setting information related to the deposit request may be included in the meeting setting information among the meeting information.

FIG. 10 is a conceptual diagram illustrating a process of changing account information among the meeting management methods of FIG. 3.

1 to 3 and 10, when the simple payment server 300 receives information related to account details related to changes in the details of the meeting public account from the outside, the meeting is responsive to the account details related information. After changing the history information in the public account, the history change information may be transmitted to the meeting management server 200 (S60). Thereafter, the meeting management server 200 changes the meeting account information among the meeting information by using the history change information in the meeting public account, and then the user terminal 100 owned by members of the meeting A They can be sent in the form of text messages, push, SNS, email, etc.

In this embodiment, the account details related information includes the payment progress information generated by the meeting management server 200 or the secretary-owned user terminal 100 in step S40 and the deposit information deposited into the meeting public account. It can contain. As described above, the setting contents according to the change of the account details may be included in the meeting setting information among the meeting information.

FIG. 11 is a conceptual diagram illustrating a memo registration process among the meeting management methods of FIG. 3.

1 to 3 and 11, the user terminal 100 owned by the secretary of the meeting A generates memo information according to a change in the details in the meeting public account and sends it to the meeting management server 200 Upon transmission, the meeting management server 200 may include and store the memo information in the meeting account information among the meeting information (S70).

FIG. 12 is a conceptual diagram illustrating an information verification process among the meeting management methods of FIG. 3.

1 to 3 and 12, a user terminal 100 owned by any one of the members of the meeting A signals a confirmation request to confirm the meeting information, for example, the meeting account information. When is transmitted to the meeting management server 200, the meeting management server 200 may transmit the stored meeting information to the user terminal 100 (S80). At this time, the range of information that can be checked for each member of the meeting A may be different from each other. The setting information for checking information by the member may be included in the meeting setting information among the meeting information.

As described above, according to this embodiment, when a user who wants to create a meeting creates a new meeting in the meeting management server 200 using his terminal, it is automatically interlocked with the new meeting in the simple payment server 300 As the meeting public account is created, it may not be necessary to directly access the simple payment server 300 and open the corresponding account.

In addition, when the meeting's secretary proceeds with the meeting's public account using his terminal, the meeting management server 200 automatically checks for changes in the meeting's public account as the payment proceeds As it is transmitted to the terminals of the members of the meeting, it is possible to avoid the trouble of reporting the contents of the payment progress to each member of the meeting.

In the detailed description of the present invention described above, it has been described with reference to preferred embodiments of the present invention, but those skilled in the art or those skilled in the art will appreciate the spirit of the present invention as set forth in the claims below. And it will be understood that various modifications and changes can be made to the present invention without departing from the scope of the technology.

100: user terminal 200: meeting management server
300: simple payment server

Claims (21)

In the meeting management method performed in the meeting management server that can send and receive signals with at least one user terminal,
Generating a meeting A using the meeting generation information received from the user A's terminal;
After creating the meeting A, storing meeting information including meeting account information for the account of the meeting A;
Generating the meeting A, generating account generation information for generating a meeting public account corresponding to the meeting A, and transmitting the generated account information to a simple payment server; And
And changing the meeting account information by using the history change information in the meeting public account received from the simple payment server,
The public account for the meeting
Meeting management method characterized in that the account is available for deposit, withdrawal, general payment and easy payment. According to claim 1,
The above meeting information
Meeting management method characterized in that it further comprises a meeting member information for the members of the meeting A. According to claim 2,
And including the subscription requester in the meeting member information by using subscription request information received from a terminal of at least one user (hereinafter referred to as a'subscription requester'). According to claim 2,
And transmitting the change in the meeting account information to the terminal of the member of the meeting A. According to claim 2,
The meeting member information
And at least one manager having permission to change the meeting information. The method of claim 5,
And changing the meeting information by using the meeting management information received from the terminal of the manager. According to claim 2,
The meeting member information
The meeting management method, characterized in that it further comprises information about at least one secretary having the authority to access and manage the meeting public account. The method of claim 7,
Using the payment request information received from the terminal of the secretary, further comprising the step of transmitting payment progress information for performing payment by the meeting public account to the simple payment server,
The details of the change in the public account of the meeting
Meeting management method characterized in that it comprises a change according to the payment progress information. The method of claim 8,
The meeting member information
Further information about at least one executive who has the authority to consent to payment by the meeting public account,
In the step of transmitting the payment progress information to the simple payment server,
If at least one payment agreement information is received from the terminal of the executive, the meeting management method, characterized in that for transmitting the payment progress information to the simple payment server. The method of claim 8,
Payment by the above public account for the meeting
Meeting management method characterized in that it comprises at least one of simple payment, account transfer and withdrawal via ATM (ATM). The method of claim 8,
And storing memo information according to the payment progress information in the meeting account information. According to claim 2,
And transmitting deposit request information for requesting deposit to the meeting public account to the terminal of the member of the meeting A. The method of claim 12,
The meeting member information
Further information about at least one secretary having the authority to request a deposit to the public account of the meeting,
In the step of transmitting the deposit request information,
A meeting management method, characterized in that using the membership request information received from the terminal of the secretary, the deposit request information is transmitted to a terminal of a member of the meeting A. According to claim 2,
And in response to the information confirmation request signal received from the terminal of the member of the meeting A, transmitting the meeting account information to the terminal of the member of the meeting A. In the meeting management method performed in a simple payment server that exchanges signals with the meeting management server,
Generating a meeting public account for meeting A in response to account creation information received from the meeting management server; And
And transmitting the history change information from the meeting public account to the meeting management server,
The meeting management server
The meeting A is generated using the meeting generation information received from the terminal of the user A,
After creating the meeting A, meeting information including meeting account information for the account of the meeting A is stored,
After creating the meeting A, the account creation information is generated and transmitted to the simple payment server,
Change the meeting account information by using the history change information in the meeting public account received from the simple payment server,
The public account for the meeting
Meeting management method characterized in that the account is available for deposit, withdrawal, general payment and easy payment. The method of claim 15,
The above meeting information
Meeting management method characterized in that it further comprises a meeting member information for the members of the meeting A. The method of claim 16,
The meeting member information
The meeting management method, characterized in that it further comprises information about at least one secretary having the authority to access and manage the meeting public account. The method of claim 17,
Further comprising the step of receiving payment progress information for performing payment by the meeting public account from the meeting management server or the terminal of the secretary,
The details of the change in the public account of the meeting
Includes changes according to the payment progress information,
The payment progress information
Meeting management method characterized in that it is generated directly in the terminal of the secretary, or in the meeting management server using payment request information generated in the terminal of the secretary. The method of claim 18,
Payment by the above public account for the meeting
Meeting management method characterized in that it comprises at least one of simple payment, account transfer and withdrawal via ATM (ATM). Create meeting A using the meeting creation information received from the terminal of user A, and after generating meeting A, store meeting information including meeting account information for the account of meeting A, and store meeting A A meeting management server that generates and generates account generation information for generating a meeting public account corresponding to the meeting A and then transmits the generated account creation information to the outside; And
And a simple payment server that generates the meeting public account using the account creation information received from the meeting management server and transmits the change information in the meeting public account to the meeting management server.
The meeting management server
The meeting account information is changed by using the history change information in the meeting public account received from the simple payment server,
The public account for the meeting
Meeting management system characterized in that the account is available for deposit, withdrawal, general payment and simple payment. The method of claim 20,
The above meeting information
Further comprising the meeting member information for the members of the meeting A,
The meeting management server
Meeting management system, characterized in that for transmitting the change in the meeting account information to the terminal of the member of the meeting A.

Images