Entertainment interaction based on accessing separate system to populate hidden field

Abstract

To provide high-level entertainment and components of interest in an amusement park.SOLUTION: There is provided an interactive platform for controlling interactive features in an amusement park, wherein the interactive platform includes a control center that receives an account request from a user computer system, populates forward facing data fields based on user inputs from the user computer system, coordinates authentication of the account request with a separate system configured to utilize a login application programming interface to share authentication data, receives the authentication data from the separate system, provides access to a user account based on the authentication data, and populates hidden data fields of the control center based on user data provided by the separate system.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 018,134, filed April 30, 2020, and entitled "ENTERTAINMENT INTERACTION BASED ON ACCESSING A SEPARATE SYSTEM TO POPULATE A HIDDEN FIELD," which is incorporated herein by reference in its entirety for all purposes.

[0002] The subject matter disclosed herein relates to amusement parks, and more particularly to providing enhanced entertainment and components of interest within amusement parks. [Background technology]

[0003] Amusement and / or theme parks may include a variety of entertainment attractions (e.g., restaurants, rides, and shows) that help provide enjoyment to guests or patrons of the amusement park. For example, attractions may include traditional children's rides, such as carousels, and traditional thrill-seeker rides, such as roller coasters. Currently, adding interest and thrill components to such attractions and other amusement park areas is recognized as a challenge. Specifically, the challenge is to incorporate features that immerse guests in the experience and make them feel as if they are experiencing something truly magical.

[0004] It is now recognized that patrons often prefer a personal experience. It is further recognized that, with the increasing availability of technology and information via the Internet, patrons are becoming more educated and technologically savvy about how special effects are produced and how information is obtained. As a result, it can be difficult to provide an experience that feels magical because the technology and mechanics behind the experience are easily discerned. Accordingly, it is now recognized that it is desirable to include an interest component in a way that is more personalized, efficient, and surprising than previous techniques.

[0005] This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present disclosure, as described below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. As such, it should be understood that these statements are to be read in this light, and not as admissions of prior art. Summary of the Invention [Means for solving the problem]

[0006] The following summarizes some embodiments within the scope of the present disclosure. These embodiments are not intended to limit the scope of the present disclosure, but rather to provide a general outline of possible forms of the present embodiments. Indeed, the present embodiments may include a variety of forms that may be similar to or different from the embodiments set forth below.

[0007] In one embodiment, an interaction platform for controlling interaction functions at an amusement park is provided, the interaction platform including a control center that receives an account request from a user computer system, populates forward-facing data fields based on user input from the user computer system, coordinates authentication of the account request with another system configured to share authentication data utilizing a login application programming interface, receives authentication data from the other system, provides access to the user account based on the authentication data, and populates hidden data fields of the control center based on user data provided by the other system.

[0008] In one embodiment, a method for authenticating and populating a hidden data field that facilitates control of an interactive device in an amusement park environment is provided. The method includes receiving an account request from a user computer system at a control center and populating a forward data field at the control center based on user input from the user computer system. The method further includes coordinating, by the control center, authentication of the account request with another system configured to share authentication data utilizing a login application programming interface; receiving, at the control center, authentication data from the other system and providing access to a user account for the user computer system based on the authentication data; and populating a hidden data field at the control center based on user data provided by the other system.

[0009] In one embodiment, a system is provided for populating hidden data fields and controlling interactive experiences at an amusement park based on the hidden data fields. The system includes another system that shares authentication data utilizing a login application programming interface. The system also includes a control center that receives an account request from a user computer system, populates forward data fields based on user input from the user computer system, coordinates authentication of the account request with the other system based on interaction with the login application programming interface, receives authentication data from the other system, provides access to the user account based on the authentication data, and populates hidden data fields of the control center based on user data provided by the other system. The system further includes one or more interaction devices located within the amusement park and configured to be controlled by the control center based on the user data.

[0010] 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 parts are designated by like numerals throughout. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a schematic diagram of an interaction platform and another system for providing account authentication and user interaction at an amusement park based on hidden data associated with the account, according to an embodiment of the present disclosure. [Figure 2] 1 is a schematic perspective view of an amusement park venue having interaction devices configured to be controlled by an interaction platform based on hidden data related to users detected within the venue by a user detection system, according to an embodiment of the present disclosure. [Figure 3] FIG. 1 is a block diagram of the interaction between an interaction platform and another system that provides account authentication and interaction at an amusement park, according to an embodiment of the present disclosure. [Figure 4] FIG. 1 is a block diagram of a graphical user interface having various transitions based on a process flow for providing account authentication and interaction at an amusement park, according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0012]

