CN117320794A - System and method for hierarchical data reporting in attractions - Google Patents

Abstract

A hierarchical reporting system for attractions may include primary and secondary wireless communication networks that are separate from one another. Components of the attraction environment, such as the augmented reality/virtual reality headset and the ride vehicle with the controller, may generate operational data for the attraction. The components of the system may also include communication circuitry to communicate the first subset of operational data to the primary wireless network. The second subset of operational data is communicated via a secondary wireless network having a higher bandwidth than the primary wireless network.

Description

System and method for hierarchical data reporting in attractions

Cross reference to related applications

This application claims priority and benefit from U.S. provisional application No. 63184892 (filed at 2021, 5, 6 and entitled "SYSTEMS AND METHODS FOR LAYERED DATA REPORTING IN AN ATTRACTION"), the disclosure of which is incorporated by reference in its entirety FOR all purposes.

Technical Field

The present disclosure relates generally to data collection and reporting for elements of attractions, such as amusement attractions. More particularly, embodiments of the present disclosure relate to systems and methods for communicating data related to attractions in separate communication networks or layers according to data type.

Background

This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present technology, which are described and/or claimed 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. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.

Amusement parks or theme parks generally include a wide variety of entertainment systems or attractions that provide a unique experience for the patron of the amusement park. For example, an amusement park may include different attraction systems, such as roller coasters, drop towers (drop towers), water rides, dark rides, and the like. Some attraction systems may include environments with animated figures and special effects that help immerse a customer in the experience of the attraction system. However, the installation and configuration of features can be difficult, and monitoring different installed features that provide data in real-time using different formats and with different complexities can be challenging. Thus, improved features and techniques facilitate more efficient processing of ride and attraction data to provide a desired effect or experience for a customer.

Disclosure of Invention

The following outlines certain embodiments commensurate in scope with the originally claimed subject matter. These embodiments are not intended to limit the scope of the claimed subject matter, but rather these embodiments are intended to provide a brief summary of possible forms of the subject matter. Indeed, the subject matter may encompass a variety of forms that may be similar to or different from the embodiments set forth below.

In one embodiment, a data reporting system for attractions may include a primary wireless communication network, a secondary wireless communication network, and a ride vehicle for the attraction. The data reporting system for the attraction may further include: a controller of the ride vehicle, the controller configured to provide ride vehicle operation data indicative of characteristics of the ride vehicle during operation; and communication circuitry (cirucitry) to communicate a first subset of ride vehicle operation data to the primary wireless network and a second subset of ride vehicle operation data to the secondary wireless network, wherein the first subset of ride vehicle operation data is at a lower bandwidth than the second subset of ride vehicle operation data.

In one embodiment, a data reporting system for attractions may include a ride vehicle having: a sensor configured to generate position information of the ride vehicle in the attraction; a vehicle controller configured to generate log data of ride vehicle operations; and communication circuitry to communicate the location information via the primary wireless communication network and the log data via the secondary wireless communication network. The data reporting system may also include a server configured to receive the location information from the primary wireless communication network and the log data from the secondary wireless communication network, and configured to combine the location information with the log data.

In one embodiment, a method includes: the data reporting system generates operational data for the attraction, communicates a first subset of the operational data in real-time via the restricted wireless network, determines a status of the attraction, and selectively communicates a second subset of the operational data via the secondary wireless network based on the status of the attraction indicating a time between loops of the attraction.

Drawings

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 represent like parts throughout the drawings, wherein:

FIG. 1 is a block diagram of a hierarchical reporting system for attractions in accordance with the techniques described in this disclosure;

FIG. 2 is a perspective view of a sight environment of a hierarchical reporting system according to one embodiment of the present disclosure;

FIG. 3 is a block diagram of components within a hierarchical reporting system according to an embodiment of the present disclosure; and

FIG. 4 is a flow chart of a method for data transfer based on the operational status of a hierarchical reporting system in accordance with the present technique.

Detailed Description

One or more specific embodiments of the present disclosure will be described below. In an effort to provide a concise description of these embodiments, all features of an actual implementation may not 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, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure. Further, to the extent that certain terms are used herein, such as parallel, perpendicular, etc., it should be understood that these terms allow for certain deviations from strict mathematical definition, such as allowing for deviations associated with manufacturing defects and associated tolerances.

