Queue management system and method

Abstract

To provide a queue management system.SOLUTION: A queue management system in accordance with present embodiments includes a data server system including a processor and a memory. The queue management system includes an interface system of the data server system configured to receive a reservation request including an indication of a general time period of arrival of a park visitor at an area. Additionally, the queue management system includes a reservation right allotment system of the data server system configured to correlate a reservation slot for accessing an attraction with identification information of the park visitor. Further, the queue management system includes a detection system of the data server system configured to determine when a portable identification feature associated with the identification information has arrived at the area, and a reservation assignment system of the data server system configured to establish a reservation for accessing the attraction at a specific time window.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure generally relates to the field of amusement parks. More specifically, embodiments of the present disclosure relate to methods and devices utilized to control wait times at attractions by providing reservations.

Background Art

[0002] Since the early 20th century, amusement parks have substantially grown in popularity. To address this increased demand, amusement parks have expanded at a furious pace by adding attractions and space. The addition of attractions (e.g., rides, restaurants, shops, and shows) generally provides additional capacity to handle the large number of visitors (guests) to the amusement park. On the other hand, additional attractions also typically provide an incentive for potential visitors to visit the amusement park. Thus, while a particular amusement park may increase its capacity, the additional capacity does not necessarily reduce the wait times for attractions, as the number of visitors often correspondingly increases as well. Also, for operational efficiency reasons, it is often desirable to limit the availability of attractions when the number of visitors is low. For these reasons, waiting in line for attractions is a year-round problem for amusement parks.

[0003] While visitors have desired more spectacular, superior, and more innovative attractions, they also seek and expect a generally pleasing experience. Providing a generally pleasing experience for amusement park visitors involves addressing specific issues related to waiting in line for attractions. In fact, it is now recognized that unpleasant experiences related to waiting in line can deter visitors from returning to certain amusement parks. Visitors may also refrain from accessing amusement park services (such as concession stands) due to the time spent waiting in line. Indeed, in the past, visitors were forced to wait in line for hours to experience some of the more popular attractions at an amusement park. In addition, it is now recognized that the park's capacity does not always match the guest utilization rate of that capacity, as individual visitors may prefer certain attractions to others. Therefore, it is now recognized that it is desirable to improve the queuing systems and methods at amusement parks.

[0004] These and other features, aspects, and advantages of this disclosure will be better understood when the following detailed description is read in conjunction with the accompanying drawings, and similar reference numerals throughout the drawings represent similar parts. [Brief explanation of the drawing]

[0005] [Figure 1] This is a schematic diagram of an amusement park that includes a reservation system using this technique. [Figure 2] This is a process diagram of the method using this technique. [Figure 3] This is a process diagram of the method using this technique. [Figure 4A] This diagram illustrates the process of the method using this technique. [Figure 4B] Figure 4A, along with a process diagram of the method using this technique, is shown. [Figure 5]This is a process diagram illustrating a method for streamlining visitor scheduling for multiple reservations at attractions using this technique. [Figure 6] This is a process diagram illustrating the method for adjusting visitor schedules using this technique. [Modes for carrying out the invention]

[0006] This disclosure broadly relates to a method and system for controlling wait times in amusement park attraction queues by dynamically managing reservations for amusement park attractions, including shows, restaurants, rides, shops, and others. This embodiment includes a system having an electronic data server and applications capable of communicating and monitoring metrics or characteristics related to reservations for attractions within an amusement park and controlling queue flow characteristics. The system may include a verification system, a tracking system, an execution system, mobile devices, and backend computers and devices. The system is configured to receive one or more reservation requests at a time and to allocate a general or specific time frame for the reservation based on information provided by the user and / or other data (e.g., data relating to the operation of the associated attraction or data relating to the detected locations of the guest holding the reservation). Furthermore, this embodiment is configured to allow access to or modification of one or more existing reservations and / or adjustment of queuing characteristics (e.g., access ratio) based on changes to reservation requests, changes to visitor scheduling, guest location, data on one or more attractions associated with the reservation, eligibility levels (e.g., based on tiered payment options for different access levels), and other factors. With respect to eligibility levels, a tiered approach may be available for pricing on various mechanisms or components, including micropayments for certain specific services or tasks. For example, visitors may be offered micropayments to receive periodic updates on shorter queues in certain areas of the park.

[0007] The system allows visitors to enter virtual queues for specific one or more attractions using mobile or wireless technology, and while waiting, they can experience other attractions in other areas of the amusement park or relax away from the park. In practice, this embodiment includes a system configured to communicate with one or more attractions associated with reservation requests or existing reservations to dynamically adjust and optimize the visitor's waiting experience in real time, and to communicate updates to the visitor (e.g., via mobile or wireless technology). This embodiment may facilitate communication with visitors via portable communication devices such as cellular telephones, pagers, and other wireless devices. Such devices are referred to as mobile devices. Communication between the system and visitors as referred to herein includes email, text, video, web-based, and voice communication from the system to mobile devices, etc. The location of visitors within the amusement park may also be obtained by monitoring such mobile devices or other means (e.g., facial recognition systems, ticket scanning, etc.). In some embodiments, communication with visitors may be achieved via publicly accessible displays. For example, kiosks with communication mechanisms (e.g., computers capable of accessing a network) may be placed throughout the amusement park.

[0008] According to this technique, the reservation system is configured to provide an interface for users or visitors to make reservations for access to one or more attractions in the amusement park during their visit. Reservations can be made for groups of visitors or for individual visitors before arrival at the amusement park or while inside the park. In practice, the functionality of the system described herein will include communication with individual visitors or groups. Making reservations for multiple visitors as a group can be facilitated by enabling the association of all corresponding tickets with the tickets of individual visitors. These reservations can be made using a laptop computer, desktop computer, mobile device, or other access device before or during a visitor's amusement park visit. Such reservations will be made via online resources, direct access to the reservation system portal, a telephone system, or otherwise.

[0009] According to this disclosure, tickets may include various types or combinations of identification documents that will be used to verify access rights to attractions (e.g., a theme park). The tickets (e.g., paper tickets, biometrics, or electronic tickets) will be used to verify current or future access rights. When tickets are not purchased together, this embodiment can associate them as a group. This allows any member of the group of visitors to make a reservation for that group. For example, if a group of visitors arrives at a theme park and each purchases a ticket separately, one of the visitors in the group can use this embodiment to make one or more reservations for the group. This embodiment can associate a reservation for a group with a single ticket, which becomes the “master ticket.” When a reservation is made, the master ticket associated with the reservation must be verified first, followed by the tickets of the remaining group members. Several techniques and systems may be available for associating tickets with a master ticket. This may involve scanning the tickets to verify identification information, authenticity, and reservation information. During the verification process, each ticket is associated with the remaining reservations within the system. Therefore, subsequent reservations do not need to have the master ticket verified before the reservation becomes available.

[0010] Furthermore, reservations can be made without visitors specifically specifying a time frame for the reservation before they visit the amusement park. For example, a reservation may be established for a particular date without specifying an hourly reservation time range. However, in some embodiments, an initial time slot is determined based on the visitor's expected arrival time at the amusement park. For example, this expected arrival time may be specified as AM or PM. In such embodiments, upon the visitor's arrival, a specific time frame (e.g., 3:00 PM to 3:15 PM) may be allocated for the reservation depending on the visitor's arrival time and the availability of reservation time slots for the associated attraction. It should be noted that this embodiment can be used to make multiple reservations for one or more attractions. This embodiment can further facilitate communication between the reservation system and visitors, provide dynamic updates of reservation times, and provide crowd control by encouraging visitors to visit specific areas of the amusement park. This embodiment can also efficiently accommodate changes in visitors' schedules by facilitating reservation transactions within the reservation system. For example, if a visitor wants to change their assigned reservation, they can use the reservation system to make a new reservation for a more convenient time, and the original reservation will be returned to the available inventory or reassigned if applicable.

