Systems and methods for intelligent virtual queues

Abstract

A system includes a virtual queue controller configured to: receive an indication of a capacity reduction event from an amusement park spot; determining a reduction in the capacity of the scenic spot; identifying each customer having a return time in a virtual queue of scenic spots affected by the capacity reduction event; removing the customer with the influenced return time from the virtual queue; and generating a re-adapted time slot for the customer removed from the virtual queue; selecting, for each of the customers removed from the virtual queue, two or more updated return times within the adaptive time slot; providing, to each customer removed from the virtual queue, a notification requesting customer input to select a single updated return time from two or more updated return times; and upon receiving a corresponding selection of the single updated return time, returning each customer to the virtual queue.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application is a divisional of Chinese patent application No. 202080046575.0, filed on June 23, 2020, entitled “System and method for intelligent virtual queue”. The Chinese patent application claims the benefit of U.S. Provisional Application No. 62 / 867634, filed on June 27, 2019, entitled “System and method for intelligent virtual queue”, the disclosure of which is incorporated by reference for all purposes. Background Art

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

[0003] This section is intended to introduce the reader to various technical aspects that may be related to various aspects of the present disclosure, which are described below. This discussion is considered to help provide the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Therefore, it should be understood that these statements will be read from this perspective, rather than as an admission of the prior art.

[0004] Theme parks or amusement park attractions have become increasingly popular, and various amusement park attractions have been created to provide passengers with unique motion and visual experiences. Patrons entering various amusement park attractions can utilize a virtual queuing system that places guests in a virtual queue rather than a physical queue, which allows the patrons to enjoy other features of the amusement park while their position advances in the virtual queue. However, a shutdown or partial closure of an amusement park attraction may have an impact on the actual loading time at the amusement park attraction, causing patrons to have to wait in the loading line at the amusement park for a long period of time, eliminating some of the benefits of having a virtual queue. Therefore, it is now recognized that it would be desirable to improve the virtual queue system during a capacity reduction event (e.g., a shutdown or partial closure of a park attraction). Summary of the invention

[0005] Certain embodiments corresponding in scope to the originally claimed subject matter are summarized below. These embodiments are not intended to limit the scope of the present disclosure, but rather, these embodiments are intended only to provide a brief summary of certain disclosed embodiments. In fact, the present disclosure may include a variety of forms that may be similar or different from the embodiments set forth below.

[0006] According to an embodiment, a 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 capacity reduction event from an amusement park attraction; determine a reduction in the capacity of the attraction associated with the capacity reduction event; identify each customer with a return time in a virtual queue of the attraction affected by the capacity reduction event based on the reduction in the capacity; remove customers with affected return times from the virtual queue; and generate a readaptation time slot for the customers removed from the virtual queue. The length of the readaptation time slot is based on the total number of affected return times of the customers removed from the virtual queue. The readaptation time slot is after all of the affected return times. The processor is also configured to execute instructions accessed from the memory to cause the virtual queue controller to: select two or more updated return times within the readaptation time slot for each of the customers removed from the virtual queue; provide a notification to each customer removed from the virtual queue requesting customer input to select a single updated return time from the two or more updated return times; and upon receiving a corresponding selection of the single updated return time, return each customer to the virtual queue.

[0007] According to an embodiment, a virtual queue system has: an amusement park attraction, which includes a capacity based on the number of available customer seats; and a virtual queue controller, which has a processor and a memory. The virtual queue controller is configured to: output a notification of reducing the number of customers admitted to the amusement park attraction from a virtual queue based at least in part on a capacity reduction event associated with a reduction in the number of available customer seats during the capacity reduction event; identify customers in the virtual queue with affected return times, wherein the affected return times are associated with return times for the amusement park attraction during the capacity reduction event; remove at least one customer with one of the affected return times from the virtual queue; generate a re-adaptation space in the virtual queue; provide a customer notification to a customer-related device associated with the at least one customer removed from the virtual queue, the customer notification indicating the removal from the virtual queue and indicating a plurality of new return times corresponding to the re-adaptation space; receive a selection notification of a selection of one of the plurality of new return times by the customer via the customer-related device; and when presented for entry at or after the new return time, verify the selected new return time. The virtual queue system also includes a sensor assembly positioned at an entrance to the amusement park attraction and configured to receive information from the patron-associated device and send the information from the patron-associated device to the virtual queue controller for verification.

[0008] According to an embodiment, a method includes the steps of: receiving an indication of a capacity reduction event; determining a reduction in customer throughput for an amusement park attraction during the capacity reduction event; determining a total number of virtual queue return times for customers in a virtual queue affected by the capacity reduction event based on the reduction in customer throughput; identifying each individual customer with an affected virtual queue return time; generating a readaptation time slot in the virtual queue, wherein a size of the readaptation time slot is based on the total number of virtual queue return times for customers in the virtual queue affected by the capacity reduction event; and providing a notification to each of the individual customers with an affected virtual queue return time indicating a plurality of available new return times in the readaptation time slot. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] These and other features, aspects, and advantages of the present disclosure will become better understood when the following detailed description is read with reference to the accompanying drawings, in which like characters refer to like parts throughout the drawings, and in which: Figure 1 is a schematic diagram of an embodiment of an amusement park including a virtual queue system according to aspects of the present disclosure; Figure 2 is a block diagram of an embodiment of a virtual queue system according to aspects of the present disclosure; Figure 3 is a flow chart of an embodiment of a virtual queue system technique during a capacity reduction event according to aspects of the present disclosure; Figure 4 is a diagram of an embodiment of a virtual queue system for an amusement park attraction according to aspects of the present disclosure; and Figure 5 is a flow chart of an embodiment of a method for determining the size of an available readaptation slot for a virtual queue system according to aspects of the present disclosure. DETAILED DESCRIPTION

