System and method for cleaning a head-mounted device

Abstract

A system for cleaning components of a head-mounted device can be used in conjunction with the head-mounted device or can include a reader for reading identification information from a plurality of interface devices that are components of the head-mounted device. Each interface device can include an RFID tag containing respective identification information of the interface device. The system can also include a cleaning system. Further, the system can include a control device having a processor and a memory, and the control device can receive identification information from the reader or cleaning cycle information from the cleaning system to determine whether the interface device has reached a threshold level of efficiency degradation.

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This application is titled "System and Method for Cleaning a Head - Mounted Device", claims the priority and benefit of U.S. Provisional Patent Application No. 63 / 350,723, filed on June 9, 2022, the disclosure of which is hereby incorporated by reference in its entirety.

[0002] (Technical Field) The subject matter disclosed herein generally relates to the field of virtual reality and / or augmented reality. Further, specifically, embodiments of the present disclosure relate to systems and methods utilized to clean user - contact components of a head - mounted device (HMD).

[0003] This section is intended to introduce the reader to various technical aspects related to the various aspects of the present disclosure that are described below and / or claimed. This discussion is believed to help provide the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, these descriptions are to be read in this context, not as an admission of prior art.

[0004] Various amusement rides have been created to provide passengers with unique movements and visual experiences. For example, virtual reality, and / or augmented reality (VR / AR) systems can be used in connection with amusement park rides and can be implemented in multi - passenger vehicles that travel along a fixed path. A headgear such as an HMD can include a display and can be implemented to give the wearer a VR / AR experience on a given ride. Since the HMD is in close contact with the user, there is a need to regularly clean the HMD.

Summary of the Invention

[0005] Embodiments that are on the same basis as within the scope of the claimed subject matter are summarized below. These embodiments are not intended to limit the scope of the claimed subject matter; rather, these embodiments are intended only to provide a brief summary of possible forms of the subject matter. Indeed, the present subject matter can encompass various forms that can be similar or different from the embodiments disclosed below.

[0006] In one embodiment, the system can include a reader for reading identification information from one of a number of interface devices. The interface device can include a radio frequency identification (RFID) tag storing the identification information of the interface device. Further, the system can include a cleaning machine and a control device. The control device can include a processor and a memory, and the identification information from the reader or the interface device can receive the cleaning cycle information of the interface device from the cleaning system to determine whether the threshold level of efficiency degradation has been reached.

[0007] In one embodiment, the system can include an interface device for reversibly coupling to a display. The interface device can include a radio frequency identification (RFID) tag associated with the interface device storing the identification information of the interface device. The system can also include a reader for reading the identification information from the RFID tag, a cleaning system, and a control device including a processor and a memory. The control device can receive the identification information from the reader and the cleaning cycle information from the cleaning system. Further, the control device can associate the cleaning cycle information with the identification information. Additionally, the control device can determine that the threshold level of efficiency degradation has been reached based on the cleaning cycle information associated with the interface device, and can generate a notification that the interface device has reached the threshold level of efficiency degradation.

[0008] In one embodiment, the method can include receiving identification information from an interface device, cleaning the interface device, operating a cleaning machine to perform a cleaning cycle, associating cleaning cycle information from the cleaning cycle with the identification information, and determining a degradation status of the interface device based on the associated cleaning cycle information and the identification information. These and other features, aspects, and advantages of the present disclosure will be better understood when the following detailed description is read with reference to the accompanying drawings, in which like characters represent like parts throughout the figures.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Modes for Carrying Out the Invention

[0010] One or more specific embodiments will be described below. To provide a concise description of these embodiments, not all features of an actual implementation are described in this specification. It should be understood 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 developer's specific goals, such as compliance with various system-related and business-related constraints that vary depending on the implementation. Further, it should be understood that such development efforts, although complex and time-consuming, are routine tasks for those of ordinary skill in the art who have the benefit of this disclosure and are responsible for designing, making, and manufacturing.

[0011] When introducing elements of various embodiments of the present disclosure, the articles “a,” “an,” and “the” are intended to mean that there is one or more elements. The terms “comprising,” “including,” “having” are intended to be inclusive and mean that there can be additional elements other than the listed elements. Additionally, references to “one embodiment” or “an embodiment” of the present disclosure are not intended to be construed as excluding the existence of additional embodiments that also incorporate the recited features.

[0012] The present disclosure generally relates to systems and methods for cleaning / washing a portion of a HMD. In the amusement park industry, VR / AR devices have emerged as a promising way to provide a more immersive entertainment experience for park visitors. Specifically, an HMD having VR / AR capabilities can be linked to a specific ride or attraction to generate a VR / AR experience for that ride or attraction. In some cases, the HMD can be composed of two separate parts, namely, an interface device for the visitor and a display. The interface device can be made of plastic or other washable and reusable materials and can be washable during visitor use. The separate display can be electronic and in some cases can be connected to a specific ride vehicle or held with the attraction. In one embodiment, the interface device and the display are separated before the interface device is washed to protect the electronic components of the display from being exposed to the fluid. That is, only the interface device is washed in the washing system. The display portion can be cleaned or handled separately.

