Ticket management system, ticket management device, ticket management method, and ticket management program

Abstract

To provide a ticket management system, a ticket management device, a ticket management method, and a ticket management program that can associate the right of an event ticket with its owner, and register, store, and manage the relationship between right detail data of the ticket and owner data as right owner management to immediately manage the present owner of the right, a transfer status, an enforcement status, a utilization status, and the like.SOLUTION: A ticket management system acquires a ticket detail request, on the basis of an information code photographed by a terminal device, or a signal received from a beacon by the terminal device, determines whether or not a terminal identifier and a stored user terminal identifier are matched each other, determines whether or not a user can enter an event, when the identifiers are determined to match each other, and controls ticket design data set to a start time when the user can enter so to be displayed on the terminal device of the user, if determined that the user can enter.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to a ticket management system, a ticket management device, a ticket management method, and a ticket management program. [Background technology]

[0002] Conventionally, tickets for events such as sports or performances have been sold at the counter or over the Internet, and after payment has been confirmed, the ticket is delivered to the purchaser by mail, at the counter or via an automatic ticket vending machine, or as an e-ticket over the Internet. Summary of the Invention [Problem to be solved by the invention]

[0003] However, with conventional ticket issuing operations, it was difficult to grasp the status of rights from the time the ticket was issued until entry to the event.

[0004] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a ticket management system, ticket management device, ticket management method, and ticket management program that can instantly manage the current owner, transfer status, execution status, usage status, etc. of the right by linking the right of tickets for various events with their owner, and registering, storing, and managing the relationship between the right detail data of tickets for various events and the owner data as part of the owner management of the right. [Means for solving the problem]

[0005] In order to solve the above-mentioned problems and achieve the object, a ticket management system according to the present invention is a ticket management system in which a ticket issuing system, a terminal device, and a ticket management device comprising a storage unit and a control unit are communicably connected, wherein the storage unit comprises: a ticket detail storage means for storing ticket detail data including a ticket identifier of a ticket for an event, including the start time of the event, and ticket design data set for each of the start times; a user storage means for storing user data including a user identifier of a user and a user terminal identifier of the terminal device of the user; and an ownership relationship storage means for storing ownership relationship data defining a link between the ticket identifier of the ticket and the user identifier of the user who owns the ticket; and the control unit stores an information code photographed by the terminal device and installed at the venue of the event, the event information display system is characterized in that it comprises: a ticket details request acquisition means for acquiring a ticket details request including a terminal identifier of the terminal device from the terminal device based on a signal received by the terminal device from a beacon installed at the venue of the event; a terminal determination means for determining whether the terminal identifier acquired by the ticket details request acquisition means matches the user terminal identifier stored in the user storage means; an entry determination means for determining whether the user is allowed to enter the event based on the ownership relationship data if the terminal determination means determines that the terminal identifier matches the user terminal identifier; and an entry display control means for controlling the user's terminal device to display the ticket design data set for the start time at which the user is allowed to enter if the entry determination means determines that the user is allowed to enter the event.

[0006] In addition, in the ticket management system of the present invention, the admission display control means is characterized in that, when the admission determination means determines that the user is able to enter the event, the ticket design data set for the start time at which the user is able to enter is controlled to be displayed on the user's terminal device after a predetermined time before the start time.

[0007] In addition, in the ticket management system of the present invention, the control unit is characterized by further comprising an ownership registration screen display control means for controlling the display of a ticket ownership registration screen on the terminal device, and a user registration means for registering the user data, including the user identifier of the user, in the user storage means when the user of the terminal device inputs the user data of the user into the ticket ownership registration screen.

[0008] In addition, in the ticket management system of the present invention, the ownership registration screen display control means is characterized in that when the information code on the ticket is photographed by the terminal device, the ticket ownership registration screen for the ticket is displayed on the terminal device.

[0009] In addition, in the ticket management system of the present invention, the control unit is characterized by further comprising an ownership relationship registration means for registering in the ownership relationship storage means the ownership relationship data that defines the link between the ticket identifier of the ticket photographed by the terminal device and the user identifier registered by the user registration means.

[0010] In addition, in the ticket management system of the present invention, the user registration means is further characterized in that, when the ticket detail data of the ticket of the user of the terminal device has not been registered in the ticket detail storage means and the ticket detail data of the ticket has been entered by the user into the ticket ownership registration screen, the user registration means registers the ticket detail data including the ticket identifier of the ticket in the ticket detail storage means.

[0011] In addition, in the ticket management system of the present invention, the control unit is characterized by further comprising an ownership relationship registration means for registering the ownership relationship data defining the link between the ticket identifier registered by the user registration means and the user identifier registered by the user registration means in the ownership relationship storage means.

[0012] In addition, in the ticket management system of the present invention, the control unit is characterized by comprising: a ticket details confirmation screen display control means that, when a ticket details confirmation request is received from the terminal device, controls the terminal device to display a ticket details confirmation screen that allows the user to input the ticket identifier; a ticket determination means that determines whether the input ticket identifier input into the ticket details confirmation screen by the user of the terminal device matches the ticket identifier stored in the ticket details storage means; and a ticket details display control means that, when the ticket determination means determines that the input ticket identifier matches the ticket identifier, controls the terminal device to display the ticket details data corresponding to the ticket identifier.

[0013] In addition, in the ticket management system of the present invention, the control unit is characterized by comprising: a user confirmation screen display control means that, when a user confirmation request is received from the terminal device, controls the terminal device to display a user confirmation screen for inputting the user identifier; a user determination means that determines whether the input user identifier input into the user confirmation screen by the user of the terminal device matches the user identifier stored in the user storage means; and a user display control means that, when the user determination means determines that the input user identifier matches the user identifier, controls the terminal device to display the user data corresponding to the user identifier.

[0014] In addition, in the ticket management system of the present invention, the control unit is characterized in that it comprises an ownership relationship confirmation screen display control means that, when an ownership relationship confirmation request is received from the terminal device, controls the terminal device to display an ownership relationship confirmation screen that allows the user to input the ticket identifier and the user identifier; an ownership relationship determination means that determines whether the input ticket identifier and input user identifier input into the ownership relationship confirmation screen by the user of the terminal device match the ticket identifier and the user identifier stored in the ownership relationship storage means; and an ownership relationship display control means that, when the ownership relationship determination means determines that the input ticket identifier and input user identifier match the ticket identifier and the user identifier, controls the terminal device to display the ownership relationship data corresponding to the ticket identifier and the user identifier.

[0015] Further, in a ticket management device according to the present invention, the ticket management device comprises a memory unit and a control unit communicably connected to a ticket issuing system and a terminal device, wherein the memory unit comprises a ticket detail storage means for storing ticket detail data including a ticket identifier of a ticket for an event including a start time of the event and ticket design data set for each start time, a user storage means for storing user data including a user identifier of a user and a user terminal identifier of the terminal device of the user, and an ownership relationship storage means for storing ownership relationship data defining a link between the ticket identifier of the ticket and the user identifier of the user who owns the ticket, and the control unit stores an information code photographed by the terminal device and installed at the venue of the event, or a ticket design data photographed by the terminal device and set at the venue of the event. and a ticket detail request acquisition means for acquiring from the terminal device a ticket detail request including the terminal identifier of the terminal device based on a signal received from a beacon installed at the venue of the event; a terminal determination means for determining whether the terminal identifier acquired by the ticket detail request acquisition means matches the user terminal identifier stored in the user storage means; an admission determination means for determining whether the user is allowed to enter the event based on the ownership relationship data if the terminal determination means determines that the terminal identifier matches the user terminal identifier; and an admission display control means for controlling the user's terminal device to display the ticket design data set for the start time at which the user is allowed to enter if the admission determination means determines that the user is allowed to enter the event.