[0010] One or more specific embodiments of the present disclosure will be described below. In order to provide a concise description of these embodiments, all features of the actual implementation may not be described in this specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, many implementation-specific decisions must be made to achieve the developer's specific goals that may vary from implementation to implementation, such as compliance with system-related constraints and business-related constraints. In addition, it should be appreciated that such development efforts may be complex and time consuming, but for ordinary technicians who benefit from this disclosure, such development efforts will be nothing more than routine tasks of design, fabrication, and manufacturing.

[0011] When introducing elements of various embodiments of the present disclosure, the articles "a," "an," and "the" are intended to mean that there are one or more of the elements. The terms "comprising," "including," and "having" are intended to be inclusive, and mean that there may be additional elements in addition to the listed elements. In addition, it should be understood that references to "one embodiment" or "an embodiment" of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features.

[0012] Theme parks or amusement park attractions have become increasingly popular, and various amusement park attractions have been created to provide passengers with unique motion and visual experiences. Customers entering various amusement park attractions can utilize a virtual queuing system that places customers in a virtual queue rather than a physical queue, which allows customers to enjoy other features of the amusement park while their position advances in the virtual queue. Some virtual queue systems provide customers with a return time indicating the time when the customer arrives at the amusement park attraction. The customer is directed to return to the amusement park attraction at the return time to wait in a physical queue or loading line of limited length before entering the amusement park attraction (e.g., riding a vehicle for an amusement park attraction). It should be understood that the loading line may also refer to a group of loading customers that may or may not be in a first-in-first-out arrangement and are assembled in a loading area. Therefore, as provided herein, the loading line may refer to a limited number of customers assembled in a loading area. In general, the loading area or a physical queue or loading line of limited length acts as a buffer for the amusement park attraction, and has enough customers so that there is a sufficient amount of customers to fill the amusement park attraction to full capacity at the loading time for the amusement park attraction. However, a loading line of limited length may also be short in length to reduce the amount of time a customer needs to spend in the loading line, allowing the customer more time to enjoy other aspects of the amusement park (e.g., dining, shopping, and other entertainment venues). The virtual queuing system may allow a predetermined number of customers to arrive at the attraction guide area so that the loading line may be short in length but also have a sufficient number of customers to fill the amusement park attraction to full capacity during each ride cycle or run of the attraction.

