System and method for smart virtual queues

Abstract

The system includes a virtual queue controller configured to receive an indication of a reduced capacity event from an amusement park attraction, determine a reduced capacity for the attraction, identify each guest in the attraction's virtual queue having a return time affected by the reduced capacity event, remove the guests with the affected return times from the virtual queue, generate re-entry time slots for the guests removed from the virtual queue, select two or more updated return times within the re-entry time slots for each of the guests removed from the virtual queue, provide 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, and return each guest to the virtual queue upon receiving a corresponding selection of the single updated return time.

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 Jun. 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 the present disclosure relate to techniques for managing reduced capacity events in virtual queues.

Background Art

[0003] This section is intended to introduce the reader to various aspects of the technology that may be related to the various aspects of the present disclosure described below. This discussion is believed to be helpful in showing the reader the background circumstances and facilitating a better understanding of the various aspects of the present disclosure. Accordingly, these descriptions are to be read from the above perspective and are not to be taken as an admission of prior art.

[0004] Theme parks and amusement park attractions are becoming increasingly popular, and a variety of amusement park attractions are being created that offer guests unique movement and visual experiences. Guests entering various amusement park attractions can utilize virtual queue systems that place them in a virtual queue rather than a physical queue, allowing them to enjoy other features of the amusement park while their position in the virtual queue moves forward. However, the actual ride times of amusement park attractions can be affected by the closure or partial closure of the attraction, which can negate some of the advantages of having a virtual queue, as guests may have to wait for long periods in the loading lines. Therefore, it is recognized that it is desirable to improve virtual queue systems during capacity reduction events (closure or partial closure of amusement park attractions). [Overview of the project]

[0005] The following summarizes several embodiments that fall within the same scope as the subject matter of the original claims. These embodiments are not intended to limit the scope of the disclosure, but rather to outline some of the disclosed embodiments. In practice, the disclosure may include a variety of forms that are 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 memory. The processor is configured to execute instructions accessed from memory to cause the virtual queue controller to perform the following actions: receive instructions for a capacity reduction event from an amusement park attraction; determine the capacity reduction of the attraction associated with the capacity reduction event; identify each guest in the attraction's virtual queue who has a return time affected by the capacity reduction event, based on the capacity reduction; remove guests with affected return times from the virtual queue; and generate a reaccommodation time slot for the guests removed from the virtual queue. 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. The reaccommodation time slot follows all affected return times. The processor is also configured to execute instructions accessed from memory to cause the virtual queue controller to: select two or more updated return times within a re-accommodation time slot for each guest removed from the virtual queue; provide each guest removed from the virtual queue with a notification requesting guest input to select a single updated return time from the two or more updated return times; and return each guest to the virtual queue when the corresponding selection of a single updated return time is received.

[0007] According to one embodiment, a virtual queue system is provided, comprising an amusement park attraction having a capacity based on the number of available guest seats, and a virtual queue controller having a processor and memory. The virtual queue controller is configured to output a notification to restrict guest entry from the virtual queue to the amusement park attraction, at least in part on a capacity reduction event related to a reduction in the number of available guest seats during a capacity reduction event, to identify guests who have affected return times in the virtual queue that are related to the return time to the amusement park attraction during a capacity reduction event, to remove at least one guest who has one of the affected return times from the virtual queue, to create re-accommodation space in the virtual queue, to provide a guest notification to a guest-related 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, to receive a selection notification from the guest via the guest-related device regarding the selection of one of the plurality of new return times, and to validate the selected new return time when it is presented for entry after the new return time. The virtual queue system includes a sensor assembly located at the entrance of an amusement park attraction, which is configured to receive information from guest-related devices and transmit the information from the guest-related devices to a virtual queue controller for verification.

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

[0009] A better understanding of these and other features, aspects and advantages of this disclosure will be gained by reading the following detailed description while referring to the attached drawings, which indicate the same parts throughout with the same reference numerals. [Brief explanation of the drawing]

[0010] [Figure 1] This is a schematic diagram of an embodiment of an amusement park including a virtual queue system according to the present disclosure.

[0011] [Figure 2] This is a block diagram of an embodiment of a virtual queue system according to an aspect of the present disclosure.

[0012] [Figure 3] This is a flowchart of an embodiment of the virtual queue system technology during a capacity reduction event according to the aspects of this disclosure.

[0013] [Figure 4] This is a graph of an embodiment of a virtual queue system for an amusement park attraction according to the aspects of this disclosure.

[0014] [Figure 5]This is a flowchart of an embodiment of a method for determining the size of available re-accommodation time slots in a virtual queue system according to an aspect of the present disclosure. [Modes for carrying out the invention]