[0013] Provided herein is a technique for interface device cleaning that monitors and manages the attributes of an interface device when the interface device experiences a cleaning cycle. For example, when an individual interface device experiences a cleaning cycle, the material of the interface device or the individual components may degrade due to the cleaning state of the cycle or repeated use. Thus, by monitoring the attributes of the interface device, park employees can be informed that a given interface device has reached the end of its life and should be disposed of or repaired.

[0014] As an introduction, FIG. 1 is a schematic diagram of a workflow for HMD management including a cleaning system as provided in this specification. This workflow can start at the distribution 10 of the HMD. In the illustrated example, an employee 12 distributes an HMD or a part of the HMD, illustrated as an interface device 14, to a visitor 16. However, it should be understood that the disclosed embodiments can also be used in conjunction with an integral or inseparable HMD device.

[0015] When the visitor 16 enters the amusement park, the visitor 16 can be provided with the interface device 14 by the employee 12. In some embodiments, the timing and location of HMD distribution may vary. For example, in embodiments where a part of the amusement park is dedicated to VR / AR experiences, HMD distribution can be done at the entrance to the VR / AR part of the amusement park. Alternatively, HMD distribution can be done when the visitor 16 enters a designated vehicle or other means of transportation to the amusement park or a part of the amusement park. For example, if a bus or ferry is used to transport the visitor 16 to the amusement park, HMD distribution can be done while regularly moving to the amusement park via the bus or ferry (or other suitable means). It should be understood that the examples described are only intended to illustrate, and that there can be other examples where HMD distribution can be done.

[0016] Further, although employee 12 is seen to hand the interface device 14 to visitor 16, other methods can be used. For example, a mechanical dispenser can distribute the interface device 14 to visitor 16. The dispenser can be placed at key entrance locations of the amusement park to ensure that visitor 16 has an opportunity to receive the interface device 14. Further, in some embodiments, the interface device 14 can be placed at the seat of the VR / AR ride or other designated location for a given visitor 16. Thus, in some embodiments, employee 12 can strategically place the interface device 14 so that visitor 16 can receive the interface device 14 before the VR / AR ride begins. In another embodiment, the distribution can include distribution of the entire HMD rather than separable components.

[0017] After receiving the interface device 14, visitor 16 can board the vehicle 20. In the illustrated example, visitor 16 can sit in seat 22. Seat 22 is intended to be illustrative of any location where visitor 16 can be positioned during the course of the ride or amusement park experience. For example, seat 22 can be a location with or without armrests, a bed or other horizontal structure, or other location.

[0018] The components of the display 24 of the HMD can be connected to the seat 22 via the tether 26. In some embodiments, the display 24 can include a transparent screen to provide a VR / AR experience. The display 24 can be configured to be detachably coupled to the interface device 14 to form the entire HMD (see HMD 50, FIG. 2). For example, when entering the attraction 20, the visitor 16 or the operator can attach the display 24 to the interface device 14 in preparation for the VR / AR experience. At the end of the VR / AR experience, the visitor 16 or the operator can be prompted to remove the display 24 from the interface device 14. Thus, after the visitor 16 removes it from the interface device 14, the display 24 can remain connected to the seat 22. In this way, since the potential for damage (e.g., dropping, excessive handling) is lower, a relatively less expensive and more robust interface device 14 can be distributed to the visitors 16 while they move through the queue. The more expensive and fragile display portion can be provided to the visitors while they are seated or moved less freely. However, in this combination, the visitors 16 come into more direct contact with the interface device 14 as they wait in the queue and move towards the ride vehicle 20, and therefore the interface device 14 may need to be cleaned after each use. Further, with respect to FIG. 2, as discussed, the display portion 24 can be separated, in whole or in part, from direct visitor contact by the interface device 14 during use. Thus, the display 24 can experience less handling from the visitors 16.

[0019] In some embodiments, visitor 16 can enter into some of the attractions while visiting the amusement park. For example, after exiting the first VR / AR experience such as a roller coaster, visitor 16 can continue with another VR / AR enhanced ride or attraction. At the end of their visit to the amusement park or when an individual attraction is over, visitor 16 can enter the disembarkation area 30 with their user interface device 14, and visitor 16 can deposit the interface device 14 into a container or cart 32. For example, in some embodiments, cart 32 can be placed at the exit of attraction 20.

[0020] At some point (e.g., after the park closes for the day or after cart 32 is filled to a threshold level), cart 32 can be moved to a cleaning area 40 that includes a cleaning system 42. For example, in some embodiments, an employee can transport the interface device 14 with container 32 to the cleaning system 42. Once in the cleaning area, the interface device 14 can be individually or batch loaded into the cleaning system. Additionally or alternatively, as discussed herein, an automated system can transport the interface device to the cleaning system 42. Further, cleaning system 42 can be configured to track the viability of the interface devices 14 being cleaned and flag those interface devices 14 whose lifespan has expired for removal.