The present disclosure is directed to a hierarchical reporting system that may be implemented by amusement park attractions, including shows, rides, promotions, and the like. As provided herein, the hierarchical reporting system facilitates the inclusion (interest), communication, processing, and/or analysis and storage of data for various components of attractions, such as amusement attractions. The data can relate to audio, visual, and physical effects that can be experienced by the occupant in the vehicle, as well as characteristics of the game, including player interactions with various game effects, as well as interaction-based dynamic experiences. The occupant may also be equipped with a virtual reality/augmented reality (AR/VR) head mounted device (head set) with additional features that provide a more immersive experience. These sight components generate corresponding operational data, and some of the operational data can be considered "fast" data that is communicated to the controller quickly (e.g., near real-time or in real-time) to permit feedback actions based on analysis of the data.

In one embodiment, one or more components of the hierarchical reporting system may generate, collect, and publish or transmit real-time fast operation data (e.g., health data) related to the status of the one or more components during operation of the ride. For example, ride vehicle operation data may include, but is not limited to, operational status, fault identification, position data, velocity, occupant status, sensor measurements, or the status of a coupling device such as a headset. Thus, higher priority fast data may be structured to facilitate faster communications, and may be compressed, communicated with lower bandwidth, and/or communicated over an access-restricted communication path dedicated to fast data communications. The operational data also includes "slow" data that is of lower priority and can be communicated at a higher bandwidth to include more information. Slow data may be transferred in real-time or may be transferred in bulk over a separate communication path from fast data.

Although the fast and slow data are communicated via separate paths, the fast and slow data may have one or more common destinations and may be provided jointly to a particular processing and/or storage layer. Accordingly, provided herein are hierarchical data reporting techniques that provide sight operation information and analysis at varying levels of detail and accuracy depending on the desired outcome. Real-time fast data (without any real-time slow data) can be fed into the security analysis to permit the attraction controller to respond quickly to deviations in ride vehicle position or to vehicle outages while the ride is running. Furthermore, the real-time fast data may enable the attraction controller to modify the current loading decision based on the real-time fast data. For example, the real-time fast data may indicate that the ride vehicle may only be able to accommodate fewer occupants than normal. Thus, the attraction controller may provide instructions to one or more team members to modify the current loading process to account for changes in the capacity of the ride vehicle. Accordingly, the fast data may be time sensitive data that is both transferred during ride operation and, in embodiments, functions in real time as the ride operates. Real-time fast data is communicated via dedicated communication paths to avoid bottlenecks or slowdowns that may be associated with slower and higher bandwidth data. The more highly detailed (extracted) operational slow data can be combined with fast data at one or more analysis layers that model past rides, identify baseline values/trends and find outliers (outliers), and predict whether performance metrics can be outliers to facilitate pre-maintenance and improve attraction run time (uptime) and customer performance.

In view of the foregoing, FIG. 1 illustrates one embodiment of a hierarchical reporting system 10 according to the present disclosure. The hierarchical reporting system 10 may be implemented to report data generated in a attraction environment through one or more client layers, one or more server layers, one or more wireless network communication layers, and one or more storage layers. As shown, the attraction environment includes one or more ride vehicles 14 that each include a vehicle game client 18 that receives vehicle operation data from one or more hardware or software elements of the ride vehicle 14.

The carrier game client 18 may be implemented as hardware or software as provided herein and operates to communicate with one or more servers (e.g., carrier game server 20). The one or more vehicle game clients 18 may include components, discussed further below, configured to collect and distribute ride vehicle operation data or to communicate ride vehicle operation data to the vehicle game server 20 via the primary wireless network 23. Ride vehicle operation data may include, but is not limited to, power levels, test logs, fault data, and the like. In some embodiments, certain high priority ride vehicle operation data may be communicated to the vehicle game server 20 via a wired or wireless connection. The data on the vehicle game server 20 may then be transferred to the ride data server 22 via the limited primary wireless network 23. Additionally or alternatively, the vehicle game client 18 and/or the vehicle game server 20 may communicate the lower priority, high detail data directly to the ride data server 22 via an auxiliary network 25 (shown as an analytics wireless network). As mentioned above, the secondary network 25 may have a higher bandwidth than the primary wireless network 23 to accommodate a larger data set size. In addition, the highly detailed data may provide a historical log or longer term view of the corresponding components of the system 10. It should be noted that the vehicle game server 20 may also compile the operational data from the vehicle game client 18 into highly detailed data and then pass it to the ride data server 22 via the auxiliary network.

