Customer-oriented game information management system and method

By designing a registration system in the amusement park, and using the database and controller to send and verify pre-check documents, efficient registration and verification are achieved before attending, solving the problem of low experience efficiency and improving the experience efficiency of the amusement park.

CN118974749APending Publication Date: 2024-11-15UNIVERSAL CITY STUDIOS LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380031406.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-29
Filing Date
2023-03-28
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

In the amusement park, it takes time to complete the pre-check document and employee confirmation process, which affects the experience efficiency and spends time enjoying the experience before the experience.

Method used

A registration system is designed, including a database and a controller, to receive customer requests through an amusement park application, send and verify pre-check documents, and provide admission codes to indicate the verified status, so as to achieve efficient registration and verification before attendance.

Benefits of technology

Reduces the time to complete the pre-checking process before the experience, improves the efficiency of the amusement park experience, and avoids delays caused by document review and queue waiting.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118974749A_ABST
    Figure CN118974749A_ABST
Patent Text Reader

Abstract

A registration system includes an amusement park spot associated with a registration process. The registration system also includes a database and a controller. A database stores data indicating availability of an amusement park spot. The controller receives a request from a customer to attend an amusement park spot. In response to the request, the controller sends one or more forms, one or more exempts, or both to the customer. After completion, the controller also receives one or more forms, one or more exempts, or both. Further, the controller verifies the one or more forms, the one or more exempts, or both as compliance to the amusement park spot. Further, in response to determining compliance, the controller sends an admission code to the customer, the admission code indicating the verified status.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] The present disclosure generally relates to the field of amusement parks. In particular, embodiments of the present disclosure relate to techniques for efficiently registering patrons attending an amusement park experience.

[0002] In some entertainment environments (such as amusement parks), customers may attend an amusement park experience. For example, an experience may include special events (e.g., seasonal events), rides, festivals, etc. Typically, an experience may be associated with a document (such as a pre-verification document) to be completed before attending the experience. The pre-verification document may include one or more waivers, consent forms, information forms, etc. The customer may receive these documents at the experience location (such as at the entrance to the experience) and then complete the pre-verification document before attending the experience. In some instances, the pre-verification document may be customized based on a specific customer. In addition, the amusement park employee may confirm that the pre-verification document is properly completed. In some instances, based on the information provided by the customer in the pre-verification document, the amusement park employee may take subsequent steps. For example, if the pre-verification document indicates that the customer requests assistance in entering and leaving the experience, the amusement park employee may call and assign another employee to accompany the customer. However, completing the pre-verification process (e.g., the customer completes the document, the amusement park employee confirms the proper completion of the document and complies with the customer's request, the customer receives an indication that the customer has passed the verification of attending the experience, etc.) may be time consuming and uses time that could otherwise be spent on enjoying the experience. Summary of the invention

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

[0004] In one embodiment, a registration system includes an amusement park attraction associated with a registration process. The registration system also includes a database and a controller. The database stores data indicating the availability of the amusement park attraction. The controller receives a request from a customer to attend the amusement park attraction. In response to the request, the controller sends one or more forms, one or more exemptions, or both to the customer. The controller also receives one or more forms, one or more exemptions, or both after completion. In addition, the controller verifies that the one or more forms, one or more exemptions, or both are compliant with the amusement park attraction. In addition, in response to determining compliance, the controller sends an admission code to the customer, the admission code indicating a verified status.

[0005] In one embodiment, a method of operating a registration system includes receiving a request to reserve a feature of an attraction. In addition, the method includes determining one or more features of the attraction as the availability of the feature. In addition, in response to determining that the feature is available, the method includes sending one or more documents to be completed. The method also includes receiving the one or more documents after completion and verifying the one or more documents after completion. The method includes providing a code indicating the verified status of the one or more documents after completion. In addition, the method includes reserving the feature of the attraction in response to verifying the one or more documents after completion.

[0006] In one embodiment, another method for operating a registration system includes sending a request via an amusement park application to reserve a feature of an amusement park attraction for one or more patrons. The method also includes receiving, via the amusement park application, a request to complete a waiver for each of the one or more patrons prior to attending the amusement park attraction. Additionally, the method includes sending, via the amusement park application, the waiver upon completion. Furthermore, the method includes receiving, via the amusement park application, a message to enter the amusement park attraction without a verification process at the amusement park attraction. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] These and other features, aspects, and advantages of the present disclosure will become better understood when the following detailed description is read with reference to the accompanying drawings, in which like characters refer to like parts throughout the drawings, and in which:

[0008] Figure 1 is a schematic diagram of an amusement park application on a display according to an embodiment of the present disclosure;

[0009] Figure 2 According to an embodiment of the present disclosure, Figure 1 A diagram of questions in a form displayed for selecting an amusement park experience in an amusement park application;

[0010] Figure 3 According to an embodiment of the present disclosure, the selection and Figure 2 A schematic diagram showing the exemptions based on the information provided in the question;

[0011] Figure 4 is a block diagram of a registration system for registering patrons for an amusement park experience according to an embodiment of the present disclosure;

[0012] Figure 5 is a process flow chart of a customer-oriented registration process according to an embodiment of the present disclosure; and

