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

Abstract

To provide a ticket management system, a ticket management method, and a ticket management program for easily managing a common ticket which is available in a plurality of facilities.SOLUTION: An issuance processing unit 112 issues, to a user, a common ticket for a service available in common in a plurality of facilities. In the case where the common ticket is available on a user terminal 2 of the user, an acquisition processing unit 114 acquires a facility ID of a facility An when the user terminal 2 reads a two-dimensional code Cn in the facility An that can provide the service, out of the facilities. A management processing unit 116 manages history information indicating that the common ticket has been used in the facility An.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a ticket management system, a ticket management method, and a ticket management program for managing tickets that can be used at multiple facilities. [Background technology]

[0002] Conventionally, a system has been known in which a user terminal acquires a ticket (electronic ticket) that can be used at a facility (see, for example, Patent Document 1). With this system, a user can acquire and issue a ticket at a desired location and use the issued ticket at the desired facility. [Prior art documents] [Patent documents]

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

[0004] Incidentally, a common ticket that can be used at multiple facilities is known as an example of a ticket that can be used at a facility. For example, when a traveler (user) stays at a lodging facility in a specified area, the ticket administrator distributes to the traveler a common ticket that can be used for a free luggage delivery service. The common ticket is a ticket that can be used at any of multiple facilities (lodging facilities, shops, etc.) registered in the area, and the traveler can use the luggage delivery service at any of the multiple facilities.

[0005] In the case of distributing common tickets that can be used at multiple facilities, it is difficult to manage the usage status of the common tickets, such as how much the distributed common tickets have been used or at which facilities the common tickets have been used.

[0006] An object of the present invention is to provide a ticket management system, a ticket management method, and a ticket management program that can easily manage common tickets that can be used in common at multiple facilities. [Means for solving the problem]

[0007] The ticket management system according to the present invention comprises an issuance processing unit, an acquisition processing unit, and a management processing unit. The issuance processing unit issues a common ticket to a user for a service that can be used at multiple facilities. When the common ticket can be used on the user's user terminal, the acquisition processing unit acquires identification information of the specific facility when the user terminal reads a readable medium located at a specific facility among the multiple facilities that can provide the service. The management processing unit manages history information indicating that the common ticket has been used at the specific facility.

[0008] The ticket management method of the present invention is a ticket management method executed by one or more processors, which includes issuing a common ticket to a user for a service that can be used at multiple facilities, and when the common ticket can be used on the user's user terminal, obtaining identification information for the specific facility when the user terminal reads a reading medium located at a specific facility among the multiple facilities that can provide the service, and managing historical information indicating that the common ticket has been used at the specific facility.

[0009] The ticket management program of the present invention is a ticket management program that causes one or more processors to execute the following operations: issuing a common ticket to a user for a service that can be used in common at multiple facilities; when the common ticket can be used on the user's user terminal, when the user terminal reads a reading medium located at a specific facility among the multiple facilities that can provide the service, obtaining identification information of the specific facility; and managing historical information indicating that the common ticket has been used at the specific facility. [Effects of the Invention]

[0010] According to the present invention, a ticket management system, a ticket management method, and a ticket management program are provided that can easily manage common tickets that can be used in common at multiple facilities. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a schematic diagram showing the overall configuration of a ticket management system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram showing an example of how a common ticket is used in the ticket management system according to the embodiment of the present invention. [Figure 3] FIG. 3 is a block diagram showing the configuration of a ticket management system according to an embodiment of the present invention. [Figure 4] FIG. 4 is a diagram showing an example of ticket information used in the ticket management system according to the embodiment of the present invention. [Figure 5] FIG. 5 is a diagram showing an example of usage history information used in the ticket management system according to the embodiment of the present invention. [Figure 6] FIG. 6 is a diagram showing an example of user information used in the ticket management system according to the embodiment of the present invention. [Figure 7] FIG. 7 is a diagram showing an example of the aggregate information used in the ticket management system according to the embodiment of the present invention. [Figure 8] FIG. 8 is a diagram showing an example of a ticket selection page displayed on the user terminal according to the embodiment of the present invention. [Figure 9] FIG. 9 is a diagram showing an example of a photographing page displayed on the user terminal according to the embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing an example of a ticket use page displayed on a user terminal according to an embodiment of the present invention. [Figure 11] FIG. 11 is a diagram showing an example of a ticket selection page displayed on a user terminal according to an embodiment of the present invention. [Figure 12]FIG. 12 is a diagram showing an example of a usage history page displayed on the management server according to an embodiment of the present invention. [Figure 13] FIG. 13 is a diagram showing an example of a usage history page displayed on the management server according to an embodiment of the present invention. [Figure 14] FIG. 14 is a flowchart showing an example of the procedure of the service participation registration process executed in the ticket management system according to the embodiment of the present invention. [Figure 15] FIG. 15 is a flowchart showing an example of a procedure of a ticket management process executed in the ticket management system according to the embodiment of the present invention. [Figure 16] FIG. 16 is a diagram showing another example of ticket information used in the ticket management system according to the embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings to help understand the present invention. Note that the following embodiments are examples that embody the present invention and do not limit the technical scope of the present invention.

[0013] [Ticket Management System 10] 1, a ticket management system 10 according to an embodiment of the present invention includes a management server 1 and a user terminal 2. The management server 1 and the user terminal 2 can communicate with each other via a communication network N1 such as the Internet, a LAN, a WAN, or a public telephone line.

[0014] The management server 1 manages tickets for users to use a specific service, for example, a common ticket that can be used at multiple facilities. Specifically, the management server 1 issues a common ticket to a user terminal 2 so that the user can use the service at the facility. When the common ticket can be used on the user terminal 2, the user uses the common ticket at a desired facility out of multiple facilities that can provide the service. When the user uses the common ticket at the desired facility to receive the service, the management server 1 acquires and manages history information (such as usage history) of the common ticket.

[0015] The service is, for example, a luggage delivery service for travelers. Specifically, when a traveler (user) stays at an accommodation facility in a specified area, the management server 1 issues a common ticket to the traveler's user terminal 2, which allows the traveler to use the luggage delivery service at any of multiple facilities (accommodations, stores, etc.) registered in the area. Once the traveler obtains the common ticket on the user terminal 2, the traveler can use the luggage delivery service at any of the multiple facilities. The service is not limited to a luggage delivery service, and may be, for example, a discount purchase service that allows the purchase of products at a retail store at a discount price, or a discount use service that allows the use of various facilities such as leisure facilities, cultural facilities, amusement facilities, and accommodation facilities for free or at a discount price. Furthermore, the service may be a free service or a paid service. In the following, a free luggage delivery service will be described as an example of the service.

