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

Abstract

To provide a ticket management system, a ticket management device, a ticket management method, and a program that can impose a restriction on transfer of an electronic ticket in which a set ticket is digitized.SOLUTION: A first determination unit 111 determines whether or not a purchased digital ticket designated as a transfer target from an information terminal 20 of a purchaser who purchased the digital ticket is a set ticket including a plurality of dependent tickets. A transfer setting unit 116 prohibits individual transfer of the dependent tickets included in the selected ticket and permits batch transfer of the selected ticket based on a result of determination by the first determination unit 111.SELECTED DRAWING: Figure 3

Description

[Technical Field]

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

[0002] In recent years, electronic tickets (digital tickets) using information codes such as QR Codes (registered trademark) have been used as tickets for railway services operated by railway operators. Such electronic tickets are used not only for train tickets but also for airline boarding passes, ship boarding passes, and admission tickets to facilities such as theme parks, museums, aquariums, movie theaters, concert venues, and event venues. Such electronic tickets are displayed on the screen of a mobile device such as a smartphone carried by the user, and authentication processing is performed by scanning the electronic ticket on the screen at the time of entry, and entry is permitted once authentication is complete.

[0003] Traditionally, railway services have sold set tickets that include multiple dependent tickets. These set tickets are not just a single passenger ticket, but also include other passenger tickets or admission tickets to facilities, and in Japan they are called special offer tickets, special offer tickets, or Tokutoku tickets. Because these set tickets include multiple dependent tickets, they are priced relatively high, but offer a higher discount than purchasing each dependent ticket individually.

[0004] In recent years, electronic tickets, which are the electronic versions of the set tickets, have been sold. The electronic tickets for the set tickets can be purchased, for example, using an online sales system operated and managed by a railway operator, and the purchased electronic tickets are managed in a database within the system.

[0005] Patent Document 1 discloses a system capable of managing the transfer of electronic tickets. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-032649 Summary of the Invention [Problem to be solved by the invention]

[0007] However, the set ticket is originally intended to be used by the purchaser and is sold at a high discount rate on the assumption that the purchaser will use it. However, if the dependent tickets included in the electronic ticket of the set ticket are individually transferred to someone other than the purchaser using conventional transfer methods, the purchaser who purchased the boarding ticket or admission ticket individually will suffer a disadvantage.

[0008] An object of the present invention is to provide a ticket management system, a ticket management device, a ticket management method, and a program that are capable of imposing restrictions on the transfer of electronic tickets in which a set ticket has been digitized. [Means for solving the problem]

[0009] A ticket management system according to one embodiment of the present invention is a ticket management system that manages electronic tickets, and includes a first judgment unit that judges whether the electronic ticket designated as a transfer target from a terminal device associated with the electronic ticket is a set ticket consisting of multiple dependent tickets, and a transfer setting unit that prohibits the individual transfer of the dependent tickets and allows the bulk transfer of the electronic ticket based on the judgment result of the first judgment unit.

[0010] A ticket management device according to another aspect of the present invention is a ticket management device that manages electronic tickets, and includes a first judgment unit that judges whether the electronic ticket designated as a transfer target from a terminal device associated with the electronic ticket is a set ticket consisting of multiple dependent tickets, and a transfer setting unit that prohibits the individual transfer of the dependent tickets and allows the bulk transfer of the electronic ticket based on the judgment result of the first judgment unit.

[0011] Another aspect of the ticket management method of the present invention is a ticket management method for managing electronic tickets, which is executed by one or more processors: a first determination step for determining whether the electronic ticket designated as a transfer target from a terminal device associated with the electronic ticket is a set ticket consisting of multiple dependent tickets; and a transfer setting step for prohibiting individual transfer of the dependent tickets and allowing bulk transfer of the electronic ticket based on the determination result of the first determination step.

[0012] A program relating to another aspect of the present invention is a program for managing electronic tickets, which is a program for causing one or more processors to execute a first determination step of determining whether the electronic ticket designated as a transfer target from a terminal device associated with the electronic ticket is a set ticket consisting of multiple dependent tickets, and a transfer setting step of prohibiting individual transfer of the dependent tickets and allowing bulk transfer of the electronic ticket based on the determination result of the first determination step.

[0013] The present invention can also be understood as an invention of a non-transitory computer-readable storage medium on which the program is stored. [Effects of the Invention]

[0014] According to the present invention, it is possible to impose restrictions on the transfer of electronic tickets in which a set ticket has been digitized. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram showing the configuration of a ticket management system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram showing the configuration of an information terminal according to an embodiment of the present invention. [Figure 3] FIG. 3 is a block diagram showing the configuration of a management device according to an embodiment of the present invention. [Figure 4] FIG. 4 is a diagram showing an example of ticket registration data including information on tickets already purchased by a specific purchaser. [Figure 5] FIG. 5 is a diagram showing an example of a screen (login screen) displayed on an information terminal used by a purchaser. [Figure 6] FIG. 6 is a diagram showing an example of a screen (digital ticket list screen) displayed on an information terminal used by a purchaser. [Figure 7] FIG. 7 is a diagram showing an example of a screen (ticket information screen) displayed on an information terminal used by a purchaser. [Figure 8] FIG. 8 is a diagram showing an example of a screen (set details screen) displayed on an information terminal used by a purchaser. [Figure 9] FIG. 9 is a diagram showing an example of a screen (information code display screen) displayed on the information terminal used by the purchaser. [Figure 10] FIG. 10 is a diagram showing an example of a screen (transfer ticket selection screen) displayed on the information terminal used by the purchaser. [Figure 11] FIG. 11 is a diagram showing an example of a screen (transfer ticket selection screen) displayed on the information terminal used by the purchaser. [Figure 12] FIG. 12 is a diagram showing an example of a screen (transfer completion notification screen) displayed on the information terminal used by the purchaser. [Figure 13] FIG. 13 is a diagram showing an example of a screen (digital ticket list screen) displayed on the information terminal used by the purchaser after the transfer. [Figure 14] FIG. 14 is a diagram showing an example of a screen (digital ticket list screen) displayed on the information terminal used by the transferee. [Figure 15] FIG. 15 is a diagram showing an example of a screen (ticket information screen) displayed on the information terminal used by the transferee. [Figure 16] FIG. 16 is a flowchart showing an example of a ticket transfer process executed in the ticket management system according to an embodiment of the present invention. [Figure 17] FIG. 17 is a flowchart showing an example of a ticket transfer process executed in the ticket management system according to an embodiment of the present invention. [Figure 18] FIG. 18 is a flowchart showing another example of the ticket transfer process executed in the ticket management system according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0016] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Note that the embodiments described below are merely examples of the present invention and do not limit the technical scope of the present invention.

[0017] [Ticket Management System 100] 1 is a diagram showing the configuration of a ticket management system 100 (hereinafter simply referred to as "management system 100") according to an embodiment of the present invention. The management system 100 is a system that manages the use and transfer of sold digital tickets (electronic tickets) in cooperation with a ticket sales system 200 operated by a railway operator.

[0018] In this embodiment, the management system 100 is described as a system that manages the use, transfer, etc. of digital tickets such as digitized digital tickets and digital set tickets sold by the ticket sales system 200, but the present invention is not limited to the management of this type of digital ticket, and may be, for example, a system that manages the use, transfer, etc. of digital set tickets that do not include digital tickets.

[0019] In the following, the management system 100 will be described as being independent from the ticket sales system 200 that sells computerized digital tickets, digital set tickets, and the like, and from other systems, but the management system 100 may also be incorporated into an existing ticket sales system 200. Furthermore, the management system 100 may also include the ticket sales system 200.