[0013] Figure 6 is a process flow diagram of a non-customer-facing registration process according to an embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0015] When introducing elements of various embodiments of the present disclosure, the articles "a," "an," and "the" are intended to mean that there are one or more of the elements described. The terms "comprising," "including," and "having" are intended to be inclusive, and mean that there may be additional elements in addition to the listed elements. In addition, it should be understood that references to "one embodiment," "an embodiment," or "some embodiments" of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the described features. The use of the terms "approximately" or "approximately" should be understood to mean including close to a target (e.g., design, value, amount), such as within any suitable or conceivable tolerance of error (e.g., within 0.1% of a target, within 1% of a target, within 5% of a target, within 10% of a target, within 25% of a target, etc.).

[0016] As used herein, "park application" may refer to a platform for accessing one or more park applications (e.g., games), tickets, documents, and notifications associated with a special event (such as a ride, festival, etc.). In addition, as used herein, "pre-verification document(s)" may refer to any one or more physical or electronic documents associated with an amusement park experience to be completed prior to attending the amusement park experience. The pre-verification document may include one or more waivers, consent forms, information forms, etc. In addition, the pre-verification document may facilitate a pre-verification process in which a customer or group of customers is approved to attend an amusement park experience prior to arriving at the amusement park experience. In addition, as used herein, "customer" or "user" may interchangeably refer to a person accessing an entertainment environment (such as an amusement park experience at an amusement park).

[0017] As previously discussed, a customer may attend an amusement park experience, such as an event at an amusement park. The amusement park experience may allow a customer to fill out a pre-verification document before attending the amusement park experience. The document may include information for efficiently placing the customer and / or other customers in the customer group within the amusement park experience. For example, the amusement park experience may be a holiday parade float, and the document may include questions related to the size of the group, the number of adults and / or children in the group, the height of individuals in the group, any special assistance requests related to loading onto or leaving the float, etc. Additionally or alternatively, the document may include exemptions for attending the parade. The document may be completed and the effective completion of the document may be verified. Specifically, the amusement park employee may confirm that the pre-verification document is properly completed (e.g., completely filled out, no blank or unreadable fields, etc.). The amusement park employee may also confirm that the customer meets the float threshold, so that the information provided in the document meets one or more thresholds for riding the float (e.g., the age of each customer in the group is above the minimum age threshold). Finally, the amusement park employee may reserve an appropriate float for the customer group (e.g., allocating a float that can accommodate the customer based on the information in the document). Manually verifying and registering a customer at an amusement park experience (e.g., at a door to a ride) (e.g., making a reservation for the customer upon approval of documentation) can be time consuming. As discussed herein, for an efficient park experience, a registration system can verify and register the customer before the customer arrives at the amusement park experience. That is, the registration system can approve the customer and reserve the amusement park experience for the customer, thereby effectively registering the customer for the amusement park experience.

[0018] It should be noted that while the examples provided herein may specifically relate to specific aspects of a registration system for an amusement park (such as to facilitate registering customers at an amusement park experience at an amusement park), the technology in the present disclosure may be applied to other conditions and / or contexts. Thus, this example should be understood to reflect a real-world example of a registration system and / or an amusement park to provide a useful context for discussion, and should not be considered to limit the further applicability of this approach. For example, the present disclosure should be understood to be applicable to additional scenarios where compliance of information is verified and / or validated before an event can be utilized.

[0019] Considering the above, Figure 11 is a schematic diagram of an amusement park application 10 for an amusement park. The amusement park application 10 may include or provide access to one or more portals (e.g., associated with an amusement park) that may be accessed through a display interface 11 (such as a web page or mobile application displayed on a device). As will be described in detail herein, the display interface 11 may include visual and / or selectable components (e.g., buttons, editable fields, etc.) that allow customers (e.g., users) to interact with the amusement park application 10. The display interface 11 may display information related to the amusement park, customers, or both. For example, the amusement park application 10 may include park notifications (e.g., closures, new ride opening dates, waiting times for rides, etc.), purchased tickets, indicators or reminders of special events at the park (e.g., performances, plays, shows, parades, etc.), a list of games provided for a gaming platform associated with the amusement park, etc. As shown, the amusement park application 10 may include one or more points of interest 12, which may include indicators (e.g., names or symbols) that identify areas associated with the amusement park and accessible by customers (e.g., physical amusement park experiences at the park or virtual experiences within a game). Although the following discussion describes points of interest 12 as relating to a parade (e.g., a special event), points of interest 12 may relate to any area accessible by patrons, such as, but not limited to, attractions, rides, restaurants, events, lounges, games, etc. It should be noted that, depending on the context, a point of interest 12 as used herein may refer to an indicator of an area or the area itself.

