Patent Description:
An amusement park may include various entertainment attractions that are useful in entertaining guests. The entertainment attractions of the amusement park may have different noise levels that may make it difficult to communicate with other guests in a party. It is recognized that it may be desirable to enhance the audio experience for guests within the entertainment attractions.

<CIT> describes a game apparatus using a video display device especially a game apparatus that displays an interactive video with a co-driver, particularly a virtual reality video. The game apparatus having a video display device of the present invention comprises, as the basic elements, a plurality of video display devices for displaying a video watched by each of the plurality of players, a plurality of player control units for controlling the video display of the corresponding video display device and a position sensor device for detecting the positions or the movements of the players. Based on the position information of one player detected by the position sensor device, the player control units for the other players control the corresponding video display device to give some change to the displaying video watched by the other players.

It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure, which is determined by the appended claims. Indeed, the present invention may encompass a variety of aspects that may not be set forth below but which are within the scope of the claims as appended.

In an embodiment, an audio channel system includes a guest interface device including a radio frequency identification (RFID) tag associated with the guest interface device. The RFID tag includes encoded device identification information of the guest interface device. The system includes a head-mounted display of a head-mounted de v ice, comprising a head-mounted display RFID reader configured to read the RFID tag of the guest interface device, when coupled to the head-mounted display, to receive the device identification information corresponding to the guest interface device. The system includes an audio distribution system having an RFID reader configured to read the RFID tag of the guest interface device to receive the device identification information of the RFID tag. The audio distribution system includes a processor configured to receive a group assignment of the guest interface device and associate the group assignment with the device identification information read by the RFID reader. The processor is also configured to receive the device identification information and head-mounted display information from the head-mounted display, associate the head-mounted display with the group assignment of the guest interface device' designate a private audio channel to the group assignment of the head-mounted display, and generate instructions to transmit audio to and from the head-mounted device using the private audio channel.

In an embodiment, a method for managing one or more private audio channels is provided that includes receiving guest interface device identification information encoded in a radio frequency identification (RFID) tag associated with a guest interface device. The method also includes assigning the guest interface device identification information into a group, receiving head-mounted device identification that indicates that a head-mounted device is coupled to the guest interface device, designating a private audio channel for the assigned group, and communicating audio signals between the head-mounted device and other head-mounted devices in the assigned group via the designated private audio channel.

In an embodiment, a head-mounted device is provided that includes a guest interface device that has an identification tag that encodes guest interface device identification information. The head-mounted device includes a head-mounted display configured to couple to the guest interface device. The head-mounted device includes a reader configured to read the guest interface device identification information from the identification tag. The head-mounted device also includes communication circuitry configured to transmit the guest interface device identification information and a head-mounted device identification to a controller. The head-mounted device further includes a speaker configured to output audio signals of a private audio channel associated with the guest interface device.

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.

Presently disclosed embodiments facilitate assignment of one or more private audio channels in order to provide an improved audio experience for guests experiencing a particular attraction at an amusement park. The audio distribution system may receive various inputs indicative of particular desired groupings. The inputs may include preferences, such as that a particular family would prefer to be grouped together. The audio distribution system may utilize the inputs to assign a particular private audio channel to each of the particular groupings. When the private audio channels are utilized, the members of the same group can hear each other, regardless of which seats of the ride that the members of the group occupy. The private audio channels facilitate an improved audio experience for the members of a group, enabling the members to engage in conversation with one another, while excluding communications from park guests on the ride that are not part of their private audio channel.

Presently disclosed embodiments describe an audio distribution system that is communicatively coupled to a head-mounted device to facilitate the private audio channel communication. The head-mounted devices may include: (<NUM>) a head-mounted display component that is relatively costly; and (<NUM>) an adaptor or interface component, referred to as a guest interface device, that is relatively robust and that each guest may adjust to their preferred fit and that is separate from the head-mounted display. These components reversibly couple to one another to permit guest interface devices to be used with head-mounted displays. The guest interface device may include device information, such as a unique device code or identification number, that is stored or otherwise associated with the device, such as via a radio frequency identification (RFID) tag. In an embodiment, the RFID tag is read by RFID readers associated with both the audio distribution system and a head-mounted display. Guests in the attraction may be temporarily assigned a head-mounted device that may be grouped into a particular private audio channel during the attraction run via the device information. The present techniques permit grouping of these temporarily assigned head-mounted devices into one or more private audio channels based on the temporary assignments and the preferences of these assigned guests. The system is able to individually address the audio input/outputs of the head-mounted devices according to these groupings to permit private communication during the attraction.