In one embodiment, one or more components of the hierarchical reporting system may collect and transmit highly detailed data, such as slow data, related to the performance of the components. Highly detailed data may be collected by the vehicle game client 18 of the ride vehicle 14 and then transferred to the secondary network 25 having a higher bandwidth than the primary wireless network 23, as mentioned above. It should be appreciated that the auxiliary network 25 may operate with closer radio and/or antenna distances for effective communications, with line-of-sight communications, with slower handovers between wireless access points, or any combination thereof to accommodate higher bandwidths. Highly detailed data from the ride vehicle 14 may be transferred to the ride data server 22 via the auxiliary network 25. Highly detailed data may also be transferred from the projection game client 24 and/or the ride game server 26 to the ride data server 22. The data may be uploaded from the ride data server 22 to the cloud-hosted analysis engine 28. It should be noted that if the limited wireless network 23 is not available to transmit data, the data may be stored on the ride vehicle 14 until the data can be transmitted. Real-time data related to the operation of the ride vehicle 14 may be transmitted to the ride data server 22 via a limited wireless network 23 (e.g., the primary wireless network of the attraction environment 12). It should be noted that the restricted wireless network 23 is restricted from access, e.g. not accessible by occupants within the attraction. A limited wireless network may use only a low bandwidth for requirements or operation, similar to the bandwidth of standard Wifi. Further, the health data of one or more projection game clients 24 may be sent to the ride game server 26 and then to the ride data server 22 (via a hard-wired connection). Once at the ride data server 22, the data may be uploaded to the cloud-hosted analysis engine 28.

The tiered reporting system permits real-time data to be transferred to the limited primary wireless network 23 as the occupant travels through the attraction. To manage the data load, the ride vehicle 14 may be equipped with a data feedback mechanism to limit data transfer in order to protect the primary wireless network 23 and/or the secondary network 25. Data load management may also be facilitated by positioning ride vehicles 14 at various wireless access points throughout the ride such that none of the wireless access points are flooded with data. The position of the ride vehicle 14 may be accomplished automatically by ride logic or manually when the ride is not operational. For example, the ride may not operate during ride cycles or during an unloading/loading process to a customer and when the ride vehicle 14 is substantially stationary. In an embodiment, the ride logic operates to distribute the ride vehicles 14 throughout the loading/unloading area to distribute the data load for different wireless access points in the area and based on the amount of data to be transmitted. If one wireless access point is full capacity, the controller of the attraction can, in embodiments, instruct other ride vehicles to autonomously move to other locations associated with other wireless access points.

Highly detailed vehicle operation data may be transmitted through the primary network 23, the secondary network 25, or any combination thereof when the ride is not operational. In one embodiment, highly detailed vehicle operation data is limited to the auxiliary network 25 when the ride is operational, but can be communicated via the primary network when the ride is not operational. In an embodiment, communication from the system to the ride vehicle 14 can occur via an auxiliary network. In one example, such communication to the ride vehicle 14 via the auxiliary network 25 may modify the code/software that generates the highly detailed vehicle operation data, the software that configures the generation of the highly detailed vehicle operation data, or the placement of data/logic on the ride vehicle that alters how the data is interpreted. This can affect what data is treated as fast and slow data and the frequency with which the data is recorded/reported/sent/received. The highly detailed data may provide insight into larger and/or longer-term problems that may occur during one or more rides. Further, the highly detailed data may relate to activities ancillary to the ride, such as activities available to the occupants while they are waiting in the team. For example, rides may have sensors disposed throughout the team that may detect signals from hand held devices associated with the ride. The sensors may collect data related to how often an occupant interacts with an activity while in a team.

The ride data server 22 may also receive data from other components of the system, such as one or more projection game clients 24, via the primary wireless network 23. Projection game client 24 may include any suitable projector, augmented reality/virtual reality (AR/VR) head mounted device, or the like. The projection game clients may be distributed throughout the attraction with the AR/VR headset located on the ride vehicle 14 and the projector being part of the environment. In an embodiment, certain head mounted information may be generated and collected by the ride vehicle game client 18.

