Smart virtual queue system and method

Abstract

To provide a virtual queue system and a method for managing reduced capacity events in a virtual queue.SOLUTION: In a virtual queue system, a virtual queue controller is configured to: receive instructions from amusement park attractions for reduced capacity events; determine the reduction in the capacity of the attraction; identify each guest in the virtual queue of the attraction who has a return time that is affected by the reduced capacity event; remove the guests with the affected return times from the virtual queue; generate re-admission time slots for the guests removed from the virtual queue; select two or more updated return times in the re-admission time slots for each of the removed guests; provide a notification to each removed guest requesting guest input to select a single updated return time from among the two or more updated return times; and return each guest to the virtual queue upon receiving the corresponding selection of the single updated return time.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] <Cross - Reference to Related Applications> This application claims the benefit of U.S. Provisional Patent Application No. 62 / 867,634, entitled "Systems and Methods for a Smart Virtual Queue," filed on June 27, 2019, the disclosure of which is hereby incorporated by reference in its entirety for all purposes.

[0002] This disclosure generally relates to the field of amusement parks. Specifically, embodiments of this disclosure relate to techniques for managing reduced capacity events in a virtual queue.

Background Art

[0003] This section is intended to introduce readers to various aspects of technologies that may be related to various aspects of the present disclosure described below. This discussion is believed to be helpful in showing the background context to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, these descriptions should not be construed as an admission of prior art and should be read from the above - mentioned perspective.

[0004] Theme parks or amusement park attractions are becoming increasingly popular, and various amusement park attractions that provide unique movements and visual experiences to passengers have been created. Guests entering various amusement park attractions can utilize a virtual queue system that positions guests within a virtual queue rather than a physical queue, allowing them to enjoy other features of the amusement park while their position within the virtual queue advances. However, the actual loading times of amusement park attractions can be affected by downtime or partial closures of the amusement park attractions, which can negate some of the advantages of having a virtual queue as guests may need to wait for long periods within the loading lines of the amusement park. Therefore, it is recognized that it is desirable to improve the virtual queue system during capacity reduction events (downtime or partial closures of amusement park attractions).

Summary of the Invention

[0005] Some embodiments within the same scope as the subject matter of the original claims are summarized below. These embodiments are not intended to limit the scope of the present disclosure, but rather merely to outline some of the disclosed embodiments. In fact, the present disclosure can include various forms that may be similar to or different from the embodiments shown below.

[0006] According to one embodiment, the system includes a virtual queue controller having a processor and a memory. The processor is configured to execute instructions accessed from the memory to cause the virtual queue controller to: receive an indication of a headcount reduction event from an amusement park attraction; determine a reduction in the headcount of the attraction associated with the headcount reduction event; identify each guest having a return time within the virtual queue of the attraction that is affected by the headcount reduction event based on the reduction in headcount; remove the guests having an affected return time from the virtual queue; generate a reaccommodation time slot for the guests removed from the virtual queue, wherein the length of the reaccommodation time slot is based on the total number of affected return times of the guests removed from the virtual queue, and the reaccommodation time slot follows all of the affected return times; select two or more updated return times within the reaccommodation time slot for each of the guests removed from the virtual queue; provide a notification requesting a guest input for each guest removed from the virtual queue to select a single updated return time from the two or more updated return times; and return each guest to the virtual queue when a corresponding selection of the single updated return time is received.

[0007] According to one embodiment, there is provided a virtual queue system having an amusement park attraction with a capacity based on the number of available guest seats, and a virtual queue controller having a processor and a memory. The virtual queue controller outputs a notice suppressing the permission for a guest to enter from the virtual queue to the amusement park attraction based at least in part on a capacity reduction event related to the reduction in the number of available guest seats during the capacity reduction event, identifies a guest having an affected return time that is a return time within the virtual queue affected by the capacity reduction event and related to the return time to the amusement park attraction during the capacity reduction event, removes at least one guest having one of the affected return times from the virtual queue, generates a re-accommodation space within the virtual queue, provides a guest notice indicating the removal from the virtual queue and a plurality of new return times corresponding to the re-accommodation space to a guest-related device associated with the at least one guest removed from the virtual queue, receives a selection notice regarding the selection of one of the plurality of new return times by the guest via the guest-related device, and is configured to verify the selected new return time when presented for entry after the new return time. The virtual queue system also includes a sensor assembly disposed at the entrance of the amusement park attraction, the sensor assembly being configured to receive information from the guest-related device and transmit the information from the guest-related device to the virtual queue controller for verification.

[0008] According to one embodiment, the method includes receiving an indication of a headcount reduction event, determining a decrease in the guest throughput of an amusement park attraction during the headcount reduction event, determining, based on the decrease in guest throughput, a total number of virtual queue return times of guests in a virtual queue affected by the headcount reduction event, identifying each individual guest having an affected virtual queue return time, generating, within the virtual queue, re-accommodation time slots sized based on the total number of virtual queue return times of guests in the virtual queue affected by the headcount reduction event, and providing, to each of the individual guests having an affected virtual queue return time, a notification indicating a plurality of available new return times within the re-accommodation time slots.

[0009] These and other features, aspects, and advantages of the present disclosure will be better understood when the following detailed description is read with reference to the accompanying drawings in which like parts are designated with like reference numerals throughout.

Brief Description of the Drawings

[0010]

Figure 1

[0011]

Figure 2

[0012]

Figure 3

[0013]

Figure 4

[0014]

Figure 5

DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, one or more specific embodiments of the present disclosure will be described. For the sake of brevity in describing these embodiments, not all implementation features may be described herein. It should be understood that in the development of any such implementation in any engineering or design project, numerous implementation-specific decisions must be made to achieve the specific objectives of the developer, such as compliance with system-related and business-related constraints that may vary depending on the implementation. Further, although such development efforts can be complex and time-consuming, they should be understood as routine endeavors of design, fabrication, and manufacturing for those skilled in the art who benefit from the present disclosure.

