Ticket management server and ticket management method

Abstract

To provide a ticket management server and a ticket management method which allow other service providers to purchase digital tickets without drastic change on a system.SOLUTION: In a ticket check system, a ticket management server has a ticket check system interface, a communication unit, a memory unit, and a processor. The ticket check system interface communicates with the ticket management server. The communication unit communicates with a server of a service provider system that is different from the ticket check system. The memory unit stores ticket data of a ticket issued by a sever of the ticket check system. The processor generates ticket issuance request data supplied to the server of the ticket check system in response to a ticket issuance request of a ticket to be used in the ticket check system from the server of the service provider system, stores the ticket data of the ticket issued by the server of the ticket check system based on the ticket issuance request in the memory unit, and provides ticket surface data to be displayed as a digital ticket in response to a request for display of the ticket whose ticket data is stored in the memory unit from the server of the service provider system.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] An embodiment of the present invention relates to a ticket management server and a ticket management method. [Background technology]

[0002] In recent years, station service systems have been proposed for railways and other public transport, in which a server acquires ticket information read from a medium presented by a user at a terminal device such as a ticket gate, and the server returns the processing results such as entry and exit determination to the terminal device to perform station service processing. Such station service systems are also called ABT (Account-Based Ticketing) systems.

[0003] The ABT system manages ticket information associated with accounts (IDs) on a server, and issues digital tickets such as two-dimensional codes that can be read by terminal devices such as ticket gates connected to the server, including information about the accounts. The two-dimensional codes used as digital tickets can be used not only when printed on paper, but also when displayed on the display screen of a user device such as a mobile phone. Digital tickets displayed on user devices can be issued online, so they can be issued not only by operators who operate the ABT system, but also by a variety of other service providers.

[0004] However, in order for other operators to issue digital tickets, the conventional ABT system requires major system changes, such as setting up a dedicated interface to connect to the systems of other service operators. Allowing other service operators to issue digital tickets not only improves convenience, but also leads to business expansion for the transportation operators and service operators that operate the ABT system. For this reason, there is a demand for other service operators to be able to provide services, including issuing digital tickets, on the existing ABT system without major system changes. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2017-167612 A Summary of the Invention [Problem to be solved by the invention]

[0006] In order to solve the above problems, an object of the present invention is to provide a ticket management server and a ticket management method that enable digital tickets to be purchased from other service providers without major system modifications. [Means for solving the problem]

[0007] According to an embodiment, the ticket management server has an interface for the ticket gate system, a communication unit, a memory unit, and a processor. The interface for the ticket gate system communicates with a server of the ticket gate system. The communication unit communicates with a server of a service provider system that is different from the ticket gate system. The memory unit stores ticket data of tickets issued by the server of the ticket gate system. The processor generates ticket issuance request data to be supplied to the server of the ticket gate system in response to a ticket issuance request from the server of the service provider system for use in the ticket gate system, stores in the memory unit the ticket data of the tickets issued by the server of the ticket gate system based on the ticket issuance request data, and provides ticket face data to be displayed as a digital ticket in response to a display request from the server of the service provider system for a ticket whose ticket data has been stored in the memory unit. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a digital ticket system having a ticket management server according to an embodiment. [Diagram 2] FIG. 2 is a block diagram illustrating an example of the configuration of the ticket management server according to the embodiment. [Diagram 3] FIG. 3 is a sequence diagram for explaining an example of the operation of a digital ticket issuing process in a digital ticket system having a ticket management server according to an embodiment. [Figure 4]FIG. 4 is a sequence diagram for explaining an example of an operation for displaying a digital ticket in a digital ticket system having a ticket management server according to an embodiment. [Diagram 5] FIG. 5 is a sequence diagram for explaining an example of an operation for displaying a digital ticket having a dynamic code image in a digital ticket system having a ticket management server according to an embodiment. [Figure 6] FIG. 6 is a sequence diagram for explaining an example of processing of performance information related to a digital ticket in a digital ticket system having a ticket management server according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments will be described with reference to the drawings. First, the configuration of a digital ticket system having a ticket management server 7 according to an embodiment will be described. FIG. 1 is a diagram showing an example of the configuration of a digital ticket system including a ticket management server 7 according to an embodiment. As shown in FIG. 1, the digital ticket system is made up of an ABT system 1 as a ticket gate (station service) system, a ticket management server 7, and each service provider system 6 (6A, 6B, 6C).

[0010] The ABT system 1 is operated by a specific transportation business operator. The ABT system 1 manages usage information (ticket information) associated with an account (ID) in the ABT server 2, and issues a digital ticket for identifying the account. The digital ticket is provided as ticket data including the account (ID), and it is sufficient that the ticket gate 3 can read the ticket data from the user terminal that has acquired the ticket data. For example, the digital ticket is a code image such as a two-dimensional code that encodes data including the account. In the following embodiment, the digital ticket is provided as a code image, and the code image is displayed on the display unit of a user terminal carried by the user.