[0020] 1, the management system 100 includes a management device 10 and one or more information terminals 20 (an example of a terminal device of the present invention). In the management system 100, the management device 10 is communicably connected to a ticket sales system 200 and the information terminals 20 via a network N1, which is a wireless communication network or a wired communication network. The network N1 is, for example, a dedicated line or a public line.

[0021] The management device 10 is, for example, an information processing device managed by a railway operator or its related operator, such as a server device or a cloud server. The management device 10 is not limited to being configured by a single computer, but may be a computer system in which multiple computers operate in cooperation, or a cloud computing system. The various processes executed by the management device 10 may be executed by a single processor, or may be executed in a distributed manner by multiple processors. Computer software for operating the management system 100 of this embodiment is installed in the management device 10.

[0022] The information terminal 20 is an information processing device or terminal device used by a user who holds a digital ticket purchased through the ticket sales system 200. The information terminal 20 is, for example, a mobile terminal such as a smartphone or tablet terminal that can be carried by the user. An application (software) is installed on the information terminal 20 in cooperation with the management system 100 and the ticket sales system 200 to purchase various digital tickets, check ticket information of purchased digital tickets, transfer purchased digital tickets, and receive transferred digital tickets. By operating the application running on the information terminal 20, the user can purchase digital tickets, check the ticket information, and transfer digital tickets.

[0023] The ticket sales system 200 is a conventionally known system that issues digital tickets for trains running on a desired date and time over a desired section of a user's travel, as well as digital set tickets that include the digital tickets as dependent tickets, based on a purchase request from an information terminal 20 used by the user. The ticket information relating to various digital tickets purchased in advance by users is stored and managed by the ticket sales system 200. The ticket sales system 200 also stores and manages the ticket information for digital tickets that have already been used by users.

[0024] Here, the digital set ticket is an electronic version of a set ticket (a ticket with an admission ticket) that includes a boarding ticket and an admission ticket to a facility, and is known as a conventional special offer ticket, special special offer ticket, or Tokutoku ticket. In other words, the digital set ticket is a set that includes not only the digital boarding ticket but also a digital admission ticket that is an electronic version of the admission ticket for entering a specified facility.

[0025] The predetermined facilities are, for example, theme parks, museums, aquariums, movie theaters, concert venues, event venues, and the like.

[0026] Hereinafter, in this embodiment, the digital set ticket may be simply referred to as a set ticket. Furthermore, multiple digital tickets (such as digital train tickets and digital admission tickets) included in the digital set ticket may be referred to as dependent tickets.

[0027] The ticket sales system 200 manages the ticket information of digital tickets purchased by users for each user ID. The ticket sales system 200 registers and manages the ticket information in ticket management data 201. The ticket management data 201 stores ticket registration data for each user ID, which includes information on all digital tickets purchased by the user. The ticket management data 201 is stored, for example, in a database owned by the ticket sales system 200 or in an external storage device accessible by the ticket sales system 200.

[0028] Figure 4 shows an example of the ticket registration data, which includes information on multiple tickets purchased by a user. As shown in Figure 4, the ticket registration data includes ticket information for each purchased digital ticket. The ticket information includes the ticket ID, ticket type, purchase date, number of tickets purchased, expiration date, ticket name, set contents, usage status, transfer setting, transfer status, and the user ID of the transferee of the purchased digital ticket.

[0029] The ticket ID is an identification number of a purchased digital ticket.

[0030] The ticket type indicates the type of digital ticket. In this embodiment, digital tickets are classified into one of a single type indicating a single ticket, a set type indicating the set ticket, a coupon type indicating a digital multi-ride ticket, and other types. The digital multi-ride ticket is a digital ticket that includes multiple identical digital tickets. Other types include, for example, a digital ticket with an express ticket that includes a ticket for a specified section and an express ticket, and a digital round-trip ticket that includes an outbound ticket and a return ticket for a specified section.

[0031] The purchase date indicates the date and time when the digital ticket was purchased. The validity period indicates the period during which the purchased digital ticket is valid for use. The validity period may be, for example, the expiration date from the purchase date or the period from the specified start date of use to the specified end date of use.

[0032] The set contents indicate the breakdown of dependent tickets when the digital ticket includes multiple dependent tickets. For example, the digital ticket "AAA Round-Trip Ticket" with ticket ID

[0002] in Figure 4 includes six dependent tickets: outbound ticket X21, return ticket X22, round-trip ticket X23, admission ticket Y24, admission ticket Y25, and bonus ticket Z26, such as a discount coupon. Furthermore, the digital ticket "BBB Round-Trip Ticket" with ticket ID

[0003] includes six dependent tickets: outbound ticket X31, return ticket X32, round-trip ticket X33, admission ticket Y34, admission ticket Y35, and bonus ticket Z36.

[0033] The usage status indicates whether the digital ticket is unused or used. If the digital ticket has dependent tickets, the usage status is indicated for each dependent ticket.

[0034] The transfer setting indicates whether transfer of the digital ticket is prohibited or permitted. For a digital ticket that is set to be prohibited, the operation screen on the application running on the information terminal 20 is configured so that a transfer instruction cannot be entered.

[0035] The transfer status indicates whether the digital ticket is untransferred or transferred. For transferred digital tickets and dependent tickets, the user ID of the transferee is registered as information to identify the transferee.

[0036] When the ticket sales system 200 receives a query request from the management device 10, it extracts the ticket purchase data (see FIG. 4) corresponding to the user ID included in the query request from the ticket management data 201, and transmits the extracted ticket purchase data to the management device 10. Alternatively, when the ticket sales system 200 receives the query request, it makes the ticket purchase data corresponding to the user ID accessible to the management device 10.

[0037] [Information terminal 20] The specific configuration of the information terminal 20 will be described below with reference to Fig. 2. Fig. 2 is a block diagram showing the configuration of the information terminal 20.

[0038] The information terminal 20 is used by the purchaser of the digital ticket or, as will be described later, by the transferee who has received the transfer of the digital ticket. Hereinafter, for convenience, the information terminal 20 used by the purchaser will be referred to as the first information terminal 20A, and the information terminal 20 used by the transferee will be referred to as the second information terminal 20B. When there is no need to distinguish between the first information terminal 20A and the second information terminal 20B, they will simply be referred to as the information terminal 20.

[0039] As shown in FIG. 2, the information terminal 20 includes a control unit 21, a storage unit 22, an operation display unit 23, a two-dimensional code reading unit 26, an imaging unit 27, a communication unit 28, and the like.

[0040] The communication unit 28 is a communication interface for connecting the information terminal 20 to the network N1 and for executing data communication with the management device 10 via the network N1 in accordance with a predetermined communication protocol.

[0041] The storage unit 22 is a non-volatile storage medium such as a flash memory that stores various types of information. The storage unit 22 stores control programs for causing the control unit 21 to execute various types of arithmetic processing, the above-mentioned application programs, data used in the various types of arithmetic processing, and the like.

[0042] The imaging unit 27 is provided, for example, on the rear surface of the information terminal 20. The imaging unit 27 is specifically a camera.

[0043] When a two-dimensional code is captured by the imaging unit 27, the two-dimensional code reading unit 26 decodes the two-dimensional code contained in the image and obtains predetermined information contained in the two-dimensional code.

[0044] The operation display unit 23 is a user interface that includes a display unit 23A such as a liquid crystal display or an organic EL display that displays various information, and an operation unit (not shown) such as a mouse, keyboard, or touch panel that accepts user operations. Display screens and screens used in the applications are displayed on the display unit 23A of the operation display unit 23.