[0016] When introducing elements of various embodiments of the present disclosure, articles such as "a", "an", and "the" are intended to mean that there is one or more of these elements. The terms "comprising", "including", and "having" are intended to be inclusive and mean that additional elements other than the recited elements may exist. Also, it should be understood that references to "one embodiment" or "an embodiment" of the present disclosure are not intended to be construed as precluding the existence of additional embodiments that also include the recited features.

[0017] Theme park or amusement park attractions are becoming increasingly popular, and various amusement park attractions have been created that provide passengers with unique movements and visual experiences. Guests entering various amusement park attractions can utilize a virtual queue system that positions guests within a virtual queue rather than a physical queue, allowing them to enjoy other features of the amusement park while their position within the virtual queue advances. Some virtual queue systems provide guests with a return time indicating the time when the guest will arrive at the amusement park attraction. The guest is instructed to return to the amusement park attraction at the return time and wait within a physical queue or ride queue of limited length before entering the amusement park attraction (e.g., boarding the ride vehicle of the amusement park attraction). Note that the ride queue can also be understood to mean a group of guests waiting to ride who have gathered in the boarding area, whether in a first-in, first-out arrangement or not. Thus, the ride queue shown in this specification can mean a limited number of guests gathered in the boarding area. Generally, the boarding area or physical queue or ride queue of limited length functions as a buffer area for the amusement park attraction and has a sufficient number of guests so that there are enough guests to fill the amusement park attraction to its full capacity at the ride time of the amusement park attraction. However, a ride queue of limited length can also be shortened to reduce the time guests need to spend in the ride queue and increase the time guests have to enjoy other aspects of the amusement park (e.g., dining, shopping, and other entertainment facilities). The virtual queue system not only shortens the length of the ride queue but also enables a predetermined number of guests to arrive at the attraction guiding area so that there can be a sufficient number of guests to fill the amusement park attraction to its full capacity during each ride cycle or operation of the attraction.

[0018] Unfortunately, an amusement park attraction may not operate at full capacity due to capacity reduction events (e.g., downtime of the amusement park attraction and / or partial closure of the attraction). During a capacity reduction event, more guests may enter the ride queue (e.g., arrive from the virtual queue at or after the return time) than leave the ride queue (e.g., board the amusement park attraction). This may cause delays to the guests present in the ride queue. Since more guests enter the ride queue than leave it, the length of the ride queue increases, and as a result, guests may have to wait in the ride queue for an extended period after returning to the amusement park attraction at or after the return time. Guests may experience inconvenience and / or dissatisfaction from waiting in the ride queue for an extended period, which may negate some of the benefits of providing a virtual queue.

[0019] Furthermore, an extended time in the ride queue due to delays caused by capacity reduction events may further negatively impact the efficiency of the entire amusement park. Guests may expect to disembark from a ride at a specific time based on their return time and may accordingly make plans (e.g., lunch plans with family, queue for subsequent amusement park attractions). However, an extended time in the ride queue may delay the guests' expected disembarkation time, which may conflict with the guests' plans. Therefore, when the ride queue is delayed, guests may arrive late or not show up at the return time of the virtual queue for subsequent amusement park attractions in the park, which may cause delays and / or a decrease in efficiency of subsequent amusement park attractions. Additionally, when the ride queue is delayed, guests may miss their meal plans with family by remaining in the queue during a capacity reduction event, which may cause the guests to experience further inconvenience and / or dissatisfaction.

[0020] Based on these, this specification provides a system and method for managing a virtual queue system during a capacity reduction event that helps maintain a ride queue of a desired length to prevent or mitigate adverse effects on both guests and amusement parks related to the capacity reduction event.

[0021] FIG. 1 is a schematic diagram of an embodiment of an amusement park 10 including a virtual queue system 12. The virtual queue system 12 includes a computer system 14, a monitoring sensor 16, a wireless communication system 18, a system display 20, a guest-related device 22 (e.g., an active wearable guest device, a guest mobile device, etc.), and other components that regulate the operation of the respective virtual queues of the amusement park attractions 24 within the amusement park 10. As described above, guests 26 entering various amusement park attractions can enter a virtual queue rather than a physical queue of the amusement park attraction 24 using the virtual queue system 12. In one embodiment, the guest 26 can submit a virtual queue request to enter the virtual queue of the amusement park attraction 24 using the guest-related device 22. In other embodiments, the guest 26 can enter a virtual queue request via a kiosk 28 placed throughout the amusement park 10. In one embodiment, the kiosk 28 is placed in proximity to the amusement park attraction 24. In other embodiments, the kiosk 28 is placed in a general area of the amusement park (e.g., the dining area 30).

[0022] The virtual queue system 12 can receive virtual queue requests via the communication circuit of the wireless communication system 18. The virtual queue system 12 can place a guest 26 in the virtual queue of the amusement park attraction 24 based on the virtual queue request and provide the guest 26 with a return time or a dynamic position within the virtual queue that progresses as the guest enters the attraction 24. For example, the virtual queue system 12 can have available time slots for the amusement park attraction at 1:45 PM, 2:00 PM, and 2:15 PM. The guest 26 can use the guest-related device 22 to send a virtual queue request for a return time of 2:00 PM. In response, the virtual queue system 12 can place the guest 26 in the virtual queue and provide the guest 26 with a notification to return to the amusement park attraction 24 at 2:00 PM.

[0023] In certain embodiments, a guest can select at their discretion from a group of available return times, and some guests may choose a later return time based on their itinerary for that day. That is, the virtual queue controller can enable a first guest 36 to select a return time of 2:00 PM, a second guest 38 to select a return time of 2:05 PM, and a third guest 40 to select a return time of 2:10 PM. The available return times for each time slot are preset at the beginning of the day and can be allocated to guests until they are no longer available.