The guest interface device may be provided to guests during queuing or at ride dispatch to provide time for fit adjustment, while the head-mounted displays are provided at a later time point, e.g., when guests are sitting on ride seats and do not have to walk or carry the relatively more fragile head-mounted displays. The distribution of the guest interface devices and head-mounted displays may be at different locations and time points. The present techniques permit rapid association of a particular head- mounted display with a guest's desired audio channel grouping based on the assignment of the guest interface device that is coupled. In this manner, the group assignment is driven by the identity of the guest interface device. Thus, guests are not required to sit in a particular assigned seat and/or together with other members of their group, so long as they retain the guest interface device that carries the identification tag that is linked to the assigned group for a private audio channel. Once seated, guests may receive head-mounted displays, which then read the identification tag and, via the guest interface device information of the identification tag, communicate to a central controller to coordinate linking of the head-mounted display to a particular private audio channel of an assigned group.

With the foregoing in mind, <FIG> is a block diagram of an augmented reality (AR)/virtual reality (VR) system <NUM> having an audio distribution system <NUM> that incorporates a guest interface device <NUM> and a head-mounted display <NUM> for a particular ride in a theme park. The guest interface device <NUM> and the head-mounted display <NUM> may be separate components that are coupled to one another to form a head-mounted device that is distributed to a guest as provided herein.

As illustrated, the audio distribution system includes a controller <NUM>, e.g., a central controller, that includes one or more processors <NUM> and one or more memory devices <NUM>. The one or more processors <NUM> may execute software programs and/or instructions to adjust display of a virtual object, assign audio channels, and so forth. Moreover, the processor(s) <NUM> may include multiple microprocessors, one or more "general-purpose" microprocessors, one or more special-purpose microprocessors, and/or one or more application specific integrated circuits (ASICS), and/or one or more reduced instruction set (RISC) processors. The memory device(s) <NUM> may include one or more storage devices, and may store machine-readable and/or processor-executable instructions (e.g., firmware or software) for the processor(s) <NUM> to execute, such as instructions relating to adjusting display of a virtual object. As such, the memory device(s) <NUM> may store, for example, control software, look up tables, configuration data, and so forth, to facilitate adjusting display of a virtual object. In some embodiments, the processor(s) <NUM> and the memory device(s) <NUM> may be external to the controller <NUM>. The memory device(s) <NUM> may include a tangible, non-transitory, machine-readable-medium, such as a volatile memory (e.g., a random access memory (RAM)) and/or a nonvolatile memory (e.g., a read-only memory (ROM), flash memory, hard drive, and/or any other suitable optical, magnetic, or solid-state storage medium).

The audio distribution system <NUM> also includes a reader <NUM> and a display or graphical user interface (GUI) <NUM>. The reader <NUM> (e.g., a radio frequency identification (RFID) reader) reads identification information <NUM> associated with a particular head-mounted display <NUM> distributed to or associated with a particular guest via the guest interface device <NUM>. The identification information may be on or part of the head-mounted display <NUM> or, as illustrated, the guest interface device <NUM>, and may include a radio frequency identification (RFID) tag <NUM> that is positioned on (e.g., on a label or sticker), attached to, embedded into, or otherwise coupled to the guest interface device <NUM>. The RFID tag may be a material that is reusable and inexpensive (e.g., plastic) that is easily replaceable, should the guest interface device <NUM> be lost, misplaced, or stolen. Of particular importance, the RFID tag <NUM> stores data associated with the guest interface device <NUM>. The identification information <NUM> stored on the RFID tag <NUM> is read and interpreted by the reader <NUM>. While embodiments of the disclosure are discussed in the context of an RFID tag, it should be understood that the device identification information of the guest interface device <NUM> may additionally or alternatively be provided via a barcode, visible marker, or optical transmitter providing a signal capable of being read by a reader (e.g., an optical sensor or reader).

In certain embodiments as discussed herein, the guest interface device <NUM> may be associated with a particular guest profile by the audio distribution system <NUM> to permit guest profile preferences to be applied to operation of the head-mounted display <NUM>, such as a guest's language preferences, ride or character preferences, preferred volume settings, a closed caption preference, a group preference and so forth.

It should be understood that components of the audio distribution system <NUM> may be separate from one another and may be communicatively coupled. For example, the reader <NUM> and GUI <NUM> may be located at an attraction dispatch area and may pass information to the controller <NUM>, which may be a central controller of the audio distribution system <NUM> and may be remote from the reader <NUM> and the GUI <NUM>. The controller <NUM> may be in communication with other components of the system <NUM> or of an amusement park to receive instructions or information related to guest profiles or ride operation status. Further, the controller <NUM> may be communicatively coupled to the head-mounted displays <NUM> to control the audio channels as provided herein, e.g., via wired or wireless communication circuitry of the controller.

