RESERVATION SYSTEM, MANAGEMENT DEVICE, AND RESERVATION AND ISSUING METHOD

Abstract

To provide a reservation system capable of reducing labor involved in identity verification when issuing a ticket.SOLUTION: A server 1 registers, in a database 4, reservation information corresponding to designation information for designating a ticket from a reservation terminal 2, and voice data from the reservation terminal 2 in association with each other. Further, the server 1 authenticates a user based on input voice data, which is voice data from the ticket issuing terminal 2, and the registered voice data, which is voice data registered in the database 4. If the authentication is successful, a ticket issuing request is transmitted to the ticket issuing terminal 2 based on the reservation information corresponding to the registered voice data.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a reservation system, a management device, and a reservation and issuing method. [Background technology]

[0002] 2. Description of the Related Art When reserving, issuing, and using tickets, such as tickets for transportation such as trains and airplanes and tickets for events such as concerts, the identity of the user using the ticket may be required.

[0003] Patent Document 1 discloses a reservation system that issues a ticket on which authentication information including a feature ID that identifies feature amount data related to a user's biometric information is recorded.

[0004] Patent Document 2 discloses a reservation system that creates and outputs a question about the ticket purchase history of tickets previously purchased by a user when issuing a ticket. In this reservation system, a ticket is issued if the question is answered correctly. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] International Publication No. 2020 / 241852 [Patent Document 2] JP 2005-50092 A Summary of the Invention [Problem to be solved by the invention]

[0006] In the technology described in Patent Document 1, information for identifying an individual is embedded in the ticket, but the identity of the user cannot be verified when the ticket is issued.

[0007] The technology described in Patent Document 2 can verify the identity of a user when issuing a ticket, but it requires the user to answer questions created by the reservation system, which is time-consuming. In addition, since the questions are created by the reservation system according to the user's ticket purchase history, if the user forgets his or her own purchase history, there is a risk that the user will not be able to answer the questions correctly.

[0008] An object of the present invention is to provide a reservation system, a management device, and a reservation and issuing method that can reduce the effort involved in identity verification when issuing tickets. [Means for solving the problem]

[0009] A reservation system according to one aspect of the present disclosure is a reservation system having a reservation terminal, a ticket issuing terminal, and a management device, wherein the reservation terminal has an input unit that accepts a designation operation from a user to designate a ticket to be reserved, a first voice acquisition unit that acquires the voice input from the user as first voice data, and a connection unit that transmits designation information indicating the ticket designated by the designation operation and the first voice data to the management device, and the ticket issuing terminal has a second voice acquisition unit that acquires the voice input from the user as second voice data, and a connection unit that transmits the second voice data to the management device. the management device has a control unit which corresponds the designation information and the first voice data from the reservation terminal and registers them in a database, authenticates the user based on the second voice data from the ticket issuing terminal and the first voice data registered in the database, and if the authentication is successful, sends the ticket issuance request to the ticket issuing terminal based on the designation information corresponding to the first voice data. Effect of the Invention

[0010] According to the present invention, it is possible to reduce the effort involved in identity verification when issuing a ticket. [Brief description of the drawings]

[0011] [Figure 1] 1 is an overall configuration diagram illustrating an example of a reservation system according to an embodiment of the present disclosure. [Diagram 2] FIG. 2 illustrates an example of a hardware configuration of a server. [Diagram 3] FIG. 2 illustrates an example of a hardware configuration of a reservation terminal. [Figure 4] FIG. 2 is a diagram illustrating an example of a hardware configuration of a ticket issuing and settlement terminal. [Diagram 5] FIG. 11 is a diagram illustrating an example of registration information stored in a database. [Figure 6] 13 is a flowchart illustrating an example of a reservation transaction process. [Figure 7] FIG. 13 is a diagram illustrating an example of a query request message. [Figure 8] FIG. 13 is a diagram showing an example of a query result message. [Figure 9] FIG. 11 is a diagram illustrating an example of a registration request message. [Figure 10] FIG. 13 is a diagram showing an example of a registration result message. [Figure 11] 11 is a flowchart illustrating an example of a ticket issuing transaction process. [Figure 12] FIG. 11 illustrates an example of an authentication request message. [Figure 13] FIG. 13 is a diagram showing an example of an authentication result message. [Figure 14] FIG. 13 is a diagram showing an example of a get-off station input screen. [Figure 15] FIG. 13 is a diagram showing an example of a keyword voice input screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0013] FIG. 1 is an overall configuration diagram showing a reservation system according to an embodiment of the present disclosure. The reservation system shown in FIG. 1 reserves and issues tickets such as tickets for transportation means such as trains and airplanes, and tickets for events such as concerts. In such a reservation system, it is effective to separate the place where the tickets are reserved from the place where the tickets are issued in order to alleviate congestion. For example, when a user reserves a train ticket as a ticket, the ticket reservation, payment, and issuance are not all performed at the counter, but the reservation is only performed at a reservation terminal at the counter, and the payment and issuance are performed at a ticket vending machine (ticket issuing settlement terminal), thereby improving the work efficiency at the counter. However, in this case, it is necessary to perform identity verification (user authentication) of the user at the time of ticket issuance so that the ticket is issued to the person who made the reservation.

