KR102129264B1 - Method and apparatus for securing of ticket - Google Patents

Abstract

Disclosed is a system capable of generating, distributing, and delivering and validating checks from the management of invitation tickets to the entrance management of staff and actual tickets sold. According to an aspect of the present invention, a server operating the system is a server constituting a ticket management system. The server controls the processing and delivery of information necessary to generate, transfer, check, and manage invitation-related information, the invitation-related information generated by the control unit, and a storage unit for storing the invitation-related information and the invitation ticket generated by the control unit And a communication unit transmitting information to a broker terminal, a user terminal, or an event site terminal. The server checks information related to the invitation ticket delivered through the URL from the server to the broker terminal, the user terminal, or the venue terminal, and continuously tracks the route from where and how each invitation group was delivered.

Description

Security ticket security method and device {METHOD AND APPARATUS FOR SECURING OF TICKET}

The present invention relates to a system for maintaining security in the process of delivering, brokering and managing mobile tickets such as invitation tickets. More specifically, the present invention relates to a system for maximizing security in managing procedures throughout the creation, delivery, registration, and use of tickets, such as invitation tickets, online and offline.

An invitation ticket is a type of ticket that is donated or sold for free or paid (in this case, it is part of the actual ticket price and is usually an environmental burden) for various purposes such as promotion of the event or advertisement of the sponsor. The invitations to watch cultural and art events from the event organizer or individual donors are distributed free or paid to activate the event and advertise the sponsor.

As the economy and industry develop, people are interested in leisure life, and tickets used in cultural events are used more frequently in the old way of purchasing tickets by visiting the designated ticket offices or by booking through the phone. have. When purchasing tickets through the Internet, you can easily purchase tickets without the hassle of directly visiting or making a phone call.

However, it is a reality that invitation tickets are delivered in offline form without specifying who the user is because of the nature of being transferred for free or for a small amount, and the nature of being traded as a gift for promotional effect. At this time, since the intermediary has to visit and deliver it in person or deliver it by mail in order to deliver the invitation ticket to each culturally underprivileged, there is a problem in that labor costs and separate delivery costs are incurred as the period during which the invitation ticket is delivered becomes longer. In addition, the intermediary has a problem in that the process of inviting the invitation ticket is cumbersome because the donor ticket is individually selected and the donation ticket is matched with the event according to the event content of the donated invitation ticket.

In addition, it is not possible to check whether the invitation ticket is used for the proper purpose for the appropriate target, and it is often lost or unused during distribution, and thus does not function as an actual invitation ticket. It is a very difficult reality to settle. As such, a broker who distributes invitation tickets with the performance organizer needs to manage the invitation authority of the new system.

10-2015-0028912 (2015.03.02.)

The technical problem of the present invention is to provide a system capable of managing an overall procedure related to creation, delivery, registration, and confirmation of invitation tickets on a system.

Furthermore, the technical problem of the present invention is to provide a system capable of managing event staff or even 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, checking and managing invitation-related information; A storage unit 220 for storing the invitation ticket related information and the invitation ticket related information generated by the control unit 210; And a communication unit 230 that transmits the invitation ticket related information generated by the control unit 210 to the broker terminal 130, the user terminal 140, or the event hall terminal 150.

The control unit 210 further includes an invitation ticket generation module 212, an invitation ticket delivery module 214, an invitation ticket validation check module 216, and an invitation ticket confirmation module 218, and the invitation ticket generation module 212 is intended to be distributed. The invitation tickets are created and grouped, and the type of ticket, the content of the event, the name of the event, the description of the event, the date and time of the event, whether the event is paid or free, and the event is a paid date In the case of generating invitation-related information including price information, the invitation-to-transfer module 214 generates a URL (uniform resource link) connecting to the invitation-related information to the broker terminal 130, and the generated invitation ticket The validity period and the recipient information to which the invitation ticket can be delivered are added to the group information, and when it is determined that the recipient information to be delivered does not exist in a predetermined database (default), it is automatically added as a member and related information To the database in the storage unit 120, and the invitation-to-transfer module 214, if the recipient information to be delivered is information existing in the database in the storage unit 120, information stored in the database The invitation ticket is delivered by utilizing the invitation ticket, and the invitation ticket delivery module 214 is associated with the invitation ticket delivered through the URL from the server 110 to the broker terminal 130, the user terminal 140, or the venue terminal 150. By checking the information, the route of each invitation group is continuously tracked from where and how.

