Patent Description:
The subject matter disclosed herein relates to amusement parks, and more specifically, to providing enhanced entertainment and components of interest in amusement parks.

Amusement parks and/or theme parks may include various entertainment attractions (e.g., restaurants, rides, and shows) useful in providing enjoyment to guests or patrons of the amusement park. For example, the attractions may include traditional rides for kids, such as carousels, as well as traditional rides for thrill seekers, such as rollercoasters. It is now recognized that adding components of interest and thrill factors to such attractions and other areas of an amusement park can be difficult. In particular, including features that facilitate emersion of the guest in an experience and that provoke guests to feel that they have experienced something truly magical is a challenge.

It is now recognized that patrons often have a preference for personalized experiences. Further, it is also recognized that, with increased availability of technology and information via the internet, patrons are also more educated and tech-savvy with respect to how special effects are generated and information is obtained. This can make it difficult to provide experiences that feel magical because the techniques and mechanisms behind the experience can be readily identified. Accordingly, it is now recognized that it is desirable to include components of interest in a personalized, efficient and surprising manner relative to traditional techniques.

<CIT> describes a method for operating a ride attraction that includes directing a rider to a kiosk or a mobile application on a smart phone, with the rider creating a character profile or accessing his/her previously created character profile. The rider is assigned to a ride vehicle or to a seat in a ride vehicle. The rider boards the into or onto the assigned vehicle or seat. The ride vehicle moves along a path in the ride attraction. At least one of the path, special effects, onscreen graphics and scoring may be modified according to the rider's character. A mobile application gameplay may unlock specified game features to change a ride experience.

Certain embodiments commensurate in scope with the present disclosure are summarized below. These embodiments are not intended to limit the scope of the disclosure which is determined by the appended claims, but rather these embodiments are intended only to provide a brief summary of possible forms of present embodiments.

In an embodiment, an interactive platform for populating hidden data fields and controlling interactive features based on the hidden data fields is provided in an amusement park. 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.

In an embodiment, a method of authentication and population of hidden data fields to facilitate control of interactive devices in an amusement park setting is provided.

The method includes receiving an account request at a control center from a user computer system, populating forward facing data fields of the control center based on user inputs from the user computer system. Further, the method includes coordinating, by the control center, authentication of the account request with a separate system configured to utilize a login application programming interface to share authentication data, receiving, at the control center, the authentication data from the separate system and providing access to a user account for the user computer system based on the authentication data, and populating hidden data fields of the control center based on user data provided by the separate system.

Present embodiments are directed to improving guest experiences at an amusement park. An amusement park may include a ride, a mall of amusement park facilities (e.g., restaurants, souvenir shops, and shows), an assembly of amusement attractions (e.g., Ferris Wheel, dark ride, or other attraction), and so forth. In certain embodiments, a ride may include a rollercoaster, dark ride or other similar ride-based experience, and may thus further include a ride path that a passenger ride vehicle traverses during operation. It should be appreciated that while the passenger ride vehicle is in operation, present embodiments may be utilized to enhance the experience of guests on the ride vehicle. Likewise, present embodiments may be utilized to enhance guest experiences throughout the amusement park, even while the guest is simply traveling between locations within the amusement park. It should be noted that the term guest is used throughout this disclosure to reference users of disclosed systems and methods. While the term guest is frequently used, other types of users are contemplated. For example, present embodiments include systems and techniques for guest registration; and it is presently contemplated that non-guest users may employ such registration systems and techniques on behalf of a guest or future guest. Further, the term user may be interchangeable with the word guest for certain aspects of the disclosure. Accordingly, it should be understood that the disclosed examples are not limiting and that the term guest may broadly represent any of various users and user-types.

Present embodiments relate to systems and methods of providing an interactive platform or interactive platform system for providing guest experiences at an amusement park (e.g., a theme park). The interactive platform may facilitate provision of tailored experiences, such as games and effects, that appeal to guests individually and allow for increased interaction between guests and park features (e.g., rides, shows, decorations, animated figures, interactive screens), other guests, costumed characters, and so forth. For example, the interactive platform may coordinate with electronic goggles, electronic eyeglasses, projection screens, or the like to provide a specialized augmented reality (AR) experience, virtual reality (VR) experience, or mixed reality (e.g., a combination of AR and VR) experience as part of an attraction, such as a thrill ride, in an amusement park. The interactive platform may also interface with more tangible entertainment features, such as animated figures, fountains, or costume components, to provide experiences based on individual preferences, characteristics, or other information about a particular guest that is available to the interactive platform.