[0016] Further, a ticket management method according to the present invention is a ticket management method to be executed by a ticket management system that communicably connects a ticket issuing system, a terminal device, and a ticket management device that has a memory unit and a control unit, wherein the memory unit comprises ticket detail storage means that stores ticket detail data including a ticket identifier of a ticket for an event including a start time of the event and ticket design data set for each start time, user storage means that stores user data including a user identifier of a user and a user terminal identifier of the terminal device of the user, and ownership relationship storage means that stores ownership relationship data that defines a link between the ticket identifier of the ticket and the user identifier of the user who owns the ticket, and the ticket management method is executed by the control unit, and a ticket details request acquisition step of acquiring a ticket details request including a terminal identifier of the terminal device from the terminal device based on a signal received by the device from a beacon installed at the venue of the event; a terminal determination step of determining whether the terminal identifier acquired in the ticket details request acquisition step matches the user terminal identifier stored in the user storage means; an entry determination step of determining whether the user is allowed to enter the event based on the ownership relationship data if it is determined in the terminal determination step that the terminal identifier matches the user terminal identifier; and an entry display control step of controlling the user's terminal device to display the ticket design data set for the start time at which the user is allowed to enter if it is determined in the entry determination step that the user is allowed to enter the event.

[0017] Further, a ticket management method according to the present invention is a ticket management method to be executed by a ticket management device that is communicably connected to a ticket issuing system and a terminal device and that includes a memory unit and a control unit, wherein the memory unit includes a ticket detail storage means that stores ticket detail data including a ticket identifier of a ticket for an event, including a start time of the event, and ticket design data set for each start time, a user storage means that stores user data including a user identifier of a user and a user terminal identifier of the terminal device of the user, and an ownership relationship storage means that stores ownership relationship data that defines a link between the ticket identifier of the ticket and the user identifier of the user who owns the ticket, and the ticket management method is executed by the control unit, and The method includes a ticket details request acquisition step for acquiring a ticket details request including a terminal identifier of the terminal device from the terminal device based on a signal received from a beacon installed at the venue of the event; a terminal determination step for determining whether the terminal identifier acquired in the ticket details request acquisition step matches the user terminal identifier stored in the user storage means; an entry determination step for determining whether the user is allowed to enter the event based on the ownership relationship data if it is determined in the terminal determination step that the terminal identifier matches the user terminal identifier; and an entry display control step for controlling the user's terminal device to display the ticket design data set for the start time at which the user is allowed to enter if it is determined in the entry determination step that the user is allowed to enter the event.

[0018] Further, a ticket management program according to the present invention is a ticket management program to be executed by a ticket management device that is communicably connected to a ticket issuing system and a terminal device and that includes a memory unit and a control unit, wherein the memory unit includes a ticket detail storage means that stores ticket detail data including a ticket identifier of a ticket for an event, including the start time of the event, and ticket design data set for each of the start times, a user storage means that stores user data including a user identifier of a user and a user terminal identifier of the terminal device of the user, and an ownership relationship storage means that stores ownership relationship data that defines a link between the ticket identifier of the ticket and the user identifier of the user who owns the ticket, and the control unit stores an information code photographed by the terminal device and installed at the venue of the event, or a ticket design data set by the terminal device. The method is characterized by executing the following steps: a ticket details request acquisition step for acquiring a ticket details request including a terminal identifier of the terminal device from the terminal device based on a signal received from a beacon installed at the event venue; a terminal determination step for determining whether the terminal identifier acquired in the ticket details request acquisition step matches the user terminal identifier stored in the user storage means; an entry determination step for determining whether the user is allowed to enter the event based on the ownership relationship data if it is determined in the terminal determination step that the terminal identifier matches the user terminal identifier; and an entry display control step for controlling the user's terminal device to display the ticket design data set for the start time at which the user is allowed to enter if it is determined in the entry determination step that the user is allowed to enter the event. [Effects of the Invention]

[0019] The present invention has the advantage of preventing fraudulent use, such as the illegal sale, unauthorized use, improper trading, or improper resale of rights. Furthermore, the present invention has the advantage of enabling ticket issuers to strictly manage the sale, execution, and use of event tickets without changing existing ticket sales methods. Furthermore, the present invention has the advantage of easily establishing new ticket issuance and management methods. Furthermore, the present invention has the advantage of enabling the owner of an event ticket (admission right), managing the transfer of rights, and restricting ticket use, thereby preventing counterfeit or fraudulent tickets from entering the event and preventing improper sales. Specifically, the present invention has the advantage of preventing improper resale, such as high-price resale, by specifying various resale restrictions at the time of ticket issuance, thereby preventing scalping. Furthermore, the present invention has the advantage of enabling performance organizers to directly obtain data on ticket purchasers. The present invention also has the advantage that even if a ticket purchaser is unable to attend a performance, if there is another person who wishes to purchase tickets for that performance, the ticket rights can be transferred for a fee. The present invention also has the advantage that ticket purchasers are prevented from purchasing high-priced tickets from auctions or scalpers, and can only purchase officially resold tickets. The present invention also has the advantage that, when tickets are considered as certificates of rights, the fulfillment of rights can be managed from reservations to the completion of various dining and drinking experiences at restaurants, travel, or other various experience services. The present invention also has the advantage of managing the fulfillment of rights to receive goods through pre-orders, etc. The present invention also has the advantage that mobile admission tickets of different colors and / or designs can be issued for each event, making it easier for staff to identify admissions. In other words, according to the present invention, the tickets sent to smartphones at the event venue have their photos, colors and / or designs changed for each performance, so that admission management staff can distinguish between the admission tickets for each performance at a glance, making it easy to identify only the attendees for that performance.As a result, according to the present invention, admission management can be smoothly carried out without incurring any costs, which not only reduces the burden on attendees and staff, but also enables attendees to keep the tickets, which have different designs for each session and are sent to their smartphones at the event venue, as souvenirs. [Brief explanation of the drawings]