[0024] In some embodiments, the virtual queue system 12 can also incorporate other ways to determine the return time or queue position and provide it to the guest 26. In some embodiments, the guest returns to the attraction based on the position of the guest 26 within the virtual queue. The virtual queue system 12 can place the guest 26 within the virtual queue in response to a virtual queue request and add the guest 26 to a position within the virtual queue that is available to other guests. For example, the first guest 36, the second guest 38, and the third guest 40 can each send their respective first, second, and third virtual queue requests. The first guest 36 can be assigned to the first position within the virtual queue, the second guest 38 can be assigned to the second position within the virtual queue, and the third guest 40 can be assigned to the third position within the virtual queue. These guests can return to the attraction when their position within the virtual queue reaches the head of the virtual queue. In some embodiments, the system 12 can provide an estimated value of the expected time until the guest reaches the head of the virtual queue, and this estimated value can function as the return time as shown herein.

[0025] The guest can return to the attraction 24 at its return time or later. In some embodiments, the sensor 16 is implemented as a wireless reader such as an NFC reader and can communicate with the guest-related device 22 to confirm the return time of the guest associated with the guest-related device. Based on this communication, an effective return time indication (e.g., green light, effective notification pushed to the guest-related device 22) can be provided based on the determination that the current time is at or after the indicated return time. When the guest attempts to enter the attraction 24 before the return time, an invalid return time indication (e.g., red light, invalid notification pushed to the guest-related device 22) can be provided. The sensor 16 can be configured to perform communication with the guest-related device 22, but the determination of the valid or invalid return time can be performed by a virtual queue controller 42 communicatively coupled to the sensor 16 as shown herein.

[0026] FIG. 2 is a block diagram of an embodiment of the virtual queue system 12. The virtual queue system 12 includes a virtual queue controller 42 configured to manage virtual queues. The virtual queue controller 42 can be configured to communicate with other components of the virtual queue system 12, including the guest-related device 22, the amusement park operator device 44, and the amusement park attraction entry system 46, or some combination thereof. Each component of the virtual queue system 12 can include communication circuits 48a, 48b, 48c, and 48d for communicating with other components of the virtual queue system 12. For example, the virtual queue controller 42 can include the communication circuit 48a. The communication circuit can include an antenna, a wireless transceiver circuit, and signal processing hardware and / or software (e.g., hardware or software filters, A / D converters, multiplexer amplifiers), or a combination thereof, and can be configured to communicate over a wireless communication path via infrared (IR) wireless communication, satellite communication, broadcast radio, microwave radio, Bluetooth, Zigbee, Wifi, UHF, NFC, etc. In one embodiment, the communication circuits 48a, 48b, 48c, and 48d include a plurality of IR transceivers disposed within the environment of the amusement park attraction.

[0027] The virtual queue controller 42 can include a processor 50a and a memory 52a. The processor 50a can include one or more processing devices, and the memory 52a can include one or more tangible non-transitory machine-readable media. By way of example, such machine-readable media can include RAM, ROM, EPROM, EEPROM, or optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to hold or store desired program code in the form of machine-executable instructions or data structures and that can be accessed by the processor 50a or other processor-based devices (e.g., mobile devices). In certain embodiments, the memory 52a is configured to store instructions executable by the processor 50a for outputting various control system signals 54. For example, the processor 50a can execute instructions to place a guest within a virtual queue based on a virtual queue request 58 from the guest-related device 22 and instructions stored in the memory 52a, and output a notification 56 indicating a return time to the guest-related device 22 via the communication circuit 48a.

[0028] As described above, the virtual queue controller 42 is configured to output a notification 56 for each guest to the respective guest-related device 22. For example, the notification 56 can instruct the guest to return to the amusement park attraction at a specified return time. In another example, the notification 56 can include a delay message. In one embodiment, the virtual queue controller 42 is configured to identify guests in a virtual queue affected by a capacity reduction event of an amusement park attraction and output a delay message including the return time of the affected virtual queue to the guests. The guest-related device 22 can be a personal guest device (e.g., a smartphone, tablet, laptop, etc.) or an amusement park queue device provided to the guest (e.g., a smart wristband, active wearable, portable communication device, etc.). The guest-related device 22 can have a processor 50b and a memory 52b. Further, the guest-related device 22 can include an operator interface 60b having a display 62b (e.g., a screen) and an input device 64b (e.g., a touch screen, keypad, keyboard, etc.). The guest-related device 22 can be configured to display the notification 56 on the display 62b. In one embodiment, the guest can respond to the notification 56 via the input device 64b. For example, the guest can confirm the return time via the input device 64b.

[0029] In one embodiment, the notification 56 can instruct the guest to return to the ride queue at the amusement park attraction at the guest's return time. The guest can enter the ride queue through the entry point 66 of the amusement park attraction entry system at their respective return times. The entry point 66 can be configured to detect that the guest has entered the ride queue. The amusement park attraction entry system 46 can include a processor 50d and a memory 52d. The processor 52d can be configured to execute instructions to output a counter signal 68 indicating that the guest has entered the ride area to the virtual queue controller 42 via the communication circuit 48d, based at least in part on the detection of the guest and the instructions stored in the memory device. In one embodiment, the entry point 66 is configured to directly output the counter signal 68 to the virtual queue controller 42. In one embodiment, the entry point 66 includes a sensor assembly 70 (e.g., including the sensor 16) configured to detect the guest-related device 22. The virtual queue controller 42 can be configured to determine that the guest has entered the ride queue based at least in part on the detection of the guest-related device 22 at the entry point 66. In one embodiment, the entry point 66 also verifies that the guest has a valid return time at the time of entry through the entry point 66. The virtual queue system 12 can determine the number of guests who have entered the ride queue based on the counter signal 68 received from the amusement park attraction entry system 46 and / or the entry point 66. In one embodiment, the amusement park attraction can include a turnstile configured to output a counter signal 68 to the amusement park attraction each time a guest passes through.