Present embodiments may include a portal (e.g., a website or app) that allows guests to register with the interactive platform. The registration process may be utilized to obtain data about each guest that can be used within the amusement park environment to provide customized entertainment enhancements. For example, the registration process may include provision of guest access to data fields along with requests to populate the data fields with user information, such as favorite color, birthdate, height, and so forth. These data fields may then be used to control interactions, such as an augmented reality laser beam having the user's favorite color, an animated figure adjusted to appear as though looking into the user's eyes based on the user's height, or a customized dialogue that mentions the user's birthdate. The registration process may be a component of a larger process or include a sub-process for obtaining tickets, making reservations, assembling a schedule of events, or other such activities in relation to the amusement park. For example, a guest may login and register via an app stored on a mobile device (e.g., a smart phone or smart watch) to obtain tickets to enter the park and to schedule certain events (e.g., rides, restaurant reservations, park area entry, or shows). As part of this registration process, login credentials may be required. While the interactive platform may certainly provide for internal generation of new login credentials (e.g., a new user identification and password) separate from any other account, the interactive platform may also allow for coordination with a separate account and a separate system. For example, the interactive platform may allow for a login based on a separately established third-party account that already has established login credentials. In some embodiments, the user may create new login credentials and use the separately established third-party account. For example, the user may provide a user name (e.g., a themed name) for the new account but still use the login credentials from the established third-party account.

