Ticket processing system, ticket vending machine, ticket management server, ticket processing method, and ticket management program

Abstract

To provide a ticket processing system capable of issuing a real ticket from an issued ticket, a ticket vending machine, a ticket management server, a ticket processing method, and a ticket management program.SOLUTION: A ticket processing system includes a ticket vending machine and a ticket management server. The ticket vending machine includes a first communication unit, a reading unit, a ticket issuing unit, and a first control unit. The first control part requests the ticket management server to exchange a part or all of the ticket information corresponding to the ticket ID read by the reading part for a real ticket, and makes the ticket issuing part issue the real ticket according to a ticket issuing instruction supplied from the ticket management server in response to the request. The ticket management server includes a second communication unit, a storage unit, and a second control unit. The second control unit supplies, to the ticket vending machine, a ticket issuing instruction of a real ticket to be issued in exchange for a part or all of the ticket information corresponding to the ticket ID of the exchange source requested from the ticket vending machine, invalidates ticket information for exchange for the real ticket from the ticket information corresponding to the ticket ID of the exchange source in the storage unit, and registers the ticket information of the real ticket to be issued in exchange in association with a new ticket ID.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a ticket processing system, a ticket vending machine, a ticket management server, a ticket processing method, and a ticket management program. [Background technology]

[0002] Traditionally, railways and other public transport systems have had a system where passengers pass through ticket gates using tickets (physical tickets) purchased from ticket vending machines at stations. In recent years, systems have been proposed that allow passengers to pass through ticket gates using mobile devices that display digital tickets sold on websites. Such digital tickets have the advantage that they can be purchased on websites, etc., and do not require the use of media to issue physical tickets.

[0003] On the other hand, conventional physical tickets have advantages that cannot be obtained with digital tickets displayed on mobile devices, etc. For example, after use, the user can take the physical ticket home as a memento of their trip. While it may be possible to issue a physical ticket with the same printed image as the digital ticket displayed on a mobile device, issuing a physical ticket with the same printed image as the digital ticket could result in both the digital ticket and the physical ticket being used at the same time. For this reason, there is a demand for a system that allows digital tickets to be exchanged for physical tickets without being used fraudulently. [Prior art documents] [Patent documents]

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

[0005] An object of the present invention is to provide a ticket processing system, a ticket vending machine, a ticket management server, a ticket processing method, and a ticket management program that can issue actual tickets from issued tickets. [Means for solving the problem]

[0006] According to an embodiment, the ticket processing system has a ticket vending machine and a ticket management server. The ticket vending machine has a first communication unit, a reading unit, a ticket issuing unit, and a first control unit. The first communication unit communicates with the ticket management server. The reading unit reads the ticket ID of a ticket presented by a user. The ticket issuing unit issues a physical ticket by printing a ticket face image including the ticket ID corresponding to the ticket information. The first control unit requests the ticket management server to exchange some or all of the ticket information corresponding to the ticket ID read by the reading unit for a physical ticket, and causes the ticket issuing unit to issue the physical ticket in accordance with an issuance instruction supplied from the ticket management server in response to the request. The ticket management server has a second communication unit, a memory unit, and a second control unit. The second communication unit communicates with the ticket vending machine. The memory unit stores ticket information associated with the ticket ID. The second control unit supplies the ticket vending machine with an instruction to issue a physical ticket in exchange for part or all of the ticket information corresponding to the ticket ID of the original ticket requested by the ticket vending machine, invalidates the ticket information corresponding to the ticket ID of the original ticket that has been exchanged for a physical ticket in the memory unit, and registers the ticket information of the physical ticket to be issued in exchange in correspondence with a new ticket ID. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram schematically illustrating an example of the configuration of a station service system as a ticket processing system including a ticket vending machine and a ticket management server according to an embodiment. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of a ticket management server in a station service system as a ticket processing system according to an embodiment. [Figure 3] FIG. 3 is a block diagram showing an example of the configuration of a ticket gate in a station service system as a ticket processing system according to an embodiment. [Figure 4] FIG. 4 is a block diagram showing an example of the configuration of a ticket vending machine in a station service system as a ticket processing system according to an embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of a ticket management table managed by the ticket management server according to the embodiment. [Figure 6]FIG. 6 is a diagram illustrating an example of a ticket management table managed by the ticket management server according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a ticket management table managed by the ticket management server according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a ticket management table managed by the ticket management server according to the embodiment. [Figure 9] FIG. 9 is a sequence for explaining an example of the operation of the procedure for issuing a digital ticket that can be used in a station service system as a ticket processing system according to the embodiment. [Figure 10] FIG. 10 is a sequence diagram for explaining the flow of ticket examination processing by a ticket examiner in a station service system as a ticket processing system according to an embodiment. [Figure 11] FIG. 11 is a sequence diagram for explaining an exchange process for exchanging a digital ticket for a physical ticket by a station service system as a ticket processing system according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, the embodiments will be described in detail with reference to the drawings. The station service system as a ticket processing system according to the embodiment is a system that performs station service processes such as ticket gate processing using digital tickets (digital tickets) and physical tickets (physical tickets) issued as passenger tickets (tickets). The digital tickets and physical tickets are assumed to display a code image such as a secondary code indicating a ticket ID, which is identification information for the ticket.

[0009] A digital ticket is a ticket that is displayed as a ticket face image including a code image indicating the ticket ID on the display of a mobile terminal (user terminal) carried by a user. A physical ticket is a ticket that is used as a recording medium on which a ticket face image including a code image indicating the ticket ID is printed. Ticket gate processing is carried out based on ticket information associated with the ticket ID indicated by the code image of the digital ticket or physical ticket presented by the user. The station service system of this embodiment provides a service that allows a user to exchange part or all of a digital ticket for a physical ticket.

[0010] First, the configuration of a station service system 1 as a ticket processing system including a ticket management server 2 and a ticket vending machine 5 according to an embodiment will be described. FIG. 1 is a diagram showing an example of the configuration of a station service system 1 including a ticket management server 2 and a ticket vending machine 5 according to an embodiment. As shown in FIG. 1, the station service system 1 includes a ticket management server 2, a sales server 3, a ticket gate 4, and a ticket vending machine 5. The ticket management server 2 is connected to the ticket gate 4 and the ticket vending machine 5 via a network for station service equipment. The ticket management server 2 is also connected to the sales server 3 via a communication line. The sales server 3 is further connected to a user terminal 6 via a wide area network such as the Internet.

[0011] The ticket management server 2 manages tickets (passenger tickets) using ticket IDs (ticket identification information). Tickets managed by the ticket management server 2 using ticket IDs include digital tickets and physical tickets. Digital tickets display ticket information including a code image indicating the ticket ID managed by the ticket management server 2 on the display of a user terminal 6, such as a mobile terminal such as a smartphone. In other words, digital tickets are provided to the user's mobile terminal 6 as electronic data and are displayed on the display of the mobile terminal 6 by user operation. Physical tickets are media with a ticket face on which ticket information including a code image indicating the ticket ID managed by the ticket management server 2 is printed. Physical tickets are issued by a ticket vending machine 5.

[0012] The ticket management server 2 manages information related to issued tickets. The ticket management server 2 has a ticket management table 24a (see FIG. 2) that stores ticket information in association with a ticket ID that identifies an issued ticket as an issued digital ticket or a physical ticket. By referring to the ticket management table 24a, the ticket management server 2 determines whether the ticket (digital ticket or physical ticket) identified by the ticket ID is allowed to pass in response to a request from the ticket gate 4, and returns the determination result to the ticket gate 4.