[0015] The following describes one or more specific embodiments of this disclosure. For the sake of brevity, this specification may not describe all features of the embodiments. It should be understood that the development of any such implementation found in any engineering or design project will require numerous implementation-specific decisions to achieve the developer's specific objectives, such as compliance with system-related and business-related constraints, which may vary by implementation. Furthermore, while such development efforts may be complex and time-consuming, it should be understood by those skilled in the art who benefit from this disclosure that they are routine design, fabrication, and manufacturing endeavors.

[0016] When describing elements of the various embodiments of this disclosure, articles such as “a,” “an,” and “the” are intended to indicate that there is one or more of these elements. The terms “comprising,” “including,” and “having” are intended to be comprehensive and mean that there may be further elements other than those listed. Furthermore, any reference in this disclosure to “one embodiment” or “a particular embodiment” should not be interpreted as excluding the existence of further embodiments, including the features described.

[0017] Theme parks and amusement park attractions are becoming increasingly popular, and a variety of amusement park attractions are being created that offer guests unique movement and visual experiences. Guests entering various amusement park attractions can utilize virtual queue systems that place guests in a virtual queue rather than a physical queue, allowing them to enjoy other features of the amusement park while their position in the virtual queue moves forward. Some virtual queue systems provide guests with a return time indicating the time they will arrive at the amusement park attraction. Guests are instructed to return to the amusement park attraction at the return time and wait in a limited-length physical queue or boarding line before entering the amusement park attraction (for example, boarding the ride vehicle of the amusement park attraction). It should be understood that the boarding line can also mean a group of guests gathered in a boarding area to ride, which may or may not be first-in, first-out. Therefore, as used herein, the boarding line can mean a limited number of guests gathered in a boarding area. Generally, a ride area or a physical queue or line of a limited length acts as a buffer zone for an amusement park attraction, ensuring that there are enough guests present to fill the attraction to its full capacity at the time of ride. However, a ride line of a limited length can also be shortened to reduce the time guests need to spend in the line, allowing them more time to enjoy other aspects of the amusement park (e.g., dining, shopping, and other entertainment facilities). A virtual queue system not only shortens the length of the ride line but also allows a predetermined number of guests to arrive at the attraction's entry area so that there are enough guests to fill the amusement park attraction to its full capacity during each ride cycle or attraction operation.

[0018] Unfortunately, amusement park attractions may not operate at full capacity due to capacity reduction events (e.g., periods of closure and / or partial closure of the attraction). During capacity reduction events, more guests may enter the queue (e.g., arrive from the virtual queue at or after reopening time) than leave the queue (e.g., board the amusement park attraction). This can cause delays for guests already in the queue. The queue becomes longer because more guests are entering the queue than leaving, resulting in guests having to wait in line for extended periods after returning to the amusement park attraction at or after reopening time. Long waits in the queue can cause inconvenience and / or frustration for guests, negating some of the benefits of providing a virtual queue.

[0019] Furthermore, delays caused by capacity reduction events can lead to longer wait times in ride queues, potentially having a further negative impact on the overall efficiency of the amusement park. Guests may anticipate exiting rides at a specific time based on their expected return time and plan accordingly (e.g., family lunches, subsequent amusement park attraction queues). However, longer wait times in ride queues can delay guests' expected exit times, potentially disrupting their plans. Consequently, delays in ride queues can cause guests to arrive late to or not show up at their virtual return times for subsequent amusement park attractions, leading to delays and / or reduced efficiency for those attractions. Additionally, delays in ride queues can cause guests to miss family meal plans due to being stuck in queues during capacity reduction events, potentially causing further inconvenience and / or dissatisfaction.

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