[0020] [Figure 1] FIG. 1 is a diagram showing an example of a conventional ticket issuing operation. [Figure 2] FIG. 2 is a diagram showing an example of a ticket management system according to this embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a ticket management system according to this embodiment. [Figure 4] FIG. 4 is a diagram showing an example of a ticket management system according to this embodiment. [Figure 5] FIG. 5 is a block diagram showing an example of the configuration of a ticket management system according to this embodiment. [Figure 6] FIG. 6 is a flowchart showing an example of processing in the ticket management system according to this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of an outline of data registration in this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of data registration in this embodiment. [Figure 9] FIG. 9 is a diagram showing an example of data registration in this embodiment. [Figure 10] FIG. 10 is a diagram showing an example of data confirmation in this embodiment. [Figure 11] FIG. 11 is a diagram showing an example of data confirmation in this embodiment. [Figure 12] FIG. 12 is a diagram showing an example of data confirmation in this embodiment. [Figure 13] FIG. 13 is a diagram showing an example of ownership transfer registration in this embodiment. [Figure 14]FIG. 14 is a flowchart showing an example of processing in the ticket management system according to this embodiment. [Figure 15] FIG. 15 is a diagram showing an example of the entrance management process in this embodiment. [Figure 16] FIG. 16 is a diagram showing an example of ticket design data in this embodiment. [Figure 17] FIG. 17 is a diagram showing an example of the entrance management process in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0021] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

[0022] [1. Overview] First, an overview of the present invention will be described with reference to Fig. 1 to Fig. 4. Fig. 1 is a diagram showing an example of a conventional ticket issuing operation. Fig. 2 to Fig. 4 are diagrams showing an example of a ticket management system in this embodiment.

[0023] As shown in Figure 1, in the past, when a customer applied for event tickets to a ticket issuing system via a website, the customer selected a method of obtaining the tickets ([1] receiving an e-ticket, [2] delivery to home, or [3] receiving at the theater) and performed payment processing. After payment was confirmed, the user could then choose to [2] receive the tickets by mail, [3] receive them at the counter, [3] receive the tickets via an automated ticket vending machine, or [1] receive the e-ticket via the Internet. Therefore, in the past, it was not possible to manage the current owner of the ticket after it was issued, the status of ticket transfers, the status of ticket redemption, or the status of ticket usage.

[0024] Therefore, in this embodiment, as shown in Figure 2, when the ticket owner (or representative) (1) reads the QR code (registered trademark) printed on the ticket with a smartphone or the like, the ticket owner calls up the ticket ownership registration site, and (2) checks the ticket detail data pre-registered by the ticket issuing system, or, if not registered, prompts the ticket owner to register the ticket detail data. Then, as shown in Figure 2, in this embodiment, (3) when user data is registered by the ticket owner, (4) ownership relationship data linking the ticket detail data and the user data is registered.

[0025] In this embodiment, as shown in Figure 3, the ticket issuance system may manage ticket issuance and sales, and the ticket management device may manage ticket rights and ownership, or as shown in Figure 4, the ticket issuance system may manage ticket issuance, and the ticket management device may manage ticket sales, rights and ownership.

[0026] [2. Ticket Management System Configuration] An example of the configuration of a ticket management system in which a ticket issuing system 600, a terminal device 100, and a server (ticket management device) 200 according to this embodiment are communicatively connected will be described with reference to Fig. 5. Fig. 5 is a block diagram showing an example of the configuration of the ticket management system according to this embodiment.

[0027] [Configuration of terminal device 100] In FIG. 5, the terminal device 100 may be a mobile terminal such as a mobile phone, a smartphone, a tablet terminal, a PHS or a PDA (Personal Digital Assistant), or an information processing device such as a commercially available desktop or notebook personal computer.

[0028] The terminal device 100 includes a control unit 102, a storage unit 106, an image capturing unit 110, and an input / output unit 112, and the units included in the terminal device 100 are communicably connected via any communication path. The terminal device 100 also has a short-range wireless communication function, and can receive signals (transmitted from a beacon or the like) such as Wi-Fi (registered trademark), Bluetooth (registered trademark), infrared, NFC-A, NFC-B, and / or NFC-F (for example, FeliCa (registered trademark)).

[0029] The input / output unit 112 may have a function of inputting and outputting data (I / O). Here, the input / output unit 112 may be, for example, a key input unit, a touch panel, a control pad (for example, a touch pad, a game pad, etc.), a mouse, a keyboard, a microphone, etc. The input / output unit 112 may also be a display unit (for example, a display, monitor, touch panel, etc., made of liquid crystal or organic electroluminescence, etc.) that displays (input / output) information of an application, etc. The input / output unit 112 may also be an audio output unit (for example, a speaker, etc.) that outputs audio information as audio. The input / output unit 112 may also be a fingerprint sensor and / or a biometric sensor such as a vein sensor.

[0030] The photographing unit 110 may be a camera that records images (still images and moving images) taken by an imaging element such as a CCD image sensor or a CMOS image sensor as digital data. The photographing unit 110 may also be a biometric sensor such as a camera (for example, an infrared camera) that can be used for iris authentication or face authentication.

[0031] The terminal device 100 has a function of communicatively connecting with other devices via a network 300 and exchanging data with the other devices. Here, the network 300 has a function of communicatively connecting the terminal device 100, the server 200, and the ticket issuing system 600 with each other, and is, for example, the Internet and / or a LAN (Local Area Network).

[0032] The storage unit 106 stores various databases, tables, and / or files. The storage unit 106 stores computer programs that cooperate with an operating system (OS) to issue commands to a central processing unit (CPU) to perform various processes. The storage unit 106 may be, for example, a random access memory (RAM), a read-only memory (ROM), a hard disk drive (HDD), and / or a solid state drive (SSD). The storage unit 106 may store image data recorded by the imaging unit 110, data received via the network 300, and / or input data input via the input / output unit 112.

[0033] The control unit 102 is a CPU or the like that performs overall control of the terminal device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processes based on these stored programs. For example, the control unit 102 may execute processes such as acquiring image data recorded by the imaging unit 110, reading text data (such as a URL) included in the image data, sending and receiving data via the network 300, acquiring input data entered via the input / output unit 112, and displaying data (on the screen) on the input / output unit 112.

[0034] [Server 200 configuration] 5, the server 200 may be an information processing device such as a personal computer or a workstation. The server 200 includes a control unit 202 and a storage unit 206, and the units included in the server 200 are connected to each other so as to be able to communicate with each other via any communication path. The server 200 is connected to the terminal device 100 or the ticket issuing system 600 via the network 300 so as to be able to communicate with each other.

[0035] The memory unit 206 stores various databases, tables, and / or files. The memory unit 206 records computer programs that work in cooperation with the OS to issue instructions to the CPU to perform various processes. The memory unit 206 is a storage means such as RAM, ROM, HDD, and / or SSD, and stores various databases and tables. Functionally, the memory unit 206 includes a ticket details database 206a, a user database 206b, and an ownership relationship database 206c.

[0036] The ticket details database 206a stores ticket identifiers for tickets for events, including the start times of those events, and ticket details data, including ticket design data set for each start time. Here, the ticket identifiers may include the ticket name, ticket ID, ticket issuance time, event start time, event end time, admission time slot, venue name, venue ID, seat name, seat ID, entrance name, and / or entrance ID, etc. The ticket details data may also include the event name, event ID, and / or ticket price, etc. The ticket design data may also have different photos, colors, and / or designs for each event start time.

[0037] The user database 206b stores user data including the user's user identifier (user name (such as name) and / or user ID, etc.). Here, the user database 206b may also store user data including the user terminal identifier (such as mobile phone number, IP address and / or MAC address) of the user's terminal device. The user data may also include gender, date of birth, telephone number, email address, address, occupation, and / or name of place of employment, etc.