[0045] The control unit 21 controls the operation of each unit of the information terminal 20. The control unit 21 has control devices such as a CPU, a ROM, and a RAM. The CPU is a processor that executes various processes. The ROM is a non-volatile storage medium in which control programs such as a BIOS and an OS that cause the CPU to execute various processes are stored in advance. The RAM is a volatile or non-volatile storage medium that stores various information, and is used as a temporary storage memory (work area) for the various processes executed by the CPU. The control unit 21 controls the information terminal 20 by having the CPU execute various control programs that are stored in advance in the ROM or the storage unit 22.

[0046] As shown in FIG. 2 , the control unit 21 includes various processing units such as a display processing unit 211, a transmission processing unit 212, and an operation invalidation processing unit 213. The control unit 21 functions as the various processing units by the CPU executing various arithmetic processing in accordance with the control program. In this embodiment, the control unit 21 runs the application program stored in the storage unit 22 on the CPU, thereby running the application on the information terminal 20. When the application runs on the information terminal 20, the control unit 21 runs a screen display process by the display processing unit 211 and a transmission process by the transmission processing unit 212. The control unit 21 or the CPU is an example of a computer that runs the control program. Note that some or all of the processing units included in the control unit 21 may be configured with electronic circuits. The control program may also be a program that causes multiple processors to function as the various processing units.

[0047] The display processing unit 211 displays each of the screens 41 to 47 described below on the display screen of the display unit 23A. The transmission processing unit 212 also transmits to the management device 10 various requests such as information, execution instructions, inquiry requests, and display requests input via each of the screens 41 to 47.

[0048] In this embodiment, the control unit 21 displays on the display screen of the display unit 23A one of a login screen 41 (see Figure 5), a digital ticket list screen 42 (see Figures 6, 12, 13, and 14), a ticket information screen 43 (see Figures 7 and 15), a set details screen 44 (see Figure 8), an information code display screen 45 (see Figure 9), a transfer ticket selection screen 46 (see Figures 10 and 11), and a transfer completion notification screen 47 (see Figure 12).

[0049] The login screen 41 is a screen for enabling the application linked to the management system 100, and is the screen that is first displayed when the application is started on the information terminal 20. As shown in Fig. 5, the login screen 41 displays an input box 411 for inputting a user ID registered in the management system 100, and an input box 412 for inputting a password. When the purchaser's user ID is input into the input box 411, the password is input into the input box 412, and then the enter button 413 is operated, the input information is sent to the management device 10, and login authentication is performed in the management device 10. When the login is approved, the control unit 21 displays a top screen (not shown) on the display unit 23A.

[0050] 6, the digital ticket list screen 42 is a screen that displays all digital tickets that have been purchased. Each digital ticket is displayed in a selectable manner on the digital ticket list screen 42. The digital ticket list screen 42 can be displayed from the menu section (not shown) on the TOP screen.

[0051] 6 shows a list of each digital ticket included in the ticket registration data shown in FIG. 4. When an operation to display the digital ticket list screen 42 is performed from the menu field of the TOP screen, a display request is sent to the management device 10. Upon receiving the display request, the management device 10 refers to the ticket management data 201 and extracts the ticket registration data corresponding to the user ID included in the display request. Then, the management device 10 obtains information on the ticket ID, ticket name, number of tickets, and purchase date for all registered digital tickets from the ticket registration data and sends this information to the information terminal 20 that made the request. Upon receiving this information, the information terminal 20 displays the received information for each digital ticket on the digital ticket list screen 42.

[0052] The digital ticket list screen 42 has three ticket display frames 421 to 423, and tickets are displayed in each display frame, divided into currently used tickets, unused purchased tickets, and used tickets.

[0053] When any digital ticket on the digital ticket list screen 42 is selected by a touch operation, a ticket information screen 43 (see FIG. 7) including detailed information about the selected digital ticket is displayed.

[0054] For example, in Fig. 6, when the digital ticket "BBB Tour Ticket" with ticket ID

[0003] displayed in the purchased ticket display frame 422 is selected, a request to query information on the selected digital ticket (hereinafter referred to as the "selected ticket") is sent to the management device 10. When the management device 10 receives the query request, it obtains ticket information for the selected ticket from the ticket registration data and sends it to the requesting information terminal 20. When the information terminal 20 receives the ticket information, it displays it on the ticket information screen 43 (see Fig. 7).

[0055] As shown in Fig. 7, the ticket information screen 43 displays status information indicating the usage status (unused, used) of the selected ticket in addition to the ticket information of the selected ticket. The ticket information screen 43 also displays an operation unit 431 for displaying details of the dependent tickets included in the selected ticket, an operation unit 432 for proceeding to transfer processing for the selected ticket, and an operation unit 433 for proceeding to refund processing for the selected ticket. Fig. 7 shows an example of the ticket information screen 43 when the digital ticket "BBB Tour Ticket" is selected.

[0056] If the selected ticket does not include any dependent tickets, the operation section 431 is not displayed.

[0057] In this embodiment, if the transfer of the selected ticket is permitted, the selected ticket becomes the transfer target, the operation unit 432 is displayed on the ticket information screen 43, and the transfer operation of the selected ticket using the operation unit 432 is enabled. On the other hand, if the transfer of the selected ticket is not permitted, the selected ticket is not the transfer target, and the transfer operation of the selected ticket using the information terminal 20 is disabled. Specifically, the operation unit 432 is not displayed on the ticket information screen 43, or is set to an inoperable state.

[0058] The validity or invalidity of the transfer operation is determined by the operation invalidation processing unit 213. That is, in this embodiment, when transfer of the selected ticket is permitted, the operation invalidation processing unit 213 displays the operation unit 432 based on permission information input from the management device 10. Furthermore, when transfer of the selected ticket is prohibited, the operation invalidation processing unit 213 does not display the operation unit 432 or displays it in an inoperable state based on prohibition information input from the management device 10.

[0059] Whether or not the transfer of the selected ticket is permitted, that is, whether or not the selected ticket is eligible for transfer, is determined in the ticket transfer process (see FIGS. 16 to 18) described later.

[0060] When the operation unit 431 is operated on the ticket information screen 43, a set details screen 44 shown in FIG. 8 is displayed.

[0061] The set details screen 44 in Figure 8 displays a plurality of operation units 441 corresponding to the dependent tickets included in the selected ticket. The operation unit 441 is used to display the information codes of the dependent tickets. When the operation unit 441 corresponding to the dependent ticket desired to be used is operated, the information code display screen 45 shown in Figure 9 is displayed, and the dependent ticket becomes usable, that is, it becomes readable by a reader that reads the information code. Note that Figure 9 shows an example of the screen when the operation unit 441 corresponding to the dependent ticket "Outbound Ticket X31" is operated.

[0062] When the operation unit 432 is operated on the ticket information screen 43, a transfer ticket selection screen 46 shown in FIG. 10 or FIG. 11 is displayed.

[0063] If the purchaser wishes to transfer the selected ticket selected on the digital ticket list screen 42, the purchaser operates the operation unit 432 to display the transfer ticket selection screen 46 (see FIG. 10 or 11). As mentioned above, if the operation unit 432 is not displayed even when the purchaser wishes to transfer the selected ticket, this means that the selected ticket is a digital ticket that is prohibited from being transferred and is not eligible for transfer. In this case, the purchaser cannot perform the transfer operation for the selected ticket.

[0064] The transfer ticket selection screen 46 shown in FIG. 10 or 11 displays the contents of the selected ticket to be transferred.