[0021] Figure 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, guest-related devices 22 (e.g., active wearable guest devices, guest mobile devices, etc.), and other components that coordinate the operation of each virtual queue for amusement park attractions 24 within the amusement park 10. As described above, guests 26 entering various amusement park attractions can use the virtual queue system 12 to enter virtual queues rather than physical queues for the amusement park attractions 24. In one embodiment, a guest 26 can use the guest-related devices 22 to submit a virtual queue request to enter the virtual queue for an amusement park attraction 24. In another embodiment, a guest 26 can enter a virtual queue request via kiosks 28 located throughout the amusement park 10. In one embodiment, the kiosks 28 are located close to the amusement park attractions 24. In another embodiment, the kiosk 28 is located in a general area of ​​the amusement park (for example, a 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 as the guest progresses towards entry into 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 choose at their discretion from a set of available return times, and some guests may choose a later return time based on their itinerary for the 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 pre-set at the beginning of the day and can be allocated to guests until they are no longer available.

[0024] In certain embodiments, the virtual queue system 12 can also incorporate other ways of determining the return time or queue position and providing it to the guest 26. In certain 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, a first guest 36, a second guest 38, and a third guest 40 can each send respective first, second, and third virtual queue requests. The first guest 36 can be assigned to a first position within the virtual queue, the second guest 38 can be assigned to a second position within the virtual queue, and the third guest 40 can be assigned to a 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 certain 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 certain 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 check 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 an effective or invalid return time can be performed by a virtual queue controller 42 communicatively coupled to the sensor 16 as shown herein.

[0026] Figure 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 guest-related equipment 22, amusement park operator equipment 44, and amusement park attraction entry systems 46, or a combination of these. 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 communication circuit 48a. The communication circuits can include antennas, wireless transceiver circuits, 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 via wireless communication paths such as infrared (IR) wireless communication, satellite communication, broadcast radio, microwave radio, Bluetooth, Zigbee, Wi-Fi, UHF, NFC, etc. In one embodiment, communication circuits 48a, 48b, 48c, and 48d include a plurality of IR transceivers placed within the environment of an amusement park attraction.

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

[0028] As described above, the virtual queue controller 42 is configured to output notifications 56 for guests to each guest-related device 22. For example, a notification 56 may instruct a guest to return to an amusement park attraction at a specified return time. In another example, the notification 56 may include a delay message. In one embodiment, the virtual queue controller 42 is configured to identify guests in virtual queues affected by a capacity reduction event at an amusement park attraction and to output a delay message to the guests, including the return time for the affected virtual queue. 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 may have a processor 50b and memory 52b. Furthermore, the guest-related device 22 may include an operator interface 60b with 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 a 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 check the return time via the input device 64b.

[0029] In one embodiment, notification 56 may instruct the guest to return to the amusement park attraction and enter the ride queue at the guest's return time. The guest can enter the ride queue through the entry gate 66 of the amusement park attraction entry system at each return time. The entry gate 66 may be configured to detect when the guest has entered the ride queue. The amusement park attraction entry system 46 may include a processor 50d and memory 52d. The processor 52d may be configured to execute an instruction to output a counter signal 68 to the virtual queue controller 42 via a communication circuit 48d, indicating that the guest has entered the ride area, at least in part based on the detection of the guest and instructions stored in the memory device. In one embodiment, the entry gate 66 is configured to output the counter signal 68 directly to the virtual queue controller 42. In one embodiment, the entry gate 66 includes a sensor assembly 70 (for example, including a sensor 16) configured to detect guest-related equipment 22. The virtual queue controller 42 may be configured to determine when the guest has entered the ride queue, at least in part based on the detection of guest-related equipment 22 at the entry gate 66. In one embodiment, the entry gate 66 also verifies that the guest has a valid return time at the time of entry through the entry gate 66. The virtual queue system 12 can determine the number of guests who have entered the boarding queue based on the counter signals 68 received from the amusement park attraction entry system 46 and / or the entry gate 66. In one embodiment, the amusement park attraction may include a revolving door 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 may also include a boarding gate 72 configured to detect guests who have left the boarding queue (for example, who have entered an amusement park attraction). The amusement park attraction entry system 46 and / or boarding gate 72 may be configured to output a second counter signal 74 to a virtual queue controller 42 indicating the detection of a guest who has left the boarding queue. The virtual queue controller 42 may be configured to determine the total number of guests in the boarding queue based on the second counter signal 74. In one embodiment, the boarding queue area may include a sensor assembly 70 of the amusement park attraction entry system 46. The sensor assembly 70 may 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 may 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 described herein, the virtual queue controller 42 is configured to manage a virtual queue for an attraction and to remove one or more guests from the virtual queue in response to a capacity reduction event. Instructions for a capacity reduction event may be based on signals received from the attraction operator, but the virtual queue controller 42 may also be configured to identify capacity reduction events based on queue information. In one embodiment, the virtual queue controller 42 is configured to determine that an amusement park attraction may be experiencing a capacity reduction event, at least in part, based on the total number of guests in the boarding queue exceeding a predetermined threshold or tolerance. Upon determining that an amusement park attraction may be experiencing a capacity reduction event, the virtual queue controller 42 may output a capacity reduction notification 78 to the amusement park operator device 44 indicating that the amusement park attraction may be experiencing a capacity reduction event. The amusement park operator device 44 may be a computer, smartphone, tablet, laptop, etc. The amusement park operator device 44 may have a processor 50c and memory 52c. Furthermore, the amusement park operator device may include an operator interface 60c equipped with 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 may be configured to display a capacity reduction notification 78 on the display 62c. The capacity reduction notification 78 may indicate to the operator that an amusement park attraction may be experiencing a capacity reduction event. The capacity reduction notification 78 may include data for the operator to determine whether an 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 may also include a prompt for the operator to enter an operator response 80 (e.g., confirmation or rejection of the capacity reduction event) via the input device 64c.In one embodiment, upon receiving confirmation of a capacity reduction event, the virtual queue controller 42 may send an instruction request 82 which includes a prompt requesting the operator to provide operator input 84 relating to the severity and / or duration of the capacity reduction event.

[0032] In one embodiment, an operator can manually output a capacity reduction event signal 86 to a virtual queue controller 42 via the operator interface 60c. For example, ride vehicles in an amusement park attraction may require maintenance. An operator can guide a ride vehicle from the main track to a service track for an amusement park attraction. If there are no ride vehicles on the main track, the amusement park attraction may not have enough rides to operate at full capacity. An 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 may include data indicating the amount of capacity reduction, the expected duration of the capacity reduction, etc. In one embodiment, an operator can also output a capacity reduction event signal 86 for other reasons, including food spills, weather delays, or complete system maintenance (e.g., shutdown). Furthermore, an 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 capacity reduction can be a function of the overall reduction in available seats per ride cycle, which is the average ride operating time (e.g., 2 minutes, 5 minutes). For example, if a single ride vehicle with 6 seats is idle, the capacity reduction may be 6 seats per ride cycle. If a ride normally has 120 seats at full capacity across all ride vehicles and operates an average of 10 times per hour (1200 guests per hour), the loss of 6 seats represents a 6% reduction in ride capacity, or a loss of 72 seats per hour. Similarly, if one seat in a ride vehicle is idle due to food spills, the capacity reduction may be 1 seat per ride 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 confirmation of a capacity reduction event or receipt of a capacity reduction event signal 86 from the amusement park operator device 44.

[0035] Figure 3 is a flowchart of an embodiment of the virtual queue system during a capacity reduction event (block 90). A capacity reduction event can include a partial shutdown of an amusement park attraction. For example, a partial shutdown can include shutting down at least one ride vehicle, ride seat, or combination thereof of an amusement park attraction. During a partial shutdown, the amusement park attraction is configured to operate at a rate greater than 0% but less than 100% of its full ride capacity. In one embodiment, the virtual controller is configured to output a notification that restricts guest entry from the virtual queue to the amusement park attraction based at least partially on a capacity reduction event. Furthermore, a capacity reduction event can also include a stop-time event for the amusement park attraction. A stop-time event can include a complete shutdown of the amusement park attraction, and therefore the amusement park attraction will cease operation during a stop-time event. Specifically, the amusement park is configured to operate at 0% of its full ride capacity during a stop-time event.

[0036] During capacity reduction events, the number of guests entering the queue for an amusement park attraction is likely to exceed the number of guests leaving the queue (for example, entering the attraction), so queue lengths may begin to increase based on the percentage reduction in the amusement park attraction's capacity. A virtual queue system can be configured to limit guest entry into the queue for an amusement park attraction in order to avoid excessive waiting times within the queue.

[0037] In one embodiment, to restrict guest entry into the boarding queue, the virtual queue controller is configured to identify queue return times that are affected by a capacity reduction event (block 92). For example, a guest whose return time falls during a stop time event is likely to be affected by the capacity reduction event because they are assumed to spend more time in the boarding queue during the stop time event. In another example, a guest whose return time falls immediately after a capacity reduction event is likely to be affected because the boarding queue may become longer than a predetermined length, potentially causing them to wait in the queue for an extended period.

[0038] In embodiments where an estimated return time is provided to guests as a notification or reminder (e.g., output to guest-related device 22) based on a specific position in a virtual queue that dynamically moves forward as guests ahead enter the attraction, the virtual queue controller can be configured to identify affected positions in the virtual queue corresponding to the estimated return time affected by the 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 affected positions in the virtual queue (and these associated affected return times).

[0039] The virtual queue controller may, after several capacity reduction events, determine that no return times were affected by the capacity reduction events. In other words, the virtual queue controller may not be able to identify guests whose return times are affected by the capacity reduction events. In such cases, the virtual queue controller does not take any further action in response to the capacity reduction events. However, in some cases, the virtual queue controller can determine that at least one return time is affected by the capacity reduction event (block 94). The virtual queue controller can be configured to remove affected return times, or guests with affected return times, from the virtual queue, rather than having guests in the virtual queue whose return times are affected sit in the boarding queue for an extended period of time (block 96). The virtual queue controller can be configured to store data in a memory device indicating which guests or return times have been removed from the virtual queue.

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

[0041] The virtual queue controller 42 can be configured to achieve a predetermined relationship between return times and passenger capacity over a specific time window. That is, return times that begin at a point in time within a time window and expire or become valid at that point in time can be considered relevant to that time window. In one example, the virtual queue controller 42 can be configured to keep the number of return times expiring or becoming valid within a particular time below a specific percentage of the total capacity for that time. In one example, the target percentages of return times to total capacity are 50% or less, 35% or less, and 25% or less. If the percentage relationship changes due to a decrease in capacity, the virtual queue controller 42 is configured to remove guests from the virtual queue during the relevant time window until the desired relationship is re-established. For example, with a 50% target, the vehicle has 1200 guests per hour, and there are approximately 600 guests whose return times expire within a particular time. However, if five vehicles are removed from operation, resulting in a total capacity reduction of 30 seats per ride cycle, and assuming 10 ride cycles occur per hour, the total ride capacity will decrease by 300 seats per hour. In such an example, 600 return times during that time represent more than 50% of the capacity. Therefore, the virtual queue controller 42 can remove guests from the virtual queue during that time window until 50% of the relationships are re-established. Furthermore, if system 12 has additional return times in its inventory during a capacity reduction event that includes an excess number of expiring return times, it can remove these return times from the inventory to prevent further guests from acquiring return times during the capacity reduction event. In the provided example, at least 100 guests are removed to rebuild the relationships. This group of 100 represents only a subgroup of the 600 expiring return times. This technology allows for finer-grained adjustment of incoming guests to ride capacity and more targeted changes to return times, which can be applied only to affected guests without being visible to the total guest population. As described herein, removal may involve providing a re-containment facility that is available at a later point in time.

[0042] In another example, if a capacity reduction of 300 seats occurs per hour, but there are only 200 unprocessed return time slots during that time, the relationship remains below 50%, and therefore the capacity reduction event may not trigger the removal of guests from the virtual queue. However, considering the capacity reduction event, many new return time slots during this time that are available to more guests can be readjusted or removed from the inventory.

[0043] Removing guests from a virtual queue in response to a capacity reduction event can be done on a last-in, first-out basis. That is, guests with a recently allocated return time can be removed from the virtual queue before guests with a return time selected earlier in the day. In another example, removing guests from a virtual queue in response to a capacity reduction event can take group size into consideration, removing smaller groups while keeping larger groups, or vice versa. In yet another example, removing guests from a virtual queue in response to a capacity reduction event can take guest status (e.g., VIP status) into consideration, avoiding the removal of higher-status guests. Guest status (e.g., VIP status) can be based at least in part on whether the guest is an Express Pass holder, an Annual Pass holder, a Resort Guest, or a Multi-Park Ticket holder. In yet another example, removing guests from a virtual queue in response to a capacity reduction event can consider ride history. Guests who rode the amusement park attraction earlier in the day can be removed. Furthermore, guests who have never ridden the amusement park attraction before (e.g., first-time passengers) may be given priority over other guests. In addition, the virtual queue system may also consider, in deciding whether to remove a guest from the virtual queue in response to a capacity reduction event, whether the guest is in the virtual queue for another attraction, the type or brand of guest device 22 associated with the guest, the guest's location within the amusement park (e.g., the guest's distance from the amusement park attraction), whether the guest is present in the park, or other factors. In some embodiments, the virtual queue system may decide whether to remove a guest 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 to guests removed from the virtual queue and to generate re-accommodation time slots within the virtual queue based on the subsequent time available to guests removed from the virtual queue (block 98). The re-accommodation time slots or re-accommodation space are configured to provide guests removed from the virtual queue with a new return time or option (block 100). The re-accommodation time slots may be configured to start immediately after the end of a de-accommodation event. For example, the first new return time may be scheduled for 2:00 p.m., given that the de-accommodation event ends at 2:00 p.m. In some embodiments, the re-accommodation time slots may start during a de-accommodation event. For example, during a prolonged partial shutdown (e.g., operating at 80% occupancy for several hours), the re-accommodation time slots may start 20 minutes after the start of the prolonged partial shutdown. In some embodiments, the re-accommodation time slots may include enough new return time to accommodate each guest removed from the virtual queue. Re-accommodation time slots can have new return times at different points in time, allowing guests flexibility to choose a new return time that suits their schedule. For example, a re-accommodation time slot could 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 delayed message to guest-related devices corresponding to guests removed from the virtual queue. The delayed message may include a message indicating that a capacity reduction event has occurred. The delayed message may also indicate to the guest that they have been removed from the virtual queue. Furthermore, the delayed message may 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 may correspond to a new return time within a re-accommodation time slot. The guest may select either the return option or the re-entry option via an input device on the guest-related device (block 102). For example, the guest may have an active wearable. The active wearable may display the delayed message on its display (e.g., a screen). The delayed message may offer the guest re-entry options including new return times at 2:00 PM, 2:15 PM, or 2:30 PM. The guest may use the input device to select the 2:00 PM return time and confirm their selection of a new return time at 2:00 PM. In another example, the new return time may not be convenient for the guest. The delayed message may further include a re-entry option to reject a new return time. If a guest rejects a new return time, the virtual queue system may present the guest with a form of electronic compensation for removing the guest from the virtual queue (e.g., preferential queuing for another attraction) (block 104). Furthermore, the guest-related device is configured to output re-entry options (e.g., selection, confirmation, or rejection of a new return time) from the guest-related device to the virtual queue controller. In some embodiments, there may not be enough re-accommodation time slots 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 available for guests removed from the virtual queue. Consequently, some guests may not be re-accommodated.The virtual queue system can offer electronic compensation to guests who are not re-accommodated.