[0014] The reservation system shown in Fig. 1 is a system in which the place for reserving tickets and the place for issuing tickets are separated. Also, although the ticket is described as a train ticket, in this disclosure the ticket is not limited to a train ticket, but may be a ticket for other means of transportation or an admission ticket for an event.

[0015] As shown in Fig. 1, the reservation system has a server 1, a reservation terminal 2, a ticket issuance and payment terminal 3, and a database 4, and the devices 1 to 4 are connected to each other so that they can communicate with each other via a network 5. The network is a communication line that enables communication between the server 1, the reservation terminal 2, the ticket issuance and payment terminal 3, and the database 4. The communication method of the network 5 is not particularly limited, and may be, for example, a wired method or a wireless method. There may be multiple reservation terminals 2 and multiple ticket issuance and payment terminals 3.

[0016] The server 1 is a management device that manages ticket reservations and issuance in cooperation with the reservation terminal 2, the ticket issuing and payment terminal 3, and the database 4. For example, the server 1 accepts a message related to a ticket reservation from the reservation terminal 2, processes the ticket reservation in accordance with the message, and registers reservation information indicating the reservation details and authentication information for identity verification when issuing the ticket in the database 4 in association with each other. In this embodiment, the authentication information is voice data indicating the user's voice.

[0017] In addition, the server 1 accepts a message regarding ticket issuance from the ticket issuing and settlement terminal 3, and executes an authentication process to verify (authenticate) the user's identity based on the message and the registration information stored in the database 4. If the authentication is successful, the server 1 sends a ticket issuance request to the ticket issuing and settlement terminal 3 based on the registration information.

[0018] The reservation terminal 2 is a terminal that transmits various electronic messages related to ticket reservations to the server 1 in response to input from a user, thereby reserving tickets.

[0019] The ticket issuing and settlement terminal 3 is a ticket issuing terminal that transmits a message regarding ticket issuing to the server 1 in response to an input from a user, and issues a ticket in response to a response to the message.

[0020] The database 4 is a storage device that stores reservation information indicating the contents of tickets reserved by users and authentication information.

[0021] 2 is a diagram showing an example of a hardware configuration of the server 1. The server 1 includes a network connection unit 101, a memory 102, and a CPU (Central Processing Unit) 103.

[0022] The network connection unit 101 is connected to each of the reservation terminal 2, the ticket issuing and settlement terminal 3, and the database 4 via the network 5 so as to be able to communicate with each other. The memory 102 is a recording medium readable by the CPU 103, and records a program that defines the operation of the CPU 103. The CPU 103 is a control unit that reads the program recorded in the memory 102, executes the read program, and controls the entire server 1. For example, the CPU 103 transmits and receives various messages via the network connection unit 101, and performs processing according to the received messages.

[0023] 3 is a diagram showing an example of a hardware configuration of the appointment terminal 2. The appointment terminal 2 shown in FIG.

[0024] The network connection unit 201 is a connection unit that is connected to the server 1 via the network 5 so as to be able to communicate with each other. The LCD touch panel 202 has a function as an input unit that receives various information from the user and a function as a display unit that displays various information to the user. The microphone 203 is a first voice acquisition unit that acquires voice input from the user as voice data (first voice data). In this embodiment, the microphone 203 acquires a keyword, which is an authentication word spoken by the user, as voice data. The keyword includes a ticket issuance word and a recovery word that is used when the user forgets the ticket issuance word. There is one ticket issuance word and one or more recovery words.