[0013] One or more specific embodiments of the present disclosure will now be described. In the interest of brevity in describing these embodiments, not all features of an implementation may be described herein. It will be understood that the development of any such implementation, as in any engineering or design project, requires numerous implementation-specific decisions to be made to achieve the developer's particular objectives, including compliance with system- and business-related constraints that may vary from implementation to implementation. Moreover, it will be understood that such a development effort may be complex and time-consuming, but would be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill in the art having the benefit of this disclosure.

[0013] When introducing elements of various embodiments of the present disclosure, the articles "a," "an," and "the" are intended to mean the presence of one or more of the element. The terms "comprising," "including," and "having" are intended to be inclusive and mean that there may be additional elements other than the listed elements. Furthermore, references to "one embodiment" or "an embodiment" of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also contain the recited features.

[0014] The present embodiments relate to improving the guest experience at an amusement park. An amusement park may include rides, an amusement park facility mall (e.g., restaurants, souvenir shops, and shows), and a collection of amusement park attractions (e.g., a Ferris wheel, dark ride, or other attractions). In some embodiments, the rides may include roller coasters, dark rides, or other similar ride-based experiences, and thus may further include a ride path along which the passenger ride vehicles travel during operation. It should be understood that the present embodiments may be utilized to enhance the experience of guests on the passenger ride vehicles while the vehicles are in operation. Similarly, the present embodiments may be utilized to enhance the guest experience throughout the amusement park, even while the guests are simply traveling between locations within the amusement park. It should be noted that the term guest, as used throughout this disclosure, refers to a user of the disclosed systems and methods. While the term guest is frequently used, other types of users are also contemplated. For example, the present embodiments include systems and techniques for guest registration, and it is also contemplated that such registration systems and techniques may be employed by non-guest users on behalf of current or prospective guests. Additionally, in some aspects of the present disclosure, the term user may be synonymous with the term guest. Accordingly, it should be understood that the disclosed examples are not limiting and that the term guest may broadly refer to any of a variety of users and user types.

[0015] The present embodiments relate to a system and method for providing an interaction platform or interaction platform system for providing guest experiences at an amusement park (e.g., a theme park). The interaction platform can facilitate the provision of personalized experiences, such as games and effects, that individually appeal to guests and can enhance interactions between guests and amusement park features (e.g., rides, shows, decorations, animated figures, interactive screens), other guests, costumed characters, etc. For example, the interaction platform can cooperate with electronic goggles, electronic glasses, projection screens, etc. to provide specialized augmented reality (AR), virtual reality (VR), or mixed reality (e.g., a combination of AR and VR) experiences as part of attractions such as amusement park thrill rides. The interaction platform can also work in conjunction with more tangible entertainment features, such as animated figures, fountains, or costume elements, to provide experiences based on personal preferences, characteristics, or other information about particular guests who are able to use the interaction platform.

[0016] This embodiment may include a portal (e.g., a website or app) that allows guests to register with the interaction platform. This registration process may be used to obtain data about each guest, which may be used within the amusement park environment to provide customized entertainment enhancements. For example, the registration process may provide guest access to data fields and include a request to enter user information into the data fields, such as favorite color, date of birth, and height. These data fields may then be used to control interactions such as an augmented reality laser beam with the user's favorite color, an animation tailored to look into the user's eyes based on the user's height, or customized dialogue that references the user's date of birth. The registration process may be one element of a larger process or may include sub-processes for obtaining tickets, making reservations, assembling event schedules, or other such activities related to the amusement park. For example, guests may log in and register via an app stored on a mobile device (e.g., a smartphone or smartwatch) to obtain admission tickets and schedule specific events (e.g., rides, restaurant reservations, entry to amusement park areas, or shows). Login credentials may be required as part of this registration process. While the interaction platform can certainly internally generate new login credentials (e.g., a new user identification and password) that are separate from any other accounts, it can also enable integration with other accounts and other systems. For example, the interaction platform can enable login based on a separately established third-party account that already has established login credentials. In some embodiments, a user can create new login credentials to use the separately established third-party account. For example, a user can provide a username (e.g., a themed name) for the new account, but still use the login credentials from the established third-party account.