[0046] The virtual queue controller is configured to provide guest-related devices with notifications indicating new return times in the re-accommodating space corresponding to selected or confirmed new return times (block 106). Guest-related devices may provide notifications to guests via their displays. In one embodiment, the notification includes verification (e.g., a code, scannable indicator, signal output, etc.) for guests to present at the entrance to an amusement park attraction. Guests can use this verification to enter the ride queue for the amusement park attraction at the new return time (block 108).

[0047] Figure 4 is a graph of an embodiment of a virtual queue system for an amusement park attraction. Graph 110 includes capacity reduction events and re-accommodation time slots 112, 114, and 116. In one embodiment, re-accommodation time slot 112 is configured to begin after a capacity reduction event. In the illustrated embodiment, re-accommodation time slot 112 begins immediately after a capacity reduction event. Re-accommodation time slot 112 includes new return times within re-accommodation time slot 112. For example, in the illustrated embodiment, re-accommodation time slot 112 is configured to begin at 2:00 p.m. and end at 3:00 p.m. Thus, new return times could be 2:00 p.m., 2:15 p.m., 2:30 p.m., and 2:45 p.m. New return times can occur in any preferred increment based on the corresponding amusement park attraction.

[0048] In one embodiment, the duration of a recapture time slot is based on the total number of affected virtual queue return times 114 removed from the virtual queue. That is, the recapture 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 may include a partial attraction closure event 130 from 1:00 PM to 2:00 PM that reduces ride throughput by 30% (e.g., one or more ride vehicles of an amusement park attraction are moved for maintenance). Thus, at least 30% of guests with return times between 1:00 PM and 2:00 PM are affected by the capacity reduction event and removed from the virtual queue. The remaining 70% of guests (e.g., unaffected guests 132) can retain their return times in the virtual queue even during the capacity reduction event. In this example, the amusement park attraction may have a guest throughput of 600 people per hour. Therefore, 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 de-accommodation event. Thus, the re-accommodation slot may start at 2:00 PM and last until 2:18 PM (for example, 18 minutes) to accommodate all 180 guests within the re-accommodation time slot 112. However, in another embodiment, the re-accommodation time slot 112 extends over a time frame to minimize disruption to guests who have a return time in the virtual queue immediately following the de-accommodation event. For example, in the illustrated embodiment, the re-accommodation time slot 112 starts at 2:00 PM and lasts until 3:00 PM.