[0016] The user terminal 2 is an operating terminal through which a user purchases train tickets, makes reservations for trains and facilities, and reserves, purchases, and obtains facility tickets (including common tickets). The ticket management system 10 includes one or more user terminals 2.

[0017] Two-dimensional codes are placed at multiple facilities. For example, two-dimensional codes are distributed to each of multiple facilities managed by the management server 1. The two-dimensional codes are placed, for example, at the counters of each facility. Read information including facility identification information (facility ID) and two-dimensional code identification information (code ID) is embedded in the two-dimensional code. FIG. 1 shows 30 facilities A1 to A30, and two-dimensional codes C1 to C30 with different read information are placed at each facility. Specifically, facility A1 has a two-dimensional code C1 for facility A1 placed therein, facility A2 has a two-dimensional code C2 for facility A2 placed therein, facility A3 has a two-dimensional code C3 for facility A3 placed therein, and facility A30 has a two-dimensional code C30 for facility A30 placed therein.

[0018] For example, as shown in FIG. 2, each user obtains a common ticket on user terminal 2, visits a desired facility among facilities A1 to A30, and reads the facility's two-dimensional code with camera 25 of user terminal 2 (see FIGS. 3, 9, etc.). When the user terminal 2 reads the two-dimensional code and is authorized to use the parcel delivery service, the user becomes able to use the parcel delivery service at the facility. In this way, since the common ticket can be used at any of multiple facilities, each user can use the common ticket at their desired facility to use the parcel delivery service. A two-dimensional code is an example of a reading medium of the present invention. The reading medium of the present invention may also be a one-dimensional code, a marker, an IC tag, etc.

[0019] In this embodiment, the management server 1 alone corresponds to the ticket management system of the present invention, but the ticket management system of the present invention may also include one or more of the components of the management server 1 and the user terminal 2. For example, if the components of the management server 1 and the user terminal 2 cooperate to share and execute the service participation registration process (see FIG. 14) and ticket management process (see FIG. 15) described below, a system including the multiple components that execute these processes can be considered as the ticket management system of the present invention. In other words, the management server 1 and the user terminal 2 may constitute the ticket management system of the present invention.

[0020] [Management Server 1] 3, the management server 1 is a server (e.g., a cloud server) that includes a control unit 11, a storage unit 12, an operation display unit 13, and a communication unit 14. The management server 1 is not limited to a single computer, but may be a computer system in which multiple computers operate in cooperation with each other. Furthermore, various processes executed by the management server 1 may be executed in a distributed manner by one or multiple processors.

[0021] The communication unit 14 is a communication interface that connects the management server 1 to the communication network N1 via a wired or wireless connection and performs data communication in accordance with a predetermined communication protocol with external devices such as the user terminal 2 via the communication network N1.

[0022] The operation display unit 13 is a user interface that includes a display unit such as a liquid crystal display or an organic EL display that displays various information, and an operation unit such as a mouse, keyboard, or touch panel that accepts operations.

[0023] The storage unit 12 is a non-volatile storage unit such as an HDD (Hard Disk Drive), SSD (Solid State Drive), or flash memory that stores various types of information. Specifically, the storage unit 12 stores data such as ticket information D1, usage history information D2, user information D3, and tally information D4. The ticket information D1 includes information regarding whether a common ticket can be used for each facility. The usage history information D2 includes information regarding the usage history of the parcel delivery service. The user information D3 includes information (membership information) regarding users who are eligible to use the ticket service (digital ticket service) provided by the management server 1. The tally information D4 includes information obtained by tallying the usage history of the common ticket for each facility. FIG. 4 is a diagram illustrating an example of the ticket information D1, FIG. 5 is a diagram illustrating an example of the usage history information D2, FIG. 6 is a diagram illustrating an example of the user information D3, and FIG. 7 is a diagram illustrating an example of the tally information D4.

[0024] As shown in FIG. 4, ticket information D1 includes information such as a corresponding "facility ID," "facility name," "code ID," and "availability" for each facility. The facility ID is identification information for the facility, and the facility name is the name of the facility. The code ID is identification information for the two-dimensional code placed at the facility. Code ID "C001" is identification information for the two-dimensional code C1 placed at facility A1, code ID "C002" is identification information for the two-dimensional code C2 placed at facility A2, and code ID "C030" is identification information for the two-dimensional code C30 placed at facility A30.

[0025] Each of the two-dimensional codes C1 to C30 (see FIG. 1) placed at each of the facilities A1 to A30 is associated with read information including an individual facility ID and code ID. Paper media on which the two-dimensional codes C1 to C30 are printed are distributed to each of the facilities A1 to A30 and placed in advance at the counter of each facility.

[0026] The usability information is information indicating whether or not the common ticket can be used. "Usable" is registered when provision of the baggage delivery service using the common ticket to the user is permitted, and "unusable" is registered when provision of the baggage delivery service using the common ticket to the user is prohibited (cancelled). For example, the administrator of the ticket service can register the "usability" of each facility on a registration screen (not shown) displayed on the operation display unit 13 of the management server 1. The administrator may also use an administrator terminal to register the "usability."

[0027] As shown in FIG. 5, the usage history information D2 includes information such as "usage date and time," "code ID," and "facility ID." The usage date and time is the date and time when the parcel delivery service was used. For example, a user uses a common ticket for the parcel delivery service (see FIG. 8), photographs a two-dimensional code placed at a facility with the camera 25 of the user terminal 2 (see FIG. 9), and applies for use of the parcel delivery service (see FIG. 10). The usage date and time may be, for example, the date and time when the application for use of the parcel delivery service was made or the date and time when the common ticket was used. The code ID is identification information of the two-dimensional code read from the two-dimensional code, and the facility ID is identification information of the facility read from the two-dimensional code. The control unit 11 registers each piece of information in the usage history information D2 each time a two-dimensional code placed at a facility is read.

[0028] As shown in FIG. 6, the user information D3 includes information such as a corresponding "user ID," "owned tickets," and "usage information" for each user. The user ID is login information for logging in to the ticket service website. Information (membership information) about users who have applied to use the ticket service is registered in the user information D3. For example, when user M1 performs an operation to register member information (e.g., user ID) on a membership registration page (not shown) of the ticket service, the control unit 11 registers the member information of user M1 in the user information D3. A user registered in the user information D3 can obtain a ticket (e.g., a common ticket) corresponding to the ticket service and use the ticket at a facility registered in the ticket information D1. In other words, a user registered in the user information D3 is a user who is eligible to use the ticket service. In another embodiment, a user name, a password, a telephone number, etc. may be registered in the user information D3.

[0029] The owned tickets are tickets that can be used by the user, and include tickets automatically provided by the management server 1, tickets purchased by the user, etc. Figure 6 shows an example in which a common ticket that can be used for parcel delivery services at multiple facilities is registered. Tickets that can be used for other services may also be registered as the owned tickets.