[0038] The ownership relationship database 206c stores ownership relationship data that defines the association between the ticket identifier (ticket name and / or ticket ID, etc.) of a ticket and the user identifier (user name and / or user ID, etc.) of the user who owns the ticket. Here, the ownership relationship data may define the association between the ticket identifier and the user identifier of the current owner and / or the user identifier of a past owner.

[0039] The control unit 202 is a CPU or the like that performs overall control of the server 200. The control unit 202 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processes based on these stored programs. In terms of functional concept, the control unit 202 includes an ownership registration screen display control unit 202a, a user registration unit 202b, an ownership relationship registration unit 202c, a ticket details confirmation screen display control unit 202d, a ticket judgment unit 202e, a ticket details display control unit 202f, a user confirmation screen display control unit 202g, a user judgment unit 202h, a user display control unit 202i, an ownership relationship confirmation screen display control unit 202j, an ownership relationship judgment unit 202k, an ownership relationship display control unit 202m, an approval notification unit 202n, an ownership transfer registration unit 202p, a ticket details request acquisition unit 202q, a terminal judgment unit 202r, an entrance judgment unit 202s, and an entrance display control unit 202t.

[0040] The ownership registration screen display control unit 202a controls the terminal device 100 to display a ticket ownership registration screen. Here, when an information code (display) on a ticket is photographed by the terminal device 100, the ownership registration screen display control unit 202a may also control the terminal device 100 to display a ticket ownership registration screen for that ticket. Here, the information code on the ticket may be a barcode (one-dimensional code), a two-dimensional code, a multi-dimensional code (for example, a three-dimensional code), or the like.

[0041] When the user of the terminal device 100 inputs user data of the user into the ticket ownership registration screen, the user registration unit 202b registers the user data including the user identifier of the user into the user database 206b. Here, when the ticket detail data of the ticket of the user of the terminal device 100 has not been registered in the ticket detail database 206a and the ticket detail data of the ticket has been input by the user into the ticket ownership registration screen, the user registration unit 202b may register the ticket detail data including the ticket identifier of the ticket into the ticket detail database 206a.

[0042] The ownership relationship registration unit 202c registers, in the ownership relationship database 206c, ownership relationship data that defines the link between the ticket identifier of the ticket photographed by the terminal device 100 and the user identifier registered by the user registration unit 202b. Here, the ownership relationship registration unit 202c may register, in the ownership relationship database 206c, ownership relationship data that defines the link between the ticket identifier registered by the user registration unit 202b and the user identifier registered by the user registration unit 202b.

[0043] When a ticket detail confirmation request is received from the terminal device 100, the ticket detail confirmation screen display control unit 202d causes the terminal device 100 to display a ticket detail confirmation screen that prompts the user to input a ticket identifier.

[0044] The ticket determining unit 202e determines whether or not the ticket identifier entered by the user of the terminal device 100 on the ticket details confirmation screen matches the ticket identifier stored in the ticket details database 206a.

[0045] When the ticket determination unit 202e determines that the input ticket identifier matches the ticket identifier, the ticket details display control unit 202f controls the terminal device 100 to display the ticket details data stored in the ticket details data corresponding to the ticket identifier.

[0046] When a user confirmation request is received from the terminal device 100, the user confirmation screen display control unit 202g controls the terminal device 100 to display a user confirmation screen that prompts the user to input a user identifier.

[0047] The user determination unit 202h determines whether or not the input user identifier input by the user of the terminal device 100 on the user confirmation screen matches the user identifier stored in the user database 206b.

[0048] If the user determination unit 202h determines that the input user identifier matches the user identifier, the user display control unit 202i controls the terminal device 100 to display the user data stored in the user database 206b corresponding to the user identifier.

[0049] When an ownership relationship confirmation request is received from the terminal device 100, the ownership relationship confirmation screen display control unit 202j controls the terminal device 100 to display an ownership relationship confirmation screen that prompts the user to input a ticket identifier and a user identifier.

[0050] The ownership relationship determination unit 202k determines whether the input ticket identifier and input user identifier input by the user of the terminal device 100 on the ownership relationship confirmation screen match the ticket identifier and user identifier stored in the ownership relationship database 206c.

[0051] When the ownership relationship determination unit 202k determines that the input ticket identifier and input user identifier match the ticket identifier and user identifier, the ownership relationship display control unit 202m controls the terminal device 100 to display the ownership relationship data stored in the ownership relationship database 206c corresponding to the ticket identifier and the user identifier.

[0052] When the payment process for the transfer of ownership of a ticket by the user who is the ticket transferee is completed, if the approval notification unit 202n obtains approval for the transfer of ownership (by inputting a PIN number, etc.) from the terminal device 100 of the user who is the ticket transferee, it notifies the user who is the transferee of the approval identifier for the transfer of ownership.

[0053] When the ownership transfer registration unit 202p receives an ownership transfer registration request from the terminal device 100 of the transferee user, which request includes the ticket identifier of the ticket, the transferor's user identifier, and the approval identifier, it updates the ownership relationship data stored in the ownership relationship database 206c by changing the user identifier linked to the ticket identifier from the transferor's user identifier to the transferee's user identifier.

[0054] The ticket details request acquisition unit 202q acquires a ticket details request including the terminal identifier of the terminal device 100 from the terminal device 100 based on an information code (display) photographed by the terminal device 100 and installed at the event venue, or a signal received by the terminal device 100 from a beacon or the like installed at the event venue. Here, the information code installed at the event venue may be a barcode (one-dimensional code), a two-dimensional code, a multi-dimensional code (for example, a three-dimensional code), or the like.

[0055] The terminal determination unit 202r determines whether the terminal identifier acquired by the ticket detail request acquisition unit 202q matches the user terminal identifier stored in the user database 206b.

[0056] If the terminal determination unit 202r determines that the terminal identifier matches the user terminal identifier stored in the ownership relationship database 206c, the entry determination unit 202s determines whether the user is allowed to enter the event based on the ownership relationship data stored in the ownership relationship database 206c.

[0057] When the admission determination unit 202s determines that the user is permitted to enter the event, the admission display control unit 202t controls the user's terminal device 100 to display ticket design data (admission permit (admission ticket) data) set for the start time at which the user is permitted to enter. Furthermore, when the admission determination unit 202s determines that the user is permitted to enter the event, the admission display control unit 202t may also control the user's terminal device 100 to display ticket design data set for the start time at which the user is permitted to enter, after a predetermined time before the start time. Furthermore, when the admission determination unit 202s determines that the user is permitted to enter the event, the admission display control unit 202t may also control the ticket issuing system 600 to display the ticket detail data stored in the ticket detail database 206a and an admission permission notice, and may also control the user's terminal device 100 to display the ticket detail data stored in the ticket detail database 206a.

[0058] [3. Ticket Management System Processing] An example of the processing of the ticket management system according to this embodiment will be described with reference to FIGS.

