Ticket management system, ticket management method and program
The ticket management system allows event participation verification through screen-based methods, addressing the need for ID cards by confirming eligibility and offering rewards, thus enhancing participation.
Patent Information
- Application Number
- JP2024109252
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-07-05
- Publication Date
- 2024-11-20
- Estimated Expiration
- 2044-07-05
AI Technical Summary
Event participants often face difficulties in participating due to the need to carry identification cards, as they may not be able to confirm participation conditions without them.
A ticket management system that uses a terminal with a screen to display a use intention confirmation area, allowing users to confirm their eligibility through various methods, such as QR codes or biometric authentication, without needing physical ID cards.
Enables event participation verification even if the user does not have an identification card, ensuring accurate confirmation of eligibility and promoting event participation through rewards.
Smart Images

Figure 0007587327000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a ticket management system, a ticket management method, and a program. [Background technology]
[0002] 2. Description of the Related Art Conventionally, a system for managing information on tickets for an event or the like using terminals connected to a network is known (for example, Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2024-056061 A Summary of the Invention [Problem to be solved by the invention]
[0004] In recent years, various types of events have been held, and some events have conditions for participation. For example, if the condition for participation in an event is that you must be over a certain age, you may be required to present identification along with your ticket when entering the event.
[0005] In such cases, there is a problem in that event participants must carry their ID with them, and if for some reason they do not have their ID with them, they cannot participate in the event because it cannot be confirmed that they meet the conditions for participation.
[0006] The present disclosure provides a ticket management system, a ticket management method, and a program that can prove that a person is eligible to participate in an event even if he or she does not carry an ID card. [Means for solving the problem]
[0007] In order to solve the above problems, one aspect of the present disclosure is a ticket management system that uses a terminal with a screen, which displays on the screen a usage intention confirmation area for confirming the intention of the holder of an event ticket to use the ticket, displays on the screen user information of holders whose intention to use has been confirmed, and performs event participation processing for the user information of persons who are determined to be eligible to participate in the event based on the user information. [Brief description of the drawings]
[0008] [Figure 1] FIG. 1 is a block diagram of a ticket management system. [Diagram 2] FIG. 2 is a block diagram of a user terminal. [Diagram 3] FIG. 2 is a block diagram of an operator terminal. [Figure 4] FIG. 2 is a block diagram of a ticket management device. [Diagram 5] 4 is a functional block diagram showing functions of a control unit of a user terminal. FIG. [Figure 6] 4 is a functional block diagram showing functions of a control unit of the operator terminal. FIG. [Figure 7] 4 is a functional block diagram showing functions of a control unit of the ticket management device. FIG. [Figure 8] FIG. 11 is a screen diagram showing an example of a screen displayed on a screen of a user terminal. [Figure 9] FIG. 2 is a flow chart for explaining a series of operations of the ticket management system. [Figure 10] FIG. 2 is a flow chart for explaining a series of operations of the ticket management system. [Figure 11] FIG. 2 is a flow chart for explaining a series of operations of the ticket management system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] Hereinafter, an embodiment of the present disclosure will be described. The ticket management system and its components according to the embodiment are merely illustrative, and each configuration can be appropriately changed without departing from the spirit of the present disclosure. In particular, in the following embodiment, detailed explanations will be given by clearly indicating the hardware and functional blocks for realizing the terminals constituting the ticket management system. However, it is clear that which hardware realizes what function can be appropriately changed according to the spirit of the present disclosure. It is also clear that each functional block can be realized by the same hardware or software, or different hardware or software. In the following explanation, it is assumed that an application (program) installed on the terminal controls each piece of hardware.
[0010] The ticket management system according to the embodiment can be applied to cases where a series of processes are performed using only the terminal owned by the ticket holder (user) (excluding some data management), and cases where a series of processes are performed using the user's terminal and a terminal owned by the event organizer. In either case, identity can be confirmed at the time of entry to the event even if the user does not actually have identification. In the embodiment, a detailed explanation will be given assuming that the user can first select which pattern they can use to prove their identity. However, rather than a user selection system, the organizer may be able to make the selection, or only one pattern may be used. (Ticket Management System)
[0011] 1 is a block diagram of a ticket management system 100. The ticket management system 100 includes at least two terminals 300 and 400 connected to each other via a network 200, and a ticket management device 500 connected to the network 200.
[0012] The terminal 300 is a terminal owned by a user. Therefore, hereinafter, the terminal 300 may be referred to as a user terminal 300. The terminal 400 is a terminal owned and managed by an event organizer. Therefore, hereinafter, the terminal 400 may be referred to as an organizer terminal 400. (User terminal)
[0013] 2, the user terminal 300 is a portable terminal such as a smartphone, a wearable terminal, etc. The user terminal 300 includes a control unit 302, a screen 304, and a storage unit 306.
[0014] The control unit 302 is the core part of the user terminal 300, and controls each main operation of the user terminal 300, writes / reads data to / from the memory unit 306, displays various information on the screen 304, and processes various information input to the screen 304. A screen 304 is, for example, a smartphone screen, which displays various information to the user and accepts various information input from the user. The storage unit 306 is a memory area that is used when the control unit 302 performs various information processes. (Operator terminal)
[0015] 3, the administrator terminal 400 is a small terminal such as a personal computer or a smartphone managed by the administrator. The administrator terminal 400 does not necessarily have to be portable. The administrator terminal 400 only needs to be able to be installed, for example, at the entrance of an event venue. The administrator terminal 400 includes a control unit 402, a screen 404, an input IF 406, and a storage unit 408.
[0016] The control unit 402 is the core part of the operator terminal 400, and controls each main operation of the operator terminal 400, writes / reads data to the memory unit 408, displays various information on the screen 404, and processes various information input to the input IF 406. The storage unit 408 is a memory area used when the control unit 402 performs various information processes.
[0017] When the operator terminal 400 is a smartphone, the screen 404 and the input IF may be the same. When the operator terminal 400 is a personal computer, the screen 404 and the input IF may be different, for example, the screen 404 is a display or the like, and the input IF is a keyboard, a mouse, etc. The input IF may have a voice input / output unit such as a microphone, or a camera. (Ticket Management Device)
[0018] 4, the ticket management device 500 is a server, etc. The ticket management device 500 includes a control unit 502 and a storage unit 504. The control unit 502 is the core part of the ticket management device 500 and controls each main operation of the ticket management device 500 and processes various information such as writing / reading data to / from the storage unit 504 . The storage unit 504 stores user information. The user information may include at least information corresponding to the participation qualification set for each event. For example, if the administrator sets the participation condition for the event as 20 years of age or older, the user information may include at least age. As an example, the user information may include various information such as name, address, date of birth, age, sex, and nationality. The user information is information that the administrator has approved in advance and stored in the storage unit 504. When registering user information, the administrator requests the user to submit necessary information and a document that certifies that the information is correct. Examples of documents that certify that the user information is correct include documents issued by public institutions such as a driver's license, passport, My Number card, residence card, special permanent resident certificate, and physical disability certificate, and membership cards issued by the administrator. The type of the certificate face is appropriately determined according to the participation conditions for the event. When registering user information, the administrator requests the user to submit these documents (for example, by electronic means using image data or scanned data). The administrator visually checks whether the submitted documents match the information declared by the user, and if the user information matches the certificate face, the user information is stored in the storage unit 504. At this time, a flag indicating that the user information has been confirmed may be attached to the user information. In addition, the user information may be stored in association with other information, such as information about events the user has previously participated in. (function)
[0019] As shown in FIG. 5, the control unit 302 of the user terminal 300 includes, as functions, a code display unit 302a, an event information display unit 302b, a participation qualification display unit 302c, a use intention confirmation unit 302d, and a user information confirmation unit 302e.
[0020] The code display unit 302a displays a code on the screen. The code may be, for example, a one-dimensional code, a two-dimensional code, a three-dimensional code, or the like. The code is information unique to the user and serves as a ticket for the event. The code is created and distributed by the organizer to users who purchase tickets. In this embodiment, the code display unit displays a QR code, which is a two-dimensional code, on the screen. The code display unit 302a is displayed on the screen 304 as a code display area 310.
[0021] The event information display section 302b displays detailed information about the event, such as the name of the event, the name of the event venue, the address of the event venue, the duration of the event, etc. The event information display section 302b is displayed on the screen 304 as an event information display area 312.
[0022] The participation qualification display section 302c displays information regarding the participation qualifications determined by the organizer. For example, when the organizer imposes an age limit on the conditions for participation in the event, the participation qualification information displays the age that can participate (e.g., age 20 or older). Other information regarding participation qualifications includes gender, nationality, address, dress code, qualifications determined by the organizer, etc. The participation qualification display section 302c is displayed on the screen 304 as a participation qualification area 314.
[0023] The usage intention confirmation unit 302d accepts a predetermined screen operation and confirms the user's usage intention. Specifically, the predetermined screen operation may be, for example, a user operation, a user pattern authentication, a user PIN authentication, or a user biometric authentication. When the user's usage intention is confirmed, the confirmation may be associated with user information and stored in the storage unit 504. The usage intention confirmation unit 302d is displayed on the screen 304 as a usage intention confirmation area 316.
[0024] The user information confirmation unit 302e executes a process of acquiring user information by being operated. When a user information confirmation area 318 described later is operated, the user information confirmation unit 302e accesses the storage unit 504 to read out the user information of the owner of the user terminal, and displays the read out user information on the screen 304. The user information displayed on the screen 304 may be information recorded in the above-mentioned storage unit 504, and may further be a document (document issued by a public institution such as a driver's license, passport, My Number card, residence card, special permanent resident certificate, or physical disability certificate) that certifies that the user information is correct, and a membership card issued by an operator or the like. The user information confirmation unit 302e is displayed on the screen 304 as the user information confirmation area 318.
[0025] As shown in FIG. 6, the control unit 402 of the administrator terminal 400 includes, as functions, a usage intention confirmation unit 402a, a user information display unit 402b, and a participation processing unit 402c. The usage intention confirmation unit 402a reads the code (QR code) displayed on the user terminal 300 using the input IF (camera) of the administrator terminal 400.
[0026] When the use intention confirmation unit 402a reads the code (QR code), the user information display unit 402b accesses the storage unit 504 and reads out the user information linked to the code (QR code). The user information display unit 402b displays the read out user information on the screen 404 of the operator terminal 400.
[0027] Upon reading the code (QR code), the participation processing unit 402c writes it into the storage unit 504 and processes the ticket as having been used. Specifically, the participation processing unit 402c sets a flag indicating that the ticket has been used. Furthermore, the participation processing unit 402c displays a used indication on the screen indicating that the ticket has been used. The used indication may be text, symbols, images, videos, or a combination of these. The used indication is displayed on a screen listing tickets held by the user. More specifically, it is displayed adjacent to the display of used ticket information on the ticket list screen. On the ticket list screen, multiple ticket information items are arranged in ascending and descending order, for example. As shown in FIG. 7, the control unit 502 of the ticket management device 500 includes, as a function, a reward granting unit 502a. The reward granting unit 502a grants a reward to the user. Specifically, the reward granting unit 502a writes information about the reward in the storage unit 504 by linking it to the user information. The information about the reward includes, for example, points that can be used in the event, electronic money, etc. The reward granting unit 502a adds the points or electronic money to the storage unit 504 by linking it to the user information. Other reward information includes various items that bring benefits to the user, such as information about upcoming events and commemorative gifts, and a flag is written in storage unit 504 to indicate whether or not these items are available. Regarding the timing of providing the reward, if the reward is provided by data, information regarding the reward may be linked to user information and written to the storage unit 504 at the same time that a flag indicating that the ticket has been used is written to the storage unit 504. Providing a reward as part of the event participation process is expected to encourage participation in the event. (Screenshot)
[0028] Next, a description will be given of screens used in the ticket management system according to the embodiment. Note that in the embodiment, information is displayed on a touch screen, and the user performs various inputs by touching the screen.
[0029] 8 shows an example of a screen displayed on the screen 304 of the user terminal 300. This screen 304 includes a code display area 310, an event information display area 312, a participation qualification display area 314, a use intention confirmation area 316, and a user information confirmation area 318. A code is displayed in the code display area 310. In this embodiment, a QR code is displayed as one aspect.
[0030] Detailed information about an event is displayed in the event information display area 312. The detailed information about an event includes, for example, the name of the event, the name of the event venue, the address of the event venue, and the duration of the event. In the participation qualification display area 314, information regarding the participation qualifications determined by the administrator is displayed.
[0031] The usage intention confirmation area 316 is used to confirm (confirm usage intention) whether or not the user will use the ticket (whether or not to participate in the event). An arrow pointing from the left side of the screen to the right is displayed in the usage intention confirmation area 316, and when the user slides the arrow, it is considered that the intention to use has been confirmed. Note that the usage intention confirmation area 316 may be a touch-type area (i.e., the intention to use is indicated by touching it).
[0032] The user information confirmation area 318 is an area for executing a process of acquiring user information by being operated. When the user information confirmation area 318 is operated, the user terminal 300 accesses the storage unit 504 and reads out the user information of the owner of the user terminal. The read out user information is displayed on the screen 304.
[0033] As described above, in this embodiment, both the code display area 310 and the use intention confirmation area 316 are displayed on the screen, and the user can select which one to use to express his / her intention to use. For example, if the administrator specifies that only QR codes are to be used as tickets, it is possible to display only the code display area 310 and not the use intention confirmation area 316. This is because presenting the code to the administrator can itself be considered as an indication of the intention to use. (flow)
[0034] Next, the operation of the ticket management system will be described. Fig. 9 is a flow diagram for explaining a series of operations of the ticket management system. For the sake of convenience, a series of flows will be explained including the case where the subject of the operation is a person.
[0035] A series of processes is started after the ticket holder arrives at the event venue and starts up the user terminal 300. At this time, it is assumed that the user has already purchased a ticket for the event, and that the purchased ticket information is linked to the user information and stored in the storage unit 504.
[0036] In step S1, the user presents the screen of the ticket management system to the administrator. At this stage, the user may verbally inform the administrator whether they wish to enter using a QR code or by operating the usage intention confirmation area 316. If entry using a QR code is desired, the processes from step S2 onwards are executed, and if entry by operating the usage intention confirmation area 316 is desired, the processes from step S4 onwards are executed.
[0037] In step S2, the administrator reads the QR code using the administrator terminal 400 (use intention confirmation step). When the QR code is read, the administrator terminal 400 accesses the storage unit 504 and reads out the user information linked to the QR code. The read out user information is displayed on the screen 404 of the administrator terminal 400 (user information display step). Note that at the stage when the QR code is read, the administrator terminal 400 may write into the storage unit 504 and set a flag indicating that the ticket has been used (event participation process).
[0038] In step S3, the administrator visually checks the user information and verifies that the user meets the participation qualifications. This allows the user to enter the event venue. Note that a flag indicating that the ticket has been used may be set at the time step S3 is completed.
[0039] If entry is desired by operating the use intention confirmation area 316, in step S4 the user slides the arrow in the use intention confirmation area 316. This indicates that the user has expressed an intention to use the ticket (use intention confirmation step). At this stage, the user terminal 300 may write to the storage unit 504 and set a flag indicating that the ticket has been used.
[0040] Next, in step S5, the user operates the user information confirmation area 318. This causes the user terminal 300 to access the memory unit 504 and read out the user information of the owner of the user terminal. The read out user information is displayed on the screen 304 (user information display step). The user presents the screen displaying the user information to the administrator. The administrator visually checks the user information and confirms that the user meets the participation qualifications. This allows the user to enter the event venue. Note that a flag indicating that the ticket has been used may be set when step S5 is completed. As described above, the ticket management system 100 can verify a user's eligibility to participate with high accuracy even if the user does not have an ID card.
[0041] In the above example, the event participation process is to mark the ticket as used. However, the event participation process may simultaneously mark the ticket as used and give a reward to the user. The reward may be points or electronic money that can be used at the event. In addition to money, the reward may be various things that bring benefits to the user, such as event information for the next event and a souvenir. If the reward is provided by data, the information on the reward may be written to the storage unit 504 in association with user information at the same time that a flag marking the ticket as used is written to the storage unit 504. By giving a reward as the event participation process, it is expected that participation in the event will be promoted.
[0042] (Variation 1) In the above embodiment, the control unit 302 of the user terminal 300 has the functions of the code display unit 302a, the event information display unit 302b, the participation qualification display unit 302c, the use intention confirmation unit 302d, and the user information confirmation unit 302e, but the control unit 302 of the user terminal 300 may further have an entry method selection receiving unit 302f (not shown). The entry method selection receiving unit 402d receives the selection of the entry method from the user. As the entry method, for example, either the code display area 310 or the use intention confirmation area 316, the entry method selected by the user, is displayed on the screen. The user can express his / her intention to use by using the selected entry method. When the use intention confirmation area is selected, and the use intention confirmation area receives a predetermined action (slide, tap, PIN, biometric authentication, etc.) by the user, the control unit displays user information (driver's license, etc.) and event information (ticket, etc.) on the screen. On the other hand, when the use of the code display area is selected, and the code display area (for example, a QR code, etc.) is read by the administrator terminal, the control unit displays user information (driver's license, etc.) and event information (ticket, etc.) on the screen. (Variation 2) Also, as shown in FIG. 10, in another embodiment, the control unit 302 may display user information (such as a driver's license) on the screen 304 (S11), and then accept either the code display area 310 or the usage intention confirmation area 316 on the screen (S12). (Variation 3) Also, as shown in FIG. 11, in another embodiment, the control unit 302 may display user information (such as a driver's license) on the screen 304 (S21), and then further display the user information (S22). After the user's eligibility to participate has been approved (S23), the screen may accept either the code display area 310 or the intention to use confirmation area 316 (S24). (Variation 4) In another embodiment, the control unit 302 may display the use intention confirmation area 316 and the user information (driver license, etc.) on the same screen 304. (Variation 5) The intention-to-use confirmation unit 302d accepts a predetermined screen operation to confirm the user's intention to use, and when the predetermined operation is completed, the intention-to-use confirmation area accepts a predetermined screen operation. Examples of the predetermined operation include checking a check box or displaying a predetermined document. (Variation 6) In the above embodiment, the user terminal 300 is equipped with a control unit 302, the operator terminal 400 is equipped with a control unit 402, and the ticket management device 500 is equipped with a control unit 502, but in the present invention, the functions or some of the functions of the control unit of the user terminal 300, the control unit 402 of the operator terminal 400, and the control unit 502 of the ticket management device 500 may be realized by other control units 302, control units 402, or control units 502. Furthermore, the control unit 302, the control unit 402, and / or the control unit 502 may be realized by other devices. In this case, the user terminal 300 or the operator terminal 400 may display information processed by the other devices on the screens 304 and 404. Furthermore, it is not essential for the ticket management system to have multiple functions integrated into one housing, and for example, the components of the ticket management system may be distributed across multiple housings. Also, some of the functions of the production management system may be realized by the cloud (cloud computing) or the like. [Explanation of symbols]
[0043] 100: Ticket Management System 300: User terminal 310: Code display area 316: Usage intention confirmation area 400: Operator terminal 500: Ticket management device
Claims
1. A ticket management system using a display terminal, displaying on said screen a usage intention confirmation area for confirming the intention of the holder of the event ticket to use said ticket; displaying on the screen the user information of the holder whose intention to use has been confirmed; performing an event participation process on the user information of the person who is determined to be eligible to participate in the event based on the user information; the screen terminal is the owner's terminal, the use intention confirmation area is displayed as an area for accepting a predetermined screen operation, The user information is information related to a pre-registered official identification card. Ticket management system.
2. The event participation process includes providing a reward to a user who owns the user information. The ticket management system according to claim 1 .
3. The eligibility to participate in the event includes a condition regarding whether or not a person has reached a certain age; The ticket management system according to claim 1 .
4. A ticket management system using a display terminal, displaying on said screen a usage intention confirmation area for confirming the intention of the holder of the event ticket to use said ticket; displaying on the screen the user information of the holder whose intention to use has been confirmed; performing an event participation process on the user information of the person who is determined to be eligible to participate in the event based on the user information; At least two of the screen terminals are provided; The usage intention confirmation area and the user information are displayed on different terminals, The at least two terminals include a terminal of the holder and a terminal of a manager of the event; The use intention confirmation area is displayed on the terminal of the owner, The user information is displayed on a terminal of a manager of the event; A code display area is displayed on the screen, A storage unit that manages the code and information related to an official identification card linked to the code, When the code is read by a terminal of the event organizer, information on the official identification card corresponding to the read code is displayed on the terminal of the event organizer. Ticket management system.
5. The code is a QR code. The ticket management system according to claim 4.
6. The method of use selection receiving unit further receives from a user whether to use the code display area or the intention-to-use confirmation area. The ticket management system according to claim 4.
7. The screen of the terminal of the holder displays at least The code display area; an event information display area in which detailed information of the event is displayed; a participation qualification display area in which information regarding the participation qualifications determined by the organizer of the event is displayed; The use intention confirmation area; A user information confirmation area that executes a process for acquiring user information by being operated is displayed on the same screen. The ticket management system according to claim 4.
8. When a predetermined operation is completed by the user, the usage intention confirmation area accepts a predetermined screen operation. The ticket management system according to claim 4.
9. A ticket management method performed by a control unit, comprising: A usage intention confirmation step for confirming the intention of the holder of the event ticket to use the ticket; a user information display step of displaying user information of the holder whose intention to use has been confirmed; a participation processing step of performing an event participation process on user information of a person who is determined to be eligible to participate in the event based on the user information, The step of confirming intention to use is for accepting a predetermined screen operation, The user information is information related to a pre-registered official identification card. Ticket management methods.
10. A program comprising: A method for managing a ticket by a processor, comprising: program.
Citation Information
Patent Citations
Mutual confirmation system
JP2000105844A
Ticket processing method and program
JP2014149556A
Program, information processing device, and information processing system
JP2018032378A
Digital ticket system
JP2018205815A
Personal information management system, and service providing system, method and program
JP2019219780A
Cited By
Information processing system, information processing method, and server
JP2026150109A
Information processing system, information processing method and server
JP7756982B1
