Ticket information management system, control method for ticket information management system, and control program for ticket information management system

Abstract

To provide a ticket information management device capable of management without waste even when tickets being securities or the like are issued in advance, a ticket information management control method, and a ticket information management program.SOLUTION: A ticket information management device system 1 includes: a management server 10; an X company server 50 of an X company which is a provision destination of movie viewing tickets; and a theater server 110 of a theater where movies are viewed using the tickets. The management server 10 stores ticket contents information including ticket identification information and ticket unique information. The tickets are provided to the provision destination in a state in which ticket validation information of the identification information is yet-to-be validated, and the ticket validation information is validated after receipt information indicating that the ticket unique information is received by the provision destination is received.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a ticket information management device for managing various ticket information such as movie tickets, a control method for the ticket information management device, and a ticket information management program. [Background technology]

[0002] BACKGROUND ART Conventionally, there have been movie tickets designated for specific films that are issued and sold before the screening period, and methods for managing information on these tickets have been proposed (for example, Patent Document 1, etc.). Furthermore, such movie tickets are considered "securities" because they have a value equivalent to the amount spent to see the movie (for example, 1,800 yen). For this reason, when tickets are issued in advance, such as through advance sales, before the performance, the pre-sale tickets received at the sales point such as a theater must be managed as securities. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-73877 Summary of the Invention [Problem to be solved by the invention]

[0004] However, many of these tickets issued in advance are never actually distributed to users, and because the validity period is printed on the ticket, it often expires. For this reason, even if a large amount of money is spent to manage ticket information as securities, much of it may end up being wasted, which has been a problem.

[0005] Therefore, the present invention can efficiently manage tickets even when the tickets are issued in advance as securities. Ticket information management that can be managed system , ticket information management system stem Control method and ticket information management Controlling the system The purpose is to provide a program.

[0006] The above object is achieved by the present invention, which provides a ticket information management system having a ticket information management device for managing tickets, a delivery company server of a delivery company that delivers the tickets, a mobile terminal of a user to whom the tickets are to be provided, and a mobile terminal of a delivery person of the delivery company, the system having a ticket information storage unit that stores at least ticket identification information and ticket content information, and a ticket unique information storage unit that stores at least ticket unique information having the ticket identification information, the ticket content information including ticket validation information, the ticket unique information being provided to the delivery company server in a state where the ticket validation information of the corresponding ticket identification information has not yet been validated, the delivery company server associating delivery identification information with the ticket unique information, and Sending The delivery person's mobile terminal transmits the delivery identification information, the ticket unique information, and the ticket to the providing device. destination The present invention is achieved by a ticket information management system characterized in that the ticket information management device transmits receipt information indicating that the ticket has been delivered to the delivery company server, and the delivery company server transmits receipt confirmation information together with the delivery identification information to the ticket information management device, and upon receiving the receipt information, the ticket information management device performs an activation process on the ticket activation information of the ticket identification information associated with the delivery identification information without waiting for an activation request from the mobile terminal of the user who is the recipient, and the user's mobile terminal can access the ticket information management device after the activation process to invalidate the ticket activation information of the ticket identification information.

[0007] According to the above configuration, the ticket is not validated until it is provided to the recipient and ticket receipt information is received from the recipient. Therefore, the ticket does not need to be treated as a security until it is validated, which reduces the cost of managing the ticket.

[0008] Preferably, the ticket-unique information of the ticket information management device is displayed or stored in a storage medium and provided to the recipient.

[0013] The object of the present invention is achieved by a control method for a ticket information management system having a ticket information management device that manages tickets, a delivery company server of a delivery company that delivers the tickets, a mobile terminal of a user to whom the tickets are provided, and a mobile terminal of a delivery person of the delivery company, the control method comprising: a ticket information storage unit that stores at least ticket identification information and ticket content information; and a ticket unique information storage unit that stores at least ticket unique information having the ticket identification information, the ticket content information including ticket validation information, the ticket unique information being provided to the delivery company server in a state where the ticket validation information of the corresponding ticket identification information has not yet been validated; the delivery company server associating delivery identification information with the ticket unique information, and Sending The delivery person's mobile terminal transmits the delivery identification information, the ticket unique information, and the ticket to the providing device. destination and transmits receipt information indicating that the ticket has been delivered to the delivery company server, the delivery company server then transmits receipt confirmation information together with the delivery identification information to the ticket information management device, and upon receiving the receipt information, the ticket information management device performs an activation process on the ticket validation information of the ticket identification information associated with the delivery identification information without waiting for an activation request from the mobile terminal of the user who is the recipient, and the user's mobile terminal can access the ticket information management device after the activation process to invalidate the ticket validation information of the ticket identification information.