[0059] [Ownership transfer registration process] An example of ownership transfer registration processing according to this embodiment will be described with reference to Fig. 6 to Fig. 13. Fig. 6 is a flowchart showing an example of processing by the ticket management system according to this embodiment.

[0060] As shown in Figure 6, when a user (transferor) uses the imaging unit 110 of the terminal device (smartphone) 100 to scan a QR code (registered trademark) on a ticket for an event (such as a performance or a sporting event), and the control unit 102 of the smartphone 100 sends a ticket ownership registration screen display request to the server 200, including the ticket identifier read from the scanned QR code (registered trademark), the ownership registration screen display control unit 202a of the server 200 controls the input / output unit 112 of the smartphone 100 to display the ticket ownership registration screen (step SA-1).

[0061] Then, the user registration unit 202b of the server 200 determines whether or not the ticket detail data of the transferor's ticket is registered in the ticket detail database 206a based on the ticket ownership registration screen display request (step SA-2).

[0062] If the user registration unit 202b of the server 200 determines that the ticket detail data of the transferor's ticket is registered in the ticket detail database 206a (step SA-2: Yes), the process proceeds to step SA-4.

[0063] On the other hand, if the user registration unit 202b of the server 200 determines that the ticket detail data of the transferor's ticket is not registered in the ticket detail database 206a (step SA-2: No), it shifts the process to step SA-3.

[0064] Then, the ownership registration screen display control unit 202a of the server 200 controls the display of the ticket ownership registration screen to prompt the user to input ticket detail data, and when the transferor inputs the ticket detail data for the ticket into the ticket ownership registration screen via the input / output unit 112 of the smartphone 100, the user registration unit 202b of the server 200 registers the ticket detail data including the ticket identifier in the ticket detail database 206a (step SA-3).

[0065] Then, the ownership registration screen display control unit 202a of the server 200 controls the display of the ticket ownership registration screen to prompt the user to enter user data, and when the transferor's user data is entered into the ticket ownership registration screen via the input / output unit 112 of the smartphone 100, the user registration unit 202b of the server 200 registers the user data including the transferor's user identifier in the user database 206b (step SA-4).

[0066] Then, the ownership relationship registration unit 202c of the server 200 registers in the ownership relationship database 206c the ticket identifier of the ticket that was previously registered in the ticket details database 206a, or ownership relationship data that defines the link between the ticket identifier registered by the user registration unit 202b and the user identifier registered by the user registration unit 202b (step SA-5).

[0067] An example of data registration in this embodiment will now be described with reference to Fig. 7 to Fig. 9. Fig. 7 is a diagram showing an example of an outline of data registration in this embodiment. Fig. 8 and Fig. 9 are diagrams showing an example of data registration in this embodiment.

[0068] 7, in this embodiment, when a user scans a QR code (registered trademark) on an admission ticket for an event using smartphone 100, a ticket ownership registration screen is displayed on smartphone 100, and when the user registers the ticket detail data and user data related to the admission ticket, the ownership relationship data is registered. Note that while this embodiment shows a case in which the ownership relationship data is registered automatically, the user may set and register the ownership relationship data based on the ticket detail data and user data related to the admission ticket.

[0069] Furthermore, as shown in FIG. 8, in this embodiment, when the user clicks the ticket details registration button on the ticket ownership registration screen with the ticket ID field left blank and the ticket is photographed, ticket details data is registered.

[0070] Also, as shown in Figure 9, in this embodiment, when a user clicks the user registration button on the ticket ownership registration screen with the user ID field left blank and a photograph of the user's face is taken, a user ID is assigned and the user is able to register user data such as name, gender, date of birth, mobile phone number, address, occupation and place of employment.

[0071] Returning to Figure 6, when a ticket ownership registration screen display request is sent to the server 200 by the control unit 102 of the smartphone 100 of a new user (transferee), the ownership registration screen display control unit 202a of the server 200 controls the input / output unit 112 of the transferee's smartphone 100 to display the ticket ownership registration screen (step SA-6).

[0072] Then, when the transferee inputs user data including the transferee's facial photograph data into the ticket ownership registration screen, the user registration unit 202b of the server 200 registers the user data including the transferee's user identifier in the user database 206b (step SA-7). Note that in this embodiment, before user registration, the transferee can view the ticket detail data of the event ticket stored in the ticket detail database 206a, the transferor's user data stored in the user database 206b, and / or the ownership relationship data of the ticket stored in the ownership relationship database 206c.

[0073] An example of data confirmation in this embodiment will now be described with reference to Fig. 7 and Fig. 10 to Fig. 12. Fig. 10 to Fig. 12 are diagrams showing an example of data confirmation in this embodiment.

[0074] As shown in FIG. 7, in this embodiment, a user can request confirmation of each piece of data to confirm the ticket detail data registered in the ticket detail database 206a, the user data registered in the user database 206b, and / or the ownership relationship data registered in the ownership relationship database 206c, all relating to the admission ticket.

[0075] Furthermore, as shown in FIG. 10, in this embodiment, when the user inputs a ticket ID into the ticket ID field on the ticket details confirmation screen and clicks the ticket details confirmation button, the ticket details data is displayed.

[0076] Furthermore, as shown in FIG. 11, in this embodiment, when the user inputs a user ID in the user ID field on the user confirmation screen and clicks the user confirmation button, the user data is displayed.

[0077] Also, as shown in Figure 12, in this embodiment, when a user enters a ticket ID or user ID into the ownership relationship confirmation screen and clicks the ownership confirmation button, the ticket ID and user ID linked to the ticket are displayed.

[0078] Returning to Figure 6, when the payment process for the transfer of ticket ownership by the transferee is completed, if the approval notification unit 202n of the server 200 obtains approval for the transfer of ownership from the smartphone 100 of the ticket transferor by the transferor inputting a PIN number via the input / output unit 112 of the smartphone 100, the approval notification unit 202n notifies the transferee of the approval identifier for the transfer of ownership (step SA-8).

[0079] Then, the ownership transfer registration unit 202p of the server 200 determines whether or not it has received an ownership transfer registration request including the ticket identifier of the ticket entered via the input / output unit 112 of the transferee's smartphone 100, the transferor's user identifier, and the approval identifier for the transfer of ownership of the ticket (step SA-9).

[0080] Then, if the ownership transfer registration unit 202p of the server 200 determines that an ownership transfer registration request has been received (step SA-9: Yes), it shifts the process to step SA-10.

[0081] Then, the ownership transfer registration unit 202p of the server 200 updates the ownership relationship data stored in the ownership relationship database 206c by changing the user identifier linked to the ticket identifier of the ticket from the user identifier of the transferor to the user identifier of the transferee (step SA-10), and terminates the processing.

[0082] An example of ownership transfer registration in this embodiment will now be described with reference to Fig. 13. Fig. 13 is a diagram showing an example of ownership transfer registration in this embodiment.

[0083] As shown in Figure 13, in this embodiment, when the transferee enters the ticket ID of the ticket, the transferor's user ID, and the ownership transfer approval ID, and clicks the ownership transfer registration button, the registration of the transfer of ownership of the ticket from the transferor to the transferee is completed.

[0084] Returning to FIG. 6, if the ownership transfer registration unit 202p of the server 200 determines that the ownership transfer registration request has not been acquired (step SA-9: No), it ends the process.