The projector, AR/VR headset or other physical object may be configured to send the health data to the ride game server 26 via the primary wireless network 23. The operational data of projection game client 24 may include, but is not limited to, status, power level, test log, fault data, and the like. In some embodiments, the data of the projection game client 24 may be communicated to the ride game server 26 via a wired connection. For stationary projection game clients 24, the wired connection may extend through or on the floor of the attraction environment to a central computing system. The mobile projection game client 24, on the other hand, may be adapted to accommodate a wired connection, a tether (tether), to the ride vehicle 14. Additionally or alternatively, the loading station and/or maintenance area (mentioned above) may include an adapter to connect to the AR/VR headset 34 to collect health data and communicate to the ride game server 26.

Once the data of the projection game client 24 is transferred to the ride game server 26, it may then be transferred to the ride data server 22 via the primary wireless network 23. Additionally or alternatively, the projection game client 24 may communicate highly detailed data directly to the ride data server 22 via the auxiliary network 25. As mentioned above, the secondary network 25 has a higher bandwidth than the primary wireless network 23 to accommodate the larger data set size. Furthermore, the highly detailed data may provide a longer term perspective of the corresponding components of the attraction environment. The ride game server 26 may also compile the health data from the projection game client 24 into highly detailed data and then pass it to the ride data server 22 via the auxiliary network.

Once the data is at the ride data server 22, it may be uploaded to the cloud-hosted analysis engine 28. Once the data is published into the cloud-hosted analysis engine 28, artificial intelligence and/or machine learning algorithms are used to understand baseline values, trends, and discover outliers. Artificial intelligence and/or machine learning may also predict whether performance metrics may be outliers to facilitate pre-maintenance and improve ride run time and occupant experience.

The disclosed hierarchical data reporting system may be used in conjunction with data generated by attractions or other entertainment environments. As illustrated by fig. 2, the attraction environment 12 may include one or more features that enhance the immersive experience and generate relevant operational data that is provided to the hierarchical data reporting system. For example, in one embodiment, one or more ride vehicles 14 traverse the ride path 38. The attraction environment 12 may include virtual game features such as those provided by the projector 32 onto the video display 42. The video display 42 may include various selectable virtual display features that can be selected by a game player (e.g., the patron 36) prior to the start of a ride. The customer 36 may also be equipped with an augmented reality/virtual reality (AR/VR) head mounted device 34. The AR/VR headset 34 may have a display that includes virtual display features similar to those on the video display 42. Both fast and slow operation data from projector 32, video display 42, and/or AR/VR headset 34 may be provided to projection game client 24. As discussed, certain AR/VR headset 34 may be tethered to the ride vehicle 14 and their operational data may additionally or alternatively flow through the vehicle game client 18.

The customer 36 may interact with virtual display features displayed on the display of the AR/VR headset 34. The video projection may generate display instructions to display images according to environment 12. The image may be determined based on the location of the patron 36 on the ride path 38. Furthermore, the same, similar, or additional visual pictures will be projected to the display on the AR/VR headset 34. This will allow the customer 36 to interact with objects within the attraction environment while also being able to see additional visual pictures that may not be physically present within the environment 12. The fast or high priority operational data collected by the projection game client 24 and provided to the ride data server 22 (fig. 1) may include head mounted device failure data, display failure data, or timing data indicating coordination of the display with corresponding audio, video, or special effects. Slow or low priority operational data may include detailed gaze direction information, detailed image display data, interaction data.

In addition, projection game client 24 or other clients of system 10 (see FIG. 1) may receive or collect operational data from interactive physical objects 40 (e.g., surface features capable of reflecting projections based on the environment) that form dynamic physical barriers, visual interests, or special effect devices such as sprinklers, foggers, fans, etc. Such physical objects 40 may also include robotic characters. The fast or high priority operational data from the physical object may include fault data requiring diversion of ride vehicle 14, activation of alternate special effects, or deactivation of a coordinated display sequence specific to the physical object or mapped onto the physical object as it moves. Slow or low priority operational data may include object movement tracking and object movement position relative to the ride vehicle 14, projection map data that evaluates the accuracy of the projection map display, or gaze direction information that determines whether a physical object is interesting to the occupant 36.