According to the present invention, the administrator can check the distribution status of the invitation ticket and who is registered as a user, and can check whether the user is registered according to the planning of the invitation ticket based on this, and based on this, the user's position at the performance site It can be checked and supervised, and ultimately, it can prevent re-transaction of invitation tickets through a ticket.

According to the present invention, it is possible to check the status of an invitation ticket that has been distributed but not used, it is possible to check who the unregistered registrant is, and to simplify the procedure for confirming whether the user of the invitation ticket is legitimate.

According to the present invention, if the invitation ticket is not completely free and is partially paid, it can be induced to easily enter the site after payment in advance.

According to the present invention, it is possible to check whether the invitation ticket is used to meet the original purpose by monitoring the entire status from creation, distribution, and use of the invitation ticket to the server.

1 is a network configuration diagram of an invitation management system according to an embodiment of the present specification.
2 is a block diagram of a server in an invitation management system according to an embodiment of the present specification.
Figure 3 is a flow chart of the process of invitation management according to an embodiment of the present specification.

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 to which the present invention pertains can easily practice. However, the present invention can be implemented in many different forms and is not limited to the embodiments disclosed below. In addition, in order to clearly disclose the present invention in the drawings, parts irrelevant to the present invention are omitted, and the same or similar reference numerals in the drawings indicate the same or similar components.

The objects and effects of the present invention may be naturally understood or more apparent 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 through the following detailed description. In addition, in the description of the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. Hereinafter, embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a network configuration diagram of the invitation management system according to an embodiment of the present specification, Figure 2 is a block diagram of a server of the invitation management system according to an embodiment of the present specification.

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 is known as TCP/IP (Transfer Control Protocol/Internet Protocol), LAN (Local Area Network), WIFI, Long Term Evolution (LTE), Wideband Code Division Multiple Access (WCDMA), or other It may be implemented using at least some of wired communication methods, wireless communication methods, and other communication methods that will 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 controller 210 performs necessary control to perform the embodiments described below. In particular, the control unit 210 may generate, transfer, check, and manage invitation-related information. The storage unit 220 stores information related to the invitation ticket generated by the control unit 210 and stores necessary information for performing other embodiments described below. The storage unit 220 may include a database.

The communication unit 230 transmits the invitation ticket related information generated by the control unit 210 to the broker terminal 130. In addition, the communication unit 230 transmits and receives signals necessary to perform other embodiments described below.

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

The control unit 210 receives the user's information from the user terminal 140 and performs a validity check whether the invitation ticket is valid. When validity is confirmed, an invitation ticket is registered to the user terminal 140.

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

The invitation voucher generation module 212 creates and groups invitation vouchers to be distributed by an administrator according to the requirements of the event organizer. At this time, the generated invitation ticket (or invitation group, hereinafter simply referred to as an invitation ticket) is the type of ticket, the content of the event, the name of the event, the description of the event, the date/time of the event, whether it is paid/free, the paid date If it contains the price (e.g. environmental burden) information.

The invitation voucher delivery module 214 generates a uniform resource link (URL) that connects to the invitation voucher related information, and delivers it to the broker terminal 130. At this time, a period during which the invitation ticket can be delivered (also referred to as an expiration date) and a recipient (name, contact information, and a predetermined security code) may be added to the generated invitation ticket group information. Or, it may further include the group code itself.

The URL information may be transmitted to the broker terminal 130 or the user terminal 140 in the form of SMS, such as text, messenger, e-mail.

When it is determined that the recipient information does not exist in a predetermined database (default), the invitation delivery module 214 automatically adds the corresponding user terminal as a member to add related information to the database.

The invitation voucher transfer module 214 transmits the invitation voucher by using the information stored in the database when the recipient is information existing in the database.

The invitation ticket delivery module 214 may retransmit the invitation ticket related information transmitted from the server 110 to the broker terminal 130 through the URL to the user terminal 140. Through this, the server 110 can continuously track the path of how and where each invitation group was delivered.