[0017] In embodiments of the interaction platform, personal information about a user can be entered directly into data fields when entering the information into a database. However, this type of input can be tricky for guests familiar with the nature of amusement park interactions, which are intended to entertain guests in part through personalized surprises. For example, if a user indicates a particular preference (e.g., Saturn is the user's favorite planet) and this preference manifests in a special effect provided to the guest within the amusement park (e.g., a mind-blowing simulation in which the guest travels to Saturn), it may become apparent to the guest that the preference originated in the registration process, potentially removing some of the mystery from the experience. Because mystery and a seemingly magical aspect of the interaction are desirable, embodiments may limit direct preference input. For example, embodiments may incorporate hidden data fields that are entered indirectly as part of the registration process or other processes related to managing the user's account. Specifically, the interaction platform may obtain personalized data from another data source, for example, based on limited information provided by the guest. This process may include importing data from a third-party database associated with login authentication for the interaction system. In practice, such a data import step can be integrated with login authentication to further obfuscate the nature of the interaction and increase the potential for surprising guests with immersive and personal special effects at the amusement park.

[0018] According to this embodiment, the interaction platform's centralized login protocol can efficiently authenticate users and facilitate account setup. For example, a single sign-on procedure employed by the interaction platform can enable users to authenticate and / or create new accounts on a website or app associated with the interaction platform by linking to a previously established account on another (e.g., third-party) system with a familiar login identity and password. This procedure can be performed using a generic login application program interface (API) supported by the other system and accessible by the interaction platform. As anyone who has had to deal with login credentials for numerous accounts can appreciate, users may prefer this login method because it simplifies the handling of passwords and identification data by avoiding the need to create yet another set of credentials for specific websites or apps. This embodiment can facilitate this process by providing, via the interaction platform, a web or app tool (e.g., a button or other type of input) that functions to allow the user to select authentication via another system. Selecting this web or app tool, which may also be referred to as an interface tool, establishes or opens a link between the other system and the interaction platform, allowing the authentication information from the other system to be used to verify the user's authenticity. For example, a graphical user interface (GUI) window may open containing a prompt for entering authentication information for the other system, and upon successful authentication, the other system may provide an indication of the authentication to the interaction platform. Thus, embodiments may open a new account and / or provide an authenticated login for a website or app of the interaction platform based on approval of the other system or third-party system, without the website or app having to receive or store login credentials.It should be noted that to provide data security, some or all of the communications between the interaction platform and another system may be encrypted, and therefore each of these functions may be configured to decrypt the associated data.

[0019] In addition to performing authentication via a generic login API, this embodiment can also utilize communication between the interaction platform and another system (e.g., a third-party system) to obtain user data to be entered into hidden data fields within the interaction platform. Specifically, a communication protocol employed as part of the login process performed by the interaction platform and the other system can be used to communicate (e.g., scrape) user information from the other system, which can be employed to provide personalized special effects. Some information can be obtained directly through a website or app associated with the interaction platform, while some data fields can be hidden from guests to facilitate the provision of surprising interactions in the amusement park. For example, a user's nickname can be entered directly into the interaction platform via an exposed data field (e.g., a prompt input), while favorite color, favorite fictional character, or other available data can be obtained from another system's database and used to enter hidden fields in the interaction platform. In this embodiment, this action requires authorization, and various levels of authorization can be required. For example, different data types can be defined to obtain different permissions. Data may be divided into three or more levels or hierarchies, such as sensitive (e.g., passwords and social security numbers), basic (e.g., date of birth, eye color, height), and trivial (e.g., favorite planet, favorite color, lucky number). According to some embodiments, sensitive data is not transferred in this manner. Additionally, guests may also select what other data types, if any, may be transferred. For example, the interaction protocol app or website may provide a prompt that allows transfer of trivial data but not basic data. In other embodiments, general approval is provided for transfers and interactions with another system as part of the authorization to use another system in the login process. Once access permissions are confirmed, data transfers may be performed in a manner that limits the visibility of the data being transferred.The data obtained in this way for these hidden data fields can then be used in interactions within the amusement park to surprise and delight guests, providing a sense of immersion and wonder by hiding the origin of the data used for personalization, creating a sense of mystery.

[0020] FIG. 1 is a schematic diagram of an interaction platform 10 including a control center 12 and an interaction device 14 coupled to another system 16 for authentication and data provisioning services, according to one embodiment. The interaction platform 10 can be defined to include hardware 18 (e.g., one or more processors and memory) and software applications 20 that together support other applications, processes, devices, and technologies developed or utilized in connection with the interaction platform 10. In one embodiment, the interaction platform 10 includes an interaction device 14 that can reside within an amusement park 21. In one embodiment, the interaction platform 10 can simply include a control center 12 that includes computers and software (e.g., an operating system) that host a website (e.g., a registration website) and run an application (e.g., an application that manages special effects equipment) over one or more networks 22. Note that the interaction platform 10 can interface with another system 16 (or a third-party system 16) over a network (e.g., a public network) that is different from the network (e.g., a private and secure network) that the interaction platform 10 uses to interface with the interaction device 14. Like the interaction platform 10, the separate system 16 may also include its own hardware 18 and software applications 20. Although these components of the interaction platform 10 and the separate system 16 share reference numbers, they may be entirely separate functions.

[0021] The interaction platform 10 (e.g., the control center 12) and the other systems 16 may each include several components that facilitate these operations to perform some of the operations described in this disclosure. With this in mind, FIG. 1 includes example components within the interaction platform 10 and the other systems 16, according to embodiments described herein. Note that while the control center 12 and the other systems 16 each include their own distinct components, these components are similar in nature and are therefore identified with similar reference numerals. Specifically, the control center 12 and the other systems 16 may each include a communications component 30, a processor 32, memory 34, storage 36, input / output (I / O) ports 38, and a display 40, among others. The communications component 30 of the control center 12 may be a wireless or wired communications component that can facilitate communications with one or more networks 22. For example, the communications component 30 of the control center 12 may function to communicate with another system 16 to retrieve data from a third-party database 44, to communicate with a guest's computer system 46 to set up an account, or to communicate with any other device accessible via one or more networks 22. Specifically, the control center 12 may communicate with another system 16 to utilize a generic login API 41 stored therein.

[0022] It should be noted that the processor 32 may be any type of computer processor or microprocessor capable of executing computer-executable code. Furthermore, the processor 32 of the control center 12 may represent or include multiple processors that are part of the control center 12 and capable of performing the processing operations described herein. The memory 34 and storage 36 may be any suitable article of manufacture capable of serving to store processor-executable code, data, or the like. These articles of manufacture may represent computer-readable media (e.g., any suitable form of memory or storage) capable of storing processor-executable code used by the processor 32 to perform the techniques of this disclosure. The memory 34 and storage 36 may also store data, analysis results of acquired data, various software applications, and the like. It should be noted that the term "non-transitory" merely indicates that the medium is tangible and not a signal.

[0023] The I / O ports 38 may be interfaces that can be coupled to communication functions or peripheral components, such as input devices (e.g., keyboards, laser scanners, mice, microphones), sensors, input / output (I / O) modules, output devices (e.g., interface devices 14), and the like. In some embodiments, the control center 12 may include one or more programmable logic controllers (PLCs) that include I / O ports 38 that facilitate communication coupling to the interaction devices 14. The one or more PLCs may be part of the control center 12 or may be coupled to a central control terminal or operator station in the control center 12 via the I / O ports 38. According to this embodiment, such a configuration may provide automated control functions from the control center 12 (e.g., the operator station and one or more PLCs) to the interaction devices 14. In some embodiments, a display 40 may be part of the central control terminal. The display 40 may be operable to portray visualizations associated with software or executable code being processed by the processor 32. The display 40 may be any suitable type of display, such as, for example, a liquid crystal display (LCD), a plasma display, or an organic light-emitting diode (OLED) display. Additionally, in one embodiment, the display 40 may be provided with touch-sensitive features (eg, a touch screen).

[0024] It should be noted that the components described above with respect to interaction platform 10 are exemplary components, and interaction platform 10 may include additional or fewer components than those illustrated. Also, guest computer systems 46 (e.g., mobile computers, mobile devices, or desktop computers) with which interaction platform 10 is configured to communicate may include components similar to those described as part of control center 12 and other systems 16. Furthermore, aspects of interaction platform 10 and / or other systems 16 may include or interface with cloud-based computer systems or servers, or the like.

[0025] 1 shows guests or other users 52 (e.g., reservation agents) using guest computer systems 46 to communicate with the interaction platform 10 to set up or manage their accounts. One of the users 52 communicates with the interaction platform 10 using a mobile device 54, while the other user 52 communicates with the interaction platform 10 using a desktop computer 55. However, the users 52 may interface with the interaction platform 52 using any of a variety of different computer-based technologies. In either case, a graphical user interface (GUI) 56 may be provided for display on the user's computer system 46 to facilitate account management. As described in further detail below, the GUI 56 may facilitate entry of an account identification (ID) (e.g., the user's email address) and enable registration via another system 16.