The hierarchical reporting system 10 (see FIG. 1) may be implemented for data reporting of operational data from a attraction, such as the attraction environment 12 of FIG. 2. Fig. 3 is a block diagram of a sight system 48 that may collect or receive operational data for reporting via the reporting system 10. The system 48 includes a sight controller 49 communicatively coupled to the one or more ride vehicles 14 and the one or more AR/VR headset 34. The controller 49 may be communicatively coupled to other elements within the environment 12, as provided herein. The controller 49 may include separate control circuitry for facilitating interactive and dynamic elements, including the display circuitry 58. Further, the controller 49 may include or be communicatively coupled to a tag or sensor 50 for tracking the ride vehicle 14, an input device of an operator interface 52, an audio component 54, a special effect controller 56 for controlling one or more physical effects (e.g., the interactive physical object 40; see FIG. 2), and a communication module 59 for communicating fast and/or slow data. One or more of the disclosed features of controller 49 may alternatively be implemented in carrier 14.

In some embodiments, the controller 49 may send instructions to the ride vehicle 14 via the auxiliary network 25 while the ride is in operation. The instructions may include, but are not limited to, instructions on how to collect data and/or instructions on determining whether the collected data is fast data or slow data. Determining whether the data collected by the health data feedback system 74 of the ride vehicle 14 is fast or slow data may increase the efficiency of the hierarchical reporting system 10.

The ride vehicle 14 may include components that generate operational data, such as a motor 66 and a brake 68. Movement of the ride vehicle 14 may include operation (e.g., acceleration, deceleration), steering, and stopping of the ride vehicle 14. The motor 66 may be powered by any suitable power source 62 including, but not limited to, a battery, a solar panel, an electrical generator, a gas engine, or any combination thereof. Operation of the motor 66 and brake 68 may be controlled by the vehicle controller 64. For example, the vehicle controller 64 may control the motor 66 to adjust its output power to accelerate or decelerate the ride vehicle 14. The vehicle controller 64 may also control the brakes 68 to slow or stop the ride vehicle 14. Further, the vehicle controller 64 may operate under instructions from a player via the operator interface 70 (e.g., driving the vehicle based on operator control of a steering wheel or joystick). Operational data generated by components of ride vehicle 14 is reported to a hierarchical reporting system, as provided herein. In one example, the fast or higher priority data may include out-of-tolerance rates, while the slow or lower priority data may include power fluctuations of the motor 66 that are indicated for future maintenance.