[0020] For example, in Figure 1, the selected point of interest 12 (point of interest 1) is related to a holiday parade. The amusement park application 10 displays information related to the point of interest 12, such as the location, duration, description, reservation options, etc. related to the actual event corresponding to the point of interest 12. Here, for the holiday parade as the point of interest 12, the amusement park application 10 may include information such as one or more event durations 14 (e.g., several weeks in the holiday month), one or more reservation timings 16 (e.g., one or more available time slots on one or more days of the week), and any other parade-related information (as indicated by ellipses). The amusement park application 10 includes a first duration 14A (the week from January 3, 2021 to January 9, 2021) and a second duration 14B (the week from January 10, 2021 to January 16, 2021) as the duration of the holiday parade. In the depicted embodiment, the customer is interested in attending the parade during the first duration 14A. The first duration 14A includes four reservation timings 16 that can be used for reservations to attend the parade (e.g., Sunday, January 3 at 11 a.m. and 6 p.m., Monday, January 4 at 6 p.m., and Tuesday, January 5 at 6 p.m.). However, each duration in the duration 14 may include one or more reservation timings 16. In some embodiments, the amusement park application 10 may be updated in real time so that if a previously unavailable reservation becomes available when canceled, the corresponding reservation timing 16 is shown as available for reservation. In the depicted embodiment, as shown by the dashed box, the user selects the reservation timing 16 at 11 a.m. on Sunday, January 3, 2021.

[0021] In some embodiments, the amusement park application 10 may include an account associated with a customer, so that the customer has a unique user identification (ID) 17 and associated customer data. In the illustrated embodiment, the user ID 17 is presented on the display interface 11. The user ID 17 (e.g., 10359) may include a unique combination of letters, numbers and / or characters that identifies the customer profile associated with the customer. As long as the user ID 17 is available (e.g., not currently used by another customer), the customer can select the user ID 17 and / or the amusement park application 10 can assign the user ID 17. The amusement park application 10 (e.g., via a registration system) can store the customer data (e.g., in one or more databases) and tag it with the user ID 17 so that the amusement park application 10 and / or the amusement park can use the unique user ID 17 to retrieve the customer data. For example, the customer data may include an email address, a customer's name or nickname, age, height, family members and corresponding ages and heights, spoken languages, preferred languages, etc. The patron data may also include patron activity tracked with or within the amusement park, such as an annual pass associated with the patron, the duration of a park visit, rides visited, areas visited, activity on a gaming portal associated with the amusement park, etc. For example, an annual pass may be unique to the patron, and as such, the annual pass ID may be used as the user ID 17 to retrieve patron data for the annual pass holder.

[0022] Additionally, in some instances, the amusement park application 10 may also extract data from third-party applications associated with the patron (e.g., medical information indicating that assistance may be requested for a ride) and tag it with the user ID 17 before storing it as patron data. Figure 4As described in detail, the registration system may communicate with a third-party application programming interface (API) that allows the registration system to communicate with third-party applications. Specifically, the API may serve as a medium for sending requests from the amusement park application 10 to a third-party application (e.g., a third-party system), receiving information returned from the third-party application, and delivering the information back to the registration system. In this way, the registration system may access third-party information that may not otherwise be available through the registration system. For example, when a customer grants access, a registration system via the amusement park application 10 on a mobile device may access third-party applications on a mobile device, such as social media applications, medical applications, banking applications, etc. The registration system may use such information to understand the customer. Third-party data may indicate preferences, including but not limited to favorite floats during holiday parades (e.g., as indicated on social media), family size, medical conditions, physical disabilities, and / or information related to the customer's family members. In some embodiments, the registration system may use user ID 17 to retrieve customer data and use customer data to pre-check customers, provide appropriate pre-check documents, automatically fill in parts of the pre-check documents for customer review and / or verify customers for points of interest 12 (e.g., parades). In this way, the registration system may use the customer data to efficiently verify and register the customer for a reservation before the customer arrives at the point of interest 12 .

[0023] Figure 2 The diagram is based on Figure 1 Schematic diagram of questions of a form presented for selection of an amusement park experience (e.g., point of interest 12) in an amusement park application of . Specifically, as previously mentioned, a customer selects a reservation timing 16 for a parade at 11 a.m. on Sunday, January 3, 2021. As previously mentioned, the amusement park application 10 includes input fields, selectable buttons, etc. to facilitate receiving input from the customer. Upon selection of the reservation timing 16, one or more sub-questions 18 related to the point of interest 12 may appear. Here, the sub-questions 18 include a first sub-question 18A requesting the number of customers in the group. The customer may enter the number of customers who will ride on the float in the parade (e.g., one, two, four, etc.). The second sub-question 18B requests the number of adults (e.g., age 18+) in the group, and the third sub-question 18C requests the number of children (e.g., age 18 or less) in the group. The second sub-question 18B and the third sub-question 18C are sub-questions of the first sub-question 18A. In some embodiments, upon answering a previous question (e.g., triggering a subsequent question to appear), a sub-question 18 derived from the previous question may be presented in the amusement park application 10. Additionally or alternatively, a sub-question 18 may be removed from the display based on the answer to the previous question. As such, the sub-questions 18 may be dynamic, such that they appear or disappear based on the previous answer. Furthermore, the subsequent sub-questions 18 may be customized to the answers provided for the previous sub-questions 18.