[0049] In one embodiment, to create sufficient space for a re-accommodation time slot 112, at least some guests whose return time falls within the re-accommodation time slot 112 can be removed from the virtual queue 124. These guests are offered a re-entry option that includes a new return time within a second re-accommodation time slot 114. Furthermore, at least some guests whose return time falls within the second re-accommodation time slot 114 can also be removed from the virtual queue to provide a re-entry option that includes a new return time within a 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 may be offered a re-entry option. However, guests who had an earlier return time before being removed from the virtual queue may be given priority when selecting a re-entry option. For example, a guest whose original return time was 2:00 PM would have priority over a guest whose original return time was 2:30 PM. In one embodiment, the re-entry options offered to guests can be restricted based on their respective return times before being removed from the virtual queue.

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

[0051] Generally, a virtual queue controller can be configured to place a number of guests in a virtual queue 124 that corresponds to the full ride capacity 120 (e.g., 100% ride capacity) of an amusement park attraction. 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% ride capacity) in the virtual queue with a return time between 2:00 PM and 3:00 PM. However, as mentioned above, it is generally expected that some guests will not arrive at the return time. Some amusement park attractions include a separate waiting line in addition to the ride line to fill the seats for the expected number of no-shows 122. However, to reduce the number of guests affected by a capacity reduction event, the amusement park attraction may close the waiting line and fill the seats for the expected number of no-shows 122 with guests from the re-capacity time slot. In other words, the virtual queue controller can place a number of guests in a re-accommodation time slot that exceeds the guest throughput when the vehicle is full capacity (e.g., 100%), based on the predicted amount of unauthorized cancellations 122.