[0030] The amusement park attraction entry system can also include a boarding gate 72 configured to detect guests who have left the boarding queue (e.g., guests who have entered the amusement park attraction). The amusement park attraction entry system 46 and / or the boarding gate 72 can be configured to output a second counter signal 74 indicating the detection of a guest who has left the boarding queue to the virtual queue controller 42. The virtual queue controller 42 can be configured to determine the total number of guests in the boarding queue based on the second counter signal 74. In certain embodiments, the boarding queue area can include a sensor assembly 70 of the amusement park attraction entry system 46. The sensor assembly 70 can have a plurality of sensors configured to detect each guest device in the boarding queue and output a total guest count signal 76 to the virtual queue controller 42. The virtual queue controller 42 can be configured to determine the total number of guests in the queue based at least in part on the total guest count signal 76.

[0031] As shown in this specification, the virtual queue controller 42 is configured to manage the virtual queue of the attraction and remove one or more guests from the virtual queue in response to a capacity reduction event. The instruction for the capacity reduction event can be based on a signal received from the operator of the attraction, or the virtual queue controller 42 can be configured to identify the capacity reduction event based on queue information. In certain embodiments, the virtual queue controller 42 is configured to determine that the amusement park attraction may be experiencing a capacity reduction event based at least in part on the total number of guests in the ride queue exceeding a predetermined threshold or tolerance value. In response to determining that the amusement park attraction may be experiencing a capacity reduction event, the virtual queue controller 42 can output a capacity reduction notification 78 indicating that the amusement park attraction may be experiencing a capacity reduction event to the amusement park operator device 44. The amusement park operator device 44 can be a computer, smartphone, tablet, laptop, etc. The amusement park operator device 44 can include a processor 50c and a memory 52c. Additionally, the amusement park operator device can include an operator interface 60c having a display 62c (e.g., a screen) and an input device 64c (e.g., a touch screen, keypad, keyboard, etc.). The amusement park operator device 44 can be configured to display the capacity reduction notification 78 on the display 62c. The capacity reduction notification 78 can indicate to the operator that the amusement park attraction may be experiencing a capacity reduction event. The capacity reduction notification 78 can include data for the operator to determine whether the amusement park attraction is experiencing a capacity reduction event, as well as the severity and / or duration of the capacity reduction event. The capacity reduction notification 78 can also include a prompt for the operator to input an operator response 80 (e.g., confirmation or rejection of the capacity reduction event) via the input device 64c.In one embodiment, in response to receiving confirmation of a capacity reduction event, the virtual queue controller 42 can send an instruction request 82 that includes a prompt requesting that the operator provide an operator input 84 related to the severity and / or duration of the capacity reduction event.

[0032] In one embodiment, the operator can manually output a capacity reduction event signal 86 to the virtual queue controller 42 via the operator interface 60c. For example, the ride vehicle of an amusement park attraction may require maintenance. The operator can guide the ride vehicle from the main track of the amusement park attraction to the service track. If there is no ride vehicle on the main track, the amusement park attraction may not have enough rides to operate at full capacity. The operator can manually output a capacity reduction event signal 86 indicating that the amusement park attraction is operating below full capacity. The capacity reduction event signal 86 can include data indicating the amount of capacity reduction, the expected duration of the capacity reduction, and the like. In one embodiment, the operator can also output a capacity reduction event signal 86 for other reasons, including spillage of food, weather delays, complete system maintenance (e.g., shutdown). Further, the operator can manually output a capacity reduction event end signal 88 indicating that the amusement park attraction is operating at full capacity.

[0033] In one embodiment, the reduction in capacity can be made a function of the overall reduction in the number of available sets per vehicle cycle, where the average vehicle operation time (e.g., 2 minutes, 5 minutes). For example, if a single vehicle with six seats is out of service, the capacity reduction can be six seats per vehicle cycle. Normally, if the vehicle has a full capacity of 120 seats across all vehicle units and operates on average 10 times per hour (1200 guests per hour), the loss of six seats represents a 6% reduction in vehicle capacity, or a loss of 72 seats per hour. Similarly, if one seat in a vehicle unit is out of service due to spilled food, the capacity reduction can be one seat per vehicle cycle.

[0034] In one embodiment, the virtual queue controller 42 is configured to determine that a capacity reduction event has occurred at an amusement park attraction, at least in part based on receiving confirmation of a capacity reduction event or a capacity reduction event signal 86 from the amusement park operator device 44.

[0035] FIG. 3 is a flowchart of an embodiment of a virtual queue system during a headcount reduction event (block 90). The headcount reduction event can include a partial shutdown of an amusement park attraction. For example, the partial shutdown can include shutting down at least one ride vehicle, ride seat, or combination thereof of the amusement park attraction. The amusement park attraction is configured to operate at a rate greater than 0% and less than 100% of full ride capacity during the partial shutdown. In one embodiment, the virtual controller is configured to output a notification suppressing guest entry permission from the virtual queue to the amusement park attraction, based at least in part on the headcount reduction event. Further, the headcount reduction event can include a stop time event of the amusement park attraction. The stop time event can include a complete shutdown of the amusement park attraction, such that the operation of the amusement park attraction stops during the stop time event. Specifically, the amusement park is configured to operate at 0% of full ride capacity during the stop time event.

[0036] During the headcount reduction event, due to the reduction in the ride capacity of the amusement park attraction, the amount of guests entering the ride queue may exceed the amount of guests leaving the ride queue (e.g., entering the amusement park attraction), so there is a possibility that the length of the ride queue may start to increase based on the percentage reduction in the ride capacity of the amusement park attraction. The virtual queue system can be configured to suppress guest entry permission to the ride queue of the amusement park attraction in order to avoid excessive waiting times within the ride queue.

[0037] In one embodiment, to suppress guest entry permission to the ride queue, the virtual queue controller is configured to identify a queue return time affected by a capacity reduction event (block 92). For example, a guest having a return time during a stop time event is assumed to spend additional time in the ride queue during the stop time event and thus is likely to be affected by the capacity reduction event. In another example, a guest having a return time immediately after a capacity reduction event is considered to be affected by the capacity reduction event because the ride queue may become longer than a predetermined length and the guest may be made to wait in the ride queue for an extended period of time.