Embodiments of the interactive platform may enable direct entry of personal information into data fields when populating a database with personalized information about a user. However, this type of input may alert savvy guests to the nature of park interactions that are intended to entertain the guest partially through the surprise of personalization. For example, if a user indicates a particular preference (e.g., a user's favorite planet is Saturn) and that preference is manifested in a special effect provided for the guest (e.g., a surprise simulation of the guest traveling to Saturn) in the amusement park, it may be apparent to the guest that the source of the preference was the registration process, which may eliminate mystery from the experience. Because mystery and seemingly magical aspects of an interaction are desirable, present embodiments may limit direct input of preferences. For example, present embodiments may incorporate hidden data fields that are indirectly populated as part of a registration process or other process associated with managing a user's account. Specifically, for example, based on limited information provided by a guest, the interactive platform may obtain personalization data from a separate data source. This may include importing data from a third-party database associated with a login authentication for the interactive system. In fact, such a data importing step may be integrated with the login authentication to further obfuscate the nature of the interaction and increase the potential for surprising the guest with immersive and personal special effects in the amusement park.

In accordance with present embodiments, a centralized login protocol for the interactive platform may provide efficient authentication of users and facilitate account setup. For example, by linking to a previously established account on a separate (e.g., third-party) system, which has a familiar login identity and password, a single sign-on procedure employed by the interactive platform may allow a user to authenticate and/or create a new account on a website or app associated with the interactive platform. This may be achieved using a universal login application program interface (API) supported by the separate system and accessible to the interactive platform. As can be appreciated by anyone that has to deal with login credentials for numerous accounts, users may prefer this manner of login because it simplifies the handling of passwords and identification data by avoiding the creation of yet another set of credentials for a specific website or app. Present embodiments may facilitate this process by offering a web or app tool (e.g., a button or other type of input) via the interactive platform, wherein the web or app tool functions to allow the user to select verification via the separate system. Upon selection of this web or app tool, which may be referred to as an interface tool, a link between the separate system and the interactive platform may be established or opened such that credentials from the separate system may be used to verify authenticity of the user. For example, a window in a graphical user interface (GUI) may be opened with a prompt to enter credentials for the separate system and, upon successful authentication, the separate system may provide an indication of authentication to the interactive platform. Thus, present embodiments may open a new account and/or provide an authenticated login for a website or app of the interactive platform based on the approval of a separate or third-party system without the need for the website or app to receive or store login credentials. It should be noted that some or all of the communication between the interactive platform and the separate system may be encrypted to provide data security. Thus, each of these features may be configured to decrypt the relevant data.

In addition to providing authentication via the universal login API, present embodiments may utilize communication between the interactive platform and the separate system (e.g., third-party system) to obtain user data to populate hidden data fields in the interactive platform. Specifically, user information that can be employed to provide individualized special effects may be communicated (e.g., scraped) from the separate system using a communication protocol that is employed as part of the login process performed by the interactive platform and the separate system. While some information may be directly obtained via the website or app associated with the interactive platform, certain data fields may be hidden from the guest to facilitate provision of surprise interactions in the amusement park. For example, a user's nickname may be entered directly into the interactive platform via revealed data fields (e.g., prompted entries) while a favorite color, favorite fictional character, or other available data may be obtained from a database of the separate system and used to populate hidden fields of the interactive platform. In present embodiments, this action requires approval and may require varying levels of approval. For example, different types of data may be defined and separate permissions obtained. Data may be divided into three or more levels or tiers, such as confidential (e.g., password and social security number), fundamental (e.g., birthdate, eye color, and height), and trivial (e.g., favorite planet, favorite color, and lucky number). In accordance with an embodiment, no confidential data will ever be transferred in this manner. Further, a guest may be allowed to select other types of data (if any) that may be transferred. For example, an app or website of the interactive protocol may provide a prompt that allows for the transfer of trivial data but not fundamental data. In other embodiments, a general approval is provided for transfer and interaction with the separate system as part of allowing use of the separate system in the login process. Once permission for access is confirmed, transfer of data may then be performed in a manner that limits the visibility of the data being transferred. Thus, data obtained for these hidden data fields in this manner can be used in interactions in the amusement park to surprise and delight the guest. By concealing the origin of the data used for personalization, an immersive and magical feel may be provided and a sense of mystery generated.

<FIG> is a schematic representation of an interactive platform <NUM> including a control center <NUM> and interactive devices <NUM>, wherein the interactive platform <NUM> is coupled to a separate system <NUM> for authentication and data provision services in accordance with an embodiment. The interactive platform <NUM> may be defined as including hardware <NUM> (e.g., one or more processors and memories) and software applications <NUM> that are used together as support for other applications, processes, device, technologies, and the like that are developed or utilized in conjunction with the interactive platform <NUM>. In one embodiment, the interactive platform <NUM> includes the interactive devices <NUM>, which may reside within an amusement park <NUM>. In one embodiment, the interactive platform <NUM> may simply include the control center <NUM>, which may include a computer and software (e.g., an operating system) that hosts websites (e.g., a registration website) and runs applications (e.g., applications that manage special effects devices) over one or more networks <NUM>. It should be noted that the interactive platform <NUM> may interface with the separate system <NUM> (or third-party system <NUM>) over a different network (e.g., a public network) than the network (e.g., a private and secured network) that the interactive platform <NUM> uses to interface with the interactive devices <NUM>. Like the interactive platform <NUM>, the separate system <NUM> may also include its own hardware <NUM> and software applications <NUM>. While these components of the interactive platform <NUM> and the separate system <NUM> share reference numbers, they may be completely separate features.

To perform some of the operations described in the present disclosure, the interactive platform <NUM> (e.g., the control center <NUM>) and the separate system <NUM> may each include certain components to facilitate these operations. With this in mind, <FIG> includes example components within the interactive platform <NUM> and the separate system <NUM>, in accordance with embodiments described herein. It should be noted that each of the control center <NUM> and the separate system <NUM> includes its own separate components but the components are similar in nature and are, thus, identified with like reference numerals. Specifically, each of the control center <NUM> and the separate system <NUM> may respectively include a communication component <NUM>, a processor <NUM>, a memory <NUM>, a storage <NUM>, input/output (I/O) ports <NUM>, a display <NUM>, and the like. The communication component <NUM> of the control center <NUM> may be a wireless or wired communication component that may facilitate communication using the one or more networks <NUM>. For example, the communication component <NUM> of the control center <NUM> may function to communicate with the separate system <NUM> to obtain data from a third-party database <NUM>, communicate with a guest's computing system <NUM> to set up an account, or communicate with any other device accessible via the one or more networks <NUM>. In particular, the control center <NUM> may communicate with the separate system <NUM> to utilize a universal login API <NUM> stored thereon.

It should be noted that the processor <NUM> may be any type of computer processor or microprocessor capable of executing computer-executable code. Further, the processor <NUM> of the control center <NUM> may be representative of or include multiple processors that are part of the control center <NUM> and that may perform processing operations herein described. The memory <NUM> and the storage <NUM> may be any suitable article of manufacture that can serve 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) that may store the processor-executable code used by the processor <NUM> to perform the presently disclosed techniques. The memory <NUM> and the storage <NUM> may also store data, results from analysis of acquired data, various software applications, and the like. It should be noted that non-transitory merely indicates that the media is tangible and not a signal.

