Queue management system and method

The reservation system addresses long wait times at amusement parks by dynamically managing attraction reservations, optimizing queue times, and enhancing visitor experience through real-time adjustments and flexible access options.

JP2024169432AActive Publication Date: 2024-12-05UNIVERSAL CITY STUDIOS LLC

Patent Information

Application Number
JP2024137775
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2012-06-07
Filing Date
2024-08-19
Publication Date
2024-12-05
Estimated Expiration
2033-06-07

AI Technical Summary

Technical Problem

Amusement parks face challenges with long wait times at attractions, which deter visitors and reduce overall experience quality, despite increased capacity and demand.

Method used

A reservation system utilizing an electronic data server and mobile devices to dynamically manage and optimize attraction reservations, allowing visitors to wait virtually and adjust queue times in real-time, with features like micropayments for queue updates and tiered access levels.

Benefits of technology

Reduces wait times by efficiently managing reservations and crowd flow, enhancing visitor experience and park operations, while providing flexibility and convenience through dynamic queue adjustments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024169432000001_ABST
    Figure 2024169432000001_ABST
Patent Text Reader

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
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] Since the early 20th century, amusement parks have grown substantially in popularity. To address this increased demand, amusement parks have expanded exponentially by adding attractions and space. Adding attractions (e.g., rides, restaurants, concessions, and shows) generally provides the amusement park with additional capacity to handle a large number of visitors (guests). On the other hand, additional attractions typically also provide an incentive for potential visitors to visit the amusement park. Thus, while certain amusement parks have added additional capacity, the additional capacity does not necessarily result in shorter wait times for attractions, since attendance usually increases commensurately. Also, for operational efficiency reasons, it is often desirable to limit the availability of attractions when attendance is low. Thus, queuing for attractions is a year-round problem for amusement parks.

[0003] While park guests have wanted grander attractions, better attractions, and more elaborate attractions, they also want and expect an overall positive experience. Providing an overall positive experience for park guests involves addressing certain issues related to queuing for attractions. In fact, it is now recognized that park guests may be deterred from returning to a particular amusement park due to negative experiences with queuing times. Also, guests may refrain from accessing park operations (e.g., concession stands) due to the time spent waiting in line. Indeed, in the past, guests 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 park capacity does not always match guest utilization of capacity due to individual guests' preferences for some specific attractions over others. Accordingly, it is now recognized that improved amusement park queuing systems and methods are desirable.

[0004] These and other features, aspects, and advantages of the present disclosure will be better understood from the following detailed description when read in conjunction with the accompanying drawings, in which like reference characters represent like parts throughout. [Brief description of the drawings]

[0005] [Figure 1] 1 is a schematic diagram of an amusement park including a reservation system in accordance with the present technique. [Diagram 2] 1 is a process diagram of a method according to the present technique. [Diagram 3] 1 is a process diagram of a method according to the present technique. [Figure 4A] 1 illustrates a process diagram of a method according to the present technique. [Figure 4B] Together with FIG. 4A, a process diagram of a method according to the present technique is depicted. [Diagram 5]1 is a process diagram of a method for facilitating guest scheduling of multiple reservations for an attraction in accordance with the present technique. [Figure 6] 1 is a process diagram of a method for adjusting guest schedules in accordance with the present technique. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0006] The present disclosure generally relates to methods and systems for controlling wait times in amusement park attraction queues by dynamically managing reservations for amusement park attractions including shows, restaurants, rides, concessions, etc. The present embodiment includes a system having electronic data servers and applications capable of communicating and monitoring metrics or characteristics related to reservations for attractions in an amusement park and controlling queue flow characteristics. The system may include verification systems, tracking systems, fulfillment systems, mobile devices, and back-end computers and devices. The system is configured to receive one or more reservation requests at a time and assign approximate or specific time frames for reservations based on information provided by a user and / or based on other data (e.g., data related to the operation of the associated attraction or data related to the detected locations of the guest holding the reservation). The present embodiment is also configured to access or modify one or more existing reservations and / or adjust queue characteristics (e.g., access ratios) based on changes in reservation requests, changes in guest scheduling, guest location, data regarding one or more attractions associated with the reservation, entitlement levels (e.g., based on tiered payment options for various access levels), etc. A tiered approach to pricing for various features or components of entitlement levels may be available, including micropayments for some specific services or tasks. For example, a guest may offer a micropayment to receive periodic updates regarding short queues in some specific areas of the park.

[0007] The system allows guests to wait in a virtual queue for a particular attraction or attractions using mobile or wireless technology, allowing them to experience other attractions in other areas of the park or relax away from the park while they wait. In effect, the present embodiment includes a system configured to communicate with one or more attractions associated with a reservation request or an existing reservation to dynamically adjust and optimize the guest's waiting experience in real time and communicate updates to the guest (e.g., via mobile or wireless technology). The present embodiment may facilitate communication with the guest 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 the guest as used herein includes email, text, video, web-based, and voice communication from the system to the mobile device, etc. The location of the guest within the 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 guests may be accomplished through publicly accessible displays, for example, kiosks having communications mechanisms (e.g., computers capable of accessing a network) may be located throughout the park.

[0008] In accordance with the present technique, a reservation system is configured to provide an interface for a user or guest to make reservations for access to one or more attractions of an amusement park during a visit. Reservations may be made for groups of guests or for single guests prior to arrival at the park or while in the park. In practice, the functionality of the system described herein may include communicating with single guests or groups. Making reservations for multiple guests as a group may be facilitated by enabling association of corresponding tickets with all single guest tickets. These reservations may be made using a laptop computer, desktop computer, mobile device, or other access device prior to or during the guest's visit to the park. Such reservations may be obtained through online resources, through direct access to a portal of the reservation system, through a telephone system, or otherwise.

[0009] According to the present disclosure, a ticket may include various types or combinations of credentials that will be used to verify access rights to an attraction (e.g., an amusement park). The ticket (e.g., paper ticket, biometric, or electronic ticket) will be used to verify current or future access rights. When tickets are not purchased in bulk, the present embodiment can associate them as a group. Any member of the group of guests can then obtain a reservation for the group. For example, if a group of guests arrives at an amusement park and each purchases a ticket separately, one of the guests in the group can use the present embodiment to make one or more reservations for the group. The present embodiment can associate a reservation for a group with a single ticket, which becomes a "master ticket." When a reservation is fulfilled, the master ticket associated with the reservation must first be verified, and then the tickets of the remaining group members are verified. Several techniques and systems could be used to associate the ticket with the master ticket. This could include scanning the ticket to verify identity, authenticity, and reservation information. During the validation process, each ticket is associated with the rest of the reservation in the system, so that subsequent reservations do not have to have the master ticket validated before the reservation can be used.

[0010] Also, reservations can be made without a specific time frame for the reservation being specified prior to the guest's visit to the park. For example, a reservation may be established for a particular date without specifying a reservation time range in hours. However, in some embodiments, an initial slot of time is defined based on the guest's expected arrival time at the park. For example, the expected arrival time may be specified as morning or afternoon. In such embodiments, upon the guest's arrival, a particular time frame (e.g., 3:00 PM to 3:15 PM) may be assigned for reservation depending on the guest's arrival time and the availability of reservation time slots for the associated attraction. It is noted that the present embodiment can be used to make multiple reservations for one or more attractions. The present embodiment can further facilitate communication between the reservation system and the guest to provide dynamic updates of reservation times and provide crowd control by encouraging the guest to visit specific areas of the park. The present embodiment can also efficiently accommodate changes in guest schedules by facilitating reservation transactions within the reservation system. For example, if a guest wishes to change their assigned reservation, the guest can use the reservation system to obtain a new reservation for a more convenient time and the original reservation will be returned to the available inventory or, if applicable, it will be reassigned.