The audio distribution system <NUM> receives the identification information <NUM> stored on the RFID tag <NUM>. The audio distribution system <NUM> may create (e.g., render), designate, or assign a first audio channel <NUM>, a second audio channel <NUM>, and as many additional audio channels <NUM> as necessary to accommodate each of the groups requested for the particular ride. As will be explained in further detail below with reference to <FIG>, the audio distribution system <NUM> can assign audio channels for as few as one guest or as many guests as the particular ride will accommodate (e.g., <NUM> to <NUM> guests, etc.). In other words, the upper limit of guests that can be grouped into a single audio channel may be a function of the number of guests the particular ride accommodates on a run. In some instances, the particular audio channels will be used to group guests that came to the theme park together and that would like to experience the particular ride together, such as a family, a group of friends, a group of classmates, and so forth. The guests may self-sort into groups at the dispatch point or the guest interface device distribution point. As discussed herein, in embodiments, the system <NUM> may take into account the guest's preferences regarding group size, particular guests within their group, language preferences, closed captioning preferences, volume preferences, and so forth.

The audio distribution system <NUM> transmits data via the audio channels <NUM>, <NUM>, <NUM> to particular head-mounted displays <NUM> of a particular ride (ride <NUM>, see <FIG>), e.g., via communication circuitry of the audio distribution system <NUM>, such as a wireless transmitter <NUM> or a wired communication device. Each of the head-mounted displays <NUM> facilitates use of the audio channels <NUM>, <NUM>, <NUM> for the corresponding group members. Each of the head-mounted displays <NUM> includes at least a tag reader <NUM> (e.g. a RFID reader), a speaker <NUM>, a GUI and/or display <NUM>, a microphone <NUM>, a plurality of sensors <NUM> (e.g., a camera, eye tracking sensors, heart rate sensor, equipment monitoring sensors, hand tracking sensors, and the like), a controller <NUM>, a processor <NUM>, and/or a memory <NUM>. The head-mounted displays <NUM> include communication circuitry for facilitating wired or wireless communication in the system <NUM>, such as an antenna <NUM> coupled to a receiver <NUM>, and a transmitter <NUM>. The head-mounted displays <NUM> also include electronic eyeglasses <NUM> (e.g., goggles). When the eyeglasses <NUM> are inactive, the guest sees a real-world environment. In other words, the guest merely sees what he would see without wearing the eyeglasses <NUM> or goggles. When the eyeglasses <NUM> are active, virtual features in an augmented or virtual reality environment may be activated via the activated eyeglasses <NUM>, as discussed in further detail below with reference to <FIG>.

Returning to the AR/VR system <NUM> of <FIG>. , the audio input/output for a particular channel of the audio channels <NUM>, <NUM>, <NUM> may be communicated by an antenna <NUM> coupled to a receiver <NUM> of the head-mounted display <NUM>. However, it should be understood that the head-mounted display <NUM> may additionally or alternatively be hardwired via a tether and may receive wired communications. The receiver <NUM> picks up the audio output for the particular channel so that the wearer of the head-mounted display <NUM> can hear the audio output for the particular channel through the speaker <NUM>. In an embodiment, the audio channel communication is addressed to its assigned head-mounted displays <NUM> such that the head-mounted displays <NUM> receive audio from other guests in their assigned group. In an embodiment, the head-mounted display <NUM> may also include noise-cancelling features that filter out other noise so that the audio for only the particular channel is heard. As may be appreciated, the ride may be a noisy environment, where music, discussion from other guests, ambient noise, and other noise sources make it very difficult to hear what another guest is saying, even when sitting in close proximity. The head-mounted display <NUM> reduces outside interference so that guests in the same party can hear one another and converse more easily through the head-mounted display <NUM>.

Regardless of where the guests assigned to the particular audio channel sit on the ride, they can hear each other via the audio channel <NUM> through their own particular head-mounted display <NUM>. For example, in some instances, a member of the group is more adventurous and wants to sit at the front of the ride and experience certain features of the ride sooner than another member of the group who wants to sit in the back of the ride. The member of the group in the front of the ride and the member of the group in the back of the ride will still be able to hear each other via the same audio channel <NUM>.

If the member of the group at the front of the ride speaks into his microphone <NUM> and says "Watch out for the waterfall! I just got soaked!", the remaining members of his party will hear the audio regardless of where the remaining members are positioned in the ride. The private audio channel that is addressed to include the head- mounted display <NUM> ensures that the members of the same group can hear each other, while also not including conversations from other audio channels <NUM> so that the members of the same group experience are not bothered by other parties' discussion.