[0065] For example, if the selected ticket is a ticket (e.g., a set ticket) that is permitted to be transferred in its entirety, including the dependent tickets, in other words, if the selected ticket is permitted to be transferred but the dependent tickets are prohibited from being transferred individually, then, as shown in Figure 10, only a selection box 462 (an example of the operation input unit of the present invention) for selecting all the dependent tickets included in the selected ticket at once will be displayed on the transfer ticket selection screen 46, and selection boxes 466 (see Figure 11) for selecting each dependent ticket individually will not be displayed. In other words, the operation of selecting the dependent tickets as transfer targets will be disabled. Furthermore, if multiple digital tickets have already been purchased, an input box 461 will be displayed for specifying the number of tickets to be transferred.

[0066] When transferring the selected tickets for which only bulk transfer is permitted, the purchaser first enters the number of tickets to be transferred in input box 461, and then enters a check mark in the selection box 462 for the selected ticket. After that, the purchaser enters the user ID of the transferee in input box 464, and when execute button 465 is pressed, a transfer execution instruction is sent to management device 10. Then, management device 10 performs a registration change process for the digital tickets, and the bulk transfer of the digital tickets is completed.

[0067] The user ID of the transferee may be obtained by operating operation unit 463 for reading an information code to activate imaging unit 27 and read an information code including the user ID displayed on second information terminal 20B of the transferee user. In this case, once the user ID is obtained, it is automatically input into input box 464.

[0068] On the other hand, for example, if the selected ticket is a ticket that allows not only bulk transfer but also individual transfer of dependent tickets (for example, a digital multiple-ride ticket), a selection box 466 (an example of the operation input unit of the present invention) is displayed on the transfer ticket selection screen 46 in addition to the bulk transfer selection box 462, as shown in Fig. 11. The selection box 466 is an operation input unit that accepts the selection input of the dependent tickets as the transfer target.

[0069] For example, when the purchaser wishes to transfer some of the dependent tickets included in the selected ticket, the purchaser first checks the selection box 466 of the dependent ticket that he / she wishes to transfer. After that, he / she enters the user ID of the transferee in the input box 464 and presses the execute button 465, which sends a transfer execution instruction to the management device 10. Then, the management device 10 performs a registration change process for the dependent tickets, and the transfer of the dependent tickets is completed.

[0070] The determination of whether the selected ticket is one for which only bulk transfer is permitted or whether individual transfer of dependent tickets is also permitted is made in the ticket transfer process (see FIGS. 16 to 18) described later.

[0071] The validity or invalidity of the selection of the individual transfer of the dependent tickets is executed by the operation invalidation processing unit 213. That is, in this embodiment, when the individual transfer of the dependent tickets is permitted, the operation invalidation processing unit 213 displays the selection box 466 based on the permission information input from the management device 10. Furthermore, when the individual transfer of the dependent tickets is prohibited, the operation invalidation processing unit 213 does not display the selection box 466 or displays it in an inoperable state based on the prohibition information input from the management device 10.

[0072] When the registration change process is completed in the management device 10, a completion notice is sent from the management device 10 to the first information terminal 20A of the purchaser and the second information terminal 20B of the transferee. When the completion notice is received, a transfer completion notice screen 47 shown in FIG. 12 is displayed on the display unit 23A of the first information terminal 20A.

[0073] When the transfer of the selected ticket is complete, the transferred selected ticket is moved from the purchased ticket display frame 422 to the in-use ticket display frame 421 on the digital ticket list screen 42 on the first information terminal 20A, as shown in Fig. 13. In other words, the transferred selected ticket is deleted from the purchased ticket display frame 422 and is added to and displayed in the in-use ticket display frame 421. Fig. 13 shows a list after transfer when only one digital ticket, the "BBB Tour Ticket" with ticket ID

[0003] , is transferred.

[0074] On the second information terminal 20B of the transferee that has received the digital ticket, a transfer ticket display frame 424 is generated on the digital ticket list screen 42, as shown in FIG. 14, and the transferred digital ticket (hereinafter referred to as the "transfer ticket") is displayed in the transfer ticket display frame 424.

[0075] In this embodiment, when the transfer ticket is selected in the transfer ticket display frame 424 on the second information terminal 20B, a ticket information screen 43A including detailed information about the transfer ticket is displayed, as shown in FIG. 15 . In this embodiment, the transfer ticket is permitted only to be returned to the transferor; transfer to anyone other than the transferor is prohibited, and refunds are also prohibited. Therefore, on the ticket information screen 43A of the transfer ticket on the second information terminal 20B, the operation unit 432 for transitioning to the transfer process of the transfer ticket is not displayed. Also, the operation unit 433 for transitioning to the refund process is not displayed, and instead, the operation unit 434 for transitioning to the ticket return process to return the ticket to the transferor is displayed. When the operation unit 434 on the ticket information screen 43A is operated, a return execution instruction is sent to the management device 10. Then, the management device 10 executes the return process of the transfer ticket.

[0076] [Management device 10] A specific configuration of the management device 10 will be described below with reference to FIG.

[0077] The management device 10 is intended to realize the management system 100 of this embodiment, and as shown in Figure 3, it includes a control unit 11, a memory unit 12, a communication unit 13, a display unit 14, and an operation unit 15.

[0078] The communication unit 13 is a communication interface that connects the management device 10 to the network N1 and executes data communication with each device connected to the network N1 in accordance with a predetermined communication protocol. Specifically, the communication unit 13 executes data communication with the information terminal 20 and the ticket sales system 200 via the network N1.

[0079] The storage unit 12 is a non-volatile storage medium such as an HDD or SSD that stores various types of information. The storage unit 12 stores control programs for executing various processes by the control unit 11, as well as data, thresholds, reference values, etc. used in the various processes.

[0080] The display unit 14 is a display device such as a liquid crystal display or an organic EL display that displays various information. The operation unit 15 is an input device such as a mouse, keyboard, or touch panel that accepts operations by an operator.

[0081] Incidentally, physical multi-ride tickets have traditionally been separated and transferred individually, and therefore, it is conceivable that the dependent tickets included in the digital multi-ride ticket may also be subject to individual transfer as in the past. However, for example, non-digital set tickets such as the physical promotional tickets are sold at a high discount rate on the assumption that the purchaser will use them, and have not traditionally been subject to individual separation and transfer. Therefore, it is necessary to impose restrictions on the transferability of each dependent ticket of a digital set ticket. If the transferability of the dependent tickets were permitted, purchasers who purchased individual boarding or admission tickets would be at a disadvantage compared to those to whom the dependent tickets were transferred.

[0082] In response to this, in the management system 100 of this embodiment, the control unit 11 configured as described below executes the ticket transfer process (see FIGS. 16 to 18) described below, which makes it possible to impose appropriate restrictions on the transfer of dependent tickets of a digital set ticket.

[0083] The control unit 11 controls the operation of each unit of the management device 10. The control unit 11 has control devices such as a CPU, a ROM, and a RAM. The CPU is a processor that executes various processes. The ROM is a non-volatile storage medium that stores control programs such as a BIOS and an OS for causing the CPU to execute various processes. The RAM is a volatile or non-volatile storage medium that stores various information and is used as a temporary storage memory (work area) for the various processes executed by the CPU. The control unit 11 controls the management device 10, the management system 100, etc. by having the CPU execute various control programs that are stored in advance in the ROM or the storage unit 12.