The I/O ports <NUM> may be interfaces that may couple to communication features or peripheral components such as input devices (e.g., keyboard, laser scanner, mouse, microphone), sensors, input/output (I/O) modules, output devices (e.g., the interface devices <NUM>) and the like. In an embodiment, the control center <NUM> may include one or more programmable logic controllers (PLCs) that include the I/O ports <NUM>, which facilitate communicative coupling to the interactive devices <NUM>. The one or more PLCs may be part of the control center <NUM> and may also couple with a central control terminal or an operator station of the control center <NUM> via the I/O ports <NUM>. Such an arrangement may provide automation control functionality from the control center <NUM> (e.g., the operator station and the one or more PLCs) to the interactive devices <NUM> in accordance with present embodiments. In an embodiment, the display <NUM> may be part of the central control terminal. The display <NUM> may operate to depict visualizations associated with software or executable code being processed by the processor <NUM>. The display <NUM> may be any suitable type of display, such as a liquid crystal display (LCD), plasma display, or an organic light emitting diode (OLED) display, for example. Additionally, in one embodiment, the display <NUM> may be provided in conjunction with a touch-sensitive mechanism (e.g., a touch screen).

It should be noted that the components described above with regard to the interactive platform <NUM> are exemplary components and the interactive platform <NUM> may include additional or fewer components relative to what is shown. Additionally, it should be noted that a guest's computing system <NUM> (e.g., mobile computer, mobile device, or desktop computer) that the interactive platform <NUM> is configured to communicate with may include components similar those described as part of the control center <NUM> and the separate system <NUM>. Further still, it should be noted that aspects of the interactive platform <NUM> and/or separate system <NUM> may include or work in conjunction with a cloud-based computing system, server, or the like.

In <FIG>, guests or other users <NUM> (e.g., booking agents) are depicted as communicating with the interactive platform <NUM> using guest computing systems <NUM> to setup or manage an account. One of the users <NUM> is communicating with the interactive platform using a mobile device <NUM> and the other user <NUM> is communicating with the interactive platform using a desktop computer <NUM>. However, any of various different computer-based technologies may be used by the users <NUM> to interface with the interactive platform <NUM>. In each case, a graphical user interface (GUI) <NUM> may be provided for display on the user's computing system <NUM> to facilitate account management. As will be discussed in further detail below, the GUI <NUM> may facilitate input of an account identification (ID) (e.g., a user's email address) and allow for registration via the separate system <NUM>.

The control center <NUM> may include a database <NUM> with numerous data fields <NUM>. Some of these data fields <NUM> may be forward facing data fields <NUM> and some are hidden data fields <NUM>. For example, the forward facing data fields <NUM> may include a data field for establishing a user account (e.g., inputting a user ID, such as an email address), and the hidden data fields <NUM> may include data fields for user preferences. The forward facing data fields <NUM> may be populated directly into the control center <NUM> via the guest computing system <NUM>. For example, upon connecting with the interactive platform <NUM>, the GUI <NUM> may be provided to the user computing system <NUM> with a prompt for entering a new or existing user identification. When the user identification, such as an email address and/or facial recognition data, is provided via the GUI <NUM>, one of the forward facing data fields <NUM> for storing the user identification may be populated. The hidden data fields <NUM>, on the other hand, may be indirectly populated. Specifically, the hidden data fields <NUM> of the control center <NUM> may be populated from data fields <NUM> of a database <NUM> present in the separate system <NUM> that correspond to the user. For example, upon selection of authentication via the separate system <NUM> and approval of information sharing between the interactive platform <NUM> and the separate system <NUM>, user data available in the separate system <NUM> may be imported or otherwise entered into the hidden data fields <NUM>. This may be done in conjunction with the authentication process. For example, the data for the hidden data fields <NUM> may be provided in parallel or in series with authentication credentials. The communication of the data for the hidden data fields <NUM> and the authentication data may be encrypted to maintain a private interaction.

