Ticket management server and program

Abstract

To provide a highly convenient ticket management server and a program.SOLUTION: A ticket management server includes a control unit, a database that stores a ticket ID identifying a ticket and a user telephone number in association with each other, and a communication unit that can communicate with a user terminal of a user via a network. The control unit determines whether there is an incoming call from the user telephone number associated with the ticket ID of the ticket to a predetermined ticketing telephone number that can be received by the communication unit, and causes a ticket issuing device to issue the ticket when a determination condition including the condition that there is a call origination from the user telephone number associated with the ticket ID of the ticket to the ticketing telephone number is satisfied.SELECTED DRAWING: Figure 6

Description

Technical Field

[0004] , , , , , , ,

[0006] , , , ,

[0005] , , , , ,<​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​This invention was made to solve the above-mentioned problems and aims to provide an improved ticket management system. [Means for solving the problem]

[0007] To solve the above problems, a ticket management system according to one embodiment of the present invention comprises a control unit, a database that stores ticket IDs and user telephone numbers associated with each other to identify tickets, and a communication unit that can communicate with the user's terminal via a network. The control unit determines whether or not there has been an incoming call from the user telephone number associated with the ticket ID of the ticket to a predetermined ticketing telephone number that can receive calls at the communication unit, and if the determination conditions, including the fact that there has been an incoming call from the user telephone number associated with the ticket ID of the ticket to the ticketing telephone number, are met, the control unit causes the ticketing device to issue a ticket.

[0008] In this invention, the control unit, upon receiving notification from the communication unit that a ticket issuance start operation has been performed on the user terminal, may determine whether or not an incoming call has been received from the user telephone number associated with the ticket ID of the ticket to a predetermined ticket issuance telephone number that can be received by the communication unit.

[0009] In the present invention, the communication unit comprises a network communication unit capable of communicating with the user's terminal and ticketing device via a network, and a telephone communication unit capable of communicating with the user terminal via a telephone line. The control unit, upon receiving notification via the network communication unit that a ticketing start operation has been performed on the user terminal, determines whether, within a predetermined valid operation time after the ticketing start operation has been performed, an incoming call has been received from the user's telephone number associated with the ticket ID of the ticket to a predetermined ticketing telephone number that can receive calls via the telephone communication unit. If the control unit satisfies the determination conditions, including the fact that an incoming call has been received from the user's telephone number associated with the ticket ID of the ticket to the ticketing telephone number within the valid operation time, it sends a command to the ticketing device to issue the ticket.

[0010] In this invention, the communication unit comprises a network communication unit capable of communicating with the user's terminal via a network and a telephone communication unit capable of communicating with the user terminal via a telephone line. The control unit, upon receiving notification from the network communication unit that a ticket issuance start operation has been performed on the user's terminal, determines whether, within a predetermined valid operation time after the ticket issuance start operation, an incoming call has been received from the user's telephone number associated with the ticket ID of the ticket to a predetermined ticket issuance telephone number that can be received by the telephone communication unit. If the determination conditions, including the fact that an incoming call has been received from the user's telephone number associated with the ticket ID of the ticket to the ticket is within the valid operation time, the control unit outputs data-embedded audio containing ticket issuance information for issuing the ticket from the speaker of the user's terminal, and the ticket issuing device issues the ticket based on the data-embedded audio output from the user's terminal. The ticket issuance information embedded in the data-embedded audio may include the printed content of the ticket to be issued.

[0011] In this invention, the data-embedded audio may be transmitted to the user terminal via a voice call over a telephone line. Alternatively, the data-embedded audio may be transmitted to the user terminal via live streaming over a network. Alternatively, the data-embedded audio may be transmitted to the user terminal over a network as an audio data file containing the data-embedded audio.

[0012] In this invention, upon initiating a ticketing operation, identification information is received indicating which of multiple ticketing devices the ticket should be issued from. If the determination conditions are met, the ticketing device corresponding to the received identification information is instructed to print the ticket.

[0013] In the present invention, the ticket management server prompts the user's terminal to access a first site before the ticket issuance start operation, records access history information to the first site on the user's terminal in response to the user's terminal accessing the first site, prompts the user's terminal to access a second site in order to perform the ticket issuance start operation, and obtains access history information to the first site from the user's terminal in response to the user's terminal accessing the second site. The determination conditions in the determination made by the control unit may include whether the access history recorded on the user's terminal when accessing the first site matches the access history obtained from the user's terminal when accessing the second site.

[0014] In the present invention, the ticket management server prompts the user's terminal to access a first site before the ticket issuance start operation, and in response to the user's terminal accessing the first site, it obtains first user agent information from the user's terminal indicating the user agent used to access the first site, prompts the user's terminal to access a second site in order to perform the ticket issuance start operation, and obtains second user agent information indicating the user agent used by the user's terminal to access the second site, and the determination conditions in the determination made by the control unit preferably include the condition that the first user agent information and the second user agent information match.

[0015] A ticket management server according to another embodiment of the present invention comprises a control unit, a database that stores ticket IDs and user telephone numbers associated with each other, a network communication unit that can communicate with the user's terminal via a network, and a telephone communication unit that can communicate with the user's terminal via a telephone line. When the control unit receives a notification via the network communication unit that an operation to initiate owner registration for a ticket has been performed on the user's terminal, it determines whether, within a predetermined valid operation time after the owner registration initiation operation has been performed, an incoming call has been received from the user's telephone number associated with the ticket ID of the ticket to a predetermined registration telephone number that can receive calls via the telephone communication unit. If the determination conditions, including the fact that an incoming call has been received from the user's telephone number associated with the ticket ID of the ticket to the registration telephone number within the valid operation time, are met, the control unit makes the ticket available for use on the user's terminal.

[0016] In this invention, when the owner registration start operation is performed, the registration telephone number is sent to the user's contact information.

[0017] In this invention, multiple candidate telephone numbers are provided as registration telephone numbers, and when the owner registration start operation is performed, one of the multiple candidate telephone numbers is notified to the user's contact person as the registration telephone number.

[0018] In the present invention, the ticket management server prompts the user's terminal to access a first site before the owner registration start operation, records access history information to the first site on the user's terminal in response to the user's terminal accessing the first site, prompts the user's terminal to access a second site in order to perform the owner registration start operation, and obtains access history information to the first site from the user's terminal in response to the user's terminal accessing the second site. The determination conditions in the determination made by the control unit may include whether the access history recorded on the user's terminal when accessing the first site matches the access history obtained from the user's terminal when accessing the second site.