[0014] The object of the present invention is to provide a ticket information management system having a ticket information management device for managing tickets, a delivery company server of a delivery company that delivers the tickets, a mobile terminal of a user to whom the tickets are to be provided, and a mobile terminal of a delivery person of the delivery company, the ticket information management system having at least a ticket identification information and a ticket content information storage unit that stores therein ticket unique information having at least the ticket identification information, the ticket content information including ticket validation information, and the ticket unique information being provided to the delivery company server in a state where the ticket validation information of the corresponding ticket identification information has not yet been validated, the delivery company server associating delivery identification information with the ticket unique information, and Sending a function of transmitting the delivery identification information to the ticket information management device, and a function of transmitting the delivery identification information, the ticket unique information, and the ticket to the delivery person's mobile terminal. destination a function of the delivery company server transmitting receipt information indicating that the ticket has been delivered to the delivery company server, a function of the delivery company server transmitting receipt confirmation information together with the delivery identification information to the ticket information management device, a function of the ticket information management device, upon receiving the receipt information, validating the ticket validation information of the ticket identification information associated with the delivery identification information without waiting for an validation request from the mobile terminal of the user who is the recipient, and a function of the user's mobile terminal being able to invalidate the ticket validation information of the ticket identification information by accessing the ticket information management device after the validation process. [Effects of the Invention]

[0015] As described above, the present invention is applicable to cases where tickets, which are securities, etc., are issued in advance. Ticket information management that can be managed efficiently system , ticket information management system Control method and ticket information management Controlling the system The advantage is that the program can be provided. [Brief explanation of the drawings]

[0016] [Figure 1] 1 is a schematic diagram showing the main configuration of a "movie ticket information management system 1" according to a first embodiment and other embodiments, which has a management server 10, for example, which is a "ticket information management device" of the present invention. [Figure 2] FIG. 2 is a schematic block diagram showing the main components of the user's mobile terminal 120, the X company's staff member's mobile terminal 130, the delivery person's mobile terminal 140, and the like shown in FIG. [Figure 3] 2 is a schematic block diagram showing the main configuration of the management server 10 of FIG. 1. FIG. [Figure 4] FIG. 2 is a schematic block diagram showing the main configuration of a management-side first various information storage unit. [Figure 5] FIG. 10 is a schematic block diagram showing the main configuration of a management-side second various information storage unit. [Figure 6] 2 is a schematic block diagram showing the main configuration of a server 50 of company X in FIG. 1. FIG. [Figure 7] FIG. 10 is a schematic block diagram showing the main configuration of a various information storage unit on Company X's side. [Figure 8] 1 is a schematic flowchart showing a first embodiment of the present invention. [Figure 9] 5 is another schematic flowchart showing the first embodiment of the present invention. [Figure 10] FIG. 1 is a schematic diagram showing a "movie ticket (card)." [Figure 11] 5 is a schematic flowchart showing a second embodiment of the present invention. [Figure 12] 10 is a schematic flowchart showing a third embodiment of the present invention. [Figure 13] 10 is a schematic flowchart showing a fourth embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0017] Preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings. The embodiments described below are preferred examples of the present invention, and therefore various technically preferable limitations are applied. However, the scope of the present invention is not limited to these embodiments unless otherwise specified in the following description to the effect that the present invention is specifically limited.

[0018] (Configurations common to the first embodiment and other embodiments) FIG. 1 is a schematic diagram showing the main configuration of a movie ticket information management system 1 according to a first embodiment and other embodiments of the present invention, which includes a management server 10, for example, as a ticket information management device.

[0019] As shown in FIG. 1, the system 1 includes a management server 10, a device to which the movie ticket is provided, such as a company X server 50 of company X, a delivery company server 100 of a delivery company that delivers the ticket, and a theater server 110 of a theater where the movie is viewed using the ticket. In addition, this theater server 110 is controllably connected to a two-dimensional code reading device 111 that reads ticket-unique information, such as a matrix two-dimensional code (hereinafter referred to as a "two-dimensional code"), which is installed at the entrances and exits of the theater and will be described later, and a gate device 112 that is a device that regulates entry to the theater. Furthermore, this ticket unique information includes not only a two-dimensional code but also a character string, a one-dimensional code, and the like. The two-dimensional code reader 111 is not limited to such a device, but may be a reader for reading barcodes such as two-dimensional codes using an imaging device such as a camera.

[0020] Furthermore, the system 1 has a mobile terminal 120 of a user, such as Mr. Y, who uses the ticket and is also the recipient, a mobile terminal 130 of a person in charge of ordering the ticket at Company X, and a mobile terminal 140 of a delivery person from a delivery company. As shown in FIG. 1, the management server 10, X Company server 50, delivery company server 100, theater server 110, user's mobile terminal 120, X Company staff member's mobile terminal 130, delivery person's mobile terminal 140, etc. are connected to each other so that they can communicate with each other via the Internet network 2, base stations 3a, 3b, 3c, etc.