[0011] 1, a system for managing theme park attraction queues is generally designated by the numeral 100. The queue management system 100 includes a data server system 102, a guest entry system 104 (e.g., a tracking system or an access authorization system), a fulfillment system 106, data readers 108, portable identification features (PIFs) 110, a tracking system 112, a back-end computer system 114, and at least one attraction 116. Some specific components of the system 100 may be extensions or modules of the data server system 102, while other components may be separate mechanisms that communicate with the data server system 102. In practice, the data server system 102 may include one or many computers having one or more processors 118 and memory 120 (e.g., hard drives or other tangible machine-readable media that are non-transitory in the sense that they are not simply signals). Indeed, in one embodiment, the data server system 102 includes one or more redundant servers to ensure reliability and allow for maintenance. The memory(s) 120 may store code or instructions that, when executed by the processor(s) 118, cause the reservation system 100 to perform certain functions according to the present embodiment. In fact, some particular component systems of the system 100 (e.g., the guest entry system 104) may include code stored in the memory 120 that may be activated by the processor 118. It should be noted that the present disclosure may refer to components of the system 100 or to a grouping of all of the components of the system 100 as the "reservation system 100" or the "system 100". Thus, actions designated as being performed by the reservation system 100 or the system 100 may include actions performed by a subset of the system 100.For example, data server system 102, in conjunction with data readers 108 of guest entry system 104, may perform the action of determining whether a particular guest has checked into the amusement park (e.g., passed through an entrance or main gate). This action may also be said to be performed by reservation system 100.

[0012] In the illustrated embodiment, the attractions 116 include monitoring and / or data maintenance systems 122 that are utilized to monitor and / or provide information regarding the operation of the associated attraction 116. These monitoring and / or data maintenance systems 122 are referred to as attraction systems 122 and may include one or more of a computer, a control system, and monitoring mechanisms (e.g., sensors and cameras). In some embodiments, the attraction systems 122 essentially include ports or workstations for inputting information into the data server system 102, retrieving data from the data server system 102, or otherwise communicating with the data server system 102. For example, the attraction systems 122 may enable park employees to input data regarding the operation of the associated attraction (e.g., wait times, attraction capacity, downtime). In other embodiments, the attraction systems 122 are separate systems configured to operate independently and to communicate with the data server system 102. As an example, the attractions system 122 may be configured to log all activity associated with a reservation for the corresponding attraction 116 (e.g., downtime, statistics regarding requested and fulfilled reservations, availability, and amount of traffic through the attraction) to facilitate data analysis by the data server system 102 and / or backend computer system 114. In one embodiment, the system 100 is scalable to store and process large amounts of data. Data obtained from the attractions system 122 is submitted to data analysis by the system 100, the results of which are used to assist in controlling queue characteristics and reservations, as described in more detail below.

[0013] The PIF 110 may include a ticket. Specifically, for example, the PIF 110 may include a printed ticket, a biometric, and / or a mobile device. As an example, the PIF 110 may include a printed strip of material, facial recognition, fingerprint scanning, a mobile phone, a microchip (e.g., memory) or circuitry embedded in a card or bracelet, a pager, or a wireless device provided by the amusement park or owned by the guest. In fact, a particular mobile phone owned by the guest or obtained from the amusement park may be associated with a guest pass. The term guest pass generally refers to a guest's right to access some particular attraction or amusement park. For example, a guest pass does not necessarily have to be a tangible item. A guest can purchase a guest pass, which is then associated with the guest's identification (e.g., password, serial number, name, or numeric code) on the system 100 to verify the guest's identity and to verify the guest's rights. This association may be accomplished by a portable identification feature assignment system of the data server system 102. Thus, once a guest pass is associated with a PIF 110 assigned to a particular guest, the PIF 110 may then be used to verify the guest's entitlement via the system 100. Depending on this information, amusement park personnel or the system may grant or deny the guest access to or the right to make reservations at certain particular 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, the tracking system 112 may employ a device monitor 124 that tracks the PIF 110 within the park and identifies the location of a particular guest within a certain spatial range. The system 100 may further detect whether a guest has arrived within the park by monitoring the guest entry system 104 and detects whether a certain PIF 110 associated with the guest has been detected.This may include scanning a ticket, scanning a bar code from a screen of a portable device, pinging a portable device, etc. using the tracking system 112. Detection of a guest's entry into the park may be confirmed at the time of purchase of a guest pass and association with the PIF 110, for example, by scanning the ticket or by associating a mobile device identity with the guest pass.

[0014] As alluded to above, a guest (or a guest agent) may use the present embodiment to obtain reservations for one or more attractions to avoid or limit wait times in attraction queues, such as queue 126 for a particular ride 128. System 100 is designed to accommodate making, modifying, or accessing multiple reservations at once without slowing down the system and with enough processing power to ensure that adding additional capacity does not affect the speed of operation. Reservations through system 100 are obtained by guests remotely or within the 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. Automated telephone system 142 is accessible from and includes a network of telephones 150. The Internet system 144 is in communication with the Internet 152 and in some embodiments includes two separate websites, a first website that responds to guests' desires to make reservations and a second website that provides access to service personnel who perform administrative tasks in addition to making and revising reservations. The text messaging system 146 is in communication with a network of wireless devices 154 (e.g., cell phones). The POS device system 148 includes and / or communicates with a POS device 156.

[0015] The system 100 depicted in FIG. 1 is capable of communicating with a wide variety of types of wireless or mobile devices owned by guests or provided by the park. In practice, the PIF 110 includes a communication mechanism that allows all guests with reservations to receive messages and updates from the system 100. However, a mobile device may be used to communicate with the system 100 without using the mobile device as a PIF 100. As an example of a system communication, a text message may be sent from the text messaging system 146 to a mobile device functioning as a PIF 110 and assigned to a guest, the text message indicating that a particular reservation time has been pushed back due to technical issues with a particular attraction. The text messaging system 146 is capable of sending at least 20,000 automated text messages per minute related to postponement notices, informational notices, advertisements, etc. Various other components of the system 100 are also capable of wirelessly communicating with mobile devices or other wireless system components. For example, the data readers 108, POS devices 156, etc., may be wireless devices capable of communicating wirelessly with the data server system 102. The term mobile device suggests items that are easily carried by guests, such as cell phones, pagers, etc.

[0016] If a guest is requesting a reservation right from off-site as part of the reservation process, the guest is prompted by the system 100 (e.g., an interface module of the data server system 102) to provide the system 100 with an estimated time of arrival (e.g., morning or afternoon) at the park or an area such as a particular attraction 116 (e.g., a differentiated area of ​​the park). Such a request is received through an interface system of the data server system 102 capable of receiving communications and input data from guests (including current and potential park patrons). Such communications could be provided via one or more of an automated telephone system 142, an Internet system 144, a text messaging system 146, or a point-of-sale device system 148. A specific reservation is not established until the guest actually arrives. Rather, a reservation allotment system of the data server system 102 sets aside reservation slots based on estimated arrival times and correlates the reservation slots with guest identification information. Providing an estimated arrival time is required to establish reservation rights during the time period of the associated visit.