[0011] Referring now to Figure 1, a system for managing queues for theme park attractions is collectively indicated by reference numeral 100. The queue management system 100 includes a data server system 102, a visitor entry system 104 (e.g., a tracking system or access authorization system), an enforcement system 106, a data reader 108, portable identification features (PIF) 110, a tracking system 112, a backend computer system 114, and at least one attraction 116. Some specific components of system 100 may be extensions or modules of the data server system 102, while other components may be separate mechanisms communicating with the data server system 102. In practice, the data server system 102 may include one or more computers having one or more processors 118 and memory 120 (e.g., hard drives, or simply other tangible machine-readable media that are non-transient in the sense that they are not signals). In practice, in one embodiment, the data server system 102 includes one or more redundant servers to ensure reliability and enable maintenance. Memory (or multiple memories) 120 may store code or instructions that, when executed by the processor (or multiple processors) 118, cause the reservation system 100 to perform specific functions according to this embodiment. In practice, some specific component systems of system 100 (e.g., the visitor entry system 104) may include code stored in memory 120 that can be activated by the processor 118. Note that this disclosure may refer to the components of system 100 or all components of system 100 as a group, "reservation system 100" or "system 100". Thus, actions indicated as being performed by the reservation system 100 or system 100 may include actions performed by a subset of system 100.For example, suppose the data server system 102 works in conjunction with the data reader 108 of the visitor entry system 104 to determine whether a particular visitor has checked into the amusement park (for example, by passing through the entrance or main gate). This action may also be said to have been performed by the reservation system 100.

[0012] In the illustrated embodiment, the attraction 116 includes a monitoring and / or data maintenance system 122 used to monitor the operation of the associated attraction 116 and / or to provide information related to its operation. These monitoring and / or data maintenance systems 122 are referred to as the attraction system 122 and may include one or more computers, control systems, and monitoring mechanisms (e.g., sensors and cameras). In some embodiments, the attraction system 122 basically includes ports or workstations for inputting information into the data server system 102, for retrieving data from the data server system 102, or for otherwise communicating with the data server system 102. For example, the attraction system 122 may allow amusement park employees to input data related to the operation of the associated attraction (e.g., wait times, attraction capacity, downtime). In other embodiments, the attraction system 122 is a separate system configured to operate independently and to communicate with the data server system 102. For example, the attraction system 122 may log all activities associated with reservations for the corresponding attraction 116 (e.g., downtime, statistics on requested and fulfilled reservations, availability, and the amount of traffic passing through the attraction) to facilitate data analysis by the data server system 102 and / or the backend computer system 114. In one embodiment, system 100 is expandable to store and process large amounts of data. The data obtained from the attraction system 122 is submitted to system 100 for data analysis, and the results are used to support queue characteristics and reservation control, as detailed below.

[0013] PIF110 may include tickets. Specifically, for example, PIF110 may include printed tickets, biometric authentication, and / or mobile devices. As an example, PIF110 may include printed material strips, facial recognition, fingerprint scanning, mobile phones, microchips (e.g., memory) or circuit configurations embedded in cards or bracelets, pagers, or wireless devices provided by or owned by the amusement park. In practice, a specific mobile phone owned by or obtained by the amusement park may be associated with a visitor pass. The term visitor pass (guest pass) generally refers to a visitor's right to access certain attractions or parts of the amusement park. For example, a visitor pass does not necessarily have to be a tangible item. A visitor can purchase a visitor pass, which is then associated with the visitor's identification information (e.g., password, serial number, name, or numeric code) on System 100 to verify the visitor's identity and confirm their rights. This association may be performed by a portable identification feature assignment system of the data server system 102. Once a visitor pass is associated with a PIF 110 assigned to a particular visitor, the PIF 110 can then be used to verify the visitor's rights via system 100. Relying on this information, amusement park employees or the system will grant or deny the visitor the right to access or make reservations for certain attractions 116. In some embodiments, the PIF 110 has wireless detection capabilities and provides access to the identification information associated with the PIF 110. For example, a tracking system 112 may employ a device monitor 124 that tracks the PIF 110 within the amusement park and identifies the location of a particular visitor within a certain spatial range. System 100 further detects whether a visitor has arrived in the amusement park by monitoring the visitor entry system 104 and whether a certain type of PIF 110 associated with the visitor has been detected.This may include scanning tickets using the tracking system 112, scanning barcodes from the screen of a portable device, pinging the portable device, etc. Detection of a visitor's entry into the amusement park may be confirmed at the time of purchase of the visitor pass and association with the PIF 110, for example, by scanning the ticket or by associating the identification information of a mobile device with the visitor pass.

[0014] As suggested above, visitors (or their agents) can use this embodiment to obtain reservations for one or more attractions in order to avoid or limit waiting times in attraction queues, such as queue 126 for a particular ride 128. System 100 is designed to handle multiple reservations being made, modified, or accessed at once with sufficient processing power to ensure that the addition of capacity does not affect the operating speed and does not slow down the system. Reservations made through System 100 are obtained by visitors remotely or from within the amusement park via an automated telephone system 142, an internet system 144 (e.g., a website or mobile site), a text messaging system 146, or a point-of-sale (POS) device system 148. The automated telephone system 142 is accessible from telephone 150 and includes the network of telephone 150. The Internet system 144 communicates with the Internet 152 and, in some embodiments, includes two separate websites, the first website which responds to visitors' wishes to make reservations, and the second website which provides access to service personnel who perform operational management tasks in addition to making and revising reservations. The text messaging system 146 communicates with the network of wireless devices 154 (e.g., mobile phones). The POS device system 148 includes and / or communicates with the POS device 156.

[0015] The system 100 depicted in Figure 1 is capable of communicating with a wide variety of wireless or mobile devices owned by visitors or supplied by the amusement park. In practice, the PIF 110 includes a communication mechanism that allows all visitors with reservations to receive messages and updates from the system 100. However, mobile devices may be used to communicate with the system 100 without being used as the PIF 100. As an example of system communication, a text message may be sent from the text messaging system 146 to a mobile device acting as the PIF 110 and assigned to a visitor, indicating that a particular reservation time has been postponed due to a technical problem related to a particular attraction. The text messaging system 146 is capable of sending at least 20,000 automated text messages per minute, including postponement notices, informational notices, and advertisements. In addition, various other components of the system 100 are capable of communicating wirelessly with mobile devices or other wireless system components. For example, the data reader 108 and POS device 156, and others, can be wireless devices capable of communicating wirelessly with the data server system 102. The term "mobile device" refers to items that visitors can easily carry with them, such as mobile phones and pagers.

[0016] If a visitor requests a reservation right from off-site as part of the reservation process, the visitor is prompted by system 100 (e.g., an interface module of data server system 102) to provide system 100 with an estimated time of arrival (e.g., AM or PM) to an area such as the amusement park or a specific attraction 116 (e.g., a differentiated area of ​​the amusement park). Such requests are received through an interface system of data server system 102, which is capable of receiving communications and input data from visitors (including current and potential amusement park sponsors). Such communications may be provided via one or more of the following: an automated telephone system 142, an internet system 144, a text messaging system 146, or a POS device system 148. A specific reservation is not established until the visitor actually arrives. Rather, the reservation allotment system of data server system 102 reserves reservation slots based on the estimated time of arrival and correlates the reservation slots with the visitor's identification information. Providing an estimated arrival time is required to establish booking rights within the associated time period of the visit.