Once the hidden data fields <NUM> are populated with the relevant user data, the relevant user data may be used by the interactive platform <NUM> (e.g., a processor and algorithm of the control center <NUM>) to identify characteristics, preferences, and so forth of a guest. Further, this personalized data (e.g., preferences and characteristics) may be utilized by the interactive platform <NUM> to provide effects in an amusement park that are tailored to entertain and delight individual guests. For example, the interactive platform <NUM> may include or communicate with a guest identification system <NUM>. The guest identification system <NUM> may include a camera, a signal detector (e.g., radio-frequency identification (RFID) detector, an integral global positioning satellite (GPS) detector), or some other guest identification mechanism (e.g., a feature built into one of the interactive devices <NUM> configured to detect use by a particular guest). When a guest is identified at a particular location proximate one of the interactive devices <NUM> or as actually interfacing with a particular device of the interactive devices <NUM> (e.g., virtual reality goggles), the interactive platform <NUM> may control the interactive device <NUM> (or multiple such devices) based on the personalized data stored in the hidden data fields <NUM>. For example, the interactive devices <NUM> may include a drone <NUM>, virtual reality goggles <NUM>, an animated figure <NUM>, an interactive display <NUM>, an interactive fountain <NUM>, or the like. Further, as instructed by the interactive platform <NUM> (e.g., the control center <NUM>), each of the interactive devices <NUM> may designed to perform a personalized action based on data from the hidden data fields <NUM>. For example, in an embodiment, the drone <NUM> and fountain <NUM> may 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 <NUM> may be operated to adjust a gaze based on data indicative of the guest's height. As yet another example, the virtual reality goggles <NUM> and/or the interactive display <NUM> may provide a virtual environment and virtual characters that align with a theme preference or fictional character preference of the guest.

<FIG> is a schematic perspective view of a guest <NUM> in an amusement park venue <NUM>, wherein the interactive platform <NUM> is operating to provide a tailored special effect for the guest <NUM> in accordance with an embodiment of the present disclosure. In the illustrated embodiment, the interactive platform <NUM> has identified the guest as being present in the venue <NUM> using a combination of facial recognition and RFID detection. Specifically, a camera <NUM> operates to detect facial features of the guest <NUM> and those facial features are being compared with user data stored in the control center <NUM>, such as in the forward facing data fields <NUM> (e.g., an image provided upon entry to the venue <NUM>). The facial identification data stored in these forward facing fields <NUM> may have been provided by the guest <NUM> during a registration process via a camera on the guest's computing system <NUM>. In conjunction with this, a RFID tag <NUM> being worn and associated with the guest <NUM> (e.g., associated with a guest account based on serial number of the RFID tag <NUM>) is being detected by an RFID detector <NUM>. The camera <NUM>, the RFID detector <NUM>, and/or the RFID tag <NUM> may be considered features of the guest identification system <NUM>. However, in some embodiments, only one technique (e.g., facial identification or signal detection) may be used to identify the location/presence of a guest. Once the guest <NUM> has been identified and associated with an account (e.g., via forward facing data fields <NUM> and/or hidden data fields <NUM>), data from the hidden data fields <NUM> may be employed to utilize preferences of the guest <NUM> in the provision of special effects. For example, in the illustrated embodiment, the guest <NUM> may have a preference for cowboy themed environments over medieval themed environments. Accordingly, as shown, an animated figure of a cowboy <NUM> may be positioned on a turntable <NUM> for viewing by the guest <NUM> instead of an animated figure of a medieval knight <NUM>.