[0030] The usage information is information about the usage history of the held ticket, and here includes information such as the usage status, date and time of use, and facility used for the common ticket for the luggage delivery service. For example, if the common ticket can be used only once at any facility for the luggage delivery service, when the user uses the common ticket, "used" is registered in the usage status. In another embodiment, if the common ticket can be used multiple times at any facility, the remaining number of times it can be used may be registered in the usage status. The control unit 11 registers the usage information in user information D3 each time the user reads the two-dimensional code at a facility and uses the common ticket.

[0031] 7, the aggregated information D4 includes information such as "date and time of use / number of times used" for each facility. The control unit 11 creates aggregated information D4 by aggregating the usage history for each facility based on the usage history information D2, user information D3, etc.

[0032] In another embodiment, some or all of the ticket information D1, usage history information D2, user information D3, and tally information D4 may be stored in another server (such as a data server) accessible from the management server 1 via the communication network N1. In this case, the control unit 11 of the management server 1 may acquire the information from the other server and execute various processes such as the service participation registration process (see FIG. 14) and ticket management process (see FIG. 15) described below.

[0033] The storage unit 12 also stores layout data and image data for generating various web pages, such as the ticket selection page P1 (see FIG. 8), the photo capture page P2 (see FIG. 9), the ticket use page P3 (see FIG. 10), and the usage history pages P4 and P5 (see FIGS. 11 and 12) displayed on the management server 1. In this embodiment, the control unit 11 of the management server 1 can generate the various web pages and send information about the web pages to the user terminal 2, thereby causing the user terminal 2 to display the various web pages. In another embodiment, the control unit 11 of the management server 1 can cause the control unit 21 of the user terminal 2 to display the various web pages by sending data necessary for displaying the various web pages to the user terminal 2.

[0034] The website (such as a ticket service site) may be a collection of web pages belonging to one predetermined domain, but the website may also be a collection of web pages belonging to multiple domains stored in the storage unit 12 of the same management server 1. The various pages included in the website may also be stored in a distributed manner on multiple servers.

[0035] Furthermore, the storage unit 12 stores control programs such as a service participation registration program and a ticket management program for causing the control unit 11 to execute a service participation registration process (see FIG. 14) and a ticket management process (see FIG. 15) described below. For example, the service participation registration program and the ticket management program are non-temporarily recorded on a computer-readable recording medium such as a CD or a DVD, and are read by a reading device (not shown) such as a CD drive or a DVD drive provided in the management server 1 and stored in the storage unit 12.

[0036] The control unit 11 has control devices such as a CPU, a ROM, and a RAM (or has equivalent functions stored on the cloud). The CPU is a processor that executes various types of arithmetic processing. The ROM is a non-volatile storage unit in which control programs such as an OS that cause the CPU to execute various types of arithmetic processing are stored in advance. The RAM is a volatile or non-volatile storage unit that stores various types of information and is used as temporary storage memory (work area) for the various types of processing executed by the CPU. The control unit 21 controls the management server 1 by having the CPU execute various control programs that are stored in advance in the ROM or the storage unit 12.

[0037] Specifically, as shown in Fig. 3, the control unit 11 includes various processing units such as a registration processing unit 111, an issuance processing unit 112, a reception processing unit 113, an acquisition processing unit 114, a determination processing unit 115, a management processing unit 116, and a presentation processing unit 117. The control unit 11 functions as the various processing units by executing various processes in accordance with the service participation registration program and the ticket management program using the CPU. Some or all of the processing units may be configured as electronic circuits. The service participation registration program and the ticket management program may be programs that cause multiple processors to function as the processing units.

[0038] The registration processing unit 111 associates and registers in advance the identification information (facility ID) of a facility that can provide a predetermined service (e.g., a parcel delivery service) with the identification information (code ID) of a two-dimensional code (readable medium) placed at the facility. For example, an administrator performs an operation to register the facility ID and facility name of a facility that wishes to participate in the parcel delivery service, and the registration processing unit 111 registers the facility ID, facility name, and code ID of the two-dimensional code in the ticket information D1 (see FIG. 4) in the storage unit 12 in response to the administrator's registration operation. The registration processing unit 111 assigns a unique facility ID and code ID to each facility. The registration processing unit 111 also issues a two-dimensional code for each facility, with the facility ID and code ID embedded therein. The administrator distributes paper media on which the issued two-dimensional code is displayed (printed) to the facilities. The paper media are placed at the counters or other locations at the facilities. The two-dimensional code may be electronic data. In this case, the data of the two-dimensional code is transmitted to a facility terminal of the facility, and the two-dimensional code is displayed on the display screen of the facility terminal.

[0039] The registration processing unit 111 may register only facilities that can provide the luggage delivery service in the ticket information D1, or may register all facilities (for example, all affiliated facilities in a predetermined area) in the ticket information D1 and register for each facility whether or not the luggage delivery service is available. By using the registration information in the ticket information D1, it is possible to temporarily suspend or resume the provision of the luggage delivery service for each facility in real time.

[0040] According to the above configuration, the administrator can register new facilities to participate in the luggage delivery service and can switch whether or not to permit provision of the luggage delivery service for each facility. Furthermore, each facility can switch in real time whether or not to permit provision of the luggage delivery service while leaving the paper medium displaying the two-dimensional code in place (without removing it). As another embodiment, the facility administrator of each facility may log in to the ticket service website (ticket service site) on a facility terminal and perform operations such as registering for participation in the luggage delivery service, permitting / denying (cancelling) provision of the luggage delivery service, and deleting the luggage delivery service registration.

[0041] The issuance processing unit 112 issues a common ticket to a user for a service (luggage delivery service) that can be used in common at multiple facilities. For example, the issuance processing unit 112 issues a common ticket for using the luggage delivery service to a user who stays at a facility under management, such as an accommodation facility. Specifically, the issuance processing unit 112 issues a common ticket to a user who has stayed or booked a stay at the accommodation facility, among users who have registered as members of the ticket service provided by the management server 1. The issuance processing unit 112 registers, in user information D3 (see FIG. 6), information indicating that the common ticket has been issued ("held ticket") in association with the user ID of the user to whom the common ticket has been issued. Here, "luggage delivery" is registered for the user to whom the common ticket for the luggage delivery service has been issued.

[0042] In another embodiment, when a user who has registered as a member of the ticket service purchases a common ticket for a luggage delivery service, the issuance processing unit 112 may issue the common ticket to the user. For example, the user may be able to purchase the common ticket on the online site of the ticket service.

[0043] The reception processing unit 113 accepts a ticket selection operation by a user. For example, when a user uses a luggage delivery service, the user performs an operation to select a common ticket on the user terminal 2. Specifically, as shown in FIG. 8, when the user logs in to the ticket service, the reception processing unit 113 displays a ticket selection page P1 on the user terminal 2 and accepts the ticket selection operation. Here, the ticket selection page P1 displays a selection button K1 for a common ticket for the luggage delivery service and a selection button K2 for tickets for other services, and the user M1 selects the selection button K1.

