JP4876928B2 - Ticketing device - Google Patents

Description

  The present invention relates to a ticket issuing device capable of issuing a ticket while communicating between a remote operator and a user.

In the conventional (remote) ticketing device, when the remote center side is congested and the operator cannot respond, the waiting user always occupies the ticketing device while waiting for a response from the operator (for example, patent Reference 1 and Patent Reference 2).
JP-A-8-50616 JP 2003-281573 A

  In the case of the prior art described above, while waiting for a response from the operator, the waiting user occupies the ticketing device all the time, and the users lining up to use the ticketing device simply wait. It was.

  The present invention has been made in view of the above points, and an object of the present invention is to provide a ticket issuing device that allows other users to use the ticket issuing device while waiting for a response from an operator.

  A ticketing device according to the present invention is a ticketing device that is connected to a center device through a communication line and has a ticketing machine that issues a ticket according to a user's ticketing operation, and includes an initial screen on which a plurality of ticket sales buttons are displayed. Via a display unit that displays various screens, an input unit for a user to issue a ticket, a communication unit that allows a user and an operator who operates the center device to interact by voice and video, and an input unit When an operator response request input requesting ticketing processing based on communication with the operator is performed, a communication unit that inquires whether the operator on the center device side is in a compatible state, and a response that the operator is compatible A control unit that displays an initial screen on the display unit and waits for another user's ticketing process while waiting for a response until receiving a response from the center device. It is intended.

  As described above, according to the present invention, while the user is waiting for the operator's response, the initial screen is displayed on the display unit to accept the ticketing operation. While waiting, other users can use the ticket issuing device.

Hereinafter, embodiments of a ticket issuing apparatus according to the present invention will be described with reference to the drawings.
Embodiment 1 FIG.
FIG. 1 is a block diagram showing the configuration of the entire system including the ticket issuing device according to Embodiment 1 of the present invention.
One or a plurality of ticket issuing devices 1 are installed in a ticket sales corner such as a station (only one is shown in FIG. 1), and the ticket issuing device 1 is a remote terminal as a center device located in a remote center via a communication line 2. 3 is connected. One or a plurality of remote terminals 3 (one in FIG. 1) are installed in the remote center, and these are operated by an operator. The ticket-issuing host computer 4 is connected to the ticket-issuing device 1 and the remote terminal 3 via the communication line 2 and exchanges data necessary for ticketing with these devices. The ticket issuing host computer 4 is provided with a database 4a for storing various tables including a processing time management table indicating the relationship between the time-consuming processing and various processing times among various ticketing processes.

  The ticket issuing apparatus 1 includes a display 10 as a touch panel screen and a display 10 as an input unit, a microphone 11, a speaker 12, a person camera 13 for photographing a user, and a sheet placed on a reading table (not shown). A document camera 14 for taking pictures, an input unit 15 such as a keyboard and a mouse, a ticketing machine 16 for issuing tickets (designated tickets, tickets, etc.), and a cash deposit / withdrawal unit 17 for settlement of the purchase price of tickets , A communication unit 18 for communicating with the remote terminal 3 via the communication line 2, a storage unit 19 for storing the control program and various programs, and a control unit 20 for controlling the entire ticketing apparatus 1. The communication unit of the present invention includes a microphone 11, a speaker 12, and a person camera 13 that captures a user.

  When an input operation for requesting remote ticket sales processing (operator handling processing) is performed on the display 10, the ticket issuing device 1 of this example calls the operator of the remote terminal 3, and the user and the operator use the video and audio. It is a device that can purchase tickets and the like while having a conversation. In addition, the ticket issuing operation can be performed not only by the user directly with the ticket issuing apparatus 1, but also by the operator acting on behalf of the user and remotely.

  The remote terminal 3 communicates with the ticket issuing device 1 via the display 30, the input unit (keyboard and mouse) 31, the microphone 32, the speaker 33, the person camera 34 for photographing the operator, and the communication line 2. Communication unit 35, a storage unit 36 that stores the control program and various programs, and a control unit 37 that controls the entire remote terminal 3.

  Hereinafter, the operation of the ticket issuing apparatus 1 according to the first embodiment will be described. The present invention is characterized in that while a user requests remote ticket sales and waits for an operator's response, other waiting users can use the ticket issuing device 1. Hereinafter, the flow at the time of remote ticket sales processing will be described. The following explanation will be given assuming that the user who first operated the ticketing apparatus 1 is the user A, and the user who is waiting for the use of the ticketing apparatus 1 next to the user A is the user B.