[0024] Sub-questions 18 also include a fourth sub-question 18D, which requests whether any of the customers in the group require special assistance, such as to take into account conditions (e.g., the need for wheelchair use or the need for language translation), etc. A fifth sub-question 18E, which is a sub-question of the fourth sub-question 18D, may request an indication of how many customers require special assistance. As previously discussed, the fifth sub-question 18E may appear based on a specific response to the previous sub-question that triggered the fifth sub-question 18E. For example, if the customer answers "yes" to the fourth sub-question 18D, the registration system may cause the fifth sub-question 18E to appear. Alternatively, if the customer answers "no" to the fourth sub-question 18D, the registration system may indicate that the information requested in this form has been completed, causing a different sub-question 18 to appear and / or removing the fifth sub-question 18E. As previously discussed, the user ID 17 can be used to pre-populate editable answers to sub-questions 18 and customize questions associated with the user ID 17. For example, if the patron data associated with user ID 17 indicates that the patron purchased both adult and child tickets for a parade, the registration system may request information related to both adults and children and pre-populate answer fields based on the ticket purchase and other patron data. In some embodiments, the information requested for points of interest 12 may be static for each patron (e.g., same form), such as based on the protocol for a particular point of interest (e.g., questions to answer for ride protocol for the ride of interest).