[0026] The control center 12 may include a database 62 having numerous data fields 64. Some of these data fields 64 may be forward-facing data fields 66, and some may be hidden data fields 68. For example, the forward-facing data fields 66 may include data fields for establishing a user account (e.g., entering a user ID such as an email address), while the hidden data fields 68 may include data fields for user preferences. The forward-facing data fields 66 may be entered directly into the control center 12 via a guest computer system 46. For example, upon connecting to the interaction platform 10, the user computer system 46 may be provided with a GUI 56 having a prompt for entering a new or existing user identification. When user identification such as an email address and / or facial recognition data is provided via the GUI 56, the fields in the forward-facing data fields 66 for storing the user identification may be filled in. On the other hand, the hidden data fields 68 may be filled indirectly. Specifically, the hidden data fields 68 of the control center 12 may be filled from data fields 72 corresponding to users in a database 73 residing in another system 16. For example, upon selection of authentication via another system 16 and approval of information sharing between the interaction platform 10 and another system 16, user data available in the other system 16 can be imported or otherwise entered into the hidden data field 68. This entry can occur in conjunction with the authentication process. For example, the data for the hidden data field 68 can be provided in parallel or serially with the authentication credentials. To maintain private interactions, the data for the hidden data field 68 and the communication of the authentication data can be encrypted.