[0011] The ticket management server 7 is provided between the ABT server 2 of the ABT system 1 and each service provider system 6 (6A, 6B, 6C). That is, the ticket management server 7 has a function to communicate with the ABT server 2 and a function to communicate with the server of each service provider system 6. The ticket management server 7 has a function to cause the ABT system 1 to issue digital tickets in response to a request from each service provider system 6, and a function to manage the ticket data of the digital tickets issued by the ABT system and provide it to the service provider.

[0012] For example, the ticket management server 7 accepts requests for issuance of digital tickets for the ABT system 1 from each service provider system 6, and sends an issuance request to the ABT server 2. The ticket management server 7 stores ticket data related to tickets that it has caused the ABT server 2 to issue at the request of each service provider system 6. When the ticket management server 7 receives a request from each service provider system 6 to display an issued ticket, it supplies the service provider system 6 with ticket face data from the stored ticket data for displaying a ticket face image as a digital ticket.

[0013] Each service provider system 6 (6A, 6B, 6C) is a system separate from the ABT system 1. Each service provider system 6 is assumed to be a system operated by an operator (service provider) different from the transportation operator that operates the ABT system 1. For example, the service provider may include a transportation operator different from the transportation operator of the ABT system 1, or may include an operator other than a transportation operator. Furthermore, examples of operators (service providers) other than transportation operators include operators that operate travel agencies, tourist facilities, restaurants, amusement facilities, etc.

[0014] Each service provider system 6 has one or more servers and provides services for users. The service provider system 6 sells services to users who log in using a user terminal. In this embodiment, the service provider system 6 provides services including the sale of digital tickets to be used in the ABT system 1. For example, the service provider system 6 is expected to sell digital tickets for the ABT system 1 to users on the Internet together with the services it provides.

[0015] The service provider system 6 communicates with the ticket management server 7. The service provider system 6 sells digital tickets (digital tickets issued by the ABT server 2) to be used in the ABT system 1 to users via the ticket management server 7. The service provider system 6 also has a function of acquiring from the ticket management server 7 the ticket face data of the issued digital ticket sold to the user via the ticket management server 7, and displaying the ticket face data acquired from the ticket management server 7 as a digital ticket on the user terminal of the user (purchaser).

[0016] In the exemplary configuration shown in FIG. 1, the ABT system 1 is made up of an ABT server 2, a ticket gate 3, a ticket vending machine 4, a ticket vending Web server 5, and the like. The ABT server 2 manages ticket information (usage information) for each account (ID) of an issued digital ticket. The ABT server 2 manages, as ticket information for a digital ticket, information indicating the validity of the digital ticket, such as the validity period and validity area, and information indicating the usage status (entry and exit information, etc.). For example, when the ABT server 2 receives information read from a digital ticket by the ticket gate 3, it determines whether or not the user is allowed to pass through (pass through) the ticket gate 3 based on the ticket information corresponding to the account included in the information read from the digital ticket, and supplies the result of this determination to the ticket gate 3.

[0017] The ticket gate 3 controls the passage (ticket gate) of a user based on a ticket (digital ticket) presented by the user. The ticket gate 3 is installed, for example, at a ticket gate of a station, and performs ticket gate processing such as ticket gate operations (entering a station premises or exiting a station premises) for a user. The ticket gate 3 forms an entrance passage or an exit passage, and executes passage control according to a passenger ticket presented as a ticket by a user passing through the passage.

[0018] The ticket gate 3 has a function of reading a code image of a digital ticket displayed on a display or the like of a user terminal carried by a user. The ticket gate 3 transmits information read from the code image of the digital ticket presented by the user to the ABT server 2. After transmitting the information read from the digital ticket to the ABT server 2, the ticket gate 3 receives a decision result on whether or not the digital ticket can be passed from the ABT server 2, and controls the passage of the user (through the ticket gate) according to the decision result on whether or not the digital ticket can be passed received from the ABT server 2.

[0019] The ABT server 2 also issues tickets in response to ticket issuance request data received from the ticket vending machine 4 or ticket sales Web server 5, and saves and manages ticket information associated with the account of the issued ticket. For example, after the ABT server 2 confirms completion of payment for the ticket requested by the ticket issuance request data, it issues an account (ID) for the ticket to be issued and registers the ticket information in a database provided in the storage device in association with the issuing account. The ABT server 2 also generates a code image readable by the ticket gate 3 that encodes information including the account associated with the ticket information, and provides ticket data including the generated code image to the ticket vending machine 4 or ticket sales Web server 5.