As discussed above, the head-mounted display <NUM> also includes the RFID reader <NUM> (or other sensing modality that is compatible with the device information on the guest interface device <NUM> as provided herein). The RFID reader <NUM> reads the RFID tag <NUM> that is coupled to the guest interface device <NUM>. The device identification information from the guest interface device <NUM> is assigned to groups after being read by the reader <NUM>. The guests within a particular group, while holding or wearing their guest interface devices <NUM>, can disperse within the attraction to receive head-mounted displays <NUM>. For example, the guests can receive the head-mounted displays <NUM> after they have taken their seats in a ride. As discussed, these seats do not have to be together to retain the audio channel assignment information. An individual head-mounted display <NUM> is coupled to a respective guest interface device <NUM> and receives the unique device identification information of the coupled guest interface device <NUM> via the reader <NUM>. This information is communicated by the head-mounted displays <NUM> to the audio distribution system <NUM>. In an embodiment, the guest interface device identification is communicated together with (bundles together) or otherwise associated with a particular identification of the coupled head-mounted display <NUM>. The audio distribution system <NUM> links a particular guest interface device <NUM> to a particular head-mounted display <NUM> based on this communication. In turn, the head-mounted display <NUM> can then be assigned to a private audio channel based on the grouping information or the assigned group of the coupled guest interface device <NUM>.

The head-mounted display <NUM> also includes the GUI and/or display <NUM>, where the user can adjust the volume of the audio channel, change closed caption preferences, and so forth via various inputs (e.g., buttons, keyboard). The GUI and/or display <NUM> may also be used to display information about the ride, notifications, and the like. The head-mounted display <NUM> may also transmit guest data to the audio distribution system <NUM> via the transmitter <NUM>. For example, the transmitter <NUM> may receive various signals output by the sensors <NUM>, which may then be communicated to the audio distribution system <NUM> and received via a receiver <NUM>. The sensors <NUM> may output signals indicative of the imagery of the surrounding environment, the sound of the surrounding environment and/or the guests' conversation, guest movement (e.g., hand movement, hand signals, etc.), biometric data (e.g., eye movement, pulse, etc.), facial movement, facial expressions, and so forth. In one embodiment, the audio distribution system <NUM> may adjust one or more aspects of the audio channels <NUM> based in part on the signals output by the various sensors <NUM>. For example, the audio distribution system <NUM> may detect that the guest is going through a part of the ride that is particularly loud due to the special effects of that part of the ride (e.g., gushing water sounds from a waterfall, noise from a volcano erupting, etc.).

<FIG> is a flowchart of a process <NUM> for assigning private audio channels <NUM>, <NUM>, <NUM> for different groups during operation of the ride. The process <NUM> includes receiving (block <NUM>) identification information from the guest interface device. The process <NUM> includes receiving (block <NUM>) inputs indicative of particular groupings. For example, the inputs could provide that a particular family is grouped together, or that members of a family are grouped in specified channels (e.g., one channel for adults, one channel for children). Other inputs could include default settings for certain groups, such as disabling a group chat feature for inputs indicating a single member group, spoken language preferences for the group used for alternative audio, turning text subtitles on or off, various default settings for interactive experiences pertaining to variety for a particular ride experience, retrieval of unique guest ID information from a separate guest-tracking system, and so forth. The reader <NUM> may receive several inputs at once or read one input at a time in an iterative process to form the particular groupings.

The process <NUM> includes assigning (block <NUM>) a private audio channel to each of the particular groups. Assigning the private audio channels involves using inputs to define each of the particular groups. The groups can be changed as circumstances change. For example, if a group member does not want to be part of a particular group anymore, or if a new member should be added to the particular group, the assignments of the private audio channels can be updated. For example, a new member can be added to an existing audio channel or a member can be removed or blocked from the audio channel.

The process <NUM> includes utilizing (block <NUM>) the private audio channel for each group during operation of the ride. As discussed above, using private audio channels facilitates a sharing of the private audio channel by a particular group only. In other words, the members of the same group can hear each other, while also excluding conversations from the ride environment or other audio channels. The process <NUM> includes communicating (block <NUM>) the audio information between guest interface devices that are grouped in the same private audio channel. The head-mounted devices may communicate with one another via wireless communication (e.g., Bluetooth, NFC, etc.) or via wired connection/communication. It may be appreciated that the process <NUM> can be repeated in full or in part to generate updated private audio channels for the ride. For example, the private audio channel can be updated when it is desired to add or remove a group member from the private audio channel.

<FIG> is a schematic illustration of a distribution and group assignment process of the present techniques. Guest interface devices <NUM> are distributed to guests at a distribution location <NUM>, which may be part of a ride queue or ride dispatch area in an embodiment. The distribution may be self-directed, where each guest takes a guest interface device <NUM> from a repository, such a container. The distribution may be operator-mediated, whereby an operator hands the guest interface device <NUM> to the guest. In any case, the guest interface devices <NUM> may be generally randomly provided, such that any guest can receive any appropriately sized guest interface device <NUM>. Further, each guest interface device <NUM> may be sized and shaped to couple to any head-mounted display <NUM>, such that there is no pre-association of the head-mounted displays <NUM> with a particular guest interface device <NUM> before the steps of the disclosed process. In an alternate embodiment, the guest may provide their own interface device <NUM> that is linked to their guest profile. Subsequent to distribution of the guest interface devices <NUM>, the guests enter a group assignment area <NUM>. The group assignment area <NUM> may be co-located with the distribution location <NUM>, such that distribution and group assignment happen generally at the same time or may be spaced apart areas. In the group assignment area <NUM>, the device identification information on the identification tag <NUM> coupled to each guest interface device <NUM> is captured (read) according to a preferred guest grouping (e.g., a group of friends riding an attraction together) such that a group of guests is sorted into a group. A first guest 238a is a member of a first group and a second guest 238b is a member of a second group. In an embodiment, each guest is sorted into only one group, such that the members of a group are nonoverlapping. This grouping information (e.g., group assignment) is used to establish the group assigned to a designated private audio channel.

