Information processing device, program, and information processing method
The information processing device manages waiting lists by setting time slot limits and generating display images to prevent store overcrowding and improve visitor prediction.
Patent Information
- Application Number
- JP2020181446
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-10-29
- Publication Date
- 2024-12-04
- Estimated Expiration
- 2040-10-29
AI Technical Summary
Existing queue management systems fail to address the issue of congestion caused by users making reservations while waiting in line, leading to increased visitor numbers and store overcrowding.
An information processing device that sets an upper limit for the number of waiting groups associated with a time slot, determines if the limit is reached, and generates display images to manage waiting lists effectively.
The system disperses user visits by time slot, preventing store congestion and allowing staff to better predict visitor numbers, while enabling efficient waiting list management and seat availability distribution.
Smart Images

Figure 0007594276000001 
Figure 0007594276000002 
Figure 0007594276000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to an information processing device, a program, and an information processing method. [Background technology]
[0002] There is a system that accepts the queue of users (customers) waiting to use a store (facility). Patent Document 1 aims to "provide a queue management system for presenting and managing waiting times to customers who are waiting in line" and discloses the following technology: "A queue management system 1 for managing waiting in a facility includes a content registration means 3 that registers service contents linked to required times, an element registration means 5 that registers service provision elements, a reception means 9 that receives a selection of desired service contents from customers, and a calculation means 8 that calculates a waiting time until the service is provided to the customer by using the required times linked to the service contents received by the reception means" (see the abstract of the document). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2019-46091 A Summary of the Invention [Problem to be solved by the invention]
[0004] In the above-mentioned Patent Document 1, an accurate waiting time can be calculated based on the time required for the service content desired by the customer, and can be presented to the customer. However, depending on the type of store, many users may be able to make reservations for waiting in line at the same time, and in such cases, the number of users visiting the store may increase, causing congestion.
[0005] Therefore, the present disclosure provides a technique for dispersing users who wish to wait their turn. [Means for solving the problem]
[0006] In order to solve the above problem, the information processing device disclosed herein is an information processing device that accepts users' waiting in line at a facility, and is characterized in having a first judgment means for determining whether an upper limit for the number of groups waiting in line associated with a time period is set, an identification means for identifying a time period on the day in which the number of groups waiting in line has not reached the upper limit, and a generation means for generating a display image for accepting the waiting in line depending on the results of processing by the first judgment means and the identification means.
[0007] Further features related to the present disclosure will become apparent from the description of the present specification and the accompanying drawings. Also, the aspects of the present disclosure are achieved and realized by the elements and combinations of various elements and the following detailed description and the appended claims. The description of the present specification is merely exemplary and is not intended to limit the scope or application of the present disclosure in any way. Effect of the Invention
[0008] According to the technology of the present disclosure, it is possible to distribute users who wish to wait their turn. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiment. [Brief description of the drawings]
[0009] [Figure 1] 1 is a configuration diagram of a queue management system according to a first embodiment. [Diagram 2] 1A is a hardware configuration diagram of a queue management server, and FIG. 1B is a functional block diagram. [Diagram 3] FIG. 11 is a diagram illustrating an example of data stored in a database. [Figure 4] 1A is a hardware configuration diagram of a management terminal, and FIG. 1B is a functional block diagram thereof. [Diagram 5] 1A is a hardware configuration diagram of a reception terminal, and FIG. 1B is a functional block diagram thereof. [Figure 6] 1A is a hardware configuration diagram of a user terminal, and FIG. 1B is a functional block diagram thereof. [Figure 7] 13 is a schematic diagram showing a waiting condition setting screen displayed on the management terminal; FIG. [Figure 8] 13 is a schematic diagram showing an order management screen displayed on a management terminal. FIG. [Figure 9] 13 is a flowchart showing a method for determining a reception screen in the queue management server. [Figure 10] 11 is a flowchart showing a method for accepting a waiting reservation from a user terminal. [Figure 11] FIG. 4 is a schematic diagram showing a reception screen displayed on the reception terminal. [Figure 12] 11A to 11C are schematic diagrams showing transitions of waiting reservation screens displayed on the reception terminal. [Figure 13] FIG. 13 is a schematic diagram showing a reservation completion screen displayed on the reception terminal. [Figure 14] 1A is a schematic diagram showing a store list screen and a reception screen displayed on a user terminal. FIG. [Figure 15] FIG. 11 is a configuration diagram of a queue management system according to a second embodiment. [Figure 16] FIG. 11 is a diagram illustrating an example of a store table according to the second embodiment. [Figure 17] 13 is a flowchart showing a method for distributing vacant seat information in the queue management server. [Figure 18] 1A is a schematic diagram showing a store list screen, a reception screen, a list screen, and a non-reception screen displayed on a user terminal. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, the present embodiment will be described with reference to the drawings. The same components will be described with the same reference numerals. Note that the following embodiment does not limit the technology of the present disclosure, and all of the combinations of features described in the present embodiment are not necessarily essential to solving the above problem.
[0011] [First embodiment] <Example of queue management system configuration> In the first embodiment, a system is described that accepts waiting reservations from users (customers) who wish to use a store where seats and tables are installed and food and drink are served, and notifies a user terminal when each user's turn approaches or when it is their turn. In this specification, the term "user" refers to a group of customers waiting in line at a store, and includes both cases where the group consists of multiple people and cases where the group consists of only one person. In addition, the term "user terminal" refers to a user terminal owned by a user who has made a waiting reservation among a group of users.
[0012] FIG. 1 is a configuration diagram of a queue management system 1 according to a first embodiment. The queue management system 1 is a system that manages the queue of users in a store, and includes a queue management server 10, a management terminal 20, a reception terminal 30, a printer 40, and a user terminal 50. The queue management server 10, the management terminal 20, the reception terminal 30, and the user terminal 50 are interconnected via a network 60, such as the Internet. The management terminal 20 is placed in the store and operated by a store clerk, and displays a GUI screen for setting queue conditions and store information, and managing users who have made a queue reservation. The queue management server 10 is placed outside the store, and manages data related to queues received from the management terminal 20, the reception terminal 30, and the user terminal 50. The reception terminal 30 is placed in the store and accepts queue reservations from users who visit the store. The reception terminal 30 is, for example, a computer device such as a smartphone or a tablet, and is supported by a support stand at a height that allows the user to view the display screen. The printer 40 is placed in the store, for example, below the reception terminal 30, and is connected to the reception terminal 30. The printer 40 issues a numbered ticket on which the reception information of the user is printed when a waiting reservation of the user is accepted via the reception terminal 30. The user terminal 50 is, for example, a computer device such as a smartphone or a tablet, and is a terminal owned by a user of the service provided by the queue management system 1.
[0013] The queue management server 10 stores in a database data relating to waiting in line received from the management terminal 20, the reception terminal 30, and the user terminal 50. The queue management server 10 updates the database according to the data received from the management terminal 20, the reception terminal 30, and the user terminal 50, thereby managing the latest waiting situation (status) for each store in the database. Note that "latest" here can be based on the date and time of transmission by the management terminal 20, the reception terminal 30, and the user terminal 50.
[0014] A user who is going to visit any store can make a reservation for a waiting order at the store to the queue management server 10 via an application or browser installed on the user terminal 50. In response to the request, the queue management server 10 generates a reception screen to be displayed on the user terminal 50 based on the data related to the waiting order stored in the database. The queue management server 10 returns the generated reception screen to the user terminal 50 as a response. When the reception screen is displayed on the user terminal 50, the user can make a waiting order reservation by operating via the reception screen.
[0015] The queue management server 10 generates a reception screen to be displayed on the reception terminal 30 based on the data related to the waiting order stored in the database. A user visiting any store can make a waiting order reservation by operating the reception screen of the reception terminal 30. When a waiting order reservation is made from the reception terminal 30 or the user terminal 50, the queue management server 10 updates the database and transmits the data related to the waiting order to the management terminal 20.
[0016] <Example of the configuration of the queue management server 10> 2(a) is a hardware configuration diagram of the queue management server 10. The queue management server 10 comprises a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a storage device 14, and a communication device 15. The CPU 11 realizes the functions provided by the queue management server 10 by executing a program described later. The ROM 12 and RAM 13 hold data used by the CPU 11. The storage device 14 stores programs and databases described later. The communication device 15 communicates with the management terminal 20, the reception terminal 30, and the user terminal 50 via a network 60.
[0017] 2(b) is a functional block diagram of the queue management server 10. The queue management server 10 includes a communication control unit 111, an update unit 112, and a determination unit 113 as software modules (functions configured by various programs expanded in the internal memory of the CPU 11) executed by the CPU 11. For convenience of description, these modules may be described below as the subject of operations, but since it is the CPU 11 that actually executes these modules, the CPU 11 may also be the subject of operations.
[0018] The storage device 14 stores a database 141 as a storage unit. The database 141 manages a store table 142 including store information registered in advance, and a queue management table 143 including data related to waiting. The configurations of the store table 142 and the queue management table 143 will be described later. The communication control unit 111 receives the waiting conditions, store information, and waiting status of the store from the management terminal 20 via the communication device 15. The communication control unit 111 also receives a waiting reservation request and user information input at the time of reception reservation from the user terminal 50 via the communication device 15. The update unit 112 updates the store table 142 and the queue management table 143 based on the data received by the communication control unit 111. When the determination unit 113 receives a waiting reservation request from the user terminal 50, it determines a reception screen to be displayed on the user terminal 50. The communication control unit 111 transmits the reception screen determined by the determination unit 113 to the user terminal 50 via the communication device 15.
[0019] FIG. 3(a) is a diagram showing an example of a store table 142 stored in the database 141. The store table 142 is a data table for managing store information of a store that has introduced a service provided by the queue management system 1. The store table 142 has, as constituent items, for example, a store ID 1421, a store name 1422, a genre 1423, a store introduction 1424, an address 1425, a telephone number 1426, and an upper limit of the number of groups waiting for their turn for each time period 1427. One record in the store table 142 manages store information of one store. The store ID 1421 is an ID for identifying each store. The address 1425 is data indicating the address of the store or the address of the facility in which the store is located. The upper limit of the number of groups waiting for their turn for each time period 1427 is a set value of the upper limit of the number of groups that can be accepted to wait for their turn in any time period. Each store information recorded in the store table 142 is data input by a store clerk from the management terminal 20.
[0020] FIG. 3B is a diagram showing an example of a queue management table 143 stored in the database 141. The queue management table 143 is linked to the store ID 1421 of each store, and is a data table that manages reception information including user information of users who have made a waiting reservation. The queue management table 143 has, as configuration items, for example, a reception ID 1431, a reception number 1432, a waiting status 1433, a number of people 1434, a reception time 1435, a waiting time 1436, a telephone number 1437, and an email address 1438. One record of the queue management table 143 manages reception information of one group of users who have made a waiting reservation. The reception ID 1431 is an ID for identifying a user who has made a waiting reservation. The reception number 1432 is a number that is assigned to each user in the order in which the waiting reservation is accepted. The waiting status 1433 indicates the waiting status of each user. For example, if the user is guided into the store, it is "reception completed", if the user is being called, it is "calling", and if the call has not yet been made, it is blank. Although not shown in the figure, if the waiting reservation is canceled, the waiting status 1433 becomes "cancelled". The number of people 1434 is the number of users in one group, and is the number of people input by the user from the reception terminal 30 or the user terminal 50. The reception time 1435 indicates the time when the user can come to the store. The waiting time 1436 indicates the time that the user should wait from the time of making the waiting reservation until the reception time. The phone number 1437 and the email address 1438 are the phone number and email address of the representative of the group who made the waiting reservation. It is sufficient that any of the contact information of the representative is registered, and instead of the phone number 1437 and the email address 1438, SNS account information or the like may be used.
[0021] <Example of configuration of management terminal 20> FIG. 4(a) is a hardware configuration diagram of the management terminal 20. The management terminal 20 includes a CPU 21 (processing device), a display device 22, an input device 23, and a communication device 24. The CPU 21 controls each unit included in the management terminal 20. The communication device 24 communicates with the queue management server 10 via the network 60, and receives from the queue management server 10 a GUI screen for inputting queue conditions and store information, and a GUI screen for managing the queue status. The display device 22 displays the GUI screen received from the queue management server 10. The input device 23 is an interface used by the store clerk to input operation instructions to the management terminal 20. For example, the display device 22 and the input device 23 can be configured as an integrated unit using a touch panel or the like.
[0022] 4(b) is a functional block diagram of the management terminal 20. The management terminal 20 includes a storage unit 211, a communication control unit 212, a setting unit 213, and a display control unit 214 as software modules (functions configured by various programs expanded in the internal memory of the CPU 21) executed by the CPU 21. For convenience of description, these modules may be described below as the subject of operations, but since it is the CPU 21 that actually executes these modules, the CPU 21 may also be the subject of operations.
[0023] The storage unit 211 functions as an internal memory of the CPU 21. The communication control unit 212 communicates with the queue management server 10 via the communication device 24. Specifically, the communication control unit 212 receives a GUI screen from the queue management server 10. The setting unit 213 accepts the queue conditions, store information, and queue status input by the store clerk via the input device 23 and the GUI screen. The communication control unit 212 transmits the queue conditions, store information, and queue status input by the store clerk to the queue management server 10. The display control unit 214 controls the display of the display device 22. Specifically, the display control unit 214 displays the GUI screen received from the queue management server 10 on the display device 22.
[0024] <Configuration example of reception terminal 30> FIG. 5(a) is a hardware configuration diagram of the reception terminal 30. The reception terminal 30 includes a CPU 31 (processing device), a display device 32, an input device 33, and a communication device 34. The CPU 31 controls each unit included in the reception terminal 30. The communication device 34 communicates with the queue management server 10 via the network 60 and receives a reception screen from the queue management server 10. The display device 32 displays the reception screen received from the queue management server 10. The input device 33 is an interface used by a user to input operation instructions to the reception terminal 30. For example, the display device 32 and the input device 33 can be integrated into one unit using a touch panel or the like. The reception terminal 30 is connected to the printer 40 by wire or wirelessly, and transmits the numbered ticket data generated by the CPU 31 to the printer 40 via the communication device 34.
[0025] 5(b) is a functional block diagram of the receiving terminal 30. The receiving terminal 30 includes a storage unit 311, a communication control unit 312, a receiving unit 313, a display control unit 314, and an output control unit 315 as software modules (functions configured by various programs expanded in the internal memory of the CPU 31) executed by the CPU 31. For convenience of description, these modules may be described below as the subject of operations, but since it is the CPU 31 that actually executes these modules, the CPU 31 may also be the subject of operations.
[0026] The storage unit 311 functions as an internal memory of the CPU 31. The communication control unit 312 communicates with the queue management server 10 via the communication device 34. Specifically, the communication control unit 312 receives a reception screen from the queue management server 10. The reception unit 313 receives user information input by the user via the input device 33 and the reception screen. The communication control unit 312 transmits the user information input by the user to the queue management server 10 and receives reception information of a new user generated by the queue management server 10. The display control unit 314 controls the display of the display device 32. Specifically, the display control unit 314 displays the reception screen received from the queue management server 10 and a reservation completion screen generated by the queue management server 10 based on the reception information on the display device 32. The output control unit 315 generates numbered ticket data based on the reception information received from the queue management server 10. The communication control unit 312 transmits the numbered ticket data generated by the output control unit 315 to the printer 40 via the communication device 34. The printer 40 includes a ticket issuing unit 411, which prints (issues) the numbered ticket data received from the communication control unit 312.
[0027] <Configuration Example of User Terminal 50> 6(a) is a hardware configuration diagram of the user terminal 50. The user terminal 50 includes a CPU 51 (processing device), a display device 52, an input device 53, and a communication device 54. The CPU 51 controls each unit included in the user terminal 50. The communication device 54 communicates with the queue management server 10 via the network 60, transmits a request for a waiting reservation, and receives a reception screen from the queue management server 10. The display device 52 displays the reception screen received from the queue management server 10. The input device 53 is an interface used by the user to input operation instructions to the user terminal 50. For example, the display device 52 and the input device 53 can be configured integrally using a touch panel or the like.
[0028] 6(b) is a functional block diagram of the user terminal 50. The user terminal 50 includes a storage unit 511, a communication control unit 512, a reception unit 513, and a display control unit 514 as software modules (functions configured by various programs expanded in the internal memory of the CPU 51) executed by the CPU 51. For convenience of description, these modules may be described below as the subject of operations, but since it is the CPU 51 that actually executes these modules, the CPU 51 may also be the subject of operations.
[0029] The storage unit 511 functions as an internal memory of the CPU 51. The communication control unit 512 communicates with the queue management server 10 via the communication device 54. Specifically, when the user inputs an instruction to send a request for a waiting reservation via the input device 53, the communication control unit 512 sends the request to the queue management server 10. The communication control unit 512 also receives a reception screen from the queue management server 10. The reception unit 513 receives user information input by the user via the input device 53 and the reception screen. The communication control unit 512 transmits the user information input by the user to the queue management server 10 and receives reception information of a new user generated by the queue management server 10. The display control unit 514 controls the display of the display device 52. Specifically, the display control unit 514 displays on the display device 52 the reception screen received from the queue management server 10 and a reservation completion screen generated by the queue management server 10 based on the reception information.
[0030] <Example of GUI screen display on management terminal 20> FIG. 7 is a schematic diagram showing a waiting condition setting screen 221 displayed on the display device 22 of the management terminal 20. The condition setting screen 221 has a button 2211 ("ON" and "OFF") for selecting whether to set an upper limit number of waiting reservations, a tab 2212 for setting a time period for setting an upper limit of the number of waiting reservations to be accepted, a tab 2213 for setting the upper limit number of each time period, a tab 2214 for setting a timing for notifying a user that their turn is approaching, and a save button 2215. When a store clerk operates the condition setting screen 221, the setting unit 213 of the management terminal 20 transmits the input conditions to the queue management server 10 via the communication control unit 212. When the update unit 112 of the queue management server 10 receives the conditions, it updates the upper limit 1427 of the number of waiting groups for each time period in the store table 142. When the button 2211 is set to "OFF", for example, the tabs 2212 and 2213 become inactive.
[0031] In the tab 2212, the upper limit number of groups for waiting reservations is set for each hour, but the time period can be set arbitrarily, for example, every 0.5 hours, every 2 hours, etc. As another embodiment, instead of setting the upper limit number at a fixed time interval as in FIG. 7, the clerk may specify an arbitrary time period (start time and end time). As shown in the tab 2213, the upper limit number for each time period does not need to be set for all time periods, and for example, the upper limit number can be set only for time periods when congestion is expected, or only for time periods when there are few clerks. In addition, the same upper limit number does not need to be set for all time periods, and different upper limit numbers can be set for different time periods. In the tab 2214, as an example, it is set to notify the user when the turn is two groups ahead. The timing of the notification to the user is not limited to two groups ahead, and can be set arbitrarily.
[0032] FIG. 8(a) is a schematic diagram showing a queue management screen 222 displayed on the display device 22 of the management terminal 20. The queue management screen 222 has text 2221 indicating the number of waiting groups, text 2222 indicating the timing of notification to the user, reception information 2223 of the user who made the waiting reservation, operation buttons 2224, a reception end button 2225, and a collective cancellation button 2226. The reception information 2223 displays any of the items in the queue management table 143, and in the example of FIG. 8(a), "reception number", "queue status", "number of people", "reception time", and "reception method" are displayed. In the "reception method" column, if the user makes a waiting reservation from the user terminal 50, "Web" is displayed. If the user makes a waiting reservation from the reception terminal 30 and issues only a numbered ticket, "numbered ticket" is displayed. If the user makes a waiting reservation from the reception terminal 30 and enters a phone number, "phone number" is displayed. The end of reception button 2225 is clicked when no more waiting orders will be accepted, for example, when the store's business hours have ended or when it is time for the last order. When a store clerk clicks the operation button 2224 for a certain reception number, a screen for changing the "waiting status" is displayed. When a user makes a waiting reservation from the reception terminal 30 or the user terminal 50, the update unit 112 of the queue management server 10 updates the queue management table 143 and transmits the updated information to the management terminal 20. As a result, the display control unit 214 of the management terminal 20 adds a new reception information row to the reception information 2223.
[0033] FIG. 8(b) is a schematic diagram showing the queue management screen 222 with the queue status change screen 223 superimposed. FIG. 8(b) shows the change screen 223 when changing the "queue status" of reception number 12. The change screen 223 has a call button 2231, a reception completion button 2232, a cancel button 2233, and a save button 2234. When the store clerk clicks any one of the call button 2231, the reception completion button 2232, and the cancel button 2233, and then clicks the save button 2234, the setting unit 213 of the management terminal 20 transmits information indicating that the queue status has been changed to the queue management server 10 via the communication control unit 212. When the update unit 112 of the queue management server 10 receives the information indicating that the queue status has been changed, it updates the queue status 1433 in the queue management table 143 and transmits the updated information to the management terminal 20. As a result, the display control unit 214 of the management terminal 20 updates the “waiting status” of the reception information 2223.
[0034] When the store clerk clicks the call button 2231 and the save button 2234, a notification indicating that the user has been called is sent to the user terminal 50 according to the reception method. For example, if the reception method is "Web", the management terminal 20 sends a notification to the contact information registered by the user. For example, if the reception method is "phone number", the management terminal 20 sends an SMS to the phone number registered by the user. The store clerk can determine which user to call by referring to the text 2222 indicating the timing of notification to the user and the waiting status of the reception information 2223. As another embodiment, the management terminal 20 may automatically send (call) a notification to a user whose notification timing has arrived. When the user comes to the store and the guidance is completed, the store clerk clicks the reception completion button 2232 and the save button 2234. As a result, the reception information of the user who has been operated as reception completion is deleted from the list of reception information 2223.
[0035] If the called user does not come to the store and a predetermined time has passed since the time slot when the user reserved the waiting order, the store clerk can click the cancel button 2233 and the save button 2234 to cancel the waiting order reservation of the user. As a result, the reception information of the user for whom the cancellation operation has been performed is deleted from the list of reception information 2223. As another form, if the called user does not come to the store and the reception completion button 2232 is not operated even after a predetermined time has passed since the time slot when the user reserved the waiting order, the queue management server 10 or the management terminal 20 may automatically cancel the waiting order reservation of the user. In this case, the update unit 112 of the queue management server 10 changes the waiting status 1433 in the queue management table 143 to "cancelled". As described above, when canceling the waiting order reservation of the user, the queue management server 10 or the management terminal 20 may send a notification indicating the cancellation to the contact registered by the user. If there is a vacant seat when a predetermined time has passed since the time slot when the user reserved the waiting order and the user can be guided, the cancellation operation may not be performed.
[0036] <How to determine the reception screen> 9 is a flowchart showing a reception screen determination method in the determination unit 113 of the queue management server 10. The reception screen is a screen displayed on the user terminal 50, and is displayed to a user who is currently waiting in line at a store. This determination method is executed when the queue management server 10 receives a request to wait in line at a store from the user terminal 50. The request includes at least the store ID and the time the request was sent.
[0037] (Step S11) The determination unit 113 refers to the upper limit 1427 of the number of waiting groups for each time period in the shop table 142, and determines whether or not an upper limit is set for the number of waiting groups in the time period that includes the transmission time of the request from the user terminal 50. If an upper limit is set (Yes), the process proceeds to step S12. If an upper limit is not set (No), the process proceeds to step S14.
[0038] (Step S12) The judgment unit 113 refers to the queue management table 143 and counts the number of reception IDs 1431 whose queue status 1433 is "calling" or blank during the time period, i.e., the number of groups waiting for their turn. The judgment unit 113 judges whether the number of groups waiting for their turn during the time period has reached its upper limit. If the number of groups waiting for their turn has reached its upper limit (Yes), the process proceeds to step S13. If the number of groups waiting for their turn has not reached its upper limit (No), the process proceeds to step S14.
[0039] (Step S13) The determination unit 113 refers to the upper limit 1427 of the number of waiting groups per time slot in the store table 142 and the queue management table 143, and determines whether there is a time slot in the day after the time slot including the time when the request was received in which the number of waiting groups has not reached the upper limit. More specifically, the determination unit 113 determines whether there is a time slot in which the number of waiting groups has not reached the upper limit (is less than the upper limit), starting from the time slot immediately following the time slot including the time when the request was received. If there is a time slot in which the number of waiting groups has not reached the upper limit (Yes), the process proceeds to step S14. If there is no time slot in which the number of waiting groups has not reached the upper limit (No), the process proceeds to step S16.
[0040] (Step S14) The determination unit 113 refers to the order management table 143 and counts the number of waiting groups in the time slot in which waiting is proposed to the user. More specifically, when this step S14 is performed after step S11 or step S12, the determination unit 113 refers to the order management table 143 and counts the number of waiting groups in the time slot including the transmission time of the request from the user terminal 50. When this step S14 is performed after step S13, the determination unit 113 refers to the order management table 143 and counts the number of waiting groups for the time slot closest to the time slot including the time when the request was received, among the time slots in which the number of waiting groups is less than the upper limit.
[0041] (Step S15) The determination unit 113 generates a reception screen including the count result of the number of groups waiting in step S14 and the time period as text, and transmits it to the user terminal 50 via the communication control unit 111.
[0042] (Step S16) Since the number of groups waiting in line has reached the upper limit for all time slots on that day, the determination unit 113 generates an acceptance refusal screen indicating that the waiting in line cannot be accepted, and transmits this to the user terminal 50 via the communication control unit 111. The acceptance refusal screen includes text such as "You cannot make a reservation to wait in line today."
[0043] The above-mentioned determination method is also executed to determine the reception screen to be displayed on the display device 32 of the reception terminal 30. In this case, the reception terminal 30 transmits a request to update the reception screen to the queue management server 10 at any time interval. Upon receiving the request, the queue management server 10 executes the above-mentioned process and transmits a reception screen or a non-reception screen to the reception terminal 30.
[0044] <How to reserve your place on the waiting list from the reception terminal 30> FIG. 10 is a flowchart showing a method for making a reservation for waiting in line at the reception terminal 30. As shown in FIG.
[0045] (Step S31) The display control unit 314 displays a reception screen on the display device 32.
[0046] (Step S32) When a user visiting a store clicks the reception button on the reception screen, the reception unit 313 receives a signal indicating that the user has clicked the reception button on the reception screen, and transmits the signal to the queue management server 10 via the communication control unit 312.
[0047] (Step S33) The communication control unit 312 receives a reception method selection screen from the queue management server 10. The display control unit 314 displays the reception method selection screen on the display device 32. For example, a "Receive with numbered ticket" button and a "Receive with phone number" button are displayed on the reception method selection screen. When the reception unit 313 receives a signal indicating that the user has selected a reception method, it transmits the signal to the queue management server 10 via the communication control unit 312.
[0048] (Step S34) The communication control unit 312 receives a number-of-people input screen from the queue management server 10. The display control unit 314 displays the number-of-people input screen on the display device 32. When the reception unit 313 receives a signal indicating that the user has input the number of people, it transmits the signal to the queue management server 10 via the communication control unit 312.
[0049] (Step S35) In step S32, if the user selects "Accept with phone number", the communication control unit 312 receives a phone number input screen from the queue management server 10. The display control unit 314 displays the phone number input screen on the display device 32. When the acceptance unit 313 receives a signal indicating that the user has input a phone number, it transmits the signal to the queue management server 10 via the communication control unit 312. Note that in this step, a case where a phone number is input as an example of the user's contact information has been described, but an email address or SNS account information may also be input. In step S32, if the user selects "Accept with numbered ticket", this step S34 may be omitted.
[0050] (Step S36) The communication control unit 312 receives a final confirmation screen from the queue management server 10. The display control unit 314 displays the final confirmation screen on the display device 32. The number of people and the phone number entered in steps S34 and S35 are displayed in text on the final confirmation screen. The final confirmation screen also displays a reservation confirmation button for confirming the entered content, and a back button for changing the entered content.
[0051] (Step S37) The reception unit 313 judges whether or not the user clicks the reservation confirmation button on the final confirmation screen. If the reservation confirmation button is clicked (Yes), the process proceeds to step S38. If the back button on the final confirmation screen is clicked (No), the process returns to step S34.
[0052] (Step S38) The reception unit 313 transmits user information including the number of people and telephone number inputted in steps S34 and S35 and the time period (reception time) for which the waiting reservation was made to the queue management server 10 via the communication control unit 312. When the queue management server 10 receives the user information, it adds the reception information of the new reception ID to the queue management table 143. The queue management server 10 generates a reservation completion screen based on the added reception information and transmits it to the reception terminal 30. The display control unit 314 displays the reservation completion screen received from the queue management server 10 on the display device 32. The reservation completion screen displays, for example, the reception number and the reception time as reception information in text. The output control unit 315 generates numbered ticket data corresponding to the reservation completion screen and transmits it to the printer 40 via the communication control unit 312. The printer 40 issues a numbered ticket based on the received numbered ticket data. This completes the reception of the waiting reservation.
[0053] The method of making a reservation for waiting in line at the reception terminal 30 has been described above, but the method of making a reservation for waiting in line from the user terminal 50 is similar to the above. In this case, the above process is executed when the user terminal 50 transmits a request to the queue management server 10 and receives a reception screen from the queue management server 10. However, when making a reservation for waiting in line from the user terminal 50, step S33 and the issuing of the numbered ticket in step S38 can be omitted.
[0054] <Example of GUI screen display on reception terminal 30> FIG. 11 is a schematic diagram showing a reception screen 322 displayed on the display device 32 of the reception terminal 30. The reception screen 322 has text 3221 indicating the time slot during which waiting is possible and how many groups are waiting in that time slot, and a reception button 3222. The reception screen 322 may display a list of groups currently making reservations for waiting. The reception screen 322 may further have a language button for selecting a language. As shown in FIG. 11, although the current time is 10:00, the number of groups waiting in the time slot from 10:00 to 12:00 has reached the upper limit, so that the text 3221 indicates that reservations for waiting from 12:00 onwards are possible. In this way, when the number of groups waiting in the time slot including the current time has reached the upper limit, the number of groups waiting in the nearest time slot in which the number of groups waiting has not reached the upper limit is displayed on the reception screen 322.
[0055] 12(a) is a schematic diagram showing a reception method selection screen 323 displayed on the display device 32 of the reception terminal 30. When the user clicks the reception button 3222 on the reception screen 322, the reception method selection screen 323 appears.
[0056] 12(b) is a schematic diagram showing a number-of-persons input screen 324 displayed on the display device 32 of the reception terminal 30. When the user selects a reception method on the reception method selection screen 323, the screen transitions to the number-of-persons input screen 324.
[0057] 12(c) is a schematic diagram showing a phone number input screen 325 displayed on the display device 32 of the reception terminal 30. When the user inputs the number of people on the number of people input screen 324, the screen transitions to a phone number input screen 325. If "Reception with numbered ticket" is selected on the reception method selection screen 323, the phone number input screen 325 does not need to be displayed.
[0058] 12(d) is a schematic diagram showing a final confirmation screen 326 displayed on the display device 32 of the reception terminal 30. When the user inputs a phone number on the phone number input screen 325, the screen transitions to the final confirmation screen 326. The number of people input on the number of people input screen 324 and the phone number input on the phone number input screen 325 are displayed in text on the final confirmation screen 326. On the final confirmation screen 326, a button for confirming the waiting reservation is displayed as a "reception completed and ticket issued" button.
[0059] FIG. 13 is a schematic diagram showing a reservation completion screen 327 displayed on the display device 32 of the reception terminal 30. The reservation completion screen 327 displays a reception number 3271 and a reception time 3272 as reception information in text form. In addition, the reservation completion screen 327 displays a schematic diagram of a numbered ticket 3273. A QR code (registered trademark) can be included in the numbered ticket issued by the printer 40. When the user reads the QR code using the reading device of the user terminal 50, an application or browser for a service provided by the queue management system 1 opens, and the user can inquire about the current waiting situation, register a contact other than a telephone number such as an email address to change notification settings, or cancel a waiting reservation. Information on such operations performed by the user is transmitted from the user terminal 50 to the queue management server 10, which updates the queue management table 143 and transmits the updated information to the management terminal 20. The reservation completion screen 327 may include text 3274 such as "Please refrain from coming more than 5 minutes earlier than the target time."
[0060] <Example of GUI screen display of user terminal 50> FIG. 14(a) is a schematic diagram showing a store list screen 521 displayed on the display device 52 of the user terminal 50. When a user transmits a request to search for a store to the queue management server 10 via a browser or application implemented in the user terminal 50, the queue management server 10 transmits a list of stores to the user terminal 50 as a response. The display control unit 514 causes the display device 52 to display the list screen 521 based on the list of stores received from the queue management server 10. When a user selects and clicks a desired store from the list screen 521, the user terminal 50 transmits a request to wait in line at the store to the queue management server 10. In the example of FIG. 14(a), it is assumed that the user selects cafe restaurant A.
[0061] FIG. 14(b) is a schematic diagram showing a reception screen 522 displayed on the display device 52 of the user terminal 50. The reception screen 522 has text 5221 indicating a time period during which waiting is possible and how many groups are waiting in that time period, and a reception button 5222. As shown in FIG. 14(b), although the current time is 10:00, the number of groups waiting in the time period from 10:00 to 12:00 has reached the upper limit, so the text 5221 indicates that reservations for waiting from 12:00 onwards are possible. In this way, when the number of groups waiting in the time period including the current time has reached the upper limit, the number of groups waiting in the nearest time period during which the number of groups waiting has not reached the upper limit is displayed on the reception screen 522. When the user clicks the reception button 5222, the screen transitions in the same manner as in FIG. 12(b) to (d).
[0062] <Modification of the first embodiment> In the first embodiment, it has been described that the upper limit number of waiting reservations can be set for each time period in the management terminal 20. In another embodiment, the upper limit number may be set by specifying a date as well. The store clerk can set the upper limit number of waiting reservations only on days when congestion is expected, such as release dates of special products or days when events are held in the store or nearby facilities. The store clerk can also choose not to set the upper limit number on days when congestion is expected not to occur, such as weekdays.
[0063] In the first embodiment, the number of users in a group and their phone numbers are input when the user makes a waiting reservation (FIG. 10). In another embodiment, a screen for inputting seat preferences (table seats, counter seats, non-smoking seats, smoking seats, any of them) may be displayed on the reception terminal 30 and the user terminal 50.
[0064] <Summary of the First Embodiment> As described above, the queue management server 10 (information processing device) of this embodiment accepts requests from users (customers) to wait in line at a store, determines whether an upper limit has been set for the number of groups waiting in line associated with a time period, identifies time periods on the day in which the number of groups waiting in line has not reached the upper limit, and generates a display image for accepting requests to wait in line according to the results of the processing. This distributes user visits by time period, preventing the store from becoming crowded due to many users visiting. Furthermore, it becomes easier for store staff to predict the number of users who will visit the store during each time period, making it easier to plan business operations.
[0065] In addition, a reservation for waiting can be made not only from the reception terminal 30 but also from the user terminal 50, and a notification is sent to the user terminal 50 when the user's turn is approaching, so the user does not need to visit the store until the notification is received, and can use time effectively. Furthermore, the time period during which a reservation for waiting can be made is limited, so the user knows when to visit the store. This prevents the user from waiting at the store until it is their turn.
[0066] [Second embodiment] In the above-described first embodiment, a technology has been described in which an upper limit on the number of groups waiting for their turn is set for each time period, and a reception screen according to the number of groups waiting for their turn is displayed on the reception terminal 30 and the user terminal 50. When a user searches for a store to visit, there is a high possibility that the user is also looking for a store with vacant seats (a store that can be entered immediately). Therefore, in the second embodiment, a technology is proposed in which vacant seat information of the store is also delivered to the user terminal 50.
[0067] <Example of queue management system configuration> FIG. 15 is a configuration diagram of the queue management system 2 according to the second embodiment. The queue management system 2 differs from the queue management system 1 of the first embodiment in that it further includes a detection device 70. The detection device 70 is installed in a store and detects the vacant seat status of the store in real time. For example, a camera or a sensor such as a human sensor can be used as the detection device 70. As another form, the detection device 70 can be a personal computer or a button device that allows a store clerk or the like to visually check the inside of the store and input the vacant seat status. The detection device 70 transmits the detected vacant seat status to the queue management server 10 via the network 60. The queue management server 10 manages the data indicating the vacant seat status received from the detection device 70.
[0068] FIG. 16 is a diagram showing an example of a store table 142 according to the second embodiment. The store table 142 further includes vacant seat information 1428 as a constituent item. The vacant seat information 1428 is data indicating the latest vacant seat status transmitted from the detection device 70 in the store. When the queue management server 10 receives the vacant seat status detected by the detection device 70, the update unit 112 updates the vacant seat information 1428. In the example shown in FIG. 16, the vacant seat information 1428 includes statuses such as "full", "vacant", and "slightly crowded". As another form, the vacant seat information 1416 may be indicated by a number such as "0" when there is a vacant seat, "1" when it is crowded, and "2" when it is full. As another form, the vacant seat information 1416 may be a numerical value indicating the number of vacant seats or the number of vacant tables.
[0069] <Processing related to distribution of vacant seat information> Even if the detection result of the detection device 70 is "vacant," other users who are waiting in line may be shown in immediately because a certain user has simply left the seat or is paying the bill. In such a case, if the detection result of the detection device 70 is delivered directly to the user terminal 50, the user may visit the store even though there are other users who have actually made reservations to wait in line.
[0070] Therefore, in this embodiment, when the queue management server 10 receives an inquiry request from the user terminal 50, if there is a store that has an upper limit set for waiting reservations, it refers to the queue management table 143 of that store to determine the vacant seating situation at the store and replies to the user terminal 50 as a response to the inquiry.
[0071] 17 is a flowchart of a process executed by the queue management server 10 according to this embodiment to distribute vacant seat information of each store based on vacant seat information, information on the upper limit of the number of groups waiting for their turn for each time period, and reception information managed by the queue management table. The following process is executed by the queue management server 10 (which can also be called the vacant seat management server) when a request to inquire about vacant seat information of a store is received from the user terminal 50.
[0072] (Step S41) The queue management server 10 refers to the store table 142 for the target store and determines whether or not an upper limit is set for each time period. If an upper limit is set for each time period (Yes), the process proceeds to step S42. If an upper limit is not set for each time period (No), the process proceeds to step S43.
[0073] (Step S42) The queue management server 10 judges whether the time next to the current time slot (hereinafter referred to as the current time slot), which includes the time when the request was received (hereinafter referred to as the next time slot), is less than a predetermined time (3 minutes, for example). As described above, this is a process in which the queue management server 10 distributes vacant seat information, taking into consideration the possibility that other users who are waiting their turn will be guided there immediately, even if the vacant seat information indicates that there are vacant seats and the number of groups waiting in the current time slot is zero. In step S42, if the current time is close to the next time slot (less than the predetermined time) (Yes), the process proceeds to step S44. If there is sufficient time until the next time slot (more than the predetermined time) from the current time slot (No), the process proceeds to step S43.
[0074] (Step S43) The queue management server 10 refers to the queue management table 143 to acquire the current (if the process has moved from step S42 to step S43, the current time period) number of groups waiting for which guidance has not yet been given.
[0075] (Step S44) The queue management server 10 refers to the queue management table 143 to acquire the number of unintroduced groups waiting in the current time slot and the number of unintroduced groups waiting in the next time slot.
[0076] (Step S45) The queue management server 10 judges whether the acquired number of waiting groups is one or more. Here, when moving from step S44 to step S45, it may judge whether each of the number of waiting groups in the current time slot and the number of waiting groups in the next time slot is one or more, or it may judge whether the combined number of waiting groups in the current time slot and the number of waiting groups in the next time slot is one or more. If it is judged in step S45 that there are waiting groups (Yes), the process proceeds to step S47. If it is judged that the number of waiting groups is 0 (No), the process proceeds to step S46.
[0077] (Step S46) The queue management server 10 acquires vacant seat information of the target store from the store table 142.
[0078] (Step S47) On the other hand, the queue management server 10 sets the vacant seat information of the target store to "full" regardless of the vacant seat information in the store table 142. In this embodiment, the queue management server 10 sets the vacant seat information to a fixed vacant seat status (full) without going through the process of acquiring vacant seat information from the store table 142. Alternatively, for example, while acquiring vacant seat information in parallel with the processes from steps S41 to S45, if the result of the determination in step S45 is Yes, the vacant seat information may be overwritten with a fixed vacant seat status (full) that has been set in advance.
[0079] (Step S48) The queue management server 10 transmits the vacant seat information to the user terminal 50. When the process proceeds from step S47 to step S48, the queue management server 10 transmits information regarding the number of groups waiting for their turn together with the vacant seat information.
[0080] Note that the above process has been described using an example in which there is one target store, but if there are multiple target stores for the inquiry request, the flowchart shown in Figure 17 can be executed for each store.
[0081] <Example of GUI screen display of user terminal 50> A user who is going to visit a store can inquire about the vacant seat information of the store to the queue management server 10 via the user terminal 50. The inquiry request includes the location information of the user terminal 50. In response to the inquiry, the queue management server 10 searches for records related to the stores in the store table 142 according to the current location of the user terminal 50 or a location on the map specified by the user, thereby identifying a group of stores from which vacant seat information will be sent to the user terminal 50, and acquiring vacant seat information of each store included in the group of stores. The queue management server 10 returns the acquired vacant seat information to the user terminal 50 as a response to the inquiry. The user terminal 50 displays the vacant seat information received from the queue management server 10 on the display device 52, for example, as a list of stores. The user terminal 50 may display the vacant seat information received from the queue management server 10 on a map (for example, by displaying it as a pin).
[0082] 18(a) is a schematic diagram showing a store list screen 523 displayed on the display device 52 of the user terminal 50. The list screen 523 is displayed when the user terminal 50 transmits a request for inquiry about vacant seat information of stores to the queue management server 10. The list screen 523 displays a list of stores and vacant seat information of each store.
[0083] FIG. 18(b) is a schematic diagram showing a reception screen 522 displayed on the display device 52 of the user terminal 50. When the user selects "cafe restaurant A" from the list screen 523, a reception screen 522 according to the number of people waiting their turn is displayed. The reception screen 522 is the same as that shown in FIG. 14(b). The user can make a waiting reservation via the reception screen 522 in the same manner as in the first embodiment. In this way, when the store's vacancy information is "full," the queue management server 10 generates a reception screen for accepting waiting reservations and transmits it to the user terminal 50.
[0084] Fig. 18(c) is a schematic diagram showing a store list screen 523 displayed on the display device 52 of the user terminal 50. Fig. 18(c) shows a case where the user has selected "Kitchen B" from the list screen 523.
[0085] 18(d) is a schematic diagram showing a non-reception screen 524 displayed on the display device 52 of the user terminal 50. When the user selects "Kitchen B" from the list screen 523, the non-reception screen 524 is displayed. On the non-reception screen 524, text 5241 indicating that the vacant seat information is "Available" and text 5242 saying "Please visit the store directly" are displayed, and the Accept button is not displayed. In this way, when the vacant seat information of the store is "Available" or "Slightly busy", the queue management server 10 generates a non-reception screen that does not accept waiting reservations and transmits it to the user terminal 50.
[0086] <Summary of the second embodiment> As described above, by detecting availability with the detection device 70 and transmitting vacant seat information to the user terminal 50, it becomes easier for the user to select a store to visit. Furthermore, when there is one or more waiting reservations, by determining that the store is full regardless of the detection result of the detection device 70, accurate vacant seat information can be presented to the user even in the event of a false detection or an omission in input of availability. Note that when there is one or more waiting reservations, the text is not limited to "full" and can be other expressions such as "waiting," as long as it indicates that the store is not immediately available.
[0087] Furthermore, the vacant seat information sent from the detection device 70 indicating either "full," "available," or "slightly crowded" may be supplemented with the congestion status according to the waiting reservations. For example, in addition to "full," "available," and "slightly crowded," information such as "n groups waiting" (n is the number of groups waiting) or "n more groups can wait today" may be distributed.
[0088] Also, when the current time is close to the next time slot, the method of determining whether there is a waiting group is explained taking into consideration the number of groups waiting in the next time slot, but as a simpler method, a process that does not include steps S42 and S44 may be executed. In that case, if an upper limit is set for each time slot and the upper limit has already been reached, a message such as "You are currently not allowed to wait in line" may be displayed instead of the vacant seat information.
[0089] [Variations] In the above embodiment, a system that accepts reservations for waiting in line from users (customers) who wish to use a store where seats and tables are installed and food and drink are served has been described as an example. The above system can also be applied to waiting in line at facilities other than restaurants. For example, the technology disclosed herein can also be applied to waiting in line for entering an event venue, or waiting in line for customer service at a cosmetics counter or bank teller.
[0090] As described above, the technology of the present disclosure can be realized by supplying a program that realizes one or more functions of the above-mentioned embodiments to a system or device via a network or a storage medium, and having one or more processors in a computer of the system or device read and run the program. It may also be realized by a circuit that realizes one or more functions.
[0091] The present disclosure is not limited to the above-described embodiments, and includes various modified examples. For example, the above-described embodiments have been described in detail to clearly explain the present disclosure, and it is not necessary to include all of the configurations described. In addition, a part of an embodiment can be replaced with a configuration of another embodiment. Furthermore, a configuration of another embodiment can be added to a configuration of an embodiment. Furthermore, a part of the configuration of each embodiment can be added to, deleted from, or replaced with a part of the configuration of another embodiment. [Explanation of symbols]
[0092] 1, 2...Queue management system 10...Queue management server 20...Administrative terminal 30…Reception terminal 40…Printer 50...User terminal 60…Network 70...Detection device
Claims
1. An information processing device that accepts a user's waiting list for a facility, a first determination means for determining whether or not an upper limit is set for the number of people waiting for their turn associated with a time period; A specifying means for specifying a time period on the day in which the number of groups on the waiting list has not reached the upper limit; A receiving means for receiving a result of detection of the vacancy status of the facility; a second determination means for determining whether or not there is a user waiting in line, and a generation means for generating a display image for accepting the user waiting in line according to a result of processing by the first determination means, the identification means, the receiving means, and the second determination means, the generating means generates the display image including the detection result of the vacant seat state according to the detection result of the vacant seat state and results of the processing by the first determining means and the identifying means; When the second judgment means judges that there is a user waiting in line, the generation means generates the display image by indicating that the vacant seat status is full, even if the detection result of the vacant seat status indicates that there are vacant seats in the facility.
2. The information processing device according to claim 1, further comprising a third judgment means for, when it is determined by the first judgment means that an upper limit value corresponding to the time period including the current time has been set, determining whether the number of people waiting in the time period including the current time has already reached the upper limit value.
3. The information processing device described in claim 2, characterized in that when the third judgment means judges that the number of waiting groups has reached the upper limit in the time period including the current time, the identification means identifies the most recent time period in which the number of waiting groups has not reached the upper limit.
4. When it is determined in the first determination means that the upper limit value is not set, the generation means generates a display image for accepting the waiting order, 2 . The information processing apparatus according to claim 1 , wherein, when the first determination means determines that the upper limit value is set, the generation means causes the time period identified by the identification means to be displayed on the display image.
5. The information processing device described in claim 1, characterized in that if the first judgment means judges that the upper limit value has been set and the identification means does not identify a time period in which the number of people waiting in line has not reached the upper limit value, the generation means generates a display image indicating that the waiting in line cannot be accepted.
6. An information processing device that accepts a user's waiting list for a facility, a first determination means for determining whether or not an upper limit is set for the number of people waiting for their turn associated with a time period; A receiving means for receiving a result of detection of the vacancy status of the facility; a second determination means for determining whether or not there is a user waiting in line, and a display control means for generating a display screen for accepting the user's waiting in line according to a result of processing by the first determination means, the receiving means, and the second determination means, and for displaying the display screen on a terminal, the display control means, when the upper limit value corresponding to the time slot including the current time is set and the number of groups on the waiting list has reached the upper limit value, causes the terminal to display a display screen for accepting waiting lists for time slots other than the time slot including the current time; When the upper limit value corresponding to the time slot including the current time is not set or the number of people waiting has not reached the upper limit value, the display control means causes the terminal to display a display screen for accepting a waiting list for the time slot including the current time, the display control means causes the terminal to display a display image including the detection result of the vacant seat state according to the detection result of the vacant seat state and a result of the processing by the first determination means; The information processing device is characterized in that, when the second judgment means judges that there is a user waiting his turn, the display control means causes the terminal to display the display image indicating that the vacant seat status is full, even if the detection result of the vacant seat status indicates that there are vacant seats in the facility.
7. A program for causing a computer to function as the information processing device according to any one of claims 1 to 6.
8. 1. An information processing method executed by an information processing device that accepts a user's waiting list for a facility, comprising: a first determination step of determining whether or not an upper limit value for the number of groups waiting for a turn associated with a time period is set; Identifying a time period on the day when the number of groups on the waiting list has not reached the upper limit; receiving a seat availability detection result for the facility; a second determination step of determining whether or not there is a user waiting in line; generating a display image for accepting the waiting in response to the results of the processing by the first determination step, the identifying step, the receiving step, and the second determination step; the generating step includes generating the display image including the detection result of the vacant seat state according to the detection result of the vacant seat state and results of the processing by the first determination step and the identifying step; An information processing method including, when it is determined in the second determination step that there is a user waiting in line, generating the display image by assuming that the vacant seat status is full, even if the detection result of the vacant seat status indicates that there are vacancies in the facility.
Citation Information
Patent Citations
Order management system, order management device, and program
JP2017142616A
Turn management system, turn management device and program
JP2017174115A
Turn managing system
JP2019046091A
Information management device, information management method, and program
JP2020140640A
Object detector and congestion state management device
JP2020173775A