[0019] In the present invention, the ticket management server prompts the user's user terminal to access the first site before the start operation of the owner registration, and in response to the access to the first site by the user terminal, acquires first user agent information indicating the user agent used for the access from the user terminal to the first site, causes the user terminal to access the second site in order to perform the start operation of the owner registration, and acquires second user agent information indicating the user agent used for the access of the user terminal to the second site. It is preferable that the determination condition in the determination performed by the control unit includes that the first user agent information and the second user agent information match.

[0020] In order to solve the above problems, the program according to the embodiment of the present invention may cause a computer to function as any of the above ticket management servers.

Brief Description of the Drawings

[0021] [Figure 1] It is a schematic diagram showing the configuration of the ticket management system 1. [Figure 2] It is a block diagram showing the configuration of the server 2. [Figure 3] It is a block diagram showing the configuration of the ticket issuing device 3. [Figure 4] It is a block diagram showing the configuration of the user terminal 4. [Figure 5] It is a flowchart showing the procedure when receiving a ticket. [Figure 6] It is a flowchart showing the procedure of the owner registration process. [Figure 7] It is a flowchart showing the procedure of electronically using a ticket. [Figure 8] It is a flowchart showing the procedure of issuing a paper ticket. [Figure 9] It is a flowchart showing the procedure of electronically transferring a ticket. [Figure 10] It is a flowchart showing the procedure of issuing a paper ticket in the second embodiment. [Figure 11]This is a flowchart showing the procedure for issuing paper tickets in the third embodiment. [Modes for carrying out the invention]

[0022] Embodiments of the present invention will be described below with reference to the drawings.

[0023] [Basic configuration of the ticket management system] As shown in Figure 1, the ticket management system 1 according to the first embodiment of the present invention consists of a server 2, a plurality of ticketing devices 3, and a plurality of user terminals 4. The server 2, the ticketing devices 3, and the user terminals 4 are connected via a network NW such as the Internet. The server 2 and the user terminals 4 are also connected to a telephone network TL.

[0024] [Server Configuration] Server 2 is, for example, a computer system, and consists of an input / output device such as a keyboard, mouse, and touch panel, a processing unit such as a CPU (Central Processing Unit), a storage device such as RAM (Random Access Memory) and ROM (read-only memory), and a display device such as a CRT (Cathode Ray Tube) or LCD (Liquid Crystal Display).

[0025] As shown in Figure 2, Server 2 comprises at least a storage unit 201, a control unit 202, a network communication unit 203, and a telephone communication unit 204. The storage unit 201 of Server 2 stores programs executed by the control unit 202 and data used by those programs. For example, the storage unit 201 stores programs for realizing the functions of Server 2 in the ticket management system 1, a database DB for electronic tickets managed by the ticket management system 1, and programs for payment processing. Server 2 does not necessarily have to be configured as a single physical unit. For example, some or all of the above components may be distributed to remote locations and can work together to function as Server 2.