[0044] The reception processing unit 113 receives a user operation on the user terminal 2. Here, the reception processing unit 113 receives a selection operation on the user terminal 2 for a common ticket for the parcel delivery service.

[0045] The acquisition processing unit 114 acquires read information when a user reads a two-dimensional code placed at a facility using the user terminal 2. Specifically, when the reception processing unit 113 accepts a selection operation (see FIG. 8) of a common ticket for the luggage delivery service by user M1, the control unit 11 activates the camera 25 of the user terminal 2 of user M1 (see FIG. 9). User M1 photographs the two-dimensional code placed at a facility (an example of a specific facility of the present invention) that can provide luggage delivery service among multiple facilities.

[0046] Here, user M1 can check a list of facilities that can provide the luggage delivery service by, for example, clicking "Registered Facilities" in the selection button K1 on ticket selection page P1. When "Registered Facilities" is clicked, control unit 11 may display a list of facilities that can provide the luggage delivery service (facility list page) as well as a map showing the location of each facility, and may provide directions to a facility selected by the user from the list.

[0047] After user M1 decides on a facility (for example, facility A1) where he / she will use the parcel delivery service, user M1 visits facility A1 and takes a picture of two-dimensional code C1 placed at facility A1 with camera 25 of user terminal 2 (see FIG. 9).

[0048] When the user terminal 2 reads the two-dimensional code C1, the acquisition processing unit 114 acquires the read information of the two-dimensional code C1. Here, the acquisition processing unit 114 acquires the facility ID "00001" of facility A1 and the code ID "C001" of the two-dimensional code C1 from the user terminal 2 of user M1. The acquisition processing unit 114 also acquires the user ID "10001" of the logged-in user M1.

[0049] In this way, when a common ticket can be used on the user's user terminal 2, the acquisition processing unit 114 acquires the facility ID of the facility when the user terminal 2 reads a two-dimensional code placed at a facility (specific facility) among multiple facilities that can provide luggage delivery services.

[0050] The determination processing unit 115 determines whether the luggage delivery service is available. Specifically, the determination processing unit 115 determines whether the facility associated with the facility ID acquired by the acquisition processing unit 114 is permitted to provide the luggage delivery service (see FIG. 4). In the above example, since "available" is registered for facility A1 in the ticket information D1, the determination processing unit 115 determines that user M1 can use the luggage delivery service at facility A1. In contrast, since "unavailable" is registered for facility A4 in the ticket information D1, the determination processing unit 115 determines that user M1 cannot use the luggage delivery service at facility A4.

[0051] In addition, to prevent users from visiting facilities where parcel delivery services are not available, the control unit 11 may delete (hide) facilities that are registered as "unavailable" on the facility list page.

[0052] When the determination processing unit 115 determines that the luggage delivery service is available, the reception processing unit 113 displays a ticket use page P3 on the user terminal 2 and accepts an instruction operation to use the common ticket, as shown in Fig. 10. The reception processing unit 113 displays, on the ticket use page P3, the name of the facility where the luggage delivery service will be used, the date and time of use, the name of the ticket to be used, etc. When the user selects "Use" on the ticket use page P3, the reception processing unit 113 accepts the selection operation.

[0053] If the facility from which the two-dimensional code was read is a facility where the parcel delivery service is not available, the control unit 11 may cause the user terminal 2 to display a message indicating that the parcel delivery service is not available. In this case, the control unit 11 may cause the user terminal 2 to display facilities that are close to the current location of the user terminal 2 (user) and that are available for the parcel delivery service.

[0054] The management processing unit 116 manages history information indicating the use of a common ticket at a facility. Specifically, when the reception processing unit 113 accepts an instruction to use the common ticket (see FIG. 10), the management processing unit 116 registers history information of the use of the common ticket. The management processing unit 116 also registers the date and time when the parcel delivery service was used, the code ID of the two-dimensional code placed at the facility where the parcel delivery service was used, and the facility ID of the facility in the usage history information D2 (see FIG. 5). For example, when user M1 applies to use the parcel delivery service at facility A1 (see FIG. 10), the management processing unit 116 registers the time (date and time of use) when "Use" was selected on the ticket use page P3, the facility ID of facility A1, and the code ID of the two-dimensional code C1 placed at facility A1 in the usage history information D2.

[0055] The management processing unit 116 also registers usage information of the common ticket in the user information D3 (see FIG. 6). For example, the management processing unit 116 registers, in the user information of user M1, information indicating that the common ticket has been used ("Used"), the date and time the common ticket was used (Use Date and Time), and the facility at which the common ticket was used (Facility Used). The management processing unit 116 registers the time when "Use" was selected on the ticket use page P3 as the date and time of use. At least one of the information registered in the usage history information D2 and the usage information registered in the user information D3 is an example of the history information of the present invention.

[0056] When the management processing unit 116 registers the history information, the control unit 11 updates the ticket selection page P1. For example, when user M1 uses a common ticket, the control unit 11 displays the selection button K1 for the common ticket for the luggage delivery service as unselectable (grayed out) on the ticket selection page P1 of the user terminal 2 of user M1, as shown in Fig. 11. Note that if the common ticket can be used multiple times, the control unit 11 may display the remaining number of times it can be used on the selection button K1.

[0057] The control unit 11 may set an upper limit on the number of times the common ticket can be used for each user. The upper limit may be one time or multiple times. When the number of times the common ticket can be used reaches the upper limit, the control unit 11 presents information to the user terminal 2 indicating that the common ticket cannot be used. The upper limit may be set to a different number for each user. For example, the control unit 11 may set an upper limit depending on the number of nights or number of guests staying at the accommodation facility.

[0058] The presentation processing unit 117 presents aggregated information (aggregation results) obtained by aggregating the history information. For example, as shown in FIGS. 12 and 13, the presentation processing unit 117 displays usage history pages P4 and P5 on the operation display unit 13 of the management server 1. Specifically, when the administrator selects "baggage delivery" as the ticket type and specifies the aggregation period on the usage history page P4, the presentation processing unit 117 displays a list of the dates and times of use of common tickets used during the aggregation period and the names of the facilities at which the tickets were used. Furthermore, when the administrator selects "baggage delivery" as the ticket type and specifies the aggregation period on the usage history page P5, the presentation processing unit 117 displays, for each facility, the number of times the common tickets were used during the aggregation period. Note that the presentation processing unit 117 may be able to switch between the usage history pages P4 and P5 in response to a switching operation by the administrator ("aggregation by facility" or "aggregation by date and time"). The usage history pages P4 and P5 are examples of the aggregated information. Note that the presentation processing unit 117 may present the aggregated information (aggregation results) on the administrator's administrator terminal. For example, the administrator may be able to view the usage history pages P4 and P5 by logging in to the ticket service site on his / her own administrator terminal.

