KR20180124792A - Method and apparatus for management of ticket - Google Patents

Abstract

Disclosed is a system capable of managing invitation tickets, managing entry of staff, creating, distributing and delivering actually sold tickets, and checking validity. A server operating the system makes up a system for ticket management. The server includes: a control unit to control processing and transfer of information required to generate, transfer, check, and manage invitation ticket-related information; a storage unit to store invitation ticket-related information generated by the control unit and the invitation ticket-related information; and a communication unit to transmit the invitation ticket-related information generated by the control unit to a broker terminal, a user terminal, or an event hall terminal. The invitation ticket-related information transferred from the server to the broker terminal, the user terminal, or the event hall terminal via a URL is checked to continuously track the route of how each invitation ticket group is transferred from where.

Description

≪ Desc / Clms Page number 1 > METHOD AND APPARATUS FOR MANAGEMENT OF TICKET &

The present invention relates to a system for delivering and managing tickets such as invitations. More particularly, to a network system for managing procedures throughout the generation, transmission, registration, and use of tickets such as invitations on-line and off-line.

An invitation ticket is a kind of ticket that is donated or sold for free or paid (in this case, part of the actual ticket price, usually an environmental contribution) for various purposes such as promotion of the event and advertising of the sponsor. Promoting the event by distributing the invitation tickets for the cultural and art events from the organizer or individual donors free of charge or for a fee, and advertising the sponsor.

As the economy and industry develop, people are interested in leisure, tickets used in cultural events are often used to purchase tickets through the Internet and purchase tickets or pre-book via telephone have. When purchasing a ticket through the Internet, it is easy to purchase a ticket without inconvenience of visiting or making a call, and there are many cases where a smartphone is entered in the field.

However, it is a reality that the invitation ticket is transmitted in the offline mode without specifying the user because of characteristics such as free or small amount of money, and the nature of trading like a gift for publicity effect. At this time, since the intermediary must directly visit or deliver by mail or mail in order to deliver the invitation ticket to the target of each cultural marginalized class, the period of time in which the invitation ticket is delivered becomes long, and labor costs and separate delivery expenses are incurred. In addition, the intermediary has a problem in that the process of transmitting the invitation ticket is troublesome because the intermediary selects the target person corresponding to the event according to the contents of the donated invitation ticket and delivers the donation ticket.

In addition, it is not possible to confirm whether the invitation ticket is used for an appropriate purpose or not, and it is often lost or unused during distribution to fail to act as an actual invitation ticket. Therefore, It is a very difficult reality to settle. In this way, the broker who distributes the concert organizer and the invitation ticket is required to manage the invitation ticket of the new system.

10-2015-0028912 (2015.03.02.)

A technical object of the present invention is to provide a system capable of managing overall procedures related to generation, transmission, registration and confirmation, etc. of invitation tickets on a system.

Furthermore, the technical object of the present invention is to provide a system that can manage management staff or paid tickets instead of invitation tickets.

According to an aspect of the present invention, a server constituting a ticket management system is disclosed. The server includes a control unit 210 for controlling processing and delivery of information necessary for generating, delivering, confirming and managing invitation-related information; A storage unit 220 for storing the invitation-related information and the invitation-related information generated by the controller 210; And a communication unit 230 transmitting the invitation ticket related information generated by the controller 210 to the broker terminal 130, the user terminal 140, or the event terminal 150.

The control unit 210 further includes an invitation ticket generation module 212, an invitation ticket delivery module 214, an invitation ticket validity check module 216 and an invitation ticket confirmation module 218. The invitation ticket generation module 212 includes an invitation ticket creation module 212, The name of the event, the description of the event, the date and time of the event, whether the event is paid or free of charge, the event is paid for The invitation ticket delivery module 214 generates a uniform resource link (URL) to be linked to the invitation ticket related information to the broker terminal 130, And adds the valid period and the recipient information that can transmit the invitation ticket to the group information, and the invitation ticket transfer module 214 does not include the recipient information to be transferred in the predetermined database The recipient information is automatically added to the database in the storage unit 120 and the related information is added to the database in the storage unit 120, The invitation ticket delivery module 214 transmits the invitation ticket using the information stored in the database to the broker terminal 130 and the user terminal 140 in the server 110, Or the invitation-related information transmitted through the URL to the event site terminal 150, and continuously tracks the route from where the respective invitation group is transmitted.

According to the present invention, the administrator can confirm the distribution status of the invitation ticket and who is registered as the user. Based on this, it is possible to check whether the user is registered according to the plan of the invitation ticket. Based on this, And ultimately prevent the re-transaction of the invitation ticket through the card.