[0025] The memory 204 is a recording medium readable by the CPU 205, and records a program that defines the operation of the CPU 205. The CPU 205 is a reservation terminal control unit that reads the program recorded in the memory 204, executes the read program, and controls the reservation terminal 2 as a whole.

[0026] Fig. 4 is a diagram showing an example of a hardware configuration of the ticket issuing and payment terminal 3. The ticket issuing and payment terminal 3 shown in Fig. 4 has a network connection unit 301, an LCD touch panel 302, a microphone 303, a ticket issuing unit 304, a payment processing unit 305, a memory 306, and a CPU 307.

[0027] The network connection unit 301 is a communication unit that is connected to the server 1 via the network 5 so as to be able to communicate with each other. The LCD touch panel 302 has a function as an input unit that receives various information from the user and a function as a display unit that displays various information to the user. The microphone 303 is a second voice acquisition unit that acquires voice input by the user as voice data (second voice data). In this embodiment, the microphone 303 acquires keywords uttered by the user as voice data.

[0028] The ticket issuing unit 304 issues tickets. The payment processing unit 305 performs payment processing by cash or non-cash (e.g., credit card or electronic money) associated with the issuance of tickets. For example, the payment processing unit 305 accepts and stores cash, and reads card information of credit cards or electronic money cards.

[0029] Memory 306 is a recording medium readable by CPU 307, and records a program that defines the operation of CPU 307. CPU 307 is a ticket issuance and settlement terminal control unit that reads the program recorded in memory 306, executes the read program, and controls ticket issuance and settlement terminal 3 as a whole.

[0030] 5 is a diagram showing an example of registration information stored in the database 4. Registration information 400 shown in FIG.

[0031] A registration ID, which is identification information for identifying a reserved ticket, is stored in a field 401. A field 402 stores reservation terminal information, which is identification information for identifying the reservation terminal 2 used to reserve the ticket.

[0032] Field 403 stores reservation information indicating the details of the reserved ticket. In this embodiment, field 403 includes fields 411 to 415. Field 411 stores the departure time of the reserved train, which is a train that can be boarded with the reserved ticket, field 412 stores the boarding station, which is the name of the station where the reserved train will be boarded, field 413 stores the disembarking station, which is the name of the station where the reserved train will be disembarked, and field 414 stores the transfer station, which is the name of the station where the reserved train will be transferred. Note that field 414 is provided for each transfer station. FIG. 5 shows an example in which there are two fields 414. Furthermore, if there is no transfer station for the reserved train, field 414 will be null (indicated as "-" in FIG. 5).

[0033] Fields 404 and 405 store voice data acquired by the reservation terminal 2. Specifically, field 404 stores voice data indicating ticketing words, and field 405 stores voice data indicating recovery words. In the illustrated example, there are eight recovery words, and a field 405 is provided for each recovery word. However, the number of recovery words is not limited to eight.

[0034] 6 is a flowchart for explaining an example of a reservation transaction process which is a process of the reservation system when reserving a ticket. The reservation transaction process is performed, for example, when the user instructs the reservation terminal 2 to start the reservation transaction process.

[0035] In the reservation transaction process, first, the CPU 205 of the reservation terminal 2 displays on the LCD touch panel 202 a selection screen that allows the user to select whether or not the station at which the user boards the train for which the ticket is to be reserved is the same as the installation station where the reservation terminal 2 is installed. Then, the CPU 205 judges whether or not the departure is from the installation station in response to an input from the user (step S601). Note that in this embodiment, the user's input is, for example, performed by an input operation on the LCD touch panel 202 (for example, operating a button on the screen) or by voice input to the microphone 203.

[0036] If the departure is not from this station (step S601: No), the CPU 205 displays a boarding station input screen on the LCD touch panel 202 for the user to input the boarding station. After that, the CPU 205 acquires the boarding station specified by the user's input (step S602). On the other hand, if the departure is from this station (step S601: Yes), the CPU 205 skips step S602 and acquires the name of the installation station as the boarding station. This makes it possible to simplify the user's operation.

[0037] Next, the CPU 205 displays on the LCD touch panel 202 a disembarking station input screen (see FIG. 14) for the user to input the disembarking station. Then, the CPU 205 acquires the disembarking station specified by the user's input (step S603). Next, the CPU 205 displays on the LCD touch panel 202 a boarding date and time input screen for the user to input the boarding date and time. Then, the CPU 205 acquires the boarding date and time specified by the user's input (step S604). Furthermore, the CPU 205 displays on the LCD touch panel 202 a passenger number input screen for the user to input the number of passengers. Then, the CPU 205 acquires the number of passengers specified by the user's input (step S605).