[0059] By checking the aggregated information, the administrator can easily grasp the usage status of the common tickets, such as how much the issued common tickets have been used, at which facilities the common tickets have been used, etc. Furthermore, since the administrator does not need to ask each facility to provide the usage status of the common tickets, the administrator can grasp the accurate usage status in real time without any effort.

[0060] [User terminal 2] 3, the user terminal 2 includes a control unit 21, a storage unit 22, an operation display unit 23, and a communication unit 24. The user terminal 2 is an information processing device such as a smartphone, a mobile phone, or a tablet terminal.

[0061] The communication unit 24 is a communication interface that connects the user terminal 2 to the communication network N1 via wired or wireless communication and performs data communication with external devices such as the management server 1 via the communication network N1 in accordance with a predetermined communication protocol.

[0062] The operation display unit 23 is a user interface that includes a display unit such as a liquid crystal display or an organic EL display that displays information such as various web pages, and an operation unit such as a mouse, keyboard, or touch panel that accepts operations.

[0063] The storage unit 22 is a non-volatile storage unit such as an HDD, SSD, or flash memory that stores various types of information. For example, the storage unit 22 stores a control program such as a browser program. Specifically, the browser program is a control program that causes the control unit 21 to execute communication processing with an external device such as the management server 1 in accordance with a communication protocol such as HTTP (Hypertext Transfer Protocol). The browser program may also be a dedicated application (ticket service application) for executing communication processing with the management server 1 in accordance with a predetermined communication protocol.

[0064] The control unit 21 has control devices such as a CPU, a ROM, and a RAM. The CPU is a processor that executes various types of arithmetic processing. The ROM is a non-volatile storage unit that pre-stores control programs such as a BIOS and an OS that cause the CPU to execute various types of processing. The RAM is a volatile or non-volatile storage unit that stores various types of information and is used as a temporary storage memory (work area) for the various types of processing executed by the CPU. The control unit 21 controls the user terminal 2 by having the CPU execute various control programs pre-stored in the ROM or the storage unit 22.

[0065] Specifically, the control unit 21 functions as a browser processing unit 211 by executing various processes in accordance with the browser program stored in the storage unit 22. The browser processing unit 211 is capable of executing browser processing to display a web page provided from the management server 1 via the communication network N1 on the operation display unit 23 and input operations for the operation display unit 23 into the management server 1. In other words, the user terminal 2 can function as an operation terminal for the management server 1 by the control unit 21 executing the browser program. Note that some or all of the processing units included in the control unit 21 may be configured with electronic circuits.

[0066] For example, when a user operates the user terminal 2 to request access to a predetermined URL corresponding to the ticket service website (ticket service site) provided by the ticket management system 10, the control unit 21 acquires web page data of the website from the management server 1 and displays the web page of the website on the operation display unit 23. Note that the access request to the predetermined URL may be made, for example, by selecting from a list of pre-registered websites, selecting from search results on an information search site, or by entering text. Furthermore, if a dedicated application (ticket service application) corresponding to the management server 1 is installed on the user terminal 2, the user of the user terminal 2 can launch the dedicated application to display the web page on the operation display unit 23.

[0067] For example, a user who wishes to use the ticket service operates the user terminal 2 to register as a member. The control unit 11 of the management server 1 acquires the user's registration information (membership information) and registers it in user information D3 (see FIG. 6). A user registered in the user information D3 can use the ticket service. For example, when using the ticket service, the user inputs login information (user ID, password, etc.) into a login page (not shown) of the website displayed on the user terminal 2. If the input login information matches the login information registered in the user information D3 (see FIG. 6), the control unit 21 causes the user terminal 2 to display a ticket selection page P1 (see FIG. 8). Furthermore, when the user selects the baggage delivery ticket selection button K1 on the ticket selection page P1, the control unit 21 causes the user terminal 2 to display a photo page P2 (see FIG. 9). Furthermore, when the user photographs a two-dimensional code with the camera 25 of the user terminal 2 (see FIG. 9), the control unit 21 causes the user terminal 2 to display a ticket use page P3 shown in FIG. 10. Furthermore, when the user uses a common ticket for the luggage delivery service, the control unit 21 updates the display contents of the ticket selection page P1 (see FIG. 11).

[0068] [Service participation registration process] 14, the service participation registration process executed in the ticket management system 10 will be described below. Specifically, in this embodiment, the service participation registration process is executed by the control unit 11 of the management server 1. Furthermore, the control unit 11 can execute the service participation registration process in parallel for each facility terminal (not shown) in response to access from each facility terminal at each facility.

[0069] The present invention can be understood as a service participation registration method that executes one or more steps included in the service participation registration process. Furthermore, one or more steps included in the service participation registration process described herein may be omitted as appropriate. The steps in the service participation registration process may be executed in a different order as long as the same operational effect is achieved. Furthermore, while the description here takes as an example a case in which the steps in the service participation registration process are executed by the control unit 11, another embodiment of the service participation registration method may also be considered in which the steps in the service participation registration process are executed in a distributed manner by one or more processors. The service participation registration method is an example of a ticket management method of the present invention.

[0070] Here, the control unit 11 executes a process for registering participation in a business that provides the ticket service (luggage delivery service) to users. Also, here, it is assumed that the facility IDs of all affiliated facilities in a predetermined area (e.g., facilities A1 to A30) are registered in advance in the ticket information D1 (see FIG. 4).

[0071] <Step S1> First, in step S1, the control unit 11 accepts a login operation for the ticket service website from a facility terminal. For example, a facility manager of a facility that wishes to participate in the luggage delivery service uses a facility terminal to input a facility ID and password on a login page (not shown) of the website. The control unit 11 accepts the input operation for the facility ID and password. When the control unit 11 accepts the login operation (S1: Yes), it shifts the processing to step S2. The control unit 11 waits until it accepts the login operation (S1: No). When the facility manager of the facility logs in to the website, he or she can view web pages containing various information related to the ticket service.

[0072] <Step S2> In step S2, the control unit 11 determines whether participation in the luggage delivery service has been accepted from the facility. For example, when a facility manager registers his / her intention to participate by entering a facility ID and password on a participation registration page (not shown), the control unit 11 determines that participation in the luggage delivery service has been accepted from the facility. Note that the control unit 11 may also determine that participation in the luggage delivery service has been accepted from the facility if the facility ID entered on the participation registration page matches the facility ID registered in the ticket information D1 (see FIG. 4). When the control unit 11 accepts participation in the luggage delivery service from the facility (S2: Yes), it transitions the process to step S3. The control unit 11 waits until participation in the ticket service is accepted from the facility (S2: No).