[0027] Once the associated user data is entered into the hidden data field 68, the interaction platform 10 (e.g., processors and algorithms in the control center 12) can use this associated user data to identify guest characteristics, preferences, and the like. Furthermore, the interaction platform 10 can utilize this personalization data (e.g., preferences and characteristics) to provide effects within the amusement park that are tailored to provide fun and enjoyment to individual guests. For example, the interaction platform 10 can include or communicate with a guest identification system 78. The guest identification system 78 can include a camera, a signal detector (e.g., a radio frequency identification (RFID) detector, an integrated global positioning satellite (GPS) detector), or some other guest identification mechanism (e.g., a feature incorporated into one of the interaction devices 14 configured to detect use by a particular guest). Upon identifying that a guest is present at a particular location near one of the interaction devices 14 or is actively engaged with a particular one of the interaction devices 14 (e.g., virtual reality goggles), the interaction platform 10 can control the interaction device 14 (or multiple such devices) based on the personalization data stored in the hidden data field 68. For example, the interaction devices 14 may include a drone 82, virtual reality goggles 84, an animated figure 86, an interactive display 88, or an interactive fountain 90, etc. Furthermore, each of the interaction devices 14 can be designed to perform personalized actions based on data from the hidden data field 68, as commanded by the interaction platform 10 (e.g., the control center 12). For example, in one embodiment, the drone 82 and the fountain 90 can provide lighting effects that heavily incorporate the guest's favorite colors (e.g., the colors of the user's favorite sports team). As another example, the animated figure 86 can be operable to adjust its gaze direction based on data indicating the guest's height.As yet another example, the virtual reality goggles 84 and / or interactive display 88 may provide virtual environments and virtual characters that match the guest's thematic preferences or the guest's fictional character preferences.