[0038] In each of the processes of steps S601 to S605, if the voice input by voice input is unclear, and if the time from the start to the end of the voice input exceeds a predetermined input time range, the CPU 205 may display information on the LCD touch panel 202 to prompt the user to input again. Also, if a cancel button (see FIG. 14) for interrupting the transaction on the LCD touch panel 202 is pressed, or if step S605 has not ended even after a predetermined upper limit time has elapsed since the selection screen was displayed in the process of step S601, the CPU 205 may interrupt the reservation transaction process and return to a standby state waiting for an instruction to start the reservation transaction process.

[0039] When step 605 is completed, the CPU 205 compiles the information acquired in steps S601 to S605 (boarding station, disembarking station, boarding date and time, and number of passengers) as reservation condition information indicating the reservation conditions for the ticket to be reserved. The CPU 205 generates a query request message including reservation terminal information for identifying the reservation terminal 2 having the CPU 205 and reservation condition information as a query request for querying tickets that meet the reservation conditions, and transmits the query message to the server 1 (step S606).

[0040] Fig. 7 is a diagram showing an example of a query request message. Query request message 500 shown in Fig. 7 has fields 501 and 502. Field 501 stores reservation terminal information. Field 502 stores reservation condition information. Field 502 specifically has fields 503 to 506. Field 503 stores the boarding station, field 504 stores the disembarking station, field 505 stores the boarding date and time, and field 506 stores the number of passengers.

[0041] Returning to the explanation of Fig. 6, when the network connection unit 101 of the server 1 receives the inquiry request message, the CPU 103 of the server 1 searches for candidate trains that match the reservation condition information included in the inquiry request message, generates an inquiry result message indicating the search results, and transmits it to the reservation terminal 2 (step S607). At this time, the CPU 103 searches, for example, from operation schedule data indicating train operation schedules and vacant seats (seats that can be reserved) on each train, for trains that operate from the boarding station to the deboarding station during the boarding date and time and have vacant seats for more than the number of passengers, and depart after the boarding date and time, as candidate trains. The operation schedule data is stored in advance in, for example, the server 1 or the database 4.

[0042] If a candidate train exists, the inquiry result message includes candidate data indicating the candidate train. At this time, if there are multiple candidate trains, CPU 103 may generate an inquiry result message including multiple candidate data indicating each of the candidate trains. If there are more than a predetermined number of candidate trains (e.g., 3), CPU 103 may generate an inquiry result message including a predetermined number of candidate data indicating each of the predetermined number of candidate trains in order of departure time closest to the boarding date and time, for example. If there are no candidate trains, CPU 103 generates inquiry result message 510 that does not include candidate data.

[0043] FIG. 8 is a diagram showing an example of an inquiry result message. The inquiry result message 510 shown in FIG. 8 is an example in which there are three candidate trains, and has three fields 511. Each field 511 stores candidate data. Specifically, each field 511 includes fields 512 to 517. Field 512 stores a candidate ID which is identification information for identifying the candidate train, field 513 stores the departure time of the candidate train, field 514 stores the boarding station of the candidate train, field 515 stores the disembarking station of the candidate train, and field 516 stores the transfer station of the candidate train. Note that field 516 is provided for each transfer station. FIG. 8 shows an example in which there are two fields 516.

[0044] Returning to the explanation of Fig. 6, when the network connection unit 201 of the reservation terminal 2 receives the inquiry result message, the CPU 205 checks whether or not the inquiry result message includes candidate data, and determines whether or not there are candidate trains (step S608).

[0045] If there are no candidate trains (step S608: NO), the CPU 205 displays on the LCD touch panel 202 a message indicating that no candidate data exists (step S609), and returns to the process of step S601 to prompt the user to re-input information such as the boarding station.

[0046] On the other hand, if there are candidate trains (step S608: YES), the CPU 205 displays each candidate data included in the inquiry result message on the LCD touch panel 202, and prompts the user to specify one of the candidate data (step S610).