FIG. 2 is a flowchart showing a flow of processing in the ticket issuing apparatus according to the first embodiment of the present invention.
First, an initial screen 40 as shown in FIG. 3 is displayed on the display 10 of the ticket issuing apparatus 1 (S1). The screen displayed on the display 10 is a screen that is divided into two parts in the vertical direction in this example, and a “remote ticket sales” button 41 and a message display area 42 for displaying various messages are provided in the upper area. The lower area is provided with a button area 43 in which a plurality of ticket sales buttons (such as a boarding amount button) for normal ticket sales, buttons for selecting options for remote ticket sales, and the like are arranged. In the initial screen 40 shown in FIG. 3, a message for requesting remote ticket sales, “Please press the left button when requesting a ticket from the station staff” is displayed in the message display area 42. The ticket sales buttons 43a to 43n necessary for normal (not remote ticket sales) ticket sales are arranged.

  When any button on the initial screen 40 is pressed by the user A (YES in S2), the control unit 20 of the ticket issuing apparatus 1 determines whether the pressed button is the “remote ticket sales” button 41 or not. If it is determined that the button is not the “remote ticket sale” button 41 (NO in S3), a ticket sale process corresponding to the pressed button is executed (S4), and after completion of the process, the display returns to the initial screen 40 ( S1).

  On the other hand, when the “remote ticket sales” button 41 is pressed (corresponding to an operator request input) (YES in S3), it is determined whether the operator of the remote terminal 3 is ready for handling (S5). In this determination, first, the communication unit 18 inquires the remote terminal 3 via the communication line 2 as to whether the operator can handle the remote ticket sales request. When the remote terminal 3 receives the inquiry from the ticket issuing device 1, the remote terminal 3 notifies the operator that a request for remote ticket sales has been received from the ticket issuing device 1 by display on the display 30 or voice output from the speaker 33 or the like.

  If there is a vacant operator, the operator inputs from the input unit 31 of the remote terminal 3 that he / she can respond to the request. As a result, the remote terminal 3 responds to the ticket issuing device 1 to the effect that it can respond. Upon receiving this response, the ticket issuing apparatus 1 determines that the operator can respond (YES in S5), and performs an operator response process (remote ticket selling process) (S6). That is, the ticket issuing device 1 controls each part (display 10, microphone 11, speaker 12, and person camera 13) in the ticket issuing device 1 so that it can communicate with the operator on the remote terminal 3 side. Perform ticketing process. Similarly, the respective units (display 10, microphone 11, speaker 12, and person camera 13) are also controlled on the remote terminal 3 side. In the remote ticket sales process, the user A may operate the ticket issuing device 1 according to the operator's instruction, or the operator may operate the ticket issuing device 1 remotely from the remote terminal 3 while communicating with the user A. Ticketing may be performed.

  In the determination of whether or not the operator can be handled in step S5, if the operator cannot be handled (NO in S5), that is, if there is no vacant operator, the control unit 20 of the ticket issuing apparatus 1 until the operator can handle it. A question screen for asking the user whether to wait is displayed on the display 10 (S7). FIG. 4 shows an example of the question screen. In the question screen 50, a message asking whether to wait for the user is displayed in the message display area 42, and a “wait” button 51 and a “do not wait” button 52 are shown in the button area 43. When the user who confirms the question screen 50 presses the “do not wait” button 52 (NO in S8), the display returns to the initial screen 40 in step S1, and when the “wait” button 51 is pressed ( A confirmation screen 60 instructing to wait near the ticket issuing apparatus 1 is displayed to the user A who is currently operating as shown in FIG. 5 (S9).

  The confirmation screen 60 in FIG. 5 displays a message for instructing the user A to wait near the ticket issuing device 1 and a confirmation button that states “Wait the operation to the next person and wait” 61 is displayed. When the confirmation button 61 is pressed by the user A who has confirmed the confirmation screen 60 (YES in S10), the control unit 20 of the ticket issuing apparatus 1 displays an initial screen when there is a user waiting for a response from the operator. It is displayed (S11).

FIG. 6 shows an example of the initial screen.
On the initial screen 70, a message indicating that there is a person waiting for a response from the operator is displayed in the message display area 42, and various ticket sales buttons 71a to 71n are displayed in the button area 43. Here, the ticket sales buttons displayed (or activated) in the button area 43 may be the same as the ticket sales buttons 43a to 43n on the initial screen 40 shown in FIG. 3, but on the initial screen 70 in FIG. The button 43a is omitted to reduce the number of buttons. Since the user A is currently waiting for the operator's response at the time when the initial screen 70 is displayed, the process button is excluded so that a time-consuming process cannot be selected. In such a button exclusion process, the control unit 20 accesses the ticketing host computer 4, refers to the processing time management table stored in the database 4a, and excludes the buttons registered in the processing time management table. This is realized by configuring the button area 43. FIG. 7 shows an example of the processing time management table of the ticketing host computer 4. In this processing time management table, for each button name, an estimated time required for processing specified by the button name is stored.

  When the display of S11 is completed, the control unit 20 checks whether or not the operator can respond at regular time intervals by communication with the remote terminal 3 similar to step S5 (S12), and can respond. If not (NO in S12), it is checked whether any of the ticket sales buttons 71a to 71n on the initial screen 70 has been pressed. If it has been pressed (YES in S13), the pressed ticket sales button is displayed. The corresponding ticket selling process is executed (Sl4), and then the screen returns to the initial screen 70 of FIG. On the other hand, if the ticket sales buttons 71a to 71n are not pressed (NO in S13), the initial screen 70 of FIG. 6 is continuously displayed until the operator can respond.

  When the control unit 20 receives a response indicating that the operator is available from the remote terminal 3 and determines that the operator is available (YES in S12), the control unit 20 displays a remote ticket sale start confirmation screen ( S15). FIG. 8 shows an example of the remote ticket sale start confirmation screen 80. On the remote ticket sales start confirmation screen 80, a message instructing the user A waiting for remote ticket sales to give up the operation and a “start remote ticket sales” button 81 are displayed.

  When the “remote ticket sales start” button 81 on the remote ticket sales start confirmation screen 80 is pressed within a predetermined time (YES in S16), the control unit 20 of the ticket issuing apparatus 1 performs an operator corresponding process (remote ticket sales process). (S6). That is, as described above, the ticket issuing device 1 controls each part (the display 10, the microphone 11, the speaker 12, and the person camera 13) in the ticket issuing device 1, and the user A and the operator communicate using video and audio. However, the ticket can be issued and issued. When the process is completed, the process returns to step S1, and the control unit 20 displays the initial screen 40 shown in FIG. 3 (Sl). In step S16, if the “remote ticket sales start” button 81 is not pressed within the determined time (NO in S16), it is determined that the user A has left without waiting, and step S6 is omitted. Then, the process returns to step S1, and the initial screen 40 is displayed (S1).

  As described above, according to the first embodiment, while the user is waiting for the operator's response, the initial screen is displayed on the display 10 to accept another user's ticketing process. Other users can use the ticket issuing apparatus 1. As a result, the operating rate of the ticket issuing apparatus 1 is increased, and the waiting time of the user as a whole is reduced. In addition, a reduction in the number of installed ticketing devices 1 can be expected.

Embodiment 2. FIG.
In the ticket issuing apparatus 1 according to the first embodiment, when another user B is about to perform an operation and the operator can respond to the user A, the operation is transferred to the waiting user A. The user B is notified of the instruction by a message displayed on the display 10. The user B may be hesitant about such a mechanical response of the ticket issuing device 1. The second embodiment has been made in view of such a point, and instead of the mechanical response of the ticket issuing apparatus 1, the operator B notifies the user B.

  Since the ticket issuing device 1 according to the second embodiment has the same device configuration as that of the first embodiment, illustration and description thereof are omitted.

FIG. 9 is a diagram showing a flow of processing in the ticket issuing apparatus according to the second embodiment of the present invention. Here, the description of the same processing as in the first embodiment will be omitted, and the second embodiment will be described focusing on the differences from the first embodiment.
In the first embodiment, when the user A who has requested remote ticket sales gives up the operation of the ticket issuing device 1 to the next user B and the operator becomes able to respond (YES in S12 of FIG. 9), FIG. The remote ticket sale start confirmation screen 80 is displayed, and a message instructing the user B to transfer the operation to the user A is displayed. However, the ticket issuing apparatus 1 according to the second embodiment can handle the operator. If this is the case (YES in S12 of FIG. 9), a remote ticket sale activation message 90, for example, as shown in FIG. 10 is displayed (S21), and the operator handling process is immediately implemented (S6). It is what you do. That is, the operator of the ticket issuing device 1 and the operator of the remote terminal 3 are in a communicable state, and the operator is encouraged to change the operation of the ticket issuing device 1.

  Thus, according to the second embodiment, when the next user B is about to operate while the first user A is waiting for an operator response, the operator response to the user A is When it becomes possible, the operator handling process is automatically started and the operator is prompted to give up the operation to the waiting user A, so that the user's habit can be moderated.

Embodiment 3 FIG.
In the first and second embodiments, only one person can wait for the operator's response. In the third embodiment, a counter is provided so that a plurality of people can wait for the operator's response.

  The ticket issuing apparatus 1 according to the third embodiment has the same apparatus configuration as that of the first embodiment, and therefore illustration and description thereof are omitted.

FIG. 11 is a diagram showing a flow of processing in the ticket issuing apparatus 1 according to the third embodiment of the present invention. Here, the operation will be described by taking as an example a case where two users, user A and user B, desire remote ticket sales processing in succession while the operator cannot respond. In the following, the third embodiment will be described with a focus on differences from the first embodiment shown in FIG.
First, the waiting number counter W is set to 0 (W = 0) (SA1). Thereafter, the initial screen 100 is displayed in step Sl. FIG. 12 shows an example of the initial screen 100. The initial screen 100 is a screen in which the current waiting number is additionally displayed with respect to the initial screen 40 of the first embodiment shown in FIG. As the waiting number displayed here, the number of waiting number counters W is used.

  Since the waiting number counter is now W = 0 (described later when W> 0), step SA2 is NO and the process proceeds to S2. The processing in steps S2 to S5 is the same as that in FIG. 3, and when the “remote ticket sales” button 41 is pressed on the initial screen 100, the control unit 20 checks whether the operator can respond (S5). Since it is not possible to respond here, a question screen 110 shown in FIG. 13 is displayed on the display 10 to ask the user A whether or not to wait until the operator becomes available. Here, if it is not known how many users are waiting for the operator, it is difficult to determine whether to wait. Therefore, as shown in FIG. 13, the value of W is substituted for the portion X in the figure, and the number of people waiting is also displayed. In this case, it is 0.

  Then, the user A confirming the question screen 110 presses the “wait” button 51 (YES in S8). As a result, one person waits, so the control unit 20 counts up the queue counter W (W = W + 1) (SA3), and displays the confirmation screen 60 of FIG. 5 (S9). When the confirmation button 61 is pressed by the user A confirming this screen (YES in S10), the control unit 20 of the ticket issuing apparatus 1 returns to step S1, displays the initial screen 100, and is newly created by another user. Until the button is pressed (S2), the operator continues to check whether the operator can respond (SA2).

  If the “remote ticket sales” button 41 on the initial screen 100 is pressed by another user B while the operator is not available (S3), the number of people waiting is increased by one. 20 counts up the queue counter W (W = W + 1) (SA3), and displays a confirmation screen 60 instructing the user B to wait near the ticket issuing device 1 (S9). When the confirmation button 61 on the confirmation screen 60 is pressed (S10), an initial screen 100 indicating that there are two people waiting is displayed on the display 10 (S1).

  After the initial screen 100 is displayed, the ticket issuing apparatus 1 processes button processing other than remote ticket sales in response to a request from the user until the operator becomes available (SA2). Meanwhile, user A and user B wait until the operator becomes available. When the operator becomes available (NO in SA2), the control unit 20 checks the waiting number counter W, and if W is larger than 0 (SA4), the waiting number counter W is counted down (SA5). A ticket sales start confirmation screen 80 (see FIG. 8) is displayed (S15) to prompt the user A to confirm the start of remote ticket sales. If the “remote ticket sales start” button 81 is pressed within a predetermined time (S16), an operator response process (remote ticket sales process) is performed (S6), and the process returns to step S1 to return to the initial screen 100. Is displayed. In this example, since there is another user B waiting, since W> 0 in step SA2, the processing in steps SA5, S15, S16, and S6 is performed again to perform the operator handling processing (remote ticket sales processing). To do. On the other hand, if the “remote ticket sales start” button 81 is not pressed within a predetermined time (NO in S16), it can be determined that all the waiting users have left, so the waiting number counter W is set to 0 again. (SAl).

  As described above, according to the third embodiment, substantially the same operational effects as those of the first and second embodiments can be obtained, and the counter is provided, so that a plurality of users can perform the operator handling process (remote ticket selling process). You can wait.

Embodiment 4 FIG.
In the third embodiment, since the counter is simply provided to count the number of people, it is necessary for the users who actually wait to grasp the order. If the user makes a mistake in order, there is no means for confirming the order, which may cause trouble between users. In the fourth embodiment, in order to prevent this, a ticket with a unique number is sequentially issued to the waiting user, and the operator confirms this number at the time of calling, so that the operator can identify the waiting user in order. It is designed to be compatible.

  FIG. 14 is a block diagram showing a configuration of the entire system including the ticket issuing device according to the fourth embodiment of the present invention. The difference from Embodiment 1 shown in FIG. 1 is that the ticket issuing machine 16 issues a turn ticket 16a on which a ticket number is printed in addition to a ticket or the like. In the fourth embodiment, the one-dimensional FIFO queue shown in FIG. 15 is stored in the database 4a of the ticketing host computer 4.

  In the queue, the ticket numbers are stored in the order in which the sequential tickets 16a are issued from the ticket issuing machine 16. When the operator becomes available, the ticket number is taken out from the queue, and the user who has the turn ticket 16a with the ticket number responds.

FIG. 16 is a flowchart showing a flow of processing in the ticket issuing apparatus according to the fourth embodiment of the present invention. Here, the operation will be described by taking as an example a case in which two users, user A and user B, wish to perform an operator-corresponding process (remote ticket selling process) continuously while the operator cannot respond. Hereinafter, the difference between the fourth embodiment and the third embodiment will be mainly described.
First, in step SB1, the control unit 20 of the ticket issuing apparatus 1 connects to the database 4a of the ticket issuing host computer 4 via the communication line 2 to initialize (empty) the queue. When the “remote ticket sales” button 41 on the initial screen 100 is pressed by the user A, the control unit 20 generates a unique number for uniquely identifying the user A and prints the number. The ordered ticket 16a is instructed to be issued to the ticket issuing machine 16 (SB2). Then, the control unit 20 transmits the number to the ticket issuing host computer 4 via the communication line 2 and registers it in the queue. Thereafter, as shown in FIG. 17, a confirmation screen 120 for instructing to take the turn ticket 16a and wait near the ticket issuing apparatus 1 is displayed (S9).

  If the “remote ticket sale” button 41 on the initial screen 100 is pressed by another user B while the operator is not available (S3), the user B is uniquely identified as described above. A unique number is generated, the turn ticket 16a printed with the number is instructed to be issued to the ticket issuing machine 16, and the number is registered in the queue in the same manner as described above. At this time, the user A number and the user B number are registered in the queue. Thereafter, a confirmation screen 120 (see FIG. 17) is displayed (S9).

  When the operator becomes available (YES in S5), the number is extracted from the queue (SB4), and the remote ticket sale start confirmation screen 80A is displayed based on the extracted number (S15A). FIG. 18 shows an example of the remote ticket sale start confirmation screen 80A. On the remote ticket sales start confirmation screen 80A, the ticket number of the user A who has been waiting for remote ticket sales is displayed, and a message instructing the user A to transfer the operation to the ticket number is displayed, and "start remote ticket sales" Button 81 is shown.

  Then, when the “remote ticket sale start confirmation” button 81 on the remote ticket sale start confirmation screen 80A (see FIG. 18) is pressed within the determined time, the number taken out from the queue, that is, the user to be dealt with (here, the user) It is confirmed that the number A) is the same as the number read from the turn ticket 16a (SB5). This confirmation may be performed by the operator on the remote terminal 3 side or automatically on the ticket issuing device 1 side. When performing on the remote terminal 3 side, as soon as the “remote ticket sales start confirmation” button 81 is pressed, the ticket issuing device 1 and the remote terminal 3 are connected in a state capable of handling an operator, and confirmation is performed by the operator. That is, the operator instructs the user to place the turn ticket 16a on a reading table (not shown) of the ticket issuing device 1, and when the turn ticket 16a is placed on the reading table in accordance with the message, the document camera 14 An image of the photographed turn ticket 16a is displayed on the display 10 of the remote terminal 3, and is visually confirmed by the image. On the other hand, the remote terminal 3 accesses the database 4a of the ticketing host computer 4 via the communication line 2, retrieves the number from the queue, and obtains the number of the user to be dealt with (here, user A). It is confirmed that the number and the number of the turn ticket 16a visually confirmed are the same. And ticket sale processing is implemented on it (SB5).

  Here, since user B is still waiting and the waiting number counter W = 1, the answer is YES in step SA2, and the operator handling process for user B (remote ticket selling process) is performed in the same manner as described above. To implement.

  As described above, according to the fourth embodiment, the turn ticket 16a is handed over to the user who waits for the operator to be available, and the ticket sale processing is performed after the operator confirms the turn ticket 16a. Users can be handled in the order in which they were waiting.