[0028] 2 is a schematic perspective view of a guest 102 at an amusement park venue 104 with the interaction platform 10 operating to provide special effects tailored to the guest 102, in accordance with an embodiment of the present disclosure. In the illustrated embodiment, the interaction platform 10 identifies the guest's presence within the venue 104 using a combination of facial recognition and RFID detection. Specifically, the camera 105 operates to detect facial features of the guest 102 and compares these facial features with user data (e.g., an image provided upon entry to the venue 104) stored in the control center 12, such as in the forward-looking data fields 66. The facial identification data stored in these forward-looking fields 66 may have been provided by the guest 102 via a camera on the guest's computer system 46 during the registration process. In this regard, the RFID tag 108 worn and associated with the guest 102 (e.g., associated with a guest account based on the serial number of the RFID tag 108) is detected by the RFID detector 110. The camera 105, the RFID detector 110, and / or the RFID tag 108 may be considered features of the guest identification system 78. However, in some embodiments, only one technology (e.g., facial recognition or signal detection) may be used to identify the location / presence of a guest. Once a guest 102 is identified and associated with an account (e.g., via forward-looking data field 66 and / or hidden data field 68), data from hidden data field 68 may be employed to utilize the guest's 102 preferences in providing special effects. For example, in the illustrated embodiment, guest 102 may prefer a cowboy-themed environment over a medieval-themed environment. Thus, as shown, an animated figure of a cowboy 122 may be positioned on turntable 124 and visible to guest 102 instead of an animated medieval knight figure 126.

[0029] FIG. 3 is a block diagram of an interaction process 198 between a user computer system 46, the interaction platform 10 (e.g., the control center 12), another system 16, and an interaction device 14, according to an embodiment of the present disclosure. In the exemplary embodiment of FIG. 3, the control center 12 initiates contact with the other system 16 based on instructions from a user obtained via communication from the user computer system 46. For example, a user may interface with the control center 12 via a user computer system 46 communicatively coupled to the control center 12 (e.g., via a network) by requesting access to an account via the GUI 56. Specifically, the user may select to use login credentials from the other system 16 as a component of requesting access to an account via the GUI 56. This selection may include activating a web app or tool, such as a soft button on the GUI 56, that initiates communication with the other system 16 regarding the requested account. Initial input 200 provided by the user via the GUI 56 may include an account identifier (e.g., an email address) and a selection of an option to use the other system 16 for authentication, which may include use of the generic login API 41. In some embodiments, the user-entered account identifier may not be provided until the user interfaces with another system 16. For example, to begin the process, the request for access to a new or existing account may simply be assigned an automatically generated account number. In any event, after the control center 12 processes the initial input 200 indicating that the user is requesting access to a new or existing account, an initial communication 202 is provided from the control center 12 to the other system 16. This initial communication 202 includes data indicating a request to coordinate user authentication information from the other system 16 to open or otherwise access an account in the control center 12 (e.g., using the generic login API 41).

[0030] In the exemplary embodiment of FIG. 3 , upon receiving the initial communication 202, the other system 16 requests authentication of the user in an authentication request 204. While the authentication request 204 is shown as being passed from the other system 16 to the user computer system 46 via the control center 12, in other embodiments, a direct communication can be established, or the control center 12 or GUI 56 can initially prompt for and provide the information necessary for authentication to the other system 16 via the initial communication 202. In the illustrated embodiment, authentication data (e.g., a password) 208 is provided from the user computer system 46 via the control center 12 back to the other system 16. This authentication data 208 can also include permissions enabling access to other data (e.g., trivial or basic user data), although such permissions can also be provided in the initial communication 202. According to this embodiment, communication of the authentication data 208, like the authentication request 204, can utilize paths other than those shown (e.g., a direct communication line between the user computer system 46 and the other system 16).

[0031] Once another system 16 receives and approves the authentication data 208 (via the generic login API 41), it can provide the authentication and approval data 212 to the control center 12 to open or enable access to the account associated with the authentication and approval data 212. In the illustrated embodiment, hidden data 216 is also provided along with the authorization data 212. The hidden data 216 can be provided integrally with, embedded in, in parallel with, serially with, or otherwise associated with the authorization data 212. Additionally, all or a portion of the data can be encrypted. For example, the authorization data 212 and / or the hidden data 216 can be encrypted. In other embodiments, the hidden data 216 is provided in a separate communication after the authorization data 212. The hidden data 216 can include specific data, such as basic data (e.g., date of birth) or trivial data (e.g., favorite color), about the user of the account associated with the authentication and approval data 212. The type or nature of the hidden data 216 provided can depend on the nature of the communication approved by the user (e.g., as indicated via the GUI 56). For example, a user may indicate that only trivial data may be shared between the interaction platform 10 and another system 16. Transferring hidden data 216 in this manner makes the transfer of data less noticeable to the user, making it easier to surprise the user later via the interaction device 14.