[0013] The ticket management server 2 also communicates with the sales server 3 and issues digital tickets to be sold by the sales server 3. For example, the ticket management server 2 issues a ticket ID for a digital ticket whose issuance is requested by the sales server 3, and registers ticket information (ticket information) indicating the contents of the ticket in association with the issued ticket ID in the ticket management table 24a. In this way, the sales server 3 sells digital tickets with the ticket IDs registered in the ticket management table 24a by the ticket management server 2.

[0014] The ticket management server 2 also communicates with the ticket vending machine 5 and issues actual tickets to be issued by the ticket vending machine 5. For example, the ticket management server 2 issues a ticket ID in response to a ticket issuance request from the ticket vending machine 5 and registers ticket information associated with the issued ticket ID in the ticket management table 24a. As a result, the ticket vending machine 5 issues an actual ticket on which a ticket face image including a code image indicating the ticket ID registered in the ticket management table 24a by the ticket management server 2 is printed.

[0015] Furthermore, the ticket management server 2 also has a function to perform processing to exchange an issued digital ticket for a real ticket issued by the ticket vending machine 5. When exchanging a digital ticket for a real ticket, the ticket management server 2 issues a new ticket ID of the real ticket as an exchange ticket to be exchanged based on the digital ticket, registers ticket information of the real ticket as an exchange ticket issued by the ticket vending machine 5 in correspondence with the issued ticket ID, and updates the ticket information corresponding to the ticket ID of the digital ticket that was exchanged so that the part exchanged for the real ticket is invalid.

[0016] The sales server 3 is a server for selling digital tickets. The sales server 3 exists on a wide area network such as the Internet that can be accessed by user terminals 6 operated by general users. For example, the sales server 3 provides a website on the Internet that can be accessed by user terminals 6 that are mobile terminals such as smartphones. In this embodiment, the sales server 3 sells digital tickets on a website that can be accessed by user terminals 6.

[0017] The ticket gate 4 has the function of performing ticket gate processing to control the passage of a user through a ticket gate based on the ticket presented by the user. In this embodiment, the ticket gate 4 performs ticket gate processing based on a digital ticket displaying a code image or a physical ticket on which a code image is printed. The ticket gate 4 reads the code image displayed as a digital ticket or the code image printed on a physical ticket, obtains from the ticket management server 2 a passage determination result based on the ticket ID indicated by the code image, and performs passage control in accordance with the passage determination result from the ticket management server 2.

[0018] The ticket vending machine 5 is a device that has the function of issuing actual tickets (actual tickets). In this embodiment, the ticket vending machine 5 issues actual tickets on which a ticket face image including a code image indicating a ticket ID is printed in response to a user's operation. The ticket vending machine 5 requests the ticket management server 2 to issue a ticket, and issues an actual ticket on which a ticket face image including a code image indicating a ticket ID specified by the ticket management server 2 is printed. The ticket vending machine 5 also has the function of reading a code image indicating an issued ticket ID, and requesting the ticket management server 2 to process the ticket indicated by the read ticket ID.

[0019] The ticket vending machine 5 accepts a process (exchange process) to exchange an issued digital ticket for a physical ticket in response to a user's operation. The ticket vending machine 5 reads the code image of the digital ticket and identifies a physical ticket that can be exchanged for the digital ticket read by the ticket management server 2. The ticket vending machine 5 performs a process to exchange part or all of the digital ticket for a physical ticket to be issued in response to a user's instruction. For example, when a digital ticket valid for one day (one-day pass) is presented, the ticket vending machine 5 issues a physical ticket valid for one day and invalidates the digital ticket. Furthermore, when a digital ticket valid for n days is presented, the ticket vending machine 5 may issue a physical ticket valid for nm (n>m) days and make the digital ticket valid for m days.

[0020] The user terminal 6 is an information processing device operated by a user. The user terminal 6 includes an information processing device (portable terminal) that can be carried by the user, such as a smartphone. The user terminal 6 as a portable terminal is equipped with a display unit that displays a ticket face image as a digital ticket including a code image indicating the ticket. The user uses the ticket gate 4 by presenting the display unit of the user terminal (portable terminal) 6 that displays the ticket face image as a digital ticket. In the following explanation, when using a digital ticket, the user displays the ticket face image including a code image indicating a ticket ID on the display unit of the portable terminal (user terminal) 6 such as a smartphone that the user carries with them, and uses it as a digital ticket.

[0021] Furthermore, the user terminal 6 accesses the sales server 3 via the Internet or the like, and carries out the procedure to purchase a digital ticket that is sold by the sales server 3 and can be used in the station service system 1. Here, the user terminal 6 that accesses the sales server 3 and carries out the procedure to purchase a digital ticket is not limited to a mobile terminal, but may be any information processing device that can be operated by the user. The image of the face of the digital ticket that the user purchased from the sales server 3 may be downloaded to the mobile terminal (user terminal) 6 carried by the user, and displayed on the display unit of the mobile terminal 6.

[0022] Next, the configuration of the ticket management server 2 in the station service system 1 as the ticket processing system according to the embodiment will be described. FIG. 2 is a block diagram showing an example of the configuration of the ticket management server 2 according to the embodiment. In the configuration example shown in FIG. 2, the ticket management server 2 includes a processor 21, a ROM 22, a RAM 23, a storage unit 24, and a communication unit 25. The processor 21 is a computing element (e.g., a CPU) that executes arithmetic processing. The processor 21 performs various processes based on data such as programs stored in the ROM 22 or the storage unit 24. The processor 21 executes the programs stored in the ROM 22 or the storage unit 24, thereby functioning as a processing unit that realizes various processing functions.

[0023] The ROM 22 is a read-only nonvolatile memory that stores programs and data used by the programs. The RAM 23 is a volatile memory that functions as a working memory. The RAM 23 temporarily stores data being processed by the processor 21. The RAM 23 also temporarily stores programs that the processor 21 executes.

[0024] The storage unit 24 is a storage device that serves as a rewritable nonvolatile memory. For example, the storage unit 24 is a solid-state drive (SSD), a hard disk drive (HDD), or another storage device. The storage unit 24 stores, for example, programs and data used by the programs.

[0025] The memory unit 24 also stores a ticket management table 24a for managing tickets. The ticket management table 24a stores information about tickets issued as digital tickets or physical tickets. The ticket management table 24a stores information indicating the validity of each ticket in association with a ticket ID, which is unique identification information assigned to each ticket, whether digital or physical. The ticket management table 24a may be stored in a state accessible to the ticket management server 2, or may be stored in a separate server device with which the ticket management server 2 can communicate.

[0026] The communication unit 25 is an interface for communicating data with each station service device and the sales server. The communication unit 25 includes a network interface for connecting to a network serving as a station service system. The communication unit 25 also includes an interface for communicating with the sales server 3 that provides a web page for selling digital tickets over a network such as the Internet. For example, the communication unit 25 may include a communication interface for communicating with station service devices such as the ticket gate 4 and the ticket vending machine 5, and a communication interface for communicating with the sales server, which is an external device to the station service system.

[0027] Next, the configuration of the ticket gate 4 in the station service system 1 as the ticket processing system according to the embodiment will be described. FIG. 4 is a block diagram showing an example of the configuration of the ticket gate 4 according to the embodiment. The ticket gate 4 is a device that controls the passage of a user according to the ticket (digital ticket or physical ticket) presented by the user. The ticket gate 4, for example, forms a passageway using a pair of housings arranged in parallel, with a door for passage control provided on the passageway side. The ticket gate 4 reads the code image on the digital ticket or physical ticket presented by a user passing through the passageway, and obtains from the ticket management server 2 the determination result as to whether the ticket indicated by the code image is passable or not, thereby controlling the passage of the user.