Embodiment 5 FIG.
In the first to fourth embodiments, it is not assumed that the user operates a normal ticket sales button and does not understand the operation while the ticket sales procedure is proceeding, and presses the “remote ticket sales” button 41. The fifth embodiment is intended to improve the operation efficiency in such a case.

  The ticket issuing apparatus 1 according to the fifth embodiment has the same apparatus configuration as that of the first embodiment, and therefore illustration and description thereof are omitted. In the fifth embodiment, the state holding queue for storing the state data of the ticket issuing device 1 for each ticket number is stored in the database 4a of the ticket issuing host computer 4.

FIG. 19 is a diagram showing the configuration of the state holding queue.
In the state holding queue, state data is registered together with the ticket number in the state holding queue in order from the top, and when there is a take-out request, it is removed in order from the top.

FIG. 20 is a diagram showing a flowchart showing a flow of processing of the ticket issuing apparatus according to the fifth embodiment of the present invention. Here, the description of the same processing as that of the fourth embodiment will be omitted, and the description will focus on the differences of the fifth embodiment from the fourth embodiment.
In the fifth embodiment, the state holding queue is initialized in step SC1, and the user is informed that the operation is lost during the ticket sales procedure by operating the ticket sales buttons 71a to 71n on the display 10. When the “remote ticket sales” button 41 is pressed (YES in S3) and the operator is not available at that time (NO in S5), the control unit 20 instructs the ticket issuing machine 16 to give the user the turn ticket 16a. Current status data of the ticket issuing device 1 together with the number of the issued sequential ticket 16a (procedure data performed by the user from the input operation on the initial screen 40 until the “remote ticket sales” button 41 is pressed) Are stored in the state holding queue of the database 4a of the ticketing host computer 4.

  When the operator can respond (YES in S5) and the user presses the “remote ticket sales start” button 81 (see FIG. 7) (YES in S16), the controller 20 issues the ticket issuing host computer. 4 is accessed to retrieve state data from the state holding queue (SC3). Then, it is confirmed by performing data communication with the remote terminal 3 that the number in the retrieved state data and the number of the user's turn ticket 16a are the same, and the ticket issuing device 1 is based on the retrieved state data. After the state is restored to the state when the “remote ticket sale” button 41 is pressed, the ticket sale process is executed (SC4).

  As described above, according to the fifth embodiment, the status data of the ticket sales procedure proceeded halfway is registered in the status holding queue for each number of the turn ticket 16a allocated to the user, and the operator can respond. When the user is called to start remote ticket sales, the status data is acquired based on the ticket number, and the ticket issuing device 1 is restored to the state when the “remote ticket sales” button 41 is pressed. So, you can resume the ticket sales procedure from the middle. This enables efficient remote ticket sales without wasting user input.