[0021] Next, returning to FIG. 2, the exemplary HMD 50 is illustrated with components including the interface device 14 and the display 24 or in separate fields of view. In some embodiments, the interface device 14 can be configured to fit adjustably on top of the head of the visitor 16. For example, knobs, buckles, securing straps, or other reversible fastening mechanisms can be used to fit the interface device 14 onto the head of the visitor 16. Further, the interface device 14 can include an identifier 52 to uniquely identify the interface device 14. In some embodiments, the identifier 52 can be an RFID tag or other identifier. In one embodiment, the identifier 52 is disposed on or within the interface device 14. In one embodiment, the identifier 52 is an RFID tag embedded in the material of the interface device 14, and the material of the interface device 14 enables the transmission of radio frequencies.

[0022] Particularly importantly, the identifier 52 can store data associated with the interface device 14, such as a unique identifier for the interface device 14. Further, in some embodiments, the identifier 52 can also store cleaning cycle data. Additionally or alternatively, the identifier 52 can be read by a reader to access cleaning cycle data stored on the cleaning system 42. The cleaning cycle data can include various data. For example, the cleaning cycle data can include a counter indicating how many cleaning cycles the interface device 14 has experienced. The data can also include information detailing the temperature, water pressure, cleaning time, chemical usage, and other settings of each cleaning cycle that the interface device 14 has experienced. The cleaning cycle data can further include any other details of the cleaning cycles that the interface device 14 has experienced to determine the extent of efficiency degradation of the interface device 14 due to the cleaning cycles.

[0023] While the disclosed embodiments are discussed in the context of RFID tags, it should be understood that other identifiers can be used. For example, identifier 52 can be an optical transmitter that provides a signal that can be read by a barcode, a visible marker, or a reader (e.g., an optical sensor or reader).

[0024] Interface device 14 can be configured to be detachably connected to display 24. For example, display 24 can be connected to the front portion of interface device 14 to form HMD 50. Additionally or alternatively, display 24 can be attached to the side or back of interface device 14. Further, display 24 can be connected to interface device 14 via a suitable coupling technique. For example, interface device 14 can have a snap-on feature that allows display 24 to snap closed to secure the connection. Further, Velcro (registered trademark) or other adhesive means can be used to connect display 24 to interface device 14. In certain embodiments, interface device 14 can include one or more integral magnets 54 that couple to corresponding magnets 56 of display 24 to attach interface device 14 and display 24. It should be understood that the number and relative positions of magnets 54, 56 are illustrated by way of example and other arrangements are also contemplated. When coupled and used together as HMD 50, interface device 14 can at least partially separate display portion 24 from direct patron contact.

[0025] The display 24 can include a screen 58. The screen 58 can be essentially transparent, translucent, or opaque. In one embodiment where the screen is transparent or translucent, when a visitor 16 activates a virtual feature (e.g., an AR feature) superimposed on the screen 58 such that the virtual feature is perceived to be integrated into the real-world environment, the screen 58 can enable the visitor to see the real-world environment (the physical structure in the attraction).

[0026] In some embodiments, the tether 26 can be attached to the display 24 to connect the display 24 to the vehicle. As shown in FIG. 1, the tether can be connected to the seat 22 of the vehicle. However, the tether 26 can be connected to any part of the vehicle. For example, in some embodiments, the tether 26 can be connected to the electronic system of the vehicle. For example, the tether 26 can include a connector for transmitting HDMI (registered trademark) or other data to supply AR / VR data from the electronic system to the display 24.

[0027] As discussed herein, the disclosed HMD 50 can be processed by the cleaning system 42. While the illustrated embodiment is directed to cleaning a separable or two-part interface device 14 separated from the display 24 in one embodiment of the HMD 50, it should be understood that the disclosed embodiment can also include cleaning an HMD 50 that includes electronic components mounted in a waterproof or water-resistant housing. As provided herein, the cleaning system 42 collects identification information from each cleaned interface device 14 such that the cleaning status of the interface device 14 can be tracked in terms of the total number of cleanings and in the embodiment. Based on the tracked information, individual interface devices 14 are identified at the end of their respective lifetimes.

[0028] In one embodiment, the life cycle status of the interface device 14 can be accessed by the display 24 in coupling the interface device 14 with the display 24. In one embodiment, the display 24 can directly read the status from the identifier 52. In another example, the display 24 can read the identification information of the interface device 14 from the identifier and communicate with another device to access the status information of the interface device 14 using the cleaning system 42 or the identification information. The status can include an acceptable status or an unacceptable status. The acceptable status can indicate that the interface device 14 is within its useful life (e.g., has not passed through the threshold number of cleaning cycles) or is above the threshold efficiency degradation status. The unacceptable status can be associated with the interface 14 of an individual being at the end of its life, e.g., having reached the threshold efficiency degradation status. In the coupling, any interface device 14 for attraction having an unacceptable status is flagged for replacement by the operator before the vehicle is actuated.