[0052] For example, the guest throughput of an amusement park attraction at full capacity can be 600 people per hour. The virtual queue controller can determine that the predicted number of no-shows 122 between 2:00 PM and 3:00 PM is approximately 9% of the guests in the virtual queue. Based on the predicted number of no-shows 122 and the guest throughput at full 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 determine, taking into account the predicted number of no-shows 122, that approximately 600 guests from the virtual queue should actually arrive at the amusement park attraction, and therefore the amusement park attraction will operate at full capacity 120, allowing only guests from the virtual queue 124 to enter. This may temporarily increase the guest throughput from the virtual queue, allowing guests to be accommodated in the re-accommodation time slot 112 more quickly. Therefore, it is possible to reduce the number of guests whose return time immediately follows a capacity reduction event that needs to be removed from the virtual queue in order 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 capacity reduction event. Based on the predicted amount of no-shows 122 and a predetermined error range for the predicted no-shows 122, the virtual queue controller can place a number of guests in the re-accommodation time slot 112 that exceeds the guest throughput at full ride capacity 120. Thus, the virtual queue controller can place fewer excess guests in the virtual queue 124 than the predicted amount of no-shows 122 to prevent the queue length from exceeding a desired amount if more guests arrive at the re-accommodation time than predicted based on the predicted amount of no-shows 122. For example, the virtual queue controller can determine that the predicted amount of no-shows 122 is 40 guests. The predetermined error range for the predicted no-shows 122 can be 25%. Thus, the virtual queue controller can allocate only 30 guests instead of allocating 40 guests, which exceeds the guest throughput at full ride capacity 120.

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