[0028] 4, the ticket gate 4 has a processor 41, a ROM 42, a RAM 43, a storage unit 44, a communication unit 45, a reading unit 46, a display unit 47, and a passage control unit 48. The processor 41 is connected to the ROM 42, the RAM 43, the storage unit 44, the communication unit 45, the reading unit 46, the display unit 47, and the passage control unit 48 in a communicable state.

[0029] The processor 41 is a computing element (e.g., a CPU) that executes arithmetic processing. The processor 41 performs various processes based on data such as programs stored in the ROM 42 or the storage unit 44. The processor 41 executes the programs stored in the ROM 42 or the storage unit 44, thereby functioning as a processing unit that realizes various processing functions.

[0030] The ROM 42 is a read-only nonvolatile memory that stores programs and data used by the programs. The RAM 43 is a volatile memory that functions as a working memory. The RAM 43 temporarily stores data being processed by the processor 41. The RAM 43 also temporarily stores programs that the processor 41 executes.

[0031] The storage unit 44 is a rewritable non-volatile memory. For example, the storage unit 44 is a storage device such as a solid state drive (SSD) or a hard disk drive (HDD). The storage unit 44 stores programs, data used by the programs, and the like. The communication unit 45 is configured to be connectable to a network serving as the station service system 1. The communication unit 45 includes a communication interface for communicating with the ticket management server 2. For example, the communication unit 45 transmits a request to the ticket management server 2 to determine whether or not a user who has presented a ticket is permitted to pass, and receives the result of the determination on whether or not the user is permitted to pass from the ticket management server. The communication unit 45 may also be configured to communicate with the ticket management server 2 via a monitoring panel that monitors one or more ticket gates installed at ticket gates or the like.

[0032] The reading unit 46 reads the ticket ID of the digital ticket or physical ticket presented by the user. In this embodiment, the reading unit 46 reads the code image of the digital ticket or physical ticket presented by the user. For example, the reading unit 46 includes a camera that optically reads the code image displayed on the display unit of the user terminal (mobile terminal) 6 as a digital ticket or the code image printed on a physical ticket.

[0033] The display unit 47 displays information related to ticket gate processing. The display content of the display unit 47 is controlled by the processor 41. For example, if passage is permitted, the display unit 47 displays information indicating that passage is permitted. The display unit 47 may also display information about the remaining balance available on the ticket medium presented by the user. The passage control unit 48 has an opening / closing function for opening and closing the door provided on the passage side. The passage control unit 48 opens and closes the door in response to an operation command from the processor 41.

[0034] Next, the configuration of the ticket vending machine 5 in the station service system 1 as the ticket processing system according to the embodiment will be described. FIG. 5 is a block diagram showing an example of the configuration of the ticket vending machine 5 in the station service system according to the embodiment. In the configuration example shown in FIG. 5, the ticket vending machine 5 has a processor 51, a ROM 52, a RAM 53, a storage unit 54, a communication unit 55, an operation unit 56, a display unit 57, a reading unit 58, and a payment processing unit 59. The processor 51 is a computing element (e.g., a CPU) that executes arithmetic processing. The processor 51 performs various processes based on programs stored in the ROM 52 or the storage unit 54. The processor 51 executes the programs stored in the ROM 52 or the storage unit 54, thereby functioning as a processing unit that realizes various processing functions.

[0035] The ROM 52 is a read-only nonvolatile memory that stores programs and data used by the programs. The RAM 53 is a volatile memory that functions as a working memory. The RAM 53 temporarily stores data being processed by the processor 51. The RAM 53 also temporarily stores programs that the processor 51 executes.

[0036] The memory unit 54 is a storage device that serves as a rewritable nonvolatile memory. For example, the memory unit 54 is a solid state drive (SSD), a hard disk drive (HDD), or other storage device. The memory unit 54 stores, for example, programs and data used in the programs. For example, the memory unit 54 may store images to be printed on actual tickets issued by the ticket vending machine 5.

[0037] The communication unit 55 is configured to be connectable to a network serving as the station service system 1. The communication unit 45 includes a communication interface for communicating with the ticket management server 2. For example, the communication unit 45 transmits a request to exchange a digital ticket for a physical ticket to the ticket management server 2, and receives from the ticket management server 2 information to be printed on the physical ticket as the exchange result.

[0038] The operation unit 56 generates an operation signal based on the operation of an operation member. The operation member is, for example, a touch sensor, a numeric keypad, or a keyboard. The touch sensor acquires information indicating a designated (touched) position within a certain area. The touch sensor is configured as a touch screen integrated with the display unit 57, and inputs a signal indicating the touched position on the display unit 57 to the processor 51. The display unit 57 displays a screen in accordance with a video signal input from the processor 51 or a display control unit such as a graphics controller (not shown).

[0039] The reading unit 58 reads the ticket ID of the digital ticket or physical ticket presented by the user. In this embodiment, the reading unit 58 reads the ticket ID indicated by the code image of the digital ticket or physical ticket presented by the user. For example, the reading unit 58 includes a camera that optically reads the code image displayed on the display unit of the user terminal (mobile terminal) 6 as a digital ticket or the code image printed on a physical ticket.

[0040] The payment processing unit 59 is a unit that performs payment of fees. For example, the payment processing unit 59 has a cash processing unit that processes cash. The payment processing unit 59 may also be a processing unit for performing payment by credit card or electronic money.

[0041] The ticket issuing unit 60 is a unit for issuing actual tickets. The ticket issuing unit 60 holds a recording medium that serves as an actual ticket, and has a function of printing an image of the ticket face including a code image on the recording medium and issuing the ticket as an actual ticket. For example, the ticket issuing unit 60 not only issues a new actual ticket designated by the user under the control of the processor 51, but also issues an actual ticket (exchange ticket) in exchange for part or all of a digital ticket held by the user.

[0042] Next, a description will be given of the ticket management table 24a used by the ticket management server 2 according to the embodiment to manage issued digital tickets or physical tickets. 5 to 8 are diagrams showing examples of the ticket management table 24a used by the ticket management server 2 according to the embodiment to manage issued digital tickets or physical tickets. The ticket management table 24a shown in Figure 5 stores, in association with the ticket ID, the ticket type, issue date, validity start date, validity period, and multiple exchange flags (exchange flag 1, exchange flag 2, ..., exchange flag n). The ticket ID is identification information for identifying the ticket as a digital ticket (digital ticket) or a physical ticket (physical ticket). The ticket ID is displayed on the ticket as a code image such as a two-dimensional barcode that can be decoded using a predetermined algorithm.

[0043] The issue date indicates the date on which the ticket identified by the ticket ID was issued. The validity start date indicates the date on which the ticket identified by the ticket ID becomes valid. The issue date and the validity start date may be the same or different. The validity period indicates the days (number of days or period, etc.) on which the ticket identified by the ticket ID is valid. In the example shown in Figure 5, the validity period indicates the period from the validity start date.

[0044] The exchange flag is information that indicates the daily validity of a ticket identified by the ticket ID. In the example shown in Figure 5, exchange flag 1 is set with information indicating validity for the first day (day 1) of the validity start date, and exchange flag n is set with information indicating validity for the nth day from the validity start date. Each exchange flag 1, ..., n is set with one of the following information indicating daily validity: "0" indicating validity, "FFh" indicating invalidity because it is outside the validity period, or "1" indicating invalidity because it has already been exchanged.