[0029] Returning to the discussion of FIG. 3, the cleaning system 42 can interact with the data from the identifier 52 of the interface device 14. Thus, the cleaning system 42 can include a reader 60. The reader 60 can obtain data from the identifier 52. For example, in one embodiment where the identifier 52 is an RFID tag, the reader 60 can be an RFID reader configured to read the data stored on the RFID tag. The data can include a unique identifier of the interface device 14. Further, in some embodiments where data for each interface device 14 is stored locally, the data can include cleaning cycle data of the interface device 14. For example, if the interface device 14 has experienced five cleaning cycles, the data can include the identification information of the interface device 14 as well as the cleaning cycle data for each of the five cleaning cycles experienced by the interface device 14.

[0030] The reader 60 can transmit data acquired by the control system 62 of the cleaning system 42. In some embodiments, the control system can include one or more processors 64 and one or more memory devices 66. The one or more processors 64 can execute software programs and / or instructions to track cleaning information or lifespan information of the one or more interface devices 14. Further, the processor(s) 64 can include multiple microprocessors, one or more "general-purpose" microprocessors, one or more special-purpose microprocessors, one or more application-specific integrated circuits (ASICs), and / or one or more reduced instruction set (RISC) processors. The memory device(s) 66 can include one or more storage devices and can store machine-readable and / or processor-executable instructions (e.g., firmware or software) for execution by the processor(s) 64. In some embodiments, the processor(s) 64 and the memory device(s) 66 can be external to the control system 62. The memory device(s) 66 can include tangible, non-transitory machine-readable media such as volatile memory (e.g., random access memory (RAM)) and / or non-volatile memory (e.g., read-only memory (ROM)), flash memory, hard drive, and / or any other suitable optical, magnetic, or solid-state storage medium. In one embodiment, the memory device(s) 66 can store a lookup table of the interface devices 14 and can organize cleaning cycle information associated with each interface device 14. For example, the cleaning cycle information can be stored in a database. The memory device(s) 66 can also store threshold information for the designation of interface device status such that it is allowed to expire or remain in use.

[0031] In some embodiments, the control system 62 can be configured to receive interface device identification information data from the reader 60, and the control system 62 can be configured to determine the status of the interface device 14 based on stored data associated with each interface device 14 (e.g., stored identification information) stored in the memory device(s) 66 of the control system 62. For example, if the memory device(s) 66 does not include a profile of the interface device 14 associated with the identification information, a profile can be generated and stored in the memory device(s) 66. This can indicate that the interface device 14 is new and not degraded as it has not experienced any wash cycles.

[0032] If the memory device(s) 66 includes a profile of the interface device 14 associated with the identification data, the status of the interface device 14 can be determined based on the data stored in the profile. For example, in some embodiments, the data can include a tracker such as a counter to determine how many wash cycles the interface device 14 has experienced. For example, the control system 62 can be configured to determine whether the interface device 14 has experienced a threshold number of wash cycles. In fact, exceeding the threshold can indicate that the interface device 14 has degraded to a point where it should be discarded beyond the course of the wash cycle. Thus, in one embodiment where the tracker indicates that the interface device 14 should be discarded, the control system 62 can flag the interface device 14 for discard as discussed herein. Additionally, the control system 62 can update the stored data for each interface device 14 by updating the data associated with a unique identifier to include the current or ongoing wash cycle.

[0033] In some embodiments, the control system 62 can further include a communication circuit 68. The communication circuit can include an antenna, a wireless transceiver circuit, signal processing hardware, and / or software (e.g., hardware or software filters, A / D converters, multiplexer amplifiers) or combinations thereof, and can be configured to communicate over a wireless communication path via infrared wireless communication, satellite communication, broadcast radio, microwave radio, Bluetooth®, Zigbee®, etc. Additionally, the communication circuit 68 can be connected to other means of communicating with the Internet or other electronic devices. For example, in some embodiments, the communication circuit can be connected to a nearby interface device 14 via a wireless connection. Further, the communication circuit 68 can be used to indicate the efficiency degradation level of the interface device 14 as determined by the control system 62. For example, in some embodiments, the communication circuit 68 can instruct the interface device 14 to display the status of its efficiency degradation. For example, the interface device 14 can include an LED, a display, or other indicator that can be activated when the interface device 14 reaches an efficiency degradation threshold level. Thus, the communication circuit 68 can send instructions to the interface device 14 to activate the indicator of the interface device 14.

[0034] Additionally, or alternatively, the cleaning system 42 can provide a notification via a user interface 69 of the cleaning system 42 that an employee can refer to in order to identify an interface device 14 that has been designated for discard. Additionally, or alternatively, the communication circuit 68 can send a status notification to a smartphone, laptop, tablet, or other personal electronic device of an employee of the amusement park or other individual / group where the user interface 69 can be viewed.

[0035] In some embodiments, the control system 62 can generate one or more instructions to display the status of the interface device 14 before the interface device 14 reaches the threshold level of efficiency degradation. For example, in some embodiments, it can be beneficial to know whether the interface device 14 is at, above, or near the threshold efficiency degradation level. Thus, in some embodiments, the status of the interface device 14 that is near the threshold efficiency degradation level can be displayed. For example, if the threshold efficiency degradation level is 100%, in some embodiments, the status of the interface device 14 having an efficiency degradation of 95% or more can be displayed, similar to when it is at or above the threshold efficiency degradation level. In such embodiments, the interface device 14 at the threshold efficiency degradation level can be shown differently than those that are not at the efficiency degradation level. For example, the interface device 14 at the threshold efficiency degradation level can be shown in the operator interface 69 in a highlighted color (e.g., red), while these that are near the threshold efficiency degradation level can be shown in a different color (e.g., yellow). Further, in some embodiments, the interface device 14 that exceeds the threshold efficiency degradation level can be shown with even differently colored lights or other markings.