[0038] In an embodiment where an estimated return time is provided as a notification or reminder (e.g., an output to the guest-related device 22) to a guest based on a particular position within a virtual queue that moves dynamically forward as the front guest enters the attraction, the virtual queue controller can be configured to identify an affected position within the virtual queue corresponding to an estimated return time affected by a capacity reduction event. The virtual queue controller can be configured to identify guests affected by the capacity reduction event based on the affected return time and / or the affected position within the virtual queue (and the associated affected return times).

[0039] The virtual queue controller may determine that there is no return time affected by the headcount reduction event after several headcount reduction events. That is, the virtual queue controller may not be able to identify guests with a return time affected by the headcount reduction event. In such a case, the virtual queue controller does not perform further operations in response to the headcount reduction event. However, in some cases, the virtual queue controller can determine that at least one return time is affected by the headcount reduction event (block 94). Instead of keeping the guests in the virtual queue with an affected return time sitting in the boarding queue for a long time, the virtual queue controller can be configured to remove the affected return time, or the guests having the affected return time, from the virtual queue (block 96). The virtual queue controller can be configured to store in the memory device data indicating which guest or return time has been removed from the virtual queue.

[0040] In one embodiment, the virtual queue controller 42 can trigger the removal of a particular guest affected from the virtual queue based on both a threshold of headcount loss (e.g., greater than 10%) during the headcount reduction event and the presence of a threshold number of return times (e.g., more than 75 given return times, more than 200 return times expiring within one hour). Thus, as a result of a given headcount reduction event, all guests within the time window associated with that headcount reduction event may be removed from the virtual queue, or only some guests may be removed from the virtual queue.

[0041] The virtual queue controller 42 can be configured to achieve a predetermined relationship between the return time and the passenger capacity over a specific time window. That is, the return time that starts at a point within the time window and meets or becomes valid until the deadline can be regarded as related to that time window. In one example, the virtual queue controller 42 can be configured to keep the number of return times that meet or become valid within a specific time below a specific percentage of the total passenger capacity at that time. In one example, the target percentage of return times with respect to the total passenger capacity is 50% or less, 35% or less, 25% or less. When the ratio relationship changes due to a decrease in the passenger capacity, the virtual queue controller 42 is configured to remove guests from the virtual queue during the target time window until the desired relationship is re-established. For example, at a 50% target, if the vehicle has 1200 guests per hour and the return time that meets the deadline within a specific time is about 600 guests. However, if five vehicle units are removed from operation and the total capacity per vehicle cycle decreases by 30 seats, and if the vehicle cycle occurs 10 times per hour, the total vehicle capacity decreases by 300 seats per hour. In such an example, the 600 return times at that time correspond to more than 50% of the passenger capacity. Therefore, the virtual queue controller 42 can remove guests from the virtual queue during that time window until the 50% relationship is re-established. Further, if the system 12 has additional return times in the inventory during the time of a passenger capacity decrease event that includes an excessive number of return times that meet the deadline, these return times can be removed from the inventory to prevent additional guests from obtaining return times during the passenger capacity decrease event. In the provided example, at least 100 guests are removed to reconstruct the relationship. This group of 100 people only corresponds to a subgroup of the 600 return times that meet the deadline in total. The present technology enables finer adjustment of incoming guests with respect to the vehicle capacity and more targeted changes to the return times, which can be addressed only to the guests who are affected without being visible to the total population of the guests. As described herein, the removal can be related to providing a re-accommodation facility available at a point in time after that day.

[0042] In another example, although the capacity reduction is 300 seats per hour, if the number of unprocessed return times for that hour is only 200, the relationship is maintained below 50%, and thus the removal of guests from the virtual queue may not be triggered by the capacity reduction event. However, considering the capacity reduction event, many new return times during this time when additional guests are available can also be re-adjusted or removed from the inventory.

[0043] Removal of guests from the virtual queue in response to a capacity reduction event can be performed in a last-in, first-out manner. That is, a guest having a return time that was most recently assigned can be removed from the virtual queue before a guest having a return time selected earlier in the day. In another example, removal of guests from the virtual queue in response to a capacity reduction event can take into account the size of the group, leaving larger groups and removing smaller groups, or vice versa. In another example, removal of guests from the virtual queue in response to a capacity reduction event can take into account the guest status (e.g., VIP status) to avoid removing guests with a higher status. The guest status (e.g., VIP status) can be based at least in part on whether the guest is an express pass purchaser, an annual pass holder, a resort guest, or a multi-park ticket holder. In another example, removal of guests from the virtual queue in response to a capacity reduction event can take into account the ride history. Guests who rode the amusement park attraction earlier in the day can be removed. Further, guests who have never ridden the amusement park attraction (e.g., first-time riders) can be prioritized over other guests. Further, the virtual queue system can also consider whether the guest is in the virtual queue of another attraction, the type or brand of the guest device 22 associated with the guest, the location of the guest within the amusement park (e.g., the distance of the guest from the amusement park attraction), whether the guest is present within the park, or other factors in determining the removal of guests from the virtual queue in response to a capacity reduction event. In some embodiments, the virtual queue system can determine the removal of guests from the virtual queue in response to a capacity reduction event based on one or more of the factors described above.