[0025] Figure 3 is based on Figure 1 The selection of amusement park experience (e.g., point of interest 12) for Figure 2 , or both. That is, upon selection of a parade as a point of interest 12, the amusement park application 10 may provide the patron with a waiver 20 for attending the parade. Additionally or alternatively, the waiver 20 provided may be based on the information provided for sub-question 18. As shown, the waiver 20 includes waivers for adults in the group, waivers for children in the group, and any other event-related documents (as indicated by the ellipsis). Thus, the amusement park application 10 may request information, request completion of waivers, etc., via a form, etc., before the patron and group arrive at the parade. In some embodiments, if the waiver 20 is improperly completed (e.g., the patron's initials are missing on each page, the digital signature is illegible, etc.), the amusement park application 10 may prompt the user to correct the identified issues when verifying a pre-verification document (e.g., a form with sub-questions 18, waivers 20, and other event-related documents). As will be described with respect to Figure 5 and Figure 6As discussed in detail, the patron may receive an indication that the registration process has been completed and the group has been approved for the point of interest 12. In this way, the amusement park application 10 may provide an interface for performing pre-verification (e.g., a patron-oriented registration process) and for performing verification for the point of interest 12 (e.g., a non-patron-oriented registration process) before the patron arrives at the point of interest 12. The pre-verification process of requesting information, verifying the patron, and providing an indication of approval prior to arrival via a pre-verification document provides an efficient process for attending a ride. In addition, pre-verification may remove any bottlenecks in the patron queue that may otherwise occur due to distributing forms, requesting information via forms, requesting signatures on waivers 20, verifying compliance of forms and waivers, verifying proper completion, approving or disapproving patrons, reserving time slots for the point of interest 12, and the like.

[0026] To illustrate the system for contacting and authenticating customers via the amusement park application, Figure 4 A registration system 50 is depicted for registering patrons prior to their arrival at a point of interest 12. As shown, the registration system 50 includes park sensors 52, controllers 54, points of interest 12, amusement park applications 10, patron mobile devices 60, and third-party applications 62. In some embodiments, the registration system 50 may also include a monitoring system 56, a service desk 58, or both. It should be understood that the illustrated system is intended to be exemplary only, and that certain features and components may be omitted, and various other features and components may be added to facilitate performance, in accordance with the disclosed embodiments.

[0027] The controller 54 may include an input device 70, a processor 72, a memory 74, and a communication circuit 76. The input device 70 may receive input data from the park sensors 52, the amusement park application 10, the third-party application 62, and the patron mobile device 60. Although the following discussion describes the amusement park application 10, the third-party application 62, and the patron mobile device 60 as separate components of the registration system 50 that provide data to the input device 70, these components may instead be integrated into the amusement park application 10 or communicate with the amusement park application 10 (as indicated by the dotted line). Based on the input data received at the input device 70, the controller 54 may register and verify the patron attending the point of interest 12, as previously discussed.

[0028] The controller 54 may register the patron for the point of interest 12 and / or confirm compliance with procedures based on the information provided for registration (e.g., approving or verifying the patron). As previously discussed, the points of interest 12 may include attractions throughout the amusement park, such as rides, virtual game rooms, picnic areas, restaurants, special events such as parades or performances, etc. In some instances, the patron may complete a pre-verification document at the point of interest 12 to attend the point of interest 12, as previously discussed. Completing such documents after arriving at the point of interest 12 may be time consuming and cause delays in attending the point of interest (e.g., boarding a float in a parade). As such, the controller 54 may communicate with the point of interest 12 (e.g., another system and / or park staff) and the amusement park application 10 to pre-verify the patron prior to arrival at the point of interest 12.

[0029] The amusement park application 10 may include an account application 78 and a notification application 80. The account application may include the customer's user ID 17 and any information related to the user ID 17. In some embodiments, and as previously discussed, customer data may be associated with a specific user ID 17 so that the pre-check document may be customized and / or pre-filled for confirmation based on the customer data. The notification application 80 may provide a message to the customer. The message may include communications related to the amusement park, such as information related to the point of interest 12. The notification application 80 may notify the customer of the pre-check document to be completed before the arrival of the point of interest 12. In some embodiments, the notification application 80 may also send a message to notify the customer, based on the customer's location (e.g., based on the location of the customer executing the amusement park application 10) recommending possible points of interest 12. In addition, the notification application 80 may notify the customer that the customer has been approved to attend the point of interest 12 (e.g., the pre-check document has been verified). As will be discussed herein, the amusement park application 10 may provide a quick response (QR) code for entering the amusement park application 10, wherein the QR code indicates that the customer has been registered and approved for the reservation of attending the point of interest 12. The patron may receive the QR code via the amusement park app 10, email, text message, etc.

[0030] In some embodiments, the controller 54 may initiate a registration process based on data from the park sensor 52. Specifically, the park sensor 52 may indicate a selection or intention to attend a point of interest 12. The park sensor 52 may include inputs within the amusement park application 10 and physical sensors at the amusement park. For example, the park sensor 52 may include a touch sensor of a mobile device 60 indicating a point of interest 12 and a selection of a reservation timer 16. The park sensor 52 may include one or more radio frequency identification (RFID) tags, one or more cameras, one or more weight sensors, one or more electronic readers, and / or one or more proximity sensors. The park sensor 52 may be placed or located in an area where a customer is expected to be present, such as near a point of interest 12. For example, a park sensor 52 located in a customer queue at a point of interest 12 may detect a customer and determine that the customer may be present at a point of interest 12 including the queue. The RFID tag may communicate with an electronic reader to indicate the presence of the customer. Thus, the electronic reader may be placed in a manner that allows the RFID tag to be scanned, such as along a specific path that gradually leads to a point of interest 12. In some embodiments, the RFID tag may include a customer wearable RFID tag associated with a specific user ID 17. Thus, the input data from the electronic reader may indicate the presence of a customer associated with the user ID 17 when the customer's wearable RFID tag is scanned. Subsequently, the controller 54 may retrieve the customer data based on the user ID 17 for filling in a form provided to the customer for attendance at a point of interest 12. In some embodiments, the amusement park application 10 may communicate with the park sensors 52 so that customers detected near a particular point of interest 12 (e.g., within a threshold distance from the point of interest 12) receive recommendations for fun in nearby points of interest 12 and / or reminders for performing a check-in process prior to arrival at the point of interest 12.

[0031] The third-party application 62 can provide input data to the input device 70. That is, when the customer permits, the third-party application 62 can be enabled to share data with the registration system 50. The third-party application 62 may include a system associated with a third party, including an entity that does not have a direct relationship with the amusement park. The third-party application 62 may provide third-party data collected through its website, mobile application and / or other platform from one or more third parties. As previously mentioned, the third-party application 62 may include, but is not limited to, social media applications, medical applications and / or banking applications. Thus, the third-party data from the third-party application 62 may include data associated with the social media application, medical application and / or banking application.

[0032] The patron mobile device 60 may also provide input data to the input device 70. Depending on permission from the patron, the patron mobile device 60 may be enabled to share device data with the registration system 50. The device data may include, but is not limited to, images and videos stored on or accessible to the patron mobile device 60 (e.g., images of a parade or other point of interest), the GPS location of the patron mobile device 60 (e.g., indicating that the patron is walking toward or within a threshold distance of a point of interest 12 and, thus, may be interested in attending the point of interest 12), tracking data determined by the patron mobile device 60, and / or environmental preferences (e.g., special accessibility features implemented, etc.).

[0033] The registration system 50 includes a monitoring system 56 and a service desk 58. Although the following discussion describes the monitoring system 56 and the service desk 58 as separate components of the registration system 50, these components may communicate with each other (e.g., as indicated by the dotted line) or be integrated into a single system (e.g., the service desk 58 is part of the monitoring system 56). The monitoring system 56 may be a management system that monitors the park sensors 52, points of interest 12, and the amusement park application 10. For example, the monitoring system 56 may monitor data used for the registration process and to verify customers, control signals that control features of points of interest (such as floats), etc. In particular, the monitoring system 56 may ensure that the park sensors 52, points of interest 12, and the amusement park application 10 function as expected. In some embodiments, the monitoring system 56 may also track waiting times or queues for rides to maintain expected throughput when performing pre-checking processes.

[0034] In addition, if the controller 54 is not functioning as expected (e.g., erroneous control signals), the monitoring system 56 can control or reconfigure the controller 54. In this way, the monitoring system 56 can reset or recalibrate the park sensors 52, points of interest 12, and the display or layout of the pre-checked documents on the amusement park application 10 and / or override the amusement park application 10 for a particular customer (as initially determined by the controller 54). The monitoring system 56 can reset the algorithms associated with the pre-checked documents. In some embodiments, the monitoring system 56 and the controller 54 can be implemented as a single controller.

[0035] In some embodiments, the service desk 58, which may include a human or virtual service agent, may manually stop features of the point of interest 12 via a stop mechanism (e.g., a button) to override the control signal from the controller 54 in the event that the service desk 58 finds any problems with the point of interest 12. Since patrons may be tracked as previously discussed (e.g., via RFID tags wearable by patrons), the service desk 58 may monitor the patrons' activity and use it to resolve unexpected delays or unexpected functions at the amusement park. For example, the tracked activity may indicate that the patron will not be able to attend the parade at the reserved reservation time 16, thereby indicating to the controller 54 that a float may be reallocated based on confirmation from the delayed patron.

[0036] The controller 54 may enable the communication circuitry 76 to interface with various electronic devices, such as the monitoring system 56, the service desk 58, the amusement park application 10, and / or the point of interest 12. The monitoring system 56 and / or the service desk 58 may communicate with the controller 54 to receive and / or send information (as indicated by the double-headed arrows) to ensure that the amusement park application 10 and / or the point of interest 12 are operating as expected. Additionally or alternatively, the controller 54 may enable the communication circuitry 76 to interface with components of the point of interest 12. For example, the communication circuitry 76 may allow the controller 54 to be communicatively coupled to a network, such as a personal area network (PAN), a local area network (LAN), and / or a wide area network (WAN). Thus, in some embodiments, the controller 54 may process data from the input device 70 via the communication circuitry 76, determine a point of interest 12, determine patron data associated with the patron based on the corresponding user ID 17, determine a pre-verification document to provide to the patron, pre-populate portions of the pre-verification document, communicate the document to the amusement park application 10, receive input from the amusement park application 10, approve the patron's attendance at the point of interest 12, etc. For example, after processing the sensor data from the input device 70, the processor 72 may determine a control signal that enables the communication circuitry 76 to wirelessly transmit control data to the amusement park application 10 and / or the point of interest 12 to facilitate directing the patron's attendance at the point of interest 12. In other embodiments, the communication circuitry 76 may be connected to the amusement park application 10 and / or the point of interest 12 via a wired connection.

[0037] The processor 72 may include one or more processing devices that receive input signals from the input device 70 associated with customer data, which can then be used to register and verify customers before reserving for the point of interest 12 using the techniques described herein. The memory 74 may include one or more tangible non-transitory machine-readable media. For example, such machine-readable media can include RAM, ROM, EPROM, EEPROM, or optical disk storage, disk storage, or other magnetic storage devices or any other medium that can be used to carry or store a desired algorithm (e.g., program code) in the form of machine-executable instructions or data structures and can be accessed by the processor 72 or other processor-based devices. In particular, the processor 72 may include a processing core that executes the machine-executable instruction algorithm stored in the memory 74. The processor 72 may also include a processor-side interface for software applications running on the processing core to interact with hardware components of the point of interest 12 associated with the processor 72 (such as hardware components of a float or other features of a parade). The memory 74 may store customer data and algorithms for verifying customers for a particular point of interest 12, providing confirmation of verification of continued attendance at the point of interest 12, etc. The memory 74 may tag the patron data with the corresponding user ID 17 before storing it for subsequent retrieval. That is, the registration system 50 may retrieve data associated with the patron by looking up the user ID 17 and using the associated patron data. As an example in an amusement park environment, the stored algorithms may include, but are not limited to, algorithms that determine patron presence based on sensor data from park sensors 52, identify specific patrons, identify points of interest 12, retrieve patron data for user ID 17 (if available), determine appropriate pre-verification documents (e.g., forms, waivers, etc.) to provide for the point of interest 12, determine portions of the pre-verification documents based on the patron data and / or populate portions of the pre-verification documents, etc.

[0038] Figure 5 1 is a flow chart of a method 100 for a customer to undergo a registration process on an amusement park application 10. That is, the method 100 includes a customer-facing interface and a registration process of the registration system 50. Figure 5 Method 100 and Figure 6 Although the method 130 of the present invention is described using actions in a particular order, it should be understood that the actions described may be performed in an order different from that shown, and that some of the described actions may be skipped or not performed in their entirety. In general, at least some of the steps of the method 100 and the method 130 may be at least partially performed by Figure 4Specifically, these steps may be implemented at least in part by the controller 54 and / or the processor 72 of the controller 54 executing instructions stored in a tangible, non-transitory computer-readable medium such as a memory 74. In alternative or additional embodiments, at least some steps of the methods 100 and 130 may be implemented by any other suitable components or control logic, etc.

[0039] As previously discussed, a patron may be interested in attending a point of interest 12 (e.g., an amusement park attraction). Thus, the processor 72 may request (process block 104) attendance at a point of interest 12 based on input received in an amusement park application 10 executed on an electronic device associated with the patron (e.g., a patron device, a mobile device 60) (e.g., the patron selects a point of interest 12). As previously mentioned, a point of interest 12 may include rides, special events (such as parades or shows), etc. The processor 72 may select (process block 106) a time for attendance at a point of interest 12 based on input received in the amusement park application 10 (e.g., the patron selects a reservation timer 16). That is, the patron may view various time slots for one or more days for a point of interest 12 (e.g., for a point of interest 12). Figure 2 ), and based on the selection from the customer, the processor 72 may select a time to be reserved for the customer. The selection may cause the amusement park application 10 to display one or more questions (e.g., sub-questions 18) related to the customer and / or customer group, such as Figure 2 The processor 72 may receive (process block 108) responses to one or more questions related to the customer and / or customer group based on input received in the amusement park application 10 (e.g., customer input information for sub-questions 18). That is, the customer may enter (e.g., select, type, etc.) responses to one or more general or point of interest related questions for a selected time, and the processor 72 may process the responses.