[0036] In some embodiments, to distinguish between the interface device 14 to be removed and the interface device 14 that has been approved for redistribution to visitors, the status can be listed in text as "expired" at the threshold efficiency degradation level, when it is exceeded, or in some cases, when it is close to it, and as "not expired" when it is not at the threshold efficiency degradation level or in a similar designation. Thus, the interface device 14 at or above the threshold efficiency degradation level can be highlighted, made bold, or otherwise visually identified. For example, in some embodiments, the interface device 14 at or above the threshold efficiency degradation level can be spatially separated from other interface devices 14 (e.g., on a separate list, located at the top of the list, etc.). Further, any other suitable method for distinguishing the interface device 14 at or above the threshold efficiency degradation level from the interface device 14 that is not at the threshold efficiency degradation level can be used. It should be noted that the examples described are intended to be illustrative only. In fact, in some embodiments, most or all of the status of the interface device 14 can be displayed. In one embodiment, only the interface device 14 determined to be at the end of its life is displayed via the user interface 69 and / or an indicator on the interface device 14.

[0037] The cleaning system 42 can further include a cleaning device 70. The cleaning device 70 can be any device capable of cleaning the interface device 14. In some embodiments, the cleaning device 70 can be sized to clean several interface devices 14 simultaneously. For example, in some embodiments, the interface devices 14 can be grouped together into cleaning batches that can include 10, 100, 200, 300, 400, 500, or any other suitable number of interface devices 14.

[0038] Batches of the interface device 14 can be placed into the cleaning device 70 for cleaning. For example, in some embodiments, batches of the interface device 14 can be placed into the cleaning device 70 by an employee, such as by loading the mesh rack of the interface device 14. In another embodiment, an employee can retrieve the interface device 14 from the cart 32 and place them into the cleaning device 70. Additionally or alternatively, an automated system can transport batches of the interface device 14 to the cleaning device 70. For example, interface devices 14 can be co-located for transport via a conveyor belt to the cleaning device 70. Additionally or alternatively, the automated system can be coupled to the cart 32 to automatically receive and transport the interface device 14 when the interface device 14 is placed into the container 32. The automated system can be configured to direct the interface device 14 towards the cleaning device 70. Alternatively, in some embodiments, the automated system can be configured to direct the interface device 14 towards a storage location near the cleaning device 70. From there, an employee can place the interface device 14 into the cleaning device 70.

[0039] The cleaning device 70 can include several sub-components such as a temperature control device 72 and a fluid control device 74. The temperature control device 72 can include circuits and sensors to adjust and monitor the temperature of the cleaning device 70. For example, the temperature control device 72 can adjust the temperature of the liquid used in a given cleaning cycle. This can facilitate differentiating between types of cleaning cycles. For example, a light cleaning can operate at a first temperature and a heavy cleaning can operate at a second temperature. The first temperature can be a low temperature, a warm temperature, room temperature, or other similar temperature. In some embodiments, the second temperature can be a high temperature, for example, high enough to more thoroughly clean the interface device 14 than a light cleaning.

[0040] The temperature control device 72 can receive instructions from other circuits within the communication circuit 68 or the cleaning system 42 to determine how to adjust the temperature of the cleaning cycle. Additionally, the temperature control device 72 can use sensors or other circuits to monitor the temperature throughout the cleaning cycle. Thus, the temperature control device can adjust the temperature in the cleaning cycle based on the monitored temperature and the instructions. In some embodiments, the temperature control device 72 can ensure that the temperature remains constant throughout a given cleaning cycle based on the instructions and the monitored temperature. Additionally or alternatively, the temperature control device 72 can adjust the temperature over the course of a given cleaning cycle. For example, in some embodiments, the cleaning cycle can be run at different temperatures throughout the course of the cleaning cycle.

[0041] The fluid control device 74 can include circuits and sensors for controlling and monitoring the fluid of a predetermined cleaning cycle. For example, the fluid control device 74 can monitor the fluid level, pressure, movement, components, etc. in the cleaning device 70. For example, in a predetermined cleaning cycle, the height of the liquid level, pressure, movement, chemical composition, and other fluid characteristics can be adjusted over the course of the cleaning cycle. For example, during a predetermined sequence of the cleaning cycle, a first liquid pressure can be used, which can be increased or decreased during different sequences of the cleaning cycle. Further, a chemical substance such as a cleaning agent can be added to the fluid at a certain point in the cleaning cycle. The fluid control device 74 can control the activation and deactivation of these functions. Additionally or alternatively, the fluid control device 74 can adjust its functions based on command signals transmitted from other circuits within the communication circuit 68 or the cleaning system 42 that can command how the fluid of a predetermined cleaning cycle can be controlled.