[0084] In this embodiment, the control unit 11 is configured to perform a ticket transfer process (see FIGS. 16 to 18) described below. To perform the ticket transfer process, the control unit 11 includes various processing units, such as a reception processing unit 110, a first determination unit 111, a second determination unit 112, a third determination unit 113, a fourth determination unit 114, an expiration date determination unit 115, a transfer setting unit 116, and a notification processing unit 117, as shown in FIG. 3. Note that in this embodiment, not all of these processing units are necessarily required, and some may be omitted.

[0085] The control unit 11 functions as the various processing units by the CPU executing various arithmetic processes in accordance with the control program. The control unit 11 or the CPU is an example of a computer or processor that executes the control program. Note that some or all of the processing units included in the control unit 11 may be configured with electronic circuits. The control program may also be a program that causes multiple processors to function as the various processing units.

[0086] The reception processing unit 110 performs processing to receive inputs of various information and data, login information, request instructions, execution instructions, and the like transmitted from the information terminal 20.

[0087] When a user performs an operation to display a list of digital tickets on the application running on the information terminal 20, the display request is sent to the management device 10. The reception processing unit 110 receives the display request. When the display request is received, the control unit 11 refers to the ticket management data 201, extracts the ticket registration data corresponding to the user ID included in the display request, and then obtains information on the ticket ID, ticket name, number of tickets, and purchase date of all digital tickets from the ticket registration data and sends it to the information terminal 20 that made the request.

[0088] Furthermore, when a user selects a specific digital ticket from the digital ticket list screen 42 on the information terminal 20, a request for inquiry about information on the selected ticket is sent to the management device 10. The reception processing unit 110 receives the inquiry request. When the inquiry request is received, the control unit 11 obtains ticket information for the selected ticket from the ticket registration data and sends it to the information terminal 20 that made the request.

[0089] Furthermore, when the user touches the operation unit 434 on the ticket information screen 43A on the information terminal 20, a request for returning the transfer ticket is sent to the management device 10. The reception processing unit 110 receives the return processing request. When the return processing request is received, the control unit 11 performs processing to return the transfer ticket to the transferor, who is the original owner.

[0090] Furthermore, when the user operates the information terminal 20 to input an instruction to proceed to transfer processing, an instruction to proceed to refund processing, or an instruction to execute transfer, these instruction signals are transmitted to the management device 10. The reception processing unit 110 receives these instruction signals.

[0091] The first determination unit 111 performs a process of determining whether the purchased digital ticket designated as a transfer target from the first information terminal 20A (an example of a terminal device of the present invention) of the purchaser who purchased the digital ticket is the set ticket including multiple dependent tickets. This determination process is executed, for example, at the timing when the inquiry request is received.

[0092] In this embodiment, the first determination unit 111 refers to the ticket information (see Figure 4) of the selected ticket that is the subject of the inquiry request, and if the ticket type of the selected ticket is a set type, determines that the selected ticket is the set ticket.

[0093] Furthermore, if no ticket type is registered in the ticket information, the first determination unit 111 may refer to the set content item (see FIG. 4) in the ticket information of the selected ticket to determine whether or not multiple dependent tickets are registered for the selected ticket, and if multiple dependent tickets are registered for the selected ticket, determine that the selected ticket is the set ticket. Furthermore, in this case, the first determination unit 111 may determine whether or not tickets of different types are included among the multiple dependent tickets, and if tickets of different types are included, determine that the selected ticket is the set ticket.

[0094] Here, the types of dependent tickets are distinguished based on, for example, the purpose of the dependent tickets. For example, if both tickets are for boarding a train (for boarding), they can be determined to be the same type of ticket. Also, if one ticket is for boarding and the other is for entering a facility, they can be determined to be different types of tickets. For example, since each dependent ticket included in a digital ticket such as a round-trip ticket or a multiple-ride ticket is for boarding, these dependent tickets are determined to be the same type.

[0095] In this embodiment, the first determination unit 111 determines that the selected ticket is the set ticket when the plurality of dependent tickets includes at least one digital train ticket and at least one digital admission ticket.

[0096] Based on the determination result of the first determination unit 111, the transfer setting unit 116 performs processing to prohibit the individual transfer of the dependent tickets included in the selected ticket and to permit the collective transfer of the selected tickets.

[0097] Specifically, when the first determination unit 111 determines that the selected ticket is the set ticket, the transfer setting unit 116 prohibits the individual transfer of the dependent tickets and allows only the lump-sum transfer of the selected tickets.

[0098] Furthermore, the transfer setting unit 116 permits the transfer of the selected ticket when the first determination unit 111 determines that the selected ticket is not one of the set tickets. In this case, if the selected ticket includes a dependent ticket, the transfer of the dependent ticket is also permitted individually.

[0099] In addition, the permission information indicating whether the bulk transfer or the individual transfer is permitted by the transfer setting unit 116, and the prohibition information indicating whether the transfer is prohibited, are sent together when the ticket information of the selected ticket is sent to the requesting information terminal 20 in response to the inquiry request.

[0100] When the first judgment unit 111 judges that the plurality of dependent tickets included in the selected ticket do not include tickets of different types, the second judgment unit 112 performs processing to judge whether or not the selected ticket has an individual non-transfer setting.

[0101] In this embodiment, the second determination unit 112 refers to the ticket information (see FIG. 4) of the selected ticket that is the subject of the inquiry request and determines whether the transfer setting item of the selected ticket is set to "Yes" or "No." If the transfer setting item is set to "Yes," the second determination unit 112 determines that the selected ticket is individually transferable. On the other hand, if the transfer setting item is set to "No," the second determination unit 112 determines that the selected ticket is individually non-transferable.

[0102] In this case, if the second determination unit 112 determines that the individual transfer prohibition setting is present, the transfer setting unit 116 prohibits the individual transfer of the dependent tickets and allows only the lump-sum transfer of the selected tickets. Note that in the example of Figure 4, "prohibited" is set for ticket types that are set as a set and for round-trip tickets.

[0103] Furthermore, when the second determination unit 112 determines that the individual transfer prohibition setting is not present, the transfer setting unit 116 permits the individual transfer of the dependent tickets and also permits the collective transfer of the selected tickets. In the example of Fig. 4, "permitted" is set for tickets whose ticket type is coupon (ticket).

[0104] When the first determination unit 111 determines that the multiple dependent tickets included in the selected ticket do not include tickets of different types, the third determination unit 113 performs a process of determining whether the multiple dependent tickets are all the same ticket. In other words, when the multiple dependent tickets included in the selected ticket are all the same type, the third determination unit 113 determines whether the multiple dependent tickets are all the same ticket. For example, all dependent tickets included in a multi-ride ticket are determined to be the same ticket. Note that the dependent tickets included in a round-trip ticket are all the same type because they are for boarding, but they are not the same ticket.

[0105] In this case, when the third determination unit 113 determines that the multiple dependent tickets are all the same ticket, the transfer setting unit 116 permits the individual transfer of the dependent tickets and also permits the collective transfer of the selected tickets.

[0106] Furthermore, when the third determination unit 113 determines that the multiple dependent tickets are not all the same ticket, the transfer setting unit 116 prohibits the individual transfer of the dependent tickets and allows only the collective transfer of the selected tickets.

[0107] The expiration date determination unit 115 performs a process of determining whether the number of days remaining until the expiration date of the selected ticket (remaining period) is equal to or greater than a predetermined set period. For example, the expiration date determination unit 115 refers to the ticket information (see FIG. 4) of the selected ticket that is the subject of the inquiry request, calculates the number of days remaining until the end of the validity period based on the current time, and determines whether the number of days remaining is equal to or greater than the first set time.