[0020] The ticket vending machine 4 is a device that issues passenger tickets. In this embodiment, the ticket vending machine 4 issues passenger tickets in the form of print media on which a code image such as a two-dimensional code that can be used as a digital ticket is printed. The ticket vending machine 4 is connected to the ABT server 2 via a specially designed interface (ticket vending machine interface). The ticket vending machine 4 sells (issues) passenger tickets by communicating with the ABT server 2 via the ticket vending machine interface.

[0021] In response to a user's operation, the ticket vending machine 4 generates ticket issuance request data for the ticket the user wishes to purchase, and sends the ticket issuance request data to the ABT server 2 via a ticket vending machine interface. The ticket vending machine 4 also executes payment processing (fare payment processing) for the ticket issued based on the ticket issuance request data. Once the payment processing is complete, the ticket vending machine 4 obtains ticket data including a code image to be printed on the face of the ticket from the ABT server 2, and issues the ticket as a printed medium on which an image of the face including the code image is printed.

[0022] The ticket sales Web server 5 is a device that sells digital tickets that can be used in the ABT system (ticket gate system) 1 over a network such as the Internet. The ticket sales Web server 5 is connected to the ABT server 2 of the ABT system 1, and is operated by the transportation company that operates the ABT system 1. In other words, the ticket sales Web server 5 provides a ticket sales site that sells digital tickets over the Internet, and is a device that provides one of the functions of the ABT system 1.

[0023] The ticket sales Web server 5 is connected to the ABT server 2 by a specially designed interface (Web interface). The ticket sales Web server 5 sells (issues) digital tickets by communicating with the ABT server 2 via the Web interface.

[0024] The ticket sales Web server 5 generates ticket issuance request data for the ticket that a user who accesses the server using a user terminal wishes to purchase, and transmits the ticket issuance request data to the ABT server 2. The ticket sales Web server 5 executes the payment process (payment of fees) for the digital ticket issued based on the ticket issuance request data, for example by online payment. Once the payment process is complete, the ticket sales Web server 5 obtains ticket data including a code image as a digital ticket from the ABT server 2, and provides the code image obtained from the ABT server 2 to the user terminal of the user who purchased the digital ticket. This allows the user to display an image of the ticket face including the code image as a digital ticket on the display unit of the user terminal.

[0025] Next, the configuration of the ABT server 2 in the ticket gate system 1 according to the embodiment will be described. FIG. 2 is a block diagram showing an example of the configuration of a control system of the ABT server 2 in the ticket gate system 1 according to the embodiment. As shown in FIG. 2, the ABT server 2 has a processor 21, a ROM (read only memory) 22, a RAM (random access memory) 23, a communication unit 24, a memory unit 25, a virtual ticket vending machine interface (I / F) 26, and a virtual Web interface 27, etc.

[0026] The processor 21 realizes various processing functions by executing programs stored in a memory such as the ROM 22 or the storage unit 25. The processor 21 is, for example, a CPU.

[0027] The ROM 22 is a non-volatile memory in which data is stored in advance. For example, the ROM 22 stores a control program and control data executed by the processor 21. The RAM 23 is a volatile memory that temporarily stores data. For example, the RAM 23 functions as a buffer memory for the control program executed by the processor 21.

[0028] The memory unit 25 is composed of a rewritable non-volatile memory. The memory unit 25 stores various data. The memory unit 25 stores ticket data of a digital ticket issued by the ABT server 2 in response to a request from the service provider system 6. The ticket data stored in the memory unit 25 includes ticket face image data (ticket face data) including a code image to be displayed on the display unit of the user terminal as a digital ticket. The memory unit 25 also stores information (performance information) related to the performance of having the ABT server 2 issue a digital ticket in response to an issuance request from the service provider system 6. For example, the memory unit 25 stores performance information including payment information for the digital tickets issued by the ABT server 2 in response to an issuance request from each service provider system 6, which is compiled for each service provider.

[0029] The communication unit 24 is a communication interface for communicating with service provider systems 6 (6A, 6B, 6C) operated by a transport provider other than the transport provider that operates the ABT system 1. The communication unit 24 is a communication interface for communicating with the service provider systems 6 via a wide area network to which the service provider systems 6 are connected.

[0030] A virtual ticket vending machine interface (I / F) 26 and a virtual Web interface (I / F) 27 are communication interfaces (interfaces for the ticket gate system) for communicating with the ABT server 2 of the ABT system 1 serving as a ticket gate system.

[0031] Virtual ticket machine interface 26 is an interface (communication function) that communicates with ABT server 2 using a communication function similar to that of the interface provided in ticket vending machine 4 in ABT system 1. Virtual ticket machine interface 26 is an interface configured to output data equivalent to the data that ticket vending machine 4 outputs to ABT server 2, and to input data equivalent to the data that ticket vending machine 4 inputs from ABT server 2. In other words, virtual ticket machine interface 26 causes ticket management server 7 to operate as a virtual ticket vending machine connected to the ABT server 2.