[0044] The virtual queue controller is configured to generate and / or identify the subsequent time available for a guest removed from the virtual queue, and generate a re-accommodation time slot within the virtual queue based on the subsequent time available for the guest removed from the virtual queue (block 98). The re-accommodation time slot or re-accommodation space is configured to provide a new return time or option to a guest removed from the virtual queue (block 100). The re-accommodation time slot can be configured to start immediately after the end of the occupancy reduction event. For example, the first new return time can be scheduled for 2:00 PM in response to the occupancy reduction event ending at 2:00 PM. In certain embodiments, the re-accommodation time slot can start during the occupancy reduction event. For example, during a long-term partial outage (e.g., operating at 80% occupancy over multiple hours), the re-accommodation time slot can start 20 minutes after the start of the long-term partial outage. In certain embodiments, the re-accommodation time slot can include a sufficient amount of new return times to accommodate each guest removed from the virtual queue. The re-accommodation time slot can have new return times at different points in time so that guests can flexibly obtain new return times that match their schedules. For example, the return time slots can have new return times at 2:00 PM, 2:15 PM, 2:30 PM, and 2:45 PM.

[0045] The virtual queue controller can be configured to output a delay message to a guest-related device corresponding to a guest removed from the virtual queue. The delay message can include a message indicating that a capacity reduction event has occurred. The delay message can also indicate to the guest that the guest has been removed from the virtual queue. Further, the delay message can be configured to prompt the guest to select a re-entry option (e.g., a new return time) for the virtual queue of the amusement park attraction. The re-entry option can correspond to a new return time within the re-accommodation time slot. The guest can select one of the return options or re-entry options via an input device of the guest-related device (block 102). For example, the guest can have an active wearable. The active wearable can display the delay message on its display (e.g., screen). The delay message can provide the guest with a re-entry option that includes a new return time at 2:00 pm, 2:15 pm, or 2:30 pm. The guest can use the input device to select the return time of 2:00 pm and confirm the selection of the new return time at 2:00 pm. In another example, the new return time may not be convenient for the guest. The delay message can further include a re-entry option to reject the new return time. If the guest rejects the new return time, the virtual queue system can present the guest with a form of electronic compensation (e.g., preferential queue placement for another attraction) for removing the guest from the virtual queue (block 104). Further, the guest-related device is configured to output a re-entry option (e.g., selection, confirmation, or rejection of a new return time) to the virtual queue controller from the guest-related device. In some embodiments, the re-accommodation time slot may not have sufficient new return times for each guest removed from the virtual queue. That is, the total number of guests removed from the virtual queue may be greater than the total number of new return times for the guests removed from the virtual queue. Therefore, some guests may not be re-accommodated.The virtual queue system can present electronic compensation to un-rehoused guests.

[0046] The virtual queue controller is configured to provide a notification indicating a new return time within the rehousing space corresponding to the selected or confirmed new return time to the guest-related device (block 106). The guest-related device can provide the notification to the guest via a display of the guest-related device. In some embodiments, the notification includes a verification (e.g., a code, a scannable indicator, a signal output, etc.) for presentation by the guest at the entrance of the amusement park attraction. The guest can use this verification to enter the ride queue of the amusement park attraction at the new return time (block 108).

[0047] FIG. 4 is a graph of an embodiment of a virtual queue system for an amusement park attraction. Graph 110 includes a capacity reduction event and rehousing time slots 112, 114, 116. In some embodiments, the rehousing time slot 112 is configured to start after the capacity reduction event. In the illustrated embodiment, the rehousing time slot 112 starts immediately after the capacity reduction event. The rehousing time slot 112 includes new return times within the rehousing time slot 112. For example, in the illustrated embodiment, the rehousing time slot 112 is configured to start at 2:00 p.m. and end at 3:00 p.m. Thus, the new return times can be 2:00 p.m., 2:15 p.m., 2:30 p.m., and 2:45 p.m. The new return times can occur in any suitable increment based on the corresponding amusement park attraction.

[0048] In one embodiment, the duration of the re-accommodation time slot is based on the total number of virtual queue return times 114 affected by removal from the virtual queue. That is, the re-accommodation time slot 112 can have a variable size based at least in part on the total number of guests removed from the virtual queue. For example, in the illustrated embodiment, a capacity reduction event can have a partial attraction closure event 130 from 1:00 p.m. to 2:00 p.m. (e.g., one or more ride vehicles of an amusement park attraction moved for maintenance) that reduced the throughput of the ride by 30%. Thus, at least 30% of the guests with return times from 1:00 p.m. to 2:00 p.m. are removed from the virtual queue due to the capacity reduction event. The remaining 70% of the guests (e.g., unaffected guests 132) can retain their return times in the virtual queue during the capacity reduction event. In this example, the amusement park attraction can have a guest throughput of 600 guests per hour. Thus, the virtual queue controller can remove 180 guests from the virtual queue during the capacity reduction event. In one embodiment, the re-accommodation time slot 112 is configured to accommodate all guests removed from the virtual queue within a time frame immediately following the capacity reduction event. Thus, the re-accommodation slot can start at 2:00 p.m. and continue until 2:18 p.m. (e.g., for 18 minutes) to accommodate all 180 guests within the re-accommodation time slot 112. However, in one embodiment, the re-accommodation time slot 112 occurs over an extended time frame to minimize disruption to guests having return times in the virtual queue immediately following the capacity reduction event. For example, in the illustrated embodiment, the re-accommodation time slot 112 starts at 2:00 p.m. and continues until 3:00 p.m.

[0049] In one embodiment, to create sufficient space for the re-accommodation time slot 112, at least some of the guests having a return time during the re-accommodation time slot 112 can be removed from the virtual queue 124. These guests are provided with a re-entry option that includes a new return time within the second re-accommodation time slot 114. Further, at least some of the guests having a return time during the second re-accommodation time slot 114 can be removed from the virtual queue to provide a re-entry option that includes a new return time within the third re-accommodation time slot 116. In another embodiment, the virtual queue system is configured to remove all guests from the virtual queue after a capacity reduction event. Each guest removed from the virtual queue can be provided with a re-entry option. However, guests that had an earlier return time before being removed from the virtual queue can be given priority when selecting a re-entry option. For example, a guest whose original return time is 2:00 PM is given priority over a guest whose original return time is 2:30 PM. In one embodiment, the re-entry options provided to the guests can be restricted based on their respective return times before being removed from the virtual queue.