The ride vehicle 14 may include a position feedback system 72 for monitoring its position in the attraction. In one embodiment, the position feedback system 72 interacts with one or more sensors or tags 50. The vehicle position feedback system 72 may include a reader that may sense the sensor or tag 50 to provide position information of the ride vehicle 14. The reader then provides the position information to the vehicle controller 64, which in turn is then communicated to the vehicle game server 20 (fig. 1) via the communication module 60. Further, the health or operational data feedback system 74 may include sensors or tags that collect real-time health data of the ride vehicle 14. The communication module 60 may also facilitate communication with the vehicle game server 20 to facilitate communicating health data from the health data feedback system 74. In this way, real-time health data of the ride vehicle 14 may be transferred to the vehicle game server 20 and ultimately to the ride data server (within a short time interval (e.g., 1s, 2s, 3s, etc.). In the event that the primary wireless network 23 is not available, the real-time operational data may be stored in the memory of the vehicle controller 64 until the primary wireless network 23 is available.

Additionally or alternatively, when the primary wireless network 23 is not available, the real-time health data may be communicated to the ride data server 22 via the secondary network 25. Highly detailed data from the ride vehicles 14 may also be communicated to the ride data server 22 via the auxiliary network when the attraction is not operational. In some embodiments, if bandwidth is available, highly detailed data may be communicated to the ride data server via the primary wireless network 23.

The attraction environment may include various components that may allow the occupant 36 to interact with the attraction environment and the ride vehicle 14. In particular, the AR/VR head-mounted device 34 can include display circuitry 80 that can present visualizations to a display 84. The visualization may be the same as or similar to the visualization on the video display 42. The AR/VR head-mounted device 34 can also include an audio component 82, which audio component 82 can present the same or similar audio as that of the audio component 54 of the attraction environment. This allows the occupant 36 to have an immersive ride experience and enhances ride enjoyment.

The AR/VR head-mounted device 34 can also include a communication module 86. It should be noted that communication module 86 may be the same or similar to communication modules 59, 60 as described above. The communication module 86 may communicate real-time health data of the AR/VR headset 34 to the ride game server 26 via the primary wireless network 23, which will then be communicated to the ride data server 22 for uploading to the cloud-hosted analysis engine 28. Alternatively or additionally, the communication module 86 may communicate the highly detailed data directly to the ride data server 22 via an auxiliary network for uploading to the cloud-hosted analysis engine 28. The AR/VR headset 34 may be communicatively coupled to the ride vehicle 14 such that the AR/VR headset real-time health data and highly detailed data may be stored in the memory of the vehicle controller 64 in the event that the primary and secondary networks are unavailable.

In addition to being communicatively coupled to the ride vehicle 14, the AR/VR headset 34 may be physically tethered to the ride vehicle 14. The connection may be facilitated via any suitable form of wiring that may allow information to be passed through. In certain embodiments, the power source 62 may also provide power to the AR/VR headset 34 when the AR/VR headset 34 is tethered to the ride vehicle 14.

Fig. 4 is a flow chart of a method of data reporting. First, components within the attraction (e.g., the ride vehicle 14, the AR/VR headset 34, an animatronics (animatronics), etc.) may generate, collect, and store operational data including a first subset of higher priority data and a second subset of data that is highly detailed and lower priority operational data, or any combination thereof, as indicated by block 90. Each component may include elements configured to generate, collect, and store data. For example, the vehicle controller 64 may generate, collect, and store data. Although the controller is not depicted in the other components shown in fig. 3, it should be noted that components within the attraction (including but not limited to the ride vehicle 14, the AR/VR headset 34) may include elements similar to those of the vehicle controller 64, such as a suitable memory capable of storing data and instructions and a processor configured to generate data and execute instructions stored within the memory. A subset of the operational data (the first subset) is automatically communicated in real-time as it is generated, independent of the sight state (block 92).

In response to the collection of operational data, the system 10 may determine a sight state (such as whether the sight is operational), as indicated by block 94. The attraction state may be active when the ride vehicle is in motion during attraction cycles, or inactive, for example, during periods between attraction cycles or when the ride vehicle is in motion or on a ride path. When the ride is in operation, the system 10 communicates high priority operational data via the primary wireless network 23. The primary wireless network 23 can only transmit real-time operational data due to limited bandwidth compared to data transmission protocols for secondary networks that transmit entered data that is more data intensive and can be transmitted in bulk via the secondary network when the ride is not operational.

When the state is inactive, components within the attraction may not generate, collect, and store new operational data or generate, collect, and store very limited new operational data. However, data stored during the ride cycle in the respective memories of the components within the attraction may be transferred via the auxiliary network. Additionally or alternatively, data transfer of real-time data may be delayed to allow for preferential transfer of highly detailed data via the auxiliary network, as indicated by block 96. Data transfer delays may also occur when the primary wireless network 23 and/or the secondary network is not available.

In some embodiments, both the primary and secondary networks are available and transmit data, whereby the primary wireless network 23 may transmit only real-time operational data, and the secondary network may transmit highly detailed data in real-time or with a delayed or periodic schedule. The higher priority and lower priority data may be combined and then uploaded to the cloud-hosted analysis engine 28. The cloud hosting analysis engine 28 may be used to make decisions about attractions based on real-time health data, highly detailed data, or any combination thereof.

The lower priority and higher priority data may be combined based on time stamp information or data source or origin (e.g., power data from a vehicle powertrain). In an embodiment, higher priority data may be present in lower priority data-but in a more data-intensive form.

Although only certain features have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the disclosure.

The techniques presented and claimed herein are referenced and applied to specific examples and substantial objects that arguably improve upon the practice of the art, and as such are not abstract, intangible, or pure theories. Further, if any claim at the end of this specification contains one or more elements designated as "means for [ performing ]," means for [ function ], or "step for [ performing ]," function ], it is intended that such elements be interpreted according to 35u.s.c.112 (f). However, for any claim containing elements specified in any other way, it is intended that such elements not be construed in accordance with 35u.s.c.112 (f).