[0032] Virtual Web interface 27 is an interface (communication function) that communicates with ABT server 2 using a communication function similar to that of the interface through which ticket sales Web server 5 in ABT system 1 communicates with ABT server 2. Virtual Web interface 27 is an interface configured to output data equivalent to the data that ticket sales Web 6 outputs to ABT server 2, and to input data equivalent to the data that ticket sales Web 6 inputs from ABT server 2. In other words, ticket management server 7 operates as a virtual ticket sales Web server connected to ABT server 2 via virtual Web interface 27.

[0033] However, the virtual web interface 27 presupposes that the ABT server 2 has an interface for the ticket sales web server 5. Therefore, if the ABT system 1 does not have a ticket sales web server 5 that sells digital tickets, the virtual web interface may be omitted.

[0034] In this embodiment, the virtual Web interface 27 is used when the digital ticket has a code image (dynamic code image) that is updated periodically (at each expiration date). A dynamic code image is updated every time a predetermined validity period (display validity period) of about several minutes has elapsed since issuance (or display). In other words, a digital ticket with a dynamic code image is not sold by the ticket vending machine 4 but by the ticket vending Web server 5, because an updated code image must be provided to the user terminal every time the display validity period elapses. Therefore, the virtual Web interface 27 is used when issuing a digital ticket with a dynamic code image.

[0035] Next, the operation of the digital ticket system including the ticket management server 7 according to the embodiment will be described. First, an operation of issuing a digital ticket accepted by the service provider system 6 using the digital ticket system including the ticket management server 7 according to the embodiment will be described. FIG. 3 is a sequence diagram for explaining an example of an operation of the ticket management server 7 according to the embodiment to issue a digital ticket upon request from the service provider system 6. In FIG. Each service provider system 6 can sell to users digital tickets for the ABT system 1. Users can purchase digital tickets for the ABT system 1 from each service provider system 6 that can be used on their own mobile terminals (user terminals) equipped with a display unit, such as smartphones.

[0036] The server of the service provider system 6 accepts an instruction from the user to purchase a digital ticket for the ABT system 1 (step 11). Here, it is assumed that the server of the service provider system 6 sells the digital ticket for the ABT system 1 on a website on a network to which a user terminal can connect. In this case, the user specifies the purchase of a digital ticket for the ABT system 1 on the website provided by the service provider system 6.

[0037] When a user specifies the purchase of a digital ticket for the ABT system 1 on the service provider's website, the server of the service provider's system 6 transmits a ticket issuance request to issue the digital ticket specified by the user to the ticket management server 7 (step ST12). The ticket issuance request includes information indicating the details of the digital ticket desired to be issued (e.g., the section to be used, the period of use, adult / child, seat assignment, etc.).

[0038] The ticket management server 7 receives a request for issuance of a digital ticket for the ABT system 1 from the server of the service provider system 6 via the communication unit 24. When the processor 21 of the ticket management server 7 receives the request for issuance of a digital ticket from the service provider system 6, it generates ticket issuance request data for requesting the ABT server 2 to issue a digital ticket (step ST13). The ticket issuance request data is data indicating the contents of the ticket issuance.

[0039] Here, it is assumed that the request is for issuance of a digital ticket that displays a fixed code image like the one printed by the ticket vending machine 4 on a passenger ticket. In this case, processor 21 of the ticket management server 7 generates ticket issuance request data similar to the ticket issuance request data for the ABT server 2 that the ticket vending machine 4 generates in response to the user's operational instructions. Processor 21 of the ticket management server 7 communicates with the ABT server 2 via virtual ticket vending machine interface 26 as a second communication unit, and transmits the ticket issuance request data to the ABT server 2 (step 14).

[0040] In addition, when issuing a digital ticket with a dynamic code image (when issuing a digital ticket to be sold by the ticket sales Web server 5), the processor 21 of the ticket management server 7 communicates with the ABT server 2 via a virtual Web interface 27 as a second communication unit, and sends ticket issuance request data to the ABT server 2.

[0041] When the ABT server 2 receives the ticket issuance request data sent by the ticket management server 7 via the virtual ticket machine interface, it performs a digital ticket issuance acceptance process based on the ticket issuance content included in the ticket issuance request data (step ST15). The ABT server 2 checks whether a digital ticket can be issued with the ticket issuance content indicated in the ticket issuance request data, and specifies the price of the digital ticket that has been confirmed as issuable. The ABT server 2 sends a payment request to the ticket management server 7 to request payment for the price of the digital ticket that has been confirmed as issuable.

[0042] When the processor 21 of the ticket management server 7 receives a payment request from the ABT server 2 via the virtual ticket machine interface 26, it sends a payment request for the digital ticket to the service provider system 6 that requested the issuance of the digital ticket (step ST17).