[0013] Unfortunately, reduced capacity events (e.g., amusement park attraction downtime and / or partial attraction closures) may prevent an amusement park attraction from operating at full capacity. During reduced capacity events, more customers may be entering the loading line (e.g., arriving from the virtual queue at or later than the customer's return time) than leaving the loading line (e.g., by riding the amusement park attraction). This may cause delays for customers present in the loading line. Having more customers enter the loading line than leaving the loading line causes the loading line to increase in length, which causes customers to wait in the loading line for an extended period of time after returning to the amusement park attraction at or after their return time. Having to wait in the loading line for an extended period of time may inconvenience and / or frustrate customers and eliminate some of the benefits of providing a virtual queue.

[0014] Moreover, extended periods of time in loading lines due to delays caused by capacity reduction events may have an additional adverse effect on overall park efficiency. Based on the customer's return time, the customer may anticipate exiting the ride at a specific time and make plans accordingly (e.g., lunch plans with family, queue for subsequent park attraction). However, extended periods of time in loading lines may delay the expected exit time for the customer, which may conflict with the customer's plans. As such, loading line delays may cause customers to be late or fail to show up within the virtual queue return time for subsequent park attractions in the park, thereby causing delays and / or reduced efficiency for subsequent park attractions. Moreover, loading line delays may cause customers to miss dining plans with family in order to remain in the queue during the capacity reduction event, which may further inconvenience and / or frustrate the customer.

[0015] With this in mind, a system and method for managing a virtual queue system during a reduced capacity event is provided herein that helps maintain an ideal length of loading lines to prevent or reduce adverse effects to both patrons and amusement parks associated with reduced capacity events.

[0016] Figure 11 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 and a wireless communication system 18, a system display 20, a customer-related device 22 (e.g., an active wearable customer device, a customer mobile device, etc.), and other components that coordinate the operation of corresponding virtual queues for amusement park attractions 24 in the amusement park 10. As explained above, customers 26 entering various amusement park attractions can utilize the virtual queue system 12 to enter virtual queues instead of physical queues for the amusement park attractions 24. In embodiments, customers 26 can use the customer-related device 22 to submit a virtual queue request to enter a virtual queue for the amusement park attraction 24. In other embodiments, customers 26 can enter the virtual queue request via kiosks 28 located around the amusement park 10. In embodiments, the kiosks 28 are located proximate to the amusement park attractions 24. In other embodiments, the kiosks 28 are located in general areas of the amusement park (e.g., dining areas 30).

[0017] The virtual queue request may be received by the virtual queue system 12 via the communication circuitry of the wireless communication system 18. Based on the virtual queue request, the virtual queue system 12 may enter the customer 26 into a virtual queue for the amusement park attraction 24 and provide the customer 26 with a return time or a dynamic position in the virtual queue that progresses as the customer enters the attraction 24. For example, the virtual queue system 12 may have available time slots at 1:45pm, 2:00pm, and 2:15pm for the amusement park attraction. Using the customer-related device 22, the customer 26 may send a virtual queue request for a 2:00 return time. In response, the virtual queue system 12 may enter the customer 26 into a virtual queue and provide the customer 26 with a notification to return to the amusement park attraction 24 at 2:00pm.

[0018] In an embodiment, customers may choose from a group of available return times at their discretion, with some customers selecting later return times based on their own schedule for the day. That is, the virtual queue controller may allow the first customer 36 to select a return time of 2:00 pm, the second customer 38 to select a return time of 2:05 pm, and the third customer 40 to select a return time of 2:10 pm. The available return times in each time slot may be preset at the beginning of the day and may be assigned to customers until they are no longer available.

[0019] In an embodiment, the virtual queue system 12 may incorporate other methods for determining a return time or queue position and providing a return time or queue position to the customer 26. In an embodiment, the customer returns to the attraction based on the position of the customer 26 in the virtual queue. In response to the virtual queue request, the virtual queue system 12 may place the customer 26 in the virtual queue and add the customer 26 to the available position relative to other customers in the virtual queue. For example, the first customer 36, the second customer 38, and the third customer 40 may send a corresponding first virtual queue request, a second virtual queue request, and a third virtual queue request. The first customer 36 may be assigned to the first position in the virtual queue, the second customer 38 may be assigned to the second position in the virtual queue, and the third customer 40 may be assigned to the third position in the virtual queue. At the time when the customer's position in the virtual queue is at the head of the virtual queue, the customer may return to the attraction. In an embodiment, the system 12 may provide an estimate of the expected time until the customer arrives at the head of the virtual queue, and the estimate may serve as the return time as provided herein.

[0020] The patron may return to the attraction 24 at or after their return time. In an embodiment, the sensor 16 is implemented as a wireless reader, such as an NFC reader, and is capable of communicating with the patron-associated device 22 to verify the patron's return time associated with the patron-associated device, and, based on the communication, may provide an indication of a valid return time based on a determination that the current time is at or after the indicated return time (e.g., a green light, a valid notification pushed to the patron-associated device 22). When the patron attempts to enter the attraction 24 at a time prior to the return time, an invalid return time indication may be provided (e.g., a red light, an invalid notification pushed to the patron-associated device 22). Although the sensor 16 may be configured to perform communication with the patron-associated device 22, the determination of a valid or invalid return time may be performed by a virtual queue controller 42 communicatively coupled to the sensor 16 as provided herein.

[0021] Figure 2is a block diagram of an embodiment of a virtual queue system 12. The virtual queue system 12 includes a virtual queue controller 42 configured to manage a virtual queue. The virtual queue controller 42 can be configured to communicate with other components of the virtual queue system 12 (including customer-related devices 22, amusement park operator devices 44, and amusement park attraction entrance systems 46 or some combination thereof). Each of the components of the virtual queue system 12 can include communication circuit systems 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 a communication circuit system 48a. The communication circuit system can include an antenna, a radio 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 via infrared (IR) wireless communication, satellite communication, broadcast radio, microwave radio, Bluetooth, Zigbee, Wifi, UHF, NFC, etc. through a wireless communication path. In one embodiment, communication circuitry 48a, 48b, 48c, and 48d includes a plurality of IR transceivers disposed in the environment of an amusement park attraction.

[0022] The virtual queue controller 42 may include a processor 50a and a memory 52a. The processor 50a may include one or more processing devices, and the memory 52a may include one or more tangible non-temporary machine-readable media. By way of example, such machine-readable media can include RAM, ROM, EPROM, EEPROM or optical disk storage, disk storage or other magnetic storage or can be used to carry 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) Any other medium. In an 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 can execute instructions to place customers in virtual queues based on virtual queue requests 58 from customer-related devices 22 and instructions stored on the memory 52a and output notifications 56 indicating return time to customer-related devices 22 via the communication circuit system 48a.

[0023] As explained above, the virtual queue controller 42 is configured to output a notification 56 for a customer to a corresponding customer-related device 22. For example, the notification 56 can guide the customer to return to the amusement park attraction at a specified return time. In another example, the notification 56 can include a delay message. In an embodiment, the virtual queue controller 42 is configured to identify customers in the virtual queue affected by the capacity reduction event for the amusement park attraction and output a delay message to customers with the affected virtual queue return time. The customer-related device 22 can be a personal customer device (e.g., a smart phone, a tablet, a laptop, etc.) or a park queue device provided to the customer (e.g., a smart wristband, an active wearable device, a portable communication device, etc.). The customer-related device 22 can have a processor 50b and a memory 52b. Moreover, the customer-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, a keypad, a keyboard, etc.). The customer-related device 22 can be configured to show the notification 56 on the display 62b. In an embodiment, the customer may respond to the notification 56 via the input device 64b. For example, the customer may confirm a return time via the input device 64b.