[0026] The database (DB) stores information related to electronic tickets, including ticket information (e.g., unique ticket ID, event ID, ticket type, seat number, redemption key, purchaser's user ID, status (used / unused, etc.), ticket image, etc.), user information (e.g., unique user ID, name, age, telephone number (user telephone number), address, gender, other attributes, contact information, etc.), and event information (e.g., event ID, event name, date and time, venue, etc.). In this embodiment, a mobile phone number and contact information are required as user information. This contact information should be a contact method (email address, SNS, etc.) that allows information to be sent and received on the user terminal 4. One ticket ID is associated with one user ID and one event ID, so that by identifying the ticket ID, information about the user who purchased the ticket and information about the event that can be entered with that ticket can be identified. If one user purchases multiple tickets for the same event, multiple ticket IDs associated with the same event ID will be linked to that single ticket ID.

[0027] The control unit 202 of server 2 executes processing according to the program stored in the storage unit 201 based on requests sent from the user terminal 4. For example, the control unit 202 performs processes such as searching for, adding, deleting, and updating data in the database DB stored in the storage unit 201, and communicates with the ticketing device 3, user terminal 4, etc. via the network communication unit 203 and the network NW. The control unit 202 also controls the telephone communication unit 204 to obtain the incoming telephone number and transmit necessary voice messages over the telephone line.

[0028] [Configuration of the ticketing device] The ticketing device 3 prints ticket information on a predetermined form and issues it based on a command from the server 2. As shown in Figure 3, the ticketing device 3 includes at least a storage unit 301, a control unit 302, a communication unit 303, a printing unit 304, a display unit 305, a microphone 306, and a camera 307.

[0029] The memory unit 301 stores programs executed by the control unit 302, as well as data used by those programs. For example, the memory unit 301 stores programs that control the printing unit 304 to print ticket information based on commands from the server 2, and programs that control the display unit 305 to display the ticket machine number and various screens based on commands from the server 2. In a ticket management system 1 equipped with multiple ticketing devices 3, each ticketing device 3 is assigned a ticketing device number to identify it, and each ticketing device 3 stores its own ticketing device number in the control unit 302. The ticketing device number may also be a ticketing telephone number individually assigned to each ticketing device 3.

[0030] The control unit 302 executes various programs stored in the memory unit 301. For example, the control unit 302 controls the printing unit 304 to print tickets in response to commands from the server 2, or controls the display content of the display unit 305.

[0031] The communication unit 303 communicates with the server 2 via the network NW. The communication unit 303 may also be configured to enable near-field communication (NFC), infrared communication, visible light communication, etc. The printing unit 304 is a printer that prints tickets on predetermined paper. The ticket paper may be, for example, pre-cut to predetermined dimensions and perforated as needed, or it may be roll paper that is cut to a predetermined length each time printing is required.

[0032] The display unit 305 is a display element such as a liquid crystal display and displays the ticket machine number, which is an identification number for identifying the ticketing device 3, as well as various notifications and guidance screens. The ticket machine number may be displayed on a label or the like, printed with the ticket machine number, instead of on the display unit 305, or in conjunction with the display unit 305. The microphone 306 accepts voice input.

[0033] [User terminal configuration] The user terminal 4 is, for example, a tablet or smartphone, and is equipped with a touch panel, a processing unit such as a CPU, a storage device such as RAM or ROM, a display device such as an LCD, a speaker for outputting sound, a microphone for collecting sound, and so on.

[0034] As shown in Figure 4, the user terminal 4 comprises at least an operation unit 401, a storage unit 402, a control unit 403, a communication unit 404, a display unit 405, a microphone 406, and a speaker 407.

[0035] The operation unit 401 receives operations from the user. The operation unit 401 includes a touch panel superimposed on the display unit 405 and other buttons. The storage unit 402 stores programs executed by the control unit 403 and data used by those programs. For example, the storage unit 402 stores the operating system (OS), application programs for the ticket management system 1, data on purchased electronic tickets used by these application programs, and user information.

[0036] A dedicated application software may be used as the application program for using the ticket management system 1, but a more general-purpose browser or messenger application may also be used. When using a browser or messenger application (hereinafter referred to as "browser, etc."), it is preferable to configure the system so that the user terminal 4 uses the browser, etc. to access the server 2 and retrieves and displays data related to the purchased electronic ticket from the database DB on the server 2 as needed. In the embodiments described below, the system will be described assuming that a browser, etc. is used as the application program for using the ticket management system 1.

[0037] The control unit 403 executes various programs, including a browser, stored in the memory unit 402. The browser accesses a specified URL to display a website, and, as will be described in detail later, performs processing based on various data stored in the memory unit 402 and operations performed by the operation unit 401.

[0038] The communication unit 404 communicates with server 2 via the network NW. The communication unit 404 also performs voice calls using the telephone network TL. Note that the network NW and the telephone network TL may be the same.

[0039] The display unit 405 is a display element such as a liquid crystal display, and under the control of the control unit 403, it displays various information (the face of an electronic ticket). The display unit 405 works in cooperation with the touch panel of the operation unit 401 to realize various input interfaces.

[0040] [Basic operation of the ticket management system] This section explains the basic process of a user purchasing and using a ticket using the ticket management system 1 configured as described above.

[0041] [Purchasing and receiving tickets] Users purchase tickets for their desired event from ticket vendors (e.g., ticket shops, ticket terminals, online ticketing sites, etc.). At this time, users select various conditions such as the event, seat type, number of seats, and ticket delivery method, and then proceed with the payment process. If electronic tickets are selected as the ticket delivery method, users will use the ticket management system via their mobile device. The following flowchart, shown in Figure 5, explains the ticket delivery process when electronic tickets are selected.

[0042] Once payment for the purchased ticket is completed, the ticket seller sends the ticket ID of the purchased ticket and the user ID of the user who purchased the ticket to server 2, which receives them (step S100). Server 2 then records the user ID received from the seller as the user ID of the purchaser associated with the ticket ID received from the seller (step S110). Server 2 also sends a receiving URL for the user to receive the purchased ticket on the user terminal 4 to the contact information (email address, SNS account, etc.) associated with the purchaser's user ID (step S120). The system may also be configured to require the input of a ticketing number, phone number, etc., before the ticket can be received. Access to this receiving URL is managed by server 2.

[0043] The user receives the ticket by accessing the receiving URL sent from server 2 in step S120 using the browser on user terminal 4 (step S130). This allows the user to use the ticket using the browser on user terminal 4. At this time, predetermined identification information is recorded as history information (so-called cookie) indicating that the receiving URL was accessed in the browser on user terminal 4 used to access the receiving URL. Server 2 records the purchaser's user ID and the cookie in association. In addition, server 2 records information about the user agent (hereinafter referred to as "UA information") indicating the model, browser, OS, etc. of user terminal 4 that accessed the receiving URL, in association with the purchaser's user ID.

[0044] In the ticket management system of this embodiment, tickets that have not been registered with their owner will not be usable. Therefore, users who purchase tickets must register their ownership using the procedure described below.

[0045] [Owner Registration] Figure 6 is a flowchart showing the procedure for the owner registration process. When a user uses user terminal 4 to launch a browser or the like and access the ticket management system site, the performances for which tickets have already been purchased are displayed for selection (step S200). If the user selects a desired ticket from these, and the ticket owner registration has not been completed, the ticket image and an owner registration screen for registering the ticket are displayed (step S210). Access to this owner registration screen is managed by server 2. The user accesses the displayed owner registration screen. At this time, user terminal 4 sends UA information of the browser used for access and cookie information left in the browser when accessing the receiving URL to receive the ticket to server 2 (step S220). In addition, server 2 notifies the user of the registration telephone number in response to the access to the owner registration screen (step S230). The method of notifying the user may be to send the registration telephone number to the user's contact information, or to display it on a web page that the user can view using user terminal, etc. This registration phone number can be a landline number, but it may also be possible to select one number from several candidate numbers and send it, so that a different number is displayed each time.

[0046] Next, the user terminal 4 displays an authentication button on the display unit 405 to start the owner registration process (step S235). When the user presses the authentication button, the server 2 records the time of pressing the button and associates it with the ticket ID (step S240). Authentication button B1 is an example of the owner registration start operation in this invention. The user terminal 4 also displays the registration telephone number received in step S220 in response to the authentication button being pressed (step S245). Alternatively, instead of sending the registration telephone number from the server 2 to the user terminal 4 in step S230, the registration telephone number may be sent from the server 2 to the user terminal 4 in response to the authentication button being pressed and displayed on the display unit 405.

[0047] Next, Server 2 determines whether a call was made to the registered telephone number from the phone number associated with the ticket (usually User Terminal 4) within a predetermined valid operation time (for example, within 4 seconds) from the time of pressing the button (Step S250). This valid operation time should be short enough that it would be difficult for a third party in a remote location to make a call by providing the ticketing telephone number and performing the call on their behalf.

[0048] In step S250, Server 2 determines whether a call was made to the registered telephone number from the user telephone number associated with the ticket (usually the user terminal 4) within a predetermined valid operation time (for example, within 4 seconds) from the time of pressing, as follows: Server 2 receives the call to the registered telephone number via the telephone communication unit 204. The telephone communication unit 204 then identifies the originating telephone number and the telephone number to which the call was made (one of the candidate telephone numbers). Server 2 identifies the ticket ID based on the telephone number to which the call was made and determines whether a call was made to the registered telephone number within the valid operation time by checking whether the ticket ID is a ticket ID whose pressing time was recorded within the period preceding the valid operation time from the time of receiving the call.

[0049] If a call is not made to the registered telephone number within the valid operation time from the time of pressing the button (step S250; No), the owner registration will not be completed, and a screen notifying the user that owner registration could not be completed will be displayed on the display unit 405 of the user terminal 4 (step S260), and the owner registration process will end. It is also advisable to configure the system to notify the user if an input error is suspected, such as when the originating telephone number differs by only one character from the user telephone number recorded linked to the ticket, or when the first character is missing. In this way, the user will easily realize that they have registered the wrong telephone number and will be prompted to correct it.

[0050] On the other hand, if a call is made to the registered telephone number within the valid operation time from the time of pressing the button (step S250; Yes), Server 2 performs a verification process (step S270). In the verification process, the purchaser's telephone number associated with the ticket ID is extracted from the database DB and verified against the number that was called in step S250. In addition, Server 2 verifies the cookie information and UA information recorded when the purchaser accessed the receiving URL associated with the user ID against the cookie information and UA information sent from the user terminal 4 in step S220. If the verification process does not confirm a match between the pieces of information (step S270; No), the owner registration is not performed, and a screen notifying the user that owner registration could not be performed is displayed on the user terminal 4 (step S260), and the owner registration process ends. On the other hand, if the verification process confirms a match between the pieces of information (step S270; Yes), Server 2 records in the database DB that owner registration for the ticket has been completed and makes the ticket available for use on the user terminal 4 (step S280). From now on, when a user launches a browser or similar application on terminal 4 and accesses the ticket management system website to view the ticket, the ticket will be displayed in an available state.

[0051] According to the owner registration process described above, tickets cannot be used unless the person who purchased them registers them as the owner, thus deterring fraudulent transfers and resales. [Use of electronic tickets]

[0052] As described above, electronic tickets managed by ticket management system 1 become usable after owner registration. As explained below, tickets can be used electronically or by issuing and using paper tickets.

[0053] Figure 7 is a flowchart illustrating an example of the processing procedure of the ticket management system 1 when a ticket that has been registered by the owner is used electronically (i.e., displayed on the user terminal 4 without issuing a paper ticket). The user, having already completed the owner registration described above, launches the browser on the user terminal 4 and accesses the ticket URL to display the electronic ticket, thereby displaying the ticket on the display unit 405 of the user terminal 4 (step S300), and presenting it to the staff at the entrance. Access to the ticket URL is managed by the server 2. When the user terminal 4 accesses the ticket URL, it sends the UA information of the browser used for access and the cookie information left in the browser when it accessed the receiving URL to receive the ticket to the server 2.

[0054] The staff member visually confirms that the electronic ticket for the event in question is for that event, and then performs a "cancellation" operation to mark the ticket as used (for example, by performing a prescribed operation on the touch panel of the user terminal 4) (step S310). When the user terminal 4 receives the cancellation operation, it overlays text or an image indicating that the ticket has been used (hereinafter referred to as "postmark information") onto the ticket and sets the status of the ticket to "used" (step S320). The user terminal 4 also notifies the server 2 that the ticket has been used at an appropriate time (it may be immediately after verification or after some time has passed), and the server 2 also sets the status of the ticket to "used" (step S330) and terminates the process. It is recommended that the user terminal 4, upon receiving the cancellation operation, verify whether the cancellation operation is correct, and only mark the ticket as used if it is correct, and issue a warning or notification if it is incorrect. In addition to verifying the redemption operation, the Cookie information and UA information transmitted from the user terminal 4 in conjunction with step S300 may also be verified against the Cookie information and UA information recorded in association with the user ID of the ticket holder. In the above example, redemption was performed by accepting a redemption operation from the user terminal 4, but redemption may be performed by other methods. For example, the display unit 405 of the user terminal 4 may display an identification code (e.g., a QR code (registered trademark), etc.) along with the ticket image, and this may be read at the entrance and verified with the server 2, so that the server 2 performs the redemption process.

[0055] [Issuance of paper tickets] On the other hand, the ticket management system 1 also allows for the purchase of tickets as paper tickets. Paper tickets can be issued by permanently installing the ticketing device 3 in a ticket shop or similar location, allowing for advance issuance before the performance, or by installing the ticketing device 3 near the entrance to the performance, allowing for issuance immediately before entry. The procedure for issuing paper tickets using the ticket management system 1 will be explained below with reference to the flowchart shown in Figure 8.

[0056] Prior to ticket issuance, the user launches a browser or similar application on user terminal 4 and accesses the ticket URL. Access to the ticket URL is managed by server 2. When user terminal 4 accesses the ticket URL, it sends the user agent information of the browser used for access and the cookie information left in the browser when accessing the receiving URL to receive the ticket to server 2. The processing procedure up to this point is the same as when using the ticket electronically.

[0057] When the user accesses the ticket URL, the display unit 405 of the user terminal 4 displays a paper ticket issuance button along with an image of the ticket. When this paper ticket issuance button is pressed (step S400), the ticket issuance process begins. Upon commencement of the ticket issuance process, the ticket becomes unusable, untransferable, and no further tickets can be issued.

[0058] In step S400, when the user presses the paper ticket issuance button, a screen prompting the user to enter the ticket machine number is displayed on the user terminal 4. When the user enters the ticket machine number displayed on the display unit 305 into the user terminal 4, the user terminal 4 transmits the ticket machine number to the server 2 (step S410). Pressing the paper ticket issuance button is one example of the ticket issuance start operation in this invention. Upon receiving the ticket machine number, the server 2 transmits a ticketing telephone number to the user terminal 4, which the user terminal 4 receives (step S420). At this time, the server 2 records the ticket ID of the ticket to be issued and the ticketing telephone number linked together. The ticketing telephone number may be a fixed telephone number, but it may also be a different number each time it is displayed, by transmitting one number selected from multiple candidate telephone numbers. In a configuration where the ticketing telephone number is individually assigned to each ticketing device 3 as the ticket machine number, steps S410 and 420 can be omitted, and the ticketing process can be started simply by calling the ticketing telephone number displayed on the display unit 305. Therefore, paper tickets can be issued even from devices that cannot install a dedicated application.

[0059] Next, the user terminal 4 displays the ticketing telephone number received in step S420 and a verification start button to initiate verification for issuing paper tickets on the display unit 405 (step S430). Note that the ticketing telephone number transmitted and displayed in steps S420 and S430 may be configured to be displayed on the display unit 305 of the ticketing device 3 instead of the display unit 405 of the user terminal 4. When the user presses the verification start button, the server 2 records the time of pressing and associates it with the ticket ID (step S440).

[0060] Next, Server 2 determines whether a call was made to the ticketing telephone number from the user's telephone number (usually the user terminal 4) associated with the ticket, within a predetermined valid operation time (for example, within 4 seconds) from the time the button was pressed (step S450). This valid operation time should be short enough that it would be difficult to transmit the ticketing telephone number to a remote location and have someone remotely make the call.

[0061] In step S450, Server 2 determines whether a call was made to the ticketing telephone number from the user telephone number associated with the ticket (usually the user terminal 4) within a predetermined valid operation time (for example, within 4 seconds) from the time of pressing the button, as follows: Server 2 receives the call made to the ticketing telephone number via the telephone communication unit 204. The telephone communication unit 204 then identifies the originating telephone number and the telephone number to which the call was made (one of the candidate telephone numbers). Server 2 identifies the ticket ID based on the telephone number to which the call was made and determines whether a call was made to the ticketing telephone number within the valid operation time by checking whether the ticket ID is a ticket ID whose press time was recorded within the period preceding the valid operation time from the time the call was received.

[0062] If the ticketing telephone number is not called within the valid operation time from the time of pressing the button (step S450; No), the ticket will not be issued. A screen notifying the user that the ticket cannot be issued will be displayed on the display unit 405 of the user terminal 4, and the ticket will be returned to a usable state (step S460), ending the ticketing process. It is also advisable to configure the system to notify the user if the originating telephone number differs by only one character from the user telephone number recorded in association with the ticket, or if the first character is missing, or if other input errors are suspected. This will make it easy for the user to realize that they have registered the wrong user telephone number and prompt them to correct it.

[0063] On the other hand, if a call is made to the ticketing telephone number within the valid operation time from the time of pressing the button (step S450; Yes), Server 2 performs a verification process (step S470). In the verification process, the user telephone number associated with the ticket ID is extracted from the database DB and verified against the number that was called in step S450. Server 2 also verifies the cookie information and UA information recorded in association with the ticket holder's user ID against the cookie information and UA information sent from the user terminal 4 when accessing the ticket URL. If the verification process does not confirm a match in the information (step S470; No), the ticket will not be issued, and a notification screen informing the user that the ticket cannot be issued will be displayed on the display unit 405 of the user terminal 4, and the ticket will be returned to a usable state (step S460), and the ticketing process will end.

[0064] On the other hand, if the matching process confirms that the information matches (step S470; Yes), the server 2 records in the database DB that a paper ticket has been issued for that ticket, and sends a command to the ticketing device 3 of the ticketing machine number received in step S420 to print the ticket from the printing unit 304 (step S480). The ticketing device 3 of the ticketing machine number receives this command, prints the ticket with the printing unit 304 (step S490), and terminates the ticketing process.

[0065] As described above, it is possible to issue paper tickets. In the ticketing process of this embodiment, verification is performed using telephone number, cookie information, UA information, etc. at the time of issuance, which can deter the issuance of fraudulent tickets, such as by performing the necessary verification operations from a remote location. The discovered paper tickets can be used at the entrance of the event in the same way as conventional paper tickets.

[0066] [Issuance of ticket stub] The above-described paper ticket issuance process can be applied not only to issuing unused paper tickets, but also to issuing stubs of used tickets after entry using electronic tickets. It is advisable to redeem tickets at the entrance of the event venue, and then issue stubs after verification using a phone number, cookie, UA, etc., following the same procedure as the above-described ticket issuance process. In this case, the ticket issuing device 3 should be installed inside the venue (for example, immediately after passing through the entrance). In this way, when multiple people enter using electronic tickets together, stubs can be issued to attendees who do not have a user terminal 4 as proof of seat number guidance or for re-entry. It is also possible to issue paper stubs in case the battery level of the user terminal 4 is low. Furthermore, when the user terminal 4 redeems electronic tickets, if there are multiple tickets being used simultaneously or if the battery level falls below a predetermined threshold, it is advisable to prompt the user to issue paper stubs by displaying a message on the display unit 405 or emitting a notification sound.

[0067] [Ticket Transfer] The ticket management system 1 allows the transfer of managed tickets from the owner to another person.

[0068] Tickets can be transferred either electronically by having the recipient re-register as the owner, or by issuing and delivering a paper ticket.

[0069] [Electronic ticket transfer] Referring to the flowchart in Figure 9, the procedure for electronically transferring tickets will be explained. In this method, the user transferring the ticket first accesses the ticket URL after completing the owner registration described above, to display the ticket to be transferred. Then, they press the recipient registration button displayed along with the ticket (step S600). After pressing this recipient registration button, a screen prompting the user to enter the recipient's phone number is displayed on the user terminal 4. After entering the recipient's phone number on this screen (step S610), the phone number is sent to the server 2 along with the ticket ID and recorded in the database DB linked to the ticket ID (step S620). Furthermore, the user transferring the ticket is disabled in their browser, etc., and cannot be used or further transferred (step S630).

[0070] When Server 2 receives the ticket ID and the recipient's phone number, it issues an owner registration URL that allows the recipient to access the owner registration screen to complete the owner registration process, and sends it to the original user's contact information (email address, SNS, etc.) (step S640). The original user forwards this owner registration URL to the recipient (step S650). Alternatively, the owner registration URL may be sent directly from Server 2 to the recipient without going through the original user.

[0071] The recipient user receives the URL sent in step S650 using their user terminal 4 (step S660). The recipient user then registers as the owner in the same way as in steps S200-S280 of the owner registration process at the time of purchase (Figure 6). Server 2 determines whether the recipient user has successfully completed the owner registration within a predetermined period (step S670). If it is determined that the registration has been successfully completed (step S670; Yes), the recipient user is recorded as the owner of the ticket in the server 2 database DB, and the original user ceases to be the owner. The ticket then becomes available for use on the recipient user's user terminal 4 (step S680). On the other hand, if the recipient user does not successfully complete the owner registration, for example, if the registration is not completed within the predetermined transfer validity period (step S670; No), Server 2 deletes the record of the recipient's phone number from the database DB and makes the ticket available for use on the original user's user terminal 4 (step S690).

[0072] As described above, it is possible to transfer tickets electronically. By requiring the same owner registration as at the time of purchase when transferring tickets electronically, the ticket management system 1 can identify the transferor and the recipient, thereby deterring fraudulent transfers and resales.

[0073] [Transfer of paper tickets] On the other hand, the method of issuing and handing over paper tickets involves the user, who is the owner, issuing the ticket using the ticket issuing device 3 and then handing over the issued ticket to the recipient. The issuance of paper tickets should be implemented in the same way as when using paper tickets as described above. Furthermore, even when transferring paper tickets, if the system is configured to require owner registration before issuing the paper ticket, it is possible to deter fraudulent transfers and resales. In this case, if the system is configured to print the name of the registered owner, etc., on the surface of the issued paper ticket, it is expected to be particularly effective in deterring fraudulent transfers and resales.

[0074] [Second Embodiment] The ticket management system according to the second embodiment of the present invention differs from the first embodiment in its method of issuing paper tickets. Specifically, in the second embodiment, the procedure is the same as the first embodiment up to the verification step (step S450 in Figure 8), but after successful verification, the procedure for issuing paper tickets from the ticketing device 3 and the hardware configuration related to this procedure differ.

[0075] Figure 10 is a flowchart showing the procedure for ticket issuance by the ticketing device 3 in the second embodiment. Prior to ticket issuance, the user launches a browser on the user terminal 4 and accesses the ticket URL. Access to the ticket URL is managed by the server 2. When the user terminal 4 accesses the ticket URL, it sends the UA information of the browser used for access and the cookie information left in the browser when it accessed the receiving URL to receive the ticket to the server 2.

[0076] When the user accesses the ticket URL, the display unit 405 of the user terminal 4 displays a paper ticket issuance button along with an image of the ticket. When this paper ticket issuance button is pressed (step S700), the ticket issuance process begins. Upon commencement of the ticket issuance process, the ticket becomes unusable, untransferable, and no further tickets can be issued.

[0077] In step S700, when the user presses the paper ticket issuing button, a screen prompting the user to enter the ticket issuing machine number is displayed on the user terminal 4. When the user enters the ticket issuing machine number displayed on the display unit 305 into the user terminal 4, the user terminal 4 transmits the ticket issuing machine number to the server 2 (step S710). Pressing the paper ticket issuing button is one example of the operation to start issuing tickets in this invention. When the server 2 receives the ticket issuing machine number, it transmits a ticket issuing telephone number to the user terminal 4 (step S720). This ticket issuing telephone number may be a fixed telephone number, but it may also be a different number each time it is displayed, by transmitting one number selected from multiple candidate telephone numbers.

[0078] Next, the user terminal 4 displays the ticketing telephone number received in step S720 and a verification start button on the display unit 405 to begin verification for issuing paper tickets (step S730). When the user presses the verification start button, the server 2 records the time of the press (step S740).

[0079] Next, Server 2 determines whether a call was made to the ticketing telephone number from the user's telephone number (usually the user terminal 4) associated with the ticket, within a predetermined valid operation time (for example, within 4 seconds) from the time the button was pressed (step S750). This valid operation time should be short enough that it would be difficult to transmit the ticketing telephone number to a remote location and have someone remotely make the call.

[0080] In step S750, Server 2 determines whether a call was made to the ticketing telephone number from the user telephone number associated with the ticket (usually the user terminal 4) within a predetermined valid operation time (for example, within 4 seconds) from the time of pressing the button, as follows: Server 2 receives the call made to the ticketing telephone number via the telephone communication unit 204. The telephone communication unit 204 then identifies the originating telephone number and the telephone number to which the call was made (one of the candidate telephone numbers). Server 2 identifies the ticket ID based on the telephone number to which the call was made and determines whether a call was made to the ticketing telephone number within the valid operation time by checking whether the ticket ID is a ticket ID whose pressing time was recorded within the period preceding the valid operation time from the time the call was received.

[0081] If the ticketing telephone number is not called within the valid operation time from the time of pressing the button (step S750; No), the ticket will not be issued. A screen notifying the user that the ticket cannot be issued will be displayed on the display unit 405 of the user terminal 4, and the ticket will be returned to a usable state (step S760), ending the ticketing process. It is advisable to configure the system to notify the user if it is suspected that the caller's telephone number is entered incorrectly, such as by only one character difference from the user's telephone number recorded in association with the ticket, or if the first character is missing. In this way, the user can easily realize that they have registered the wrong telephone number and be prompted to correct it.

[0082] On the other hand, if a call is made to the ticketing telephone number within the valid operating time (step S750; Yes), server 2 performs a verification process (step S770). In the verification process, the user telephone number associated with the ticket ID is extracted from the database DB and verified against the number that was called in step S750. Server 2 also verifies the cookie information and UA information recorded in association with the ticket holder's user ID against the cookie information and UA information sent from the user terminal 4 when accessing the ticket URL. If the verification process does not confirm a match in the information (step S770; No), the ticket will not be issued, and a notification screen informing the user that the ticket cannot be issued will be displayed on the display unit 405 of the user terminal 4. The ticket will then be returned to a usable state (step S760), and the ticketing process will end.

[0083] On the other hand, if the matching process confirms that the information matches (step S770; Yes), the server 2 initiates a voice call on the phone received in step S750 using the telephone communication unit 204 (step S780). The telephone communication unit 204 then transmits data-embedded voice to the user terminal 4 using the voice call, containing information for printing tickets on the ticketing device 3 (hereinafter referred to as "ticketing information"). It is preferable that the voice call be disconnected after a predetermined call time has elapsed. Here, the ticketing information may include all the data on the ticket face, or it may include only the encrypted ticket ID as needed. If the ticketing information consists only of the ticket ID, the ticketing device 3 may receive data linking the ticket ID and the data on the ticket face from the server 2 in advance and store it in the storage unit 301. Alternatively, each time ticketing information is received, the ticketing device 3 may query the server 2 for the ticket face data corresponding to the ticket ID and receive it via the network NW. Furthermore, the ticketing information may include the ticketing machine number entered in step S710. Additionally, the ticketing information may include timestamp information indicating the time of the ticketing process, such as the time the button was pressed and the time the ticketing telephone number was dialed, as recorded in step S740.

[0084] The user holds the speaker 407 of the user terminal 4 over the microphone 306 of the ticketing device 3, inputting data-embedded audio into the microphone 306 (step S800). The ticketing device 3 decodes the audio input into the microphone 306 and obtains ticketing information (step S810). The ticketing device 3 then determines whether the received ticketing information is valid or not (step S820).

[0085] Whether the received ticketing information is valid can be determined, for example, as follows: If the ticketing information includes a ticketing machine number, it is good to include a condition for determining validity that the ticketing machine number of the ticketing device 3 into which the data-embedded voice was input matches the ticketing machine number included in the ticketing information. Also, if the ticketing information includes a timestamp, it is good to include a condition for determining validity that the current time falls within the predetermined ticketing validity period from the time indicated by the timestamp information. The ticketing validity period should be a time (e.g., 3 minutes) that makes it difficult to record the data-embedded voice and send it to a remote location via a network NW, etc. It is also possible to include a condition that the voice was input within a predetermined time after the information match was confirmed in the matching process. In addition, it is good to include a condition for determining validity that the ticketing information includes information indicating that the matching in step S780 was performed.

[0086] If the received ticketing information is valid (step S820; Yes), the ticketing device 3 prints the ticket in the printing unit 304 and sends information to the server 2 indicating that the ticket has been issued, such as the result of the determination in step S820 (step S830). In response, the server 2 records in the database DB that a paper ticket has been issued for that ticket (step S840) and terminates the ticketing process.

[0087] On the other hand, if the received ticketing information is not valid (step S820; No), the ticketing device 3 displays a message on the display unit 305 indicating that the ticket cannot be issued and sends information to the server 2 indicating that the ticket was not issued, such as the result of the decision in step S840 (step S850). In response, the server 2 returns the ticket to a usable state (step S860) and terminates the ticketing process.

[0088] As described above, when issuing paper tickets, the ticketing information is transmitted from the user terminal 4 to the ticketing device 3 via data-embedded voice. This prevents the transmission of the data-embedded voice necessary for ticketing to the ticketing device 3, even if a remote call is successful during verification. Therefore, the issuance of fraudulent tickets can be more effectively deterred.

[0089] [Modified version of the second embodiment] In the second embodiment described above, data-embedded audio was transmitted from server 2 via voice call over a telephone line TL and received by user terminal 4. However, data-embedded audio may be transmitted to user terminal 4 by a method other than voice call over a telephone line TL and output from speaker 407 of user terminal 4. For example, data-embedded audio may be transmitted from server 2 via live streaming over a network NW and received by user terminal 4, and the data-embedded audio may be streamed and played back on user terminal 4 to be output from speaker 407. Alternatively, data-embedded audio may be transmitted as an audio data file over a network NW, received by user terminal 4, and the data-embedded audio may be played back on user terminal 4 to be output from speaker 407. According to these methods, since data-embedded audio is not degraded during the transmission process from server 2 to user terminal 4, errors in the transmission of ticketing information can be made less likely.

[0090] Furthermore, in a configuration where data-embedded audio is transmitted as an audio data file via a network, the system may be configured to restrict the forwarding of the received audio data file by the user terminal 4, or to restrict playback of the audio data file on other terminals. For example, the audio data may be linked to cookie information used during ticketing or session information of data communication via the network, so that the audio data file can only be played on the user terminal 4 used for ticketing.

[0091] [Third Embodiment] The ticket management system according to the third embodiment of the present invention differs from the first embodiment in its method of issuing paper tickets. Specifically, in the second embodiment, the procedure is the same as the first embodiment up to the verification step (step S450 in Figure 8), but after successful verification, the procedure for issuing paper tickets from the ticketing device 3 and the hardware configuration related to this procedure differ.

[0092] Figure 11 is a flowchart showing the procedure for ticket issuance by the ticketing device 3 in the third embodiment. Prior to ticket issuance, the user launches a browser on the user terminal 4 and accesses the ticket URL. Access to the ticket URL is managed by the server 2. When the user terminal 4 accesses the ticket URL, it sends the UA information of the browser used for access and the cookie information left in the browser when it accessed the receiving URL to receive the ticket to the server 2.

[0093] When the user accesses the ticket URL, the display unit 405 of the user terminal 4 displays a paper ticket issuance button along with an image of the ticket. When this paper ticket issuance button is pressed (step S900), the ticket issuance process begins. Upon commencement of the ticket issuance process, the ticket becomes unusable, untransferable, and no further tickets can be issued.

[0094] In step S900, when the user presses the paper ticket issuing button, a screen prompting the user to enter the ticket issuing machine number is displayed on the user terminal 4. When the user enters the ticket issuing machine number displayed on the display unit 305 into the user terminal 4, the user terminal 4 transmits the ticket issuing machine number to the server 2 (step S910). Pressing the paper ticket issuing button is one example of the ticket issuance start operation in this invention. Upon receiving the ticket issuing machine number, the server 2 transmits a ticket issuing telephone number to the user terminal 4 (step S920). This ticket issuing telephone number may be a fixed telephone number, but it may also be a different number each time it is displayed, by transmitting one number selected from multiple candidate telephone numbers.

[0095] Next, the user terminal 4 displays the ticketing telephone number received in step S720 and a verification start button on the display unit 405 to begin verification for issuing paper tickets (step S930). When the user presses the verification start button, the server 2 records the time of the press (step S940).

[0096] Next, Server 2 determines whether a call was made to the ticketing telephone number from the user's telephone number recorded in association with the ticket (usually the user terminal 4) within a predetermined valid operation time (for example, within 4 seconds) from the time of pressing the button (step S950). This valid operation time should be short enough that it would be difficult to transmit the ticketing telephone number to a remote location and have someone remotely make the call.

[0097] In step S950, Server 2 determines whether a call was made to the ticketing telephone number from the user telephone number associated with the ticket (usually the user terminal 4) within a predetermined valid operation time (for example, within 4 seconds) from the time of pressing the button, as follows: Server 2 receives the call made to the ticketing telephone number via the telephone communication unit 204. The telephone communication unit 204 then identifies the originating telephone number and the telephone number to which the call was made (one of the candidate telephone numbers). Server 2 identifies the ticket ID based on the telephone number to which the call was made and determines whether a call was made to the ticketing telephone number within the valid operation time by checking whether the ticket ID is a ticket ID whose pressing time was recorded within the period preceding the valid operation time from the time the call was received.

[0098] If the ticketing telephone number is not called within the valid operation time from the time of pressing the button (step S950; No), the ticket will not be issued. A screen notifying the user that the ticket cannot be issued will be displayed on the display unit 405 of the user terminal 4, and the ticket will be returned to a usable state (step S960), ending the ticketing process. It is also advisable to configure the system to notify the user if the originating telephone number differs by only one character from the user telephone number recorded in association with the ticket. This makes it easy for the user to realize that they have registered the wrong telephone number and prompts them to correct it.

[0099] On the other hand, if a call is made to the ticketing telephone number within the valid operating time (step S950; Yes), server 2 performs a verification process (step S970). In the verification process, the user telephone number associated with the ticket ID is extracted from the database DB and verified against the number that was called in step S950. Server 2 also verifies the cookie information and UA information recorded in association with the ticket holder's user ID against the cookie information and UA information sent from the user terminal 4 when accessing the ticket URL. If the verification process does not confirm a match in the information (step S970; No), the ticket will not be issued, and a notification screen informing the user that the ticket cannot be issued will be displayed on the display unit 405 of the user terminal 4. The ticket will then be returned to a usable state (step S960), and the ticketing process will end.

[0100] On the other hand, if the matching process confirms that the information matches (step S970; Yes), the server 2 transmits an identification code (barcode, QR code (registered trademark), etc.) and displays it on the display unit 405 of the user terminal 4 (step S980). The identification code transmitted by the server 2 may include data from the ticket face, or it may contain only the encrypted ticket ID as needed. If only the ticket ID is included, the ticketing device 3 may receive data linking the ticket ID and the ticket face data from the server 2 in advance and store it in the storage unit 301. Alternatively, each time the identification code is read, the ticketing device 3 may query the server 2 for the ticket face data corresponding to the ticket ID and receive it via the network NW. The identification code may also include information such as a URL indicating the location of the information necessary for issuing the ticket on the network NW. The identification code may also include the ticketing machine number entered in step S910. The identification code may also include timestamp information indicating the time of the ticketing process, such as the time the button was pressed or the time the ticketing telephone number was dialed, as recorded in step S940. The identification code should be configured so that it disappears from the display unit 405 of the user terminal 4 after a predetermined amount of time has elapsed since it was displayed.

[0101] The user holds the display unit 405 of the user terminal 4 over the camera 307 of the ticket issuing device 3 to allow the ticket issuing device 3 to read the identification code (step S990). The ticket issuing device 3 then determines whether the read identification code is valid or not (step S1020).

[0102] Whether a received identification code is valid can be determined, for example, as follows: If the identification code includes a ticket machine number, the condition for determining its validity should include that the ticket machine number of the ticketing device 3 that read the identification code matches the ticket machine number included in the identification code. If the identification code includes timestamp information, the condition for determining its validity should include that the current time falls within the predetermined ticketing validity period from the time indicated in the timestamp information. Additionally, the condition may include that the identification code was read within a predetermined time after the information match was confirmed in the matching process. Furthermore, the condition for determining its validity should include that the ticketing information includes information indicating that the matching in step S980 was performed.

[0103] If the read identification code is valid (step S1020; Yes), the ticketing device 3 prints the ticket in the printing unit 304 and sends information to the server 2 indicating that the ticket has been issued based on the determination in step S1020 (step S1030). In response, the server 2 records in the database DB that a paper ticket has been issued for that ticket (step S1040) and terminates the ticketing process.

[0104] On the other hand, if the read identification code is not valid (step S1020; No), the ticketing device 3 displays on the display unit 305 that a ticket cannot be issued and sends information to the server 2 indicating that, as a result of the decision in step S1040, the ticket was not issued (step S1050). In response, the server 2 returns the ticket to a usable state (step S1060) and terminates the ticketing process.

[0105] As described above, when issuing a paper ticket, the identification code displayed on the user terminal 4 is read by the ticketing device 3. Therefore, even if a remote call is successfully made during verification, the identification code necessary for ticketing cannot be transmitted to the ticketing device 3, thus more effectively deterring the issuance of fraudulent tickets.

[0106] Although embodiments of the present invention have been described above, the present invention is not limited to these examples. Furthermore, any additions, deletions, or design modifications of components to the aforementioned embodiments, or any combination of features from each embodiment as appropriate by those skilled in the art, are also included within the scope of the present invention, as long as they retain the essence of the present invention. [Explanation of symbols]

[0107] 1. Ticket Management System 2 servers 3 Ticket issuing device 4. User terminals NW Network TL telephone network

Claims

1. An information processing device comprising a control unit, The control unit, The steps include receiving a notification that an authentication operation for the ticket has been performed on the user's terminal, and storing the time the said operation was performed, A database that stores information that can identify the ticket in association with the user's user telephone number, a step of determining whether an incoming call from the user telephone number associated with the ticket to a predetermined authentication telephone number occurred within a predetermined time from the stored operation time, An information processing device that performs the step of allowing the user to use the ticket if an incoming call from the user's telephone number associated with the ticket to the authentication telephone number occurs within a predetermined time from the stored operation time.

2. A program for operating a computer equipped with a processor, wherein the program is configured to operate the processor, The steps include receiving a notification that an authentication operation for the ticket has been performed on the user's terminal, and storing the time the said operation was performed, A database that stores information that can identify the ticket in association with the user's user telephone number, a step of determining whether an incoming call from the user telephone number associated with the ticket to a predetermined authentication telephone number occurred within a predetermined time from the stored operation time, A program that, if an incoming call from the user's telephone number associated with the ticket to the authentication telephone number occurs within a predetermined time period from the stored operation time, causes the program to make the ticket available to the user.

3. A method to be performed on a computer having a processor, wherein the processor The steps include receiving a notification that an authentication operation for the ticket has been performed on the user's terminal, and storing the time the said operation was performed, A database that stores information that can identify the ticket in association with the user's user telephone number, a step of determining whether an incoming call from the user telephone number associated with the ticket to a predetermined authentication telephone number occurred within a predetermined time from the stored operation time, A method of performing the steps of enabling the user to use the ticket if an incoming call from the user's telephone number associated with the ticket to the authentication telephone number occurs within a predetermined time period from the stored operation time.

4. A means for receiving notification that an authentication operation for a ticket has been performed on the user's terminal, and for storing the time the said operation was performed, A database that stores information that can identify the ticket in association with the user's user telephone number, includes means for determining whether an incoming call from the user telephone number associated with the ticket to a predetermined authentication telephone number occurred within a predetermined time from the stored operation time. A system comprising means for allowing the user to use the ticket if an incoming call from the user's telephone number associated with the ticket to the authentication telephone number occurs within a predetermined time period from the stored operation time.

Images