[0047] Thereafter, when the user performs a designation operation on the LCD touch panel 202 to designate one of the candidate data, the CPU 205 acquires the candidate ID of the candidate data designated by the user as designation information for designating the ticket to be reserved, and displays on the LCD touch panel 202 a keyword voice input screen (see FIG. 15) that prompts the user to input a keyword by voice (step S611). The keywords include a ticketing word and a recovery word as described above. The ticketing word is a word that the user spontaneously decides, and may be the name of the boarding station or the disembarking station, or the like. The recovery word is a word that the user decides following guidance on the keyword voice input screen. The number of recovery words may be arbitrarily designated by the user or may be predetermined, so long as it is 1 or more.

[0048] When the user inputs a keyword as voice data into the microphone 203, the CPU 205 generates a registration request message including reservation terminal information that identifies the reservation terminal 2 having the CPU 205, the candidate ID of the candidate data selected by the user, and the input voice data, as a registration request requesting registration of the reservation information, and transmits the message to the server 1 (step S612).

[0049] Fig. 9 is a diagram showing an example of a registration request message. The registration request message 520 shown in Fig. 9 has fields 521 to 524. Field 521 stores reservation terminal information of the reservation terminal 2. Field 522 stores the candidate ID of the candidate data selected by the user. Field 523 stores a ticket issuing word from the voice data input as a keyword. Field 524 stores a recovery word from the voice data input as a keyword. A field 524 is provided for each recovery word. Fig. 9 shows an example in which there are eight recovery words.

[0050] Returning to the explanation of Fig. 6, when the network connection unit 101 of the server 1 receives the registration request message, the CPU 103 regards the departure time, boarding station, disembarking station, and transfer station included in the candidate data of the candidate ID included in the registration request message as reservation information, assigns a registration ID to the reservation information and the reservation terminal information and voice data included in the registration request message, and registers them in the database 4. The CPU 103 also generates a registration result message including the registration result and transmits it to the reservation terminal 2 (step S612).

[0051] Fig. 10 is a diagram showing an example of a registration result message. The registration result message 530 shown in Fig. 10 includes a field 531. The field 531 stores the registration result. The registration result indicates "REGISTRATION OK", which indicates successful registration, or "REGISTRATION NG", which indicates unsuccessful registration. Note that "REGISTRATION NG" is used when an error occurs in the processing of step S612, etc.

[0052] Returning to the explanation of Fig. 6, when the network connection unit 201 of the reservation terminal 2 receives the registration result message, the CPU 205 checks the registration result message. If the registration result message indicates "Registration OK", the CPU 205 displays the reservation details and a confirmation button on the LCD touch panel 202, and when the confirmation button is subsequently pressed, the CPU 205 completes the reservation transaction and ends the process. On the other hand, if the registration result message indicates "Registration NG", the CPU 205 displays a message to that effect on the LCD touch panel 202, and ends the process without completing the reservation transaction (step S613).

[0053] 11 is a flowchart for explaining an example of a ticket issuing transaction process which is a process of the reservation system when issuing a ticket. The ticket issuing transaction process is performed, for example, when a user instructs the ticket issuing and settlement terminal 3 to start the ticket issuing transaction process.

[0054] In the ticket issuing transaction process, the CPU 307 of the ticket issuing and settlement terminal 3 displays a ticket issuing word input screen on the LCD touch panel 302, which prompts the user to input a ticket issuing word by voice (step S701). The ticket issuing word input screen may include a message indicating that a recovery word may be used if the user has forgotten the ticket issuing word.

[0055] When a user inputs voice data into the microphone 303, an authentication request message is generated and sent to the server 1 as an authentication request requesting authentication of the user, the message including the voice data and ticket-issuing payment terminal information, which is identification information for identifying the ticket-issuing payment terminal 3 (step S702).

[0056] Fig. 12 is a diagram showing an example of an authentication request message. An authentication request message 540 shown in Fig. 12 has fields 541 and 542. Field 541 stores ticket issuing and settlement terminal information. Field 542 stores voice data.

[0057] Returning to the explanation of Fig. 11, when the network connection unit 101 of the server 1 receives the inquiry request message, the CPU 103 authenticates the user by comparing the input voice data, which is the voice data included in the inquiry request message, with each of the registered voice data, which is the voice data included in the registration information stored in the database 4, and determining whether or not there is registered voice data that matches the input voice data. Then, the CPU 103 generates an authentication result message including the authentication result of the user authentication and transmits it to the ticket issuance and settlement terminal 3 (step S702).