[0024] In an embodiment, the notification 56 may direct the customer to return to the amusement park attraction at his return time to enter the loading line. At the customer's corresponding return time, the customer may enter the loading line through an entry gate 66 of the amusement park attraction entry system. The entry gate 66 may be configured to detect that the customer has entered the loading line. The amusement park attraction entry system 46 may include a processor 50d and a memory 52d. The processor 52d may be configured to execute instructions to output a counter signal 68 indicating that the customer has entered the loading area to the virtual queue controller 42 via the communication circuit system 48d based at least in part on the detection of the customer and the instructions stored on the memory device. In an embodiment, the entry gate 66 is configured to output the counter signal 68 directly to the virtual queue controller 42. In an embodiment, the entry gate 66 includes a sensor assembly 70 (e.g., which includes the sensor 16) configured to detect the customer-related device 22. The virtual queue controller 42 may be configured to determine that the customer has entered the loading line based at least in part on the detection of the customer-related device 22 at the entry gate 66. In an embodiment, the entry gate 66 also verifies that the customer has a valid return time at the time of entering through the entry gate 66. The virtual queue system 12 may determine the number of patrons entering the loading line based on counter signals 68 received from the amusement park attraction entrance system 46 and / or the entry gate 66. In an embodiment, the amusement park attraction may include a turnstile configured to output a counter signal 68 to the amusement park attraction for each patron passing through the turnstile.

[0025] The amusement park attraction entrance system may also include a loading gate 72 configured to detect a customer exiting the loading line (e.g., entering the amusement park attraction). The amusement park attraction entrance system 46 and / or the loading gate 72 may be configured to output a second counter signal 74 indicating the detection of a customer exiting the loading line to the virtual queue controller 42. The virtual queue controller 42 may be configured to determine the total number of customers in the loading line based on the second counter signal 74. In an embodiment, the loading line area may include a sensor assembly 70 of the amusement park attraction entrance system 46. The sensor assembly 70 may have a plurality of sensors configured to detect each customer device in the loading line and output a total customer count signal 76 to the virtual queue controller 42. The virtual queue controller 42 may be configured to determine the total number of customers in the loading line based at least in part on the total customer count signal 76.

[0026] As provided herein, the virtual queue controller 42 is configured to manage the virtual queue of the attraction and remove one or more customers from the virtual queue in response to a capacity reduction event. Although the indication of the capacity reduction event can be based on a signal received from the attraction operator, the virtual queue controller 42 can also be configured to identify the capacity reduction event based on queue information. In an embodiment, the virtual queue controller 42is is configured to determine that the amusement park attraction is experiencing a potential capacity reduction event based at least in part on the total number of customers in the loading line exceeding a predetermined threshold or tolerance. In response to determining that the amusement park attraction is experiencing a potential 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, a smart phone, a tablet computer, a laptop, etc. The amusement park operator device 44 can have a processor 50c and a memory 52c. Moreover, 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, a keypad, a keyboard, etc.). The amusement park operator device 44 may be configured to show a capacity reduction notification 78 on the display 62c. The capacity reduction notification 78 may indicate to the operator that the amusement park attraction is experiencing a potential capacity reduction event. The capacity reduction notification 78 may include data for the operator to determine whether the amusement park attraction is experiencing a capacity reduction event and to determine the severity and / or duration of the capacity reduction event. The capacity reduction notification 78 may also include a prompt to enter an operator response 80 (e.g., confirmation or denial of the capacity reduction event) via the input device 64c. In an embodiment, in response to receiving confirmation of the capacity reduction event, the virtual queue controller 42 may send an instruction request 82 with a prompt requesting the operator to provide an operator input 84 related to the severity and / or duration of the capacity reduction event.

[0027] In an embodiment, the operator may manually output a capacity reduction event signal 86 to the virtual queue controller 42 via the operator interface 60c. For example, a ride vehicle of an amusement park attraction may require maintenance. The operator may direct the ride vehicle from the main track of the amusement park attraction to the maintenance track. In the absence of a ride vehicle on the main track, the amusement park attraction may not have enough ride vehicles to operate at full capacity. The operator may 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 capacity reduction, etc. In an embodiment, the operator may output a capacity reduction event signal 86 for other reasons including food spillage, weather delays, full system maintenance (e.g., closure), etc. In addition, the operator may manually output an end capacity reduction event signal 88 indicating that the amusement park attraction is operating at full capacity.

[0028] In an embodiment, the reduced capacity may be a function of the total number of available groups reduced for each ride cycle, whereby a ride cycle is the average time a ride runs (e.g., two minutes, five minutes). For example, if a single ride vehicle with six seats is inoperable, the reduced capacity may be six seats for each ride cycle. If the ride facility typically has 120 seats at full capacity across all ride vehicles, and operates an average of 10 times per hour (1,200 customers per hour), the loss of six seats is a 6% reduction in the capacity of the ride facility or a loss of 72 seats per hour. Similarly, if a single seat of a ride vehicle is inoperable due to food spillage, the reduced capacity may be a single seat for each ride cycle.

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

[0030] Figure 390 is a flow chart of an embodiment of a virtual queue system during a capacity reduction event (block 90). A capacity reduction event may include a partial closure of an amusement park attraction. For example, the partial closure may include closing at least one ride vehicle, ride facility seat, or some combination thereof of the amusement park attraction. During the partial closure, the amusement park attraction is configured to operate at a percentage greater than 0% and less than 100% of the full ride capacity. In an embodiment, the virtual controller is configured to output a notification of a reduction in the number of admitted customers from the virtual queue for the amusement park attraction based at least in part on the capacity reduction event. In addition, the capacity reduction event may also include a shutdown event for the amusement park attraction. The shutdown event may include a complete closure of the amusement park attraction such that during the shutdown event, the operation of the amusement park attraction ceases. Specifically, during the shutdown event, the amusement park is configured to operate at 0% of the full ride capacity.