[0085] As described above, in this embodiment, (1) the rights assignor registers ticket detail data as a procedure required for transferring rights to an event ticket, (2) the rights assignee checks the ticket detail data, registers the assignee's user data as the intended owner data, and pays the transfer fee to the management account as a procedure required for the rights transfer, (3) the rights assignor confirms the receipt of the transfer fee in the management account and consents to the transfer of rights in the rights ownership relationship data registration, and (4) immediately after the consent of both the rights assignor and the rights assignee at the time of the rights transfer is confirmed, the transfer of ticket ownership is officially registered. Note that this embodiment provides a system in which the processes (1) to (4) operate in real time.

[0086] Furthermore, in this embodiment, the ownership transfer registration process using a QR code (registered trademark) has been described, but the ownership transfer registration process may also be performed using not only a QR code (registered trademark), but also a barcode or other information code, etc., to enable registration and / or confirmation of ticket details and / or ticket owners.

[0087] [Admission Management Processing] An example of the entrance management process according to this embodiment will be described with reference to Fig. 14 to Fig. 17. Fig. 14 is a flowchart showing an example of the process of the ticket management system according to this embodiment.

[0088] As shown in FIG. 14, the ticket details request acquisition unit 202q of the server 200 acquires (receives) a ticket details request including the terminal identifier of the smartphone 100 from the smartphone 100 based on a QR code (registered trademark) installed at the event venue that is photographed by the user using the smartphone 100, or a signal received by the terminal device 100 from a beacon installed at the event venue (step SB-1).

[0089] Then, the terminal determination unit 202r of the server 200 determines whether the terminal identifier acquired by the ticket detail request acquisition unit 202q matches the user terminal identifier of the user's smartphone 100 stored in the user database 206b (step SB-2).

[0090] If the terminal determination unit 202r of the server 200 determines that the terminal identifier and the user terminal identifier do not match (step SB-2: No), the process proceeds to step SB-3.

[0091] Then, the admission display control unit 202t of the server 200 controls the user terminal device 100 to display an admission denial notice (step SB-3), and the process ends.

[0092] On the other hand, if the terminal determination unit 202r of the server 200 determines that the terminal identifier and the user terminal identifier match (step SB-2: Yes), it moves the process to step SB-4.

[0093] Then, the admission determination unit 202s of the server 200 determines whether the user is allowed to enter the event based on the event ID stored in the ticket details database 206a, the user data including the user ID and user terminal identifier stored in the user database 206b, and the ownership relationship data stored in the ownership relationship database 206c (step SB-4).

[0094] If the admission determination unit 202s of the server 200 determines that the user is not permitted to enter the event (step SB-4: No), the process proceeds to step SB-3.

[0095] On the other hand, if the admission determination unit 202s of the server 200 determines that the user is permitted to enter the event (step SB-4: Yes), the process proceeds to step SB-5.

[0096] Then, the entrance display control unit 202t of the server 200 controls the display of the ticket design data stored in the ticket details database 206a, which is set to the start time at which the user can enter, on the user's terminal device 100 starting one hour before that start time (step SB-5), and ends the processing.

[0097] A specific example of the entrance management process in this embodiment will now be described with reference to Fig. 15. Fig. 15 is a diagram showing an example of the entrance management process in this embodiment.

[0098] As shown in Figure 15, in this embodiment, when a user scans an admission QR code (registered trademark) located near the entrance to the event with a smartphone 100, the ticket details and admission OK are displayed on the ticket issuing system 600 (such as the PC or tablet of an event staff member), and the ticket details are displayed on the user's own smartphone 100.

[0099] A specific example of the admission management process in this embodiment will be described with reference to Fig. 16 and Fig. 17. Fig. 16 is a diagram showing an example of ticket design data in this embodiment. Fig. 17 is a diagram showing an example of the admission management process in this embodiment.

[0100] In this embodiment, when a user reads an admission QR code (registered trademark) posted at the entrance to a concert venue with smartphone 100, or receives and decodes a signal transmitted from a beacon or the like installed at the event venue with smartphone 100, if the electronic ticket purchased by the user is for a performance on the day, the electronic ticket is automatically registered as attendance on the day, and admission ticket data (admission permit data) is sent to the user's smartphone 100 one hour before the start of the performance. The user can then enter the venue simply by presenting the admission ticket data displayed on smartphone 100 to the admission management staff during the permitted admission time slot.

[0101] In this embodiment, as shown in FIG. 16, admission pass data is issued by changing the photo and / or background color of the admission ticket for each concert start time, so that, as shown in FIG. 17, the performance admission management staff can instantly determine whether or not a person is attending a concert that starts at 7 p.m. today without having to check the small text displayed on the user's smartphone 100, and can instantly allow entry to a user who presents ticket design data for today's start at 7 p.m., and deny entry to a user who presents ticket design data for yesterday's start at 3 p.m.

[0102] In this embodiment, the history management of various data is mainly performed by storing data in various databases, but it is also possible to use a method of storing history in the data itself using blockchain technology.

[0103] 4. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0104] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0105] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0106] Furthermore, the components of the terminal device 100, the server 200, and the ticket issuing system 600 shown in the figures are conceptual functional components, and do not necessarily have to be physically configured as shown in the figures.

[0107] For example, all or any part of the processing functions of the terminal device 100 and the server 200, particularly the processing functions performed by the control units 102 and 202, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the terminal device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). The computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0108] In addition, this computer program may be stored in an application program server connected to the terminal device 100 and the server 200 via any network 300, and it is also possible to download all or part of it as needed.

[0109] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0110] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0111] The various databases stored in memory unit 106 and memory unit 206 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0112] The terminal device 100 and the server 200 may be configured as information processing devices such as known personal computers or workstations, or may be configured as such information processing devices to which any peripheral devices are connected. The terminal device 100 and the server 200 may be realized by installing software (including programs, data, etc.) that causes the devices to perform the processes described in this embodiment.

[0113] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0114] The present invention is useful in industries such as service industries that issue tickets and manage admission to events. [Explanation of symbols]

[0115] 100 Terminal Device 102 Control section 106 Storage section 110 Filming Department 112 Input / output section 200 servers 202 Control section 202a Ownership registration screen display control unit 202b User Registration Section 202c Ownership Registration Division 202d Ticket details confirmation screen display control unit 202e Ticket Judgment Department 202f Ticket detail display control unit 202g User confirmation screen display control section 202h User identification section 202i User display control section 202j Ownership relationship confirmation screen display control section 202k Ownership Determination Section 202m Ownership display control section 202n Approval notification section 202p Ownership Transfer Registration Section 202q Ticket Detail Request Acquisition Unit 202r Terminal determination unit 202s Admission Judgment Department 202t Entrance display control unit 206 Memory section 206a Ticket Detail Database 206b User Database 206c Ownership Database 300 Network 600 Ticket Issuance System

Claims