According to the present invention, it is possible to check the status of the uninhabited but not yet used unregistered person, and to simplify the process of confirming whether the unauthorized person is legitimate.

According to the present invention, if the invitation ticket is not completely free, and if a part of the invitation ticket is paid, the invitation ticket can be promptly entered on the spot after payment in advance.

According to the present invention, the status of generation, distribution, and use of the invitation ticket can be monitored entirely in the server, and the person planning the invitation ticket can confirm whether the invitation ticket is used for the original purpose.

1 is a network configuration diagram of an invitation ticket management system according to an embodiment of the present invention.
2 is a block diagram of a server of an invitation ticket management system according to an embodiment of the present invention.
3 is a flow chart of the process of invitation ticket management according to one embodiment of the present disclosure.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the present invention. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Also, in order to clearly illustrate the present invention in the drawings, portions not related to the present invention are omitted, and the same or similar reference numerals denote the same or similar components.

The objects and effects of the present invention can be understood or clarified naturally by the following description, and the objects and effects of the present invention are not limited only by the following description.

The objects, features and advantages of the present invention will become more apparent from the following detailed description. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 is a network configuration diagram of an invitation ticket management system according to an embodiment of the present invention, and FIG. 2 is a block configuration diagram of a server of an invitation ticket management system according to an embodiment of the present invention.

1 and 2, the invitation ticket management system 100 includes a server 110, an administrator terminal 120, a plurality of broker terminals 130, 132, 134, ..., and a user terminal 140. At this time, the broker terminal 130 may also serve as the user terminal 140.

The server 110, the administrator terminal 120, the broker terminal 130 and the user terminal 140 transmit and receive information through the wired / wireless network 190. At this time, the wired / wireless network 190 may be connected to a network such as TCP / IP (Transport Control Protocol / Internet Protocol), LAN (Local Area Network), WIFI, Long Term Evolution (LTE), Wideband Code Division Multiple Access (WCDMA) A wired communication method, a wireless communication method, and other communication methods to be known in the future.

At this time, the server 110 includes a control unit 210, a storage unit 220, and a communication unit 230.

The control unit 210 performs necessary control to perform the following embodiments. In particular, the control unit 210 can generate, deliver, confirm, and manage invitation-related information. The storage unit 220 stores the invitation-related information generated by the control unit 210 and stores information necessary for performing the embodiments described later. The storage unit 220 may include a database.