[0073] <Step S3> In step S3, the control unit 11 registers participation information corresponding to the facility in the ticket information D1 (see FIG. 4). For example, the control unit 11 registers "usable" in the ticket information D1 for the facility. That is, the control unit 11 registers "usable" in the ticket information D1 as whether or not the common ticket for using the luggage delivery service can be used.

[0074] <Step S4> In step S4, the control unit 11 issues a two-dimensional code for using the parcel delivery service. Specifically, the control unit 11 issues a two-dimensional code with embedded read information including the facility ID of the facility and the code ID of the two-dimensional code. After issuing the two-dimensional code, the control unit 11 registers the code ID in the ticket information D1. If the control unit 11 receives an instruction from the facility to stop using the parcel delivery service, it registers information prohibiting the use of the common ticket ("unusable") in the ticket information D1. After step S4, the service participation registration process ends.

[0075] The issued two-dimensional code is distributed to the facility and placed within the facility (for example, at a counter), allowing users to use the package delivery service at the facility.

[0076] The facility manager of each facility that wishes to participate in the luggage delivery service performs the registration operation to obtain qualifications to provide the luggage delivery service. Each facility registered in ticket information D1 becomes able to provide the luggage delivery service to users. In this manner, the control unit 21 executes the service participation registration process. Note that the above-mentioned registration operation may also be performed manually by the manager of management server 1. For example, when the manager hears from each facility that they wish to participate in the luggage delivery service, he operates management server 1 or the manager's terminal to register "available" in ticket information D1.

[0077] [Ticket Management Processing] 15, the ticket management process executed in the ticket management system 10 will be described below. Specifically, in this embodiment, the ticket management process is executed by the control unit 11 of the management server 1. Furthermore, the control unit 11 can execute the ticket management process in parallel for each user terminal 2 in response to access from each user terminal 2.

[0078] The present invention can be understood as a ticket management method that executes one or more steps included in the ticket management process. One or more steps included in the ticket management process described herein may be omitted as appropriate. The steps in the ticket management process may be executed in a different order as long as the same operational effect is achieved. While the present invention will be described here with an example in which the steps in the ticket management process are executed by the control unit 11, another embodiment of the ticket management method may also be considered, in which the steps in the ticket management process are executed in a distributed manner by one or more processors. The ticket management method described above is one example of the ticket management method of the present invention.

[0079] <Step S11> First, in step S11, the control unit 11 determines whether or not a ticket issuance request has been received from a user. For example, when user M1 uses the user terminal 2 to log in by entering his or her user ID and password on the login page of the ticket service website (ticket service site), the control unit 11 receives a ticket issuance request from the user terminal 2. In another embodiment, the control unit 11 may receive a ticket issuance request when the user issues a ticket issuance instruction (purchase operation) on the ticket service site. When the control unit 11 receives a ticket issuance request (S11: Yes), it transitions the process to step S12. The control unit 11 waits until it receives a ticket issuance request (S11: No).

[0080] <Step S12> In step S12, the control unit 11 issues a ticket to the user. Specifically, the control unit 11 issues (displays) the ticket held by the user on the ticket selection page P1 of the user's user terminal 2 (see FIG. 8). Here, the control unit 11 displays the common ticket for the luggage delivery service on the ticket selection page P1 of the user terminal 2 of user M1.

[0081] <Step S13> Next, in step S13, the control unit 11 determines whether or not a ticket selection operation has been accepted. For example, when the user M1 selects the selection button K1 for a common ticket for the luggage delivery service on the ticket selection page P1, the control unit 11 accepts the selection operation for the common ticket. If the control unit 11 accepts the ticket selection operation (S13: Yes), it shifts the processing to step S14. If the control unit 11 does not accept the ticket selection operation (S13: No), it terminates the ticket management processing.

[0082] <Step S14> In step S14, the control unit 11 outputs an instruction to the user to photograph the two-dimensional code. Specifically, the control unit 11 displays a photographing page P2 (see FIG. 9) on the user terminal 2 of user M1. This causes the user terminal 2 to activate the camera 25 and transition to a state where it can photograph. User M1 photographs the two-dimensional code C1 with the camera 25 at a facility (e.g., facility A1) where they use the parcel delivery service (see FIG. 9).

[0083] <Step S15> In step S15, the control unit 11 determines whether or not the read information of the two-dimensional code (facility ID, code ID) has been acquired. For example, when user M1 photographs the two-dimensional code C1 of facility A1 with the user terminal 2, the control unit 11 acquires the facility ID "00001" of facility A1 and the code ID "C001" of the two-dimensional code C1 read from the two-dimensional code C1 via the user terminal 2. The control unit 11 also acquires the user ID "10001" of logged-in user M1. When the control unit 11 acquires the read information of the two-dimensional code (S15: Yes), it transitions the process to step S16. The control unit 11 waits until the read information of the two-dimensional code is acquired (S15: No).

[0084] <Step S16> In step S16, the control unit 11 determines whether the user can use the service at the facility. Here, the control unit 11 determines whether the user M1 can use the luggage delivery service at the facility A1. For example, the control unit 11 determines whether the facility associated with the acquired facility ID allows the provision of luggage delivery service (see FIG. 4). Here, since "Available" is registered for facility A1 in the ticket information D1, the control unit 11 determines that the user M1 can use the luggage delivery service at facility A1. If the user can use the service at the facility (S16: Yes), the control unit 11 shifts the process to step S17. On the other hand, if the user cannot use the service at the facility (S16: No), the control unit 11 shifts the process to step S61.

[0085] <Step S17> In step S17, the control unit 11 registers history information about the use of tickets for using the services. For example, the control unit 11 registers usage information about the common ticket for the luggage delivery service, i.e., the date and time when the common ticket was used (date and time of use) and the facility where the common ticket was used (facility where the common ticket was used), in the user information D3 (see FIG. 6). The control unit 11 also registers usage information about the luggage delivery service, i.e., the date and time when the luggage delivery service was used, the code ID of the two-dimensional code placed at the facility where the luggage delivery service was used, and the facility ID of the facility, in the usage history information D2 (see FIG. 5).

[0086] <Step S18> In step S18, the control unit 11 determines whether or not a request for tally information has been received from the administrator. For example, the administrator of the management server 1 uses the management server 1 or the administrator terminal to access the administrator page of the ticket service site and request tally information of the usage history. If the control unit 11 receives a request for tally information from the administrator (S18: Yes), it shifts the process to step S19. If the control unit 11 does not receive a request for tally information from the administrator (S18: No), it terminates the ticket management process.