[0031] Based on the percentage of reduction in ride capacity of the amusement park attraction during the reduced capacity event, the loading line may begin to increase in length because, due to the reduction in ride capacity of the amusement park attraction, the volume of patrons entering the loading line will likely exceed the volume of patrons exiting the loading line (e.g., entering the amusement park attraction). To avoid excessive wait times in the loading line, the virtual queue system may be configured to reduce the number of entries into the loading line admitting patrons into the amusement park attraction.

[0032] In an embodiment, to reduce the number of customers admitted into the loading line, the virtual queue controller is configured to identify queue return times that are affected by the capacity reduction event (block 92). For example, customers with return times during a downtime event will be affected by the capacity reduction event because it is assumed that the customers will experience additional time in the loading line during the downtime event. In another example, customers with return times immediately after a capacity reduction event may be affected by the capacity reduction event because the loading line may be longer than a predetermined length, causing the customers to have to wait in the loading line for a long period of time.

[0033] In embodiments where an estimated return time is provided to a patron as a notification or reminder (e.g., output to a patron-associated device 22) based on a particular position in a virtual queue that dynamically advances as a preceding patron enters an attraction, the virtual queue controller may be configured to identify an affected position in the virtual queue that corresponds to an estimated return time that is affected by the capacity reduction event. The virtual queue controller may be configured to identify patrons that are affected by the capacity reduction event based on the affected return time and / or the affected position in the virtual queue (and its associated affected estimated return time).

[0034] Following some capacity reduction events, the virtual queue controller may determine that the return time is not affected by the capacity reduction event. That is, the virtual queue controller may fail to identify any customers with return times affected by the capacity reduction event. In such a case, the virtual queue controller does not take further action in response to the capacity reduction event. However, in some cases, the virtual queue controller may determine that at least one return time is affected by the capacity reduction event (box 94). Instead of making the customers with affected return times in the virtual queue sit in the loading line for an extended period of time, the virtual queue controller may be configured to remove the affected return time or the customers with affected return time from the virtual queue (box 96). The virtual queue controller may be configured to store data indicating which customers or return times are removed from the virtual queue in a memory device.

[0035] In an embodiment, during a capacity reduction event, the virtual queue controller 42 may trigger the removal of certain affected customers from the virtual queue based on both a threshold of capacity loss (e.g., greater than 10%) and the presence of a threshold number of return times (e.g., more than 75 return times at a given time, more than 200 return times expiring during the course of an hour). Thus, a given capacity reduction event may result in all or only some of the customers being removed from the virtual queue within the time window associated with the capacity reduction event.

[0036] The virtual queue controller 42 can be configured to reach a predetermined relationship between the return time and the ride capacity for a specific time window. That is, the return time that begins to expire or become valid within the time window can be considered to be related to the time window. In one example, the virtual queue controller 42 can be configured to keep the number of return times that expire or become valid within a specific hour less than a specific percentage of the total capacity within the hour. In one example, the target percentage of the return time relative to the total capacity is 50% or less, 35% or less, 25% or less. When the reduction in capacity changes the percentage relationship, the virtual queue controller 4 is configured to remove customers from the virtual queue during the time window in question until the desired relationship is reestablished. For example, for a 50% target, the ride facility has 1,200 customers per hour, and the return time that expires within a specific hour is approximately 600 customers. However, if five ride vehicles are removed from operation, the capacity is reduced by a total of 30 seats for each ride cycle, and if the ride cycle occurs 10 times per hour, the total ride capacity is reduced by 300 seats per hour. In such an example, then, 600 return times within the hour will represent more than 50% of the capacity. Therefore, the virtual queue controller 42 can remove customers from the virtual queue during this time window until 50% of the relationship is reestablished. Moreover, if the system 12 has additional return times in the inventory along with an excessive number of expired return times during the capacity reduction event, these return times can be removed from the inventory to prevent additional customers from obtaining return times during the capacity reduction event. In the example provided, at least 100 customers are removed to reestablish the relationship. This group of 100 only represents a subgroup of a total of 600 expired return times. Current technology allows for a more granular adjustment of the incoming customer about the ride capacity and a more targeted change to the return time, which may only be for the affected customers and is invisible to the total population of customers. As discussed herein, removal may also be related to giving available readaptation later in the day.

[0037] In another example, if the reduced capacity is reduced by 300 seats per hour, but the number of outstanding return times during that hour is only 200, the relationship remains less than 50%, and the capacity reduction event may not trigger any removal of customers from the virtual queue. However, the number of new return times during that hour available for additional customers may be readjusted or removed from inventory to account for the capacity reduction event.