<FIG> is a block diagram of a process <NUM> of interactions between the user computing system <NUM>, the interactive platform <NUM> (e.g., the control center <NUM>), the separate system <NUM>, and the interactive devices <NUM> in accordance with an embodiment of the present disclosure. In the illustrated embodiment of <FIG>, the control center <NUM> initiates contact with the separate system <NUM> based on instructions from a user obtained via communication from the user computing system <NUM>. For example, a user may be interfacing with the control center <NUM> via the user computing system <NUM>, which is communicatively coupled to the control center <NUM> (e.g., via a network), by requesting access to an account via the GUI <NUM>. Specifically, as a component of requesting access to the account via the GUI <NUM>, the user may opt to use login credentials from the separate system <NUM>. This may include activating a web app or tool on the GUI <NUM>, such as a soft button, that initiates communication regarding the requested account with the separate system <NUM>. The initial input <NUM> provided by the user via the GUI <NUM> may include an account identifier (e.g., an email address) and selection of an option to use the separate system <NUM> for authentication, which may include using a universal login API <NUM>. In some embodiments, a user-entered account identifier may not be provided until the user is interfacing with the separate system <NUM>. For example, to initiate the process, the request for a new account or access to an existing account may simply be assigned an auto-generated account number. Regardless, an initial communication <NUM> is provided to the separate system <NUM> from the control center <NUM> after the control center <NUM> processes the initial input <NUM>, which is indicative of the user requesting a new account or access to an existing account. This initial communication <NUM> includes data indicating a request for coordinating user credentials from the separate system <NUM> (e.g., using the universal login API <NUM>) to open or otherwise access an account for the control center <NUM>.