1. A ticket management system in which a ticket issuing system, a terminal device, and a ticket management device having a storage unit and a control unit are communicatively connected, The storage unit a ticket detail storage means for storing ticket detail data including a plurality of start times of an event, ticket identifiers of tickets for the event, and ticket design data in which a different design is set for each of the start times; a user storage means for storing user data including a user identifier of a user and a user terminal identifier of the terminal device of the user; an ownership relationship storage means for storing ownership relationship data that defines a link between the ticket identifier of the ticket and the user identifier of the user who owns the ticket; Equipped with The control unit an ownership registration screen display control means for controlling the terminal device to display a ticket ownership registration screen; a user registration means for registering, in the user storage means, user data including a user identifier of the user and a user terminal identifier of the terminal device of the user when the user data of the user of the terminal device is input to the ticket ownership registration screen by the user of the terminal device; an approval notification means for notifying the user who is the transferee of an approval identifier for the transfer of ownership of the ticket when the transfer of ownership of the ticket is approved by the transferor at the terminal device of the user who is the transferor and approval of the transfer of ownership is obtained from the terminal device of the transferor; an ownership transfer registration means, when receiving an ownership transfer registration request from the terminal device of the transferee, the ownership transfer registration request including the ticket identifier of the ticket, the user identifier of the transferor, and the approval identifier for the transfer of ownership of the ticket, for updating the ownership relationship data stored in the ownership relationship storage means by changing the user identifier linked to the ticket identifier from the user identifier of the transferor to the user identifier of the transferee; a ticket details request acquisition means for acquiring a ticket details request including a terminal identifier of the terminal device from the terminal device based on an information code photographed by the terminal device and installed at the venue of the event, or a signal received by the terminal device from a beacon installed at the venue of the event; a terminal determination means for determining whether the terminal identifier acquired by the ticket detail request acquisition means matches the user terminal identifier stored in the user storage means; an admission determination means for determining whether or not the user is permitted to enter the event based on the ownership relationship data when the terminal determination means determines that the terminal identifier and the user terminal identifier match; an entrance display control means for controlling, when the entrance determination means determines that the user is permitted to enter the event, the ticket design data set for the start time at which the user is permitted to enter the event to be sent to the user's terminal device a predetermined time before the start time, so that the ticket design data is displayed on the user's terminal device after the predetermined time before the start time; A ticket management system comprising:

2. The ownership registration screen display control means 2. The ticket management system according to claim 1, wherein when the information code on the ticket is photographed by the terminal device, the ticket ownership registration screen for the ticket is displayed on the terminal device.

3. The control unit an ownership relationship registration means for registering in the ownership relationship storage means the ownership relationship data that defines the association between the ticket identifier of the ticket photographed by the terminal device and the user identifier registered by the user registration means; 3. The ticket management system according to claim 2, further comprising:

4. The user registration means The ticket management system described in claim 1 further characterized in that, when the ticket detail data of the ticket of the user of the terminal device has not been registered in the ticket detail storage means and the ticket detail data of the ticket is entered by the user into the ticket ownership registration screen, the ticket detail data including the ticket identifier of the ticket is registered in the ticket detail storage means.

5. The control unit an ownership relationship registration means for registering in the ownership relationship storage means the ownership relationship data that defines the link between the ticket identifier registered by the user registration means and the user identifier registered by the user registration means; 5. The ticket management system according to claim 4, further comprising:

6. The control unit a ticket details confirmation screen display control means for controlling the terminal device to display a ticket details confirmation screen for inputting the ticket identifier when a ticket details confirmation request is received from the terminal device; a ticket determination means for determining whether an input ticket identifier input on the ticket details confirmation screen by the user of the terminal device matches the ticket identifier stored in the ticket details storage means; a ticket detail display control means for controlling the terminal device to display the ticket detail data corresponding to the ticket identifier when the ticket determination means determines that the input ticket identifier matches the ticket identifier; 2. The ticket management system according to claim 1, further comprising:

7. The control unit a user confirmation screen display control means for controlling the terminal device to display a user confirmation screen for inputting the user identifier when a user confirmation request is received from the terminal device; a user determination means for determining whether an input user identifier input on the user confirmation screen by the user of the terminal device matches the user identifier stored in the user storage means; a user display control means for controlling the terminal device to display the user data corresponding to the user identifier when the user determination means determines that the input user identifier matches the user identifier; 2. The ticket management system according to claim 1, further comprising:

8. The control unit an ownership relationship confirmation screen display control means for controlling the terminal device to display an ownership relationship confirmation screen for inputting the ticket identifier and the user identifier when an ownership relationship confirmation request is received from the terminal device; an ownership relationship determination means for determining whether or not an input ticket identifier and an input user identifier input by the user of the terminal device on the ownership relationship confirmation screen match the ticket identifier and the user identifier stored in the ownership relationship storage means; an ownership relationship display control means for controlling the terminal device to display the ownership relationship data corresponding to the ticket identifier and the user identifier when the ownership relationship determination means determines that the input ticket identifier and the input user identifier match the ticket identifier and the user identifier; 6. The ticket management system according to claim 1, further comprising:

9. A ticket management device including a memory unit and a control unit, the ticket management device being communicably connected to a ticket issuing system and a terminal device, The storage unit a ticket detail storage means for storing ticket detail data including a plurality of start times of an event, ticket identifiers of tickets for the event, and ticket design data in which a different design is set for each of the start times; a user storage means for storing user data including a user identifier of a user and a user terminal identifier of the terminal device of the user; an ownership relationship storage means for storing ownership relationship data that defines a link between the ticket identifier of the ticket and the user identifier of the user who owns the ticket; Equipped with The control unit an ownership registration screen display control means for controlling the terminal device to display a ticket ownership registration screen; a user registration means for registering, in the user storage means, user data including a user identifier of the user and a user terminal identifier of the terminal device of the user when the user data of the user of the terminal device is input to the ticket ownership registration screen by the user of the terminal device; an approval notification means for notifying the user who is the transferee of an approval identifier for the transfer of ownership of the ticket when the transfer of ownership of the ticket is approved by the transferor at the terminal device of the user who is the transferor and approval of the transfer of ownership is obtained from the terminal device of the transferor; an ownership transfer registration means, when receiving an ownership transfer registration request from the terminal device of the transferee, the ownership transfer registration request including the ticket identifier of the ticket, the user identifier of the transferor, and the approval identifier for the transfer of ownership of the ticket, for updating the ownership relationship data stored in the ownership relationship storage means by changing the user identifier linked to the ticket identifier from the user identifier of the transferor to the user identifier of the transferee; a ticket details request acquisition means for acquiring a ticket details request including a terminal identifier of the terminal device from the terminal device based on an information code photographed by the terminal device and installed at the venue of the event, or a signal received by the terminal device from a beacon installed at the venue of the event; a terminal determination means for determining whether the terminal identifier acquired by the ticket detail request acquisition means matches the user terminal identifier stored in the user storage means; an admission determination means for determining whether or not the user is permitted to enter the event based on the ownership relationship data when the terminal determination means determines that the terminal identifier and the user terminal identifier match; an entrance display control means for controlling, when the entrance determination means determines that the user is permitted to enter the event, the ticket design data set for the start time at which the user is permitted to enter the event to be sent to the user's terminal device a predetermined time before the start time, so that the ticket design data is displayed on the user's terminal device after the predetermined time before the start time; A ticket management device comprising:

10. A ticket management method to be executed by a ticket management system in which a ticket issuing system, a terminal device, and a ticket management device including a storage unit and a control unit are communicatively connected, the method comprising: The storage unit a ticket detail storage means for storing ticket detail data including a plurality of start times of an event, ticket identifiers of tickets for the event, and ticket design data in which a different design is set for each of the start times; a user storage means for storing user data including a user identifier of a user and a user terminal identifier of the terminal device of the user; an ownership relationship storage means for storing ownership relationship data that defines a link between the ticket identifier of the ticket and the user identifier of the user who owns the ticket; Equipped with Executed by the control unit, an ownership registration screen display control step of controlling the terminal device to display a ticket ownership registration screen; a user registration step of registering, in the user storage means, user data including a user identifier of the user and a user terminal identifier of the terminal device of the user when the user data of the user of the terminal device is input to the ticket ownership registration screen by the user of the terminal device; an approval notification step of notifying the user who is the transferee of an approval identifier for the transfer of ownership of the ticket when the transfer of ownership of the ticket is approved by the transferor at the terminal device of the user who is the transferor and approval of the transfer of ownership is obtained from the terminal device of the transferor; an ownership transfer registration step of updating the ownership relationship data stored in the ownership relationship storage means by changing the user identifier linked to the ticket identifier from the user identifier of the transferor to the user identifier of the transferee when an ownership transfer registration request including the ticket identifier of the ticket, the user identifier of the transferor, and the approval identifier for the transfer of ownership of the ticket is received from the terminal device of the transferee; a ticket details request acquisition step of acquiring a ticket details request including a terminal identifier of the terminal device from the terminal device based on an information code photographed by the terminal device and installed at the venue of the event, or a signal received by the terminal device from a beacon installed at the venue of the event; a terminal determination step of determining whether the terminal identifier acquired in the ticket detail request acquisition step matches the user terminal identifier stored in the user storage means; an admission determination step of determining whether or not the user is permitted to enter the event based on the ownership relationship data when it is determined in the terminal determination step that the terminal identifier and the user terminal identifier match; an entrance display control step of, if it is determined in the entrance determination step that the user is permitted to enter the event, sending the ticket design data set to the start time at which the user is permitted to enter to the user's terminal device a predetermined time before the start time, and controlling the ticket design data to be displayed on the user's terminal device after the predetermined time before the start time; A ticket management method comprising:

11. A ticket management method to be executed by a ticket management device that is communicably connected to a ticket issuing system and a terminal device and includes a storage unit and a control unit, the method comprising: The storage unit a ticket detail storage means for storing ticket detail data including a plurality of start times of an event, ticket identifiers of tickets for the event, and ticket design data in which a different design is set for each of the start times; a user storage means for storing user data including a user identifier of a user and a user terminal identifier of the terminal device of the user; an ownership relationship storage means for storing ownership relationship data that defines a link between the ticket identifier of the ticket and the user identifier of the user who owns the ticket; Equipped with Executed by the control unit, an ownership registration screen display control step of controlling the terminal device to display a ticket ownership registration screen; a user registration step of registering, in the user storage means, user data including a user identifier of the user and a user terminal identifier of the terminal device of the user when the user data of the user of the terminal device is input to the ticket ownership registration screen by the user of the terminal device; an approval notification step of notifying the user who is the transferee of an approval identifier for the transfer of ownership of the ticket when the transfer of ownership of the ticket is approved by the transferor at the terminal device of the user who is the transferor and approval of the transfer of ownership is obtained from the terminal device of the transferor; an ownership transfer registration step of updating the ownership relationship data stored in the ownership relationship storage means by changing the user identifier linked to the ticket identifier from the user identifier of the transferor to the user identifier of the transferee when an ownership transfer registration request including the ticket identifier of the ticket, the user identifier of the transferor, and the approval identifier for the transfer of ownership of the ticket is received from the terminal device of the transferee; a ticket details request acquisition step of acquiring a ticket details request including a terminal identifier of the terminal device from the terminal device based on an information code photographed by the terminal device and installed at the venue of the event, or a signal received by the terminal device from a beacon installed at the venue of the event; a terminal determination step of determining whether the terminal identifier acquired in the ticket detail request acquisition step matches the user terminal identifier stored in the user storage means; an admission determination step of determining whether or not the user is permitted to enter the event based on the ownership relationship data when it is determined in the terminal determination step that the terminal identifier and the user terminal identifier match; an entrance display control step of, if it is determined in the entrance determination step that the user is permitted to enter the event, sending the ticket design data set to the start time at which the user is permitted to enter to the user's terminal device a predetermined time before the start time, and controlling the ticket design data to be displayed on the user's terminal device after the predetermined time before the start time; A ticket management method comprising:

12. A ticket management program to be executed by a ticket management device that is communicably connected to a ticket issuing system and a terminal device and that includes a storage unit and a control unit, The storage unit a ticket detail storage means for storing ticket detail data including a plurality of start times of an event, ticket identifiers of tickets for the event, and ticket design data in which a different design is set for each of the start times; a user storage means for storing user data including a user identifier of a user and a user terminal identifier of the terminal device of the user; an ownership relationship storage means for storing ownership relationship data that defines a link between the ticket identifier of the ticket and the user identifier of the user who owns the ticket; Equipped with In the control unit, an ownership registration screen display control step of controlling the terminal device to display a ticket ownership registration screen; a user registration step of registering, in the user storage means, user data including a user identifier of the user and a user terminal identifier of the terminal device of the user when the user data of the user of the terminal device is input to the ticket ownership registration screen by the user of the terminal device; an approval notification step of notifying the user who is the transferee of an approval identifier for the transfer of ownership of the ticket when the transfer of ownership of the ticket is approved by the transferor at the terminal device of the user who is the transferor and approval of the transfer of ownership is obtained from the terminal device of the transferor; an ownership transfer registration step of updating the ownership relationship data stored in the ownership relationship storage means by changing the user identifier linked to the ticket identifier from the user identifier of the transferor to the user identifier of the transferee when an ownership transfer registration request including the ticket identifier of the ticket, the user identifier of the transferor, and the approval identifier for the transfer of ownership of the ticket is received from the terminal device of the transferee; a ticket details request acquisition step of acquiring a ticket details request including a terminal identifier of the terminal device from the terminal device based on an information code photographed by the terminal device and installed at the venue of the event, or a signal received by the terminal device from a beacon installed at the venue of the event; a terminal determination step of determining whether the terminal identifier acquired in the ticket detail request acquisition step matches the user terminal identifier stored in the user storage means; an admission determination step of determining whether or not the user is permitted to enter the event based on the ownership relationship data when it is determined in the terminal determination step that the terminal identifier and the user terminal identifier match; an entrance display control step of, if it is determined in the entrance determination step that the user is permitted to enter the event, sending the ticket design data set to the start time at which the user is permitted to enter to the user's terminal device a predetermined time before the start time, and controlling the ticket design data to be displayed on the user's terminal device after the predetermined time before the start time; A ticket management program to run

Images