[0043] The server of the service provider system 6 performs a payment process in response to a payment request from the ticket management server 7 (step ST18). For example, as the payment process, the server of the service provider system 6 executes an online payment with the user for an amount including the fee for the digital ticket of the ABT system 1. When the server of the service provider system 6 completes the payment process to receive the amount including the fee for the digital ticket from the user, the server of the service provider system 6 notifies the ticket management server 7 of the completion of the payment (step ST19).

[0044] The payment process and the payment procedure are not limited to a specific method. For example, the payment process by the service provider system 6 may be a method determined by the service provider, and the payment of the digital ticket fee to the transportation company of the ABT system 1 may be a method determined in advance between the service provider and the transportation company of the ABT system 1. Here, the service provider executes a payment process to receive an amount including the digital ticket fee from the user, and pays the digital ticket fee out of the amount received from the user to the transportation company that operates the ABT system 1.

[0045] When the processor 21 of the ticket management server 7 receives a notice of completion of payment from the service provider system 6 (step ST19), the processor 21 stores information related to the payment of the digital ticket in the storage unit 25 (step ST20). For example, the processor 21 saves in the storage unit 25 information that associates the service provider that requested the issuance, the issuance content of the digital ticket, the payment content, and the like.

[0046] Furthermore, when the processor 21 of the ticket management server 7 receives a notice of completion of the payment from the service provider system 6, it notifies the ABT server 2 of the completion of the payment for the digital ticket via the virtual ticket vending machine interface 26 (step ST21).

[0047] When the ABT server 2 receives a notification that payment for the ticket issuance details has been completed, it performs a ticket issuance process to issue a digital ticket with the paid ticket issuance details (step ST22). For example, as part of the ticket issuance process, the ABT server 2 issues an account (ID) for the digital ticket to be issued. The ABT server 2 generates a code image, such as a two-dimensional code, that encodes information including the account of the issued digital ticket. The ABT server 2 stores and manages the ticket information (usage information) such as the issued details and the code image in a storage device, in association with the issued account. When the ABT server 2 stores the ticket information corresponding to the account generated in the ticket issuance process in the storage device, it transmits ticket data including the code image of the issued digital ticket to the ticket management server 7 (step ST23).

[0048] The ticket management server 7 receives the ticket data of the digital ticket issued by the ABT server 2 via the virtual ticket machine interface 26. When the processor 21 of the ticket management server 7 receives the ticket data of the digital ticket issued from the ABT server 2, it stores the received ticket data in the memory unit 25 (step ST24). For example, the processor 21 stores the ticket data in the memory unit 25 in association with identification information. The identification information of the ticket data may be information related to the account of the digital ticket, may be a serial number issued separately from the account, or may be information specified by the service provider system 6.

[0049] When processor 21 of ticket management server 7 stores the ticket data of the digital ticket issued by ABT server 2 in memory unit 25, it notifies service provider system 6 of the completion of issuance of the digital ticket (step ST25). Here, processor 21 of ticket management server 7 notifies service provider system 6 of identification information for identifying the ticket data stored in memory unit 25 (digital ticket issued by ABT server 2) together with the issuance completion notification.

[0050] When the server of the service provider system 6 receives a notification of completion of ticket issuance from the ticket management server 7, it notifies the user of the completion of ticket issuance and stores in a storage device information indicating the user who sold the digital ticket (the currently logged-in user) and the identification information of the digital ticket in association with each other. This allows the server of the service provider system 6 to obtain from the ticket management server 7 the face data of the specified digital ticket in response to a display request of the digital ticket specified by the user at any time. As a result, after logging in to the service provider system 6 with the user terminal owned by the user, the user can obtain from the service provider system 6 the face data of the digital ticket that was purchased in the service provider system 6 and managed by the ticket management server 7, and display it on the display unit of the user terminal.

[0051] According to the above operation, when the ticket management server receives a request from the service provider system to issue a digital ticket for use in the ABT system, it generates ticket issuance request data to be sent to the ABT server according to the content of the ticket issuance request. The ticket management server sends the ticket issuance request data generated according to the ticket issuance request to the ABT server, and the ABT server obtains ticket data for the ticket to be issued based on the ticket issuance request data.

[0052] This allows the ticket issuance server to store in the memory unit the ticket data of the ticket that the ABT server has issued in response to an issuance request from the service provider system.As a result, the ticket management server can provide the ticket face data contained in the ticket data of the digital ticket stored in the memory unit to the service provider system as display data for the digital ticket.