[0021] In addition, each device such as the management server 10 in Figure 1 has a computer, which has a CPU (Central Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), a hard disk, etc., and is connected via a bus. Such devices may be deployed as a so-called "cloud," which offers the advantages of non-stop operation and no backup required.

[0022] FIG. 2 is a schematic block diagram showing the main components of the user's mobile terminal 120, the X company's staff member's mobile terminal 130, the delivery person's mobile terminal 140, and the like shown in FIG. These terminal devices 120 etc. have almost the same configuration, so the configuration will be explained below using the user's mobile terminal 120 as an example, and explanations of the other terminals will be omitted.

[0023] As shown in FIG. 2, the user's mobile terminal 120 has a terminal-side control unit 121, which is configured to control a "terminal-side communication device 122" and a "touch panel 123" for communicating with external devices, etc. This "touch panel 123" is an electronic component that combines a display, which is a display unit, with a position input device, and is an input device that allows the user to input various information by touching what is displayed on the display. The control unit 121 also controls the "terminal side various information storage unit 124" shown in FIG.

[0024] FIG. 3 is a schematic block diagram showing the main configuration of the management server 10 of FIG. As shown in Figure 3, the management server 10 has a management-side control unit 11, which is configured to control a "management-side communication device 12" for communicating with external devices, a display unit for displaying various information, such as a "management-side display 13," and a "management-side various information input device 14" for inputting various information. The control unit 11 also controls the "management side first various information storage unit 20" and the "management side second various information storage unit 30" in Figure 3, and Figures 4 and 5 are schematic block diagrams showing the main configurations of the "management side first various information storage unit 20" and the "management side second various information storage unit 30", respectively. The contents of each block of the "management-side first various information storage unit 20" and the "management-side second various information storage unit 30" will be described later with reference to FIGS. 4 and 5, etc.

[0025] FIG. 6 is a schematic block diagram showing the main configuration of the server 50 of company X shown in FIG. As shown in FIG. 6, Company X's server 50 has Company X's control unit 51, which is configured to control an "X's communication device 52" for communicating with external devices, a display unit for displaying various information, such as an "X's display 53," and an "X's various information input device 54" for inputting various information. The control unit 51 also controls the "X company various information storage unit 60" in FIG. 6, and FIG. 7 is a schematic block diagram showing the main configuration of the "X company various information storage unit 60". The contents of this "X company's various information storage unit 60" will be described later.

[0026] (First embodiment) 8 and 9 are schematic flow charts showing a first embodiment of the present invention using the above-described configuration. In this embodiment, an example will be described below in which a recipient, for example, an individual "Mr. Y," wishes to purchase a ticket, for example, a movie ticket, in advance before the screening period. First, in step (hereinafter referred to as "ST") 1 of FIG. 8, Mr. Y accesses the "management server 10" of FIG. 1 via his own "user's mobile terminal 120" of FIG. Mr. Y then applies for and pays for one movie ticket, which allows him to choose and watch one of several films screening during the screening period from May 1 to July 31, 2021. This ticket allows an individual, "Mr. Y," to select any one movie from a group of movies that includes multiple movies during the screening period and reserve a seat for it. When applying, Mr. Y enters his name, address, telephone number, etc.

[0027] Next, the process proceeds to ST2. In ST2, the "ticket information generation unit (program) 21" of the management server 10 shown in Fig. 4 operates to generate Mr. Y's "movie ticket information." Specifically, ticket identification information, such as the "movie ticket identification number (123456)," ticket content information, such as the "movie group (movie A, movie B, movie C, etc.)," ​​Mr. Y's "name," "address," "telephone number," "PIN code," and "email address," etc., are associated and stored as related information in the ticket information storage unit in Figure 4, such as the "movie ticket information storage unit 22." The generating unit 21 also generates, for example, two-dimensional code information that stores the "ticket identification number" and "PIN number" out of the related information, and stores the information in the storage unit 22. Therefore, the storage unit 22 is an example of a two-dimensional code information storage unit.

[0028] Next, the process proceeds to ST3. In ST3, the management company of the management server 10 creates a movie ticket (card) by attaching a two-dimensional code to a pre-prepared card made of resin or the like, which contains the movie ticket identification number (123456) and the personal identification number stored in the memory unit 22. FIG. 10 is a schematic diagram showing the "movie ticket (card)" created in this process. This "movie ticket (card)" is an example of a storage medium, such as a card-shaped object made of paper or resin, such as a business card, and has a "movie ticket identification number (123456)," a "PIN number," and a "two-dimensional code" displayed on its surface. In the present invention, the ticket is not limited to a card-shaped one as in this embodiment, but may be a storage medium equipped with a memory for storing data, and the code that can uniquely identify the ticket (such as "ticket identification number (123456)", "PIN number" and "two-dimensional code") may be stored internally as data rather than on the surface.