[0055] Figure 5 is a flowchart of an embodiment of a method for determining the size of a re-accommodation time slot in a virtual queue system. To begin the method, an amusement park attraction may experience a capacity reduction event. The method includes a step of receiving notification of a capacity reduction event (block 140). The method further includes a step of determining the decrease in guest throughput of the amusement park attraction during the capacity reduction event (block 142). The operator can output the severity of the capacity reduction event via a user interface so that the virtual queue controller can determine the decrease in guest throughput of the amusement park attraction during the capacity reduction event.

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

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

[0058] While this specification illustrates and describes only some features of the present disclosure, many modifications and changes will come to mind for those skilled in the art. Therefore, it should be understood that the appended claims are intended to cover all such modifications and changes as well as those that constitute the actual spirit of the present disclosure.

[0059] The claimed technologies described herein refer to and apply to tangible objects and specific examples of a practical nature that are not abstract, intangible, or purely theoretical, but which certainly improve the art. Furthermore, if any of the claims appended to the end of this specification contain one or more elements designated as "...means for performing [function]" or "...steps for performing [function]," such elements should be interpreted in accordance with 112(f) of the U.S. Patent Act. On the other hand, any claim containing elements designated in any other form should not be interpreted in accordance with 112(f) of the U.S. Patent Act.

Claims

1. A virtual queue controller includes a processor and memory, which places the guest in a virtual queue upon the guest's request and provides an estimated time for the guest to reach the front of the virtual queue. The aforementioned processor, Receiving instructions from an amusement park attraction for a capacity reduction event, which is an event that reduces the capacity of the attraction, To determine the reduction in the capacity of the attraction related to the aforementioned capacity reduction event, Based on the capacity reduction, identify the guests whose expected time is provided to be affected by the capacity reduction event, Remove the guests whose estimated time of impact has been provided from the virtual queue, Generating a re-accommodation time slot for assigning a new estimated time for the guest removed from the virtual queue, wherein the length of the re-accommodation time slot is based on the total number of the affected estimated times for the guest removed from the virtual queue, and the re-accommodation time slot is configured to begin after the end of the capacity reduction event; From within the aforementioned re-accommodation time slot, assign two or more new non-overlapping estimated times for the guest removed from the virtual queue, To provide the guest removed from the virtual queue with a notification requesting guest input to select one new expected time from the two or more new expected times, When a corresponding selection of the aforementioned new estimated time is received, the guest is returned to the virtual queue, It is configured to execute instructions accessed from the memory in order to cause the virtual queue controller to perform the following action. Virtual queue system.

2. The capacity reduction event includes the attraction's shutdown event, The virtual queue system according to claim 1.