[0087] <Step S19> In step S19, the control unit 11 presents the tally information to the administrator. Specifically, the control unit 11 causes the management server 1 or the administrator terminal to display usage history pages P4 (see FIG. 12) and P5 (see FIG. 13) based on the usage history information D2 and the user information D3. Specifically, the control unit 11 causes the usage history page P4 to display a list of the dates and times of use of common tickets used during the specified tally period and the names of the facilities at which the tickets were used. In addition, the control unit 11 causes the usage history page P5 to display, for each facility, the number of common tickets used during the specified tally period.

[0088] In another embodiment, the control unit 11 may send the tally information to the administrator terminal by email. Also, the control unit 11 may automatically send the tally information to the administrator terminal by email every predetermined period (for example, every month). After step S19, the control unit 11 ends the ticket management process.

[0089] <Step S61> If the control unit 11 determines in step S16 that the user cannot use the service at the facility (S16: No), it notifies the user in step S61 of a message indicating that the service is unavailable. For example, the control unit 11 causes the user terminal 2 to display a message indicating that the parcel delivery service is unavailable. The control unit 11 may also cause the user terminal 2 to display facilities where the parcel delivery service is available. After step S61, the control unit 11 ends the ticket management process. In this manner, the control unit 21 executes the ticket management process.

[0090] As described above, the ticket management system 10 of this embodiment issues a common ticket to a user for a service that can be used at multiple facilities, and when the common ticket can be used on the user's user terminal 2, when the user terminal 2 reads a reading medium (such as a two-dimensional code) placed at a facility among the multiple facilities that can provide the service, it obtains identification information (facility ID) of the facility and manages historical information indicating that the common ticket was used at the facility.

[0091] According to the above configuration, a user who has been issued a common ticket can use services at any of a plurality of facilities. Furthermore, the administrator can easily grasp the facilities where the user has used the common ticket. Therefore, it becomes possible to easily manage the usage status of the common ticket, such as how much the common ticket issued to the user has been used and at which facility the common ticket has been used.

[0092] The ticket management system 10 also associates and registers in advance the facility ID of a facility that can provide the service with the code ID of a two-dimensional code placed at the facility (see FIG. 4). This makes it possible to easily identify and manage the facilities that can provide the service. It also makes it easy to add or delete facilities that can provide the service.

[0093] The ticket management system 10 also associates and pre-registers the user IDs of multiple users with permission information regarding whether or not they can use the common ticket (see FIG. 6). This makes it easy to understand and manage users who can use the common ticket. It also makes it easy to add or delete users who can use the common ticket.

[0094] The ticket management system 10 also registers whether the common ticket can be used for each of a plurality of facilities in response to a user operation. For example, an administrator can appropriately register and update whether the use of the common ticket is permitted or prohibited for each facility.

[0095] Furthermore, a two-dimensional code is placed at each of the multiple facilities, and the facility ID and code ID of each facility are associated with the two-dimensional code. This allows the facility ID and two-dimensional code ID of the facility where the common ticket was used to be easily obtained by reading the two-dimensional code with the user terminal 2.

[0096] Furthermore, when a common ticket that can be used by a user is selected on the user terminal 2, the ticket management system 10 allows the user terminal 2 to read the two-dimensional code. This allows specific users to be permitted to use the common ticket, thereby preventing fraudulent use of the common ticket. Furthermore, the convenience of the common ticket can be improved because users can use services using the electronic ticket.

[0097] In addition, the ticket management system 10 acquires the user ID of the user terminal 2 that performed the reading process, the facility ID of the specific facility read by the reading process, and the date and time when the reading process was performed (see FIG. 6).

[0098] The ticket management system 10 also registers history information including the user ID of the user who used the common ticket, the facility ID of the facility where the common ticket was used, and the date and time when the common ticket was used, thereby making it possible to manage information related to the use of the common ticket for each user.

[0099] Furthermore, the ticket management system 10 sets an upper limit on the number of times a common ticket can be used for each user, and when the upper limit is reached, information indicating that the common ticket cannot be used is presented to the user terminal 2. This allows the user to easily understand whether or not the common ticket can be used.

[0100] The ticket management system 10 also presents aggregated information obtained by aggregating historical information. For example, the ticket management system 10 presents at least one of the following information: the date and time the common ticket was used, the facility where the common ticket was used, and the number of times the common ticket was used. This allows the administrator to easily understand the usage status of the common ticket without having to ask each facility about it.

[0101] [Other embodiments] The ticket management system of the present invention is not limited to the above-described embodiment. A ticket management system 10 according to another embodiment of the present invention will be described below.

[0102] In another embodiment of the present invention, the control unit 11 may register facilities that satisfy predetermined conditions as facilities that permit the use of the common ticket (permit the provision of services). For example, the control unit 11 may register "allowed to use" in the ticket information D1 for facilities that are close to the train station used by the user (e.g., the disembarking station). The control unit 11 may also set the number of times (maximum number of times) that the common ticket can be used at a facility depending on the distance from the station used. For example, the control unit 11 may set a high number of times that the common ticket can be used for facility A1 that is close to the user's disembarking station, and a low number of times that the common ticket can be used for facility A2 that is far from the user's disembarking station.

[0103] In another embodiment, the control unit 11 may switch between "available" and "unavailable" based on the usage status of each service at a plurality of facilities. For example, the control unit 11 temporarily switches to "unavailable" a facility whose current usage rate or usage count of the parcel delivery service exceeds a threshold. The control unit 11 also sets to "available" a facility whose current usage rate or usage count of the parcel delivery service is equal to or less than a threshold.

[0104] Furthermore, the control unit 11 may set the number of times (upper limit) that the common ticket can be used at a facility depending on the current usage rate or number of times that the luggage delivery service is used. For example, if the luggage delivery service is used less frequently at facility A2, the control unit 11 sets the number of times that the common ticket can be used at facility A2 to be higher, and if the luggage delivery service is used more frequently at facility A1, the control unit 11 sets the number of times that the common ticket can be used at facility A1 to be lower.

[0105] In another embodiment, the control unit 11 may suggest facilities where the luggage delivery service is available to a user who holds a common ticket for the luggage delivery service. For example, the control unit 11 may suggest the facilities based on the user's current location, or based on the user's usage history. The control unit 11 may also suggest the facilities based on the current usage status of multiple facilities. For example, the control unit 11 suggests to the user facilities with a low number of current luggage delivery service users (acceptance numbers).

[0106] In the above-described embodiment, as shown in Fig. 4, the control unit 11 registers information regarding whether or not a common ticket can be used for each facility for a specific service (here, a luggage delivery service), but in another embodiment, the control unit 11 may register information regarding whether or not a ticket can be used for each facility for each of a plurality of services (services X, Y, and Z), as shown in Fig. 16. The administrator can collectively register and manage whether or not a plurality of services provided at a plurality of facilities can be used.