[0029] Next, the process proceeds to ST4. In ST4, the management company of the management server 10 requests a delivery company to deliver the "movie ticket (card)" to Mr. Y's house. Next, the process proceeds to ST5. In ST5, the delivery company server 100 of the delivery company in Fig. 1 associates the "movie ticket identification number (123456)" of the "movie ticket (card)" with the "delivery identification number (7891011)" and transmits this delivery identification number and movie ticket number to the management server 10.

[0030] Next, the process proceeds to ST6. In ST6, the management server 10 associates this "delivery identification number (7891011)" with the "movie ticket identification number (123456)" and stores them in the movie ticket information storage unit 22 of FIG. Next, the process proceeds to ST7. In ST7, when a delivery person from a delivery company delivers the "movie ticket (card)" to Mr. Y's house, the delivery person uses his / her "delivery person's mobile terminal 140" in Fig. 1 to send information that the movie ticket (card) has been delivered to Mr. Y's house to the "delivery company server 100" in Fig. 1. Specifically, the delivery identification number, the information on the two-dimensional code, and other information are sent to the "delivery company server 100" as delivery completion information, for example, "receipt completion information."

[0031] Then, when the delivery company server 100 receives and confirms this "receipt information" from the "delivery person's mobile terminal 140", the delivery company server 100 sends "receipt confirmation information" along with the "delivery identification number (7891011)" to the management server 10.

[0032] Next, proceed to ST8. In ST8, when the "validation processing unit (program) 23" of the management server 10 in Figure 4 receives the "receipt confirmation information," which is the receipt information, it validates the "movie ticket information" in Figure 4 for the "ticket identification number (123456)" associated with the "delivery identification number (7891011)" (specifically, it validates it for the period "May 1 to July 31, 2021"). Here, "validation" refers to the movie ticket becoming usable, and means that it has become a security.

[0033] Thus, according to this embodiment, even if the "movie ticket (card)" is lost before it arrives at Mr. Y's house, as long as it has not yet been activated, it is simply a card or the like and not a security, making it easy to handle and reducing the cost of managing the ticket. Furthermore, according to this embodiment, the "movie ticket (card)" is activated when it actually arrives at Mr. Y's house, so the "movie ticket (card)" can be activated at the appropriate time, and the "movie ticket (card)" can be managed efficiently.

[0034] Furthermore, in this embodiment, even if Mr. Y loses his "movie ticket (card)" after the activation process, he can access the management server 10 via his mobile terminal 120 and provide his name, address, telephone number, etc., so that the ticket can be invalidated as shown in the "movie ticket information storage unit 22" in Figure 4.

[0035] In this case, the new "movie ticket (card)" can be validated by setting a new "movie ticket identification number," re-sending it, and obtaining "receipt confirmation information" as described above. In this way, by performing the validation and invalidation processes, the "movie ticket (card)" can be easily reissued.

[0036] Furthermore, according to this embodiment, if a "movie ticket (card)" that has been validated is lost and then used by a third party, it will be invalidated and unusable, and information about the original right holder of the fraudulently used "movie ticket (card)" will be known, making it easy to discover the route of fraudulent use.

[0037] Next, the process by which Mr. Y, who has obtained a validated "movie ticket (card)," actually watches a movie at a theater will be described below. First, in ST11 in FIG. 9, Mr. Y goes to the theater and has the two-dimensional code displayed on the "movie ticket (card)" in FIG. 10 read by the "two-dimensional code reader 111" in the theater shown in FIG.

[0038] Next, the process proceeds to ST12. In ST12, the two-dimensional code reader 111 transmits the two-dimensional code that it has read to the theater server 110 in FIG. Next, the process proceeds to ST13. In ST13, the theater server 110 transmits to the management server 10 information on the read two-dimensional code, information on the movie currently being shown at the theater, and the like.

[0039] Next, the process proceeds to ST14. In ST14, the "information confirmation processing unit (program) 24" of the management server 10 in Fig. 4 operates to identify the "movie ticket identification number (123456)" based on the information in the received two-dimensional code, and refer to the "movie ticket information." Then, the ticket information is checked to see if it is valid, if it matches the movie information, whether it is valid, whether it is within the screening period, etc. If all of the conditions are met, the management server 10 transmits an "approval" signal to the theater server 110.