[0045] As a specific example, the example of ticket management table 24a shown in Figure 5 assumes that the current date and time is "2024 / 1 / 19." Therefore, a ticket with ticket ID "TSB10000101" is a one-day ticket with a validity start date of "2024 / 1 / 19," and only the first day's ticket is valid, as indicated by exchange flag 1. Also, a ticket with ticket ID "TSB10000102" is a four-day ticket with a validity start date of "2024 / 1 / 18," and because the current date and time is 1 / 19, the first day's ticket (2024 / 1 / 18) indicated by exchange flag 1 is invalid, and only the second through fourth days' tickets indicated by exchange flags 2-4 are valid. Furthermore, the ticket with the ticket ID "TSB10000103" is a three-day ticket with a validity start date of "2024 / 1 / 19", which indicates that it is valid from the first day to the third day as indicated by the exchange flag 1-3.

[0046] Next, an example of the ticket management table 24a when a one-day digital ticket is exchanged for a one-day physical ticket will be described. Fig. 6 is a diagram for explaining an example of the ticket management table 24a when a digital ticket is exchanged for a physical one-day ticket. The ticket management table 24a shown in Fig. 6 shows an example when the ticket with ticket ID "TSB10000101" shown in Fig. 5, which is a one-day ticket, is exchanged for a one-day ticket.

[0047] When exchanging the digital ticket with ticket ID "TSB10000101" shown in Fig. 5 for a physical one-day ticket, the ticket management server 2 updates the exchange flag 1 corresponding to ticket ID "TSB10000101" of the digital ticket being exchanged to "1" as shown in Fig. 6. This invalidates the first day (same day) of the ticket with ticket ID "TSB10000101."

[0048] Furthermore, the ticket management server 2 issues the ticket ID "TSB11000101" of the actual ticket to be issued as an exchange ticket. The ticket management server 2 registers the issued ticket with ticket ID "TSB11000101" in the ticket management table 24a as a one-day ticket with a validity start date of "2024 / 1 / 19". In this case, of the exchange flags corresponding to the ticket ID "TSB11000101", only exchange flag 1 is set to "0" (information indicating validity), and the other exchange flags 2 to n are set to "FFh". As a result, the ticket with ticket ID "TSB11000101" can be issued as a one-day ticket valid for the day.

[0049] By updating the ticket management table 24a in the manner described above, a one-day digital ticket can be exchanged for a one-day physical ticket, and the physical ticket can be issued while invalidating the ticket information of the digital ticket that was exchanged.

[0050] Next, an example of the ticket management table 24a when a multi-day digital ticket is exchanged for a one-day physical ticket will be described. The ticket management table 24a shown in FIG. 6 shows an example in which a one-day ticket is exchanged based on the three-day ticket shown in FIG. 5 with ticket ID "TSB10000103." When exchanging the digital ticket with ticket ID "TSB10000103" shown in Fig. 5 for a physical one-day ticket (same-day ticket), the ticket management server 2 updates the exchange flag 1 corresponding to ticket ID "TSB10000103" of the digital ticket being exchanged to "1" (information indicating that the ticket has been exchanged), as shown in Fig. 6. As a result, the first day's ticket of ticket ID "TSB10000103" becomes invalid, and the second and third days' tickets become valid.

[0051] Furthermore, the ticket management server 2 issues the ticket ID "TSB11000103" of the actual ticket to be issued as an exchange ticket. The ticket management server 2 registers the issued ticket with ticket ID "TSB11000103" in the ticket management table 24a as a one-day ticket with a validity start date of "2024 / 1 / 19". In this case, for each exchange flag corresponding to ticket ID "TSB11000103", only exchange flag 1 is set to "0" (information indicating validity), and the other exchange flags 2 to n are set to "FFh". As a result, the ticket with ticket ID "TSB11000103" can be issued as a one-day ticket valid for the day.

[0052] By updating the ticket management table 24a in the manner described above, a digital ticket that is a three-day ticket (multiple-day ticket) can be exchanged for a physical ticket for only one day (exchange period), and a physical one-day ticket can be issued, while the ticket information for one day that has already been exchanged on the digital ticket that was originally exchanged can be invalidated.

[0053] Next, an example of the ticket management table 24a will be described in which a multi-day digital ticket is exchanged for a physical ticket for a partial period (exchange period) out of the multiple days (period) for which the digital ticket is valid. 7 is a diagram illustrating an example of the ticket management table 24a when a digital ticket is exchanged for a physical ticket (multiple-day ticket) whose exchange period is part or all of the validity period of the digital ticket. The ticket management table 24a shown in Fig. 7 shows an example when the four-day ticket with ticket ID "TSB10000102" shown in Fig. 5 is exchanged for a three-day ticket.

[0054] When exchanging the digital ticket with ticket ID "TSB10000102" shown in Fig. 5 for a physical three-day ticket, the ticket management server 2 updates the exchange flags 2, 3, and 4 corresponding to ticket ID "TSB10000102" of the digital ticket being exchanged to "1," as shown in Fig. 7. As a result, the ticket with ticket ID "TSB10000102" becomes a four-day ticket with three days remaining, and the second day (exchange flag 2), third day (exchange flag 3), and fourth day (exchange flag 4) become invalid.

[0055] Furthermore, the ticket management server 2 issues the ticket ID "TSB11000102" of the actual ticket to be issued as an exchange ticket. The ticket management server 2 registers the issued ticket with ticket ID "TSB11000102" in the ticket management table 24a as a three-day ticket with a validity start date of "2024 / 1 / 19". In this case, the exchange flags corresponding to the ticket ID "TSB11000102" are set to "0" (information indicating validity) for exchange flags 1, 2, and 3, and the other exchange flags 4 to n are set to "FFh". As a result, the ticket with ticket ID "TSB11000102" shown in FIG. 7 can be issued as a three-day ticket valid for three days from the current day.

[0056] By updating the ticket management table 24a as shown in Figure 7, a digital ticket that is a 4-day ticket (multi-day ticket) can be exchanged for a physical 3-day ticket, and the physical 3-day ticket can be issued and the ticket information for the 3 days that has already been exchanged on the digital ticket that was originally exchanged can be invalidated.

[0057] Next, an example of the ticket management table 24a when a multi-day digital ticket is exchanged for multiple physical tickets will be described. Fig. 8 is a diagram for explaining an example of the ticket management table 24a when a digital ticket is exchanged for a physical ticket that is a multi-day ticket. The ticket management table 24a shown in Fig. 8 shows an example when the ticket with ticket ID "TSB10000102" which is a 4-day ticket shown in Fig. 5 is exchanged for a 1-day ticket and a 2-day ticket.

[0058] When exchanging the digital ticket with ticket ID "TSB10000102" shown in Fig. 5 for a one-day physical ticket and a two-day physical ticket, the ticket management server 2 updates the exchange flags 2, 3, and 4 corresponding to ticket ID "TSB10000102" of the digital ticket being exchanged to "1," as shown in Fig. 8. As a result, the ticket with ticket ID "TSB10000102" becomes a four-day ticket with three days remaining, and the second day (exchange flag 2), third day (exchange flag 3), and fourth day (exchange flag 4) become invalid.