[0108] In this case, the transfer setting unit 116 allows the transfer of the selected ticket or the dependent ticket if the remaining number of days is equal to or greater than the set period, and prohibits the transfer of the selected ticket or the dependent ticket if the remaining number of days is less than the set period.

[0109] By only allowing the transfer of a digital ticket if there are sufficient remaining days, it is possible to ensure sound transactions between the transferor and the transferee. The set period is set, for example, to a period according to the type of the selected ticket or the type of the dependent tickets. For example, the set period is set longer the more dependent tickets included in the selected ticket, and shorter the fewer dependent tickets included.

[0110] The notification processing unit 117 performs processing to output various information to the information terminal 20. For example, the notification processing unit 117 performs processing to output the permission information indicating permission for transfer by the transfer setting unit 116 or the prohibition information indicating prohibition of transfer to the information terminal 20. In addition, the notification processing unit 117 outputs a completion notification to the information terminal 20 when the transfer or return of the digital ticket performed in response to a request from the information terminal 20 is completed.

[0111] [Ticket transfer processing] 16 and 17, an example of the procedure for ticket transfer processing executed in the management system 100 will be described, along with a description of the ticket transfer method of the present invention. The target of the ticket transfer processing is a purchased digital ticket. In each figure, S11, S12, ... indicate the number (step number) of the processing procedure.

[0112] Note that one or more steps included in the ticket transfer process described below may be omitted as appropriate. Furthermore, the steps in the ticket transfer process may be executed in a different order as long as the same operational effect is achieved. Furthermore, the following description will be given using an example in which a processor corresponding to the control unit 11 or control unit 21 that executes the ticket transfer process executes the processing of each step in the ticket transfer process, but the steps in the ticket transfer process may also be executed in a distributed manner by multiple processors.

[0113] 16, in step S11, the control unit 21 of the information terminal 20 determines whether or not an operation has been performed to select a specific digital ticket from the digital ticket list screen 42. When one digital ticket is selected from the digital ticket list screen 42, the control unit 21 transmits the ticket ID of the selected digital ticket (selected ticket) to the management device 10.

[0114] In step S12, the control unit 11 of the management device 10 determines whether the number of days remaining until the expiration date of the selected ticket (remaining period) is equal to or greater than the predetermined set period. If the number of days remaining is less than the set period, a setting is made to prohibit transfer of the selected ticket (S30). Specifically, the control unit 11 transmits prohibition information indicating the prohibition of transfer of the selected ticket to the information terminal 20 that is the transmission source. At this time, the control unit 11 also transmits ticket information of the selected ticket to the information terminal 20.

[0115] When the information terminal 20 receives the prohibition information and the ticket information, the control unit 21 displays the ticket information screen 43 (see FIG. 7) on the display unit 23A, in which the operation input of the operation unit 432 is invalidated (S31). After that, the series of processes ends.

[0116] If it is determined in step S12 that the remaining number of days is equal to or greater than the set period, the control unit 11 determines whether the selected ticket is the set ticket (S13).

[0117] In step S13, the control unit 11 refers to the ticket information of the selected ticket (see FIG. 4), and if the ticket type of the selected ticket is a set type, determines that the selected ticket is the set ticket. Step S13 is an example of a first determination step of the present invention.

[0118] If it is determined in step S13 that the selected ticket is the set ticket, then in the next step S14, the control unit 11 determines whether all of the dependent tickets included in the selected ticket are unused. If it is determined that all of the dependent tickets are unused, the control unit 11 proceeds to step S28, where it permits the bulk transfer of the selected tickets and prohibits the individual transfer of the dependent tickets (S28). Specifically, the control unit 11 transmits permission information indicating permission for the bulk transfer of the selected tickets and prohibition information indicating prohibition of the transfer of the dependent tickets to the source information terminal 20. At this time, the control unit 11 also transmits ticket information of the selected tickets to the information terminal 20.

[0119] When the information terminal 20 receives the prohibition information, the permission information, and the ticket information, in the next step S29, the control unit 21 displays the ticket information screen 43 (see FIG. 7) on the display unit 23A, where the operation input of the operation unit 432 is validated. Then, the processing from step S41 onward in FIG. 17 is performed.

[0120] If it is determined in step S13 that the selected ticket is not a set ticket, the control unit 11 proceeds to step S21 and performs the processes from step S21 onwards.

[0121] In step S13 described above, the control unit 11 determines whether the selected tickets are set tickets based on the ticket type information registered in the ticket information of the selected tickets (see FIG. 4). However, there may be cases where the ticket type is not registered in the ticket information. In such cases, it is not possible to determine whether the selected tickets are set tickets based on the ticket type information alone. Therefore, in this embodiment, by performing the processes of steps S21 and S22, it is possible to determine whether the selected tickets are set tickets even without the ticket type information.

[0122] In step S21, if the ticket type is not registered in the ticket information, the control unit 11 determines whether the selected ticket has multiple dependent tickets. In other words, the control unit 11 determines whether the selected ticket is made up of multiple dependent tickets.

[0123] Specifically, the control unit 11 refers to the set content item (see FIG. 4) of the ticket information of the selected ticket, and determines whether or not multiple dependent tickets are registered for the selected ticket.

[0124] In step S21, if multiple dependent tickets are not registered, the selected ticket is determined to be a single ticket. In this case, the control unit 11 proceeds to step S25 and determines whether the selected ticket is unused. This determination is made based on the usage status item of the ticket information (see FIG. 4).

[0125] If it is determined in step S25 that the selected ticket (single ticket) is unused, the control unit 11 proceeds to step S26 and performs a setting to permit transfer of the selected ticket (S26). Specifically, the control unit 11 transmits permission information indicating permission for transfer of the selected ticket to the information terminal 20 that is the transmission source. At this time, the control unit 11 also transmits ticket information of the selected ticket to the information terminal 20.

[0126] Thereafter, when the information terminal 20 receives the permission information, in step S29, the control unit 21 displays the ticket information screen 43 (see FIG. 7) on the display unit 23A, where the operation input of the operation unit 432 has been validated. Then, the processing from step S41 onward in FIG. 17 is performed.

[0127] On the other hand, if it is determined in step S25 that the selected ticket (single ticket) has been used, the control unit 11 sets the selected ticket to be prohibited from being transferred (S30), and then the control unit 21 displays the ticket information screen 43 (see Figure 7) on the display unit 23A, with the operation input of the operation unit 432 disabled (S31).

[0128] If it is determined in step S21 that multiple dependent tickets have been registered, then in the next step S22, the control unit 11 determines whether the multiple dependent tickets include tickets of different types. In this embodiment, for example, it is determined whether the multiple dependent tickets include the digital train ticket and the digital admission ticket. Here, if the multiple dependent tickets include tickets of different types, the selected ticket can be determined to be the set ticket. Therefore, in this case, the control unit 11 proceeds to step S14, and processing from step S14 onwards is performed.

[0129] If it is determined in step S22 that the multiple dependent tickets do not include tickets of different types, the control unit 11 determines in the next step S23 whether the selected ticket is individually transferable. Specifically, the control unit 11 references the ticket information of the selected ticket (see FIG. 4) and determines whether the transfer setting item of the selected ticket is set to "Yes" or "No."

[0130] If individual transfer is disabled in step S23, the control unit 11 proceeds to step S14, and the processes from step S14 onward are performed. On the other hand, if individual transfer is disabled, the control unit 11 determines in step S24 whether there are any unused tickets among the multiple dependent tickets. This determination is made based on the usage status item of the ticket information (see FIG. 4).