[0038] Removing customers from the virtual queue in response to a capacity reduction event may be implemented in a last-in, first-out manner. That is, customers with a recently assigned return time may be removed from the virtual queue before customers with a return time selected earlier in the day. In another example, removing customers from the virtual queue in response to a capacity reduction event may factor in group size, retaining larger groups while removing smaller groups, or vice versa. In another example, removing customers from the virtual queue in response to a capacity reduction event may factor in customer status (e.g., VIP status) and avoid removing customers with higher status. Customer status (e.g., VIP status) may be based at least in part on whether the customer is a fast pass purchaser, an annual pass holder, a resort customer, or a multi-park ticket holder. In another example, removing customers from the virtual queue in response to a capacity reduction event may factor in ride history. Customers who have ridden amusement park attractions earlier in the day may be removed. Moreover, customers who have never ridden amusement park attractions may be given priority (e.g., first-time riders) over other customers. Additionally, the virtual queue system may factor in whether the patron is in a virtual queue for another attraction, the type or brand of patron device 22 associated with the patron, the patron's location in the park (e.g., the patron's distance from an amusement park attraction), whether the patron is located in the park, or other factors when determining to remove a patron from a virtual queue in response to a reduced capacity event. In some embodiments, the virtual queue system may determine to remove a patron from a virtual queue in response to a reduced capacity event based on one or more of the factors set forth above.

[0039] The virtual queue controller is configured to generate and / or identify a later available time for a customer removed from the virtual queue and generate a readaptation time slot in the virtual queue based on the later available time for the customer removed from the virtual queue (box 98). The readaptation time slot or readaptation space is configured to provide a new return time or option for the customer removed from the virtual queue (box 100). The readaptation time slot can be configured to start immediately after the end of the capacity reduction event. For example, the first new return time can be scheduled for 2:00 pm after the capacity reduction event ends at 2:00 pm. In an embodiment, the readaptation time slot can start during the capacity reduction event. For example, during a long-term partial closure (e.g., operating at 80% of the ride capacity for multiple hours), the readaptation time slot can start twenty minutes after the start of the long-term partial closure. In an embodiment, the readaptation time slot may include an amount sufficient to accommodate the new return time of each customer removed from the virtual queue. The readaptation time slot may have a new return time at different times to allow customer flexibility in obtaining a new return time compatible with the customer's scheduling. For example, the return time slots may have new return times at 2:00 pm, 2:15 pm, 2:30 pm, and 2:45 pm.

[0040] The virtual queue controller may be configured to output a delay message to a customer-related device corresponding to the customer removed from the virtual queue. The delay message may include a message indicating that a capacity reduction event has occurred. The delay message may also indicate to the customer that the customer has been removed from the virtual queue. Moreover, the delay message may be configured to prompt the customer to select a reentry option (e.g., a new return time) for the virtual queue of the amusement park attraction. The reentry option may correspond to a new return time in the re-adaptation time slot. The customer may select one of the return option or the reentry option via an input device of the customer-related device (block 102). For example, the customer may have an active wearable device. The active wearable device may display a delay message on a display (e.g., a screen) of the active wearable device. The delay message may provide the customer with a reentry option including a new return time at 2:00 pm, 2:15 pm, or at 2:30 pm. The customer may use the input device to select a 2:00 pm return time and confirm the selection of the new return time at 2:00 pm. In another example, the new return time may be inconvenient for the customer. The delay message may also include a reentry option to veto the new return time. If the customer rejects the new return time, the virtual queue system may give the customer some form of electronic compensation (e.g., prioritized queue placement for another attraction) to remove the customer from the virtual queue (box 104). In addition, the customer-related device is configured to output the re-entry option (e.g., selection, confirmation, or rejection of the new return time) from the customer-related device to the virtual queue controller. In some embodiments, the readaptation time slot may not have enough new return time for each customer removed from the virtual queue. That is, the total number of customers removed from the virtual queue may be greater than the total number of new return times for customers removed from the virtual queue. Thus, some customers may not be readapted. The virtual queue system may give electronic compensation for customers who are not readapted.

[0041] The virtual queue controller is configured to provide a notification to the customer-associated device indicating a new return time in the re-accommodation space corresponding to the selected or confirmed new return time (block 106). The customer-associated device may provide the notification to the customer via a display of the customer-associated device. In an embodiment, the notification includes a verification (e.g., a code, a scannable indicia, a signal output, etc.) for the customer to present at the entrance to the amusement park attraction. Using the verification, the customer may be admitted to the loading line of the amusement park attraction at the new return time (block 108).

[0042] Figure 41 is a diagram of an embodiment of a virtual queue system for an amusement park attraction. Diagram 110 includes a capacity reduction event and readaptation time slots 112, 114, 116. In an embodiment, the readaptation time slot 112 is configured to begin after the capacity reduction event. In the illustrated embodiment, the readaptation time slot 112 begins immediately after the capacity reduction event. The readaptation time slot 112 includes a new return time within the readaptation time slot 112. For example, in the illustrated embodiment, the readaptation time slot 112 is configured to begin at 2:00pm and end at 3:00pm. Thus, the new return time can be at 2:00pm, 2:15pm, 2:30pm, and 2:45pm. The new return time can occur in any suitable increment based on the corresponding amusement park attraction.