[0017] A detection system (e.g., tracking system 112, guest entry system 104, and / or data reader 108) determines whether the portable identification mechanism has arrived at a designated area (e.g., the amusement park). If the guest fails to arrive during the expected time period (e.g., during the morning hours), system 100 contacts the guest and reschedules or cancels the associated reservation rights based on guest feedback and / or other criteria. Similarly, once the guest is confirmed to be entering the amusement park, a reservation assignment system in data server system 102 determines a specific reservation time, and the guest is notified of the specific reservation time (e.g., a 15 minute window to arrive at the attraction 116). For example, a guest who has an existing reservation right or has requested a reservation will receive a text message or pre-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. As one particular example, upon checking in at a kiosk including the POS device 156, the guest will be notified via the POS device system 148 that a specific time for the reservation has been established by printing a message and reservation time on a receipt generated by the POS device 156. Similarly, communication from the system 100 may be provided via the automated telephone system 142, the Internet system 144, or the text messaging system 146 to the guest via a voice message, text message, or email sent to a mobile device and / or PIF 110 assigned to the guest (e.g., the guest's personal communication device or a device provided by the park). The specific time may be narrower than an approximate time, typically within the approximate time, but may be later.

[0018] Additionally, the system 100 in the illustrated embodiment facilitates communication from guests to the system 100. For example, a user may communicate that a reservation is no longer desired or that the guest's arrival at the park or an individual attraction 116 is likely to be delayed by submitting data to the system 100 via a mobile device including a PIF 110. This type of information would be used by the system 100 to manage reservations for that guest and other guests. Such information would also be used by the system 100 to facilitate queue management. For example, cancellations could be used to adjust the ratio of waiting queues, express queues, VIP queues, single ride queues, and reservation queues, or the number of guests allowed access via reservation entries. In practice, the system 100 would communicate such data to an attraction control system (e.g., attraction system 122) or park employees responsible for queue management. This would include providing an access control system or attraction system 122 in the data server system 102 with the ability to control adjustable ratio variables that adjust some particular queue characteristics (e.g., number of waiting line entries) relative to reserved entries so that a desired wait time is maintained, and the ability to provide information about nearby attractions with low wait times (e.g., lower wait times than the reserved queue or the nearest attraction with the lowest wait time).

[0019] Communications from guests to the system 100 may include periodic updates regarding the location of each of the PIFs 110 or updates entered by the guest via a data entry component of each of the PIFs 110. As an example, the PIFs 110 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 the PIFs 110. Specifically, for example, if the PIFs 110 are detected by a data reader 108 or scanned as part of a purchase detected by device monitors 124 located within the amusement park, such information can be employed to determine the general location of the guest with whom the system 100 has associated the PIFs 110. Guests could also submit requests or updates via a data entry mechanism (e.g., a keyboard or other interface of the PIFs 110). For example, the PIFs 110 may each include a keyboard or basic input that allows the guest to respond with an affirmative or negative response to questions posed by the system 100, such as questions regarding whether the guest intends to show up for a pending reservation, etc. Other mobile devices not employed as PIFs 110 could also be used to communicate with the system 100.

[0020] In addition to communications regarding reservations, communications between the system 100 and guests may include other types of information or data, such as information related to crowd flow through the park. For example, the system 100 may use location data from the PIF 110 or other sources to gather crowd flow data. This data may then be employed by the system 100 to encourage guest dispersion throughout the park and reduce crowds. For example, electronic coupons for nearby attractions, which may be restricted to certain guests by identification information, may be issued by the system 100 via the PIF 110, or announcements may be distributed indicating shorter wait times at certain attractions. The system 100 is capable of pushing information (e.g., coupons, advertisements, and wait times) to guests via a web portal or the like. Specifically, for example, the system 100 may be configured to deliver a text message to all supporters with PIFs 110 with a particular identification, allowing them to receive discounts at a concession stand or restaurant. The system 100 may also be configured to track the use of these discounts so that the system 100 knows the time and location of use and can use them for crowd control (submitting additional notifications based on purchase location, item purchased, etc.). Additionally, the system 100 may be configured to automatically adjust reservations based on location and availability. For example, a reservation may be adjusted because a supporter is located too far away from an associated attraction (as determined by the time of item purchase) to arrive at the attraction in time for the reservation, or a guest's position in line may be adjusted because the guest is delayed by slow service at a restaurant.

[0021] As with the other types of information discussed above, the system 100 can communicate crowd flow information between attractions 116 and dynamically adjust queue characteristics (e.g., admission ratios between reservations and waiting lines) to move toward optimizing guest wait times for attractions. For example, adjustments may be made based on the ratio of guests allowed into the souvenir shop 160 queuing from waiting line 162 (e.g., where guests line up to enter an attraction without a reservation) to guests allowed into the souvenir shop 160 from reservation line 164 (where guests line up to enter an attraction based on a reservation), remaining reservations for admission to the souvenir shop 160, and the availability of access to attractions throughout the amusement park. It should be noted that a guest entering the reservation line 164 has their right to enter the reservation line or queue 164 verified by accessing a PIF 110 associated with a data reader 108, and their access to enter the souvenir shop 160 verified by accessing a data reader PIF 110 associated with a different data reader 108. Thus, the data reader 108 is utilized as an entry access verification mechanism. This dual verification can be utilized to monitor queue wait times. Similarly, the data reader 108 can be employed as an access verification mechanism by verifying that the guest has entered the attraction (e.g., boarded an attraction ride vehicle).

[0022] The system 100 may also facilitate guest-to-guest and system-directed communications based on common characteristics of some particular guests. Specifically, the present embodiment may collect demographic data during a registration process or through an opt-in process. The registration process may include data entry requirements or some use of the system 100 by the guest that facilitates the acquisition of demographic data. For example, registration may include the guest's use of a mobile phone in conjunction with the system 100, and the demographic data acquired may include the area code of the phone number associated with the mobile phone. Direct guest-to-guest communications may be established through the system between PIFs 110 assigned to the guest, if the PIFs 110 have communication capabilities, or direct guest-to-guest communications may be established between communication devices provided by the guest or the park and known by the system 100. Similarly, such communications may be established through enabling access to social media, again employing PIFs 110 or known communication devices. Thus, guests who share common characteristics based on their registration data or selected options can provide notifications to one another. For example, guests from similar geographic areas can inform one another of activities that may be of common interest. Similarly, the system 100 can provide information about activities of common interest based on demographic data. The system 100 can facilitate posting status updates, notifying guests in a particular group of activities related to that group, or providing notifications of certain conditions within a part of the park, among other things.

[0023] In one embodiment of the present disclosure, a PIF 110 (e.g., an RFID transponder) is provided to each guest or group upon their entry into the park. This may include the park renting, leasing, or simply selling the PIF 110 to the guest. Each PIF 110 is programmed and assigned within the system 100 to uniquely identify each guest or group. In some embodiments, providing each guest with a PIF 110 includes instructing the system to recognize and / or communicate with a device owned by the guest, such that the device owned by the guest is adopted as a PIF 110 and activated by the system 100 as a PIF 100. For example, the system 100 may be used to download an application to the guest's mobile phone, such that the system 100 associates the guest's mobile phone with the park ticket and the guest (or group). In another embodiment, the system 100 is programmed to detect the PIF 110 and recognize its association with a valid guest pass. Also, as discussed above, different types of PIFs 110 include paper or plastic tickets or bracelets with integrated detection devices. For example, bracelets may include integral circuitry that stores a unique identifier in memory and / or 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 capture (AIDC) device such as an RFID tag may be used. Other mechanisms for the PIF 110 that may be used in accordance with the present embodiment include bar codes, magnetic strips, pin numbers, cell phone identifiers, hotel room keys, credit cards, combinations thereof, and the like. Any of the identification components of the PIF 110 or combinations of such devices may have a reciprocal reader that communicates with the data reader 108 or other guest identifiers (e.g., POS device 156) to track the guest's movements and / or activities in and / or around the theme park. This makes it possible to track crowd flows.Additionally, in some embodiments, the PIF 110 may include a handheld electronic device with a display screen capable of communicating crowd flow to facilitate directing guests to specific areas of a portion of the park.

[0024] In one embodiment, the system 100 is capable of controlling access and managing reservations for the attractions 116 by facilitating communication between the data server system 102, which acts as a central queue control system, and the guest entry system 104. In practice, the cooperation between the data server system 102 and the guest entry system 104 facilitates the identification of guests with reservations arriving and entering the park, thus assisting in the management of reservations. In practice, reservations may be modified or cancelled depending on an algorithm that takes into account arrival time at the park. The communication of guest arrival and / or entry may be achieved by the data server system 102 polling the guest entry system 104 at regular intervals (e.g., every 30 or 60 seconds) or at a particular time, or by sending identification data of the associated PIF 110 from the guest entry system 104 to the data server system 102 each time a guest enters the park via the guest entry system 104. For example, a data reader 108 associated with a particular attraction 116 may communicate with the data server system 102 or directly with the guest entry system 104 to verify that the guest has a valid ticket to enter the park. Specifically, for example, a guest may provide a PIF 110 assigned to the guest to the 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 verify that the PIF 110 is associated with a valid reservation and that the PIF 110 is known to have properly entered the park. This may include verifying that the PIF 110 (e.g., a cell phone) is identified (e.g., scanned upon entry) via the guest entry system 104 upon entry to the park and that the PIF 110 is associated with a reservation for the particular attraction 116 or any attraction 116.In some embodiments, a guest must use the PIF 110 to communicate with a first data reader 166 to enter the queue 164, and then use the PIF 110 to communicate with a second data reader 168 to enter the attraction 116. This facilitates monitoring of queue characteristics.

[0025] In one embodiment, the system 100 allows an individual or group to make reservations and access attractions during a range of times, modify reservations, delay reservations (e.g., delay reservations by 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 alluded to above, the system 100 includes numerous access or interface points capable of interfacing with a commercial management system for the park (e.g., a module of the data server system 102 or a separate system in communication with or accessible through the data server system 102). In practice, users can access or interface with the system 100 remotely or from the 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 accomplished using the PIF 110, which is used to communicate with the data server system 102. In practice, a guest may request to postpone a reservation (e.g., 30 minutes) or cancel a reservation because a meal took longer than expected by sending a text message from the PIF 110 or a communication device known to the system to the data server system 102. All interface points may be assigned the same capabilities depending on the available security. For example, if it is determined that there is a risk of losing financial data during a transaction due to limited security through an interface point, access from such an interface point may be limited. Also, access to the system 100 to obtain reservations may be limited depending on the purchase of access rights.For example, a guest may be required to purchase reservation ability in order to successfully make a reservation through system 100. However, the purchase price of reservation ability may be set to zero or the purchasing step may be bypassed. If the purchasing step is bypassed, the reservation acquisition step will function seamlessly with no indication of the required payment amount being provided. Note that in order to access system 100 and, as a precursor, to make a reservation that requires access to a particular area or attraction (e.g., an amusement park), a user is required to have already purchased a ticket for the attraction or set of attractions. In practice, access to make reservations within system 100 or to system 100 itself may be limited to users who own the corresponding ticket or to those with special access (e.g., theme park employees).

[0026] 2 and 3 include a process flow diagram for a procedure according to the present embodiment. The process is generally designated by the numeral 200 and includes various blocks representing acts or stages of the process 200. The process 200, according to the present embodiment, is controlled or facilitated by a system such as the data server system 120 or other components of the system 100. Indeed, in one embodiment, the data server system 102 includes a processor 118 and a memory 120 that stores instructions that are executed by the processor 118 to receive data inputs, manipulate associated data to convert the inputs into structured information, and provide outputs corresponding to the steps or acts of the process disclosed herein. The components of the process 200 may be performed by the data reader 108, which maintains its own data processing capabilities, or may be performed by other components of the system 100. Also, in different embodiments, some particular acts or stages may be performed in different orders.

[0027] As shown in FIG. 2, process 200 begins with a determination as to whether a ticket or tickets have already been purchased, as represented by block 202. In this context, a ticket is a right to access an amusement park or an attraction 116 at the amusement park. In other contexts, a ticket may be associated with different access rights. As an example, obtaining a ticket includes having a guest's identity associated with such rights within system 100. Specifically, for example, a guest may be assigned and provided with a guest identification number, and the system stores information in memory identifying the number that has the access right. If a ticket has not yet been purchased, process 200 facilitates the purchase of a ticket, as represented by block 204. According to the present embodiment, the purchase of the ticket or tickets is coordinated by a POS device system 148 (e.g., a ticket booth), by an Internet system 144, or by an automated telephone system 142. During the purchase, an attraction reservation capability is added to the purchased ticket or tickets, as represented by block 206. The ability to reserve an attraction is automatically added as a free component of a ticket in some embodiments. In other embodiments, the ability to reserve an attraction is a user-selected option that may be free or require an additional fee. The system 100 has the ability to give certain reservation priorities over other reservations. Priority may be given to guests who pay a premium, VIPs, or guests performing special tasks.

[0028] Block 206 further represents the actual addition of one or more attraction reservations at the time of the ticket or tickets purchase. In effect, block 208 represents prompting the guest to indicate whether a mobile device is available. If the guest does not have access to such a device, the guest is directed to obtain alternative communication capabilities (e.g., a personal communication device or a park-provided communication device), as represented by block 210. To facilitate this, the guest is directed to communicate with guest services, which will then arrange for the provision of a mobile device to the guest for the purpose of communicating information about the reservation and possibly acting as the PIF 110. If the guest does not wish to use such a mobile device, arrangements will be made for other types of notification and confirmation, such as via kiosks throughout the park and paper tickets. Returning to the prompt provided in block 208, if the guest has a mobile phone, a mobile communication device assigned by the park, or the like, the guest may indicate that such a device is available. In this event, the guest may be further prompted to provide access to the mobile device via a phone number, an email address, or the like, as represented by block 212. For example, the guest may provide a phone number that the system 100 may use for text or voice communications related to the attraction reservation. In fact, the guest may actually select the desired notification type, as represented by block 214. This includes selecting whether voice and / or text notifications are to be sent. The system 100 may prompt the guest to indicate whether text messages are acceptable. If the guest does not wish to use text, an automated voice message is used. Block 214 also represents a step of allowing the guest to decide whether some particular type of information is to be sent to the mobile device.For example, a guest may limit communications to those related to an established reservation so that the guest does not receive information related to coupons, wait times in other areas of the park, etc. In some embodiments, certain types of information are accessed, received, or controlled based on the pricing tier of the access rights purchased. For example, guests 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 they would not otherwise be able to block.

[0029] Once a method of communication between the system 100 and the guest has been established, the 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 of the reservation. In some embodiments, only one attraction and / or reservation date may be available for a reservation, and thus an attraction and / or date need not be selected. This embodiment allows a user to make a reservation prior to entering the park to confirm access to a particular attraction; however, the specific time of the reservation cannot be booked until the guest is actually inside the park. In practice, for example, the specific time of the reservation cannot be booked until the ticket associated with the reservation has been identified by the guest entry system 104.

[0030] In the illustrated embodiment, the guest is requested by the system 100 to provide an approximate reservation time to aid in scheduling the reservation, as indicated in block 216. As previously noted, the actual reservation time is not established until certain criteria are met. For example, a particular time window for the reservation (e.g., a 15 minute time window) may not be established until the reserving guest has confirmed entry into the park and confirmed that a reservation is still desired. The approximate reservation time may be indicated as morning, afternoon, or evening. In another embodiment, the approximate reservation time may be one of various time windows (e.g., a 4 hour time window) that the guest may select. The indication of the approximate time allows for flexibility within the reservation system 100. For example, if the guest indicates morning of a particular day as the approximate reservation time, a determination may be made as to whether the guest actually arrives at the park by a particular time in the morning. If the guest has not arrived, the guest is contacted via a mobile device including the PIF 110 to determine whether an adjustment to the reservation or a cancellation should be made. Certain adjustments to the reservation or a cancellation may be made automatically if the guest does not arrive within the indicated time window, if the guest fails to respond via the mobile device, if the guest provides some kind of update (e.g., "I'm an hour late"), etc. In one particular example, if the guest does not arrive by the time corresponding to the time set as the approximate time of the reservation, the guest is prompted to indicate whether he or she still plans to visit the park. If the guest still plans to visit the park, the reservation is adjusted. If the guest is no longer planning to visit the park, the reservation is canceled. If the reservation is adjusted, other reservations will be moved around. Also, if the reservation is canceled, other reservations will be moved around and those in the alternate list will be contacted to fill the reservation slot that has become available.

[0031] The system 100 allows for multiple reservations to be made at one time. In one embodiment, when multiple reservations are made, they are first associated with a single ticket or multiple tickets respectively. In effect, in addition to receiving other information provided in block 216, block 218 represents receiving an indication of the number of guests for the requested reservation. By allowing multiple reservations to be associated with a single ticket, it allows one group member to make a reservation for a group of guests. However, reservations for more than a certain number of guests (e.g., 10 guests) may require acceptance from amusement park personnel (e.g., a member of the group sales department). Thus, block 218 represents receiving input regarding the number of guests wishing to make a reservation, which may include indicating that the reservation is for a single guest. A determination is then made as to whether the reservation is for a group greater than a certain threshold, as represented by block 220. If the group exceeds the threshold, the guest is prompted to contact a group sales representative for the amusement park, etc., as represented by block 222. This may include automatically connecting the guest to the appropriate contact via phone or automatically initiating an email to the appropriate contact.

[0032] If the group does not exceed a threshold defined for a group reservation (e.g., the reservation is for a single guest), the process 200 proceeds to determine whether the attraction for which the reservation is being requested has sufficient capacity, as indicated by block 224. In one embodiment, this action may include 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 regarding reservation times, availability, out-of-service times, etc. In other embodiments, all of this information is centrally located (e.g., stored on the data server system 102). If a determination is made that there is sufficient capacity for the requested reservation or reservations, a confirmation of the reservation or reservations may be provided to the guest and the reservation may be booked, as represented by block 226, and the reservation may be booked in the data server system 102 and / or the management system or attraction system 122 for the particular attraction 116 for which the reservation was made. For example, the 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, the confirmation is simply provided via the device employed to make the reservation.

[0033] If a determination is made that there is insufficient capacity to accommodate the requested reservation, the process prompts the guest to select a different date, a different time period, or a different attraction, as represented by block 228. In some embodiments, if a reduced or split group size may allow for a reservation, the guest may be notified of the option to split the group or reduce the group size to obtain an available reservation slot. If the guest chooses to make the change to the requested reservation, the process returns to block 216. If the guest chooses not to revise the request, the guest is prompted to select whether they wish to be placed on the reserve list (a queue to fill slots as they become available) or to cancel the reservation request, as represented by block 229. The prompt at block 229 may make it clear that not choosing to be placed on the reserve list will result in cancellation. If an option is selected, the requested reservation is placed on the reserve list, as represented by block 230. In fact, this embodiment includes a waiting list feature whereby when a reservation is not available, the guest can obtain a place on the waiting list to be notified of a likely available reservation slot. Once the guest or group has been assigned a place on the reserve list, the guest is notified that the reservation was not booked, but that the guest and / or group has been assigned a slot on the reserve list, as represented by block 232. If the guest chooses to cancel, the reservation request is simply canceled and the guest is notified, as represented by block 234. As with the reservation confirmation discussed above, notification may be accomplished by submitting a text message or voicemail to the mobile device or by communicating via the device employed to request the reservation. Additionally, once a reservation opening becomes available, the guest or group will be notified of the opening via the mobile device or via other notification mechanisms.Guests are requested to respond to such notifications by indicating whether they are available to fill the slot. The guest may respond via the PIF 110 assigned to the guest. If the guest indicates availability to take the available reservation slot, the waiting list reservation is moved to the available reservation slot.

[0034] Returning to block 202 of process 200, if tickets have already been purchased, process 200 is directed to contacting reservation system 100, as represented by block 250 of FIG. 3. Upon accessing the reservation system, the guest is prompted to verify the identity of the guest or group, as represented by block 252. This may include entering a confirmation number, scanning a physical ticket, accessing an application on a mobile device, etc. A determination is then made as to whether the identification corresponds to a currently valid or active guest pass, as represented by block 254. If the identification does not correspond to a valid guest pass, the process directs the user to guest services, as represented by block 256. This may include automatically connecting the guest to park personnel via telephone or automatically generating an email to park personnel.

[0035] If the system 100 determines that the identification information corresponds to a valid guest pass, a determination is made as to whether the guest has previously associated the guest pass with a mobile device. If a mobile device has not been associated with the guest, the process 200 proceeds to block 258, which represents determining whether such a device is available. Many of the steps that follow are essentially equivalent to those indicated and described in connection with FIG. 2. Specifically, block 258 represents prompting the guest to indicate whether a mobile device is available. If the guest does not have access to such a mobile device, the guest is directed to guest services, as represented by block 260. Guest services will then arrange for communication capabilities for the guest, for example, by providing the guest with a mobile device for purposes of communicating information about the reservation. If the guest does not wish to use such a mobile device, arrangements will be made for notification, such as via kiosks throughout the park.

[0036] Returning to the prompt provided in block 258, if the guest has a mobile phone, a mobile communication device assigned by the park, or the like, the guest may indicate that such a mobile device is available. In this event, the guest may be further prompted to provide access to the mobile device, as represented by block 262, and then such access by way of a phone number, an email address, or the like. For example, the guest may provide a phone number that the system 100 uses for text or voice communications related to the attraction reservation. In fact, the guest may currently select a notification type, as represented by block 264. This may include selecting whether voice and / or text notifications are sent. The system 100 may prompt the guest to indicate whether a text message is acceptable. If the guest does not wish to use text, an automated voice message would be used. Similarly, email may be provided as an option. Block 264 also represents a step of allowing the guest to decide whether some particular type of information is to be sent to the mobile device. For example, the guest may limit communications to those related to reservations so that the guest does not receive communications related to coupons, wait times in other areas of the park, etc. Note that if the mobile device was already identified in block 254, process 200 can proceed directly to block 264 or block 266.

[0037] Once a method of communication between the system 100 and the guest has been established, the process 200 proceeds to establish the details of the reservation. As represented by block 266, this may include selecting an attraction, a reservation date, and an approximate time of the reservation. In some embodiments, only one attraction may be available for the reservation, and thus an attraction need not be selected. As noted above, the present embodiment allows a user to make a reservation prior to entering the park to confirm access to a particular attraction. However, the specific time of the reservation is not entered by the system 100 or provided to the guest until the guest actually enters the park. In practice, for example, the specific time of the reservation cannot be entered until the ticket associated with the reservation has been identified by the guest entry system 104.

[0038] As indicated by block 266, an approximate time of the reservation (e.g., morning or afternoon) is requested by the system 100 to aid in the organization of the reservation. The approximate time of the reservation may be indicated as morning, afternoon, or evening. In another embodiment, the approximate time of the reservation may be one of various time windows that the guest may select. The indication of the approximate time allows flexibility within the reservation system 100. If the guest does not arrive by the time corresponding to the indicated approximate time, the guest is contacted, such as via a mobile device, to determine whether an adjustment to the reservation or a cancellation should be made. Certain adjustments to the reservation or a cancellation may be made automatically if the guest does not arrive within the indicated time window, if the guest fails to respond via a mobile device, if the guest provides some kind of update, etc. When a reservation is adjusted, other reservations will be moved around. Also, when a reservation is canceled, other reservations will be moved around and people on the reserve list will be contacted to fill the reservation slot that has become available.

[0039] As with the ticket purchase shown in FIG. 2, the system 100 allows multiple reservations to be made for tickets that have already been purchased. Indeed, in one embodiment, when multiple reservations are made, they are first associated with a single ticket or with each of the multiple tickets. Allowing multiple reservations to be associated with a single ticket allows one group member to make a reservation for a group of guests. However, reservations for more than a certain number of guests may require acceptance from park personnel. Thus, block 268 represents the step of inputting the number of guests for whom a reservation is desired, which may include indicating that the reservation is for a single guest. Next, as represented by block 270, a determination is made as to whether the reservation is for a group larger than a certain threshold. If the group exceeds the threshold, the guest is directed to contact, such as a group sales representative for the park, as represented by block 272. This may include automatically connecting the guest to the appropriate contact via phone or automatically initiating an e-mail to the appropriate contact.

[0040] If the group size is within the threshold, a determination is made regarding attraction capacity, as represented by block 276. If a determination is made that there is insufficient capacity to accommodate the requested reservation, process 200 includes prompting the guest to select a different date, a different time period, or a different attraction, as represented by block 278. In some embodiments, if a reduced or split group size would allow a reservation, the guest may be notified of the option to split the group or reduce the group size to obtain an available reservation slot. If the guest chooses to make changes to the requested reservation, the process returns to block 266. If the guest chooses not to revise the request and does not cancel the request, the requested reservation will be placed on a waiting list, as represented by block 280. In fact, this embodiment includes a waiting list feature such that when a reservation is not available, the guest may obtain a place on a waiting list to be notified of potential available reservation slots. Once the guest or group has been assigned a position on the alternate list, the guest is notified, as represented by block 282, that the reservation was not booked, and that the guest and / or group has been assigned a slot on the alternate list.

[0041] If a determination is made that there is sufficient capacity for the requested reservation or reservations, then a determination is made as to whether the guest or guests have already accessed the attraction within the time period (e.g., on the day of the requested reservation, within the morning hours, etc.), as indicated by block 290. If the guest has previously experienced the attraction with the time designation, then a determination is made in block 292 as to whether a threshold amount of access has been reached (e.g., whether the guest or guests or group have experienced the attraction three times on the same day). Such a determination may be made by an access management mechanism (e.g., the system of data server system 102 or system 122). If there are no or no restrictions on accessing the attraction, then a confirmation of the reservation or reservations will be provided to the guest or group, as represented by block 294, and the reservation will be booked in the data server system 100 and / or management system 122 for the particular attraction 116 for which the reservation has been made. However, future access to the attraction may be restricted based on previous access. If a guest has a limit on the number of times they can access an attraction within a time period and that limit has been reached, access for further reservations is denied and the guest is placed on a waiting list, as indicated by block 280. For example, the confirmation may include a text or voice message sent from the data server system 102 to the mobile device via the Internet system 144, the phone system 142, the text system 146, or the POS device system 148.

[0042] 4 is a process flow diagram of a method employing the system 100 according to the present embodiment. The process is generally designated by the numeral 400 and includes various blocks representing acts or stages of the process 400. The process 400 is controlled or facilitated by a system such as the data server system 102 or other components of the system 100 according to the present embodiment. Indeed, in one embodiment, the data server system 102 includes a processor 118 and a memory 120 that stores instructions that are executed by the processor 118 to receive inputs and provide outputs corresponding to the steps or acts 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 particular acts or stages may be performed in different orders.

[0043] Inputs from guests to the system 100 (before or during the visit) may include ticket identification, mobile phone number, reservation due date, reservation group size, estimated park entry time (e.g., morning or afternoon), associated ticket identification (e.g., group ticket information), etc. Inputs from operators to the system 100 may include data indicating ride capacity, outage time estimates, attraction operating status, re-boarding status, queue ratios, messages, advertisements, statistics, and data requests. Automatic inputs may include the time the guest enters the park, the time the guest enters the queue, the time the guest leaves the queue, wait time estimates, and valid ticket confirmation. Outputs from the system 100 to various systems (e.g., websites, mobile sites, text messaging systems, phones, and POS devices) may include reservation capacity check results, general messaging, advertisements, available reservation due dates, and reservation confirmations. Outputs from the system 100 to operators may include allowed ride queue entry messages and reservation acceptance messages. Outputs from the system 100 to guests may include status updates, reservation modification messages, reservation window messages, time limit warnings, active time window messages, guest thank you messages, reservation confirmations, reservation updates, general messaging, advertisements, entry messages, etc. In different embodiments, some particular inputs and outputs may be directed to different components.

[0044] The process 400 begins with verifying that a guest has the appropriate access rights, as represented by block 402, and admitting the guest to the amusement park if the access rights are verified. This may involve the use of the guest entry system 104. The access rights are verified by determining that the guest has provided identification information (e.g., a barcode on a physical ticket or a date stored on a mobile device) that corresponds to a valid right to access the amusement park. For example, this may include scanning the ticket provided by the guest and verifying that the information retrieved from the ticket is stored in the central database as corresponding to a right to enter on the date being scanned. In practice, such information may be stored in the central database 102 and issued to the guest electronically or 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 represented by block 404. If a reservation is not associated with the identification information, the guest may use the waiting line to access the attraction, may join a group that has a group reservation, or may obtain a reservation, as represented by block 406. For example, if the guest did not establish a reservation prior to arriving at the park, the guest may 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 represented by block 408. In practice, once the guest is identified as entering the park, as occurs in block 402, 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 will allow the reservation to be accessed), and the guest is provided with a notification of the reservation (e.g., a voice message, text message, or email) via a mobile device, etc., as represented in block 410. In one specific example, when requesting a reservation, the guest may provide a broad time window, such as "during morning operating hours," "during afternoon operating hours," "during night operating hours," "between 1:00 PM and 6:00 PM," "between 7:00 AM and noon," etc. Upon confirming the guest's entry into the park, confirming that the guest is in a particular area, or upon the guest's check-in, the system 100 assigns a specific time for the reservation, such as a time window from 2:00 PM to 2:15 PM, or approximately 3:00 PM. This may occur automatically when certain criteria are met. For example, if a guest does not arrive within a predefined time frame (e.g., morning or afternoon), the availability of the reservation may change. As another example, an attraction may be unavailable due to technical failure.Any problems with the reservation may be communicated to the guest in the same manner that the reservation confirmation is communicated.

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

[0047] Once all handoffs have been made, a determination is made regarding any associated delays or other problems, as indicated by block 422. This may include periodic updates and continuous monitoring of attraction information from a monitoring system (e.g., attractions system 122) associated with the relevant attraction. If a problem is identified that may cause a change in the reservation, the guest is notified of the new time window for the reservation via text message, voice message, email, or kiosk display, as represented 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 guest may be prompted to define the desired outcome from a selection of available options.

[0048] If no issues are identified with respect to the reservation change, process 400 continues to monitor whether the pre-reservation time period has been reached, as represented by block 430. For example, block 430 may represent a determination as to 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 guest will be provided with a reminder that the reservation time is approaching, as represented by block 432. This may include a suggestion that the guest begin traveling toward the attraction. Note that the time period before the guest is notified may vary depending on the guest's location. For example, if system 100 identifies that the guest is in a particular location where it typically takes a certain amount of time to travel to the attraction for which the guest has 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 the reservation reminder notification, the system 100 may allow the guest to move or postpone the reservation. For example, the guest may be prompted or allowed to request a postponement of the reservation, as indicated by block 434. If the guest chooses to postpone the reservation, the guest notifies the reservation system 100 via a mobile device or other access point to the reservation system 100, as indicated by block 436. The reservation system 100 may respond to such a request with information regarding a new reservation for a later time, a selection of available reservation times at the later time, or an indication that the later time is not available. The system 100 may then allow the guest to respond, for example, by confirming or selecting the provided later time or by declining to change the existing reservation. If a new reservation is established, the 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, a guest may choose to cancel their reservation in addition to modifying the reservation.

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

[0051] Once an initial verification of guest identification and reservation information (e.g., ticket scanning) is performed at the entrance to the queue, further verification is required prior to actual entry to the attraction, as represented by block 448. This can facilitate monitoring of queue lengths at the associated attraction. Future projections of access provided to reservations and waiting queues can be adjusted based on this measurement to control waiting time in reservation queues. For example, during steady state operation, the present embodiment may control the approximate time a guest spends in a reservation queue to be around 10 minutes. In practice, the system 100 commands the operator to allow guests to exit the queue and board the attraction at a specified interval based on an algorithm that takes into account queue characteristics. Verifying a guest's identification to board a ride (e.g., scanning a ticket and accessing associated reservation data) can also facilitate monitoring and control of subsequent access to the attraction. For example, this can be used to indicate that a guest has already accessed a particular attraction using a reservation. The instructions are stored in the system 100 and associated with the identification information so that future reservation requests can be controlled based on whether some particular attraction has already been accessed by the guest, which may include scanning the ticket after the guest exits the attraction, etc.

[0052] System 100 may employ algorithms that take into account that some particular guests may have accessed an attraction just before the attraction experienced a technical failure that prevented it from operating. For example, block 452 represents a step of determining whether a guest checked into the attraction but did not experience the attraction due to a technical failure or the like. If the attraction was functional, the guest is indicated as having experienced the attraction, as represented by block 454. If the attraction was not functional, the guest is automatically assigned another reservation or the right to access the attraction as soon as the technical failure or the like is resolved, as represented by block 456. If access to the attraction is prevented or the experience of the attraction is interrupted, the attraction is considered not functional.

[0053] The present embodiment seeks to enable reservation transactions through a reservation transaction system, which may be a component or module of the data server system 102. This functionality would be utilized when the system 100 is used in conjunction with multiple attractions. For example, a first guest has a reservation to access a first ride at 1:00 PM. However, the first guest is going to have lunch and is unlikely to be able to arrive at the attraction in time for the reservation. The system prompts the first guest at a certain time prior to the reservation (e.g., 15 minutes) to decide whether the first guest intends to keep the reservation. The time of the prompt may be based on the guest's detected location relative to the attraction 116 where the reservation is established. Because the first guest is unable to arrive at the first attraction in time, the first guest responds by indicating that he or she does not intend to keep the reservation. The system 100 then automatically searches for a later reservation for the first guest. Assume that a second guest has a reservation for 4:00 PM and is currently located near the first attraction as determined by the system 100. Once the system 100 identifies this second guest based on location and reservation time, it sends a message to the second guest indicating that a transaction is available for the reservation held by the first guest. If the second guest accepts the transaction, the reservation is transferred by the system 100 between the first and second guest, and each guest will be notified of their new reservation. This helps maintain full capacity while eliminating the stress for guests associated with getting appointments on time.

[0054] The present embodiment includes processes and systems configured to provide multiple reservations or itineraries to each of multiple different guests or groups based on input from the guests. For example, FIG. 5 is a process flow diagram providing a general overview of a process 600 for facilitating a guest to schedule multiple reservations for attractions ranging from rides to restaurants, according to the present embodiment. The process 600 of FIG. 5 generally illustrates the steps of establishing an itinerary that substantially optimizes a guest's time within the park and park facilities. It should be noted that the process 600 is illustrated at a high level and may include certain process features discussed above with respect to FIGS. 2-4. Additionally, the process 600 may be implemented using all or some of the features of the system 100 discussed above.

[0055] Process 600 begins by allowing a guest to communicate with a reservation system to provide certain attraction preferences, as represented by block 602. This may include providing access to the reservation system for guests inside or outside the park. For example, a guest may provide a list of certain attractions that the guest is interested in experiencing or a list of types of attractions that the guest is interested in experiencing. This may include providing specific attractions and associated reservation time preferences along with a ranking indicating the level of interest for each attraction. Alternatively, a guest may simply provide a list of attractions that interest them and have the system provide times. Similarly, a guest may simply provide certain types of attractions (e.g., rides suitable for small children) and have the system provide an itinerary. Once the preferences are entered, the reservation system receives the associated data, as represented by block 604, and the process then processes the data, as represented by block 606, to substantially optimize schedules for each guest and optimize utilization of the park attractions. In response to the preferences provided by the guest, the reservation system performs an optimization algorithm and outputs a proposed itinerary, as represented by block 608. In one embodiment, the guest may provide inputs prior to entering the park, but does not receive the proposed itinerary until after entering the park.

[0056] The algorithm represented as being performed at block 606 may be stored in memory and may be performed by a processor of the system (processor 118 of data server system 102) to generate a proposed itinerary as represented by block 608. The guest may then confirm the itinerary as represented by block 610 or request a different itinerary after reviewing the proposed itinerary. If confirmation is received by the system, the process provides the confirmed itinerary as represented by block 612. If the guest chooses to modify the itinerary, the guest is prompted to indicate whether specific modifications are required or whether cancellation is desired. If cancellation is desired, the process ends and cancellation is confirmed as represented by block 616. If modifications are desired, the process returns to block 604 and / or allows changes to be made to the schedule. It should be noted that at any point in process 600, the system may provide suggested modifications based on the optimization data, attraction availability, and perceived limitations of the guest's preferred schedule.

[0057] The algorithm depicted as being performed at block 606 may function to identify the locations of attractions listed as being of interest to a guest and determine a schedule based on a number of factors or optimization data, such as ease of transition between individual attractions of interest. For example, the system may present an itinerary that includes reservations for the guest's favorite attractions in a sequence that allows the guest to travel throughout the park from attraction to attraction without having to retrace their steps. The itinerary may further include reservations for attractions along the proposed route based on gaps in the schedule. In addition to taking into account distance and location of attractions, the algorithm may also consider maximizing park operational efficiency, reservations by others, interest levels, meal times, schedule overlaps with other guests identified as being in a common group (e.g., social network), and so forth. For example, the optimization algorithm may present an itinerary that limits travel between attractions, but also accommodates the lack of availability of reservations at certain times for highly sought-after attractions. The algorithm may also be adapted to guide guests throughout the park to avoid anticipated overcrowding in certain areas based on established reservations and historic park data. The algorithm may also take into account that rest breaks may be needed around meal times and suggest reservations for restaurant attractions or simply recommend nearby restaurants. The algorithm may also be adapted to take into account certain practical considerations. For example, the algorithm may adjust the itinerary so that some highly strenuous attractions are omitted for certain times after meals. The algorithm may also be adapted to maximize utilization of the park by suggesting reservations or visits to underutilized attractions at certain times.In one embodiment, the algorithm considers the ranking of the level of interest (e.g., high, medium, low) provided by the guest for the attractions and provides an itinerary that takes this into account. For example, the algorithm may arrange for reservations for high interest attractions to be spread out throughout the day to ensure interest is sustained throughout the day, or all to occur early in the day to ensure that all of the high interest attractions are experienced early.

[0058] The present embodiment also facilitates on-site rendezvous for groups that arrive separately, disperse once inside the park, or desire some overlap in scheduling. For example, FIG. 6 illustrates a process 700 performed by the present embodiment for arranging guest schedules. The process begins by prompting the guest to indicate whether they wish to join a group of which they are already a member or whether they wish to have an itinerary that overlaps with another group's itinerary. This initial procedure is represented by block 702 and may be performed using any of the access mechanisms discussed above in connection with system 100, such as a cell phone associated with system 100. Block 702 includes identifying the guest and the group.

[0059] If the guest wishes to meet with a group or organization of which the guest is a member, the process may identify a meeting location, as represented by block 704, and direct the guest to the location and / or instruct the organization to meet the guest at the location, as represented by block 706. This will generally occur if the guest has not arrived at the park with their organization or has split off from their organization during their visit. To facilitate group reunion, the present embodiment may utilize PIF positioning information to direct the guest to the desired organization, provide the meeting location using an established itinerary for the organization, communicate the meeting location using guest-to-guest communications, and / or communicate the meeting location using system-to-guest communications. For example, the next attraction on the itinerary will be provided to the guest and the organization will be informed via text message that the guest will join the organization at a reservation for the next attraction. Guest-to-guest communication may also be facilitated between groups and guests via the reservation system (eg, text messaging or voice communication).

[0060] If the guest wishes to establish an overlap between the guest or group or entity of guests and at least one other entity, process 700 proceeds to block 710 in the illustrated embodiment. This occurs when two or more groups or individuals decide to spend time together at the park. For example, groups from a particular area may decide to establish overlapping schedules so that they can experience attractions of common interest together while also experiencing other attractions with their separate groups. The groups or individuals may or may not already have reservations (e.g., itineraries). Block 710 generally represents a step of identifying groups or individuals and confirming a desire to have an overlapping attraction experience. Once this is established, a determination is made as to whether one or more groups have an existing itinerary or reservation, and a preference is provided if no itinerary or reservation has been established, as represented in block 712. Existing itineraries and reservations are taken into account, and preferences are provided otherwise. This may include providing attractions of common interest and desired overlap. Then, as represented by block 714, an algorithm is run based on guest common interests, preference comparisons, existing itinerary comparisons, and / or optimization data based on the explicit specifications to provide overlapping itineraries for two or more individual guests or groups of two or more guests.

[0061] Although only certain features of the invention have been shown and described herein, numerous modifications and changes will occur to those skilled in the art, and it is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.

Claims

1. a data server system including at least one processor and a memory; an interface system of the data server system configured to receive a reservation request including an indication of an approximate time period for a guest's arrival at an area of ​​the park; a reservation rights allocation system of said data server system configured to correlate reservation slots for accessing an attraction with said guest identification information; a detection system of said data server system configured to determine when a portable identification mechanism associated with said identification information arrives in said area; a reservation allocation system of the data server system configured to establish reservations for access to the attraction for a particular time window. Queue management system.

2. The queue management system of claim 1 , wherein the reservation allocation system is configured to correlate the reservation slot with the identification information based on the indication of the approximate time period of arrival of the guest at the area.

3. The queue management system of claim 1 , wherein the specific time window is narrower than the general time period.

4. The queue management system of claim 1 , wherein the interface system is configured to receive the reservation request via a telephone system, an Internet system, a text messaging system, or a point-of-sale device system.

5. The queue management system of claim 1 , comprising a portable identification mechanism assignment system configured to associate said identification information with said portable identification mechanism.

6. The queue management system of claim 1 , wherein the portable identification mechanism is a mobile phone, a pager, a portable computer, a card, or a wearable mechanism including an integrated circuit.

7. 7. The queue management system of claim 6, wherein the portable identification mechanism comprises a bracelet containing the integrated circuitry that stores the identification information and enables location detection of the portable identification mechanism.

8. 2. The queue management system of claim 1, wherein the portable identification mechanism is guest biometric data registered with the detection system.

9. 2. The queue management system of claim 1, comprising a guest entry system configured to detect the portable identification mechanism during entry through a main gate and communicate the detected entry to the detection system, or a location monitor configured to detect a location of the portable identification mechanism within a spatial range and communicate the location to the detection system.

10. 2. The queue management system of claim 1, comprising at least one data reader configured to interface with the portable identification mechanism and to communicate with the data server system to determine rights associated with the portable identification mechanism.

11. The queue management system of claim 10, wherein the at least one data reader is configured to read a memory of the portable identification mechanism.

12. The queue management system of claim 1 , wherein the queue management system comprises the portable identification mechanism, the portable identification mechanism configured to interface with the reservation allocation system to modify the reservation.

13. 2. A queue management system as claimed in claim 1, comprising at least one access verification mechanism configured to detect the portable identification mechanism upon entry to the attraction and / or upon entry into a queue for the attraction.

14. The queue management system of claim 1 , further comprising an access validation mechanism configured to detect the portable identification mechanism upon exiting the attraction.

15. 2. The queue management system of claim 1, comprising an access management mechanism configured to determine a number of times the portable identification mechanism has been used to access an attraction, and to limit or allow subsequent access to the attraction using the portable identification mechanism based on the number and a threshold for repeat access.

16. 2. The queue management system of claim 1, comprising an access control mechanism configured to adjust the ratio of guests allowed through a waiting line to a reservation queue based on monitoring the portable identification mechanism.

17. 2. The queue management system of claim 1, comprising a reservation transaction system configured to facilitate electronic trading of reservations for different reservations assigned to different portable identification mechanisms.

18. 20. The queue management system of claim 17, wherein the reservation transaction system is configured to be interacted with externally by guests or internally by operations managers.

19. 20. The queue management system of claim 17, wherein the portable identification mechanism interfaces with the reservation transaction system.

20. The queue management system of claim 1 , comprising an attraction system configured to monitor the status of the attraction and / or characteristics of a queue associated with the attraction and to communicate corresponding data to the data server system.

21. receiving identification information of the guest at a data server system; storing said identification information in a memory of said data server system; receiving, at said data server system, a reservation request for a guest including an approximate time period of arrival of the guest at an area of ​​the park; assigning the identification information of the guest to a portable identification mechanism; allocating slots for reservation based on said general time periods; monitoring the zone to determine if the portable identification mechanism has entered the zone and an associated time of entry; assigning said reservation to said identification information and allocating a specific time for said reservation when said portable identification mechanism is detected within said area; A method comprising:

22. 22. The method of claim 21, comprising receiving a plurality of reservation requests and generating an itinerary based on the plurality of reservations, location information, and attraction availability.

23. 22. A method according to claim 21, comprising the step of sending a message from said data server system to the holder of said portable identification mechanism after said step of assigning said specific time, said message including confirmation of said specific time.

24. 24. The method of claim 23, wherein the message is sent via a telephone system, a text messaging system, an Internet system, or a point-of-sale device system.

25. 22. The method of claim 21, comprising receiving data from the portable identification mechanism via a data reader into the data server system, and modifying the reservation based on the data.

26. 26. The method of claim 25, comprising establishing the data using a tracking system, the data including a location of the portable identification mechanism.

27. 27. The method of claim 26, including transmitting information to the guest or other guests based on the location of the portable identification mechanism.

28. 22. The method of claim 21, comprising receiving a text message into the data server system and modifying the reservation based on the text message, the text message being from the portable identification mechanism or a communication device associated with the guest.

29. 26. The method of claim 25, including modifying the reservation by transacting the reservation for a different reservation associated with a different portable identification mechanism, wherein the modifying the reservation by transacting upon notice or consent from a different guest associated with the different portable identification device.

30. A system comprising a data server system, The data server system includes a processor circuit configuration, the processor circuit configuration comprising: receiving data from a data reader based on detection of a portable identification mechanism, the data including a location of the portable identification mechanism or data utilized by the processor circuitry to determine a location of the portable identification mechanism; Identifying a correlation between the portable identification mechanism and a guest's identity; Identifying reservation information associated with the identification information; and modifying said reservation information based on said data received from said data reader by providing specific time slots for reservations at least within a predefined approximate time period of expected arrival at a certain area; The system is configured as follows.

31. 31. The system of claim 30, wherein the system comprises the data reader, the data reader configured to perform facial recognition to detect the portable identification mechanism.

32. receiving attraction preference data into a reservation system, the attraction preference data including a plurality of attractions of interest to at least one user; analyzing the attraction preference data using an algorithm performed by a processor of the reservation system, the algorithm being configured to perform an analysis based on attraction availability data, location data associated with the attraction preference data, and park occupancy data; generating a proposed timeline based on the analyzing step; The method includes:

33. receiving a request into a reservation system to join a member to a group or to create a schedule overlap between guests; Upon a member joining the group, using a processor of the reservation system to identify a meeting location and direct the member or group to the location based on detecting the location of the group via accessing a portable identification mechanism associated with the group or based on determining the next attraction scheduled on the group's itinerary; or when generating schedule overlaps between guests, using the processor of the reservation system to identify existing itineraries or reservations of the guests, receive preferences, and generate overlapping itineraries based on common interests identified by the existing itineraries and / or the preferences; The method includes:

Citation Information

Patent Citations

  • System and method for reservation management and program making computer implement the method

    JP2003288515A

  • Model course distribution system and method

    JP2006134260A

  • Electronic ticket transfer system

    JP2006318340A

  • Electronic-ticket transfer system and electronic-ticket transfer method

    US20090030744A1

Cited By

  • Information processing device, information processing method, and program

    JP2026149052A

  • Information processing device, information processing method, and program

    JP7760782B1