Embodiment 6 FIG.
In the first to fifth embodiments, each device (microphone 11, speaker 12, person camera 13, document camera 14) as communication means necessary for handling the operator is provided in the ticket issuing device 1. However, in actual operation of the ticket issuing apparatus 1, the ticket issuing apparatus 1 having a device configuration excluding communication means is already installed in a station, for example. Therefore, in the sixth embodiment, an embodiment in which a new operator support function (remote ticket selling function) is added to the already installed ticket issuing apparatus 1 will be described.

FIG. 21 is a diagram illustrating a ticket issuing device on the ticket sales corner side according to the fifth embodiment. In FIG. 21, the same parts as those in FIG.
In the figure, reference numeral 200 denotes a remote unit, and the remote unit 200 includes various devices (microphone 11, speaker 12, person camera 13, document camera 14) as communication means necessary for remote ticket sales. The ticket issuing device 1 and the remote unit 200 are connected by a communication line 201a so that they can communicate with the ticket issuing host computer 4 and the remote center 5, respectively. Note that these devices are removed from the ticket issuing device 1 because the microphone 11, the speaker 12, the person camera 13, and the document camera 14 are attached to the remote unit 200. The ticket issuing device 1 and the remote unit 200 can be operated independently.

FIG. 22 is a diagram showing a screen configuration displayed on the display of the ticket issuing apparatus.
In the sixth embodiment, the upper area of the screen is a remote unit display area 210a for inputting and displaying the remote unit 200, and the lower area is a ticket machine display area 210b for inputting and displaying the ticket issuing apparatus 1. Both buttons and message displays are displayed in their respective areas. For example, the ticket sales buttons 43a to 43n in FIG. 3 are displayed in the ticket machine display area 210b, and the displays in FIGS. 4, 5, and 7 are displayed in the remote unit display area 210a. As a result, the ticket selling function and the remote ticket selling function can separately operate by performing input / output separately. When it is necessary to operate in cooperation, necessary information is transmitted / received via the communication line 201a.

  As described above, when the screen configuration is divided between the remote unit 200 side and the ticket issuing device 1 side, when adding a screen related to the remote ticket selling function to the screen of the existing ticket issuing device 1, a program for screen control of the existing ticket issuing device 1 It is possible to cope with this by adding a program related to the remote ticket selling function without drastically changing the password. Therefore, it is possible to simplify the program development related to screen control when adding the remote ticket selling function to the existing ticket issuing device.