The present techniques permit grouping and assignment without necessarily capturing guest identification information. That is, the groups may be established based on the guests self-sorting into preferred groups. These self-sorted groups may then scan the tags <NUM> on their distributed guest interface devices <NUM> using the reader <NUM>, e.g., at a kiosk <NUM> or reading station, or the groups may be scanned by a handheld device that includes the reader <NUM>, which may be controlled by an operator of the attraction. In an embodiment, the grouping process is not slowed down by guests without guest profiles having to enter their information at the point of distribution or scanning or by guests having to provide their names or other information as part of the assignment process. Further, guests are able to freely seat themselves within an attraction <NUM>, because the grouping information is tied to the guest interface devices <NUM>, which they take with them to their desired seats. As noted, any guest interface device <NUM> can couple to any head-mounted display <NUM>. However, the system <NUM> has captured grouping information that is linked to particular guest interface devices <NUM>. Thus, so long as a guest retains their guest interface device <NUM>, the guest may sit anywhere and/or receive any head-mounted display <NUM> and maintain their group assignment.

The temporary assignments to groups may be directly linked to the guest interface device identification information such that the guest interface devices <NUM> need not store guest information. Accordingly, these assignments are able to be efficiently terminated at the end of every attraction run without having to erase or modify the information stored on the guest interface devices <NUM> to permit new groupings and associations for a new group of guests. Efficiency in the device distribution and dispatching process permits the attraction to operate on time and with greater throughput, thus increasing the overall guest experience and operating efficiency of the attraction. In contrast to user-controlled head-mounted devices in which a guest is able to adjust communication settings via direct inputs to the device or a controller, the head- mounted devices as provided herein may be provided or maintained by a third party, e.g., a theme park. The present techniques permit efficient temporary association of a head-mounted device to a particular audio channel group in the context of a device with limited user input capabilities.

The captured device identification information is then provided to a central controller together with the assigned grouping information. When the guest interface device <NUM> couples to the head-mounted display <NUM>, the head-mounted display reader <NUM> of the head-mounted display <NUM> reads the unique device identification from its particular coupled guest interface device <NUM>, as shown in <FIG>. The reading may be near field communication or contact-based, such that the reading is initiated only when the guest interface device <NUM> and the head-mounted device <NUM> are relatively close to one another to prevent reading of an uncoupled guest interface device <NUM> in the next seat. Once captured by the head-mounted display <NUM>, the head-mounted display <NUM> communicates both the guest interface device identification information and its own head-mounted device unique information to a controller (e.g., the controller <NUM>, <FIG>) in a manner that links or associates the guest interface device identification information with head-mounted device unique information. The controller then associates the head-mounted display <NUM> coupled to the guest interface device <NUM> to the correct audio group and private audio channel by looking up the group assignment of the guest interface device identification (e.g., stored in the memory <NUM> of the controller <NUM>) and linking communications of the head-mounted display <NUM> to that group. The association of the head-mounted display <NUM> with the guest interface device <NUM> is performed at or subsequent to the coupling of these components to one another and requires no additional inputs from the guests for an efficient and user-friendly process that avoids bottlenecks and improves ride efficiency.

The tag <NUM> may be an active or passive tag. As discussed herein, the tag <NUM> may be a RFID, NFC, and/or optical barcode that is scanned by a RFID reader, a NFC reader, and/or an optical reader, respectively. The device identification information may be provided to the head-mounted display by a light emitter on the guest interface device <NUM> that is sensed by a detector on the head-mounted display. Each guest interface device <NUM> may emit light having unique modulation patterns.