[0042] It should be understood that in addition to or instead of the temperature control device 72 and the fluid control device 74, other control devices can be present in the cleaning device. Further, the cleaning device 70 can perform any number of cleaning methods in addition to those described. In fact, the cleaning device 70 can be configured to vary any number of temperatures, fluids, and other characteristics to complete the cleaning cycle. Further, after the cleaning cycle is completed or as part of the cleaning cycle, the cleaning device 70 can dry the interface device 14 either actively (e.g., via a fan, ultrasonic vibration, or other drying method) or passively (e.g., by waiting for a certain period of time for the interface device 14 in the interface device 14). The interface device 14 can then be prepared for reuse by being stored in a storage container for an employee to access when distributing the interface device 14 as described, for example, in FIG. 1.

[0043] Further, the temperature control device 72, the fluid control device 74, and any other control devices of the cleaning device 70 can be configured to transmit cleaning cycle data to the control system 62 for storage in a profile associated with the interface device 14 cleaned in the cleaning cycle. Thus, the profile of the interface device 14, and / or the interface devices 14 themselves, can store all of the cleaning cycle data associated with each respective interface device 14. The cleaning cycle data can, moreover, be accessed by the processor 64(s) of the control system 62 to determine the level of efficiency degradation of the interface device 14, as described above.

[0044] With the foregoing in mind, FIG. 4 illustrates an exemplary method 80 of operation of the cleaning system 42. In a first step 82, the reader 60 can receive an identification signal from the interface device 14. As discussed above, this signal can be an RFID signal received by the RFID reader of the reader 60. However, in some embodiments, other methods can be used to receive any type of identification signal.

[0045] In a second step 84, the control system 62 can access the cleaning cycle data of the interface device 14 corresponding to the identification signal. For example, the control system 62 can access the identification signal from the reader 60 via the communication circuit 68 from a profile stored in the memory device 66(s) or from the interface device 14 data. The identification signal can further include cleaning cycle data corresponding to the interface device 14. The controller control system 62 can access the cleaning cycle data from the identification signal via the processor 64(s) or any other suitable circuitry of the control system 62.

[0046] In the third step 86, the control system 62 can determine whether the interface device 14 has expired based on the cleaning cycle data. For example, as described above, the control system 62 can determine the efficiency degradation level of the interface device 14. For example, the control system 62 can determine the efficiency degradation level of the interface device 14 based on the number of cleaning cycles experienced by the interface device 14, the cleaning state of the previous cleaning cycle, or both. The control system 62 can also compare the efficiency degradation level of the interface device 14 with a threshold efficiency degradation level. Based on this determination, the status of the individual interface device 14 can be set to be expired and designated for removal from distribution, or not expired and designated for re-entry into the visitor distribution.

[0047] For example, the threshold efficiency degradation level is determined in advance by empirical evaluation and stored in the control system 62 or can be accessed in another way. In one example, the evaluation can be based on the number or nature of cleaning cycles associated with the inability of the interface device 14 to successfully magnetically couple with the display 24. The threshold efficiency degradation level can determine when an individual interface device 14 is expired and should be discarded or repaired. The threshold efficiency degradation level can be based on the number of cleaning cycles experienced by a given interface device 14. For example, if the number of cleaning cycles is greater than a pre-determined number (e.g., 10, 50, 100, 1000), the interface device is determined to be degraded. In another embodiment, the determination can be based on the cumulative effect of the cleaning conditions experienced by the interface device 14 on the integrity of the interface device 14. If the efficiency degradation level of the interface device 14 is greater than or equal to the threshold efficiency degradation level, the control system 62 can determine that the interface device 14 should be discarded as expired. If the efficiency degradation level of the interface device 14 is less than the threshold efficiency degradation level, the control system 62 can determine that the interface device 14 is not expired and can be reused.

[0048] In the fourth step 88, the control system 62 can generate a display of the efficiency degradation level of the interface device 14. In some embodiments, the communication circuit 68 can command the interface device 14 to indicate its efficiency degradation level using an indicator on or associated with the interface device 14. Additionally or alternatively, the control system 62 can generate a notification via the user interface 69. If the notification is a unique identifier associated with a degraded or end-of-life interface device 14, the method 80 can include receiving a second reading of the batch of interface devices 14 such that the identified interface device 14 can be distinguished. For example, it can be challenging to distinguish a degraded interface device 14 from a batch of interface devices 14 when the interface device 14 does not include an efficiency degradation indicator on any device. When a degraded interface device 14 is determined and identified and read, the system 42 can provide an instruction, for example, via the user interface 69, that a particular interface device 14 should be removed from the batch. The instruction can be audible, visual, tactile, or a combination thereof. If the interface device 14 is in a container with multiple interface devices 14, additional one-by-one reading steps can be performed.