Although the embodiment has been described above, the present invention is not limited to this, and can be appropriately changed as follows.
A handset or a headset may be used instead of the microphone 11 and the speaker 12.
While the operator is handling in the operator handling process in step S6, the ticket issuing button in the button area may be kept valid (displayed) or may be invalidated (erased).
-While the response by the operator is being performed, the operation of the ticket issuing apparatus 1 may be performed by the operator from a remote location, or the user may perform the operation himself / herself under the instruction of the operator.

-The display 10 of the ticket issuing apparatus 1 does not need to be a touch panel type. The “remote ticket sale” button 41 may be a hardware button, and each button in the button area may be a hardware button. You may make it display the display of the message display area 42 on the apparatus which can perform only a display.

When each button in the button area is a hardware button, it is necessary to switch the invalidity / validity of each button as appropriate so that no button operation input is accepted except when necessary.
The database 4 a that is in the ticketing host computer 4 may be installed in the ticketing device 1.
When the initial screen 70 is displayed when there is a user waiting for a response from the operator in step S11, the processing that can be selected by the user is limited as shown in FIG. It is good also as a structure which changes the transaction display which can be handled according to this restriction | limiting (for example, deletes the display of the transaction which is no longer handled).

In the second embodiment, step S9 and step S10 may be executed as one step. In that case, the display corresponding to FIG. 4 and the display corresponding to FIG. 5 are displayed on one screen.