[0058] In authenticating a user, the CPU 103 may, for example, perform voiceprint authentication of the input voice data and the registered voice data, and if there is registered voice data having a feature value whose similarity with the feature value of the input voice data is equal to or greater than a threshold value, determine that the registered voice data matches the input voice data. The CPU 103 may also match the input voice data with voice data (voice data stored in field 404 in FIG. 4) that indicates a ticket issuing word among the registered voice data, and if there is no registered voice data that matches the input voice data, match the input voice data with voice data (voice data stored in field 405 in FIG. 4) that indicates a recovery word among the registered voice data.

[0059] In addition, in the case of "authentication OK", in this embodiment, the CPU 103 adds the reservation information corresponding to the registered voice data that matches the input voice data to the authentication result message 550, and uses the authentication result message 550 as a ticket issuance request to request the issuance of a ticket according to the reservation information.

[0060] FIG. 13 is a diagram showing an example of an authentication result message. An authentication result message 550 shown in FIG. 13 has fields 551 and 552. The field 551 stores the authentication result. The authentication result indicates "authentication OK" representing a successful authentication, or "authentication NG" representing a failed authentication. The field 552 stores reservation information. The reservation information is stored when the authentication result indicates "authentication OK", and when the authentication result indicates "authentication NG", the field 552 is null. The field 552 specifically includes fields 553 to 556. The field 553 stores the departure time of the reserved train, the field 554 stores the boarding station of the reserved train, the field 555 stores the disembarking station of the reserved train, and the field 556 stores the transfer station of the reserved train. The field 556 is provided for each transfer station. FIG. 13 shows an example in which there are two fields 556.

[0061] Returning to the description of Fig. 11, when network connection unit 301 of ticket issuing and settlement terminal 3 receives the authentication result message, CPU 307 checks whether the authentication result in the authentication result message indicates "authentication OK" (step S703).

[0062] If the authentication is "NG" (step S703: NO), CPU 307 displays a message to that effect on LCD touch panel 302 (step S704), returns to the process of step S701, and prompts the user to re-enter voice data.

[0063] If the authentication is "OK", the CPU 307 displays the reservation information and a confirmation button included in the authentication result message on the LCD touch panel 302 (step S705). When the confirmation button is operated, the CPU 307 uses the ticket issuing unit 304 and the payment processing unit 305 to issue a ticket according to the reservation information included in the authentication result message and to execute a ticket issuance and payment process to settle the ticket price (step S706), and ends the process.

[0064] Fig. 14 is a diagram showing an example of the alighting station input screen. The alighting station input screen 800 shown in Fig. 14 includes a message 801 prompting the user to input the alighting station, a cancel button 802 for interrupting the reservation transaction, and a key 803 for inputting the alighting station.

[0065] Fig. 15 is a diagram showing an example of a keyword voice input screen. The keyword voice input screen shown in Fig. 15 includes a message 811 for prompting input of a keyword by voice, a cancel button 812 for interrupting the ticket issuance and payment transaction, and an example word 813 which is guidance information for inducing recollection of a recovery word.

[0066] As described above, according to this embodiment, the CPU 103 of the server 1 registers in the database 4 the reservation information corresponding to the designation information designating the ticket from the reservation terminal 2 and the voice data from the reservation terminal 2 in association with each other. The CPU 103 also authenticates the user based on the input voice data, which is the voice data from the ticket issuing terminal 2, and the registered voice data, which is the voice data registered in the database 4, and if the authentication is successful, transmits a ticket issuance request to the ticket issuing terminal 2 based on the reservation information corresponding to the registered voice data. Therefore, the user does not have to answer questions at the time of ticket issuance, but can simply input voice data at the time of reservation and ticket issuance to perform identity verification at the time of ticket issuance (user authentication), thereby reducing the effort required for identity verification at the time of ticket issuance.

[0067] In this embodiment, the CPU 103 of the server 1 checks the input voice data against a plurality of registered voice data, and if there is registered voice data that matches the input voice data, it determines that the user authentication is successful. Therefore, even if the user forgets the contents of the registered voice data, it is possible to recover it using other voice data.

[0068] Furthermore, in this embodiment, the reservation terminal 2 displays input request information that prompts the user to input a keyword as voice, so that appropriate data can be input as voice data.