The invitation voucher delivery module 214 may recognize that the user can register the invitation voucher by checking that the URL is generated and delivered in a packaged form.

The invitation ticket validity check module 216 checks if the terminal receiving the URL is legally eligible to receive the invitation ticket. Such a procedure is called an invitation access procedure, and when a user's name, email, gender, contact number, social security number, and a predetermined security code are input, this is legalized through an algorithm in the database validation check module 114 Check whether or not.

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

The invitation ticket confirmation module 218 checks the user information of the user terminal at the end of the invitation ticket. Through this, the manager can check which process the invitation ticket was finally delivered to. In addition, the broker terminal 130 may check the user information holding the invitation ticket, and may additionally track whether the user terminal 140 delivered by the user retransmits the invitation ticket to another user terminal. The broker terminal 130 may transfer the invitation ticket to the user terminal 140 or to another broker terminal. That is, a user who has received a ticket from a broker can access and use each ticket, or deliver it to another person.

The invitation ticket confirmation module 218 may transmit the corresponding information to the terminal 150 of the event site as well as the administrator terminal 120 or the broker terminal 130.

Through this, the event site terminal 150 (eg, an iPad) receives and compares the invitation ticket 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 at the same time and compares it to the site. You can check if the user you want to enter is a legitimate user.

That is, in the field, enter the registered invitation and personal information of the user on the tablet (eg, iPad), and check the validity again on the server. The user terminal that has received the invitation ticket may register in advance by linking the ID, and in this case, even the process of checking the ID in the field can be simplified. The invitation ticket can be divided into pre-payment and post-payment to receive payment in advance, which greatly simplifies the access procedure at the venue.

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

Through this, only the pre-registered user can easily enter the contact information on the tablet of the event hall or check the identification card to easily perform the access permission. In other words, it is possible to prevent the indiscriminate position from being formed through the vote.

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

The data management module 222 checks and stores all the creation status of the invitation ticket, delivery status, validity check status, admission status at the site, admission time, paid/free status, payment of environmental burden, and payment method.

The data management module 222 may further include a staff information management module 226. At this time, the type of invitation ticket can be classified into one type of staff related to the event, such as the field team, artist team, and security team, and the invitation ticket can be used as a kind of employee ID to manage the staff of the day. In this case, the information related to the invitation ticket includes the status of staff creation, staff team distribution status, staff qualification check status, staff attendance status, staff attendance time, and whether the staff is paid, and similarly to the invitation ticket, the server manages staff-related information. Can.

It is possible to manage the server 110 by checking it on the on-site terminal 150 without having to check whether the staff commute or on-site is checked orally or visually. In this case, the invitation ticket management system may also be referred to as a staff management system, and the administrator terminal 120 connected to the server 110 can check in real time whether the staff is working internally or externally. It can also be used to conduct events.

The data management module 224 may connect to a third-party ticket sales server (eg, a server of a ticket sales agency such as Interpark or its own ticket sales server) to share and manage 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, delivered, validated, or confirmed to perform overall management.

Even if it is not a third-party ticket sales server but a separate terminal or system outside, the information can be checked with the naked eye or checked with a photographed image.

As an example according to the present invention, the invitation ticket information or the ticket information may be separately classified into a group where a ticket is purchased, an invitation ticket group, and a membership group of a club, and may be displayed.

In this case, the on-site terminal 150 may make a separate line according to the group of the invitation ticket, the paid ticket, and the membership, and check the exclusive ticket (invitation ticket, paid ticket, or membership card) on each line to check whether or not admission is possible or to check the validity. .

According to the present invention, the performance organizer may be an administrator himself, or a planner dedicated to the invitation may be an administrator. The broker may be a person who is in charge of distributing invitation tickets, and may be a senior manager or a main manager. The user may actually be the party who uses the ticket or enters the venue.

The broker can also manage information about the group including the type, type, and number of invitation tickets at once.

For example, if 50 of the 100 invitation tickets are completely free and 50 are partly paid, each can be grouped and delivered to different users or different brokers.

In addition, the invitations of each group of 50 cards can also be sent to one broker or user as a group, or divided into two groups of 25 cards or divided into different groups of different numbers to different brokers or users. You can also deliver.