[0059] Furthermore, the ticket management server 2 issues the ticket ID "TSB11000102" and the ticket ID "TSB12000102" of the actual ticket to be issued as an exchange ticket. The ticket management server 2 registers the issued ticket with the ticket ID "TSB11000102" in the ticket management table 24a as a one-day ticket with a validity start date of "2024 / 1 / 19". The ticket management server 2 also registers the issued ticket with the ticket ID "TSB12000102" in the ticket management table 24a as a two-day ticket with a validity start date of "2024 / 1 / 20".

[0060] As shown in FIG. 8, since the ticket with ticket ID "TSB11000102" is a one-day ticket, the exchange flags corresponding to ticket ID "TSB11000102" are such that exchange flag 1 is set to "0" (information indicating validity) and other exchange flags 3 to n are set to "FFh." Furthermore, since the ticket with ticket ID "TSB12000102" is a two-day ticket, the exchange flags corresponding to ticket ID "TSB12000102" are such that exchange flag 1 and exchange flag 2 are set to "0" (information indicating validity) and other exchange flags 3 to n are set to "FFh." As a result, the ticket with ticket ID "TSB11000102" shown in FIG. 8 can be issued as a one-day ticket for the day, and the ticket with ticket ID "TSB11000102" shown in FIG. 8 can be issued as a two-day ticket valid for two days from 2024 / 1 / 20.

[0061] As described above, by updating the ticket management table 24a as shown in Figure 8, a digital ticket that is a four-day ticket (multi-day ticket) can be exchanged for a one-day actual ticket and a two-day actual ticket, and two actual tickets can be issued and the ticket information for the three days that has already been exchanged on the digital ticket that was originally exchanged can be invalidated.

[0062] Next, an example of the operation of the procedure for issuing a digital ticket that can be used in the station service system 1 as the ticket processing system according to the embodiment will be described. FIG. 9 is a sequence for explaining an example of the operation of the procedure for issuing a digital ticket that can be used in the station service system 1 as the ticket processing system according to the embodiment. The sales server 3 provides a website for selling digital tickets that can be accessed via a network such as the Internet. The sales server 3 sells digital tickets that can be used in the station service system 1 in response to requests from user terminals 6 connected via the network.

[0063] The user uses the user terminal 6 to access a website for selling digital tickets provided by the sales server 3. When the user terminal 6 accesses the website provided by the sales server 3, the display unit displays a digital ticket issuance screen as a web page provided by the sales server 3 for specifying the digital ticket to be purchased (ST11). The user specifies the details of the digital ticket to be purchased, payment information, etc. on the ticket issuance screen displayed on the display unit of the user terminal 6. The user terminal 6 transmits a ticket issuance instruction indicating the ticket issuance details specified by the user to the sales server 3 (ST12).

[0064] The sales server 3 confirms the issuance details of the digital ticket based on the ticket issuance details specified on the user terminal 6 (ST13). Once the issuance details of the digital ticket have been confirmed, the sales server 3 executes a payment process for the issuance amount for issuing the digital ticket (ST14). For example, the sales server 3 issues the issuance amount for the digital ticket based on the payment information specified on the user terminal 6. Once the payment for the issuance amount for the digital ticket has been completed, the sales server 3 accesses the ticket management server 2 and requests the issuance of the digital ticket for which payment has been completed (ST15).

[0065] The ticket management server 2 receives a request for issuing a digital ticket from the sales server 3 via the communication unit 55. Upon receiving the request for issuing a digital ticket, the processor 51 of the ticket management server 2 issues a ticket ID to be assigned to the digital ticket (ST16). The processor 51 of the ticket management server 2 issues a ticket ID that is unique identification information that can uniquely identify the digital ticket. For example, the processor 51 issues a ticket ID such as that shown in the ticket management table 24a illustrated in FIG. 5.

[0066] When the processor 51 of the ticket management server 2 issues a ticket ID, it registers ticket information corresponding to the issued ticket ID and the ticket details of the digital ticket in the ticket management table 24a (ST17). For example, the processor 51 registers information indicating the validity of the digital ticket identified by the ticket ID as ticket information in the ticket management table 24a. For example, when issuing an n-day ticket as a digital ticket, according to the example of Fig. 5, the processor 51 registers the ticket type (n-day ticket), issue date, validity start date, number of valid days (n days), exchange flag for n days, and the like as ticket information in the ticket management table 24a in association with the ticket ID.

[0067] When the processor 51 of the ticket management server 2 completes the registration of the ticket information associated with the ticket ID, it generates a code image indicating the ticket ID (ST18). The processor 51 generates a code image such as a two-dimensional barcode that encodes the ticket ID based on a predetermined standard. Furthermore, when the processor 51 generates the code image indicating the ticket ID, it may also generate a ticket image including the code image to be displayed as a digital ticket on the display unit of the mobile terminal as a digital ticket including the code image.

[0068] When the processor 51 of the ticket management server 2 generates a code image indicating the ticket ID of the issued digital ticket, it transmits a ticket issuance completion notification and the code image (or a ticket face image including the code image) to the sales server 3 that requested the ticket issuance (ST19). The code image indicating the ticket ID may be generated by the sales server 3 or the user terminal 6, and the ticket face image including the code image to be displayed as the digital ticket may also be generated by the sales server 3 or the user terminal 6. In this case, the processor 51 of the ticket management server 2 simply transmits a ticket issuance completion notification and the ticket ID of the issued digital ticket to the sales server 3.

[0069] When the sales server 3 receives the ticket issuance completion notification and the code image from the ticket management server 2, it transmits the received ticket issuance completion notification and the code image to the user terminal 6 that purchased the ticket (ST20). As a result, the mobile terminal serving as the user terminal 6 can obtain the code image or the ticket face image including the code image to be used as the digital ticket purchased from the sales server 3.

[0070] The sales server 3 may also display a notice of ticket issuance completion and access information for acquiring the code image on the web page accessed by the user terminal 6. In this case, the user can use a mobile terminal as the user terminal 6 to acquire the code image of the digital ticket, which can be acquired using the access information presented by the sales server 3. The sales server 3 may also send the code image of the issued digital ticket (or access information for the code image) to a destination, such as an email address, specified by the user. In this case, the user can acquire the code image sent to the specified destination using a mobile terminal as the user terminal 6.

[0071] Next, a description will be given of the ticket examination process by the ticket examiner 4 in the station service system 1 as the ticket processing system according to the embodiment. FIG. 10 is a sequence diagram for explaining the flow of ticket examination processing by the ticket examiner 4 in the station service system 1 as the ticket processing system according to the embodiment. In a standby state, the processor 41 of the ticket gate 4 displays passage guidance on the display unit 47 and accepts ticket gate processing based on a ticket (digital ticket or physical ticket) presented by a user entering the passage.

[0072] A user approaches the passage of the ticket gate 4 and presents the code image of the ticket they hold at a predetermined reading position on the ticket gate 4 (ST31). For example, a user using a digital ticket displays the face image of the digital ticket including the code image on the display of a mobile terminal (user terminal 6) they hold, and presents the code image of the digital ticket at the predetermined reading position. Also, a user using a physical ticket presents the code image printed on the physical ticket they hold at the predetermined reading position.

[0073] The processor 41 of the ticket gate 4 reads, by the reading unit 46, the code image of the digital ticket or physical ticket that a user who has entered the passageway presents at the reading position (ST32). For example, the reading unit 46 extracts a code image of a predetermined format from an image captured by an imaging unit such as a camera, and supplies information obtained by decoding the extracted code image as the reading result to the processor 41. As a result, when the reading unit 46 reads the code image of the ticket that the user presents at the reading position, it supplies information including the ticket ID indicated by the code image to the processor 41 as the reading result.