Claims (20)

1. A data reporting system for a attraction, the data reporting system comprising:

a primary wireless communication network;

a secondary wireless communication network separate from the primary wireless network; and

the riding carrier of scenic spot, the riding carrier includes:

a controller of the ride vehicle, the controller configured to provide ride vehicle operation data indicative of characteristics of the ride vehicle during operation; and

a communication circuit that communicates a first subset of the ride vehicle operation data to the primary wireless network and a second subset of the ride vehicle operation data to the secondary wireless network, wherein the first subset of the ride vehicle operation data is at a lower bandwidth than the second subset of the ride vehicle operation data.

2. The data reporting system of claim 1 wherein the primary wireless communication network does not receive data communicated via the secondary wireless network.

3. The data reporting system of claim 1, wherein the first subset of the ride vehicle operation data comprises real-time ride vehicle operation data.

4. The data reporting system of claim 1, comprising:

a data server that receives the first subset of the ride vehicle operation data from the primary wireless network and the second subset of the ride vehicle operation data from the secondary wireless network.

5. The data reporting system of claim 1, comprising:

a display controller configured to perform:

the image is transmitted to an AR/VR headset, wherein the AR/VR headset is coupled to the ride vehicle.

6. The data reporting system of claim 5, wherein the AR/VR headset generates headset operating data, wherein a portion of the headset operating data is provided to the controller of the ride vehicle as part of the first subset of the ride vehicle operating data.

7. The data reporting system of claim 5, wherein the AR/VR headset includes a headset communication circuit that receives the transmitted image and communicates headset operating data to the auxiliary wireless network, the headset operating data including a first portion of headset operating data and a second portion of the headset operating data, wherein the first portion of the headset operating data is at a lower bandwidth than the second portion of the headset operating data.

8. The data reporting system of claim 7 wherein the display controller receives the headset operating data and separates the data in the first portion and the second portion.

9. The data reporting system of claim 8, wherein the display controller communicates the first portion of the headset operating data via the primary wireless network.

10. The data reporting system of claim 1, wherein the first subset of the ride vehicle operation data comprises position data of the ride vehicle.

11. The data reporting system of claim 1, comprising a plurality of sensors configured to detect customer interactions, wherein the plurality of sensors generate customer data that is communicated to a data server via the secondary wireless network.

12. A data reporting system for a attraction, the system comprising:

a ride vehicle, comprising:

a sensor that generates position information of the ride vehicle in the attraction during a cycle of the attraction;

a vehicle controller that generates log data of ride vehicle operation during the cycle of the attraction;

a communication circuit that communicates the location information via a primary wireless communication network and communicates the log data via a secondary wireless communication network, wherein the location information is communicated at a lower bandwidth than the log data; and

a server configured to receive the location information from the primary wireless communication network and the log data from the secondary wireless communication network, and configured to combine the location information with the log data.

13. The system of claim 12, wherein the location information is communicated in real-time, and wherein the log data is communicated in bulk.

14. The system of claim 12, wherein the location information is communicated during the loop of the attraction, and wherein the log data is communicated only after the loop of the attraction has been completed.

15. The system of claim 12, wherein the position information is communicated while the ride vehicle is in motion, and wherein the log data is communicated only while the ride vehicle is stationary based on the position information.

16. The system of claim 12, wherein the log data is only transferred when the ride vehicle is in a loading and/or unloading area of the attraction based on the location information.

17. The system of claim 12, wherein the server is configured to communicate instructions to the vehicle controller, wherein the instructions include the log data of how to generate ride vehicle operation during the cycle of the attraction.

18. A method for data reporting for a attraction, the method comprising:

generating operation data of the scenic spot;

communicating the first subset of operational data in real-time via a limited wireless network;

determining the state of the scenic spot; and

a second subset of the operational data is selectively communicated via an auxiliary wireless network based on the status of the attraction indicating a time between loops of the attraction.

19. The method of claim 18, comprising generating instructions to move a ride vehicle of the attraction relative to a wireless access point to selectively communicate the second subset of the operational data.

20. The method of claim 18, wherein the operational data comprises vehicle position data, and wherein the vehicle position data is part of the first subset.