Eventually, the administrator decides the type, number, and type of the first invitation ticket and delivers it to one or more brokers, and each broker can distribute the invitation ticket according to his or her policy or philosophy. You can distribute the invitation ticket. The invitation ticket management system according to the present invention has an effect of monitoring whether the distribution is suitable or not.

After passing the invitation ticket, the administrator can check the trend simply by accessing the server 110 without having to separately manage the broker, and it is convenient because the broker is redistributed after distributing his/her invitation ticket (for example, resale with a ticket) Or not), and if it is detected in the middle, the validity of the ticket may be invalidated.

In other words, the broker can also have the authority to manage the validity of the invitations they have, and can also deliver it to other users or register for themselves.

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

When the invitation ticket delivery module 114 delivers invitation ticket information to the broker terminal 130 or the user terminal 140, the invitation ticket management module 118 deactivates the invitation ticket for all owners of the invitation ticket. However, by granting a separate authority to the broker terminal 130, the validity of the user terminal receiving the invitation ticket information may be invalidated.

When the invitation voucher is deactivated to the broker, and the user or a sub-user registers the invitation voucher, the invitation voucher confirmation module 118 may check this by updating who holds the deactivated voucher.

The user terminal 140 may register the invitation ticket as a situation in which he or she can use the invitation ticket by entering a name, a phone number, or a dedicated code.

One of the broker terminals 130 may be designated as a terminal of a master broker or a main representative.

At this time, the main person among the brokers can check and manage the status of the registrants of the whole invitation ticket separately from the administrator who hosts the event, and can also check and manage the sub-brokers, users, and sub-users who have distributed the invitation tickets.

At this time, the main manager may invalidate or reduce the authority even if a specific user is valid.

The invitation voucher management module may push notification to the terminals of users and sub-users associated with the invitation voucher whether the voucher is valid or changed.

The terminal of the main contact person can grasp the status of the ticket for which the invitation ticket is not registered until the valid time (that is, the final time at which the invitation ticket can be delivered). At this time, the effective time may be extended. In addition, the main person in charge can follow up the route to which the invitation ticket was delivered. Through this, the cancer mark can be removed.

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

In the administrator account, data managed by the server can be identified. The person in charge can check whether the registration is valid or not, and whether or not the ID card (if there is an age limit to the performance) is registered.

According to the present invention, the organizer of the event can check whether the distributed invitation ticket is properly delivered or through which route to the entry, and whether the actually entered user is the same as the original invitation ticket distributor. At this time, all of this route and information can be stored in the database, and the user's gender, age, registration time, and number of transmissions can be reviewed to check whether the invitation ticket has been used for advertising purposes. Validity is checked by mobile phone number, e-mail, etc., and it is continuously checked.

Since the admission status of the invitation ticket to the present invention is checked directly through the on-site terminal, the invitation ticket and the paid invitation ticket (environmental charge) can be settled immediately after the event is completed.

Figure 3 is a flow chart of the process of invitation management according to an embodiment of the present specification.

Referring to FIG. 3, after the host logs in (S310), a new ticket group corresponding to a predetermined number of first events is generated on the application (S320). For example, the first group of 100 invitations to the Ultra Music Festival, the second group of 150, and the third group of 50, that is, a total of three groups may be generated.

Subsequently, the host delivers the ticket of the first group (that is, 100 sheets) to the manager 1 (S332), passes the ticket of the second group (that is, 150 sheets) to the manager 2 (S334), and sends the ticket to the manager 3 3 groups (that is, 50 tickets) are delivered (S336). Through this, the host can monitor the status of the tickets delivered to the administrators 1 to 3.

Manager 1 passes the tickets to their customers, respectively (S342). You can pass one ticket, or you can pass multiple tickets. The customer who received the ticket registers on the application and transmits the information that declares the ticket as a ticket to be used by the server (S352). The server confirms that customer 1 has registered the ticket, and passes this fact to host and manager 1 so that host and manager 1 can monitor the registration status of the ticket.

Manager 2 also delivers tickets to their customers (S344). A single ticket may be delivered, multiple tickets may be delivered, or a plurality of tickets may be delivered to a sub-manager to allow the sub-manager to deliver tickets to each customer (S354).

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