[0040] Next, the process proceeds to ST 15. In ST 15, upon receiving the "approval" signal, the theater server 110 transmits an "entrance permitted" signal to the gate device 112 of the theater, and the gate device 112 "opens" the gate.

[0041] Next, the process proceeds to ST16. In ST16, when the theater server 110 receives a signal from the gate device 112 that the theater gate has been opened, it transmits the “ticket identification number (123456)” and “open information” to the management server 10.

[0042] Next, the process proceeds to ST17. In ST17, the "invalidation processing unit (program) 25" of the management server 10 in Fig. 4 operates to cancel the "validation information" of the "movie ticket information" of the "ticket identification number (123456)" and mark it as "invalidated (used)."

[0043] This invalidates the "movie ticket (card)" and makes it impossible to use it again, thereby reliably preventing fraudulent use.

[0044] Furthermore, in this embodiment, one "movie ticket (card)" has been described as ticket information for one person and one movie, etc., but the present invention is not limited to this, and one "movie ticket (card)" can also be used as tickets for multiple people and multiple movies, etc., in which case it is possible to process each ticket as "used." Therefore, the same card can be used multiple times, and there is no need to leave the card at the theater as evidence of use after each use. Furthermore, in the present invention, unlike the present embodiment, one "movie ticket (card)" may be a "multiple-ticket type." In this case, one "movie ticket (card)" can be used to watch a movie or the like multiple times.

[0045] Furthermore, in this embodiment, an example has been described in which the "movie ticket (card)" is validated by the management server 10, but the "validation" process may be performed at a theater or the like. Furthermore, unlike this embodiment, the present invention may be configured such that "Mr. Y" specifies the theater, film, screening, and seat in advance on the management server 10 or the theater's reservation site before going to the theater, etc., and inputs the "ticket identification number" which is unique information that he possesses, and a reservation number is issued after a determination is made as to whether it can be used, and then presents (inputs) the "reservation number" when he arrives at the theater, etc., and it is exchanged for a seat ticket.

[0046] (Second embodiment) FIG. 11 is a schematic flow chart showing a second embodiment of the present invention using the above-described configuration. In this embodiment, an example will be described below in which a provider, for example, Company X (corporation), wishes to purchase a large number of tickets, for example, movie tickets, for sales promotion purposes in advance of a screening period.

[0047] First, in ST21, a person in charge of Company X accesses the management server 10 via the person in charge's mobile terminal 139 of Company X in Figure 1 and places an order for 100,000 card-shaped "movie tickets (cards)" for a "movie group (movie A, movie B, movie C)" that includes a predetermined number of movies that have been registered in advance, with a "screening period of May 1st to July 31st, 2021."

[0048] Next, the process proceeds to ST22. In ST22, the "corporate ticket information generation unit (program) 31" shown in Fig. 5 of the management server 10 in Fig. 1 operates to generate the "management server side corporate movie ticket information" shown in Fig. 5 for Company X in the "management server side corporate movie ticket information storage unit 31," and enters the 100,000 "ticket identification numbers," "movie group," and "PIN numbers" for "Company X." At this time, the "user name," "telephone number," "address," etc., of the person who will actually use the "corporate movie ticket (card)" are not entered because they are uncertain.

[0049] In addition, a "two-dimensional code" is generated from the information on the "movie ticket identification number" and "PIN number," and the related information is stored in the "management server side corporate movie ticket information storage unit 32" in association with the "movie ticket identification number."

[0050] Next, the process proceeds to ST23. In ST23, a two-dimensional code is generated based on the "Corporate movie ticket information on the management server side" of Company X in Figure 5, and 100,000 "movie tickets (cards)" with this code displayed, as shown in Figure 10, are produced and sent to Company X. Then, the management server 10 executes a process to validate the sent "movie ticket (card)." The "validation process" executed by the management server 10 is an example of destination ticket validation information.

[0051] Next, the process proceeds to ST24. In ST24, Company X inputs the necessary information for each of the 100,000 "movie tickets (cards)" it has received into the "company server-side corporate movie ticket information storage unit 61" in FIG. Specifically, for example, when reserving a seat, the user's "name," "telephone number," "address," etc. are entered in association with each "ticket identification number" in the "Corporate movie ticket information on the company server side" in Figure 7.

[0052] In this way, in this embodiment, information such as the "name" of the "user" who actually uses each "movie ticket (card)" is not transmitted to the management server 10, so that the personal information of the user can be securely protected and Company X can manage it more safely.

[0053] In the present invention, the server 50 of company X may be configured to transmit personal information such as the user's name to the management server 10.

[0054] Next, the process proceeds to ST25. In ST25, Company X hands over a "movie ticket (card)" to each actual user (for example, a customer).