[0074] When the processor 41 of the ticket gate 4 acquires the result of reading the code image of the ticket, it accesses the ticket management server 2 via the communication unit 45. The processor 41 specifies the ticket ID (ticket ID indicated by the code image) included in the result of reading the code image and inquires of the ticket management server 2 about whether or not the person is permitted to pass through the ticket gate where the ticket gate 4 is installed (ST33).

[0075] The ticket management server 2 accepts inquiries from each ticket gate 4 in the station service system 1 with which it can communicate via the communication unit 55. When the processor 51 of the ticket management server 2 receives an inquiry from the ticket gate 4 to determine whether or not passage is permitted, it determines whether or not passage is permitted through the ticket gate 4 based on the ticket information of the ticket identified by the specified ticket ID (ST34). The processor 51 of the ticket management server 2 identifies the ticket information corresponding to the ticket ID specified by the ticket gate 4 using the ticket management table 24a, and determines whether or not passage through the ticket gate 4 should be permitted based on the ticket information. When the processor 51 of the ticket management server 2 determines whether or not passage is permitted, it notifies the ticket gate 4 that originated the inquiry of the result of the determination of whether or not passage is permitted via the communication unit 55 (ST35).

[0076] The processor 41 of the ticket gate 4 inquires of the ticket management server 2 about whether or not the user is permitted to pass, and then receives the result of the determination of whether or not the user is permitted to pass from the ticket management server 2. When the processor 41 of the ticket gate 4 receives the result of the determination of whether or not the user is permitted to pass from the ticket management server 2, the processor 41 controls the passage of the user based on the result of the determination (ST36). For example, when the processor 41 of the ticket gate 4 receives the determination result of whether or not the user is permitted to pass from the ticket management server 2, the processor 41 allows the user to pass by opening the doors, etc., with the passage control unit 48 to make the passage passable, and displaying a message on the display unit 47 indicating that the user is permitted to pass. On the other hand, when the processor 41 of the ticket gate 4 receives the determination result of whether or not the user is permitted to pass from the ticket management server 2, the processor 41 closes the doors, etc., with the passage control unit 48 to block the passage, and displaying a message on the display unit 47 indicating that the passage is not passable, thereby blocking the user from passing.

[0077] Next, an example of the operation of the exchange process in which part or all of a digital ticket is exchanged for a physical ticket by the station service system 1 as the ticket processing system according to the embodiment will be described. FIG. 11 is a sequence for explaining an example of the operation of the exchange process for exchanging part or all of a digital ticket for a physical ticket by the station service system 1 as the ticket processing system according to the embodiment. In the station service system 1 according to this embodiment, a digital ticket (digital ticket) held by a user can be exchanged for a physical ticket (actual ticket) in part or in whole at the ticket vending machine 5. That is, the ticket vending machine 5 issues a physical ticket in part or in whole from the digital ticket held by the user in response to an operation by the user. The ticket management server 2 also performs processing to validate the physical ticket issued by the ticket vending machine operated by the user as an exchange ticket for part or all of the digital ticket, and invalidate the portion of the digital ticket that was exchanged for a physical ticket.

[0078] First, when a user exchanges part or all of a digital ticket for a physical ticket, the user operates the operation unit 56 of the ticket vending machine 5 to instruct the exchange of the digital ticket for a physical ticket (ST51). For example, when an exchange from a digital ticket to a physical ticket is instructed by the operation unit 56, the processor 51 of the ticket vending machine 5 displays on the display unit 57 a guide to present the code image of the digital ticket to be exchanged at the reading position.

[0079] After issuing an instruction to exchange the digital ticket, the user displays the digital ticket to be exchanged on the display of the portable terminal serving as the user terminal 6 that the user possesses (ST52). After displaying the digital ticket on the display of the portable terminal serving as the user terminal 6, the user presents the code image of the digital ticket displayed on the display of the portable terminal to the reading position of the reading unit 58 of the ticket vending machine 5 (ST53).

[0080] When an instruction to exchange a digital ticket is given via the operation unit 56, the processor 51 of the ticket vending machine 5 reads the ticket ID indicated by the code image of the digital ticket to be exchanged that is presented at the reading position, using the reading unit 58 (ST54). For example, the reading unit 58 extracts a code image from a captured image of the reading position captured by an imaging unit such as a camera, and supplies information obtained by decoding the extracted code image to the processor 51 as the reading result.

[0081] Processor 51 of ticket vending machine 5 obtains the ticket ID indicated by the code image of the digital ticket to be exchanged as the reading result by reading unit 58. Processor 51 of ticket vending machine 5 specifies the ticket ID indicated by the code image of the digital ticket to be exchanged, and sends an inquiry to ticket management server 2 via communication unit 55 asking whether or not part or all of the digital ticket can be exchanged for a physical ticket (ST55).

[0082] The ticket management server 2 receives an inquiry from the ticket vending machine 5 via the communication unit 25 (ST56). The processor 21 of the ticket management server 2 identifies, using the ticket management table 24a, the ticket information corresponding to the ticket ID specified in the inquiry from the ticket vending machine 5. When the processor 21 of the ticket management server 2 identifies the ticket information corresponding to the specified ticket ID, it performs an exchange determination to determine whether or not the ticket can be exchanged for an actual ticket based on the ticket information corresponding to the identified ticket ID (ST56).

[0083] To determine whether or not a ticket can be exchanged, processor 21 of ticket management server 2 determines what kind of actual ticket can be exchanged for based on the ticket information corresponding to the specified ticket ID. That is, processor 21 of ticket management server 2 determines the actual ticket that can be exchanged for (or the exchange period during which the ticket can be exchanged for a real ticket) from the period during which the ticket information corresponding to the specified ticket ID is valid. As a specific example, if the ticket information corresponding to the specified ticket ID is a three-day ticket, processor 21 of ticket management server 2 determines that the ticket for the three days for which the ticket ID is valid can be exchanged for a three-day ticket (three-day ticket), two-day ticket (two-day ticket), or one-day ticket (one-day ticket).

[0084] When the processor 21 of the ticket management server 2 determines whether the actual ticket can be exchanged for the ticket with the specified ticket ID, the processor 21 transmits the result of the exchange determination to the ticket vending machine 5 that made the inquiry via the communication unit 25 (ST57).

[0085] After sending the exchange inquiry, the ticket vending machine 5 receives the result of the exchange determination from the ticket management server 2 via the communication unit 55. When the processor 51 of the ticket vending machine 5 receives the result of the exchange determination for the presented digital ticket, it displays an exchange guide screen based on the result of the exchange determination on the display unit 57 (ST58) and accepts instructions regarding the exchange contents via the operation unit 56 (ST59).

[0086] For example, processor 21 of ticket vending machine 5 displays a selection screen for an exchangeable actual ticket (exchange period during which the ticket can be exchanged for a real ticket) on the exchange guide screen on display unit 57. As a specific example, if a ticket can be exchanged for a 3-day ticket, a 2-day ticket, or a 1-day ticket, processor 21 may display a selection screen on display unit 57 that allows the user to select either a 3-day ticket, a 2-day ticket, or a 1-day ticket as the actual ticket to be issued as an exchange ticket.