[0049] As discussed, the control system 62 can determine the status of the interface device 14 by considering previous wash cycles. For example, in some embodiments, data can indicate the wash state that the interface device 14 experienced in a previous wash cycle. Thus, the control system 62 can determine the level of efficiency degradation of the interface device 14 based on the data. For example, the control system 62 can determine the percentage of efficiency degradation for the interface device 14. For example, if the wash settings for one wash (e.g., temperature, wash time, chemicals used, etc.) degrade the interface device 14 by 0.5%, and the interface device 14 has been washed 10 times (e.g., as indicated by a counter in the data or otherwise determined based on the data), then the control system 62 can determine that the interface device 14 has degraded by 5%. In some embodiments, 100% efficiency degradation can indicate that the interface device 14 is no longer operational for use and should be discarded. However, other thresholds can be used to ensure that the interface device 14 does not malfunction during use. For example, the control system 62 can be configured to flag for discard when each interface device 14 reaches an efficiency degradation of 50%, 60%, 70%, 80%, or 90% or any other efficiency degradation threshold level once.

[0050] The level of efficiency degradation can, in one embodiment, be an evaluation of the efficiency degradation based on the number of wash cycles completed and / or the wash cycle state. In one example, the interface device 14 can have a specific point value at the start of its life cycle, and by experiencing wash cycles, the control system 62 subtracts points from the total number of points. The end of life can be associated with the interface device 14 when the total number of points falls below a specific point total after a sufficient number of points have been subtracted.

[0051] The control system 62 can also determine a reduction in efficiency despite a non-uniform cleaning state. For example, in some embodiments, the interface device 14 can experience an irregular cleaning cycle as discussed herein. Thus, the control system 62 can determine the level of efficiency degradation of the interface device 14 that incorporates such irregularities into the calculations. For example, if the interface device 14 experiences a light cleaning and a heavy cleaning, each may potentially degrade the interface device 14 by 0.1% and 0.2% respectively. Thus, the control system 62 can determine that the efficiency degradation of the interface device 14 is at the 0.3% point based on the two cleaning cycles. This example is intended to be non-limiting, and it should be noted that there can be many non-uniform cleaning states that the control system 62 can consider to determine the level of efficiency degradation of the interface device 14. In some cases, the level of efficiency degradation is based on the total time exposed to a particular fluid, or at or beyond a certain temperature level (e.g., 30 degrees or more) or total time exceeded. Thus, if the total time at a high temperature during a cleaning cycle is unusually long, the total time is recorded and the interface device 14 from that particular batch may expire earlier compared to other batches. Thus, based on the state of individual cleaning cycles, some interface devices 14 may expire at different rates even if they have the same relative number of cleaning cycles.

[0052] The efficiency degradation status can, in embodiments, be based on profile data of the interface device 14 stored on the control system 62, for example, stored within the memory device(s) 66. In one embodiment, the efficiency degradation status can be stored directly on the interface device 14. Thus, the control system 62 can write data to the tag 52 of the interface device 14.

[0053] Furthermore, the efficiency degradation status of the interface device 14 can be determined at any time. For example, the status can be determined before the interface device 14 experiences a predetermined cleaning cycle. Thus, the interface device 14 can be flagged for removal either before or after the cleaning cycle. Additionally, or alternatively, the efficiency degradation status of the interface device 14 can be determined after a predetermined cleaning cycle. In such embodiments, the interface device 14 can be flagged for quick removal so that the interface device 14 does not remain in operation.

[0054] In some embodiments, an automated system can transport the interface device 14 to and from the cleaning device 70. Thus, FIG. 5 shows an exemplary embodiment of the automation system 100. The system 100 can include a transport device 102. In some embodiments, the transport device 102 can be a conveyor belt, a trolley, or any other automated movement mechanism. The interface device 14 can be positioned at the transport device 102, for example, by an employee or another transport system. Thereafter, the interface device 14 can be moved towards the cleaning device 70 via the transport device 102.

[0055] As described above, in some embodiments, the cleaning system 42 can instruct a predetermined interface device 14 to indicate whether there is a reduction in efficiency to a threshold efficiency reduction level or a reduction in efficiency exceeding the threshold efficiency reduction level. Thus, in some embodiments, the interface device 14 can include an LED light 104. The light 104 can be configured to turn on if there is a threshold level of efficiency reduction indicating that the interface device 14 should be expired and disposed of. Further, as previously described, there may be other ways to indicate that the interface device 14 has expired.

[0056] As illustrated, if the interface device 14 has expired, it will enter the waste container 106. From there, the expired interface device 14 can be disposed of by either an employee or some other automated system. Further, the waste container 106 can include a reader 108 to track the interface device 14 entering the waste container 106. For example, the reader 108 can be an RFID reader. The reader 108 can be used to ensure that the expired interface device 14 is properly moved to the waste container 106. For example, in some embodiments, the cleaning system 42 can include circuitry to communicate with the reader 108 to track the disposal of the expired interface device 14. In some embodiments, the communication circuitry 68 can receive a signal from the reader 108 and transmit that signal to other circuitry of the control system 62 to track the disposal of the expired interface device 14.