[0107] In the above configuration, the two-dimensional codes issued to each facility may be assigned a common code ID for services X, Y, and Z. This allows each facility to receive one two-dimensional code, eliminating the need for multiple two-dimensional codes at one facility, thereby preventing confusion and errors in reading the two-dimensional codes. In the above configuration, the control unit 11 may issue tickets for each available service to each user. For example, if user M1 can use services X and Y, the control unit 11 issues user M1 a first common ticket for service X and a second common ticket for service Y. For example, when user M1 uses service X at facility A5, user M1 selects the first common ticket and reads the two-dimensional code for facility A5. The control unit 11 then identifies service X in response to user M1's selection operation and acquires the facility ID and code ID of facility A5. This allows the control unit 11 to acquire and manage usage information related to service X.

[0108] [Notes on the Invention] The following is a summary of the invention extracted from the above-described embodiment. Note that the configurations and processing functions described in the following supplementary notes can be selected and combined as desired.

[0109] <Appendix 1> an issuance processing unit that issues a common ticket for a service that can be used in common at a plurality of facilities to a user; an acquisition processing unit that acquires identification information of a specific facility when the user terminal reads a reading medium placed at a specific facility that can provide the service among the plurality of facilities, when the common ticket can be used with the user terminal of the user; a management processing unit that manages history information indicating that the common ticket has been used at the specific facility; A ticket management system that includes:

[0110] <Appendix 2> a registration processing unit that associates and registers in advance identification information of a facility that can provide the service with identification information of the readable medium placed at the facility; The ticket management system described in Appendix 1.

[0111] <Appendix 3> The registration processing unit further associates identification information of each of a plurality of users with availability information regarding availability of the common ticket and registers the information in advance. The ticket management system described in Appendix 2.

[0112] <Appendix 4> the registration processing unit registers whether the common ticket can be used for each of the plurality of facilities in response to a user operation; 3. A ticket management system as set forth in Appendix 2 or 3.

[0113] <Appendix 5> The reading medium is disposed in each of the plurality of facilities, The reading medium is associated with identification information of the facility and identification information of the reading medium for each facility. Attachment 1 to 4, the ticket management system of any one of the above.

[0114] <Appendix 6> When the common ticket that can be used by the user is selected at the user terminal, the reading process of the read medium at the user terminal is permitted. 6. A ticket management system according to any one of appendices 1 to 5.

[0115] <Appendix 7> The acquisition processing unit acquires identification information of the user of the user terminal that performed the reading process, identification information of the specific facility read by the reading process, and the date and time when the reading process was performed. 10. A ticket management system according to any one of appendices 1 to 6.

[0116] <Appendix 8> the management processing unit registers the history information, which includes identification information of the user who used the common ticket, identification information of the specific facility where the common ticket was used, and the date and time when the common ticket was used; 10. A ticket management system according to any one of appendices 1 to 7.

[0117] <Appendix 9> A maximum number of times the common ticket can be used is set for each user, When the number of times of use reaches the upper limit, information indicating that the common ticket cannot be used is presented to the user terminal. Attachment 1-8: A ticket management system according to any one of the preceding claims.

[0118] <Appendix 10> a presentation processing unit that presents aggregated information obtained by aggregating the history information; The presentation processing unit presents at least one of information on the date and time of use of the common ticket, the specific facility where the common ticket was used, and the number of times the common ticket was used. 10. A ticket management system according to any one of appendices 1 to 9. [Explanation of symbols]

[0119] 1: Management Server 2: User terminal 10: Ticket management system 11: Control section 12: Storage section 13: Operation display section 14: Communications Department 21: Control unit 22: Storage section 23: Operation display section 24: Communications Department 25: Camera 111: Registration processing unit 112: Issuance processing unit 113: Reception processing unit 114: Acquisition processing unit 115: Judgment processing unit 116: Management Processing Unit 117: Presentation processing unit 211: Browser processing section D1: Ticket Information D2: Usage history information D3: User information D4: Aggregate information K1: Select button K2: Select button P1: Ticket selection page P2: Shooting page P3: Ticket use page P4: Usage history page P5: Usage history page

Claims

1. an issuance processing unit that issues a common ticket for a service that can be used in common at a plurality of facilities to a user; an acquisition processing unit that acquires identification information of a specific facility when the user terminal reads a reading medium placed at a specific facility that can provide the service among the plurality of facilities, when the common ticket can be used with the user terminal of the user; a management processing unit that manages history information indicating that the common ticket has been used at the specific facility; A ticket management system that includes:

2. a registration processing unit that associates and registers in advance identification information of a facility that can provide the service with identification information of the readable medium placed at the facility; The ticket management system according to claim 1 .

3. The registration processing unit further associates identification information of each of a plurality of users with availability information regarding availability of the common ticket and registers the information in advance. The ticket management system according to claim 2 .

4. the registration processing unit registers whether the common ticket can be used for each of the plurality of facilities in response to a user operation; The ticket management system according to claim 2 .

5. The reading medium is disposed in each of the plurality of facilities, The reading medium is associated with identification information of the facility and identification information of the reading medium for each facility. The ticket management system according to claim 1 .

6. When the common ticket that can be used by the user is selected at the user terminal, the reading process of the read medium at the user terminal is permitted. The ticket management system according to claim 1 .

7. The acquisition processing unit acquires identification information of the user of the user terminal that performed the reading process, identification information of the specific facility read by the reading process, and the date and time when the reading process was performed. The ticket management system according to claim 6 .

8. the management processing unit registers the history information, which includes identification information of the user who used the common ticket, identification information of the specific facility where the common ticket was used, and the date and time when the common ticket was used; The ticket management system according to claim 1 .

9. A maximum number of times the common ticket can be used is set for each user, When the number of times of use reaches the upper limit, information indicating that the common ticket cannot be used is presented to the user terminal. The ticket management system according to claim 1 .

10. a presentation processing unit that presents aggregated information obtained by aggregating the history information; The presentation processing unit presents at least one of information on the date and time of use of the common ticket, the specific facility where the common ticket was used, and the number of times the common ticket was used. The ticket management system according to any one of claims 1 to 9.

11. Issuing a common ticket for a service that can be used in common at a plurality of facilities to a user; When the common ticket can be used on the user terminal of the user, when the user terminal reads a reading medium placed at a specific facility among the plurality of facilities that can provide the service, acquiring identification information of the specific facility; managing history information indicating that the common ticket has been used at the specific facility; A ticket management method executed by one or more processors.

12. Issuing a common ticket for a service that can be used in common at a plurality of facilities to a user; When the common ticket can be used on the user terminal of the user, when the user terminal reads a reading medium placed at a specific facility among the plurality of facilities that can provide the service, acquiring identification information of the specific facility; managing history information indicating that the common ticket has been used at the specific facility; A ticket management program for executing on one or more processors.

Images