[0032] Once the hidden data 216 and the authentication authorization data 212 are provided to the control center 12, the control center 12 can open and / or access the user's account and enter the hidden data 216 into the account. Furthermore, the hidden data 216 can be employed for special effects, etc. Specifically, the control center 12 can utilize the hidden data 216 to control the interaction device 14. By way of example, and referring again to FIG. 1 , the control center 12 can control the virtual reality goggles 84 to display a virtual reality experience corresponding to the user's preferences found in the hidden data 216. Specifically, in a virtual haunted house, for example, because the user indicated a preference for werewolves in the horror genre, the control center 12 can control the virtual reality goggles to present images corresponding to werewolves rather than other options (e.g., ghosts or zombies). Obscuring or concealing the acquisition of such preferences through the transmission of the hidden data 216 in a disclosing manner can add an element of surprise to the amusement park experience, such as by providing an experience tailored to the user's preferences or characteristics. The surprising interaction may also include providing information about the user from the interaction device 14. For example, an animated figure 86 dressed as a fortune teller may surprise and delight the user by telling them the zodiac sign associated with their date of birth.

[0033] 4 is a schematic diagram of interaction with a GUI 56 according to an embodiment of the present disclosure. In response to initiating contact with the control center 12 to open or access a user account, a first GUI 302 may be provided via the display of the user computer system 46. The first GUI 302 includes prompts for the user to provide identification, specifically a prompt for an email address 304 and a prompt for a subject name 306 (e.g., a nickname or username). Additionally, the first GUI 302 provides a prompt 308 to approve or a prompt 310 to decline use of another system 16 for authentication purposes. These and other prompts may also be included to facilitate or add dimensions to the disclosed interactions. Prompts may include inputs for data entry, toggle buttons, radio buttons, and other interface tools, etc.

[0034] If the user declines to use another system 16 for authentication purposes by selecting the decline prompt 310, a personalization GUI 312 may be provided on the user computer system 46 to allow the user to directly input preferences and characteristics. This results in desired information about the user for use within the amusement park via the interaction device 14, but the acquisition of this data is not hidden, thus limiting the surprise. Such data may be gleaned from questions posed by the personalization GUI 312 that are intended to conceal the acquisition of relevant data. However, a knowledgeable user may recognize the intent of the questions. In some embodiments, the user may decline to use another system 16 for authentication but permit data sharing between the other system 16 and the interaction platform 10 (e.g., the control center 12). After engaging with the personalization GUI 312, a login credential request GUI 314 may be presented on the user computer system 46 to verify the user's authenticity and open or access the user account.

[0035] If the user accepts the use of another system 16 for authentication purposes by selecting the prompt 308 for approval, an access permission GUI 318 may be provided via the user computer system 46. The access permission GUI 318 may provide an access permission prompt 322 that allows the user to indicate whether data other than that required for authorization can be shared from the other system 16 with the interface platform 10. Providing this access permission prompt 322 may further prompt the type of data that can be shared, such as whether only trivial data can be shared or whether additional data can be shared. As described above, allowing this data sharing may provide hidden data 216 to the control center 12 for the purpose of surprising guests through interactions within the amusement park. If access permission is accepted, a login credential request GUI 314 may be provided immediately via the user computer system 46. If access permission is denied, a personalization GUI 312 may be presented, and the login credential request GUI 314 may be provided upon completion of the personalization GUI 312.

[0036] While only a few features and embodiments have been shown and described, it is anticipated that numerous modifications and variations will occur to those skilled in the art, such as changes in the size, dimensions, structure, shape, and proportions of various elements, parameter values, attachment methods, use of materials, color, and orientation, without substantially departing from the novel teachings and advantages of the claimed subject matter. The order or sequence of any process or method steps may be changed or re-sequenced according to alternative embodiments. It is therefore to be understood that the appended claims are intended to cover all such modifications and variations within the true spirit of the present disclosure. Moreover, in an effort to concisely describe exemplary embodiments, not all features of an actual implementation, such as those not related to the best mode currently contemplated or not related to feasibility, may be described. It is to be understood that numerous implementation-specific decisions may be made in the development of any such implementation, as in any engineering or design project. While such a development effort may be complex and time-consuming, for those of ordinary skill in the art having the benefit of this disclosure, it will be a routine undertaking of design, fabrication, and manufacture without undue experimentation. [Explanation of symbols]