[0053] Next, an operation of displaying the digital ticket managed by the ticket management server 7 according to the embodiment on a user terminal connected to the service provider system 6 will be described. FIG. 4 is a sequence diagram for explaining an example of an operation in which the ticket management server 7 according to the embodiment displays a face image of a digital ticket on a user terminal connected to the service provider system 6. In FIG. The server of the service provider system 6 accepts the login of a user who has purchased a digital ticket (step ST31). When a user who has already purchased a digital ticket logs in using a user terminal, the server of the service provider system 6 accepts the designation of a digital ticket for which the logged-in user requests display of ticket face data from among the digital tickets he or she has already purchased (available digital tickets) (step ST32).

[0054] For example, the server of the service provider system 6 displays digital tickets that the logged-in user can use on the display unit of the user terminal, and allows the user to select (designate) the digital ticket that the user wants to use (whose face is to be displayed) from the displayed digital tickets. The server of the service provider system 6 may also accept input of identification information that designates a digital ticket, and identify the digital ticket with the identification information input on the user terminal.

[0055] When a specific digital ticket is specified, the server of the service provider system 6 transmits a display request for the specified digital ticket to the ticket management server 7 (step ST33). The display request for the ticket includes information specifying the digital ticket, such as the identification information (or serial number) of the digital ticket to be displayed.

[0056] The ticket management server 7 receives a display request for a digital ticket from the service provider system 6 via the communication unit 24. When the processor 21 of the ticket management server 7 receives the display request for a ticket from the service provider system 6, it searches for the ticket data of the specified digital ticket from the issued ticket data stored in the memory unit 25.

[0057] When the processor 21 of the ticket management server 7 detects the ticket data of the specified digital ticket, it reads out face data for displaying an image of the face of the ticket including a code image as a digital ticket from the ticket data (step ST34). After reading out the face data, the processor 21 of the ticket management server 7 transmits the read face data via the communication unit 24 to the service provider system 6 that made the display request (step ST35).

[0058] When the server of the service provider system 6 acquires the ticket face data from the ticket management server 7, it supplies the acquired ticket face data to the user terminal of the logged-in user (step ST36). This allows the user to display the ticket face data on the display unit of the user terminal, and the user terminal displaying the ticket face image can be used as a digital ticket. For example, the user presents the ticket face image to the ticket gate 3 with the ticket face image based on the ticket face data displayed on the display unit of the user terminal. The ticket gate 3 performs ticket gate processing in the ABT system 1 by reading the ticket face image as the face of the digital ticket.

[0059] As described above, the ticket management server manages ticket data for digital tickets issued by the ABT server in response to an issuance request from the service provider system. In response to a digital ticket display request from the service provider system that sold the digital ticket for the ABT system, the ticket management server provides the service provider system with ticket face data indicating an image of the ticket face to be displayed as the digital ticket.

[0060] This eliminates the need for the service provider system to manage the ticket data of the ABT system digital ticket after selling it, and allows the service provider system to provide the user with the face data of the digital ticket obtained from the ticket management server upon request from the user. In addition, after purchasing a digital ticket for the ABT system on the service provider system, the user can obtain the purchased digital ticket for the ABT system from the service provider system at any time.

[0061] Next, a second operation example for displaying the digital ticket managed by the ticket management server 7 according to the embodiment on a user terminal connected to the service provider system 6 will be described. FIG. 5 is a sequence for explaining a second operation example in which the ticket management server 7 according to the embodiment provides a face image of a digital ticket to a user terminal connected to the service provider system 6. In the example shown in FIG.

[0062] The server of the service provider system 6 accepts the login of a user who has purchased a digital ticket (step ST41). When a user who has already purchased a digital ticket logs in using a user terminal, the server of the service provider system 6 accepts the designation of a digital ticket for which the logged-in user requests display of ticket face data from among the digital tickets he or she has already purchased (available digital tickets) (step ST42).

[0063] For example, the server of the service provider system 6 displays digital tickets that the logged-in user can use on the display unit of the user terminal, and allows the user to select (designate) the digital ticket that the user wants to use (whose face is to be displayed) from the displayed digital tickets. The server of the service provider system 6 may also accept input of identification information that designates a digital ticket, and identify the digital ticket with the identification information input on the user terminal.

[0064] When a specific digital ticket is specified, the server of the service provider system 6 transmits a display request for the specified digital ticket to the ticket management server 7 (step ST43). The ticket display request includes information specifying the digital ticket, such as the identification information (or serial number) of the digital ticket to be displayed. The ticket management server 7 receives the display request for the digital ticket from the service provider system 6 via the communication unit 24.

[0065] When processor 21 of ticket management server 7 receives a ticket display request from service provider system 6, it searches for ticket data of the specified digital ticket from the issued ticket data stored in memory unit 25. When processor 21 of ticket management server 7 detects the ticket data of the specified digital ticket, it checks whether the specified digital ticket is a digital ticket for which a dynamic code image (a code image that needs to be newly generated) should be displayed.