[0057] Alternatively, an interface device 14 that has not expired can enter into the cleaning device 70 and be cleaned accordingly. Further, in some embodiments, the waste container and the reader 108 can be disposed beyond the cleaning device 70. For example, in some embodiments, instead of determining the level of efficiency degradation before cleaning, the control system 62 can determine the level of efficiency degradation after each cleaning cycle. For example, if, as a result of a given cleaning cycle, one of the interface devices 14 meets or exceeds the efficiency degradation threshold level, then that interface device 14 can be moved to the waste container 106.

[0058] While only certain features of this specification have been illustrated and described herein, many modifications and changes will occur to those skilled in the art of this technology. Therefore, it is to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the disclosed embodiments.

[0059] The technology claimed and shown in this specification refers to and applies to tangible articles and specific examples of a practical nature that will surely improve this technical field and thus are not abstract, intangible, or purely theoretical. Further, if any claim appended hereto includes one or more elements designated as "means for [performing]... [function]" or "steps for [performing]... [function]", such elements are to be construed in accordance with 35 U.S.C. § 112(f). On the other hand, for any claim that includes elements designated in any other form, such elements are not to be construed in accordance with 35 U.S.C. § 112(f).

Claims

1. A head-mounted device cleaning system, comprising: A reader configured to read identification information from one of a plurality of interface devices, wherein the interface device among the plurality of interface devices includes a radio frequency identification (RFID) tag storing the identification information of the interface device; A cleaning system; A control device including a processor and a memory, Receiving the identification information from the reader, Receiving cleaning cycle information of the interface device from the cleaning system, The control device is configured to determine whether the interface device has reached a threshold level of efficiency degradation based on the identification information or the cleaning cycle information; A head-mounted device cleaning system including the above.

2. The system according to claim 1, wherein the control device is configured to identify the interface device based on the identification information and evaluate a current level of efficiency degradation of the interface device based on the cleaning cycle information. The system according to claim 1.

3. The system according to claim 2, wherein the control device is configured to determine that the interface device has reached a threshold level of efficiency degradation by comparing an evaluation level of efficiency degradation of the interface device with the threshold level of efficiency degradation. The system according to claim 2.

4. The system according to claim 1, wherein the cleaning cycle information indicates a cleaning state experienced by the interface device via the cleaning system. The system according to claim 1.

5. The system according to claim 1, wherein the cleaning system is configured to clean a plurality of interface devices with variable temperature and fluid settings. The system according to claim 1.

6. The system according to claim 5, wherein the cleaning cycle information includes temperature and fluid settings associated with past cleaning cycles of the interface device. The system according to claim 5.

7. The system according to claim 1, wherein the control device is configured to store respective profiles associated with each one of the plurality of interface devices. The system according to claim 1.

8. The system according to claim 7, wherein each respective profile includes respective identification information of each one of the plurality of interface devices. The system according to claim 7.

9. Each of the profiles includes cleaning cycle information indicating a cleaning state experienced by each one of the plurality of interface devices via the cleaning system. The system according to claim 7.

10. The interface device is configured to reversibly couple with a display to form a head-mounted device. The system according to claim 1.

11. A head-mounted device cleaning system includes an interface device configured to reversibly couple with a display, the interface device including a radio frequency identification (RFID) tag associated with the interface device, the RFID tag storing identification information of the interface device, a reader configured to read the identification information from the RFID tag, a cleaning system, a control device including a processor and a memory, receiving the identification information from the reader, receiving cleaning cycle information from the cleaning system, associating the cleaning cycle information with the identification information, determining that the interface device has reached a threshold level of efficiency degradation based on the associated cleaning cycle information, a control device for generating a notification that the interface device has reached a threshold level of efficiency degradation, and a system including the same.

12. The control device is configured to determine that the interface device has reached the threshold level of efficiency degradation based on the number of cleaning cycles of the interface device exceeding a predetermined threshold. The system according to claim 11.

13. The interface device is configured to be decoupled from the display before being cleaned by the cleaning system. The system according to claim 11.

14. The control device is configured to store a profile of the interface device in the memory, the profile including the identification information and the associated cleaning cycle information. The system according to claim 11.

15. The cleaning cycle information indicates a cleaning state experienced by the interface device via the cleaning system. The system according to claim 14.

16. The control device is configured to generate a command to activate an indicator on the interface device in response to the interface device reaching a threshold level of efficiency degradation. The system according to claim 11.

17. A method for cleaning a head-mounted device, receiving identification information from an interface device using a reader, activating a washer of a cleaning device to execute a cleaning cycle for cleaning the interface device, associating cleaning cycle information from the cleaning cycle with the identification information using a control system, determining an efficiency degradation status of the interface device based on the associated cleaning cycle information and the identification information using the control system. A method comprising the steps of:

18. Determining the efficiency degradation status includes determining that the cleaning status of the cleaning cycle combined with the previous cleaning status has cumulatively caused degradation of the interface device. The method according to claim 17.

19. Furthermore, via a control device, the interface device includes indicating that the expiration date has passed based on the efficiency degradation status and setting a flag for replacement on the interface device. The method according to claim 17.

20. The efficiency degradation status is associated with the interface device whose expiration date has passed based on the total number of the cleaning cycle of the interface device and the previous cleaning cycle exceeding a predetermined threshold. The method according to claim 19.

Images