[0037] 10 Interaction Platform 12 Control Center 14 Interaction device 16 Another System 18 Hardware 20 Software Applications 21. Amusement Park 22 Network 30 Communication Components 32 processors 34 memory 36 Storage 38 Input / Output (I / O) ports 40 Display 41 General-purpose login API 44 Third-Party Databases 46 Guest Computer Systems 52 users 54 Mobile Devices 55 Desktop Computers 56 Graphical User Interface 62 databases 64 Data Fields 66 Forward-looking data field 68 Hidden Data Fields 72 Data Fields 73 databases 78 Guest Identification System 82 Drone 84 Virtual Reality Goggles 86 Anime Figures 88 Interactive Displays 90 Interactive Fountain

Claims

1. 1. An interactive platform for controlling interactive functions in an amusement park, comprising: a control center; receiving an account request from a user computer system; populating positive data fields based on user input from said user computer system; Coordinating authentication of the account request with another system configured to share authentication data utilizing a login application programming interface; receiving the authentication data from the other system and providing access to the user account based on the authentication data; populating hidden data fields in the control center based on user data provided by the other system; The interaction platform is configured to:

2. the control center is configured to receive the authentication data and the user data in parallel from the other system. The interaction platform according to claim 1 .

3. the control center is configured to receive the user data embedded in the authentication data; The interaction platform according to claim 1 .

4. the control center is configured to restrict the user data received from the other system based on a type of the user data; The interaction platform according to claim 1 .

5. the control center is configured to block a sensitive portion of the user data while allowing a trivial portion of the user data to be received, the sensitive portion and the trivial portion being defined by one or both of the control center and the other system; The interaction platform according to claim 4.

6. the control center is configured to use user input to determine the types of user data provided by the other system that the control center will accept and / or reject; The interaction platform according to claim 4.

7. one or more interface devices in an amusement park environment configured to be controlled by the control center based on the user data; The interaction platform according to claim 1 .

8. the control center includes a programmable logic controller; The interaction platform according to claim 7.

9. the one or more interface devices include virtual reality glasses, augmented reality glasses, a display screen, an animated figure, a ride-on vehicle, or a combination thereof; The interaction platform according to claim 7.

10. a guest identification system configured to detect guests within the amusement park and communicate an indication of the presence of the guests to the control center; The interaction platform according to claim 1 .

11. the control center is configured to associate the presence of the guest with the guest data and to control at least one interface device based on the guest data while the guest is present within the amusement park venue. The interaction platform according to claim 10.

12. the control center is configured to receive the authentication data and the user data as encrypted data; The interaction platform according to claim 1 .

13. 1. A method for authentication and entry of hidden data fields that facilitates control of an interactive device in an amusement park environment, comprising: receiving an account request from a user computer system at a control center; populating forward data fields of the control center based on user input from the user computer system; the control center coordinating authentication of the account request with another system configured to share authentication data utilizing a login application programming interface; receiving, at the control center, the authentication data from the other system and providing access to the user account of the user computer system based on the authentication data; populating hidden data fields in the control center based on user data provided by the other system; A method comprising:

14. receiving and decrypting, at the control center, the user data provided by the other system; The method of claim 13.

15. providing a graphical user interface from the control center to the user computer system for obtaining the user input for entering the forward data fields; The method of claim 13.

16. requesting, via the graphical user interface, permission to share at least one type of data between the control center and the other system.

16. The method of claim 15.

17. controlling one or more interaction devices from the control center based on data in at least one of the hidden data fields. The method of claim 13.

18. the data in the at least one of the hidden data fields includes user preferences, user characteristics, or a combination thereof.

18. The method of claim 17.

19. 1. A system for inputting hidden data fields and controlling interactive experiences at an amusement park based on said hidden data fields, comprising: another system configured to share authentication data utilizing a login application programming interface; The control center and one or more interactive devices located within the amusement park; The control center comprises: receiving an account request from a user computer system and populating prospective data fields based on said user input from said user computer system; coordinating authentication of the account request with the other system in conjunction with the login application programming interface; receiving the authentication data from the other system and providing access to the user account based on the authentication data; populating the hidden data fields of the control center based on user data provided by the other system; wherein the one or more interaction devices are configured to be controlled by the control center based on the user data. A system characterized by:

20. a user identification system disposed within the amusement park and configured to activate the control center to control the one or more interaction devices based on detection of a user associated with the user data; 20. The system of claim 19.

Images