[0043] In an embodiment, the duration of the re-adaptation time slot is based on the total number of affected virtual queue return times 114 removed from the virtual queue. That is, the re-adaptation time slot 112 can have a variable size based at least in part on the total number of customers removed from the virtual queue. For example, in the illustrated embodiment, the capacity reduction event may have been a partial attraction closure event 130 from 1:00 pm to 2:00 pm with a 30% reduction in ride throughput (e.g., one or more ride vehicles of an amusement park attraction are moved for maintenance). Thus, at least 30% of the customers with a return time from 1:00 pm to 2:00 pm are affected by the capacity reduction event and removed from the virtual queue. The remaining 70% of customers (e.g., unaffected customers 132) can retain their return time in the virtual queue during the capacity reduction event. In this example, the amusement park attraction can have a customer throughput of 600 customers per hour. Thus, the virtual queue controller can remove 180 customers from the virtual queue during the capacity reduction event. In an embodiment, the readaptation time slot 112 is configured to accommodate all customers removed from the virtual queue in the time frame immediately following the capacity reduction event. Thus, the readaptation time slot may begin at 2:00 pm and last until 2:18 pm (e.g., 18 minutes) to accommodate all 180 customers in the readaptation time slot 112. However, in an embodiment, the readaptation time slot 112 occurs within an extended time frame to minimize disruption to customers who have return times in the virtual queue immediately following the capacity reduction event. For example, in the illustrated embodiment, the readaptation time slot 112 begins at 2:00 pm and lasts until 3:00 pm.

[0044] In an embodiment, at least some customers with return time during re-adaptation time slot 112 can be removed from virtual queue 124 to generate enough space for re-adaptation time slot 112. These customers are provided with the re-entry option including the new return time in the second re-adaptation time slot 114. Moreover, at least some customers with return time during the second re-adaptation time slot 114 can also be removed from virtual queue and provided with the re-entry option including the new return time in the third re-adaptation time slot 116. In another embodiment, the virtual queue system is configured to remove all customers from virtual queue after capacity reduction event. Each customer removed from virtual queue can be provided with the re-entry option. However, before being removed from virtual queue, customers with earlier return time can be given priority in selecting the re-entry option. For example, customers with the original return time at 2:00pm will be given priority over customers with the original return time at 2:30pm. In an embodiment, the re-entry option provided to customers may be limited based on their corresponding return time before being removed from virtual queue.

[0045] In an embodiment, the virtual queue controller is configured to determine the amount of predicted absentees 122 for an amusement park attraction. For example, the virtual queue controller may determine that 9% of the patrons will fail to arrive at their respective return times (e.g., predicted absentees 122). Thus, only 91% of the patrons may be predicted to arrive at their respective return times (e.g., predicted attendees 126). The virtual queue controller may be configured to determine the amount of predicted absentees 122 based at least in part on historical data and current virtual queue data. When determining the amount of predicted absentees 122 for an amusement park attraction, the virtual queue controller may consider the time of day, date, weather patterns, special events, past queue data, current queue data, and other suitable factors.

[0046] In general, the virtual queue controller may be configured to place a number of customers in a virtual queue 124 corresponding to the full ride capacity 120 (e.g., 100% ride capacity) of an amusement park attraction. For example, when the customer throughput of the amusement park attraction is 600 customers per hour, the virtual queue controller may place 600 customers (e.g., 100% ride capacity) in a virtual queue with a return time between 2:00 pm and 3:00 pm. However, as described above, a portion of the customers will generally fail to arrive at their return time. Some amusement park attractions include a standby line separate from the loading line to fill seats for predicted absentees 122. However, in order to reduce the amount of customers affected by the capacity reduction event, the amusement park attraction may close the standby line and fill the seats for predicted absentees 122 with customers from the readaptation time slot. That is, based on the amount of predicted absentees 122, the virtual queue controller may place a certain amount of customers in the readaptation time slot that exceeds the customer throughput at the full ride capacity 120 (e.g., 100%).

[0047] For example, the customer throughput of an amusement park attraction at full capacity may be 600 customers per hour. The virtual queue controller may determine that the amount of the predicted absentees 122 between 2:00 pm and 3:00 pm is approximately 9% of the customers in the virtual queue. Based on the amount of the predicted absentees 122 and the customer throughput at full ride capacity, the virtual queue controller may place approximately 660 customers in the re-adaptation time slot 112 between 2:00 pm and 3:00 pm. The virtual ride controller may determine that, in fact, approximately 600 customers from the virtual queue should arrive at the amusement park attraction, taking into account the amount of the predicted absentees 122, so that the amusement park attraction operates at full capacity 120, wherein only customers from the virtual queue 124 are allowed to enter. This may temporarily increase the customer throughput from the virtual queue, so that the re-adaptation time slot 112 can accommodate customers faster. As such, it may be necessary to remove fewer customers with a return time immediately after a capacity reduction event from the virtual queue to accommodate the re-adaptation time slot 112.

[0048] In an embodiment, the virtual queue controller may incorporate a predetermined margin of error while managing the virtual queue during a capacity reduction event. The virtual queue controller may place a certain amount of customers in a re-adaptation time slot 112 that exceeds the customer throughput at full ride capacity 120 based on the predicted amount of absentees 122 and the predetermined margin of error for the predicted absentees 122. Thus, the virtual queue controller may place fewer excess customers than the predicted amount of absentees 122 in the virtual queue 124 to prevent potentially causing the length of the loading line to exceed the expected amount based on the predicted amount of absentees 122 when more customers arrive at their return time. For example, the virtual queue controller may determine that the predicted amount of absentees 122 is forty customers. The predetermined margin of error for the predicted absentees 122 may be 25%. Thus, the virtual queue controller may only allocate thirty customers, rather than forty customers that exceed the customer throughput at full ride capacity 120.