The communication unit 230 transmits the invitation-related information generated by the control unit 210 to the broker terminal 130. [ Also, the communication unit 230 transmits / receives signals necessary for performing other embodiments described later.

The control unit 210 receives the information of the broker from the broker terminal 130 and checks whether the invitation ticket is valid or not. When validity is confirmed, the broker terminal 130 transmits information related to a part or all of the invitation to the user terminal.

The control unit 210 receives the information of the user from the user terminal 140 and checks whether the invitation ticket is valid or not. When the validity is confirmed, the invitation ticket is registered in the user terminal 140.

The server 110 is provided with a dedicated program for managing invitation tickets. The server 110 includes a controller 210 and drives the invitation generation module 212, the invitation delivery module 214, the invitation validity check module 216, and the invitation confirmation module 218, respectively.

The invitation ticket generation module 212 generates invitation tickets to be distributed by the administrator and groups them according to the requirements of the event organizer. At this time, the generated invitation ticket (or a group of invitation tickets, hereinafter simply referred to as an invitation ticket) includes information such as the type of ticket, content of the event, name of the event, description of the event, date / time of the event, (Eg, environmental contribution) information.

The invitation ticket delivery module 214 generates a uniform resource link (URL) to be linked to the invitation ticket related information, and transmits the URL to the broker terminal 130. At this time, a period (also referred to as a validity period) in which the invitation ticket can be transmitted to the created invitation ticket group information, a recipient (name, contact, predetermined security code) may be added. Or the affiliation group code itself.

The URL information may be delivered to the broker terminal 130 or the user terminal 140 in the form of SMS, messenger, e-mail or the like.

When the invitation ticket delivery module 214 determines that the recipient information is not in the predetermined database (default), the invitation ticket transfer module 214 automatically adds the corresponding user terminal as a member and adds related information to the database.

The invitation ticket transfer module 214 transfers the invitation ticket using the information stored in the database when the recipient information exists in the database.

The invitation ticket delivery module 214 may cause the server 110 to retransmit the invitation related information transmitted to the broker terminal 130 to the user terminal 140 via the URL. This allows the server 110 to keep track of where the respective group of invitees are from, and how they are delivered.

The invitation ticket delivery module 214 may check that the invitation ticket is generated and delivered in the form of a packaged form so that the user can recognize that the invitation ticket can be registered.

The invitation validity check module 216 checks whether the terminal receiving the URL is legitimately entitled to receive the invitation ticket when the terminal is connected by a link. Such a procedure is called an invitation ticket access procedure. When a name, an e-mail, a gender, a contact, a resident registration number and a predetermined security code of a user are input, .

Through this, only a legitimate user can register and use the URL so that the URL is transmitted to a plurality of terminals multiple times online.

The invitation ticket confirmation module 218 checks the user information of the endmost user terminal to which the invitation ticket is transmitted. Through this, the administrator can check which process the invitation ticket has been transmitted to and ultimately to whom. In addition, the broker terminal 130 can confirm the user information holding the invitation ticket, and can additionally track whether the user terminal 140 transmitted by the broker terminal 130 has retransmitted the invitation ticket to another user terminal. The broker terminal 130 can forward the invitation to the user terminal 140 or deliver it to another broker terminal. That is, a user who receives a ticket from a broker can access each ticket and use it, or deliver it to another person.

The invitation ticket validation module 218 may transmit the information to the terminal 150 at the event site as well as the administrator terminal 120 or the broker terminal 130. [

The event site terminal 150 (eg, iPad) simultaneously receives the invitation information displayed on the display of the user terminal 140 and the information transmitted from the invitation ticket confirmation module 218 of the server 110, You can verify that the user you are entering is a legitimate user.

That is, at the site, the invitation ticket and the user's personal information registered on the tablet (for example, iPad) are inputted and the validity is checked again by the server. The user terminal receiving the invitation ticket can register the ID card in conjunction with the ID card in advance. In this case, the procedure for checking the ID card on the spot can be simplified. The invitation ticket can be divided into prepayment and postpayment, and payment can be received in advance, which greatly simplifies access procedures at the venue.

For example, the invitation ticket confirmation module 118 confirms the invitation ticket image, the invitation ticket unique number, the invitation ticket unique code, and the registered user contact information, and transmits the confirmation to the event site terminal 150.

Through this, only the user registered in advance can enter the contact information on the tablet of the event site, or can confirm the ID card to easily perform the access permission. In other words, it is possible to prevent the indefinite stance from taking place.

The server 110 may further include a database 222 and a data management module 224. [

The data management module 222 checks and stores all of the generation status of the invitation ticket, the delivery status, the validity check status, the admission status on the field, the entry time, the fee / free status, the payment of the environment charge and the payment method confirmation.

The data management module 222 may further include a staff information management module 226. At this time, the types of invitations can be classified as one type of staff related to the events such as field team, artist team, and security team, and the invitation ticket can be used as a kind of employee certificate for managing the staff of the day. In this case, invitation related information includes staff creation status, staff team distribution status, staff qualification status, staff presence status, staff attendance time, staff payroll status, etc., .

It is possible to check on the field terminal 150 and manage it on the server 110 without having to check whether or not the staff commute to work or place on the spot, verbally or visually. In this case, the invitation ticket management system may also be referred to as a staff management system. The administrator terminal 120 connected to the server 110 can check in real time whether the staff is performing work internally or externally, It can also be used for event work.

The data management module 224 can access the third ticket sales server (e.g., a ticket sales agency server such as Interpark or its own ticket sales server) to share and manage the seller information of the ticket. In this case, the invitation ticket management system may be extended to a ticket management system.

In this case, not only the invitation ticket but also the information of the ticket purchased for a fee can be checked and transmitted, validated, or confirmed to perform overall management.

Even if the terminal is not a third ticket selling server but an external terminal or system, the information may be visually checked in the field or may be checked with an image photographed with a photograph.

In an example according to the present invention, the invitation ticket information or the ticket information may separately distinguish and display the ticket as a membership group of a purchased group, an invitation ticket group, and a club.

In this case, the field terminal 150 may create a separate line according to the group of the invitation ticket, the fee, and the membership, check the exclusive ticket (invitation ticket, fee ticket or membership card) in each line, .

According to the present invention, the performance organizer may be the manager himself, or the invitation dedicated planner may be the manager. A broker can be a person who takes charge of distributing invitations and may be a top person or a main person. The user may be the party who actually uses the ticket or enters the venue.

The broker may manage information about the group including the type, type, and number of invitations at once.

For example, if 50 out of 100 invitations are completely free, and 50 are partially paid, each can be grouped and delivered to different users or other brokers.

Also, invitations of each group of 50 chapters can be sent as a group to one broker or user, divided into two groups of 25 chapters, or classified into different numbers of different groups and sent to different brokers or users It can also be delivered.

As a result, the administrator can specify the type, number, and type of the first invitation to be delivered to one or more brokers, and each broker can distribute the invitation according to his or her policy or philosophy. You can distribute your invitation to. The invitation ticket management system according to the present invention is effective for monitoring the flow of such a distribution.

After the invitation is delivered, the manager can easily confirm that the broker is connected only to the server 110 even if the broker is not separately managed. Therefore, the broker can easily determine whether the broker is redistributed after distributing his / her invitation card (for example, Whether the ticket is valid or not, and if it is detected in the middle, the validity of the ticket may be invalidated.

In other words, a broker can also have the authority to manage the validity of its own invitations, or it can pass on to other users or register itself.

The administrator can check not only the situation in which the invitation ticket is delivered, but also the result after entry. In this case, it can be confirmed as basic data for settlement of the cost of hosting the event or managing the invitation ticket.

When the invitation ticket delivery module 114 delivers the invitation information to the broker terminal 130 or the user terminal 140, the invitation authority management module 118 deactivates the invitation ticket for the previous owner of the invitation ticket. However, another privilege may be given to the broker terminal 130 to invalidate the validity of the user terminal that has received the invitation ticket information.

When the invitation ticket is deactivated to the broker and the user or its downstream user registers the invitation ticket, the invitation ticket validation module 118 can check who is the holder of the inactive invitation ticket.

The user terminal 140 may enter a name, a telephone number, or a dedicated code to register the invitation as a situation that the user can use.

One of the broker terminals 130 may be designated as the master broker or the terminal of the main contact person.

At this time, apart from the manager who organizes the event, the main person in the broker can check and manage the status of the registrant of the entire invitation card, and can also check and manage the sub brokers, users, and downstream users who have distributed the invitation card.

At this time, the main contact person can invalidate or reduce the authority even if a specific user is valid.

The invitation ticket management module can notify the validity of the invitation ticket or the change of registration to the terminals of the user and the downstream user associated with the invitation ticket.

The terminal of the main contact person can grasp the current state of the ticket whose uninvited ticket is unrecorded until the valid time (that is, the final time when the invitation ticket can be delivered). At this time, the validity time may be extended. In addition, the main contact can raise the route to which the invitation ticket has been sent. This can remove the stigma.

The server 110 may determine the terminal connected to the administrator account as the administrator terminal 120 and grant authority.

An administrator account can identify the data managed by the server. The person in charge can confirm whether the registration is valid or not and whether the identification card (when there is an age where the position of the performance is limited) is registered.

According to the present invention, the organizer of the event can check whether the distributed invitation ticket has been properly delivered or not, through which route, until the entrance, and whether the user who actually entered the ticket is the same as the first invitation ticket distributor. At this time, all the routes and information are stored in the database, and the user's gender, age, registration time, and the number of times of transmission are checked to check whether the invitation ticket is used for the advertisement purpose. It checks the validity by mobile number, e-mail, etc., and confirms it continuously.

Since the entrance situation of the invitation ticket is directly checked through the field terminal in the present invention, the invitation ticket and the paid invitation card (environmental contribution) can be settled immediately after the event.

3 is a flow chart of the process of invitation ticket management according to one embodiment of the present disclosure.

Referring to FIG. 3, after the host logs in (S310), a new ticket group corresponding to a predetermined number of the first event is created in the application (S320). For example, it is possible to create a first group of 100 invitations to an ultra music festival, a second group of 150, and a third group of 50, that is, three groups in total.

Subsequently, the host delivers the ticket of the first group (that is, chapter 100) to the manager 1 (S332), delivers the ticket of the second group (that is, 150 tickets) to the manager 2 (S334) And delivers a ticket of 3 groups (i.e., 50 sheets) (S336). Through this, the host can monitor the status of the ticket transmitted from the manager 1 to the manager 3.

The manager 1 delivers the ticket to its customers (S342). You can deliver a single ticket, or you can deliver multiple tickets. The customer who has received the ticket registers with the application and transmits the information to the server, which declares the ticket as a ticket to be used by the client (S352). The server confirms that the customer 1 has registered the ticket, and transmits this fact to the host 1 and the manager 1 so that the host 1 and the manager 1 can monitor the registration status of the ticket.

The manager 2 also delivers the ticket to his / her customers (S344). A single ticket can be delivered, multiple tickets can be delivered, or a plurality of tickets can be delivered to a lower manager so that the lower manager can deliver a ticket to each customer (S354).

Manager 3 can also deliver the ticket to his clients or sub-managers.

It will be apparent to those skilled in the art that various modifications, additions and substitutions are possible, without departing from the spirit and scope of the invention as defined by the appended claims. Should be regarded as belonging to the above-mentioned patent claims.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the inventive concept as defined by the appended claims. But is not limited thereto.

In the above-described exemplary system, the methods are described on the basis of a flowchart as a series of steps or blocks, but the present invention is not limited to the order of the steps, and some steps may occur in different orders . It will also be understood by those skilled in the art that the steps shown in the flowchart are not exclusive and that other steps may be included or that one or more steps in the flowchart may be deleted without affecting the scope of the invention.

Claims (8)

A control unit 210 for controlling processing and delivery of information necessary for creating, delivering, confirming and managing invitation-related information; A storage unit 220 for storing the invitation-related information and the invitation-related information generated by the controller 210; And a communication unit 230 that transmits the invitation ticket related information generated by the controller 210 to the broker terminal 130, the user terminal 140, or the event venue terminal 150, 110)
The control unit 210 further includes an invitation ticket generation module 212, an invitation ticket delivery module 214, an invitation validity check module 216, and an invitation ticket confirmation module 218,
The invitation ticket generation module 212 generates and groups the invitation tickets to be distributed, and displays the ticket type, the content of the event, the name of the event, the description of the event, the date and time of the event, Create invitation-related information, including whether the event is free or for free, and if the event is paid,
The invitation ticket delivery module 214 generates a uniform resource link (URL) to be connected to the invitation ticket related information to be transmitted to the broker terminal 130. The invitation ticket transfer module 214 transmits the invitation ticket information to the broker terminal 130, In addition,
The invitation ticket transfer module 214 automatically adds the related information to the database in the storage unit 120 if the recipient information to be transferred is not found in the predetermined database by default,
When the recipient information to be transmitted is information existing in the database in the storage unit 120, the invitation ticket delivery module 214 transmits the invitation ticket using the information stored in the database,
The invitation ticket delivery module 214 checks the invitation ticket related information transmitted from the server 110 via the URL to the broker terminal 130, the user terminal 140 or the event terminal 150, Wherein the server continuously tracks the path from where the request was received to the server.
The method according to claim 1,
The invitation ticket delivery module 214 generates and transmits a URL in the form of a packaged invitation ticket, and the control unit 210 checks whether the packaged URL is delivered to determine whether a user is allowed to register the invitation ticket A server characterized by verification.
3. The method of claim 2,
The invitation ticket validity checking module 216 receives the broker information from the broker terminal 130 and checks whether the invitation ticket is valid. When the validity is confirmed, the invitation ticket transfer module 216 transmits the broker terminal 130 to the broker terminal 130, Handles information on transferring information related to a part or all of the invitation ticket to the user terminal,
The validity checking module 216 receives the user's information from the user terminal 140 and checks whether the invitation ticket is valid. If the validity checking module 216 validates the invitation ticket, the validity checking module 216 sends the invitation ticket to the user terminal 140 Wherein the server is configured to process the registration.
The method according to claim 1,
The validity checking module 216 checks whether the terminal receiving the URL of the broker terminal 130, the user terminal 140 and the event terminal 150 is legally entitled to receive the invitation ticket And,
Wherein the server checks whether the user's name, e-mail, gender, contact, resident registration number, and security code are legitimate.
The method according to claim 1,
The invitation ticket validation module 218 checks the user information of the end user terminal to which the invitation ticket has been transferred, checks the number of types of terminals to which the invitation ticket is transmitted, and stores the number in the storage unit.
The broker terminal 130 transmits the user information having the invitation ticket so that it can be confirmed,
And further tracks whether the user terminal (140) has retransmitted the invitation to another user terminal.
The method according to claim 1,
The invitation ticket validation module 118 confirms the invitation ticket image, the invitation ticket unique number, the unique code of the invitation ticket, and the registered user contact, and delivers it to the event terminal 150.
The method according to claim 1,
The storage unit 220 further includes a data management module 224,
The data management module 222 checks and stores all of the generation status of the invitation ticket, the delivery status, the validity check status, the admission status on the field, the entrance time, the fee / free status, the payment of the environment charge,
The data management module 222 further includes a staff information management module 226,
The staff information management module 226 classifies the type of the invitation ticket into one of a field team, an artist team, and a security team.
Wherein the invitation-related information includes at least one of a staff creation status, a staff team distribution status, a staff qualification check status, a staff presence status, a staff attendance time, and a staff payroll status.
The method according to claim 1,
Wherein the URL information is delivered to the broker terminal (130) or the user terminal (140) in the form of SMS, messenger, e-mail or the like.

Images