[0087] When the exchange information screen is displayed on the display unit 57 of the ticket vending machine 5, the user follows the displayed instructions and indicates the exchange details using the operation unit 56. The user uses the operation unit 56 of the ticket vending machine 5 to specify the actual ticket for which they wish to exchange part or all of the digital ticket they have presented. For example, the user uses the operation unit 56 of the ticket vending machine 5 to specify the exchange period for exchanging the digital ticket they have presented for the actual ticket (the validity period of the actual ticket to be issued as an exchange ticket) from the validity period of the digital ticket they have presented.

[0088] When the exchange details are instructed by the operation unit 56, the processor 51 of the ticket vending machine 5 determines the ticket issuing details (exchange details) of the actual ticket to be issued as an exchange voucher from the presented digital ticket in accordance with the instructions on the operation unit 56 (ST60). After determining the exchange details, the processor 51 transmits an exchange request specifying the exchange details from the digital ticket to the actual ticket via the communication unit 55 to the ticket management server 2 (ST61). For example, the exchange details include information indicating the ticket ID of the digital ticket to be exchanged and the ticket information of the actual ticket to be issued as an exchange voucher.

[0089] The ticket management server 2 receives an exchange request specifying the exchange details from the ticket vending machine 5 via the communication unit 55. The processor 51 of the ticket management server 2 validates the ticket information of the actual ticket to be issued as an exchange ticket based on the received exchange details (ST62). For example, the processor 51 issues a ticket ID for the actual ticket to be issued, and registers the ticket information of the actual ticket to be issued in association with the ticket ID in the ticket management table 24a. As a specific example, when exchanging one day of a three-day digital ticket for a physical ticket, the processor 51 registers the ticket information of the one-day ticket in the ticket management table 24a in association with the ticket ID of the actual ticket to be issued in exchange for the digital ticket in the ticket management table 24a.

[0090] When processor 21 of ticket management server 2 completes the registration of the ticket information of the actual ticket (exchange ticket) in ticket management table 24a, it transmits an issuance instruction indicating the issuance content of the actual ticket as an exchange ticket to ticket vending machine 5 (ST63). Here, processor 21 of ticket management server 2 may generate a code image indicating the ticket ID of the actual ticket and transmit it to ticket vending machine 5 together with the issuance instruction. Note that if the ticket vending machine 5 generates a code image indicating the ticket ID, processor 21 of ticket management server 2 may transmit the ticket ID of the actual ticket together with the issuance instruction.

[0091] The ticket vending machine 5 receives an instruction to issue a real ticket from the ticket management server 2 via the communication unit 55. When the processor 51 of the ticket vending machine 5 receives the instruction to issue a ticket, it generates print data for printing an image of the face of the ticket on the real ticket to be issued in accordance with the instruction (ST64), and issues the real ticket with the generated print data printed on the face of the ticket via the ticket issuing unit 60 (ST65).

[0092] Here, the processor 51 of the ticket vending machine 5 generates a ticket face image to be printed on the face of the actual ticket that will be used as an exchange voucher for the digital ticket presented by the user. For example, the processor 51 of the ticket vending machine 5 generates the ticket face image in a predetermined format. The ticket face image of the actual ticket that will be used as an exchange voucher includes a code image indicating the ticket ID for which a ticket issuance instruction is instructed. The ticket face image of the actual ticket that will be used as an exchange voucher also includes information indicating the contents of the ticket (expiration date, validity period, etc.).

[0093] Furthermore, the processor 51 of the ticket vending machine 5 may include a specific image (original image) in the ticket face image printed on the actual ticket issued as an exchange ticket. The original image (specific image) printed on the actual ticket may be an illustration, mark, symbol, or the like, or may be specific text information.

[0094] For example, the original image printed on the face of the physical ticket may be an image set for each ticket vending machine. In this case, the face of the physical ticket issued as an exchange ticket for a digital ticket will have an original image for each ticket vending machine printed on it. In this manner, if a user wants to obtain a physical ticket with a specific original image printed on it, they can visit a ticket vending machine that prints the desired original image on physical tickets and exchange the digital ticket for the physical ticket. This can motivate users to travel (travel) to a station or other location where a specific ticket vending machine is installed, thereby encouraging users to travel (travel). Furthermore, by providing users with a physical ticket printed with an original image that serves as a special memento for each ticket vending machine, user satisfaction can be improved.

[0095] Furthermore, the original image printed on the face of the physical ticket may be an image set for each station (location). In this case, the face of the physical ticket issued as an exchange ticket for the digital ticket will have an original image printed for each station (location) where the ticket vending machine is installed. In this manner, if a user wants to obtain a physical ticket with a specific original image printed on it, they can visit a station that prints the desired original image on physical tickets and exchange the digital ticket for the physical ticket. As a result, this can motivate users to travel (travel) to stations where physical tickets with specific original images printed on them are issued, thereby encouraging users to travel (travel). Furthermore, it is possible to provide users with physical tickets printed with original images that serve as special mementos for each station, thereby improving user satisfaction.

[0096] Furthermore, the original image printed on the face of the physical ticket may be an image set for each date and time, such as the date and time of issuance. In this case, the face of the physical ticket issued as an exchange ticket for the digital ticket will be printed with an original image set for each date and time of issuance. This type of operation makes it possible to provide physical tickets printed with original images that serve as special mementos for users for each date and time of issuance, thereby improving user satisfaction.

[0097] When the issuing unit 60 has completed issuing of the actual ticket as an exchange ticket, the processor 51 of the ticket vending machine 5 notifies the ticket management server 2 that issuing of the actual ticket has been completed (ST66). The ticket management server 2 receives a notification from the ticket vending machine 5 via the communication unit 25 that the issuance of the physical ticket that it instructed to issue has been completed. Upon receiving the notification of the completion of issuance, the processor 21 of the ticket management server 2 invalidates the ticket information for the exchanged portion of the digital ticket that is the source of exchange for the issued physical ticket (ST67). For example, the processor 51 identifies the ticket ID of the digital ticket that is the source of exchange in the ticket management table 24a, and invalidates the ticket information for the exchanged portion of the ticket information corresponding to that ticket ID. As a specific example, when exchanging one day of a three-day digital ticket for a physical ticket, the processor 51 invalidates the ticket information for one day from the ticket information of that digital ticket in the ticket management table 24a.

[0098] By the above process, a part or all of the digital ticket held by the user can be exchanged for a real ticket issued by a ticket vending machine, and the exchanged digital ticket and real ticket can be managed so that they cannot be used fraudulently.

[0099] The above-described steps of the processes may be interchanged as appropriate. For example, the ticket management server 2 may register the ticket information of the actual ticket (ST62) after receiving a ticket issuance completion notification of the actual ticket from the ticket vending machine 5. Furthermore, the ticket management server 2 may invalidate the exchanged portion of the ticket information corresponding to the ticket ID of the exchange source (ST67) together with registering the ticket information of the actual ticket (ST62) before sending a ticket issuance instruction to the ticket vending machine 5.

[0100] Furthermore, in the above embodiment, it is assumed that a digital ticket is exchanged for a physical ticket, but the source of exchange is not limited to a digital ticket, and it is also possible to issue a physical ticket from one physical ticket as an exchange ticket, as in the above embodiment. For example, it is possible to operate in such a way that a user holding a three-day physical ticket can exchange it at a ticket machine for just one day of the validity period of the three-day physical ticket for another physical ticket (one-day ticket).

[0101] Furthermore, in the above description of the embodiment, the digital ticket and the physical ticket are described as having a code image indicating the ticket ID displayed thereon, but it is sufficient that the ticket gate 4 and the ticket vending machine 5 are capable of reading the ticket ID. In other words, the digital ticket and the physical ticket used in the station service system as a ticket processing system are not limited to those that display or print a code image indicating the ticket ID, but are capable of being read by the ticket gate and the ticket vending machine.