[0050] In one embodiment, the virtual queue controller is configured to determine the amount of predicted no-shows 122 of an amusement park attraction. For example, the virtual queue controller can determine that 9% of the guests will not arrive at their respective return times (e.g., predicted no-shows 122). Thus, it can be predicted that only 91% of the guests will arrive at each return time (e.g., predicted arrivals 126). The virtual queue controller can be configured to determine the amount of predicted no-shows 122 based at least in part on past data and current virtual queue data. The virtual queue controller can consider time, date, weather patterns, special events, past queue data, current queue data, and other suitable factors when determining the amount of predicted no-shows 122 of an amusement park attraction.

[0051] Generally, a virtual queue controller can be configured to place a number of guests corresponding to the full ride capacity 120 of an amusement park attraction (e.g., 100% of the ride capacity) within a virtual queue 124. For example, if the guest throughput of an amusement park attraction is 600 people per hour, the virtual queue controller can place 600 guests (e.g., 100% of the ride capacity) with a return time between 2:00 PM and 3:00 PM within the virtual queue. However, as described above, generally some guests are not expected to arrive at the return time. Some amusement park attractions include a standby queue separate from the ride queue to fill seats for the predicted no-shows 122. However, an amusement park attraction can close the standby queue and fill the seats for the predicted no-shows 122 with guests from the reboarding time slots to reduce the amount of guests affected by a capacity reduction event. That is, the virtual queue controller can place an amount of guests that exceeds the guest throughput at full ride capacity 120 (e.g., 100%) within the reboarding time slots based on the amount of predicted no-shows 122.

[0052] For example, the guest throughput at full capacity of an amusement park attraction can be 600 people per hour. The virtual queue controller can determine that the amount of expected no-show cancellations 122 between 2:00 PM and 3:00 PM is approximately 9% of the guests in the virtual queue. Based on the amount of expected no-show cancellations 122 and the guest throughput at full ride capacity, the virtual queue controller can place approximately 660 guests within the re-accommodation time slot 112 between 2:00 PM and 3:00 PM. The virtual ride controller can consider the amount of expected no-show cancellations 122 and determine that approximately 600 guests from the virtual queue should actually arrive at the amusement park attraction, and thus the amusement park attraction will operate at full capacity 120 allowing entry only to guests from the virtual queue 124. This may temporarily increase the throughput of guests from the virtual queue, enabling guests to be accommodated in the re-accommodation time slot 112 more quickly. Therefore, it is possible to reduce guests with a return time immediately after a capacity reduction event that needs to be removed from the virtual queue to accommodate the re-accommodation time slot 112.

[0053] In one embodiment, the virtual queue controller can incorporate a predetermined error range while managing the virtual queue during a headcount reduction event. The virtual queue controller can place a number of guests within the re-accommodation time slot 112 that exceeds the throughput of guests at full vehicle capacity 120, based on the predicted amount of no-show cancellations 122 and a predetermined error range of the predicted amount of no-show cancellations 122. Thus, the virtual queue controller can prevent the length of the boarding queue from exceeding a desired amount if more guests arrive at the return time than predicted based on the predicted amount of no-show cancellations 122, by placing fewer excess guests within the virtual queue 124 than the predicted amount of no-show cancellations 122. For example, the virtual queue controller can determine that the predicted amount of no-show cancellations 122 is 40 guests. The predetermined error range of the predicted amount of no-show cancellations 122 can be 25%. Thus, the virtual queue controller can assign only 30 guests instead of assigning 40 guests that exceed the throughput of guests at full vehicle capacity 120.

[0054] Furthermore, the virtual queue controller is configured to limit new return times to guests removed from the virtual queue 124 during a headcount reduction event. Thus, the virtual queue controller can be configured to not accept virtual queue requests from new guests seeking a return time during the re-accommodation time slots 112, 114, 116. The virtual queue controller can be configured to output a signal to the guest-related device indicating that the amusement park attraction is unavailable during the headcount reduction event and during the re-accommodation time slot 112. Preventing new guests from entering the queue during the headcount reduction event and the re-accommodation time slot 112 can help maintain the length of the boarding queue and a consistent throughput of the amusement park attraction during the headcount reduction event and the re-accommodation time slot 112.

[0055] FIG. 5 is a flowchart of an embodiment of a method for determining the size of a re-accommodation time slot of a virtual queue system. At the start of the method, an amusement park attraction can be hit by an occupancy reduction event. The method includes receiving an indication of the occupancy reduction event (block 140). The method further includes determining a decrease in the guest throughput of the amusement park attraction during the occupancy reduction event (block 142). The operator can output the severity of the occupancy reduction event via a user interface so that the virtual queue controller can determine a decrease in the guest throughput of the amusement park attraction during the occupancy reduction event.

[0056] The method can include determining the total number of virtual queue return times of guests in a virtual queue affected by the occupancy reduction event based on the decrease in guest throughput (block 144). The method can also include determining the total number of virtual queue return times affected based on the duration of the occupancy reduction event. The method can further include identifying each individual guest having a virtual queue return time affected (block 146). The memory device can store the virtual queue data of the individual guests. The virtual queue controller can analyze the virtual queue data to determine which guests have a virtual queue return time affected.

[0057] The method can further include generating a re-accommodation time slot in the virtual queue (block 148). The size of the re-accommodation time slot can be based on the total number of virtual queue return times of guests in the virtual queue affected by the occupancy reduction event (block 148). The re-accommodation time slot can include a size large enough to accommodate each guest in the virtual queue affected by the occupancy reduction event. Further, the method can include providing a notification indicating the possibility of a new return time within the re-accommodation time slot to each of the individual guests having a virtual queue return time affected (block 150).

[0058] In this specification, only some features of the present disclosure have been illustrated and described, but many modifications and changes will occur to those skilled in the art. Therefore, it should be understood that the appended claims are intended to cover all such modifications and changes that fall within the true spirit of the present disclosure.