In the fourth embodiment, the ticket number is “unique number”, but it is sufficient if the order among a plurality of users can be determined. For example, when the number increases from 1 to reach a certain number It may be a cyclic numbering system that starts from 1 again.
Similarly, in the fourth embodiment, when step S16 is NO, the next waiting user is called and the skipped user is not called again. It is good also as a structure which calls again after progress of a period.

In the fifth embodiment, the remote function is separated from the ticket issuing device 1 to form a separate unit as the remote unit 200. However, devices such as the microphone 11, the speaker 12, the person camera 13, and the document camera 14 are the same as the ticket issuing device 1. Either remote unit 200 or both may be present. This is because information can be exchanged via the communication line 201a.

As a means for acquiring the number written on the turn ticket 16a from the turn ticket 16a, a scanner, an OCR, or a reader such as magnetism or non-contact can be used in addition to the camera.

It is a block diagram which shows the whole system structure provided with the ticket issuing apparatus in Embodiment 1 of this invention. It is a flowchart which shows the flow of a process in the ticket issuing apparatus of Embodiment 1 of this invention. It is a figure which shows an example of an initial screen. It is a figure which shows an example of a question screen. It is a figure which shows an example of a confirmation screen. It is a figure which shows an example of an initial screen when there exists a user waiting for the response by an operator. It is a figure which shows an example of a processing time management table. It is a figure which shows an example of the remote ticket sale start confirmation screen of Embodiment 1. FIG. It is a figure which shows the flow of a process in the ticket issuing apparatus of Embodiment 2 of this invention. It is a figure which shows an example of a remote ticket sale starting screen. It is a figure which shows the flow of a process in the ticket issuing apparatus of Embodiment 3 of this invention. FIG. 10 is a diagram illustrating an example of an initial screen according to the third embodiment. FIG. 10 is a diagram illustrating an example of a question screen according to the third embodiment. It is a block diagram which shows the structure of the whole system provided with the ticket issuing apparatus of Embodiment 4 of this invention. It is a figure which shows a queue. It is a flowchart which shows the flow of a process in the ticket issuing apparatus of Embodiment 4 of this invention. FIG. 10 is a diagram illustrating an example of a confirmation screen according to a fourth embodiment. It is a figure which shows an example of the remote ticket sale start confirmation screen of Embodiment 4. FIG. It is a figure which shows the structure of a state holding queue. It is a figure which shows the flowchart which shows the flow of a process in the ticket issuing apparatus of Embodiment 5 of this invention. It is a figure which shows the ticket issuing apparatus by the side of the ticket sales corner of Embodiment 6. FIG. It is a figure which shows the screen structure displayed on the display of the ticket issuing apparatus of Embodiment 6. FIG.