[0102] As described above, the ticket processing system according to the embodiment includes a ticket vending machine that issues physical tickets and a ticket management server that manages ticket information. The ticket vending machine reads a ticket such as an issued digital ticket presented by a user, and exchanges some or all of the read ticket for a physical ticket. In response to a request from the ticket vending machine, the ticket management server invalidates the portion of the ticket information of the ticket that has been exchanged for a physical ticket, and newly registers the ticket information of the physical ticket issued by the ticket vending machine.

[0103] This allows the ticket vending machine to issue a physical ticket by exchanging part or all of the digital ticket presented by the user in accordance with the user's instructions. Furthermore, when part or all of the digital ticket is exchanged for a physical ticket, the ticket management server can manage the exchanged digital ticket and the physical ticket so that they cannot be used fraudulently. As a result, the user can exchange the digital ticket displayed on their mobile device for a physical ticket and take the physical ticket home as a souvenir of their trip.

[0104] The functions described in the above embodiments can be realized not only by hardware but also by software by loading a program describing each function into a computer. Also, each function may be realized by selecting either software or hardware as appropriate.

[0105] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims. [Explanation of symbols]

[0106] 2...ticket management server, 3...sales server, 4...ticket gate, 5...ticket vending machine, 6...user terminal (mobile terminal), 21...processor, 24...memory unit, 25...communication unit, 21...processor, 24...memory unit, 25...communication unit, 41...processor, 44...memory unit, 45...communication unit, 46...reading unit, 47...display unit, 48...passage control unit, 51...processor, 54...memory unit, 55...communication unit, 56...operation unit, 57...display unit, 58...reading unit, 59...payment processing unit, 60...ticket issuing unit.

Claims

1. A ticket processing system having a ticket vending machine and a ticket management server, The ticket vending machine is a first communication unit that communicates with the ticket management server; a reading unit that reads the ticket ID of the ticket presented by the user; a ticket issuing unit that issues a ticket by printing a ticket face image including a ticket ID corresponding to the ticket information; a first control unit that requests the ticket management server to exchange part or all of the ticket information corresponding to the ticket ID read by the reading unit for a real ticket, and causes the ticket issuing unit to issue the real ticket in accordance with an issuance instruction provided by the ticket management server in response to the request; The ticket management server A second communication unit that communicates with the ticket vending machine; a storage unit that stores ticket information associated with a ticket ID; a second control unit that supplies to the ticket vending machine an instruction to issue a real ticket in exchange for part or all of the ticket information corresponding to the ticket ID of the exchange source requested by the ticket vending machine, invalidates the ticket information corresponding to the ticket ID of the exchange source that has been exchanged for a real ticket in the memory unit, and registers the ticket information of the real ticket to be issued in exchange in association with a new ticket ID; Ticket processing system.

2. The reading unit reads a code image indicating the ticket ID, The ticket issuing unit prints a ticket face image including a code image indicating the ticket ID of the actual ticket to be issued. The ticket processing system of claim 1 .

3. The reading unit reads a code image displayed as a digital ticket on a display unit of a user terminal, the first control unit requests the digital ticket to be exchanged for a physical ticket, using the ticket ID indicated by the code image of the digital ticket read by the reading unit as the exchange source; The ticket processing system according to claim 2 .

4. The ticket vending machine further has an operation unit that instructs the exchange contents to be exchanged for a real ticket, The first control unit of the ticket vending machine makes the request in accordance with the exchange content instructed by the operation unit. The ticket processing system according to claim 3 .

5. The first control unit of the ticket vending machine requests the ticket management server to exchange the ticket for a physical ticket within a part of the exchange period indicated by the operation unit from the period during which the ticket information corresponding to the ticket ID read by the reading unit is valid, The second control unit of the ticket management server invalidates the redemption period from the ticket information corresponding to the ticket ID of the redemption source in the storage unit, and sets the ticket information of the actual ticket to be issued as the redemption to ticket information in which the redemption period is valid. The ticket processing system according to claim 4.

6. the first control unit of the ticket vending machine causes a ticket face image including a specific image set in the ticket vending machine to be printed on the actual ticket issued by the ticket issuing unit; The ticket processing system according to claim 5 .

7. The first control unit of the ticket vending machine causes a ticket face image including a specific image set according to a location where the ticket vending machine is installed to be printed on the actual ticket issued by the ticket issuing unit. The ticket processing system according to claim 5 .

8. The first control unit of the ticket vending machine causes a ticket face image including a specific image set according to the ticket issuance date and time to be printed on the actual ticket issued by the ticket issuing unit. The ticket processing system according to claim 5 .

9. A ticket processing system having a ticket vending machine and a ticket management server, The ticket vending machine is a communication unit that communicates with a ticket management server that manages ticket information corresponding to the ticket ID; a ticket issuing unit that issues a ticket on which a ticket face image including a ticket ID is printed; a reading unit that reads the ticket ID of the ticket presented by the user; a first control unit that requests the ticket management server to exchange part or all of the ticket information corresponding to the ticket ID read by the reading unit for a real ticket, and causes the ticket issuing unit to issue the real ticket in accordance with an issuance instruction provided by the ticket management server in response to the request; A ticket vending machine with

10. a communication unit that communicates with a ticket vending machine that issues actual tickets; a storage unit that stores ticket information associated with a ticket ID; a control unit that, in response to a request from the ticket vending machine, supplies the ticket vending machine with an instruction to issue a real ticket in exchange for part or all of the ticket information corresponding to the ticket ID of the exchange source, invalidates the part of the ticket information corresponding to the ticket ID of the exchange source that has been exchanged for a real ticket in the memory unit, and registers the ticket information of the real ticket that the ticket vending machine issues in exchange in association with a new ticket ID; A ticket management server having:

11. A ticket processing method for a ticket processing system having a ticket vending machine and a ticket management server, comprising: The ticket vending machine reads the ticket ID of the presented ticket, a request to the ticket management server to exchange part or all of the ticket information corresponding to the ticket ID read by the ticket vending machine for a real ticket; The ticket vending machine issues a ticket in accordance with an issuance instruction provided by the ticket management server in response to the request; The ticket management server supplies to the ticket vending machine an instruction to issue a real ticket in exchange for part or all of the ticket information corresponding to the ticket ID of the exchange source requested by the ticket vending machine; The ticket management server invalidates the portion of the ticket information corresponding to the ticket ID of the exchange source that has been exchanged for a physical ticket in a storage unit that stores ticket information associated with the ticket ID; The ticket management server registers ticket information of the actual ticket issued in exchange in the storage unit in association with a new ticket ID. Ticket processing method.

12. The ticket management server that communicates with the ticket vending machine that issues the actual tickets receiving a request from the ticket vending machine to exchange some or all of the ticket information corresponding to a specific ticket ID for a physical ticket; In response to a request from the ticket vending machine, supply to the ticket vending machine an instruction to issue a real ticket in exchange for part or all of the ticket information corresponding to the ticket ID of the exchange source; In a storage unit that stores ticket information associated with the ticket ID, invalidating the ticket information corresponding to the ticket ID of the exchange source that has been exchanged for a physical ticket; registering ticket information of the actual ticket issued by the ticket vending machine in exchange in the storage unit in association with a new ticket ID; A ticket management program that executes this.

Images