[0049] Furthermore, the virtual queue controller is configured to restrict new return times for customers 124 removed from the virtual queue during the capacity reduction event. Thus, the virtual queue controller may be configured to not accept virtual queue requests from new customers for return times during the readaptation time slots 112, 114, 116. The virtual queue controller may be configured to output a signal to a customer-related device indicating that the amusement park attraction is unavailable during the capacity reduction event and during the readaptation time slot 112. Preventing new customers from queuing during the capacity reduction event and the readaptation time slot 112 can help maintain the length of the loading line during the capacity reduction event and the readaptation time slot 112 and maintain a consistent throughput for the amusement park attraction.

[0050] Figure 5 1 is a flow chart of an embodiment of a method for determining the size of a re-adaptation time slot for a virtual queue system. At the start of the method, an amusement park attraction may experience a capacity reduction event. The method includes the step of receiving an indication of a capacity reduction event (block 140). The method also includes the step of determining a reduction in customer throughput for the amusement park attraction during the capacity reduction event (block 142). An operator may output the severity of the capacity reduction event via a user interface so that a virtual queue controller may determine a reduction in customer throughput for the amusement park attraction during the capacity reduction event.

[0051] The method may include the step of determining a total number of virtual queue return times for customers in a virtual queue affected by a capacity reduction event based on a reduction in customer throughput (block 144). The method may also include determining a total number of affected virtual queue return times based on a duration of the capacity reduction event. The method may also include the step of identifying each individual customer having an affected virtual queue return time (block 146). The memory device may store individual customer virtual queue data. The virtual queue controller may analyze the virtual queue data to determine which customers have been affected by the virtual queue return time.

[0052] The method may also include the step of generating a readaptation time slot in the virtual queue (block 148). The size of the readaptation time slot may be based on the total number of virtual queue return times for customers in the virtual queue affected by the capacity reduction event (block 148). The readaptation time slot may include a size large enough to accommodate each customer in the virtual queue affected by the capacity reduction event. In addition, the method may include the step of providing a notification indicating a potential new return time in the readaptation time slot to each of the individual customers having an affected virtual queue return time (block 150).

[0053] While only certain features of the disclosure have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It will, therefore, be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the disclosure.

[0054] The technology presented and claimed herein is cited and applied to substantial objects and specific examples of a practical nature that arguably improve the art and are therefore not abstract, intangible, or purely theoretical. Moreover, if any claim appended at the end of this specification contains one or more elements designated as "a means for [performing] ... [function]" or "a step for [performing] ... [function]," it is intended that such elements will be interpreted in accordance with 35 U.S.C. 112(f). However, for any claim containing elements designated in any other manner, it is intended that such elements will not be interpreted in accordance with 35 U.S.C. 112(f).

Claims

1. A virtual queue system, comprising: Transportation to scenic spots; Take a vehicle controller, which is configured to: receiving maintenance signals; and driving operation of the ride vehicle from a first track to a maintenance track based on the maintenance signal; and A virtual queue controller comprising a processor and a memory, wherein the processor is configured to execute instructions accessed from the memory to cause the virtual queue controller to: receiving a signal indicative of the maintenance signal; generating an indication of a capacity reduction event for the attraction based on the maintenance signal; determining a percentage reduction in capacity of the attraction in response to the indication of the capacity reduction event, wherein the capacity reduction event comprises removing capacity of the ride vehicle from total capacity; identifying, based on the capacity reduction percentage, affected patron profiles having return times in a virtual queue for the attraction affected by the capacity reduction event; removing the affected patron profile from the virtual queue to maintain a predetermined relationship between an attraction return time and a capacity of the attraction, wherein the capacity of the attraction is updated in response to the capacity reduction percentage; generating a readaptation time slot for the affected customer profile removed from the virtual queue, wherein the virtual queue controller incrementally adjusts the length of the readaptation time slot as a customer is removed from the virtual queue, and wherein the readaptation time slot is after all affected return times for the affected customer profile; selecting two or more updated return times within the readaptation time slot for each of the affected customer profiles removed from the virtual queue; generating and sending to a customer device a notification of each affected customer profile removed from the virtual queue, wherein the notification causes display of a user interface on the customer device requesting customer input to select a single updated return time from the two or more updated return times; and Upon receiving a corresponding selection of a return time for the single update, each affected customer profile is returned to the virtual queue. 2 . The virtual platoon system of claim 1 , wherein the maintenance signal comprises a duration of maintenance of the vehicle.

3. The virtual queue system according to claim 2, wherein: The indication of the capacity reduction event is based on the duration.

4. The virtual queue system according to claim 3, wherein: The readaptation time slot is after an estimated end of the capacity reduction event based on the duration.

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

6. The virtual queue system according to claim 1, wherein: The amount of return time affected is based on the number of seats in the ride vehicle.

7. The virtual queue system according to claim 1, wherein: The virtual queue controller includes communication circuitry configured to communicate the notification to a respective patron-associated device of each patron removed from the virtual queue.

8. The virtual queue system according to claim 1, wherein: The readaptation time slot occurs simultaneously with the capacity reduction event.

9. The virtual queue system according to claim 1, wherein: The virtual queue controller is configured to estimate an amount of absentee return time for the attraction based at least in part on historical data and current virtual queue data, wherein at least a portion of the readaptation time slots include excess capacity return time configured to fill the predicted absentee return time after the capacity reduction event ends.

10. The virtual queue system according to claim 1, wherein: The virtual queue controller is configured to identify the affected return times by determining a capacity reduction for the attraction associated with the capacity reduction event and determining that a relationship between existing return times in a time window and the capacity reduction is outside a desired tolerance.

Images