[0131] If it is determined in step S24 that there is an unused ticket among the multiple dependent tickets of the selected ticket, the control unit 11 proceeds to step S27 and performs settings to permit both the bulk transfer of the selected ticket and the individual transfer of its dependent tickets (S27). Specifically, the control unit 11 transmits permission information permitting the bulk transfer of the selected ticket and the individual transfer of the dependent tickets to the source information terminal 20. At this time, the control unit 11 also transmits ticket information of the selected ticket to the information terminal 20.

[0132] In the information terminal 20, when the permission information and the ticket information are received, in the next step S29, the control unit 21 displays the ticket information screen 43 (see FIG. 7) on the display unit 23A, in which the operation input of the operation unit 432 is validated. Then, the processing from step S41 onwards in FIG. 17 is carried out.

[0133] 17, in step S41, the control unit 21 of the information terminal 20 determines whether or not a transfer instruction has been input. When the operation unit 432 of the ticket information screen 43 is touched by the user, the control unit 21 determines that the transfer instruction has been input.

[0134] When the transfer instruction is input, the next step S42 determines whether the dependent tickets of the selected ticket can be individually transferred. This determination is made based on the permission information or prohibition information sent from the management device 10. Note that if the selected ticket to be transferred is a single ticket, the determination process of step S42 is not performed, and when the transfer instruction is input, the processes from step S43 onwards are performed.

[0135] If it is determined in step S42 that the dependent tickets cannot be individually transferred, then in the next step S43, the control unit 21 displays on the display unit 23A a transfer ticket selection screen 46 (see FIG. 10) that allows only a lump-sum transfer. In this embodiment, if the selected ticket is the set ticket and all dependent tickets are unused, a transfer ticket selection screen 46 (see FIG. 10) that does not have a selection box 466 is displayed on the display unit 23A. Thereafter, input of the number of transfers is accepted on the transfer ticket selection screen 46 (S44), and further input of the user ID of the transferee is accepted (S45). Thereafter, when an execution instruction is entered (S46), the information accepted in steps S44 to S46 and the execution instruction are sent to the management device 10, and the management device 10 executes the transfer process of step S50.

[0136] If it is determined in step S42 that the dependent tickets are individually transferable, then in the next step S47, the control unit 21 displays on the display unit 23A a transfer ticket selection screen 46 (see FIG. 11) that allows both bulk transfer and individual transfer. In this embodiment, if the selected ticket is not a set ticket but, for example, a digital multiple-ride ticket, and if unused dependent tickets remain, the transfer ticket selection screen 46 (see FIG. 11) having a selection box 466 is displayed on the display unit 23A. Thereafter, the transfer ticket selection screen 46 accepts the selection of the dependent tickets to be transferred (S48), and further accepts input of the user ID of the transferee (S45). Thereafter, when an execution instruction is input (S46), the information and execution instruction accepted in steps S48, S45, and S46 are sent to the management device 10, and the management device 10 executes the transfer process of step S50.

[0137] In step S50, the control unit 11 of the management device 10 performs a process to invalidate the ticket information to be transferred from the ticket registration data of the transferor (S51), and also performs a process to register the ticket information to be transferred in the ticket registration data of the transferee (S52).

[0138] When the transfer process (S50) is completed, the control unit 11 transmits a transfer completion notification to the information terminal 20. At this time, the transfer completion notification is transmitted to both the information terminal 20 of the transfer source and the information terminal 20 of the transfer destination.

[0139] Next, another example of the ticket transfer process will be described with reference to Fig. 18. The difference from the above-described ticket transfer process is that step S231 has been added instead of step S23. Note that in the following explanation, only the differences from the above-described ticket transfer process will be explained, and explanations of other common processes will be omitted.

[0140] 18, if it is determined in step S22 that the multiple dependent tickets do not include tickets of different types, the control unit 11 determines in the next step S231 whether the multiple dependent tickets are all the same ticket. The control unit 11 determines whether all tickets are the same by referring to the set content item of the ticket information (see FIG. 4).

[0141] If it is determined in step S132 that all the tickets are the same, the selected tickets can be determined to be digital coupon tickets (for example, digital boarding coupon tickets). In this case, the control unit 11 proceeds to step S24 and performs the processing from step S24 onwards. On the other hand, if it is determined that all the tickets are not the same, the selected ticket can be determined to be a digital ticket having multiple subordinate tickets of the same type, for example, a round-trip ticket. In this case, the control unit 11 proceeds to step S14 and performs the processing from step S14 onwards.

[0142] As explained above, in the management system 100 according to this embodiment, the ticket transfer process described above is performed. For example, if the selected ticket is a set ticket, the dependent tickets cannot be transferred individually and only a lump-sum transfer is possible, provided that all dependent tickets are unused. Furthermore, if the selected ticket is made up of the same dependent tickets, such as a digital coupon ticket, the dependent tickets can be transferred individually, provided that unused dependent tickets remain. Furthermore, if the selected ticket is a single ticket without dependent tickets, transfer is possible, provided that the ticket is unused. Furthermore, if the selected ticket is a digital ticket made up of the same type of dependent tickets (such as a round-trip ticket), only a lump-sum transfer is possible, provided that all dependent tickets are unused.

[0143] Because the ticket transfer process is performed in this manner, it is possible to impose appropriate restrictions on the transfer of the digital ticket depending on the type and specifications of the digital ticket selected as the transfer target.

[0144] In the above-described embodiment, a ticket management system 100 including the management device 10 and the information terminal 20 has been exemplified, but the present invention is not limited to this configuration. For example, all or part of the processing units of the control unit 11 of the management device 10 may be provided in the control unit 21 of the information terminal 20. Furthermore, the present invention can also be understood as a management device 10 (ticket management device) including a control unit 11 including a first determination unit 111, a second determination unit 112, a third determination unit 113, and a transfer setting unit 116.