[0066] Here, it is assumed that the specified (display requested) digital ticket is a digital ticket that displays a dynamic code image. If the specified digital ticket is a fixed code image, the processor 21 of the ticket management server 7 may provide the ticket face data to the service provider system 6 by the operation shown in FIG. 4 described above.

[0067] If the digital ticket requested to be displayed is a dynamic code image, processor 21 of ticket management server 7 sends a request to generate ticket data to ABT server 2, requesting the generation of ticket display data (ticket data) for the ticket face including the code image to be displayed on the digital ticket (step ST44). In this case, processor 21 of ticket management server 7 connects to ABT server 2 via a virtual web interface. This allows ticket management server 7 to operate as a virtual ticket sales web server for ABT server 2, thereby requesting the generation of ticket data for a digital ticket with a dynamic code image.

[0068] When the ABT server 2 receives a request to generate face data from the ticket management server 7, it generates face data including a code image of the digital ticket specified in the generation request (step ST45). For example, the ABT server 2 generates a code image that encodes information including the account and the displayed expiration date of the digital ticket specified in the generation request by the ticket management server 7. When the ABT server 2 generates new face data in response to the generation request, it transmits the generated face data to the ticket management server 7.

[0069] The ticket management server 7 receives the ticket face data generated by the ABT server 2 via the virtual web interface 27. The processor 21 of the ticket management server 7 transmits the ticket face data received from the ABT server 2 to the service provider system 6 that has requested the display (step ST35).

[0070] When the server of the service provider system 6 acquires the ticket face data from the ticket management server 7, it supplies the acquired ticket face data to the user terminal of the logged-in user (step ST36). This allows the user to display the ticket face data including the dynamic code image acquired from the service provider system 6 on the display unit of the user terminal, and the user terminal displaying the ticket face image can be used as a digital ticket.

[0071] Next, a function of the ticket management server 7 according to the embodiment for tallying up information about the digital ticket issued by the ABT server 2 will be described. The processor 21 of the ticket management server 7 has the function of storing information regarding digital tickets issued by the ABT server 2 in response to an issuance request from each service provider system 6 in a memory unit 25, and of aggregating the stored data and providing it to each system.

[0072] FIG. 6 is a sequence diagram for explaining an example of an operation in which the ticket management server 7 according to the embodiment displays a face image of a digital ticket on a user terminal connected to the service provider system 6. In FIG. The processor 21 of the ticket management server 7 stores in the memory unit 25 the contents of the digital ticket issued by the ABT server 2, information regarding the payment of the fee for the issued digital ticket, and the like.

[0073] The processor 21 of the ticket management server 7 generates performance information to be reported to the ABT system 1 based on the information stored in the memory unit 25 (step ST51). The performance information to be reported to the ABT server 2 is, for example, information that compiles information (such as ticket issuance content and payment information) about digital tickets issued by the ABT server 2 in response to ticket issuance requests from each service provider system 6 connected to the ticket management server 7.

[0074] When the processor 21 of the ticket management server 7 generates performance information to be reported to the ABT system 1, it transmits the generated performance information to the ABT server 2 via the virtual ticket machine interface 26 or the virtual Web interface 27 (step ST52). Furthermore, the processor 21 of the ticket management server 7 may transmit the generated performance information to the ABT server 2 at a preset timing for reporting to the ABT system 1, or may transmit the generated performance information to the ABT server in response to an instruction from an administrator.

[0075] This allows the ABT server 2 of the ABT system 1 to collectively obtain from the ticket management server 7 the ticket issuance details and payment information of digital tickets issued in response to ticket issuance requests from a service provider system 6 outside the ABT system 1. As a result, transportation providers of the ABT system 1 can clarify payment information and the like related to tickets issued in response to requests from service providers outside the system without having to tally the data themselves.

[0076] The processor 21 of the ticket management server 7 generates performance information to be reported to each service provider system 6 based on the information stored in the memory unit 25 (step ST52). The performance information to be reported to the service provider system 6 is, for example, information that compiles information (such as ticket issuance content and payment information) about a digital ticket that the service provider system 6 requested the ticket management server 7 to issue and had the ABT server 2 issue it.

[0077] When the processor 21 of the ticket management server 7 generates performance information of a specific service provider system 6 as a report destination, the processor 21 transmits the generated performance information to the service provider system 6 as a report destination via the communication unit 24 (step ST52). The processor 21 of the ticket management server 7 may transmit the generated performance information to the service provider system 6 at a report timing preset for each service provider system 6, or may transmit the performance information to a service provider system 6 designated by an administrator in response to an instruction from the administrator.

[0078] This allows each service provider system 6 to obtain the issuance details and payment information of the digital ticket issued at its request as performance information compiled by the ticket management server 7. As a result, the service provider system 6 can clarify the payment information and the like related to the digital ticket requested to the ticket management server (digital ticket sold to the user) without having to tally it up by itself.