[0069] Furthermore, in this embodiment, the input request information includes guidance information for inducing the user to recall a keyword, so that even if the user cannot think of a keyword, it is possible to allow the user to appropriately input voice data.

[0070] The above-mentioned embodiments of the present disclosure are illustrative examples for explaining the present disclosure, and are not intended to limit the scope of the present disclosure to only those embodiments. Those skilled in the art can implement the present disclosure in various other aspects without departing from the scope of the present disclosure. For example, the above-mentioned embodiments have been described in detail to clearly explain the present disclosure, and are not necessarily limited to those having all the configurations described. In addition, it is possible to add, delete, or replace other configurations with respect to a part of the configuration of the embodiment. In addition, information such as programs, tables, and files that realize each configuration can be recorded in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD. [Explanation of symbols]

[0071] 1: Server 2: Reservation terminal 3: Ticket issuing and settlement terminal 4: Database 101: Network connection unit 102: Memory 103: CPU 201: Network connection unit 202: Touch panel 202: LCD touch panel 203: Microphone 204: Memory 205: CPU 301: Network connection unit 302: LCD touch panel 303: Microphone 304: Ticket issuing unit 305: Settlement processing unit 306: Memory 307: CPU

Claims

1. A reservation system having a reservation terminal, a ticket issuing terminal, and a management device, The reservation terminal is acquiring, from a user, designation information for designating a ticket to be reserved and first voice data representing the voice of the user, and transmitting the designation information and the first voice data to the management device; The ticket issuing terminal includes: acquiring second voice data representing the voice of the user from the user, transmitting the second voice data to the management device, and when receiving a ticket issuance request from the management device, issuing the ticket in response to the ticket issuance request; The management device includes: registering reservation information indicating the reservation content of the ticket according to the designation information from the reservation terminal in association with the first voice data from the reservation terminal, authenticating the user based on the second voice data from the ticket issuing terminal and the registered first voice data, and if the authentication is successful, transmitting the ticket issuance request to the ticket issuing terminal based on the designation information corresponding to the first voice data; The first audio data is a plurality of pieces of audio data, The plurality of first voice data are voice data of different words, A reservation system in which the management device compares the second voice data with each of the multiple first voice data, and if there is any first voice data that matches the second voice data, determines that the authentication is successful.

2. The reservation terminal is The reservation system according to claim 1 , wherein input request information is displayed to prompt the user to input a word as the voice.

3. The reservation system according to claim 2 , wherein the input request information includes guidance information for inducing recall of the word.

4. The reservation system according to claim 1 , wherein the ticket is a transportation ticket.

5. A management device communicably connected to the reservation terminal and the ticket issuing terminal, receiving, from the reservation terminal, designation information designating a ticket reserved by a user and first voice data indicating the voice of the user, and registering the designation information and the first voice data in association with each other; when second voice data indicating the voice of the user is received from the ticket issuing terminal, authenticating the user based on the second voice data and the registered first voice data; If the authentication is successful, a ticket issuance request is sent to the ticket issuing terminal based on the designation information corresponding to the first voice data; The first audio data is a plurality of pieces of audio data, The plurality of first voice data are voice data of different words, In authenticating the user, the management device compares the second voice data with each of the multiple first voice data, and if there is first voice data that matches the second voice data, determines that the authentication is successful.

6. A reservation and ticket issuing method for a reservation system having a reservation terminal, a ticket issuing terminal, and a management device, comprising: the reservation terminal acquires, from a user, designation information for designating a ticket to be reserved and first voice data representing the user's voice, and transmits the designation information and the first voice data to the management device; the management device registers reservation information indicating the reservation content of the ticket according to the designation information from the reservation terminal in association with the first voice data from the reservation terminal; the ticket issuing terminal acquires second voice data indicating the voice of the user from the user and transmits the second voice data to the management device; The management device authenticates the user based on the second voice data from the ticket issuing terminal and the registered first voice data; if the authentication is successful, the management device transmits a ticket issuance request to the ticket issuing terminal based on the designation information corresponding to the first voice data; When the ticket issuing terminal receives the ticket issuing request from the management device, the ticket issuing terminal issues the ticket in response to the ticket issuing request; The first audio data is a plurality of pieces of audio data, The plurality of first voice data are voice data of different words, In authenticating the user, the management device compares the second voice data with each of the multiple first voice data, and if there is any first voice data that matches the second voice data, determines that the authentication is successful.

Images