<FIG> is a schematic view of the different groups associated with different private audio channels <NUM> during operation of the ride, according to embodiments of the present disclosure. The schematic view depicts the private audio channels <NUM> formed for each of the groups. As shown, each vehicle <NUM> of the ride <NUM> can include more than one audio channel <NUM> to accommodate different sized groups. For example, a first vehicle <NUM> includes two different audio channels <NUM> for each of the two groups in the first vehicle <NUM>. A first group <NUM> of the first vehicle includes two passengers seated next to each other at one end of the first vehicle <NUM>, while a second group <NUM> of the first vehicle includes four passengers in two rows of two passengers seated behind the first group <NUM>. While the ride <NUM> is in operation, the first group <NUM> of the first vehicle <NUM> and the second group <NUM> of the first vehicle <NUM> cannot hear each other's private conversations that are occurring via their respective private audio channels <NUM>. As discussed above, the audio for a first audio channel 32A associated with the first group <NUM> of the first vehicle <NUM> is received by the head-mounted display <NUM>. The wearer of the head-mounted display <NUM> can hear only the audio output for the particular channel <NUM>. As such, the head-mounted display <NUM> receives audio for only the particular channel 32A. The ride <NUM> may be in a noisy environment, where outside noise, music, other guests, and so forth can make it very difficult to hear what another guest is saying even when sitting in close vicinity. The head-mounted display <NUM> reduces outside interference so that guests in the same party can hear one another and converse more easily.

It may be appreciated that the private audio channels <NUM> work in the same manner regardless of where the members of each party are seated. Even if each member of the party is seated next to a member of a different party, as shown in Vehicle <NUM> (e.g., <NUM>), the audio input/output from other channels (e.g., channels <NUM>, <NUM>, see <FIG>) is not provided to those assigned to the channel <NUM>. For example, in Vehicle <NUM> (e.g., <NUM>), a first group <NUM> in vehicle <NUM> includes three passengers seated behind one another in a column, while a second group <NUM> in Vehicle <NUM> (e.g., <NUM>) includes three more passengers seated behind the one another in a column. While on the ride <NUM>, the guests seated next to each other may speak, shout or otherwise make noise simultaneously when the ride <NUM> is in operation, while still being able to hear everyone else in their private audio channel <NUM> even if the passenger that is seated next to him is not in their private audio channel <NUM>. Further, the head-mounted display <NUM> and/or the guest interface device <NUM> may include noise shielding or cancelling features to block ambient or adjacent noise. The guests of a particular group <NUM>, <NUM> can hear each other regardless of the number of individuals in their group or where the guests are seated on the ride <NUM>.

In one embodiment, one-way communication from a team member <NUM> (e.g., ride operator) or a particular character associated with the ride <NUM> can be activated to allow communication from the team member <NUM> to the ride passengers. The one-way communication may be selectively activated so that the team member <NUM> can communicate a message to all of the passengers of the ride <NUM>, to only a particular group of riders through their private audio channel <NUM>, or to only a particular rider in the private audio channel <NUM>. For example, the team member <NUM> may have reason to communicate to the entire group of passengers of the ride <NUM> in instances when there may be maintenance related issues, emergency situations, or other suitable reasons. In these scenarios, it may be useful for the team member <NUM> to engage the one-way communication from the team member <NUM> to the ride passengers to communicate "The ride is will need to stop in order to render aid to a passenger. Please remain seated while we assist this passenger as quickly as possible and resume operation of the ride.

In another scenario, it may be useful for the team member <NUM> to engage a particular audio channel 32A to communicate a message to only those members of the particular audio channel 32A. In some scenarios, it could be helpful to communicate a message to the members of the particular audio channel 32A that would apply only to the members associated with the particular audio channel 32A. In one example, the team member <NUM> could have need to let the group members know of an emergency for the group or communicate a change of plans for the group. For instance, the team member <NUM> may need to tell a group of students that are grouped in a particular audio channel a message from their school's principal (e.g., "Students of Harris Elementary School need to return to the school bus after the ride ends in order to depart the theme park.

It could also be useful for the team member <NUM> to engage a particular audio channel to communicate a message to only a single member of the particular audio channel 32A. In one example, the team member <NUM> could have need to communicate a message to one particular guest that may require that a specific message be distributed to the single guest as shown by element <NUM>. For instance, if a guest in the private audio channel has moved his arm outside of the vehicle <NUM> to touch an element (e.g., a waterfall, a rock, a character, etc.), the team member <NUM> can engage the one-way communication from the team member <NUM> to the single guest to remind the passenger of proper riding etiquette. In one example, the team member <NUM> could use the one-way communication to tell the single guest "Please keep hands in the vehicle. " Audio channel communication may be controlled by weight/rankings of individual members based on action within the ride or pre-set preferences (e.g., by order of scanning into the group).

It may be appreciated that one-way communication between the team member <NUM> and the passengers may be activated for a first time period. Indeed, the team member <NUM> may communicate with one group (e.g., all of the ride passengers) for the first time period, such as before the ride begins so that the team member <NUM> may communicate specific instructions to the entire group <NUM>. A private chat feature (e.g., the private audio channels <NUM>) may be activated in a second time period. For example, after the ride has begun, the private chat feature may be turned on so that group members can hear each other and begin conversing with one another via their private audio channel <NUM>.

However, the team member <NUM> may selectively reactivate the one-way communication with the group at a particular time outside of the first time period. Indeed, the team member <NUM> may reactivate the one-way communication at any point during the ride when it is necessary (e.g., in an emergency scenario).