[0017] A detection system (e.g., tracking system 112, visitor entry system 104, and / or data reader 108) determines whether the portable identification device has arrived in a designated area (e.g., an amusement park). If the visitor fails to arrive within the expected time period (e.g., during the morning), system 100 contacts the visitor and, based on feedback from the visitor and / or other criteria, reschedules or cancels the associated reservation. Similarly, once it is confirmed that the visitor has entered the amusement park, the reservation assignment system of data server system 102 sets a specific reservation time, and the visitor is informed of that specific reservation time (e.g., a 15-minute window to arrive at attraction 116). For example, visitors who have existing reservation rights or have requested a reservation will receive a text message or recorded voice message from the system via one or more of the automated telephone system 142, the internet system 144, the text messaging system 146, or the POS device system 148. In a particular example, when checking in at a kiosk including a POS device 156, visitors will be notified via the POS device system 148 that a specific time for their reservation has been established, through a message and the time printed on a receipt created by the POS device 156. Similarly, communications from system 100 may also be provided to visitors via the automated telephone system 142, the internet system 144, or the text messaging system 146, by voice messages, text messages, or email sent to their mobile devices and / or PIF 110 assigned to them (e.g., the visitor's personal communication device or a device provided by the amusement park). The specific time is narrower than the approximate time and is typically set within the approximate time, but may also be later.

[0018] In addition, the system 100 in the illustrated embodiment facilitates communication from visitors to the system 100. For example, a user can communicate to the system 100, via a mobile device including a PIF 110, that a reservation is no longer desired, or that there is likely to be a delay in the visitor's arrival at the amusement park or individual attraction 116. This type of information will be used by the system 100 to manage the reservations of that visitor and other visitors. Such information will also be used by the system 100 to facilitate queue management. For example, cancellations can be used to adjust the ratio of waiting queues, express queues, VIP queues, single-ride queues, and reservation queues, or the number of visitors allowed to access via reservation entries. In practice, the system 100 will communicate such data to the attraction control system (e.g., attraction system 122) or to amusement park employees responsible for queue management. This would include providing an access management system or attraction system 122 for the data server system 102 that has the ability to control an adjustable ratio variable that adjusts certain queuing characteristics (e.g., the number of queue entries) relative to reservation entries so that a desired wait time is maintained, and the ability to provide information on nearby attractions with low wait times (e.g., wait times lower than the reservation queue or the nearest attraction with the lowest wait time).

[0019] Communication from visitors to system 100 may include periodic updates regarding the location of each PIF110 or updates entered by visitors through each data entry component of PIF110. For example, PIF110 may include a Global Positioning System (GPS), a Radio Frequency Identification (RFID) tag, or other detectable mechanism that can be used to determine the location of PIF110. Specifically, for example, if PIF110 is detected by a data reader 108 or scanned as part of a purchase detected by a device monitor 124 located within the amusement park, such information can be used by system 100 to determine the approximate location of the visitor to whom PIF110 is associated. Visitors may also submit requests or updates via a data entry mechanism (e.g., a keyboard or other interface of PIF110). For example, each PIF110 may include a keyboard or basic input that allows visitors to respond with affirmative or negative answers to questions posed by the system 100, such as questions about whether the visitor intends to show up for a pending reservation, and so on. Other mobile devices not used as PIF110 may also be used to communicate with the system 100.

[0020] Communication between System 100 and visitors may include other types of information or data, such as information relating to the flow of people throughout the amusement park, in addition to communication regarding reservations. For example, System 100 may collect data on the flow of people using location data from PIF 110 or other sources. This data may then be used by System 100 to encourage visitor distribution throughout the amusement park and thereby reduce crowding. For example, electronic coupons for nearby attractions, which may be restricted to certain visitors by identification information, may be issued by System 100 via PIF 110, or notices indicating that wait times will be shorter for certain attractions may be distributed. System 100 has the capability to push information (e.g., coupons, advertisements, and wait times) to visitors via a web portal or the like. Specifically, for example, system 100 may be configured to deliver text messages to all park supporters with PIF110 that have specific identification information, allowing these supporters to receive discounts at shops or restaurants. System 100 may also be configured to track the use of these discounts so that it can track the time and location of use and use this information to control crowds (by issuing additional notifications based on purchase location, purchased items, etc.). In addition, system 100 may be configured to automatically adjust reservations based on location and availability. For example, a reservation may be adjusted because the supporter is located too far from the attraction (judged by the time of item purchase) to arrive on time for the reservation, or a visitor's position in line may be adjusted because the visitor is delayed due to slow service at a restaurant.

[0021] Similar to the other types of information discussed above, System 100 can communicate crowd flow information between attractions 116 and dynamically adjust queuing characteristics (e.g., the ratio of entry between reservations and queues) toward optimizing visitor wait times for attractions. For example, the adjustment may be based on the ratio of visitors allowed to enter the queued souvenir shop 160 from the queue 162 (e.g., the area where visitors queue to enter attractions without reservations) to visitors allowed to enter the souvenir shop 160 from the reservation 164 (the area where visitors queue to enter attractions based on reservations), and the availability of remaining reservations for entry to the souvenir shop 160 and access to attractions throughout the amusement park. It should be noted that visitors entering the reservation line 164 have their right to enter the reservation line or queue 164 confirmed by accessing a PIF 110 associated with data reader 108, and their access to enter the souvenir shop 160 is confirmed by accessing a different data reader PIF 110 associated with data reader 108. Thus, data reader 108 is used as an entry access confirmation mechanism. This double confirmation can be used to monitor queue waiting times. Similarly, data reader 108 can be used as an access confirmation mechanism by confirming that a visitor has entered an attraction (for example, boarded an attraction vehicle).

[0022] System 100 can also facilitate visitor-to-visitor communication and system-directed communication based on common characteristics of some specific visitors. Specifically, in this embodiment, demographic data may be collected during the registration process or through an opt-in process. The registration process may include data entry requirements that facilitate the acquisition of demographic data or some use of System 100 by the visitor. For example, registration may include the use of a mobile phone by the visitor in cooperation with System 100, and the demographic data obtained may include the area code of the phone number associated with the mobile phone. Direct visitor-to-visitor communication may be established via the system between the PIFs 110 assigned to the visitors if the PIFs 110 have communication capabilities, or direct visitor-to-visitor communication may be established between communication devices provided by the visitors or the park and known to System 100. Similarly, such communication may be established through enabling access to social media, and again, PIFs 110 or known communication devices can be employed. Thus, visitors having common characteristics based on the registration data or selected options of the visitors can provide notifications to each other. For example, visitors from the same geographical area can inform each other of activities that they may commonly be interested in. Similarly, System 100 can provide information on activities that are likely to be of common interest based on demographic data. System 100 can, among other things, especially smooth the process of posting status updates, notifying visitors within a specific group of activities related to that group, or providing notifications of some specific situations within the park.

[0023] In one embodiment of the present disclosure, a PIF110 (e.g., an RFID transponder) is provided to each visitor or group upon their entry into the amusement park. This may include the amusement park renting, lending, or simply selling the PIF110 to visitors. Each PIF110 is programmed to uniquely identify each visitor or group and is assigned within the system 100. In some embodiments, providing each visitor with a PIF110 involves instructing the system to recognize and / or communicate with a device owned by the visitor, so that the device owned by the visitor is adopted as a PIF110 and activated as a PIF100 by the system 100. For example, the system 100 may be used to download an application to the visitor's mobile phone so that the system 100 associates the visitor's mobile phone with the amusement park ticket and the visitor (or group). In another embodiment, system 100 is programmed to detect the PIF 110 and recognize its association with a valid visitor pass. Also, as discussed above, different types of PIF 110 include paper or plastic tickets or bracelets with integrated detection devices. For example, a bracelet may include an integral circuitry that stores a unique identifier in memory and / or an integral circuitry that provides communication capabilities (e.g., the ability to communicate with a Global Positioning Unit or other location detection system). For example, an automatic identification and data acquisition (AIDC) device such as an RFID tag may be used. Other mechanisms for the PIF 110 that can be used according to this embodiment include barcodes, magnetic strips, PIN numbers, mobile phone identifiers, hotel room keys, credit cards, combinations thereof, and others. Any identification component of the PIF 110 or a combination of such devices may have a mutual reader that communicates with a data reader 108 or other visitor identifiers (e.g., a POS device 156) to track the visitor's movements and / or activities within and around the amusement park. This makes it possible to track the flow of people in crowds.In some embodiments, the PIF110 may also include a handheld electronic device with a display screen that can communicate about the flow of people in order to facilitate the movement of visitors to specific areas within the park.

[0024] In one embodiment, system 100 has the ability to control access and manage reservations for attractions 116 by facilitating communication between a data server system 102 acting as a central queuing control system and a visitor entry system 104. In practice, the coordination between the data server system 102 and the visitor entry system 104 facilitates the identification of visitors with reservations arriving at and entering the amusement park, and thus assists in reservation management. In practice, reservations may be modified or canceled depending on an algorithm that takes into account the time of arrival at the amusement park. Communication of visitor arrival and / or entry may be achieved by polling the visitor entry system 104 with the data server system 102 at regular intervals (e.g., every 30 seconds or every 60 seconds) or at specific times, or by sending associated PIF 110 identification data from the visitor entry system 104 to the data server system 102 each time a visitor enters the amusement park via the visitor entry system 104. For example, a data reader 108 associated with a particular attraction 116 may communicate with a data server system 102 or directly with a visitor entry system 104 to confirm that the visitor has a valid park admission ticket. Specifically, for example, a visitor may supply their assigned PIF 110 to a data reader 108 for a particular attraction 116. The data reader 108 then retrieves information from the PIF 110 and communicates with other system components to confirm that the PIF 110 is associated with a valid reservation and that the PIF 110 is known to be properly entered into the amusement park. This may include confirming that the PIF 110 (e.g., a mobile phone) is identified via the visitor entry system 104 when entering the amusement park (e.g., scanned upon entry) and that the PIF 110 is associated with a reservation for a particular attraction 116 or any attraction 116.In some embodiments, visitors must use the PIF 110 to communicate with a first data reader 166 to enter queue 164, and then use the PIF 110 to communicate with a second data reader 168 to enter attraction 116. This facilitates monitoring of queue characteristics.

[0025] In one embodiment, System 100 enables individuals or groups to make reservations, access attractions within a time range, modify reservations, delay reservations (e.g., delay reservations in 5-minute intervals), transfer reservations from one PIF 110 to another (e.g., from one group member to another), cancel reservations, and provide reservation details and updates (e.g., in real time). As suggested above, System 100 includes numerous access points or interface points capable of interfaceping with a commercial management system for the amusement park (e.g., a module of Data Server System 102 or a separate system that communicates with or can be accessed through Data Server System 102). In practice, users can access or interface with System 100 remotely or from the amusement park property via an automated telephone system 142, an internet system 144, a text messaging system 146, or a POS device system 148. In some embodiments, accessing and manipulating reservations is achieved using a PIF 110 used to communicate with the data server system 102. In practice, a visitor may request to postpone (e.g., by 30 minutes) or cancel a reservation because they took longer than expected to eat, by sending a text message to the data server system 102 from the PIF 110 or a communication device recognized by the system. All interface points may be assigned the same capabilities depending on the available confidentiality. For example, if it is determined that there is a risk of losing financial data during a transaction due to the limited confidentiality of an interface point, access from such an interface point may be restricted. Access to system 100 for retrieving reservations may also be restricted depending on the purchase of access rights.For example, it may be stated that in order for a visitor to successfully make a reservation via system 100, they must purchase reservation ability. However, the purchase price of the reservation ability may be set to zero, or the purchase step may be bypassed. If the purchase step is bypassed, the reservation acquisition step will function continuously without any indication of the amount to be paid being provided. Note that in order to access system 100 and make a reservation in advance for access to a specific area or attraction (such as an amusement park), it should be noted that it is a requirement for the user to already have purchased and possess tickets for the attraction or a set of attractions. In fact, access to make a reservation within system 100 or access to system 100 itself may be limited to users who own the corresponding tickets or those with special access (such as theme park employees).

[0026] Figures 2 and 3 include process flow diagrams for the procedures according to this embodiment. The process is generally indicated by reference numeral 200 and includes various blocks representing the acts or steps of process 200. Process 200 is controlled or facilitated by a system such as data server system 120 or other components of system 100 according to this embodiment. In fact, in one embodiment, data server system 102 includes a processor 118 and a memory 120, and the memory 120 is implemented by the processor 118 to receive data inputs, manipulate the associated data to convert those inputs into assembled information, and provide outputs corresponding to the steps or acts of the processes disclosed herein. The components of process 200 may be performed by a data reader 108 that maintains its own data processing capabilities, or may be performed by other components of system 100. Also, in different embodiments, some specific acts or steps may be performed in a different order.

[0027] As shown in Figure 2, process 200 begins with determining whether one or more tickets have already been purchased, as represented by block 202. In this context, a ticket is the right to access the amusement park or its attractions 116. In other contexts, tickets may be associated with different access rights. For example, acquiring a ticket involves associating the visitor's identity with such a right within system 100. Specifically, for example, the visitor is assigned and provided with a visitor identification number, and the system stores information in memory that identifies the number having the right to access. If tickets have not yet been purchased, process 200 facilitates the purchase of tickets, as represented by block 204. According to this embodiment, the purchase of one or more tickets is coordinated by a POS device system 148 (e.g., a ticket booth), an internet system 144, or an automated telephone system 142. During the purchase, attraction reservation capacity is added to the one or more purchased tickets, as represented by block 206. In some embodiments, attraction reservation capabilities are automatically added as a free component of the ticket. In other embodiments, attraction reservation capabilities are a user-selectable option, which may be free or require an additional fee. System 100 has the ability to grant certain reservation priority over other reservations. Priority may be granted to visitors who pay a surcharge, VIPs, or visitors performing special duties.

[0028] Block 206 further represents the actual addition of one or more attraction reservations when purchasing one or more tickets. In practice, Block 208 represents the stage where visitors are prompted to indicate whether a mobile device is available. If a visitor does not have access to such a device, they are guided to obtain alternative communication capabilities (e.g., their own communication device or a park-provided communication device), as represented by Block 210. To facilitate this, visitors are guided to communicate with guest services, which will then arrange for the provision of a mobile device to the visitor for the purpose of communicating information about reservations and, in some cases, acting as a PIF110. If a visitor does not wish to use such a mobile device, arrangements will be made for other types of notification and confirmation, such as through kiosks throughout the amusement park and paper tickets. Returning to the prompts provided in block 208, if the visitor has a mobile phone, a mobile communication device assigned by the amusement park, etc., the visitor should indicate that such a device is available. In this event, the visitor is further prompted to provide access to the mobile device via a telephone number, email address, etc., as represented by block 212. For example, the visitor may provide a telephone number to be used by system 100 for text or voice communications related to attraction reservations. In practice, the visitor can actually select their preferred notification format, as represented by block 214. This includes choosing whether voice and / or text notifications will be sent. System 100 may prompt the visitor to indicate whether text messages are acceptable. If the visitor does not wish to use text, an automated voice message will be used. Block 214 also represents a stage in which the visitor decides whether certain types of information will be sent to the mobile device.For example, visitors may limit their communications to those related to established reservations, preventing them from receiving information related to coupons, wait times for other areas of the park, and other such information. In some embodiments, certain types of information are accessed, received, or controlled based on the pricing tier of the purchased access rights. For example, visitors with higher-tier rights may be able to receive or access exclusive information about events available only to those with such access rights. As an example, those with higher-tier rights may be able to block certain communications (e.g., advertisements) that cannot be blocked otherwise.

[0029] Once a method of communication between system 100 and the visitor is established, process 200 proceeds to establish the reservation details. As represented by block 216, this may include selecting an attraction, a reservation date, and an approximate time for the reservation. In some embodiments, only one attraction and / or reservation date may be available for the reservation, in which case the attraction and / or date does not need to be selected. This embodiment allows the user to make a reservation before entering the park to confirm access to a particular attraction. However, the specific time for the reservation cannot be entered until the visitor actually enters the amusement park. In practice, for example, the specific time for the reservation cannot be entered until the ticket associated with the reservation is identified by the visitor entry system 104.

[0030] In the illustrated embodiment, as shown in block 216, visitors are asked by the system 100 to provide an approximate time for their reservation to help organize it. As previously noted, the actual reservation time is not established until certain criteria are met. For example, a specific time window for a reservation (e.g., a 15-minute window) may not be established until it is confirmed that the reserved visitor is inside the amusement park and that the reservation is still desired. The approximate time for a reservation may be indicated as AM, PM, or Evening. In another embodiment, the approximate time for a reservation may be one of several time windows that visitors can choose from (e.g., a 4-hour window). The indication of an approximate time allows for flexibility within the reservation system 100. For example, if a visitor indicates AM on a particular day as the approximate time for their reservation, it becomes possible to determine whether the visitor actually arrived at the park by a specific time in the morning. If a visitor has not arrived, they will be contacted via a mobile device containing PIF110 to decide whether their reservation should be adjusted or canceled. Certain adjustments or cancellations may be automatically made to the reservation if the visitor does not arrive within the specified time window, fails to respond via the mobile device, or provides some kind of update (e.g., "I will be an hour late"). In a particular example, if a visitor does not arrive by the time corresponding to the approximate time set for the reservation, the visitor will be prompted to indicate whether they still intend to visit the amusement park. If the visitor still intends to visit the amusement park, the reservation will be adjusted. If the visitor no longer intends to visit the amusement park, the reservation will be canceled. When a reservation is adjusted, other reservations will also be moved. Similarly, when a reservation is canceled, other reservations will be moved around, and those on the alternate list will be contacted to fill the now-available reservation slot.

[0031] The system 100 allows for multiple reservations to be made at once. In one embodiment, when multiple reservations are made, each of the multiple reservations is initially associated with either a single ticket or multiple tickets. In practice, in addition to receiving other information provided in block 216, block 218 represents the stage of receiving instructions regarding the number of visitors for the requested reservation. By allowing multiple reservations to be associated with a single ticket, one member of a group can make a reservation for a group of visitors. However, reservations for more than a certain number of visitors (e.g., 10 visitors) may require acceptance from a park employee (e.g., a member of the group sales department). Therefore, block 218 represents the stage of receiving input regarding the number of visitors for whom the reservation is to be made, which may include indicating that the reservation is for a single visitor. Next, as represented by block 220, a determination is made as to whether the reservation is for a group larger than a certain threshold. If the group exceeds a threshold, visitors are directed to contact the group sales representative for the amusement park, as represented by block 222. This may include automatically connecting visitors to the appropriate contact via telephone or automatically initiating an email to the appropriate contact.

[0032] If the group does not exceed the threshold specified for group reservations (for example, the reservation is for a single visitor), process 200 proceeds to determining whether the attraction for which a reservation is being requested has sufficient capacity, as indicated by block 224. In one embodiment, this action would involve communication between the data server system 102 and the attraction system 122. For example, as discussed above, each attraction 116 may include a monitoring and / or status management mechanism (e.g., an attraction computer) that maintains information such as reservation time, availability, downtime, etc. In other embodiments, all this information is centralized (e.g., stored on the data server system 102). If it is determined that there is sufficient capacity for the requested single or multiple reservations, confirmation of the single or multiple reservations is provided to the visitor, as shown in block 226, the reservations are recorded, and the reservations are recorded in the data server system 102 and / or the management system or attraction system 122 for the specific attraction 116 for which the reservations were made. For example, confirmation may include a text message, email, printout, or voice message sent from the data server system 102 to the mobile device via the POS device system 148, the internet system 146, the telephone system 142, or the text messaging system 146. In other embodiments, confirmation is simply provided via the device used to make the reservation.

[0033] If it is determined that there is insufficient capacity to accommodate the requested reservation, the process prompts the visitor to choose a different date, a different time period, or a different attraction, as represented by block 228. In some embodiments, if reducing or splitting the group size might make the reservation possible, the visitor may be informed of the option to split the group or reduce the group size in order to obtain an available reservation slot. If the visitor chooses to make changes to the requested reservation, the process returns to block 216. If the visitor chooses not to revise the request, the visitor is prompted to choose whether to be placed on a waiting list (a queue to fill a slot that will become available) or to cancel the reservation request, as represented by block 229. The prompt in block 229 can make it clear that not choosing to be placed on a waiting list will result in cancellation. If an option is selected, the requested reservation is placed on a waiting list, as represented by block 230. In fact, this embodiment includes a waiting list function that allows visitors to obtain a position in a waiting list to be notified of reservation slots that are likely to become available when a reservation is unavailable. Once a visitor or group is assigned a position in the waiting list, as represented by block 232, the visitor is notified that the reservation was not made, but that the visitor and / or group has been assigned a slot in the waiting list. If the visitor chooses to cancel, as represented by block 234, the reservation request is simply canceled and the visitor is notified. Similar to the reservation confirmations discussed above, notifications may be implemented by submitting a text message or voicemail to a mobile device, or by communicating via the device used to request the reservation. Furthermore, when a reservation slot becomes available, the visitor or group will be notified of the availability via the mobile device or via other notification mechanisms.Visitors are asked to respond to such notifications by indicating whether or not they can fill a slot. Visitors can respond via the PIF110 assigned to them. If a visitor indicates availability to take an available reservation slot, the waitlist reservation will be moved to the available slot.

[0034] Returning to block 202 of process 200, if a ticket has already been purchased, process 200 proceeds to the stage of contacting the reservation system 100, as shown by block 250 in Figure 3. Upon accessing the reservation system, the visitor is prompted to verify their identity as a visitor or group, as shown by block 252. This may include entering a verification number, scanning a physical ticket, accessing an application on a mobile device, etc. Next, as shown by block 254, it is determined whether the identification information corresponds to a visitor pass that is currently valid or in operation. If the identification information does not correspond to a valid visitor pass, the process directs the user to visitor services, as shown by block 256. This may include automatically connecting the visitor to amusement park staff via telephone or automatically generating an email to amusement park staff.

[0035] If system 100 determines that the identification information corresponds to a valid visitor pass, it determines whether the visitor has previously associated the visitor pass with a mobile device. If the mobile device is not associated with the visitor, process 200 proceeds to block 258, which represents a step in determining whether such a device is available. Many of the subsequent steps are essentially equivalent to those indicated and described in relation to Figure 2. Specifically, block 258 represents a step in prompting the visitor to indicate whether a mobile device is available. If the visitor does not have access to such a mobile device, the visitor is directed to visitor services, as shown in block 260. Visitor services then arrange for communication capabilities for the visitor, for example, by providing the visitor with a mobile device for the purpose of communicating information about reservations. If the visitor does not wish to use such a mobile device, arrangements will be made for notification via kiosks throughout the amusement park.

[0036] Returning to the prompts provided in block 258, if the visitor has a mobile phone, a mobile communication device assigned by the amusement park, etc., the visitor only needs to indicate that such a mobile device is available. In this event, as represented by block 262, the visitor is further prompted to provide access to the mobile device, and then to provide such access by telephone number, email address, etc. For example, the visitor may provide a telephone number to be used by system 100 for text or voice communications related to attraction reservations. In practice, as represented by block 264, the visitor may actually select a notification format. This may include selecting whether voice and / or text notifications will be sent. System 100 may prompt the visitor to indicate whether text messages are acceptable. If the visitor does not wish to use text, an automated voice message will be used. Similarly, email may be provided as an option. Block 264 also represents a stage in which the visitor decides whether certain types of information will be sent to the mobile device. For example, visitors may limit their communications to those related to reservations, preventing them from receiving communications related to coupons, wait times for other areas of the park, and other matters. Note that if a mobile device has already been identified in block 254, process 200 may proceed directly to block 264 or block 266.

[0037] Once a method of communication between system 100 and the visitor is established, process 200 proceeds to the stage of establishing reservation details. As represented by block 266, this may include selecting an attraction, a reservation date, and an approximate time for the reservation. In some embodiments, only one attraction may be available for the reservation, in which case the attraction does not need to be selected. As noted above, this embodiment allows a user to make a reservation and confirm access to a particular attraction before entering the park. However, the specific time for the reservation is neither entered by system 100 nor provided to the visitor until the visitor actually enters the amusement park. In practice, for example, the specific time for the reservation cannot be entered until the ticket associated with the reservation is identified by the visitor entry system 104.

[0038] As shown in block 266, the system 100 requests an approximate time for a reservation (e.g., AM or PM) to help organize reservations. The approximate time for a reservation is indicated as AM, PM, or Evening. In another embodiment, the approximate time for a reservation may be one of several time windows that the visitor can choose from. The indication of approximate time allows for flexibility within the reservation system 100. If a visitor has not arrived by the time corresponding to the indicated approximate time, the visitor is contacted via a mobile device or the like to decide whether the reservation should be adjusted or canceled. Certain adjustments or cancellations to the reservation may be made automatically if the visitor has not arrived within the indicated time window, if the visitor fails to respond via a mobile device, if the visitor provides some kind of update, etc. When a reservation is adjusted, other reservations will also be moved. Also, when a reservation is canceled, other reservations will be moved around and contacted to fill the reservation slot that has become available to someone on the waiting list.

[0039] As shown in Figure 2 when purchasing tickets, the system 100 allows for multiple reservations to be made for tickets that have already been purchased. In one embodiment, when multiple reservations are made, they are first associated with a single ticket or with each of the multiple tickets. By associating multiple reservations with a single ticket, one member of a group can make a reservation for a group of visitors. However, reservations for more than a certain number of visitors may require acceptance from amusement park staff. Therefore, block 268 represents the step of entering the number of visitors for whom the reservation is to be made, and this step may include indicating that the reservation is for a single visitor. Next, as shown by block 270, it is determined whether the reservation is for a group larger than a certain threshold. If the group exceeds the threshold, as shown by block 272, the visitor is directed to contact a group sales representative for the amusement park. This may include automatically connecting the visitor to the appropriate contact via telephone or automatically initiating an email to the appropriate contact.

[0040] If the group size is within a threshold, a determination is made regarding the attraction's capacity, as shown by block 276. If it is determined that there is insufficient capacity to accommodate the requested reservation, process 200 includes a step of prompting the visitor to choose a different date, a different time period, or a different attraction, as shown by block 278. In some embodiments, if reducing or splitting the group size might make the reservation possible, the visitor may be notified of the option to split the group or reduce the group size to obtain an available reservation slot. If the visitor chooses to make changes to the requested reservation, the process returns to block 266. If the visitor chooses not to revise the request and not to cancel the request, the requested reservation is placed on a waiting list, as shown by block 280. In practice, this embodiment includes a waiting list feature that allows the visitor to get a position on a waiting list to be notified of reservation slots that are likely to become available when a reservation is unavailable. Once a visitor or group is assigned a position on the waiting list, as indicated by block 282, the visitor is notified that their reservation was not made, by the assignment of a slot on the waiting list.

[0041] If it is determined that there is sufficient capacity for the requested single or multiple reservations, a determination is made as indicated by block 290 as to whether the single or multiple visitors have already accessed the attraction within a specified time period (e.g., within the morning hours on the day of the requested reservation). If the visitors have previously experienced an attraction with a time slot, block 292 determines whether the access threshold has been reached (e.g., whether the single or multiple visitors or group have experienced the attraction three times on the same day). Such determinations may be made by an access management mechanism (e.g., the system of data server system 102 or system 122). If there are no restrictions on access to the attraction or the restrictions have not been reached, a confirmation of the single or multiple reservations is provided to the visitors or group as shown in block 294, and the reservations are recorded in the data server system 100 and / or the management system 122 for the specific attraction 116 to which the reservations were made. However, subsequent access to the attraction may be restricted based on previous access. If a visitor has a limit on the number of times they can access an attraction within a given time period and has reached that limit, access to any further reservations will be denied, and the visitor will be placed on a waiting list as indicated by block 280. For example, confirmation may include a text message or voice message sent from the data server system 102 to the mobile device via the internet system 144, telephone system 142, text system 146, or POS device system 148.

[0042] Figure 4 is a process flow diagram of a method employing the system 100 according to this embodiment. The process as a whole is indicated by reference numeral 400 and includes various blocks representing actions or stages of the process 400. According to this embodiment, the process 400 is controlled or facilitated by a system such as the data server system 102 or other components of the system 100. In practice, in one embodiment, the data server system 102 includes a processor 118 and a memory 120, which stores instructions executed by the processor 118 to receive inputs and provide outputs corresponding to the stages or actions of the process disclosed herein. These inputs and outputs may be received from and directed to other components of the system 100 with respect to the data server system 102, respectively. Also, in different embodiments, some specific actions or stages may be performed in a different order.

[0043] Input from visitors to System 100 (before or during their visit) may include ticket identification, mobile phone number, reservation date, reservation group size, estimated park entry time (e.g., AM or PM), associated ticket identification (e.g., group ticket information), and other information. Input from operators to System 100 may include data indicating ride capacity, estimated downtime, attraction operating status, re-ride status, queue ratio, messages, advertisements, statistics, and data requests. Automated input may include the time visitors enter the park, the time visitors enter the queue, the time visitors leave the queue, estimated wait times, and valid ticket verification. Output from System 100 to various systems (e.g., website, mobile site, text messaging system, telephone, and POS devices) may include reservation capacity check results, general messaging, advertisements, available reservation dates, and reservation confirmations. Output from System 100 to operators may include allowable ride queue entry messages and reservation acceptance messages. Outputs from system 100 to visitors may include status updates, reservation modification messages, reservation window messages, time limit warnings, active time window messages, visitor thank-you messages, reservation confirmations, reservation updates, general messaging, advertisements, and admission messages. In different embodiments, some specific inputs and outputs may be directed to different components.

[0044] Process 400, as represented by block 402, begins with the steps of verifying that a visitor has the applicable access rights and, once access rights are verified, allowing the visitor into the amusement park. This step may involve the use of the visitor entry system 104. Access rights are verified by determining that the visitor has provided identification information (e.g., a barcode on a physical ticket or a date stored on a mobile device) corresponding to a valid right to access the amusement park. For example, this may include scanning the ticket provided by the visitor and verifying that the information read from the ticket is stored in a central database as corresponding to the right to enter on the date being scanned. In practice, such information may be stored in a central database 102 and issued electronically to the visitor or printed on a physical ticket item at the time of purchase.

[0045] After the identification information is verified, a determination is made as to whether the identification information is associated with an attraction reservation, as shown in block 404. If the reservation is not associated with the identification information, the visitor may use the queue to access the attraction, join a group that has a group reservation, or make a reservation, as shown in block 406. For example, if a visitor has not established a reservation before arriving at the amusement park, the visitor can obtain reservation rights and / or make a reservation using the internet system 144, the telephone system 142, the text system 146, or the POS device system 148. If one or more reservations are already associated with the identification information and certain criteria are met, the system 100 automatically establishes a specific reservation time, as shown in block 408. In practice, as is happening in block 402, once a visitor is identified as having entered the amusement park, the approximate time associated with the established reservation is converted to a more specific time (e.g., a time window or approximate time during which the attraction can access the reservation), and the visitor is provided with a reservation notification (e.g., voice message, text message, or email) via a mobile device, as shown in block 410. In a specific example, when requesting a reservation, the visitor may provide a broad time window such as "during morning hours," "during afternoon hours," "during evening hours," "between 1:00 PM and 6:00 PM," "between 7:00 AM and noon," etc. As soon as the visitor's entry into the amusement park is confirmed, as soon as the visitor is confirmed to be in a specific area, or as soon as the visitor checks in, a specific time for the reservation, such as a time window from 2:00 PM to 2:15 PM or approximately 3:00 PM, is assigned by system 100. This may occur automatically when certain criteria are met. For example, if a visitor does not arrive within a predefined time frame (e.g., morning or afternoon), the availability of their reservation may change. Another example is when an attraction becomes unavailable due to technical problems.If there are any issues related to reservations, they may be communicated to visitors in the same manner as reservation confirmations.

[0046] Once a reservation is confirmed, system 100 prompts the visitor to make the option to cancel or modify the reservation available, as represented by block 412. For example, immediately after notifying the visitor of the confirmed reservation, system 100 may require the visitor to indicate whether certain reservations should be canceled or modified. If the visitor indicates that the reservations should be modified or canceled, the visitor is directed to visitor services or to components of the reservation system 100 that facilitate the execution of components of process 200 shown in Figure 3, as represented by block 414. If the visitor wishes not to change any reservations, the reservations may be transferred to other identifying information (e.g., information associated with a PIF 110 assigned to another visitor). For example, a visitor with a ticket associated with a particular attraction may transfer the reservation to another visitor's ticket. In practice, system 100 will prompt the user to transfer the reservation or receive a user request to transfer the reservation, as shown by block 416. The visitor will respond by transferring the reservation to identification information for another access path, using a mobile device, kiosk, visitor contact service, etc., as shown by block 420. Multiple reservations may be transferred at once, or a series of transfers may be performed in a loop operation, as indicated by the arrow pointing from block 420 to block 416, until the desired transfers are completed. Note that system 100 allows visitors to change or modify their reservations within a certain time window (for example, up to 30 minutes before the reservation time) or at any time before an existing reservation time slot. This may include attempting to cancel an existing reservation and replace it with a time slot preferred by the visitor, trading an existing reservation with another visitor, or canceling an existing reservation and being placed in a virtual queue, etc.If a visitor attempts to change an existing reservation, that visitor may be given priority over visitors without existing reservations for the purpose of selecting another available time slot for a replacement reservation.

[0047] Once all transfers have been made, a determination is made regarding any associated delays or other issues, as indicated by block 422. This may include periodically updating and continuously monitoring attraction information from the monitoring system associated with the attraction in question (e.g., attraction system 122). If an issue is identified that is likely to cause a change in the reservation, the visitor is notified of a new time window for the reservation via text message, voice message, email, or kiosk display, as indicated by block 424. The notification may further include an indication of the nature of the delay or change. Any conflicting reservations may also be automatically adjusted. For example, if the changed reservation time conflicts with an established reservation time, the established reservation time may be automatically changed, or the visitor may be prompted to determine the desired outcome from the available options.

[0048] If no issues are identified regarding the reservation change, process 400 continues to monitor whether the time period prior to the reservation has been reached, as shown in block 430. For example, block 430 may represent a determination of whether the current time is 15 minutes or less before the reservation (e.g., time window). If the current time is not 15 minutes or less before the reservation, process 400 continues monitoring. If the current time is 15 minutes or less before the reservation, the visitor will be given a reminder that their reservation time is approaching, as shown in block 432. This would include a suggestion that the visitor should begin moving toward the attraction. Note that the time period before the visitor is notified may vary depending on the visitor's location. For example, if system 100 identifies that the visitor is in a particular location where it normally takes a certain amount of time to reach the attraction for which they have a reservation, the time period associated with the reservation reminder notification would be based on this distance and the corresponding travel time.

[0049] After receiving a reservation alert notification, system 100 may allow visitors to postpone or delay their reservations. For example, visitors may be prompted to or permitted to request a reservation postponement, as indicated by block 434. If a visitor chooses to postpone their reservation, they notify the reservation system 100 via a mobile device or other access point to the reservation system 100, as shown by block 436. The reservation system 100 would respond to such a request with information about a new reservation for a later time, a selection of available reservation times for the later time, or an instruction that the later time is unavailable. System 100 may then prompt the visitor to respond, for example, by confirming or selecting a supplied later time or by declining to modify an existing reservation. If a new reservation is established, system 100 provides confirmation of the revised reservation, as indicated by block 438, and the process continues to monitor the current time against the reservation, as indicated by block 430. Please note that at any point during the process, visitors may choose to cancel their reservation in addition to modifying it.

[0050] If a visitor decides not to delay their reservation, they will begin walking towards the attraction, as indicated by block 440. As noted above, the reservation reminder takes into account the distance the visitor must travel by monitoring the visitor's location and providing the reminder with a corresponding amount of time before the reservation time. As indicated by block 442, a determination is made regarding when the reservation time becomes active, such as when the current time falls within the reservation time window. This is continuously monitored in the illustrated embodiment. When the current time matches the reservation (for example, when the current time falls within the reservation window), the visitor is notified that the reservation is active and that they should enter the attraction, as indicated by block 444. As indicated by block 446, once the visitor enters the queue associated with the attraction, the visitor is required to confirm that they have a reservation by providing the appropriate identification information. For example, a data reader 108 of system 100 may be used to scan a ticket or interface with a mobile device at the entrance or entry point to a short reservation queue to confirm that the visitor has a reservation.

[0051] Once visitor identification and initial verification of reservation information (e.g., ticket scanning) are performed at the entrance to the queue, further verification is required before actually entering the attraction, as shown by block 448. This facilitates monitoring of queue length at the associated attraction. Based on this measurement, future access prospects for reservations and queues can be adjusted to control wait times in reservation queues. For example, under stable operation, this embodiment may be configured to control the approximate time a visitor spends in a reservation queue to about 10 minutes. In practice, system 100 instructs the operator to allow visitors to leave the queue and board the attraction at specified intervals based on an algorithm that takes queue characteristics into account. The verification of identification information by visitors to board a ride (e.g., ticket scanning and access to associated reservation data) also facilitates monitoring and control of subsequent access to the attraction. For example, this can be used to indicate that a visitor has already accessed a particular attraction using a reservation. The instructions are stored in system 100 and associated with identification information, so that subsequent reservation requests can be controlled based on whether certain attractions have already been accessed by the visitor. This may include scanning tickets after the visitor has left an attraction.

[0052] System 100 may employ an algorithm that takes into account that some specific visitors may have had access to an attraction immediately before it became inoperable due to a technical failure. For example, block 452 represents the stage where it is determined whether a visitor checked in to an attraction but was unable to experience it due to a technical failure or other reasons. If the attraction was functioning, the visitor is indicated as having experienced the attraction, as shown in block 454. If the attraction was not functioning, the visitor is automatically assigned another reservation or the right to access it as soon as the technical failure or other reasons are resolved, as shown in block 456. If access to the attraction is blocked or the experience of the attraction is interrupted, the attraction is considered not functioning.

[0053] This embodiment aims to enable reservation transactions via a reservation transaction system, which may be a component or module of the data server system 102. This functionality would be useful when system 100 is used for multiple attractions. For example, suppose a first visitor has a reservation to access a first ride at 1:00 PM. However, the first visitor decides to have lunch and will not be able to arrive at the attraction in time for the reservation. The system prompts the first visitor at a specific time prior to the reservation (e.g., 15 minutes before) to decide whether they intend to extend the reservation. The prompting time may be based on the visitor's detected location relative to the attraction 116 where the reservation has been established. The first visitor responds by indicating that they will not intend to extend the reservation because they will not be able to arrive at the first attraction in time. System 100 then automatically searches for a later reservation for the first visitor. Suppose a second visitor has a 4:00 PM reservation and, as determined by System 100, is currently located near the first attraction. System 100 identifies this second visitor based on their location and reservation time and sends a message to the second visitor indicating that a transaction with the reservation held by the first visitor is available. If the second visitor accepts the transaction, the reservation is transferred between the first and second visitors by System 100, and each visitor is notified of their new reservation. This helps to eliminate the stress on visitors associated with making appointments on time and helps maintain full capacity.

[0054] This embodiment includes processes and systems configured to provide each of several different visitors or groups with multiple reservations or itineraries based on input from those visitors. For example, Figure 5 is a process flow diagram that provides an overall overview of process 600 according to this embodiment for facilitating visitors scheduling multiple reservations for attractions ranging from rides to restaurants. Process 600 in Figure 5 as a whole depicts the steps of establishing an itinerary that substantially optimizes visitors' time within the park and its facilities. Note that process 600 is depicted at a high level and may include specific process mechanisms discussed above with respect to Figures 2-4. Furthermore, process 600 may be implemented using all or some of the mechanisms of system 100 discussed above.

[0055] Process 600 begins, as shown by block 602, by enabling visitors to communicate with the reservation system and provide attraction preferences for certain attractions. This may include a step of providing access to the reservation system for visitors, whether inside or outside the park. For example, a visitor may provide a list of certain attractions or types of attractions that the visitor is interested in experiencing. This may include a step of providing specific attractions and associated reservation preferences along with a ranking indicating the level of interest for each attraction. Alternatively, a visitor may simply provide a list of attractions of interest and have the system suggest times. Similarly, a visitor may simply provide certain attraction types (e.g., rides suitable for young children) and have the system suggest itineraries. Once preferences are entered, the reservation system receives the associated data, as shown by block 604, and the process then processes the data, as shown by block 606, to substantially optimize the schedule for each visitor and optimize the utilization rate of park attractions. In response to the preferences provided by visitors, the reservation system executes an optimization algorithm, as represented by block 608, and outputs a proposed itinerary. In one embodiment, visitors may provide input before entering the park, but do not receive the proposed itinerary until after they have entered.

[0056] The algorithm represented in block 606, which is to be executed, may be stored in memory and, when executed by the system's processor (processor 118 of the data server system 102), generate a draft itinerary as represented in block 608. The visitor can then review the itinerary as represented in block 610 or, after examining the draft itinerary, request a different itinerary. If the confirmation is received by the system, the process provides the confirmed itinerary as represented in block 612. If the visitor chooses to modify the itinerary, the visitor is prompted to indicate whether a specific modification is needed or if a cancellation is desired. If a cancellation is desired, the process terminates and the cancellation is confirmed as represented in block 616. If a modification is desired, the process returns to block 604 and / or allows the change to the schedule. Note that at any point in process 600, the system may provide a revised itinerary based on optimization data, taking into account the availability of attractions and known limitations of the visitor's preferred schedule.

[0057] The algorithm, as described in block 606, may function to identify the locations of attractions listed as of interest to the visitor and to determine the schedule based on various factors or optimization data such as the ease of transition between individual attractions of interest. For example, the system may present an itinerary that includes reservations for visitor-favorite attractions arranged in series so that the visitor can move from attraction to attraction throughout the park without having to retrace their steps. The itinerary may further include reservations for attractions along a route suggested based on gaps in the schedule. In addition to taking distance and attraction locations into account, the algorithm may also take into account maximizing the park's operational efficiency, other people's reservations, levels of interest, meal times, scheduling overlaps with other visitors identified as belonging to common groups (e.g., social networks), and other factors. For example, the optimization algorithm may present an itinerary that restricts movement between attractions but also accommodates the unavailability of reservations for specific times for highly requested attractions. The algorithm may further guide visitors throughout the park to avoid anticipated overcrowding in certain areas based on established reservation and historical park data. The algorithm may further take into account that visitors may need breaks around meal times and either suggest restaurant reservations or simply recommend nearby restaurants. The algorithm may further take into account certain specific realities. For example, the algorithm may adjust the itinerary so that certain extremely popular attractions are excluded at certain times after meals. The algorithm may further maximize park utilization by suggesting reservations or visits to attractions that are underutilized at certain times.In one embodiment, the algorithm takes into account the ranking of visitors' levels of interest in attractions (e.g., high, medium, low) and provides a schedule that takes this into account. For example, the algorithm may arrange reservations for high-interest attractions to be spread throughout the day to maintain interest throughout the day, or to ensure that all high-interest attractions are experienced early on the day by having everything happen early.

[0058] This embodiment further facilitates in-park meeting for groups arriving separately, groups that disperse once they enter the park, or groups that desire a certain overlap in their scheduling. For example, Figure 6 illustrates a process 700 performed by this embodiment for coordinating visitor schedules. The process begins with prompting the visitor to indicate whether they wish to join a group they were already a member of or whether they wish to have a schedule that overlaps with another group's schedule. This initial procedure is represented by block 702 and may be performed using any of the access mechanisms discussed above in relation to system 100, such as a mobile phone interacting with system 100. Block 702 includes a step of identifying the visitor and the group.

[0059] If a visitor wishes to meet up with a group or organization to which they belong, the process may identify a meeting location, as represented by block 704, guide the visitor to that location, as represented by block 706, and / or instruct the organization to meet the visitor at that location. This would generally occur if a visitor did not arrive at the park together with their organization or became separated from their organization during their visit. To facilitate the regrouping of organizations, this embodiment may use PIF positioning information to guide the visitor to the desired organization, provide a meeting location using an established itinerary for the organization, communicate the meeting location using visitor-to-visitor communication, and / or communicate the meeting location using system-to-visitor communication. For example, the next attraction on the itinerary is provided to the visitor, and the organization is notified via text message that the visitor is supposed to join the organization with a reservation for the next attraction. Furthermore, visitor-to-visit communication can be facilitated between groups and visitors through a reservation system (e.g., text messaging or voice communication).

[0060] If a visitor wishes to establish overlap between themselves or a group or organization of visitors and at least one other group, process 700 proceeds to block 710 in the illustrated embodiment. This occurs when two or more groups or individuals decide to spend time together in the park. For example, a group from a particular area might decide to establish overlapping schedules so that they can experience attractions of common interest together, while their separate groups also experience other attractions. The group or individual may or may not already have reservations (e.g., itineraries). Block 710 generally represents the stage of identifying the group or individual and confirming their desire to have overlapping attraction experiences. Once this is established, a determination is made as shown in block 712 as to whether one or more groups have existing itineraries or reservations, and if no itineraries or reservations have been established, preferences are offered. Existing itineraries and reservations are taken into consideration, and otherwise preferences are offered. This would include offering attractions of common interest and desired overlaps. Then, as shown in block 714, the algorithm is performed based on the common interests and preferences of visitors, the comparison of existing itineraries, and / or optimization data, based on explicit designations, to provide overlapping itineraries for two or more individual visitors or groups of two or more visitors.

[0061] Although only certain mechanisms of the present invention are illustrated and described herein, many modifications and changes will be conceivable to those skilled in the art. Therefore, the accompanying claims should be understood as intended to encompass such modifications and changes as being essential to the essence of the invention.

Claims

1. A queuing management system, Based on a first set of guest preferences and the operational status data associated with the first set of guest preferences, a first reservation for a first guest is generated. A second reservation for a second guest is generated based on a second set of guest preferences and the operational status data associated with the second set of guest preferences. At a predetermined time prior to the time of the first reservation, based on the location of the first guest at that predetermined time and the time of the first reservation, a reservation reminder for the first reservation is issued to the first guest. In response to the first guest's reply that they will not continue the first reservation in response to the reservation warning for the first reservation, it is determined whether the first reservation can be transferred to the second guest based on the second guest's location, the time of the first reservation, and the time of the second reservation. In response to the determination that the transfer is possible, a notification is sent to the second guest stating that the transfer of the first reservation is possible. The first reservation is transferred from the first guest to the second guest. Including at least one processor configured as follows: Waiting queue management system.

2. The queuing management system according to claim 1, wherein the first guest is associated with a first portable identification device (PIF), the second guest is associated with a second PIF, and the first and second PIFs are associated with each other.

3. The queuing management system according to claim 2, wherein the first PIF corresponds to a master PIF having access to modify the reservation associated with the second PIF.

4. The queuing management system according to claim 3, wherein the master PIF has access to make multiple reservations on behalf of one or more PIFs associated with the master PIF.

5. The queuing management system according to claim 4, wherein the at least one processor is further configured to prevent the master PIF from making reservations on behalf of the one or more PIFs if the number of PIFs exceeds a threshold number of PIFs.

6. The queue management system according to claim 4, wherein the at least one processor is further configured to prevent the master PIF from making reservations for attractions on behalf of the one or more PIFs if the one or more PIFs access an attraction within a certain period of time.

7. The at least one processor is further configured to receive a request to transfer the first reservation from the first guest to the second guest. The queuing management system according to claim 1, wherein the first reservation is transferred to the second guest based on the received request.

8. The aforementioned at least one processor is Upon receiving a signal indicating that the first guest is inside the amusement park, In response to receiving the aforementioned signal, the operating status data associated with the attraction indicated by the first set of guest preferences is determined. The system is further configured such that the first reservation is generated in response to the operational status data. The queuing management system according to claim 1.

9. The queuing management system according to claim 8, wherein the at least one processor is further configured to receive the signal based on the detection of a first portable identification device (PIF) associated with the first guest located within the amusement park.

10. A method for queue management performed by at least one processor, To generate a first reservation for a first guest based on a first set of guest preferences and the operational status data associated with the first set of guest preferences, To generate a second reservation for a second guest based on a second set of guest preferences and the operational status data associated with the second set of guest preferences, At a predetermined time prior to the time of the first reservation, based on the location of the first guest at that predetermined time and the time of the first reservation, a reservation reminder for the first reservation is issued to the first guest. In response to the first guest's reply that they will not continue the first reservation in response to the reservation warning for the first reservation, it is determined whether the first reservation can be transferred to the second guest based on the second guest's location, the time of the first reservation, and the time of the second reservation. In response to the determination that the transfer is possible, a notification is issued to the second guest that the transfer of the first reservation is possible. Transferring the first reservation from the first guest to the second guest, Methods that include...

11. The method according to claim 10, wherein the first guest is associated with a first portable identification device (PIF), the second guest is associated with a second PIF, and the first and second PIFs are associated with each other.

12. The method according to claim 11, wherein the first PIF corresponds to a master PIF having access to modify the reservation associated with the second PIF.

13. The method according to claim 12, wherein the master PIF has access to make multiple reservations on behalf of one or more PIFs associated with the master PIF.

14. The method according to claim 13, further comprising preventing the master PIF from making reservations on behalf of the one or more PIFs if the number of PIFs exceeds a threshold number.

15. The method of claim 13, further comprising preventing the master PIF from making a reservation for an attraction on behalf of the one or more PIFs if the one or more PIFs access an attraction within a certain period of time.

16. The method according to claim 10, further comprising receiving a request from the first guest to transfer the first reservation to the second guest, wherein the first reservation is transferred to the second guest based on the received request.

17. The aforementioned method, Receiving a signal indicating that the first guest is inside the amusement park, In response to receiving the aforementioned signal, the operation status data associated with the attraction indicated by the first set of guest preferences is determined, The first reservation is generated in response to the operational status data, The method according to claim 10.

18. The method according to claim 17, wherein the signal is received based on the detection of a first portable identification device (PIF) associated with the first guest located within the amusement park.

Images