[0055] After that, if each user has not made a reservation, they bring their "movie ticket (card)" to the theater, enter, and watch the movie.The process is the same as ST11 to ST17 in Figure 9 of the first embodiment, so the explanation will be omitted. If you have made a reservation in advance, you will need to mark the item as used at the time of reservation.

[0056] Furthermore, in the above-described embodiment, in ST23, the management server 10 is configured to validate all "movie tickets" sent to Company X, but the present invention is not limited to this, and the management server 10 may be configured to send all movie tickets to Company X without performing the validation process. In this case, the user's "name," "telephone number," "address," etc. are entered in association with each "ticket identification number" in the "corporate movie ticket information on the company server side" in Figure 7, and the "validation process" is performed. Next, the X company server 50 notifies the management server 10 of only the validated "ticket identification number." In this embodiment, the "validation process" executed by the X company's server 50 is an example of destination ticket validation information.

[0057] (Third embodiment) FIG. 12 is a schematic flow chart showing a third embodiment of the present invention using the above-described configuration. In this embodiment, unlike the first embodiment described above, instead of handing over a card-shaped "movie ticket" to the recipient, for example, Mr. Y, a "movie ticket (electronic ticket)" is sent to Mr. Y's user mobile terminal 120. This will be explained in detail below.

[0058] First, in ST31 of FIG. 12, Mr. Y accesses the management server 10 with his own user mobile terminal 120 and applies for a "movie ticket (electronic ticket)." Specifically, Mr. Y applies for one movie ticket (electronic ticket) for a group of films that includes several specified films during the screening period from May 1 to July 31, 2021, pays the fee, and when applying, enters and submits his name, phone number, and email address.

[0059] Next, the process proceeds to ST32. In ST32, as in ST2 described above, the "ticket information generating unit (program) 21" in Fig. 4 operates to generate Mr. Y's "movie ticket information." Specifically, the "movie ticket identification number (123456)," "movie group," Mr. Y's "name," "telephone number," "PIN code," and "email address" are associated and stored as related information in the "movie ticket information storage unit 22" in Figure 4. The generating unit 21 also generates "two-dimensional code" information that stores the "ticket identification number" and "PIN number" from among the related information, and stores the generated information in the storage unit 22.

[0060] Next, the process proceeds to ST33. In ST33, the management server 10 creates a "movie ticket (electronic ticket)" with a "two-dimensional code" that stores the "ticket identification number (123456)" and the "PIN number," and generates "movie ticket display information (movie ticket (electronic ticket))" to be displayed on the "touch panel 123" of the user's mobile terminal 120, as will be described later, and stores this in the "movie ticket display information storage unit 26" in FIG. 4.

[0061] Next, the process proceeds to ST34. In ST34, the management server 10 sends the "movie ticket display information (movie ticket (electronic ticket))" to the email address of the mobile terminal 120 of Mr. Y, the user.

[0062] Next, the process proceeds to ST35. In ST35, when the management server 10 receives a receipt confirmation email including the "movie ticket identification number" from the mobile terminal 120 of Mr. Y, the management server 10 "validates" the "movie ticket information" for the "movie ticket identification number" in FIG.

[0063] In this manner, in this embodiment, as in the first embodiment, even if the "movie ticket (electronic ticket)" is mis-delivered before being sent to Mr. Y's user mobile terminal 120, as long as it has not yet been validated, it is simply an electronic ticket or the like and not a security, making it easier to handle and reducing ticket management costs.

[0064] Thereafter, Mr. Y takes his user mobile terminal 120 to the theater, displays the "two-dimensional code" on the touch panel 123 of his user mobile terminal 120, has the "two-dimensional code reader 111" at the theater read the "two-dimensional code," and then enters the theater. This step is similar to ST12 to ST17 in FIG. 9 of the first embodiment, and therefore a description thereof will be omitted.

[0065] (Fourth embodiment) FIG. 13 is a schematic flow chart showing a fourth embodiment of the present invention using the above-described configuration. In this embodiment, unlike the second embodiment described above, instead of handing over a card-shaped "movie ticket" to the recipient, for example, Company X, a "movie ticket (electronic ticket)" is sent to Company X's server 50. This will be explained in detail below.

[0066] First, in ST41, a person in charge at Company X accesses the management server 10 via the person in charge's mobile terminal 130 and places an order for 100,000 "movie tickets (electronic tickets)" for a "movie group" including a specified number of movies, with a "screening period from May 1 to July 31, 2021."

[0067] Next, the process proceeds to ST42. In ST42, similar to ST22 described above, the "corporate ticket information generation unit (program) 31" shown in Fig. 5 operates to generate the "management server-side corporate movie ticket information" for Company X shown in Fig. 5 in the "management server-side corporate movie ticket information storage unit 31," and enters 100,000 "ticket identification numbers," "movie groups," and "PIN numbers" for "Company X."