Further, it may be appreciated that the private audio channels <NUM> can accommodate more passengers than a particular vehicle can hold and that the vehicle size does not limit the number of passengers in the private audio channel. For example, even though a particular vehicle associated with the ride may only hold six guests in the vehicle (e.g., Vehicle <NUM>, <NUM>), the private audio channel can be transmitted to guests in a separate vehicle (e.g., Vehicle <NUM>, <NUM> or Vehicle <NUM>, <NUM>), as long as they are grouped together by the team member <NUM> (or by group assignment <NUM>) into the same private audio channel. In this way, guests seated in Vehicle <NUM>, <NUM> can still hear and talk to guests seated in Vehicle <NUM>, <NUM> or Vehicle <NUM>, <NUM> as long as they are assigned to the same private audio channel <NUM>.

<FIG> depicts an example graphical user interface (GUI) <NUM> (e.g., that may be displayed as the GUI <NUM> of <FIG>) for assigning the private audio channels for the different groups during operation of the ride, according to embodiments of the present disclosure. The GUI <NUM> may be displayed a handheld or portable device <NUM>, as shown, that may be controlled by an operator, such as a ride operator, and that integrates the reader <NUM> (<FIG>). The GUI <NUM> may be integrated into a kiosk or station (e.g., kiosk <NUM> of <FIG>) with which the guests interact to self-group by scanning their guest interface devices <NUM>. The GUI <NUM> may include various objects (e.g., icons, windows, buttons, drop down menus, etc.) to carry out certain commands of the audio distribution system <NUM>. In the illustrated embodiment, the GUI <NUM> includes an input device, such as a selectable soft key or button <NUM>, for the designating a group size. Once designated, the device <NUM> may transition to a different screen <NUM> that updates as the devices are read (by scanning the tags <NUM> via the reader <NUM>).

The device <NUM> may include one or more indicators, such as audio or visual indicators associated with successful reading of the tag <NUM>. Upon scanning of the last tag <NUM> in the party (corresponding to the designated party size), the audio or visual cue may shift to a characteristic completion cue to indicate that scanning is complete. The reader <NUM> may be triggered to activate and deactivate in conjunction with receiving user input of a party size and completion of scanning of the designated number of tags <NUM> in the party. The GUI <NUM> may also include an indication of a faulty scan, which may prompt replacement of the guest interface device <NUM> that includes the damaged or nonfunctioning tag <NUM>. The GUI <NUM> may permit inputs or flags to select language of the group, subtitles or captioning.

<FIG> is a perspective view of an embodiment of the guest interface device <NUM> and the head-mounted display <NUM> of the AR/VR system <NUM> of <FIG>. The guest interface device <NUM> and the head-mounted display <NUM>, when coupled, form a head-mounted device <NUM>. Each of the guest interface devices <NUM> in the ride <NUM> has a unique identification (ID) associated with the particular guest interface device <NUM>. The unique ID may be used to identify a particular guest interface device <NUM>. At any given time, the park may have enough guest interface devices <NUM> having unique IDs so that there are no repeat IDs when the park is at maximum capacity. In this way, the unique IDs ensure that the private audio channels <NUM> assigned by audio distribution system <NUM> are transmitted only to the guest interface device <NUM> associated with particular head-mounted displays <NUM>. Each guest interface device <NUM> may be removably coupled to each of the head-mounted displays <NUM> via a coupling interface <NUM>. When coupled together, the guest interface device <NUM> and the head-mounted display <NUM> may be configured to enable the user (e.g., a guest, a passenger of a ride vehicle) to experience (e.g., view, interact with) AR/VR scenes and hear passengers in his private audio channel <NUM>.

In the illustrated embodiment, the guest interface device <NUM> is coupled to the head-mounted display <NUM> via the coupling interface <NUM>, shown as being resident on the head-mounted display <NUM>. However it should be understood that complementary portions of the coupling interface <NUM> may also be incorporated on or in the guest interface device <NUM>. The coupling interface <NUM> may include an electromagnetic coupling device, a press-fit assembly, a fastener, or any other suitable coupling device. When coupled together, the guest interface device <NUM> and the head-mounted display <NUM> are in an attached configuration so that the guest interface device <NUM> and the head-mounted display <NUM> are coupled together and function as an integrated unit. The guest interface device <NUM> may be a replaceable device that is provided at each attraction and that is returned at the exit for the attraction. In this manner, the guest interface devices <NUM> may be tracked throughout the park and collected before the guest leaves the attraction by an exit scan of the identification tag <NUM>. The exit scan may serve as a termination of the group assignment associated with the particular guest interface device <NUM> and the head- mounted device <NUM>. When the guest interface devices <NUM> are collected, they are sanitized and inspected to ensure proper functionality. Once the guest interface devices <NUM> are deemed satisfactory for use, the guest interface devices <NUM> are put back into circulation and reused by other guests entering the park for the first time.