[0040] Additionally or alternatively, the processor 72 may receive (process block 110) one or more waivers 20 displayed on the amusement park application 10 for the customer and / or customer group to receive on the display. In particular, the processor 72 may retrieve or receive general waivers 20, specific waivers 20, or both that are then provided to the customer and / or customer group in the amusement park application 10. As such, as described above with respect to Figure 3 As discussed, the amusement park application 10 may request information, request completion of a waiver 20 , etc., prior to a patron arriving at a point of interest 12 via a pre-verification document including a form or the like (eg, one or more questions).

[0041] After indicating the waiver as completed based on the received customer input (e.g., the customer submits the completed waiver 20), the processor 72 may submit (process block 112) the waiver 20 for review. In particular, the customer may receive the waiver 20 in the amusement park application 10, complete the waiver 20, and submit the waiver 20 for review as part of the registration process. The customer may receive an indication of whether the waiver 20 is approved (decision block 114) via the processor 72. Specifically, the customer may receive an indication of whether the customer is approved or verified to attend the point of interest 12 of the customer and / or customer group. The processor 72 may provide an indication based on the input information from the waiver 20.

[0042] If the waiver 20 is approved, the processor 72 may receive (process block 115) information related to attendance at the point of interest 12 to be displayed correspondingly in the amusement park application 10 for the customer to receive the information. That is, the customer may receive a notification (e.g., a message) indicating that the waiver 20 was accepted along with a QR code that can be verified or scanned for admission to attend the point of interest 12. The QR code may indicate that the customer and / or customer group has been verified to attend the point of interest 12. However, if the waiver 20 is not approved, the processor 72 may receive (process block 116) an indication to modify the waiver 20 and display the indication on the amusement park application 10 for the customer to receive. Specifically, the processor 72 may provide (e.g., the customer may receive) an indication that the waiver 20 was not accepted, a reason for not accepting the waiver 20, a recommendation to modify the waiver 20 (e.g., an indication of fields that need to be modified within the waiver 20), any other reasons related to the failed or unapproved registration, etc. As such, the processor 72 may update the waivers 20 based on modified or new information entered by patrons in the amusement park application 10 .