[0068] In addition, a "two-dimensional code" is generated from information such as the "movie ticket identification number" and "PIN number," and the related information is stored in the "management server side corporate movie ticket information storage unit 32" in association with the "movie ticket identification number."

[0069] Next, the process proceeds to ST43. In ST43, 100,000 pieces of "movie ticket display information (movie tickets (electronic tickets)") displaying "two-dimensional codes" are generated based on the "corporate movie ticket information on the management server side" of Company X in FIG. 5, and these are stored in the "movie ticket display information storage unit 26" in FIG. 4.

[0070] Next, the process proceeds to ST44. In ST44, the management server 10 transmits the "movie ticket display information" to the X company's server 50. Then, the management server 10 executes a process to validate the sent "movie ticket (card)."

[0071] Next, the process proceeds to ST45. In ST45, Company X associates and inputs the user's "Name," "Telephone Number," and "Email Address" of the "Company Server-Side Corporate Movie Ticket Information" in the "Company Server-Side Corporate Movie Ticket Information Storage Unit 61" in Fig. 7 for each of the received "Movie Ticket Display Information (Movie Ticket (Electronic Ticket))."

[0072] As described above, in this embodiment, unlike the third embodiment, the "activation" of the "movie ticket (electronic ticket)" is not performed by the management server 10 but by the X company's server 50.

[0073] In this way, in this embodiment, information such as the "name" of the "user" who actually uses each "movie ticket (electronic ticket)" is not transmitted to the management server 10, so that the personal information of the user can be securely protected and Company X can manage it more safely.

[0074] In the present invention, the server 50 of company X may be configured to transmit personal information such as the user's name to the management server 10.

[0075] Next, the process proceeds to ST46. In ST46, Company X sends "movie tickets (electronic tickets)" to each actual user (for example, customer, etc.).

[0076] The user (customer) then brings their mobile terminal to the theater, displays the "2D code" on the touch panel of their mobile terminal, has the "2D code reader 111" at the theater read the "2D code," and then enters the theater. This step is similar to ST12 to ST17 in FIG. 9 of the first embodiment, and therefore a description thereof will be omitted.

[0077] Furthermore, in this embodiment of the present invention, the ST44 management server 10 is configured to validate all "movie tickets (electronic tickets)" sent to Company X, but the present invention is not limited to this, and the management server 10 may be configured to send all movie tickets to Company X without performing the validation process. In this case, the user's "name," "telephone number," "address," etc. are entered in association with each "ticket identification number" in the "corporate movie ticket information on the company server side" in Figure 7, and the "validation process" is performed. Next, the X company server 50 notifies the management server 10 of only the validated "ticket identification number."

[0078] In the present embodiment described above, an example has been given in which the invention is realized as an apparatus, but the invention is not limited to this, and the invention may be distributed as a program that can be executed by a computer, stored on a storage medium such as a magnetic disk, an optical disk (CD-ROM, DVD, etc.), a magneto-optical disk (MO), or a semiconductor memory.

[0079] The storage medium may be any medium that can store the program and is computer-readable, and the storage format of the storage medium is not particularly limited.

[0080] In addition, an OS (operating system), database management software, network software, or other MW (middleware) running on a computer may execute some of the processes required to realize this embodiment based on instructions from a program installed on the computer from a storage medium.

[0081] Furthermore, the storage medium in the present invention is not limited to a medium independent of a computer, but also includes a storage medium that stores or temporarily stores a program downloaded via a LAN, the Internet, or the like.

[0082] Furthermore, the computer in the present invention only needs to execute each process in this embodiment based on a program stored in a storage medium, and may be a device consisting of a single personal computer or the like, or a system in which multiple devices are connected to a network.

[0083] Furthermore, the term "computer" in this invention is not limited to a personal computer, but also includes an arithmetic processing unit, a microcomputer, etc. included in information processing equipment, and is a general term for equipment or devices that can realize the functions of this invention by a program.

[0084] The above describes the embodiments of the present invention. However, the present invention is not limited to the above embodiments, and various modifications can be made without departing from the scope of the claims. The configurations of the above embodiments can be partially omitted or arbitrarily combined in a different manner from the above. [Explanation of symbols]