As discussed above, each of the head-mounted displays <NUM> includes at least the tag reader <NUM> (e.g. a RFID reader), the speaker <NUM>, the display(s) <NUM>, the microphone <NUM>, and the plurality of sensors <NUM> (e.g., a camera, eye tracking sensors, equipment monitoring sensors, hand tracking sensors, and the like). The head-mounted display <NUM> also includes the electronic display <NUM> (e.g., AR/VR eyeglasses, goggles) that are coupled to a housing <NUM> of the head-mounted display <NUM>. The electronic display <NUM> may be transparent, semi-transparent, or opaque in nature. In an embodiment, the electronic eyeglasses <NUM> may enable the guest to view a real-world environment (e.g., physical structures in the attraction) when activated with certain virtual features (e.g., AR features) overlaid onto the electronic eyeglasses <NUM> so that the guest perceives the virtual features as being integrated into the real-world environment. That is, the electronic eyeglasses <NUM> may at least partially control a view of the guest by overlaying the virtual features onto a line of sight of the guest.

In an embodiment, when implemented in the amusement park setting, the head-mounted display <NUM> may be physically coupled to (e.g., tethered via a cable or tether) to a structure (e.g., a ride vehicle of the amusement park ride) to prevent separation of the head-mounted display <NUM> from the structure. The guest interface device <NUM> is configured to be affixed to a head of the guest and, thus, enable the guest to comfortably wear the guest interface device <NUM> throughout various attractions or while traversing certain amusement park environments. For example, the guest interface device <NUM> may include a head strap assembly <NUM> that is configured to span about a circumference of the head of the guest and configured to be tightened (e.g., constricted) on the head of the guest. In this manner, the head strap assembly <NUM> facilitates affixing the guest interface device <NUM> to the head of the guest, such that guest interface device <NUM> may be utilized in conjunction with the coupling interface <NUM> to retain the guest interface device <NUM> on the guest (e.g., when the guest interface device <NUM> is engaged with the head-mounted display <NUM>). The head strap assembly <NUM><NUM> may include an adjustment assembly for adjusting an inner circumference of the head strap assembly <NUM> to accommodate head parameters (e.g., head sizes, head shapes, hair styles) of a variety of guests to facilitate coupling the head-mounted display <NUM> to the respective heads of the guests.

The tag <NUM> may be coupled to the guest interface device <NUM> at a location that generally corresponds to a location of the reader <NUM> of the head-mounted display <NUM> when the guest interface device <NUM> and the head-mounted display <NUM> are coupled to one another. As shown, the tag <NUM> and the reader <NUM> may be generally on a same side after coupling. In an embodiment, the tag <NUM> and the reader <NUM> are in contact with one another when the guest interface device <NUM> and the head-mounted display <NUM> are coupled to one another. Termination of the contact or separation of the tag <NUM> out of range of the reader <NUM> may trigger deactivation of the group assignment as provided herein.

While certain embodiments are discussed in the context of the guest interface device <NUM>, the disclosed group assignment information may be linked to other tags <NUM> carried by the guest. For example, the guest may wear a sticker that is scanned to designate group assignments. The sticker is then subsequently scanned by the head-mounted device <NUM> (which may be a single integrated unit) that is assigned to that guest to facilitate private audio channels as provided herein.

Claim 1:
An audio channel system (<NUM>) comprising:
a guest interface device (<NUM>) comprising a radio frequency identification (RFID) tag (<NUM>) associated with the guest interface device (<NUM>), the RFID tag (<NUM>) comprising encoded device identification information (<NUM>) of the guest interface device (<NUM>);
a head-mounted display (<NUM>) of a head-mounted device (<NUM>) comprising a head-mounted display RFID reader (<NUM>) configured to read the RFID tag (<NUM>) of the guest interface device (<NUM>), when coupled to the head-mounted display (<NUM>), to receive the device identification information (<NUM>) corresponding to the guest interface device (<NUM>); and
an audio distribution system (<NUM>) comprising:
an RFID reader (<NUM>) configured to read the RFID tag (<NUM>) of the guest interface device (<NUM>) to receive the device identification information (<NUM>) of the RFID tag (<NUM>); and
a processor (<NUM>) configured to:
receive a group assignment of the guest interface device (<NUM>) and associate the group assignment with the device identification information (<NUM>) read by the RFID reader (<NUM>);
receive the device identification information (<NUM>) and head- mounted display information from the head-mounted display (<NUM>);
associate the head-mounted display (<NUM>) with the group assignment of the guest interface device (<NUM>);
designate a private audio channel (<NUM>, <NUM>, <NUM>) to the group assignment of the head-mounted display (<NUM>); and
generate instructions to transmit audio to and from the head-mounted device (<NUM>) using the private audio channel (<NUM>, <NUM>, <NUM>).