In the illustrated embodiment of <FIG>, once the initial communication <NUM> has been received by the separate system <NUM>, the separate system <NUM> requests authentication of the user in an authentication request <NUM>. While the authentication request <NUM> is illustrated as passing from the separate system <NUM> to the user computing system <NUM> via the control center <NUM>, in other embodiments, a direct communication may be instituted or the information required for authentication may be initially prompted by the control center <NUM> or the GUI <NUM> and provided to the separate system <NUM> via the initial communication <NUM>. In the illustrated embodiment, authentication data (e.g., a password) <NUM> is provided from the user computing system <NUM> back to the separate system <NUM> via the control center <NUM>. This authentication data <NUM> may also include an authorization to provide access to other data (e.g., a user's trivial or fundamental data); however, such an authorization may also be provided in the initial communication <NUM>. In accordance with present embodiments, as with the authentication request <NUM>, communication of the authentication data <NUM> may utilize routes (e.g., a direct line of communication between the user computing system <NUM> and the separate system <NUM>) other than that illustrated.

Once the separate system <NUM> receives and approves the authentication data <NUM> (via the universal login API <NUM>), authentication approval data <NUM> may be provided to the control center <NUM> for opening or allowing access to an account associated with the authentication approval data <NUM>. In the illustrated embodiment, hidden data <NUM> is also provided in conjunction with this approval data <NUM>. The hidden data <NUM> may be provided as integrated with, embedded with, parallel with, in series with, or otherwise provided in relation to the approval data <NUM>. Further, all data or a portion of the data may be encrypted. For example, the approval data <NUM> and/or the hidden data <NUM> may be encrypted. In other embodiments, the hidden data <NUM> is provided in a separate communication after the approval data <NUM>. The hidden data <NUM> may include certain data about the user of the account associated with the authentication approval data <NUM>, such as fundamental data (e.g., birthdate) or trivial data (e.g., favorite color). The type or nature of the hidden data <NUM> provided may depend on the nature of approved communications by the user (e.g., as indicated via the GUI <NUM>). For example, a user may indicate that only trivial data can be shared between the interaction platform <NUM> and the separate system <NUM>. By transmitting the hidden data <NUM> in this fashion, the transfer of the data is inconspicuous to the user, which facilitates later surprise of the user via the interactive devices <NUM>.

Once the hidden data <NUM> and the authentication approval data <NUM> is provided to the control center <NUM>, the control center <NUM> may open and/or access an account for the user and populate that account with the hidden data <NUM>. Further, this hidden data <NUM> may be employed for special effects and the like. Specifically, the control center <NUM> may utilize the hidden data <NUM> to control the interactive devices <NUM>. As an example, with reference back to <FIG>, the control center <NUM> may control the virtual reality goggles <NUM> to display a virtual reality experience that corresponds to a preference of the user found in the hidden data <NUM>. Specifically, for example, in a virtual haunted house, the control center <NUM> may control the virtual reality goggles to provide imagery corresponding to a werewolf instead of other options (e.g., a ghost or zombie) because the user has indicated a preference for werewolves in the horror genre. By obscuring or masking the acquisition of such a preference via the transmission of the hidden data <NUM> in the disclosed fashion, an element of surprise can be added to experiences in an amusement park, such as via the provision of experiences in line with user preferences or characteristics. Surprise interactions may also include providing information about the user from an interactive device <NUM>. For example, the animated figure <NUM> dressed as a fortune teller may announce an astrological sign associated with the birthdate of the user, which may surprise and delight the user.

<FIG> is a schematic diagram of interactions with the GUI <NUM> in accordance with an embodiment of the present disclosure. A first GUI <NUM> may be provided via a display of the user computing system <NUM> in response to initiation of contact with the control center <NUM> to open or access a user account. The first GUI <NUM> includes prompts for the user to provide identification, specifically a prompt for an email address <NUM> and a prompt for a themed name <NUM> (e.g., a nickname or username). Further, the first GUI <NUM> provides a prompt to approve <NUM> or a prompt to decline <NUM> utilization of the separate system <NUM> for authentication purposes. The described prompts and other prompts may also be included to facilitate or add aspects to the disclosed interactions. The prompts may include inputs for data entry, toggle buttons, radio button, other interface tools and so forth.

If the user declines utilization of the separate system <NUM> for the purpose of authentication by selecting the prompt to decline <NUM>, a personalization GUI <NUM> may be provided on the user computing system <NUM> to allow the user to enter preferences and characteristics directly. While this provides desired information about the user for use in an amusement park via the interactive devices <NUM>, this acquisition of data is not hidden and will limit the provision of surprise. Such data may be gleaned from questions presented by the personalization GUI <NUM> that are intended to conceal the acquisition of relevant data. However, a savvy user may perceive the intent of the questions. In some embodiments, the user may decline to use the separate system <NUM> for authentication but allow data sharing between the separate system <NUM> and the interactive platform <NUM> (e.g., the control center <NUM>). After the personalization GUI <NUM> is addressed, a login credential request GUI <NUM> may be presented on the user computer system <NUM> to confirm authenticity of the user and open or access a user account.

If the user accepts utilization of the separate system <NUM> for authentication purposes by selecting the prompt to approve <NUM>, an access authorization GUI <NUM> may be provided via the user computer system <NUM>. The access authorization GUI <NUM> may provide an access authorization prompt <NUM> that allows the user to indicate whether data beyond the data required for authorization may be shared with the interface platform <NUM> from the separate system <NUM>. This may include additional prompting for types of data that can be shared, such as whether only trivial data can be shared or additional data can be shared. By allowing this data sharing, the hidden data <NUM> may be provided to the control center <NUM> for purposes of surprising the guest via interactions in the amusement park, as discussed above. If access authorization is accepted, the login credential request GUI <NUM> may be immediately provided via the user computer system <NUM>. If access authorization is declined, the personalization GUI <NUM> may be presented and then the login credential request GUI <NUM> may be provided upon completion of the personalization GUI <NUM>.

Claim 1:
An interactive platform (<NUM>) for populating hidden data fields (<NUM>) and controlling interactive features (<NUM>) in an amusement park (<NUM>) based on the hidden data fields (<NUM>), wherein the interactive platform (<NUM>) comprises a control center (<NUM>) configured to:
receive an account request (<NUM>) from a user computer system (<NUM>);
populate forward facing data fields (<NUM>) based on user inputs (<NUM>) from the user computer system (<NUM>) ;
coordinate authentication of the account request (<NUM>) with a separate system (<NUM>) configured to utilize a login application programming interface to share authentication data (<NUM>);
receive the authentication data (<NUM>) from the separate system (<NUM>) and provide access to a user account based on the authentication data (<NUM>); and
populate the hidden data fields (<NUM>) of the control center (<NUM>) based on user data (<NUM>) provided by the separate system (<NUM>).