[0059] The technology shown and claimed in this specification refers to and applies to tangible things and specific examples of a practical nature that reliably improve this technical field and are thus not abstract, intangible, or purely theoretical. Further, if any claim appended at the end of this specification includes one or more elements designated as "means for [performing]... [function]" or "steps for [performing]... [function]", such elements shall be construed in accordance with 35 U.S.C. § 112(f). On the other hand, for any claim that includes elements designated in any other form, such elements shall not be construed in accordance with 35 U.S.C. § 112(f).

Claims

1. a virtual queue controller including a processor and a memory; The processor, receiving reduced capacity event instructions from an amusement park attraction; determining a reduction in capacity of the attraction associated with the reduced capacity event; identifying each guest having a return time within a virtual queue for the attraction affected by the reduced capacity event based on the reduced capacity; removing guests having affected return times from the virtual queue; generating a re-admission time slot for the guest removed from the virtual queue, the length of the re-admission time slot being based on a total number of return times affected by the guest removed from the virtual queue, the re-admission time slot following all of the affected return times; selecting two or more updated return times within the re-entry time slot for each of the guests removed from the virtual queue; providing a notification to each guest removed from the virtual queue requesting guest input to select a single updated return time from the two or more updated return times; returning each guest to the virtual queue upon receiving a corresponding selection of the single updated return time; and executing instructions accessed from the memory to cause the virtual queue controller to: Virtual queuing system.

2. the reduced capacity event includes a downtime event for the attraction; 2. The virtual queuing system of claim 1.

3. the reduced capacity event includes a partial outage, and at least one ride vehicle, ride seat, or combination thereof is taken out of operation during the partial outage.

2. The virtual queuing system of claim 1.

4. the reduction in capacity event includes removing the at least one ride vehicle from the attraction, and the number of affected return times is based on a capacity of the ride vehicle.

4. The virtual queuing system of claim 3.

5. the affected return times include a subset of all return times scheduled during the reduced capacity event; 5. The virtual queuing system of claim 4.

6. the virtual queue controller including communication circuitry configured to communicate the notification to a respective guest-associated device of each guest removed from the virtual queue; 2. The virtual queuing system of claim 1.

7. the re-accommodation time slot follows an estimated end of the de-occupancy event.

2. The virtual queuing system of claim 1.

8. the re-accommodation time slot occurs simultaneously with the de-capacity event; 2. The virtual queuing system of claim 1.

9. the virtual queue controller is configured to estimate an amount of no-show return times for the amusement park attraction based at least in part on historical data and current virtual queue data, and at least some of the re-accommodation time slots include excess capacity return times configured to fill in the predicted no-show return times following the end of the reduced capacity event; 2. The virtual queuing system of claim 1.

10. the virtual queue controller is configured to identify the affected return times by determining a reduction in capacity of the attraction associated with the reduced capacity event and determining that a relationship between existing return times within a time window and the reduced capacity is outside a desired tolerance.

2. The virtual queuing system of claim 1.

11. the number of affected return times within a time window is based on reducing existing return times within the time window such that a relationship between the existing return times within the time window and the capacity reduction is within a desired tolerance after reducing the existing return times within the time window.

2. The virtual queuing system of claim 1.

12. an amusement park attraction having a capacity based on the number of available guest seats; A virtual queue controller including a processor and a memory, outputting a notification to curtail guest entry admissions to the amusement park attraction from a virtual queue based at least in part on the reduced capacity event associated with a reduction in the number of available guest seats during the reduced capacity event; identifying guests in the virtual queue having affected return times that relate to a return time to the amusement park attraction during the reduced capacity event; removing at least one guest from the virtual queue having one of the affected return times; generating re-accommodation space within said virtual queue; providing a guest notification to a guest associated device associated with the at least one guest removed from the virtual queue indicating the removal from the virtual queue and a plurality of new return times corresponding to the re-accommodation space; receiving a selection notification of a selection of a new return time among the plurality of new return times by the guest via the guest-associated device; validating the selected new return time when presented for entry at or after the new return time; a virtual queue controller configured to a sensor assembly disposed at an entrance of the amusement park attraction, the sensor assembly configured to receive information from the guest related devices and to transmit information from the guest related devices to the virtual queue controller for verification; A virtual queue system comprising:

13. the plurality of new return times are scheduled for a time after the reduced capacity event; 13. The virtual queuing system of claim 12.

14. the reduced capacity event includes a loss of available guest seats in a single ride vehicle; 13. The virtual queuing system of claim 12.

15. the at least one guest removed from the virtual queue comprises a subset of guests having the same return time such that only some guests having the same return time are removed from the virtual queue.

13. The virtual queuing system of claim 12.

16. the re-accommodation space is based at least in part on a total number of guests removed from the virtual queue; 13. The virtual queuing system of claim 12.

17. receiving instructions for reduced capacity events; determining a decrease in guest throughput at the amusement park attraction during the reduced capacity event; determining a total number of virtual queue return times for guests in the virtual queue affected by the reduced capacity event based on the reduction in guest throughput; Identifying each individual guest that has an affected virtual queue return time; generating re-entry time slots in the virtual queue based on a total number of virtual queue return times for guests in the virtual queue affected by the de-capacity event; providing a notification to each of the individual guests having an affected virtual queue return time indicating a number of available new return times within the re-accommodation time slot; A method comprising:

18. outputting a delay message including a request for confirmation from the individual guest selecting and confirming the new return time; and in response to receiving confirmation from the individual guest, providing a notification to the individual guest indicating the new return time.

20. The method of claim 17.

19. the type of capacity reduction event includes ceasing operation of the amusement park attraction; 20. The method of claim 17.

20. the reduced capacity event includes a partial shutdown, wherein at least one ride vehicle of the amusement park attraction, a ride seat of the amusement park attraction, or a combination thereof is taken out of operation during the partial shutdown; 20. The method of claim 17.

Images