[0079] As described above, when the ticket management server of the embodiment receives a request from the service provider system to issue a digital ticket to be used in the ABT system, it generates ticket issuance request data to be sent to the ABT server according to the contents of the ticket issuance request, and sends the ticket issuance request data to the ABT server. The ticket management server acquires ticket data for the ticket to be issued by the ABT server based on the ticket issuance request data, and stores the acquired ticket data for the issued ticket in a memory unit. In response to a request to display the digital ticket from the service provider system, the ticket management server provides the service provider system with the ticket face data of the digital ticket stored in the memory unit or the ticket face data newly generated by the ABT server.

[0080] This means that even if an ABT system has already been established as an existing ticket gate system, it will be possible to issue and use digital tickets for use in the ABT system sold to users by the service provider system via the ticket management server without making any major changes to the ABT system.

[0081] In addition, the ticket management server of the embodiment is equipped with a virtual ticket machine interface that realizes communication functions equivalent to the interface provided in existing ticket vending machines in the ABT system, which is an existing ticket gate system, and sends ticket issuance request data in response to a ticket issuance request from the service provider system to the ABT server via the virtual ticket machine interface, and obtains ticket data for tickets issued by the ABT server.

[0082] This allows the ABT server of the existing ABT system to receive ticket issuance request data in response to a ticket issuance request from the service provider system using an interface equivalent to that of existing ticket vending machines, making it possible to issue and use tickets sold to users by the service provider system without adding a dedicated interface or making major system changes.

[0083] In addition, the ticket management server of the embodiment is equipped with a virtual web interface that realizes communication functions equivalent to the interface of the existing web server in the ABT system as an existing ticket gate system, and when a digital ticket displaying a dynamic code image is issued, the virtual web interface provides the service provider system with ticket data including the code image generated by the ABT server in response to a display request from the service provider system.

[0084] This allows the service provider system to sell digital tickets with dynamic code images to users without adding a dedicated interface to the ABT system or making major system changes, and each time a user makes a display request, the service provider system can obtain ticket data including a new code image via the ticket management server and provide the user with a digital ticket.

[0085] Although some 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 implemented 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 in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0086] 1...ABT system (ticket gate system), 2...ABT server, 3...ticket gate, 4...ticket vending machine, 5...ticket sales web server, 6 (6A, 6B, 6C)...service provider system, 7...ticket management server, 21...processor, 24...communication unit, 25...memory unit, 26...virtual ticket vending machine interface (interface for ticket gate system), 27...virtual web interface (interface for ticket gate system).

Claims

1. an interface for the ticket gate system for communicating with a server of the ticket gate system; A communication unit that communicates with a server of a service provider system different from the ticket gate system; A storage unit that stores ticket data of tickets issued by the server; a processor that generates ticket issuance request data to be supplied to the server of the ticket gate system in response to a request from the server of the service provider system for issuing a ticket to be used in the ticket gate system, stores in the memory unit ticket data of a ticket issued by the server of the ticket gate system based on the ticket issuance request data, and provides ticket face data to be displayed as a digital ticket in response to a display request from the server of the service provider system for a ticket whose ticket data has been stored in the memory unit; A ticket management server having the above configuration.

2. the ticket gate system interface is an interface for connecting to a server of the ticket gate system as a ticket vending machine, The processor acquires data including image data to be printed on the face of the passenger ticket medium by a ticket vending machine in the ticket gate system as ticket data of a ticket issued by a server of the ticket gate system, and stores in the memory unit ticket face data displaying the image data as the ticket data. The ticket management server according to claim 1.

3. the ticket gate system interface is an interface for connecting to a server of the ticket gate system as a Web server, When the processor receives a ticket display request from the service provider system, the processor requests the server of the ticket gate system to generate ticket face data to be displayed as the digital ticket requested to be displayed, and the server of the ticket gate system provides the generated ticket face data to the service provider system. The ticket management server according to claim 1.

4. The face data to be displayed as the digital ticket is face display data including a code image in which information including the account of the ticket issued by the server of the ticket gate system is encoded. A ticket management server according to any one of claims 1 to 3.

5. A ticket management method by a server that communicates with a server of a ticket gate system and a server of a service provider system different from the ticket gate system, comprising: receiving a request for issuing a ticket to be used in the ticket gate system from a server of the service provider system; generating ticket issuance request data to be supplied to a server of the ticket gate system in response to the ticket issuance request; Transmitting the ticket issuance request data to a server of the ticket gate system; The server of the ticket gate system receives ticket data of the ticket issued based on the ticket issuance request data, The server of the ticket gate system stores ticket data of the ticket issued based on the ticket issuance request data in a storage unit; receiving a display request for the ticket whose data has been stored in the storage unit from the server of the service provider system; providing face data to be displayed as a digital ticket in response to a display request from a server of the service provider system; Ticket management method.

Images