The above-described preferred embodiments of the present invention are disclosed for the purpose of illustration, and those skilled in the art will appreciate various modifications, changes and additions within the spirit and scope of the present invention. It should be regarded as belonging to the above claims.

If a person having ordinary knowledge in the technical field to which the present invention pertains, various substitutions, modifications, and changes are possible without departing from the technical spirit of the present invention. It is not limited by.

In the exemplary system described above, the methods are described based on a flow chart as a series of steps or blocks, but the present invention is not limited to the order of steps, and some steps may occur in a different order or simultaneously with other steps as described above. You can. In addition, those skilled in the art will understand that the steps shown in the flowchart are not exclusive, other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the present invention.

Claims (7)

A control unit 210 for controlling processing and delivery of information necessary for generating, delivering, checking and managing invitation-related information; A storage unit 220 for storing the invitation ticket related information and the invitation ticket related information generated by the control unit 210; And a communication unit 230 that transmits the invitation ticket related information generated by the control unit 210 to the broker terminal 130, the user terminal 140, or the field terminal 150; In 110),
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 generation module 212 generates and groups invitation tickets to be distributed, and the type of ticket, the content of the event, the name of the event, the description of the event, the date and time of the event, Whether the event is paid or free, and when the event is paid, information related to invitation tickets including price information is generated.
The invitation delivery module 214 generates a URL (uniform resource link) connecting to the invitation-related information to the broker terminal 130, and transmits the validity period and recipient information for the invitation ticket delivery to the generated invitation ticket group information. In addition, when the recipient information to be transmitted is information existing in the database in the storage unit 220, the invitation ticket is transmitted by utilizing the information stored in the database,
The invitation ticket delivery module 214 checks information related to the invitation ticket delivered through the URL from the server 110 to the broker terminal 130 and the user terminal 140 to determine how and where each invitation ticket group was delivered. Keep track of your route,
The invitation ticket confirmation module 218 transmits the user information holding the invitation ticket to the field terminal 150, so that the field terminal 150 displays the invitation ticket information displayed on the user terminal 140 and the invitation ticket confirmation module 218 ) By comparing the information transmitted from the legitimate user, characterized in that the mobile ticket security device.
According to claim 1,
The invitation voucher delivery module 214 generates and transmits a URL in the form of an invitation voucher, and the control unit 210 checks that the packaged URL is delivered to determine which user can register the invitation voucher. Mobile ticket security device characterized in that the check.
According to claim 2,
The invitation ticket validity check module 216 receives the broker information from the broker terminal 130 and performs a validity check whether the invitation ticket is valid, and when the validity is confirmed, the invitation ticket delivery module 216 is the broker terminal 130 Process information related to delivering information related to part or all of the invitation ticket to the user terminal,
The validity check module 216 receives the user's information from the user terminal 140 and performs a validity check to see if the invitation voucher is valid, and when the validity is confirmed, the invitation voucher confirmation module 216 invites the user terminal 140 A device for securing a mobile ticket, characterized in that it processes the registration box.
According to claim 1,
The validity check module 216 checks whether the terminal receiving the URL among the broker terminal 130, the user terminal 140, and the field terminal 150 is legally eligible to receive an invitation ticket when connected by a link. Characterized by,
A device for securing a mobile ticket, characterized in that the user's name, email, gender, contact information, social security number, and a predetermined security code are entered to check whether or not they are legal.
According to claim 1,
The invitation ticket confirmation module 118 is a device for securing a mobile ticket, characterized in that it checks the invitation ticket image, the invitation ticket unique number, the invitation ticket unique code, and the registered user's contact information and delivers it to the on-site terminal 150.
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 creation status, delivery status, validity check status, admission status at the site, admission time, paid/free status, payment of environmental burden, and payment method confirmation, etc.
The data management module 222 further includes a staff information management module 226,
The staff information management module 226 is characterized in that the type of invitation ticket is classified as one of a field team, an artist team, and a security team, and transmitted.
The invitation ticket-related information includes at least one of a staff creation status, a staff team distribution status, a staff qualification check status, a staff attendance status, a staff attendance time, and a staff salary payment.
According to claim 1,
The URL information is transmitted to the broker terminal 130 or the user terminal 140 in the form of SMS, messenger, e-mail, and the like.

Images