[0145] [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.

[0146] <Appendix 1> A ticket management system for managing electronic tickets, a first determination unit that determines whether the electronic ticket designated as a transfer target by the terminal device associated with the electronic ticket is a set ticket consisting of a plurality of dependent tickets; a transfer setting unit that prohibits the individual transfer of the dependent tickets and permits the collective transfer of the electronic ticket based on the determination result of the first determination unit; A ticket management system that includes:

[0147] <Appendix 2> The transfer setting unit When the first determination unit determines that the electronic ticket is the set ticket, prohibiting the individual transfer of the dependent tickets and permitting the collective transfer of the electronic ticket; A ticket management system as described in Appendix 1, which allows the transfer of the electronic ticket if the first judgment unit judges that the electronic ticket is not the set ticket.

[0148] <Appendix 3> The ticket management system described in Appendix 1 or 2, wherein the first judgment unit determines whether the electronic ticket includes the multiple dependent tickets, and if the multiple dependent tickets include the multiple dependent tickets, determines whether the multiple dependent tickets include tickets of different types, and if the different types of tickets are included, judges the electronic ticket to be the set ticket.

[0149] <Appendix 4> a second determination unit that, when the first determination unit determines that the plurality of dependent tickets do not include tickets of different types, determines whether the electronic ticket is set to be individually non-transferable; The transfer setting unit prohibiting individual transfer of the dependent tickets and permitting bulk transfer of the electronic ticket when the second determination unit determines that the individual transfer prohibition setting is present; A ticket management system as described in Appendix 3, which allows individual transfer of the dependent tickets and allows bulk transfer of the electronic ticket when the second judgment unit determines that there is no setting that prevents individual transfer.

[0150] <Appendix 5> a third determination unit that, when it is determined by the first determination unit that the plurality of dependent tickets do not include tickets of different types, determines whether the plurality of dependent tickets are all the same ticket; The transfer setting unit When the third determination unit determines that the plurality of dependent tickets are all the same ticket, permitting the individual transfer of the dependent tickets and permitting the collective transfer of the electronic ticket; A ticket management system as described in Appendix 3, which prohibits individual transfer of the dependent tickets and allows bulk transfer of the electronic ticket when the third judgment unit determines that the multiple dependent tickets are not all the same ticket.

[0151] Appendix 6 further comprising an expiration date determination unit that determines whether the remaining period of the expiration date of the electronic ticket is equal to or greater than a predetermined set period; A ticket management system described in any of Appendices 1 to 5, wherein the transfer setting unit allows the transfer of the electronic ticket or the dependent ticket if the remaining period is equal to or greater than the set period, and prohibits the transfer of the electronic ticket or the dependent ticket if the remaining period is less than the set period.

[0152] Appendix 7 A ticket management system according to any one of appendices 1 to 6, wherein the electronic ticket includes at least an electronic ticket for use on public transport as the dependent ticket.

[0153] Appendix 8 the terminal device includes an operation input unit that accepts a selection input of the dependent ticket as a transfer target; A ticket management system according to any one of appendices 1 to 7, wherein the operation input unit is disabled when the individual transfer is prohibited by the transfer setting unit.

[0154] Appendix 9 A ticket management device for managing electronic tickets, a first determination unit that determines whether the electronic ticket designated as a transfer target by the terminal device associated with the electronic ticket is a set ticket consisting of a plurality of dependent tickets; a transfer setting unit that prohibits the individual transfer of the dependent tickets and permits the collective transfer of the electronic ticket based on the determination result of the first determination unit; A ticket management device comprising:

[0155] Appendix 10 A ticket management method for managing electronic tickets, comprising: a first determination step of determining whether the electronic ticket designated as a transfer target from a terminal device associated with the electronic ticket is a set ticket consisting of a plurality of dependent tickets; a transfer setting step of prohibiting individual transfer of the dependent tickets and permitting bulk transfer of the electronic ticket based on the determination result of the first determination step, the ticket management method being executed by one or more processors.

[0156] Appendix 11 A program for managing electronic tickets, a first determination step of determining whether the electronic ticket designated as a transfer target from a terminal device associated with the electronic ticket is a set ticket consisting of a plurality of dependent tickets; A program for causing one or more processors to execute a transfer setting step that prohibits individual transfer of the dependent tickets and allows bulk transfer of the electronic ticket based on the judgment result of the first judgment step, or a non-transitory computer-readable storage medium on which the program is stored. [Explanation of symbols]

[0157] 10: Management device 11: Control section 12: Storage section 13: Communications Department 14:Display section 15:Operation unit 20: Information terminal 21: Control unit 22: Storage section 23: Operation display section 23A: Display section 26: Two-dimensional code reader 27: Imaging unit 28: Communications Department 41:Login screen 42: Digital ticket list screen 43: Ticket information screen 44: Set details screen 45: Information code display screen 46: Transfer ticket selection screen 47: Transfer completion notification screen 100: Ticket management system 100: Management System 110: Reception processing unit 111: 1st judgment part 112:Second judgment part 113: Third judgment part 114: 4th judgment part 115: Expiration date determination section 116: Transfer Setting Section 117: Notification processing unit 200: Ticket sales system 201: Ticket management data 211: Display processing unit 212: Transmission processing unit 213: Operation invalid processing unit

Claims

1. A ticket management system for managing electronic tickets, a first determination unit that determines whether the electronic ticket designated as a transfer target by the terminal device associated with the electronic ticket is a set ticket consisting of a plurality of dependent tickets; a transfer setting unit that prohibits the individual transfer of the dependent tickets and permits the collective transfer of the electronic ticket based on the determination result of the first determination unit; A ticket management system that includes:

2. The transfer setting unit When the first determination unit determines that the electronic ticket is the set ticket, prohibiting the individual transfer of the dependent tickets and permitting the collective transfer of the electronic ticket; The ticket management system according to claim 1 , wherein when the first determination unit determines that the electronic ticket is not the set ticket, transfer of the electronic ticket is permitted.

3. 3. The ticket management system according to claim 1, wherein the first determination unit determines whether the electronic ticket includes the plurality of dependent tickets, and if the plurality of dependent tickets include the plurality of dependent tickets, determines whether the plurality of dependent tickets include tickets of different types, and if the plurality of dependent tickets include tickets of different types, determines the electronic ticket to be the set ticket.

4. a second determination unit that, when the first determination unit determines that the plurality of dependent tickets do not include tickets of different types, determines whether the electronic ticket is set to be individually non-transferable; The transfer setting unit When the second determination unit determines that the individual transfer prohibition setting is present, the individual transfer of the dependent tickets is prohibited and the collective transfer of the electronic ticket is permitted; The ticket management system according to claim 3 , wherein when the second determination unit determines that the individual transfer prohibition setting is not present, the individual transfer of the dependent tickets is permitted and the collective transfer of the electronic ticket is permitted.

5. a third determination unit that, when it is determined by the first determination unit that the plurality of dependent tickets do not include tickets of different types, determines whether the plurality of dependent tickets are all the same ticket; The transfer setting unit When the third determination unit determines that the plurality of dependent tickets are all the same ticket, permitting the individual transfer of the dependent tickets and permitting the collective transfer of the electronic ticket; 4. The ticket management system according to claim 3, wherein when the third determination unit determines that the plurality of dependent tickets are not all the same ticket, the system prohibits the individual transfer of the dependent tickets and permits the collective transfer of the electronic ticket.

6. further comprising an expiration date determination unit that determines whether the remaining period of the expiration date of the electronic ticket is equal to or greater than a predetermined set period; 3. The ticket management system according to claim 1, wherein the transfer setting unit permits the transfer of the electronic ticket or the dependent ticket if the remaining period is equal to or greater than the set period, and prohibits the transfer of the electronic ticket or the dependent ticket if the remaining period is less than the set period.

7. The ticket management system according to claim 1 or 2, wherein the electronic tickets include at least electronic passenger tickets used in transportation facilities as the dependent tickets.

8. the terminal device includes an operation input unit that accepts a selection input of the dependent ticket as a transfer target; The ticket management system according to claim 1 , wherein the operation input unit is disabled when the individual transfer is prohibited by the transfer setting unit.

9. A ticket management device for managing electronic tickets, a first determination unit that determines whether the electronic ticket designated as a transfer target by the terminal device associated with the electronic ticket is a set ticket consisting of a plurality of dependent tickets; a transfer setting unit that prohibits the individual transfer of the dependent tickets and permits the collective transfer of the electronic ticket based on the determination result of the first determination unit; A ticket management device comprising:

10. A ticket management method for managing electronic tickets, comprising: a first determination step of determining whether the electronic ticket designated as a transfer target from a terminal device associated with the electronic ticket is a set ticket consisting of a plurality of dependent tickets; a transfer setting step of prohibiting individual transfer of the dependent tickets and permitting bulk transfer of the electronic ticket based on the determination result of the first determination step, the ticket management method being executed by one or more processors.

11. A program for managing electronic tickets, a first determination step of determining whether the electronic ticket designated as a transfer target from a terminal device associated with the electronic ticket is a set ticket consisting of a plurality of dependent tickets; a transfer setting step of prohibiting individual transfer of the dependent tickets and permitting bulk transfer of the electronic ticket based on the determination result of the first determination step, and a program for causing one or more processors to execute the program.

Images