[0043] Figure 6 1 is a flow chart of a method 130 of a non-customer-facing registration process. That is, the method 130 includes back verification of a customer based on input received at a customer-facing interface, such as for Figure 5On the back of the verification process for registering a customer, the processor 72 may receive (process block 132) a request from the customer to attend a point of interest 12 (such as a parade at a specific time and location). The processor 72 may receive input and perform checks related to the point of interest, such as determining whether the point of interest 12 is available at the selected time. Regarding the parade, the processor 72 may determine whether a float is available for a specific customer at the selected time. Specifically, the processor 72 may query a database storing the number of floats in the parade and the current reservation to determine the availability of a suitable float. The database generally may store any information related to the features that can be used for reservations for the point of interest 12. Regarding the float, the database may store the type of float (e.g., 2-seater, 4-seater, etc.), the time of the float that is reserved or available each day, special assistance features in the float, etc. In some instances, availability may be changed based on the answers provided to the questions and / or the information provided in the waiver 20. That is, the specific float reserved for the customer at a specific available time slot may be changed based on new information (such as the number of customers in the group attending the parade with the customer, special assistance, etc.).

[0044] In some embodiments, processor 72 may identify (process block 134) a customer. In particular, and as described with respect to Figure 1 As discussed above, the processor 72 may use a user ID 17 associated with a customer in an amusement park application. As previously mentioned, the user ID 17 may include age, height, family members and corresponding ages and heights, spoken languages, preferred languages, special assistance preferences, etc. The processor 72 may send (process box 136) one or more questions (e.g., as sub-questions 18) to customers attending the point of interest 12 at the selected time slot. For example, for a parade, the processor 72 may request information related to the number of adults, children, or both that will be on the same float. The processor 72 may receive (process box 138) answers to one or more questions from the amusement park application 10 based on customer input to the questions. For example, a customer may answer a question to indicate that the group includes a customer (e.g., an adult) and three children.

[0045] Based on the information provided by the customer, the processor 72 may retrieve and send (process box 140) one or more exemptions to the customer based on the received answers. For example, if the customer answers that the group includes a specific number of adults and children, the processor 72 may retrieve and transmit a specific number of exemptions for both adults and children. In some embodiments, the point of interest 12 may request the completion of specific exemptions 20 for each customer, and as such, some exemptions 20 may always be transmitted to the customer. The processor 72 may receive (process box 142) the completed exemptions 20. After the customer and / or group completes the exemptions 20, such as by signing the exemptions (e.g., using a finger or stylus in the amusement park application 10) and submitting the exemptions 20, the processor 72 may receive the submitted exemptions 20 to confirm compliance with the procedures for completing the exemptions 20 for the point of interest 12.

[0046] After receiving the completed waiver, the processor 72 may determine (decision box 144) whether the waiver is compliant for attending the point of interest. In some embodiments, compliance may be based on one or more factors, such as the point of interest 12, a specific customer, readability, etc. For example, compliance for the point of interest may be related to a minimum weight and / or age on a float. If the completed waiver 20 is compliant, the processor 72 may approve the customer and send (process box 145) a message indicating the successful approval of the request to attend the point of interest 12. The registration system 50 may also register the customer at the point of interest 12 (e.g., pre-approving the customer for attendance). In addition, the registration system may reserve the requested time and date for the customer to attend the point of interest 12. In some embodiments, and as previously discussed, the approved message may include a QR code or another unique identifier. In some instances, the unique identifier may be secure so that the identifier is not easily copied or is not susceptible to fraud (e.g., used by another customer). On the other hand, if the processor 72 is not compliant, the processor 72 may not approve (process box 146) the customer. As such, the customer may not be able to attend the point of interest 12. As previously mentioned, the processor may send a request to the customer (e.g., via the amusement park application 10) to modify the exemption 20 (e.g., maintain the reservation) within a predetermined time period so that the customer can be approved to attend the point of interest 12. In some embodiments, the processor 72 may request payment in the amusement park application 10. For example, some points of interest 12 may request payment for reservations (e.g., holiday shows, restaurant reservations, etc.). In such instances, if the pre-verification documents associated with the reservation are not properly completed, the processor 72 may refund the payment. In this way, the registration system 50 can verify and register customers before they arrive at a point of interest 12 (e.g., an amusement park experience) for an efficient park experience.