[0085] 10...Movie ticket information management system, 2...Internet network, 3a, 3b, 3c...Base station, 10...Management server, 11...Management control unit, 12...Management communication device, 13...Management display, 14...Management various information input device, 20...Management first various information storage unit, 21...Two-dimensional code information generation unit (program), 22...Movie ticket information storage unit, 23...Validation processing unit (program), 24...Information confirmation processing unit (program), 25...Invalidation processing unit (program), 26...Movie ticket display information storage unit, 30...Management second various information storage unit, 31...Corporate two-dimensional code Code information generation unit (program), 32... Management server side corporate movie ticket information storage unit, 50... X company server, 51... X company side control unit, 52... X company side communication device, 53... X company side display, 60... X company side various information storage unit, 61... Company server side corporate movie ticket information storage unit, 100... Delivery company server, 110... Theater server, 111... Two-dimensional code reader, 112... Gate device, 120... User's mobile terminal, 121... Terminal side control unit, 122... Terminal side communication device, 123... Touch panel, 124... Terminal side various information storage unit, 130... Person in charge mobile terminal, 140... Delivery person's mobile terminal

Claims

1. a ticket information management device that manages tickets; a delivery company server of a delivery company that delivers the ticket; a mobile terminal of a user to whom the ticket is to be provided; a mobile terminal of a delivery person of the delivery company; and a ticket information management system having the mobile terminal, a ticket information storage unit that stores at least ticket identification information and ticket content information; a ticket unique information storage unit that stores at least ticket unique information having the ticket identification information; The ticket content information includes ticket validation information, The ticket unique information is provided to the delivery company server in a state where the ticket validation information of the corresponding ticket identification information has not yet been validated, the delivery company server associates delivery identification information with the ticket unique information and transmits the ticket unique information and the delivery identification information to the ticket information management device; The delivery person's mobile terminal transmits the delivery identification information, the ticket unique information, and receipt information indicating that the ticket has been delivered to the delivery destination to the delivery company server; The delivery company server transmits receipt confirmation information together with the delivery identification information to the ticket information management device, When the ticket information management device receives the received information, it performs a process of validating the ticket validation information of the ticket identification information associated with the delivery identification information without waiting for an validation request from the mobile terminal of the user who is the recipient of the ticket, A ticket information management system characterized in that the user's mobile terminal can invalidate the ticket validation information of the ticket identification information by accessing the ticket information management device after the validation process.

2. 2. The ticket information management device according to claim 1, wherein the ticket unique information is displayed or stored in a storage medium and provided to the recipient.

3. a ticket information management device that manages tickets; a delivery company server of a delivery company that delivers the ticket; a mobile terminal of a user to whom the ticket is to be provided; and a mobile terminal of a delivery person of the delivery company. a ticket information storage unit that stores at least ticket identification information and ticket content information; a ticket unique information storage unit that stores at least ticket unique information having the ticket identification information; The ticket content information includes ticket validation information, The ticket unique information is provided to the delivery company server in a state where the ticket validation information of the corresponding ticket identification information has not yet been validated, the delivery company server associates delivery identification information with the ticket unique information and transmits the ticket unique information and the delivery identification information to the ticket information management device; The delivery person's mobile terminal transmits the delivery identification information, the ticket unique information, and receipt information indicating that the ticket has been delivered to the delivery destination to the delivery company server; The delivery company server transmits receipt confirmation information together with the delivery identification information to the ticket information management device, When the ticket information management device receives the received information, it performs a process of validating the ticket validation information of the ticket identification information associated with the delivery identification information without waiting for an validation request from the mobile terminal of the user who is the recipient of the ticket, A control method for a ticket information management system, characterized in that the user's mobile terminal can invalidate the ticket validation information of the ticket identification information by accessing the ticket information management device after the validation process.

4. The system includes a ticket information management device that manages tickets, a delivery company server of a delivery company that delivers the tickets, a mobile terminal of a user to whom the tickets are to be provided, and a mobile terminal of a delivery person of the delivery company, A ticket information management system having a ticket information storage unit that stores at least ticket identification information and ticket content information, and a ticket unique information storage unit that stores at least ticket unique information having the ticket identification information, The ticket content information includes ticket validation information, and the ticket unique information is provided to the delivery company server in a state where the ticket validation information of the corresponding ticket identification information has not yet been validated. a function of the delivery company server associating delivery identification information with the ticket unique information and transmitting the ticket unique information and the delivery identification information to the ticket information management device; a function of the delivery person's mobile terminal transmitting the delivery identification information, the ticket unique information, and receipt information indicating that the ticket has been delivered to the delivery destination to the delivery company server; a function of the delivery company server transmitting receipt confirmation information together with the delivery identification information to the ticket information management device; a function of the ticket information management device, upon receiving the received information, validating the ticket validation information of the ticket identification information associated with the delivery identification information without waiting for an validation request from the mobile terminal of the user who is the recipient; A control program for a ticket information management system that enables the user's mobile terminal to access the ticket information management device after the activation process to invalidate the ticket activation information in the ticket identification information.

Images