3. The capacity reduction event includes a partial shutdown event in which at least one ride vehicle, ride seat, or combination thereof used in the attraction is partially shut down. The virtual queue system according to claim 1.

4. The capacity reduction event includes an event in which at least one ride vehicle is removed from the attraction, and the number of expected affected times is based on the number of seats in the ride vehicle. The virtual queue system according to claim 3.

5. The affected expected times include a subset of all expected times scheduled during the capacity reduction event. The virtual queue system according to claim 4.

6. The virtual queue controller includes a communication circuit configured to transmit the notification to the respective guest-related device of each guest removed from the virtual queue. The virtual queue system according to claim 1.

7. The aforementioned re-accommodation time slot occurs simultaneously with the capacity reduction event. The virtual queue system according to claim 1.

8. The virtual queue controller is configured to estimate the expected amount of no-shows for the amusement park's attractions based at least partially on historical data and current virtual queue data, and to allocate guests to at least a portion of the re-accommodation time slots to fill the expected amount of no-shows after the capacity reduction event has ended. The virtual queue system according to claim 1.

9. The virtual queue controller is configured to identify the affected expected time by determining the capacity reduction of the attraction associated with the capacity reduction event and determining that the relationship between the number of existing expected times within the time window associated with the time the capacity reduction event occurs and the capacity reduction is outside a desired acceptable range. The virtual queue system according to claim 1.

10. The number of affected expected times within a time window related to the time when the capacity reduction event occurs is based on reducing the number of existing expected times within the time window such that the relationship between the number of existing expected times within the time window and the capacity reduction falls within a desired acceptable range after the reduction in the number of existing expected times within the time window. The virtual queue system according to claim 1.

11. Amusement park attractions have a capacity based on the number of available guest seats, A virtual queue controller comprising a processor and memory, which places a guest in a virtual queue upon the guest's request and provides an estimated time for the guest to reach the head of the virtual queue, Based at least in part on the capacity reduction event, which is an event in which the capacity of the amusement park's attractions is reduced, a notification is issued to restrict guest entry permission from the virtual queue to the amusement park's attractions. Identify the guests for whom the predicted time will be affected by the capacity reduction event, Remove at least one guest from the virtual queue for whom the aforementioned expected time of impact has been provided. A re-accommodation space is created within the aforementioned virtual queue, The guest-related device associated with the at least one guest removed from the virtual queue is provided with a guest notification indicating the removal from the virtual queue and a plurality of new expected times corresponding to the re-accommodation space. The guest receives a selection notification via the guest-related device regarding the selection of one of the multiple new expected times. The selected new predicted time is validated when it is presented for entry after the new predicted time. A virtual queue controller configured as follows, A sensor assembly located at the entrance of an attraction in the amusement park, 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, A virtual queue system equipped with these features.

12. The aforementioned multiple new predicted times are scheduled for the time after the capacity reduction event. The virtual queue system according to claim 11.

13. The aforementioned capacity reduction event includes the loss of available guest seats in a single vehicle. The virtual queue system according to claim 11.

14. The at least one guest removed from the virtual queue includes a subset of guests who were given the same expected time, such that only some of the guests given the same expected time are removed from the virtual queue. The virtual queue system according to claim 11.

15. The aforementioned re-accommodation space is at least partially based on the total number of guests removed from the virtual queue, The virtual queue system according to claim 11.

16. A method performed by a virtual queue controller, which includes a processor and memory, places a guest in a virtual queue upon the guest's request, and provides an estimated time for the guest to reach the head of the virtual queue, The aforementioned processor receives instructions for a capacity reduction event, which is an event that reduces the capacity of an amusement park attraction. The processor determines the decrease in guest throughput of an amusement park attraction during the capacity reduction event, The processor determines, based on the decrease in guest throughput, the total number of expected time periods affected by the capacity reduction event. The processor identifies the guest for whom the affected expected time has been provided, The processor generates a re-accommodation time slot in the virtual queue for guests for whom the expected time of the capacity reduction event has been provided, with a size based on the total number of the expected time of the affected guests. The processor provides each of the affected guests for whom the expected time has been provided with a notification indicating a number of new available expected times within the re-accommodation time slot. Methods that include...

17. The processor outputs a delay message including a request for confirmation from an individual guest to select and confirm the new estimated time, and the processor, upon receiving confirmation from the individual guest, provides the individual guest with a notification indicating the new estimated time. The method according to claim 16.

18. The aforementioned capacity reduction event includes an event in which the operation of the amusement park's attractions stops. The method according to claim 16.

19. The capacity reduction event includes a partial shutdown event in which at least one ride vehicle of the amusement park attraction, a ride seat of the amusement park attraction, or a combination thereof partially ceases operation. The method according to claim 16.

Images