[0047] Specifically, some of the benefits and efficiencies provided by the registration system 50 include improved computer operations. Improved computer operations may include a registration process that reduces the large and often irrelevant number of documents that are reviewed when verifying a customer. Unlike processing multiple redundant documents for each customer (which may be time consuming and use a relatively large amount of processing power), the registration system 50 described herein utilizes data to provide appropriate documents customized to the customer for computer processing during the process of registering the customer. In addition, computer processing of documents can be performed at a single location (e.g., at a back end or non-customer interface), thereby speeding up otherwise time-consuming and power-consuming processes that are otherwise associated with multiple registration processes at various locations (e.g., in a campus application, at the entrance to a point of interest, in a queue at a point of interest, etc.).

[0048] Although only certain features of the present disclosure have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It is to be understood, therefore, that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the present disclosure. It should be appreciated that any of the features illustrated or described with respect to the drawings discussed above may be combined in any suitable manner.

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

Claims

1. A registration system comprising: amusement park attractions, which are associated with the registration process; a database storing data indicating availability of said amusement park attractions; as well as A controller configured to: receiving a request from a patron to attend the amusement park attraction; In response to the request, sending one or more forms, one or more waivers, or a combination thereof to the customer; Upon completion, receiving said one or more forms, one or more waivers, or said combination thereof; and verifying the one or more forms, the one or more exemptions, or the combination thereof as compliant for the amusement park attraction; as well as In response to determining compliance, an access code is sent to the patron, the access code indicating a verified status.

2. A registration system as claimed in claim 1, wherein: The controller is configured to register the patron at the amusement park attraction using the admission code without requiring a verification process at the amusement park attraction.

3. The registration system as claimed in claim 1, wherein: The admission code includes a Quick Response (QR) code.

4. The registration system as claimed in claim 1, wherein: The controller is configured to: In response to determining that the one or more forms, the one or more exemptions, or the combination thereof are non-compliant, a request to modify the one or more forms, the one or more exemptions, or the combination thereof is sent to the customer.

5. The registration system as claimed in claim 1, wherein: The controller is configured to: identifying the customer; retrieving information associated with the customer; and The one or more forms, the one or more waivers, or the combination thereof are sent based at least in part on the information.

6. A registration system as claimed in claim 5, wherein: The controller is configured to pre-populate at least a portion of the one or more forms, the one or more waivers, or the combination thereof based on the information.

7. The registration system as claimed in claim 1, wherein: The request includes a time slot among a plurality of time slots for attending the amusement park attraction.

8. A registration system as claimed in claim 7, wherein: The controller is configured to: Based on collecting sensor data from the amusement park attraction, availability of the amusement park attraction during the time slot is determined prior to sending the one or more forms, the one or more waivers, or the combination thereof.

9. The registration system of claim 1, wherein: The controller is configured to determine the availability based on pending reservations for the amusement park attraction.

10. A method of operating a registration system, the method comprising: receiving a request to reserve a feature of an attraction; determining one or more features of the attraction as an availability of the features; In response to determining that the feature is available, sending the one or more documents to be completed; receiving the one or more documents after completion; the one or more documents after verification is complete; providing a code indicating a verified status of the one or more documents upon completion; as well as Responsive to the one or more documents after verification is complete, the feature of the attraction is reserved.

11. The method of claim 10, wherein: The request includes an indication of the number of persons attending the feature.

12. The method of claim 11, wherein: Determining the availability of the features includes determining a currently reserved, future availability of the one or more features based at least in part on the number of people and a current state defined by at least one sensor of the one or more features.

13. The method of claim 11, wherein: The one or more documents are based at least in part on the number of people.

14. The method of claim 10, wherein: The request indicates the number of adults, the number of children, or a combination thereof.

15. The method of claim 14, wherein: Determining the availability of the features includes determining a current reservation, a future availability of the one or more features based at least in part on the number of adults, the number of children, or a combination thereof.

16. The method of claim 10, wherein: The request includes an indication of a request for special assistance in attending to the feature.

17. The method of claim 16, wherein: The one or more documents are based at least in part on the specific assistance request.

18. A method of operating a registration system, the method comprising: sending, via the amusement park application, a request to reserve features of an amusement park attraction for one or more patrons; receiving, via the amusement park application, a request to complete a waiver for each of the one or more patrons prior to attending the amusement park attraction; sending the waiver via the amusement park application upon completion; as well as Via the amusement park application, a message for entering the amusement park attraction is received without a verification process at the amusement park attraction.

19. The method of claim 18, comprising: A request is received via the amusement park application to provide payment for the amusement park application prior to attending the amusement park attraction.

20. The method of claim 18, wherein: The message includes a unique code associated with the reservation of the feature.