Explanation of symbols

  1 ticketing device, 2 communication line, 3 remote terminal, 4 ticketing host computer, 4a database, 5 remote center, 10 display, 11 microphone, 12 speaker, 13 person camera, 14 document camera, 15 input unit, 16 ticketing machine, 16a turn ticket, 17 cash deposit / withdrawal unit, 18 communication unit, 19 storage unit, 20 control unit, 30 display, 31 input unit, 32 microphone, 33 speaker, 34 person camera, 35 communication unit, 36 storage unit, 37 control unit , 40 Initial screen, 41 “Remote ticket sale” button, 42 Message display area, 43 button area, 43a-43n Ticket sale button, 50 Question screen, 51 “Wait” button, 52 “Do not wait” button, 60 Confirmation screen, 61 Confirmation Button, 70 initial screen, 71a-71n ticket sales button, 80, 8 0A Remote ticket sale start confirmation screen, 81 “Remote ticket sale start” button, 90 Remote ticket sale start screen, 100 Initial screen, 110 Question screen, 120 Confirmation screen, 200 Remote unit, 201a Communication line, 210a Remote unit display area, 210b Ticket vending machine Display area.

Claims (12)

A ticketing device that is connected to the center device through a communication line and includes a ticketing machine that issues a ticket according to a user's ticketing operation,
A display unit for displaying various screens including an initial screen on which a plurality of ticket sales buttons are displayed;
An input unit for users to issue tickets;
A communication unit that enables dialogue between a user and an operator who operates the center device by voice or video;
When an operator response request is input through the input unit to request ticketing processing based on communication with an operator, the communication unit inquires whether the operator on the center device side is in a state capable of handling,
A control unit that displays an initial screen on the display unit and waits for another user's ticketing process while waiting for a response until the response indicating that the operator is available is received from the center device. Characteristic ticketing device.   The control unit displays a question screen on the display unit for asking the user whether to wait or not to wait until the operator on the center device side is ready for the response while waiting for the response. 2. The ticket issuing apparatus according to claim 1, wherein when an input for waiting is made, an initial screen when there is a user waiting for a response by an operator is displayed on the display unit.   3. The ticket issuing apparatus according to claim 2, wherein the initial screen when there is a user waiting for a response by an operator is a screen excluding a ticket sales button for processing that takes time to issue a ticket.   After receiving an input indicating waiting from the input unit, the control unit displays a start instruction button for instructing start of communication when a response indicating that the operator is available is received from the center device. 4. The ticket issuing device according to claim 2, wherein the start confirmation screen is displayed on the display unit, and the communication unit is activated when the start instruction button is pressed.   After receiving an input to wait from the input unit, when receiving a response from the center device that the operator is available, the control unit is a user other than the waiting user. Whether or not the ticket issuing process is being executed is checked. If the ticket issuing process is being executed, the communication unit is activated immediately after the ticket issuing process is completed. Item 3. Ticketing device.   A counter is provided for counting the number of users waiting until the operator can respond, and the control unit can repeat the ticketing process based on communication with the operator by the counter value of the counter. The ticket issuing device according to any one of claims 1 to 5.   The ticket issuing device according to any one of claims 2 to 6, wherein the control unit also displays a counter value of the counter on the question screen.   The control unit generates a unique identification number for a user who waits until the operator becomes available, manages the waiting order of the user based on the identification number, and issues a ticket based on communication with the operator according to the waiting order. The ticket issuing apparatus according to any one of claims 2 to 7, wherein processing is performed.   The ticket issuing apparatus according to claim 8, wherein the control unit causes the ticket issuing machine to issue a turn ticket on which the identification number is printed.   10. The ticket issuing apparatus according to claim 9, further comprising means for acquiring an identification number printed on the turn ticket from the turn ticket.   11. A screen for normal ticketing processing and a screen for ticketing processing based on communication with an operator are configured separately and displayed on the display unit. Ticketing equipment.   The control unit, when a ticket sales button is operated and the operator response request is input while the ticket sales procedure is in progress, the procedure performed by the user from the initial screen until the operator response request is input Is stored in the database, and when the operator becomes ready to handle the operator, the state of the ticketing device is restored to the state when the ticketing process by communication is requested based on the data stored in the database. The ticket issuing device according to any one of claims 1 to 11, wherein each unit is controlled.

Images