Head wearable device configured to accommon multiple face profiles by adjusting depth between lens and wearer face

Abstract

Head wearable devices configured to accommodate multiple facial contours by adjusting the depth between a lens and a wearer's face and methods of using the same are provided. A head wearable device for presenting augmented reality includes a lens system and a facial interface. The face interface includes a portion configured to couple with the lens system via an adjustment mechanism assembly and a face interface portion configured to contact a face of a wearer. The adjustment mechanism assembly is configured to move the facial interface portion relative to the lens system to vary a depth (eye pitch) between a lens of the lens system and a face of the wearer between (i) a first depth configured to accommodate a first facial profile associated with a first wearer and (ii) a second depth configured to accommodate a second facial profile associated with a second wearer. The second depth is configured to accommodate a second facial profile associated with a second wearer.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 585,589, entitled “Head-Wearable Device Configured to Accommodate Multiple Facial Profiles by Adjusting a Depth Between a Lens and a Wearer's Face, and Methods and Use Thereof,” filed on September 26, 2023, and U.S. Non-Provisional Patent Application No. 18 / 736,302, filed on June 6, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure generally relates to mechanisms for adjusting the depth of eye relief between a lens of a head-wearable device (e.g., an extended reality headset (e.g., a mixed reality headset) that can present a virtual reality headset) and a wearer's eyes, including but not limited to a hook-and-mortise adjustment mechanism assembly that allows the wearer to adjust the depth of the lens to improve the eye relief by pressing a button on the head-wearable device and moving a lens holder of the head-wearable device relative to a facial interface of the head-wearable device. Background Art

[0004] A typical head-mounted view device worn on the head comes in only one size. However, facial profiles vary widely across the population. Differences in facial features (e.g., eyebrow, nose, and cheekbone size) may affect how the head-mounted view device contacts the wearer's face, thereby affecting the position of the wearer's eyes relative to the lenses of the head-mounted view device. Differences in the position of the wearer's eyes relative to the lenses of the head-mounted view device may result in an eye relief that is different from the ideal eye relief (the distance between the lens and the wearer's eyes) for using the head-mounted view device. The difference between the wearer's actual eye relief and the ideal eye relief may cause eye strain and / or eye fatigue to the wearer, and / or present a larger or smaller field of view than the developer of the head-mounted view device intended, all of which have a negative impact on the user experience. As a result, a significant portion of the population with larger or smaller facial features than average has a worse user experience when using a typical augmented reality (AR) device. Additionally, owners of head mounted view devices will often share their head mounted view devices with their friends and family, and therefore, a typical head mounted view device will need to accommodate a variety of different facial features.

[0005] Therefore, there is a need for a head mounted view device that allows the wearer to easily and quickly adjust the eye distance between the wearer's eyes and the lenses of the head mounted view device. A brief summary of solutions to the above problems is described below. Summary of the invention

[0006] An example of a head wearable device (e.g., an extended reality head-mounted view device (e.g., a mixed reality head-mounted view device) capable of displaying virtual reality to a user) is described herein. This exemplary head wearable device for presenting virtual reality includes a lens system and a facial interface. The facial interface includes a portion configured to be coupled to the lens system via an adjustment mechanism assembly and a facial interface portion configured to contact the face of a wearer. The adjustment mechanism assembly is configured to move the facial interface portion relative to the lens system so that the depth between the lens of the lens system and the face of the wearer (the depth between the lens of the lens system and the face of the wearer is the eye relief) varies between (i) a first depth and (ii) a second depth, the first depth being configured to accommodate a first facial profile associated with a first wearer, and the second depth being configured to accommodate a second facial profile associated with a second wearer. The change in depth between the lens of the lens system and the face of the wearer corresponds to a change in depth between a rear portion of the facial interface portion and the wearer's eyes.

[0007] The features and advantages described in the specification are not necessarily all-inclusive, and in particular, certain additional features and advantages are obvious to those of ordinary skill in the art in view of the drawings, the specification and the claims. In addition, it should be noted that the language used in the specification is mainly selected for readability and instructional purposes.

[0008] Having summarized the above exemplary aspects, a brief description of the drawings will now be given. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] For a better understanding of the various embodiments described, reference should be made to the following detailed description taken in conjunction with the accompanying drawings, in which like reference numerals refer to corresponding parts throughout the several views.

[0010] Figure 1 An exemplary head wearable device is shown, according to some embodiments, which is configured to allow a wearer to adjust the eye relief depth between the wearer's eyes and the lenses of the head wearable device.

[0011] FIG. 2A to FIG. 2B An exemplary hook-and-mortise adjustment mechanism assembly for adjusting the depth between a wearer's eyes and a lens of a head wearable device to improve eye relief is shown in accordance with some embodiments.

[0012] Figure 3A An exemplary visual indicator for indicating the depth of an eye relief mechanism to a user via a user interface displayed at an artificial reality head mounted viewer is shown in accordance with some embodiments.

[0013] Figure 3B An exemplary actuator adjustment mechanism assembly for adjusting the depth of a lens to improve eye relief is shown in accordance with some embodiments.

[0014] Figure 4A , Figure 4B , Figure 4C-1 and Figure 4C-2 An exemplary AR system is shown in accordance with some embodiments.

[0015] FIG. 5A to FIG. 5B An exemplary wrist wearable device is shown in accordance with some embodiments.

[0016] Fig. 6A , Figure 6B-1 , Figure 6B-2 and Figure 6C An exemplary head wearable device is shown in accordance with some embodiments.

[0017] FIG. 7A to FIG. 7B An exemplary handheld intermediate processing device is shown in accordance with some embodiments.

[0018] As a matter of practice, the various features shown in the drawings may not be drawn to scale. Therefore, for the sake of clarity, the sizes of the various features may be arbitrarily expanded or reduced. In addition, some of the drawings may not depict all of the components of a given system, method, or device. Finally, throughout the specification and drawings, the same reference numerals may be used to represent the same features. DETAILED DESCRIPTION

[0019] Numerous details are described herein to provide a thorough understanding of the exemplary embodiments shown in the accompanying drawings. However, some embodiments may be practiced without many of these specific details, and the scope of the claims is limited to only those features and aspects specifically recited in the claims. In addition, well-known processes, components, and materials are not necessarily described in detail to avoid obscuring the relevant aspects of the embodiments described herein.

[0020] Embodiments of the present disclosure may include various types or embodiments of extended reality systems, or be implemented in combination with various types or embodiments of extended reality systems. As described herein, extended reality (Extended-Reality, XR) is any superimposed functionality and / or sensory perceptible presentation provided by an XR system within a user's physical environment. Such XR may include and / or represent virtual reality (VR), AR, mixed reality (MR), or some combination thereof and / or a variation of one of them. For example, a user may perform an air swipe gesture to skip a song through a song providing an application programming interface (API) such as the following: the song providing API provides playback at a home speaker, for example. The XR environment described herein includes, but is not limited to: MR environments (including non-immersive VR environments, semi-immersive VR environments, and fully immersive VR environments); AR environments (including marker-based AR environments, markerless AR environments, location-based AR environments, and projection-based AR environments); hybrid reality; and other types of MR environments. The difference between MR and AR lies in their presentation of physical objects in the environment surrounding the head-mounted viewer. The MR head-mounted viewer presents a virtual reconstruction of physical objects from the surrounding physical environment, where in some embodiments, the reconstruction is generated using data from a camera and / or other one or more sensors. In addition to these virtual reconstructions, other virtual objects and environments are presented, where the other virtual objects and environments have no corresponding objects in the surrounding physical environment. The AR head-mounted viewer presents a perspective (pass-through) view of physical objects from the surrounding physical environment of the head-mounted viewer (for example, the user can directly view physical objects in the environment through one or more transparent lenses and / or one or more waveguides). In addition to the perspective view of the physical objects, AR enhancements are also presented via a display (for example, via a display, a projector, and a waveguide).

[0021] XR content may include fully generated content or generated content combined with captured (e.g., real-world) content. XR content may include video, audio, haptic events, or some combination thereof, any of which may be presented in a single channel or in multiple channels (e.g., stereo video that produces a three-dimensional effect to the viewer). In addition, in some embodiments, XR may also be associated with applications, products, accessories, services, or some combination thereof, which are used, for example, to create content in XR and / or otherwise used in XR (e.g., to perform activities in XR).

[0022] As described herein, gestures may include air gestures, surface contact gestures, and / or other gestures that can be detected and determined based on the movement of a single hand (e.g., a single-handed gesture performed by a user's hand detected by one or more sensors of a wearable device (e.g., electromyography (EMG) and / or an inertial measurement unit (IMU) of a wrist wearable device) and / or detected via image data as follows) and other gestures that can be detected and determined based on the combined movement of the user's hands: the image data is collected by an imaging device of the wearable device (e.g., a camera of a head wearable device). In some embodiments, air means that the user's hand does not contact a surface, object, or part of an electronic device (e.g., a head wearable device or other communicatively coupled device, such as a wrist wearable device). In other words, the gesture is performed in open air in 3D space and does not contact a surface, object, or electronic device. More generally, surface contact gestures (contact at a surface, object, user body part, or electronic device) are also contemplated in which contact (or intent to contact) is detected at a surface (e.g., a single finger tap or double finger tap on a table, on a user's hand or another finger, on a user's lap, on a sofa, on a steering wheel). The different gestures disclosed herein can be detected using image data and / or sensor data (e.g., neuromuscular signals sensed by one or more biopotential sensors (e.g., EMG sensors) or other types of data from other sensors (e.g., proximity sensors, time-of-flight (ToF) sensors, sensors of inertial measurement units)) detected by a wearable device worn by a user and / or other electronic devices owned by the user (e.g., smartphones, laptops, imaging devices, intermediate devices, and / or other devices described herein).

[0023] As described herein, the eye relief is the distance between the eye and the lens. The devices described herein include methods and systems for adjusting the eye relief depth between the wearer's eye and at least one lens of a lens system of a head wearable device using an adjustment mechanism assembly.

[0024] Figure 1An exemplary head wearable device 110 is shown, which is configured to allow a wearer 100 to adjust an eye relief depth, which is the depth between at least one lens of a lens system of the head wearable device and the wearer's eye, according to some embodiments. In some embodiments, the head wearable device includes four parts: a lens holder 120, a first frame member 130, a second frame member 140, and a facial interface 150. The lens holder 120 is coupled to the first frame member 130, and in some embodiments, the lens holder 120 is removably coupled to the first frame member 130. The facial interface 150 is coupled to the second frame member 140, and in some embodiments, the facial interface 150 is removably coupled to the second frame member 140. The first frame member 130 and the second frame member 140 are adjustably coupled so that when the first frame member 130 and the second frame member 140 remain coupled, a frame offset distance can be changed between at least two distances, the frame offset distance being the distance between the front side 131 of the first frame member and the back side 142 of the second frame member. In some embodiments, the head wearable device 110 is configured so that the wearer 100 can change the eye relief when wearing the head wearable device 110 and / or when not wearing the head wearable device 110. In some embodiments, the wearer 100 can change the depth and thereby adjust their personal eye relief by interacting with buttons, switches, dials, and / or sliders located on the surface of the head wearable device 110 and / or a user interface of the head wearable device 110.

[0025] In some embodiments, the head wearable device 110 is an MR head-mounted viewer configured to present MR and / or VR. In some embodiments, the lens holder 120 includes electronic components configured to present MR and / or VR to the wearer 100 when the wearer 100 wears the head wearable device 110. The lens holder 120 includes a lens system having at least two lenses. The facial interface 150 is configured to contact the wearer's face when the wearer 100 wears the head wearable device 110 (e.g., as shown in FIG. 1 ). Figure 1 ). At least one of the lens holder 120, the first frame member 130, the second frame member 140, or the facial interface 150 is made of a first material. In some embodiments, the first material is a plastic material, a plastic polymer material, and / or a thermoplastic material (e.g., polycarbonate, polyethylene, polypropylene). In some embodiments, the first frame member 130 and the second frame member 140 are adjustably coupled via at least one adjustment mechanism assembly (see FIG. 2A to FIG. 3BDetailed description is provided in further detail). In some embodiments, when the wearer 100 wears the head wearable device 110, at least one adjustment mechanism component is not visible to the wearer 100. In some embodiments, at least one adjustment mechanism component is made of a second material different from the first material. In some embodiments, at least one adjustment mechanism component is made of the first material, or a portion of at least one adjustment mechanism component is made of the first material. In some embodiments, the second material is a metal material (e.g., aluminum, magnesium, a composite material, copper, steel, an alloy).

[0026] In some embodiments, the first frame member 130 and the second frame member 140 are adjustably coupled by at least two adjustment mechanism assemblies. The head wearable device can be configured so that the first adjustment mechanism assembly is located on the left side of the head wearable device 110, and the second adjustment mechanism assembly is located on the right side of the head wearable device 110. The head wearable device can be configured so that the first adjustment mechanism assembly is located on the top side of the head wearable device 110, and the second adjustment mechanism assembly is located on the bottom side of the head wearable device 110. In some embodiments, the first adjustment mechanism assembly is configured to adjust the first frame member 130 relative to the second frame member 140 simultaneously with the second adjustment mechanism assembly.

[0027] In an alternative embodiment, the first frame member 130 can be integrally formed with the lens holder 120 to produce a combined lens-frame portion. Additionally, the second frame member can be integrally formed with the facial interface 150 to produce a combined frame-interface portion. Similar to the components described above, the combined lens-frame portion is adjustably coupled to the combined frame-interface portion such that the offset distance can be varied between at least two distances while the combined lens-frame portion and the combined frame-interface portion remain coupled.

[0028] FIG. 2A to FIG. 2B An exemplary hook-and-mortise adjustment mechanism assembly 200 for adjusting the eye relief (also referred to as "eye relief depth" or "depth") 274A-274B between at least one lens of a lens system of a head wearable device and the wearer's eye is shown in accordance with some embodiments. The hook-and-mortise adjustment mechanism assembly 200 adjustably couples the first frame member 130 to the second frame member 140. The hook-and-mortise adjustment mechanism assembly 200 includes a hook member 240, a tenon member 230, and a button 250. In some embodiments, the hook member 240 is coupled to the second frame member 140, and the tenon member 230 is coupled to the first frame member 130 (e.g., as shown in FIG. 2 ). FIG. 2A to FIG. 2B). In some embodiments, the hook member 240 is coupled to the first frame member 130, and the tongue member is coupled to the second frame member 140. In some embodiments, the button 250 is located on an inner portion of the head wearable device 110, which is a portion of the head wearable device 110 that faces the wearer's face (e.g., FIG. 2A to FIG. 2B In some embodiments, the button 250 is located on an external portion of the head wearable device 110, which is the portion of the head wearable device 110 that faces away from the wearer's face.

[0029] According to an exemplary embodiment, the hook member 240 includes at least one hook 242A to 242C (e.g., FIG. 2A to FIG. 2B 242A to 242C) and at least two grooves 244A to 244D adjacent to at least one hook 242A to 242C (e.g., as shown in FIG. FIG. 2A to FIG. 2B The tenon 230 includes a leaf spring portion 232 and a tenon portion 234. The tenon 230 is configured such that when the leaf spring portion 232 is in a relaxed state, the tenon portion 234 is located in one of the at least two slots 244A to 244D, and when the leaf spring portion 232 is in a compressed state, the tenon portion 234 is located behind the hook 240. When the leaf spring portion 232 is in a relaxed state and the tenon portion 234 is located in one of the at least two slots 244A to 244D, the tenon 230 cannot move relative to the hook 240 because at least one of the hooks 242A to 242C prevents movement of the tenon portion (e.g., as shown in FIG. 1 ). FIG. 2A to FIG. 2B 240). When the leaf spring portion 232 is in a compressed state and the tenon portion 234 is located behind the hook 240, the tenon 230 can move relative to the hook 240 because the hook 240 does not prevent the tenon portion 234 from moving. The button 250 is coupled to the tenon portion 234 so that when the button 250 is not pressed, the leaf spring portion 232 is in a relaxed state and the tenon 230 cannot move relative to the hook 240. When the button 250 is pressed, the thrust is transmitted to the tenon portion 234, and the leaf spring portion 232 enters a compressed state, and the tenon 230 can move relative to the hook 240.

[0030] The hook member 240 is coupled to the second frame member 140, which is coupled to the facial interface 150, and the tenon member 230 is coupled to the first frame member 130, which is coupled to the lens holder 120, so that when the tenon member 230 moves relative to the hook member 240, the eye relief changes. The hook-tenon adjustment mechanism assembly 200 is configured so that when the button 250 is pressed and the leaf spring portion 232 is in a compressed state, the wearer can move the tenon member 230 relative to the hook member 240 by pushing or pulling the first frame member 130 and the lens holder 120 and / or the second frame member 140 and the facial interface 150. The wearer can move the tenon member 230 relative to the hook member 240 until the eye relief 274A-274B is at a desired depth. When the eye relief 274A-274B is at a desired depth, the wearer releases the button 250, and the leaf spring portion 232 enters a relaxed state. When in a relaxed state, the tenon 230 cannot move relative to the hook 240, and the eye relief maintains its depth. In some embodiments, the hook-tenon adjustment mechanism assembly 200 can allow the eye relief to vary between at least two predetermined depths (e.g., 10 mm, 14 mm, 18 mm, and 22 mm), and thereby allow the frame offset distance to vary between at least two predetermined distances (e.g., 0 mm, 4 mm, 8 mm, and 12 mm) corresponding to at least two grooves 244A to 244D, respectively (e.g., four predetermined depths corresponding to FIG. 2A to FIG. 2B In some embodiments, the hook-and-mortise adjustment mechanism assembly 200 can allow the eye relief to be infinitely varied between a minimum depth and a maximum depth (e.g., between 0 mm and 30 mm), and thereby allow the frame offset distance to be infinitely varied between a minimum distance and a maximum distance (e.g., between 0 mm and 30 mm). In some embodiments, changing the eye relief depth provides tactile feedback to the wearer 100 (e.g., feedback provided by the mortise 230 moving along the hook 240).

[0031] In some embodiments, the head wearable device further includes a visual indicator to indicate the depth and / or relative depth of the eye relief to the wearer. In some embodiments, the visual indicator is located on the surface of the head wearable device 110 (e.g., visual indicators 260A to 260B displaying one to four colored circles corresponding to four predetermined depths, such as FIG. 2A to FIG. 2B In some embodiments, the visual indicator is displayed via a user interface of the head wearable device 110 (e.g., as shown in FIG. Figure 3A shown).

[0032] As an example of how the wearer may change the eye relief, according to some embodiments, FIG. 2A to FIG. 2B The tenon 230 is shown in two different positions relative to the hook 240 . Figure 2AThe hook-and-mortise adjustment mechanism assembly 200 is shown in a first position, wherein the mortise portion 234 is located in the first slot 244A. In the first position, the frame offset distance is the first offset distance 272A. The first offset distance 272A corresponds to the first eye relief depth, and the visual indicator 260A indicates to the wearer 100 that the eye relief is the first eye relief depth. To change the hook-and-mortise adjustment mechanism assembly 200 from the first position to the second position, the wearer 100 presses the button 250, which causes the leaf spring portion 232 to enter a compressed state and the mortise portion 234 to move behind the hook member 240. The wearer 100 slides the lens holder 120 and the first frame member 130 away from the wearer's face while continuing to press the button 250. As the wearer 100 slides the lens holder 120 and the first frame member 130, the mortise portion 234 passes the first hook 242A and moves to a position behind the second slot 244B. The wearer 100 then releases the button 250, which causes the leaf spring portion 232 to enter a relaxed state and the tongue portion 234 to move into the second slot 244B. Figure 2B The hook-and-mortise adjustment mechanism assembly 200 is shown in a second position, wherein the mortise portion 234 is located in the second slot 244B. In the second position, the frame offset distance is a second offset distance 272B. The second offset distance 272B corresponds to a second eye relief depth. In the second position, the visual indicator 260B indicates to the wearer 100 that the eye relief is the second eye relief depth. In some embodiments, the second offset distance is greater than the first offset distance (e.g., FIG. 2A to FIG. 2B shown).

[0033] The facial contour of the wearer 100 is one factor in determining the desired eye relief depth. For example, facial features such as larger than average eyebrows, larger than average noses, and / or larger than average cheekbones will result in a longer than ideal eye relief depth, while facial features such as smaller than average eyebrows, smaller than average noses, and / or smaller than average cheekbones will result in a shorter than ideal eye relief depth. FIG. 2A to FIG. 2B As shown, the first wearer 100A has a first facial profile and wears the head wearable device 110 with a first offset distance 272A in a first position, which provides an ideal eye relief depth 274A for the first wearer 100A. The second wearer 100B has a second facial profile and wears the head wearable device 110 with a second offset distance 272B in a second position, which provides an ideal eye relief depth 274B for the second wearer 100B. In some embodiments, the ideal eye relief depth is the eye relief depth that causes the least amount of eye fatigue and / or eye strain to the wearer 100 when the wearer 100 wears the head wearable device 110 and / or presents the wearer 100 with an expected field of view.

[0034] Figure 3A An exemplary alternative visual indicator for indicating the eye relief depth and / or the relative eye relief depth to the wearer 100 via a user interface (UI) 310 of the head wearable device 110 is shown. The user interface 310 includes a UI element 312 that indicates the eye relief depth and / or the relative eye relief depth to the wearer 100 (i.e., the UI element indicates the relative eye relief depth between the maximum eye relief depth and the minimum eye relief depth, such as Figure 3A In some embodiments, user interface 310 also includes additional UI elements 314A to 314D that allow wearer 100 to increase the eye relief depth (e.g., additional UI element 314B), decrease the eye relief depth (e.g., additional UI element 314A), set the eye relief depth to a current value (e.g., additional UI element 314C), and / or reset the eye relief depth to a previous value (e.g., additional UI element 314D).

[0035] Figure 3B An exemplary alternative adjustment mechanism assembly is shown. According to some embodiments, the adjustment mechanism assembly that adjustably couples the first frame member 130 and the second frame member 140 is an actuator 350. The actuator 350 couples the first frame member 130 and the second frame member 140 so that when the first frame member 130 and the second frame member 140 remain coupled, the frame offset distance can be changed between at least two distances, whereby the eye relief can be changed between at least two depths. In some embodiments, the wearer can change the eye relief depth by interacting with the user interface 310 and / or by interacting with a button 250, a switch, a dial, and / or a slider located on the surface of the head wearable device 110. In some embodiments, the actuator 350 can change the eye relief depth between at least two predetermined eye relief depths. In some embodiments, the actuator 350 can change the eye relief depth steplessly between a minimum eye relief depth and a maximum eye relief depth.

[0036] (A1) According to some embodiments, a head wearable device for presenting VR includes a lens system and a facial interface. The facial interface includes a portion configured to be coupled to the lens system via an adjustment mechanism assembly and a facial interface portion configured to contact a wearer's face. The adjustment mechanism assembly is configured to move the facial interface portion relative to the lens system so that the depth between the lens of the lens system and the wearer's face varies between (i) a first depth and (ii) a second depth, the first depth being configured to accommodate a first facial profile associated with a first wearer, and the second depth being configured to accommodate a second facial profile associated with a second wearer. In some embodiments, changing the depth between the lens of the lens system and the wearer's face changes the depth between the back of the facial interface portion and the wearer's eyes. For example, Figures 1 to 2B A head wearable device 110 including a lens system 120 and a facial interface is shown. The exemplary facial interface includes a portion 140 configured to be coupled to the lens system 120 via an adjustment mechanism assembly 200 and a facial interface portion 150 configured to contact the face of a wearer 100. The exemplary adjustment mechanism assembly 200 is configured to move the facial interface portion 150 relative to the lens system 120 so that the depth between the lens of the lens system and the wearer's face varies between (i) a first depth 272A configured to accommodate a first facial contour associated with the first wearer 100A and (ii) a second depth 272B configured to accommodate a second facial contour associated with the second wearer 100B.

[0037] (A2) In some embodiments of A1, the adjustment mechanism assembly is located on a first side of the facial interface, and the first side corresponds to the left side of the wearer's face. The head wearable device also includes a second adjustment mechanism assembly, which is positioned opposite to the adjustment mechanism assembly, so that the second adjustment mechanism assembly is located on a second side of the facial interface, and the second side corresponds to the right side of the wearer's face. In some embodiments, the second adjustment mechanism assembly is configured to move the facial interface relative to the lens system simultaneously with the adjustment mechanism assembly. For example, FIG. 2A to FIG. 2B A head wearable device 110 is shown having an adjustment mechanism assembly 200 located on a first side of a facial interface.

[0038] (A3) In some embodiments of any of A1 to A2, the adjustment mechanism assembly includes a button. The button is configured to move the facial interface portion relative to the lens system when the button is pressed, and to maintain the position of the facial interface portion relative to the lens system when the button is released. For example, FIG. 2A to FIG. 2B The adjustment mechanism assembly 200 is shown to include a button 250 that is configured to move the facial interface portion relative to the lens system when the button is pressed. FIG. 2A to FIG. 2BAlso shown is maintaining the position of the facial interface portion relative to the lens system when the button is released.

[0039] (A4) In some embodiments of any of A1 to A3, the button is located on an inner surface of the facial interface. In some embodiments, the inner surface of the facial interface is the surface that faces the wearer when the wearer wears the head wearable device. For example, FIG. 2A to FIG. 2B Button 250 is shown located on the interior surface of the facial interface.

[0040] (A5) In some embodiments of any one of A1 to A4, the button is located on an outer surface of the facial interface. The outer surface of the facial interface is the surface facing away from the wearer when the wearer wears the head wearable device. The facial interface is configured to be adjusted when the head wearable device is worn.

[0041] (A6) In some embodiments of any one of A1 to A5, the adjustment mechanism assembly further comprises at least one actuator configured to move the facial interface portion relative to the lens system. For example, Figure 3B An actuator 350 configured to move a facial interface portion relative to the lens system is shown.

[0042] (A7) In some embodiments of any of A1 to A6, the adjustment mechanism assembly further comprises two hooks and a tenon coupled to a spring. The tenon is configured to move between the two hooks when the spring is compressed to move the facial interface relative to the lens system, wherein (i) when the tenon is located within a first of the two hooks, the tenon is associated with a first depth, and (ii) when the tenon is located within a second of the two hooks, the tenon located within the second hook is associated with a second depth. In some embodiments, the spring is connected to the lens system and the two hooks are connected to the facial interface. For example, FIG. 2A to FIG. 2B An adjustment mechanism assembly including two hooks 242A- 242B and a tenon 234 coupled to a spring 232 is shown.

[0043] (A8) In some embodiments of any one of A1 to A7, the tenon, the spring, and the two hooks are configured so that when the head wearable device is worn, the tenon, the spring, and the two hooks are not visible. For example, FIG. 2A to FIG. 2B Shown are a tenon 234, a spring 232, and two hooks 242A-242B, each of which is configured to be invisible when the head wearable device is worn.

[0044] (A9) In some embodiments of any one of A1 to A8, the tenon, the spring, and the two hooks are made of a first material, and the lens system and the facial interface are made of a second material.

[0045] (A10) In some embodiments of any one of A1 to A9, the first material is a metal material.

[0046] (A11) In some embodiments of any one of A1 to A10, the second material is a thermoplastic material.

[0047] (A12) In some embodiments of any of A1 to A11, the depth between the lens of the lens system and the rear portion of the facial interface can vary between 0 mm and 30 mm. In some embodiments, the depth between the lens of the lens system and the rear portion of the facial interface can vary between 0 mm and 12 mm.

[0048] (A13) In some embodiments of any one of A1 to A12, the adjustment mechanism assembly is configured to vary the depth between the lens of the lens system and the wearer's face between two predetermined depths. For example, FIG. 2A to FIG. 2B Two predetermined depths 274A-274B are shown.

[0049] (A14) In some embodiments of any one of A1 to A13, the adjustment mechanism assembly is further configured to vary the depth between the lens of the lens system and the wearer's face between two additional predetermined depths. In some embodiments, the additional predetermined depth is different from the two predetermined depths.

[0050] (A15) In some embodiments of any one of A1 to A14, varying the depth between a lens of the lens system and a rear portion of the facial interface between a first of two predetermined depths and a second of the two predetermined depths provides tactile feedback to the wearer.

[0051] (A16) In some embodiments of any one of A1 to A15, the adjustment mechanism assembly is configured to have stepless adjustment so that the depth between the lens of the lens system and the wearer's face can be adjusted steplessly.

[0052] (A17) In some embodiments of any one of A1 to A16, the head wearable device also includes a visual indicator to indicate the depth between the lens of the lens system and the wearer's face.

[0053] (A18) In some embodiments of any one of A1 to A17, the visual indicator is displayed via a user interface of the head wearable device. For example, Figure 3A A visual indicator 312 displayed via the user interface 310 of the head wearable device 110 is shown.

[0054] (A19) In some embodiments of any one of A1 to A18, the visual indicator is located on a surface of the head wearable device. For example, FIG. 2A to FIG. 2B Visual indicators 260A-260B located on the surface of the head wearable device are shown.

[0055] (A20) In some embodiments of any one of A1 to A19, the depth between the lens of the lens system and the rear portion of the facial interface determines the eye relief between the lens system and the wearer's eye. For example, FIG. 2A to FIG. 2B The depth 272A-272B between the lens of the lens system and the back of the facial interface is shown and defines the eye relief 274A-274B between the lens system and the wearer's eye.

[0056] (B1) According to some embodiments, a facial interface includes a portion configured to be coupled to a lens system via an adjustment mechanism assembly and a facial interface portion configured to contact a wearer's face. The adjustment mechanism assembly is configured to move the facial interface portion relative to the lens system so that the depth between the lens of the lens system and the wearer's face varies between (i) a first depth and (ii) a second depth, wherein the first depth is configured to accommodate a first facial profile associated with a first wearer and the second depth is configured to accommodate a second facial profile associated with a second wearer. For example, Figures 1 to 2B The facial interface is shown to include a portion 140 configured to be coupled to the lens system 120 via an adjustment mechanism assembly 200 and a facial interface portion 150 configured to contact the face of the wearer 100. In the exemplary facial interface 150, the adjustment mechanism assembly 200 is configured to move the facial interface portion 150 relative to the lens system 120 so that the depth between the lens of the lens system and the wearer's face varies between (i) a first depth 274A configured to accommodate a first facial contour associated with the first wearer 100A and (ii) a second depth 274B configured to accommodate a second facial contour associated with the second wearer 100B.

[0057] (B2) In some embodiments of B1, the facial interface is further configured according to any of A1 to A20.

[0058] (C1) According to some embodiments, a lens system includes a portion configured to be coupled to a facial interface via an adjustment mechanism assembly and at least two lenses. The adjustment mechanism assembly is configured to move the facial interface relative to the lens system so that the depth between a lens of the at least two lenses and the face of a wearer varies between (i) a first depth and (ii) a second depth, wherein the first depth is configured to accommodate a first facial profile associated with a first wearer and the second depth is configured to accommodate a second facial profile associated with a second wearer. For example, Figures 1 to 2BA lens system 120 is shown that includes a portion 130 configured to be coupled to a facial interface 150 via an adjustment mechanism assembly 200 and at least two lenses. In the exemplary lens system 120, the adjustment mechanism assembly 200 is configured to move the facial interface 150 relative to the lens system 120 so that the depth between a lens of the at least two lenses and the face of the wearer 100 varies between (i) a first depth 274A configured to accommodate a first facial profile associated with the first wearer 100A and (ii) a second depth 274B configured to accommodate a second facial profile associated with the second wearer 100B.

[0059] (C2) In some embodiments of C1, the lens system is further configured according to any one of A1 to A20.

[0060] (D1) According to some embodiments, a method for adjusting the eye relief of a facial interface is performed at a head wearable device, the head wearable device including a facial interface portion configured to contact a wearer's face and a lens system configured to move relative to the facial interface via an adjustment mechanism assembly. The method includes: moving the facial interface portion of the head wearable device to a first depth relative to the lens system of the head wearable device via the adjustment mechanism assembly, wherein the first depth is configured to accommodate a first facial profile associated with a first wearer. The method also includes: moving the facial interface portion of the head wearable device to a second depth relative to the lens system of the head wearable device via the adjustment mechanism assembly, wherein the second depth is configured to accommodate a second facial profile associated with a second wearer. In some embodiments, the second depth is greater than the first depth. For example, Figures 1 to 2B A head wearable device 110 including a lens system 120 and a facial interface is shown. The exemplary facial interface includes a portion 140 configured to be coupled to the lens system 120 via an adjustment mechanism assembly 200 and a facial interface portion 150 configured to contact the face of a wearer 100. The exemplary adjustment mechanism assembly 200 is configured to move the facial interface portion 150 relative to the lens system 120 so that the depth between the lens of the lens system and the wearer's face varies between (i) a first depth 272A configured to accommodate a first facial contour associated with the first wearer 100A and (ii) a second depth 272B configured to accommodate a second facial contour associated with the second wearer 100B.

[0061] (D2) In some embodiments of D1, the facial interface is further configured according to any one of A1 to A20.

[0062] The above-mentioned devices, including systems, wrist wearable devices, head-mounted viewer devices, and smart textile-based clothing, are described in further detail below. The above-mentioned specific operations may occur due to specific hardware, which will be described in more detail below. The devices described below are not restrictive, and the features on these devices may be removed or additional features may be added to these devices. Different devices may include one or more similar hardware components. For the sake of brevity, similar devices and components are described below. Any differences in the devices and components will be described in the corresponding sections below.

[0063] As described herein, a processor (e.g., a central processing unit (CPU) or a microcontroller unit (MCU)) is an electronic component responsible for executing instructions and controlling the operation of an electronic device (e.g., a wrist wearable device 500, a head wearable device, a handheld intermediate processing device (HIPD) 700, a smart textile-based garment, or other computer system). There are various types of processors that may be used interchangeably or that are specifically required by the embodiments described herein. For example, the processor may be: (i) a general-purpose processor designed to perform various tasks, such as running software applications, managing operating systems, and performing arithmetic and logic operations; (ii) a microcontroller designed for specific tasks, such as controlling electronic devices, sensors, and motors; (iii) a graphics processing unit (GPU) designed to accelerate the creation and rendering of images, videos, and animations (e.g., VR animations such as three-dimensional modeling); (iv) a field-programmable gate array (FPGA) that can be programmed and reconfigured after manufacturing and / or customized to perform specific tasks, such as signal processing, cryptography, and machine learning; (v) a digital signal processor (DSP) designed to perform mathematical operations on signals such as audio, video, and radio waves. Those skilled in the art will appreciate that one or more processors of one or more electronic devices may be used in the various embodiments described herein.

[0064] As described herein, a controller is an electronic component that manages and coordinates the operation of other components within an electronic device (e.g., controlling inputs, processing data, and / or generating outputs). Examples of controllers may include: (i) a microcontroller, which includes small, low-power controllers commonly used in embedded systems and Internet of Things (IoT) devices; (ii) a Programmable Logic Controller (PLC), which may be configured for use in industrial automation systems to control and monitor manufacturing processes; (iii) a System-on-a-Chip (SoC) controller, which integrates multiple components such as a processor, memory, I / O interfaces, and other peripherals into a single chip; and / or a DSP. As described herein, a graphics module is a component or software module designed to handle graphics operations and / or processes, and may include a hardware module and / or a software module.

[0065] As used herein, memory refers to an electronic component in a computer or electronic device that stores data and instructions for access and operation by a processor. The devices described herein may include volatile memory and non-volatile memory. Examples of memory may include: (i) Random Access Memory (RAM) (e.g., Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Double Data Rate RAM (DDR RAM), or other random access solid-state memory devices), which is configured to temporarily store data and instructions; (ii) Read-Only Memory (ROM) (e.g., one or more portions of system firmware and / or a boot loader), which is configured to permanently store data and instructions; (iii) Flash memory, magnetic disk storage devices, optical disk storage devices, other non-volatile solid-state storage devices, which can be configured to store data in electronic devices (e.g., Universal Serial Bus (USB) drives, memory cards, and / or Solid-State Drives (SSD)); and (iv) Cache memory, which is configured to temporarily store frequently accessed data and instructions. As described herein, the memory may include structured data (e.g., a structured query language (SQL) database, a MongoDB database, GraphQL data, or JSON data). Other examples of memory may include: (i) profile data, which includes user account data, user settings, and / or other user data stored by the user; (ii) sensor data detected by one or more sensors and / or otherwise obtained; (iii) media content data, which includes stored image data, audio data, and documents, etc.; and (iv) application data, which may include data collected and / or otherwise obtained and stored during use of the application; and / or any other type of data described herein.

[0066] As described herein, the power system of an electronic device is configured to convert input power into a form that can be used to operate the device. The power system may include various components, including: (i) a power source, which may be an alternating current (AC) adapter power source or a direct current (DC) adapter power source; (ii) a charger input, which may be configured to use a wired connection and / or a wireless connection (the wired connection and / or the wireless connection may be part of a peripheral device interface, such as a universal serial bus (USB), a micro USB interface, near-field magnetic coupling, magnetic induction and magnetic resonance charging, and / or radio frequency (RF) charging); (iii) a power management integrated circuit, which is configured to distribute power to various components of the device and ensure that the device operates within safe limits (e.g., regulating voltage, controlling current, and / or managing heat dissipation); and / or (iv) a battery, which is configured to store power to provide available power to one or more components of the electronic device.

[0067] As described herein, a peripheral device interface is an electronic component (e.g., an electronic component of an electronic device) that allows the electronic device to communicate with other devices or peripherals and can provide a means for inputting and outputting data and signals. Examples of peripheral device interfaces may include: (i) a USB interface and / or a micro USB interface, wherein the USB interface or the micro USB interface is configured to connect a device to an electronic device; (ii) a Bluetooth interface, wherein the Bluetooth interface is configured to allow devices to communicate with each other, wherein the Bluetooth interface includes Bluetooth Low Energy (BLE); (iii) a Near Field Communication (NFC) interface, wherein the NFC interface is configured as a short-range wireless interface for operations such as access control; (iv) a POGO pin, wherein the POGO pin can be a small spring-loaded pin, wherein the small spring-loaded pin is configured to provide a charging interface; (v) a wireless charging interface; (vi) a Global Positioning System (GPS) interface; (vii) a Wi-Fi interface, wherein the WiFi interface is used to provide a connection between a device and a wireless network; and (viii) a sensor interface.

[0068] As described herein, a sensor is an electronic component (e.g., an electronic component located in and / or otherwise in electronic communication with an electronic device such as a wearable device) that is configured to detect physical and environmental changes and generate electrical signals. Examples of sensors may include: (i) an imaging sensor (e.g., including one or more cameras disposed on a corresponding electronic device) for collecting imaging data; (ii) a biopotential signal sensor; (iii) an inertial measurement unit (IMU) for detecting changes in, for example, angular rate, force, magnetic field, and / or acceleration; (iv) a heart rate sensor for measuring a user's heart rate; (v) an SpO2 sensor for measuring a user's blood oxygen saturation and / or other biometric data; (vi) a capacitive sensor for detecting changes in electrical potential near a portion of a user's body (e.g., a sensor-skin interface) and / or other devices or objects; and (vii) an optical sensor (e.g., a time-of-flight sensor, an infrared light sensor, or a visible light sensor) and / or a sensor for sensing data from a user or a user's environment. As described herein, a biopotential signal sensing component is a device (e.g., a biopotential signal sensor) for measuring electrical activity in the body. Some types of biopotential signal sensors include: (i) an electroencephalography (EEG) sensor configured to measure electrical activity in the brain to diagnose neurological diseases; (ii) an electrocardiography (ECG or EKG) sensor configured to measure the electrical activity of the heart to diagnose heart problems; (iii) an electromyography (EMG) sensor configured to measure the electrical activity of muscles and diagnose neuromuscular diseases; (iv) an electrooculography (EOG) sensor configured to measure the electrical activity of eye muscles to detect eye movements and diagnose eye diseases.

[0069] As described herein, an application (e.g., software) stored in a memory of an electronic device includes instructions stored in the memory. Examples of such applications include: (i) games; (ii) word processors; (iii) messaging applications; (iv) media streaming applications; (v) financial applications; (vi) calendars; (vii) clocks; (viii) web browsers; (ix) social media applications; (x) camera applications; (xi) web-based applications; (xii) health applications; (xiii) artificial reality (AR) applications; and / or any other application that may be stored in the memory. The application may operate in conjunction with data and / or one or more components of a device or a communicatively coupled device to perform one or more operations and / or functions.

[0070] As described herein, the communication interface module may include hardware and / or software capable of communicating data using any of the following: various custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, or MiWi), custom or standard wired protocols (e.g., Ethernet or HomePlug), and / or any other suitable communication protocol, including communication protocols that have not been developed as of the filing date of this application. A communication interface is a mechanism that enables different systems or devices to exchange information and data with each other, including hardware, software, or a combination of both hardware and software. For example, a communication interface may refer to a physical connector and / or port on a device that is capable of communicating with other devices (e.g., USB, Ethernet, High Definition Multimedia Interface (HDMI), or Bluetooth). In some embodiments, a communication interface may refer to a software layer that enables different software programs to communicate with each other (e.g., an application programming interface (API), and protocols such as Hypertext Transfer Protocol (HTTP) and Transmission Control Protocol / Internet Protocol (TCP / IP)).

[0071] As described herein, a graphics module is a component or software module designed to handle graphics operations and / or processes and may include a hardware module and / or a software module.

[0072] As described herein, a non-transitory computer-readable storage medium is a physical device or storage medium that can be used to store electronic data in a non-transitory form (eg, such that the data is permanently stored until it is intentionally deleted or modified).

[0073] Example AR System

[0074] Figure 4A , Figure 4B , Figure 4C-1 and Figure 4C-2 An exemplary extended reality system is shown in accordance with some embodiments. Figure 4A A first XR system 400a and a first exemplary user interaction using a wrist wearable device 500 , a head wearable device (eg, XR device 600 ), and / or a handheld intermediate processing device (HIPD) 700 are shown. Figure 4B A second XR system 400b and a second exemplary user interaction using the wrist wearable device 500, the XR device 600, and / or the HIPD 700 are shown. Figure 4C-1 and Figure 4C-2 A third XR system 400c and a third exemplary user interaction using a wrist wearable device 500, a head wearable device (e.g., a virtual reality (VR) device 610), and / or a HIPD 700 are shown. As will be appreciated by those skilled in the art upon reading the description provided herein, the exemplary XR system described above (described in detail below) may perform the above-referenced Figures 1 to 3B Various functions and / or operations are described.

[0075] References below FIG. 5A to FIG. 5B The wrist wearable device 500 and its components are described below with reference to FIG. 6A to FIG. 6C Describe the head wearable device and its components, refer to FIG. 7A to FIG. 7B Describe the HIPD 700 and its components. The wrist wearable device 500, the head wearable device, and / or the HIPD 700 can be communicatively coupled via a network 425 (e.g., cellular, near field, Wi-Fi, a personal area network, or a wireless local area network (wireless LAN)). In addition, the wrist wearable device 500, the head wearable device, and / or the HIPD 700 can also be communicatively coupled to one or more servers 430, computers 440 (e.g., laptops or computers), mobile devices 450 (e.g., smartphones or tablets), and / or other electronic devices via a network 425 (e.g., cellular, near field, Wi-Fi, a personal area network, or a wireless LAN).

[0076] Go to Figure 4A, showing a user 402 wearing a wrist wearable device 500 and an XR device 600, and placing a HIPD 700 on their desk. The wrist wearable device 500, the XR device 600, and the HIPD 700 facilitate the user's interaction with the XR environment. In particular, as shown in the first XR system 400a, the wrist wearable device 500, the XR device 600, and / or the HIPD 700 enable the presentation of one or more avatars 404, digital representations 406 of contacts, and virtual objects 408. As described below, the user 402 can interact with one or more avatars 404, digital representations 406 of contacts, and virtual objects 408 via the wrist wearable device 500, the XR device 600, and / or the HIPD 700.

[0077] User 402 may provide user input using any of: wrist wearable device 500, XR device 600, and / or HIPD 700. For example, user 402 may perform one or more gestures detected by: wrist wearable device 500 (e.g., using the gestures described below with reference to FIG. 1 ), to provide user input. FIG. 5A to FIG. 5B One or more EMG sensors and / or IMUs described herein) and / or XR device 600 (e.g., using the FIG. 6A to FIG. 6C Alternatively or additionally, user 402 may provide user input through one or more touch surfaces of wrist wearable device 500, XR device 600, and / or HIPD 700 and / or voice commands collected by microphones of wrist wearable device 500, XR device 600, and / or HIPD 700. In some embodiments, wrist wearable device 500, XR device 600, and / or HIPD 700 include a digital assistant to help the user provide user input (e.g., complete a sequence of operations, suggest different operations or commands, provide reminders, or confirm commands). In some embodiments, user 402 may provide user input through one or more facial gestures and / or facial expressions. For example, a camera of wrist wearable device 500, XR device 600, and / or HIPD 700 may track the eyes of user 402 to navigate a user interface.

[0078] The wrist wearable device 500, the XR device 600, and / or the HIPD 700 can operate alone or in combination to allow the user 402 to interact with an XR environment (e.g., an augmented reality environment or a mixed reality environment). In some embodiments, the HIPD 700 is configured to operate as a central hub or control center for the wrist wearable device 500, the XR device 600, and / or another communication coupling device. For example, the user 402 can provide input to interact with the XR environment at any one of the wrist wearable device 500, the XR device 600, and / or the HIPD 700, and the HIPD 700 can identify one or more back-end tasks and front-end tasks to perform the requested interaction and distribute instructions to perform one or more back-end tasks and front-end tasks at the wrist wearable device 500, the XR device 600, and / or the HIPD 700. In some embodiments, the backend task is a background processing task that is not perceptible to the user (e.g., rendering content, decompressing, or compressing), while the frontend task is a user-facing task that is perceptible to the user (e.g., presenting information to the user, or providing feedback to the user). FIG. 7A to FIG. 7B As described, the HIPD 700 can perform backend tasks and provide the wrist wearable device 500 and / or the XR device 600 with operation data corresponding to the performed backend tasks, so that the wrist wearable device 500 and / or the XR device 600 can perform frontend tasks. In this way, the HIPD 700, which has more computing resources and greater thermal headroom than the wrist wearable device 500 and / or the XR device 600, performs computing-intensive tasks and reduces the computer resource utilization and / or power usage of the wrist wearable device 500 and / or the XR device 600.

[0079] In the example shown in the first XR system 400a, the HIPD 700 identifies one or more backend tasks and frontend tasks associated with the following user request, and distributes instructions to cause the one or more backend tasks and frontend tasks to be performed: a user request to initiate an XR video call with one or more other users (represented by avatars 404 and digital representations 406 of contacts). In particular, the HIPD 700 performs backend tasks for processing and / or rendering image data (and other data) associated with the XR video call, and provides operating data associated with the performed backend tasks to the XR device 600, so that the XR device 600 performs frontend tasks for presenting the XR video call (e.g., presenting the avatars 404 and digital representations 406 of contacts).

[0080] In some embodiments, the HIPD 700 can be operated as a focus or anchor point for information presentation. This allows the user 402 to know generally where the information is presented. For example, as shown in the first XR system 400a, the avatar 404 and the digital representation 406 of the contact are presented above the HIPD 700. In particular, the HIPD 700 and the XR device 600 operate in conjunction to determine the location for presenting the avatar 404 and the digital representation 406 of the contact. In some embodiments, information can be presented within a predetermined distance from the HIPD 700 (e.g., within five meters). For example, as shown in the first XR system 400a, the virtual object 408 is presented on the table at a certain distance from the HIPD 700. Similar to the above example, the HIPD 700 and the XR device 600 can be combined to operate to determine the location for presenting the virtual object 408. Alternatively, in some embodiments, the presentation of information is not constrained by the HIPD 700. More specifically, the avatar 404 , the digital representation of the contact 406 , and the virtual object 408 do not have to be presented within a predetermined distance of the HIPD 700 .

[0081] User input provided at the wrist wearable device 500, the XR device 600, and / or the HIPD 700 is coordinated so that the user can use any device to start an operation, continue an operation, and / or complete an operation. For example, the user 402 can provide user input to the XR device 600 to cause the XR device 600 to present a virtual object 408, and when the virtual object 408 is presented by the XR device 600, the user 402 can provide one or more gestures via the wrist wearable device 500 to interact with and / or manipulate the virtual object 408.

[0082] Figure 4B The user 402 is shown wearing the wrist wearable device 500 and the XR device 600 and holding the HIPD 700. In the second XR system 400b, the wrist wearable device 500, the XR device 600, and / or the HIPD 700 are used to receive one or more messages and / or provide one or more messages to contacts of the user 402. In particular, the wrist wearable device 500, the XR device 600, and / or the HIPD 700 detect and coordinate one or more user inputs to launch a messaging application and prepare a response to a message received via the messaging application.

[0083] In some embodiments, the user 402 launches an application on the wrist wearable device 500, the XR device 600, and / or the HIPD 700 via a user input that causes the application to be launched on at least one device. For example, in the second XR system 400b, the user 402 performs a gesture associated with a command for launching a messaging application (represented by the messaging user interface 412), the wrist wearable device 500 detects the gesture, and based on determining that the user 402 is wearing the XR device 600, causes the XR device 600 to present the messaging user interface 412 of the messaging application. The XR device 600 can present the messaging user interface 412 to the user 402 through its display (e.g., as shown in the field of view 410 of the user 402). In some embodiments, the application is launched and can be run on the device (e.g., the wrist wearable device 500, the XR device 600, and / or the HIPD 700) that detects the user input to launch the application, and the device provides another device running data to cause the messaging application to be presented. For example, the wrist wearable device 500 can detect user input for launching a messaging application, launch and run the messaging application, and provide running data to the XR device 600 and / or HIPD 700 so that the messaging application is presented. Alternatively, the application can be launched and run on a device other than the device that detects the user input. For example, the wrist wearable device 500 can detect a gesture associated with launching a messaging application and cause the HIPD 700 to run the messaging application and coordinate the presentation of the messaging application.

[0084] In addition, user 402 can provide user input provided at wrist wearable device 500, XR device 600, and / or HIPD 700 to continue and / or complete an operation initiated at another device. For example, after launching a messaging application via wrist wearable device 500, and when XR device 600 presents messaging user interface 412, user 402 can provide input at HIPD 700 to prepare a response (e.g., as shown by a sliding gesture performed on HIPD 700). The gesture of user 402 performed on HIPD 700 can be provided and / or displayed on another device. For example, the sliding gesture performed by user 402 on HIPD 700 is displayed on the virtual keyboard of the messaging user interface 412 displayed by XR device 600.

[0085] In some embodiments, the wrist wearable device 500, the XR device 600, the HIPD 700, and / or other communication coupling devices may present one or more notifications to the user 402. The notification may be an indication of a new message, an incoming call, an application update, a status update, and the like. The user 402 may select the notification via the wrist wearable device 500, the XR device 600, or the HIPD 700, and cause an application or operation associated with the notification to be presented on at least one device. For example, the user 402 may receive a notification that a message is received at the wrist wearable device 500, the XR device 600, the HIPD 700, and / or other communication coupling devices, and provide user input at the wrist wearable device 500, the XR device 600, and / or the HIPD 700 to view the notification, and the device detecting the user input may cause the application associated with the notification to be launched and / or presented at the wrist wearable device 500, the XR device 600, and / or the HIPD 700.

[0086] Although the above example describes coordinated input for interacting with a messaging application, a person skilled in the art will understand upon reading this specification that user input can be coordinated to interact with any number of applications, including but not limited to gaming applications, social media applications, camera applications, web-based applications, financial applications, etc. For example, XR device 600 can present gaming application data to user 402, and HIPD 700 can use a controller to provide input to the game. Similarly, user 402 can use wrist wearable device 500 to activate the camera of XR device 600, and the user can use wrist wearable device 500, XR device 600, and / or HIPD 700 to manipulate image acquisition (e.g., zoom in or out, or apply filters) and capture image data.

[0087] Go to Figure 4C-1 and Figure 4C-2 , showing that the user 402 is wearing a wrist wearable device 500 and a mixed reality (MR) device 610 capable of displaying virtual reality (VR), and holding a HIPD 700. In the third XR system 400c, the wrist wearable device 500, the MR device 610, and / or the HIPD 700 are used to interact within an MR environment (e.g., a VR game or other XR application). When the MR device 610 presents a representation of a VR game (e.g., a first XR game environment 420) to the user 402, the wrist wearable device 500, the MR device 610, and / or the HIPD 700 detect and coordinate one or more user inputs to allow the user 402 to interact with the VR game.

[0088] In some embodiments, the user 402 may provide user input via the wrist wearable device 500, the MR device 610, and / or the HIPD 700, which may cause an action to be generated in the corresponding XR environment. Figure 4C-1 4) raises the HIPD 700 in preparation for swinging in the first XR gaming environment 420. The MR device 610 causes the XR representation 422 of the user to perform a similar action (e.g., raise a virtual object such as a virtual sword 424) in response to the user 402 raising the HIPD 700. In some embodiments, each device uses corresponding sensor data and / or image data to detect user input and provide an accurate representation of the movement of the user 402. For example, the image sensor 758 of the HIPD 700 (e.g., described below) Fig. 7A and Figure 7B The simultaneous localization and mapping (SLAM) camera or other camera discussed in the previous section can be used to detect the position of the HIPD 700 relative to the body of the user 402 so that the virtual objects can be properly positioned within the first XR game environment 420; the sensor data from the wrist wearable device 500 can be used to detect the speed at which the user 402 raises the HIPD 700 so that the user's XR representation 422 and the virtual sword 424 are synchronized with the movement of the user 402; and the imaging sensor 626 ( FIG. 6A to FIG. 6C ) can be used to represent real-world objects, the body of the user 402, or boundary conditions within the first XR gaming environment 420.

[0089] exist Figure 4C-2 In the embodiment of the present invention, the user 402 swings downward while holding the HIPD 700. The wrist wearable device 500, the MR device 610 and / or the HIPD 700 detect the downward swing of the user 402 and perform a corresponding action in the first XR game environment 420. In some embodiments, the data collected by each device is used to improve the user experience in the XR environment. For example, the sensor data of the wrist wearable device 500 can be used to determine the speed and / or force of performing the downward swing, and the image sensor of the HIPD 700 and / or the MR device 610 can be used to determine the position of the swing and how the swing should be represented in the first XR game environment 420, which can then be used as input to the XR environment (e.g., the following game mechanism): the game mechanism can use the detected speed, force, position and / or aspects of the action of the user 402 to classify the user's input (e.g., the user performs a light blow, a heavy blow, a vital attack, a flash, a miss) or calculate the output (e.g., the amount of damage).

[0090] Although the wrist wearable device 500, the MR device 610, and / or the HIPD 700 are described as detecting user input, in some embodiments, the user input is detected at a single device (where the single device is responsible for distributing signals to other devices to perform the user input). For example, the HIPD 700 can run an application for generating the first XR gaming environment 420, and provide corresponding data to the MR device 610 so that the first XR gaming environment 420 is presented, (when the user holds the HIPD 700), and the HIPD 700 also detects the movement of the user 402 to cause the corresponding action to be performed within the first XR gaming environment 420. Additionally or alternatively, in some embodiments, the operating data (e.g., sensor data, image data, application data, device data, and / or other data) of one or more devices is provided to a single device (e.g., HIPD 700) to process the operating data and cause the corresponding device to perform an action associated with the processed operating data.

[0091] Having discussed exemplary XR systems, devices for interacting with such XR systems, and other computing systems, devices, and components in relatively general terms, they will now be discussed in greater detail below. For ease of reference, some definitions of devices and components that may be included in some or all of the exemplary devices discussed below are defined herein. Those skilled in the art will appreciate that certain types of components described below may be more suitable for a particular set of devices and less suitable for a different set of devices. However, subsequent references to components defined herein should be considered to be included in the definitions provided.

[0092] In some embodiments discussed below, exemplary devices and systems including electronic devices and systems will be discussed. Such exemplary devices and systems are not intended to be limiting, and those skilled in the art will appreciate that alternative devices and systems to the exemplary devices and systems described herein may be used to perform the operations described herein and to construct the systems and devices described herein.

[0093] As described herein, an electronic device is a device that uses electrical energy to perform a specific function. An electronic device can be any physical object that contains electronic components such as transistors, resistors, capacitors, diodes, and integrated circuits. Examples of electronic devices include smart phones, laptop computers, digital cameras, televisions, game consoles, and music players, as well as the exemplary electronic devices discussed herein. As described herein, an intermediate electronic device is a device that is located between two other electronic devices and / or a subset of components of one or more electronic devices and facilitates communication and / or data processing and / or data transmission between the corresponding electronic devices and / or electronic components.

[0094] Example wrist wearable device

[0095] Figure 5A and Figure 5B An exemplary wrist wearable device 500 is shown in accordance with some embodiments. Figure 5A Various components of wrist wearable device 500 are shown, which can be used alone or in combination, including combinations containing other electronic devices and / or electronic components.

[0096] Figure 5A Wearable band 510 and watch body 520 (or bladder) are shown coupled (as discussed below) to form wrist wearable device 500. Wrist wearable device 500 can perform various functions and / or operations associated with navigating through a user interface and selectively opening applications, as well as the above-referenced Figure 4A to Figure 4C-2 Describes the functionality and / or operation.

[0097] As will be described in more detail below, operations performed by wrist wearable device 500 may include: (i) presenting content to a user (e.g., displaying visual content via display 505); (ii) detecting (e.g., sensing) user input (e.g., sensing a touch on peripheral button 523 and / or a touch at a touch screen of display 505, a gesture detected by a sensor (e.g., a biopotential sensor)); (iii) sensing biometric data (e.g., neuromuscular signals, heart rate, temperature, or sleep) via one or more sensors 513; messaging (e.g., text, voice, or video messaging); image acquisition via one or more imaging devices or cameras 525; wireless communications (e.g., cellular, near-field, Wi-Fi, or personal area network); location determination; financial transactions; providing tactile feedback; alerts; notifications; biometric authentication; health monitoring; and / or sleep monitoring.

[0098] The above exemplary functions may be performed independently in the watch body 520, independently in the wearable band 510, and / or via electronic communication between the watch body 520 and the wearable band 510. In some embodiments, when an AR environment is presented (e.g., via one of the XR systems 400a to 400c), the functions may be performed on the wrist wearable device 500. As will be understood by those skilled in the art upon reading the description provided herein, the novel wearable device described herein may be used with other types of XR environments.

[0099] The wearable band 510 can be configured to be worn by a user so that the inner (or inner side) surface of the wearable structure 511 of the wearable band 510 contacts the user's skin. When worn by the user, the sensor 513 contacts the user's skin. The sensor 513 can sense biometric data, such as the user's heart rate, saturated oxygen level, temperature, sweat level, neuromuscular signals, or a combination thereof. The sensor 513 can also sense data about the user's environment, including the user's movement, altitude, position, orientation, gait, acceleration, positioning, or a combination thereof. In some embodiments, the sensor 513 is configured to track the positioning and / or movement of the wearable band 510. One or more sensors 513 may include those defined above and / or described below. Figure 5B Any sensor discussed.

[0100] One or more sensors 513 may be distributed on the inner surface and / or outer surface of the wearable band 510. In some embodiments, one or more sensors 513 are evenly spaced along the wearable band 510. Alternatively, in some embodiments, one or more sensors 513 are positioned at different points along the wearable band 510. Figure 5A As shown, one or more sensors 513 may be the same or different. For example, in some embodiments, the shape of one or more sensors 513 may be determined as a sheet (e.g., sensor 513a), an ellipse, a circle, a square, an oblong (e.g., sensor 513c), and / or any other shape that maintains contact with the user's skin (e.g., so that neuromuscular signals and / or other biometric data can be accurately measured at the user's skin). In some embodiments, one or more sensors 513 are aligned to form a sensor pair (e.g., for sensing neuromuscular signals based on differential sensing within each corresponding sensor). For example, sensor 513b is aligned with an adjacent sensor to form sensor pair 514a, and sensor 513d is aligned with an adjacent sensor to form sensor pair 514b. In some embodiments, the wearable band 510 does not have a sensor pair. Alternatively, in some embodiments, the wearable band 510 has a predetermined number of sensor pairs (a pair of sensors, three pairs of sensors, four pairs of sensors, six pairs of sensors, or sixteen pairs of sensors).

[0101] The wearable band 510 may include any suitable number of sensors 513. In some embodiments, the number and arrangement of sensors 513 depends on the specific application in which the wearable band 510 is used. For example, a wearable band 510 configured as an armband, wristband, or chest band may include multiple sensors 513 with a different number of sensors 513 and a different arrangement for each use case (e.g., a medical use case compared to a gaming or general everyday use case).

[0102] According to some embodiments, the wearable band 510 also includes an electrical ground electrode and a shield electrode. Like the sensor 513, the electrical ground electrode and the shield electrode can be distributed on the inner surface of the wearable band 510 so that they contact a portion of the user's skin. For example, the electrical ground electrode and the shield electrode can be located at the inner surface of the coupling mechanism 516 or the inner surface of the wearable structure 511. The electrical ground electrode and the shield electrode can be formed as the sensor 513, and / or use the same components as the sensor 513. In some embodiments, the wearable band 510 includes more than one electrical ground electrode and more than one shield electrode.

[0103] The sensor 513 may be formed as part of the wearable structure 511 of the wearable band 510. In some embodiments, the sensor 513 is flush or substantially flush with the wearable structure 511 so that the sensors do not extend beyond the surface of the wearable structure 511. In the case where the sensor 513 is flush with the wearable structure 511, the sensor 513 is still configured to contact the user's skin (e.g., through a skin contact surface). Alternatively, in some embodiments, the sensor 513 extends beyond the wearable structure 511 by a predetermined distance (e.g., 0.1 mm to 2 mm) to contact the user's skin and press against the user's skin. In some embodiments, the sensor 513 is coupled to an actuator (not shown) that is configured to adjust the extension height of the sensor 513 (e.g., the distance from the surface of the wearable structure 511) so that the sensor 513 contacts the user's skin and presses against the user's skin. In some embodiments, the actuator adjusts the extension height to between 0.01 mm and 1.2 mm. This allows the user to customize the position of sensor 513 to improve the overall comfort when wearing wearable band 510, while still allowing sensor 513 to contact the user's skin. In some embodiments, sensor 513 is indistinguishable from wearable structure 511 when worn by the user.

[0104] The wearable structure 511 can be formed of an elastic material, an elastomer, etc., which is configured to be stretched and adapted to be worn by a user. In some embodiments, the wearable structure 511 is a textile or a woven fabric. As described above, the sensor 513 can be formed as a part of the wearable structure 511. For example, the sensor 513 can be molded into the wearable structure 511 or integrated into the woven fabric (for example, the sensor 513 can be sewn into the fabric and simulate the flexibility of the fabric (for example, the sensor 513 can be composed of a series of woven fabric strands)).

[0105] The wearable structure 511 may include flexible electronic connectors that will be enclosed in the wearable band 510 sensors 513, electronic circuits and / or (hereinafter referred to as Figure 5BIn some embodiments, the flexible electronic connector is configured to interconnect the sensor 513, electronic circuits, and / or other electronic components of the wearable band 510 with corresponding sensors and / or other electronic components of another electronic device (e.g., watch body 520). The flexible electronic connector is configured to move with the wearable structure 511 so that the user's adjustment of the wearable structure 511 (e.g., resizing, pulling, or folding) does not cause stress or strain on the electrical coupling of the components of the wearable band 510.

[0106] As described above, the wearable band 510 is configured to be worn by the user. In particular, the wearable band 510 can be shaped or otherwise manipulated to be worn by the user. For example, the wearable band 510 can be shaped to have a generally circular shape so that the wearable band can be configured to be worn on the user's forearm or wrist. Alternatively, the wearable band 510 can be shaped to be worn on another body part of the user, such as the user's upper arm (e.g., around the biceps), forearm, chest, leg, etc. The wearable band 510 may include a retaining mechanism 512 (e.g., a buckle, or a hook and loop fastener, etc.) for fixing the wearable band 510 to the user's wrist or other body part. When the user wears the wearable band 510, the sensor 513 senses data from the user's skin (referred to as sensor data). In particular, the sensor 513 of the wearable band 510 obtains (e.g., senses and records) neuromuscular signals.

[0107] The sensed data (e.g., sensed neuromuscular signals) can be used to detect and / or determine the user's intention to perform certain motor actions. In particular, when the user performs muscle activation (e.g., movement or gesture), the sensor 513 senses and records neuromuscular signals from the user. The detected and / or determined motor actions (e.g., phalangeal (or finger) movements, wrist movements, hand movements, and / or other muscle intentions) can be used to determine control commands or control information (instructions for executing certain commands after the data is sensed) for causing the computing device to execute one or more input commands. For example, the sensed neuromuscular signals can be used to control certain user interfaces displayed on the display 505 of the wrist wearable device 500, and / or can be transmitted to a device responsible for rendering the XR environment (e.g., a head-mounted display) to perform actions in the associated XR environment, such as to control the movement of a virtual device displayed to the user. Muscle activations performed by a user may include static gestures, such as placing the user's palm down on a table; dynamic gestures, such as grabbing a physical or virtual object; and covert gestures that are imperceptible to another person, such as slightly tensing a joint by co-contracting opposing muscles or using sub-muscular activation. Muscle activations performed by a user may include symbolic gestures (e.g., gestures that are mapped to other gestures, interactions, or commands (e.g., based on a gesture vocabulary that specifies a mapping of gestures to commands)).

[0108] Sensor data sensed by sensor 513 can be used to provide a user with improved interaction with physical objects (e.g., devices communicatively coupled to wearable band 510) and / or virtual objects in an XR application generated by the XR system (e.g., user interface objects presented on display 505 or another computing device (e.g., a smartphone)).

[0109] In some embodiments, the wearable band 510 includes one or more haptic devices 546 ( Figure 5B ; e.g., vibrotactile actuators), the one or more haptic devices being configured to provide tactile feedback (e.g., skin and / or kinesthetic sensations) to the user's skin. Sensors 513 and / or haptic devices 546 may be configured to operate in conjunction with a plurality of applications, including but not limited to health monitoring, social media, gaming, and XR (e.g., applications associated with XR).

[0110] The wearable band 510 may also include a coupling mechanism 516 for removably coupling a bladder (e.g., a computing unit) or a watch body 520 (via a coupling surface of the watch body 520) to the wearable band 510 (e.g., a bracket or shape of the coupling mechanism may correspond to the shape of the watch body 520 of the wrist wearable device 500). In particular, the coupling mechanism 516 may be configured to receive a coupling surface near the bottom side of the watch body 520 (e.g., a side of the watch body 520 opposite to the front side where the display 505 is located), so that a user can push the watch body 520 downward into the coupling mechanism 516 to attach the watch body 520 to the coupling mechanism 516. In some embodiments, the coupling mechanism 516 may be configured to receive a top side of the watch body 520 (e.g., a side of the watch body 520 near the front side where the display 505 is located), which is pushed upward into the bracket instead of being pushed downward into the coupling mechanism 516. In some embodiments, coupling mechanism 516 is an integrated component of wearable band 510, such that wearable band 510 and coupling mechanism 516 are a single unitary structure. In some embodiments, coupling mechanism 516 is a type of frame or shell, which allows the coupling surface of watch body 520 to be held inside or on coupling mechanism 516 (e.g., a bracket, tracker band, support base, or buckle) of wearable band 510.

[0111] The coupling mechanism 516 may allow the watch body 520 to be removably coupled to the wearable band 510 by friction fit, magnetic coupling, a rotation-based connector, a shear pin coupling, a retaining spring, one or more magnets, a clamp, a pin, a hook and loop fastener, or a combination thereof. The user may perform any type of motion to couple the watch body 520 to the wearable band 510 and to separate the watch body 520 from the wearable band 510. For example, the user may twist, slide, turn, push, pull, or rotate the watch body 520 relative to the wearable band 510, or a combination of the above actions, to attach the watch body 520 to the wearable band 510 and to detach the watch body 520 from the wearable band 510. Alternatively, as discussed below, in some embodiments, the watch body 520 may be separated from the wearable band 510 by actuating a release mechanism 529.

[0112] The wearable band 510 can be coupled to the watch body 520 to increase the functionality of the wearable band 510 (e.g., converting the wearable band 510 into a wrist wearable device 500, adding additional computing units and / or batteries to increase the computing resources and / or battery life of the wearable band 510, or adding additional sensors to improve the sensed data). As described above, the wearable band 510 (and the coupling mechanism 516) are configured to operate independently of the watch body 520 (e.g., perform functions independently). For example, the coupling mechanism 516 may include one or more sensors 513 that contact the user's skin when the user wears the wearable band 510 and provide sensor data for determining control commands.

[0113] The user can remove the watch body 520 (or the bladder) from the wearable band 510 to reduce the burden on the user of the wrist wearable device 500. For embodiments in which the watch body 520 is detachable, the watch body 520 can be referred to as a detachable structure, so that in these embodiments, the wrist wearable device 500 includes a wearable portion (e.g., the wearable band 510) and a detachable structure (watch body 520).

[0114] Turning to the watch body 520, the watch body 520 may have a generally rectangular or circular shape. The watch body 520 is configured to be worn by a user on their wrist or another body part. More specifically, the watch body 520 is sized to be easily carried by a user, attached to a portion of a user's clothing, and / or coupled to the wearable band 510 (forming a wrist wearable device 500). As described above, the watch body 520 may have a shape corresponding to the coupling mechanism 516 of the wearable band 510. In some embodiments, the watch body 520 includes a single release mechanism 529 or multiple release mechanisms (e.g., two release mechanisms 529 (e.g., spring-loaded buttons) located on opposite sides of the watch body 520) for separating the watch body 520 and the wearable band 510. The release mechanism 529 may include, but is not limited to, a button, a knob, a plunger, a handle, a lever, a fastener, a buckle, a dial, a latch, or a combination thereof.

[0115] The user can actuate the release mechanism 529 by pushing, turning, lifting, depressing, shifting the release mechanism 529, or performing other actions on the release mechanism 529. Actuating the release mechanism 529 can release (e.g., separate) the watch body 520 from the coupling mechanism 516 of the wearable band 510, thereby allowing the user to use the watch body 520 independently of the wearable band 510, and vice versa. For example, separating the watch body 520 from the wearable band 510 can allow the user to use the rear camera 525b to capture images. Although the release mechanism 529 is shown as being located at a corner of the watch body 520, the release mechanism 529 can be located at any position on the watch body 520 that is convenient for the user to actuate. In addition, in some embodiments, the wearable band 510 may also include a corresponding release mechanism for separating the watch body 520 from the coupling mechanism 516. In some embodiments, the release mechanism 529 is optional, and the watch body 520 can be separated from the coupling mechanism 516 in the manner described above (e.g., by twisting or rotating, etc.).

[0116] The watch body 520 may include one or more peripheral buttons 523 and 527 for performing various operations at the watch body 520. For example, the peripheral buttons 523 and 527 may be used to turn on or wake up the display 505 (e.g., transition from a sleep state to an active state), unlock the watch body 520, increase or decrease the volume, increase or decrease the brightness, interact with one or more applications, interact with one or more user interfaces. Additionally or alternatively, in some embodiments, the display 505 operates as a touch screen and allows a user to provide one or more inputs for interacting with the watch body 520.

[0117] In some embodiments, the watch body 520 includes one or more sensors 521. The sensors 521 of the watch body 520 may be the same as or different from the sensors 513 of the wearable band 510. The sensors 521 of the watch body 520 may be distributed on the inner surface and / or the outer surface of the watch body 520. In some embodiments, the sensors 521 are configured to contact the user's skin when the user wears the watch body 520. For example, the sensor 521 may be placed on the bottom side of the watch body 520, and the coupling mechanism 516 may be a bracket with an opening that allows the bottom side of the watch body 520 to directly contact the user's skin. Alternatively, in some embodiments, the watch body 520 does not include a sensor configured to contact the user's skin (e.g., including a sensor located inside and / or outside the watch body 520 configured to sense data of the watch body 520 and the surrounding environment of the watch body 520). In some embodiments, the sensor 513 is configured to track the position and / or movement of the watch body 520.

[0118] The watch body 520 and the wearable band 510 can share data using a wired communication method (e.g., a Universal Asynchronous Receiver / Transmitter (UART) or a USB transceiver) and / or a wireless communication method (e.g., near field communication or Bluetooth). For example, the watch body 520 and the wearable band 510 can share data sensed by the sensors 513 and 521 as well as application and device specific information (e.g., active and / or available applications), output devices (e.g., a display, or a speaker, etc.), and / or input devices (e.g., a touch screen, a microphone, or an imaging sensor).

[0119] In some embodiments, the watch body 520 may include, but is not limited to, a front camera 525a and / or a rear camera 525b, sensors 521 (e.g., a biometric sensor, an IMU sensor, a heart rate sensor, a saturated oxygen sensor, a neuromuscular signal sensor, an altimeter sensor, a temperature sensor, a bioimpedance sensor, a pedometer sensor, an optical sensor (e.g., Figure 5B ; imaging sensor 563), touch sensor, or sweat sensor). In some embodiments, the watch body 520 may include one or more haptic devices 576 (eg, haptic devices 576) configured to provide tactile feedback (eg, skin and / or kinesthetic sensations) to the user. Figure 5B ; vibrotactile actuator). The sensor 521 and / or haptic device 576 may also be configured to operate in conjunction with a plurality of applications, including but not limited to health monitoring applications, social media applications, gaming applications, and XR applications (e.g., applications associated with XR).

[0120] As described above, the watch body 520 and the wearable band 510 can form the wrist wearable device 500 when coupled. When coupled, the watch body 520 and the wearable band 510 operate as a single device to perform the functions described herein (e.g., operation, detection, or communication). In some embodiments, specific instructions for performing one or more operations of the wrist wearable device 500 are provided to each device. For example, based on a determination that the watch body 520 does not include a neuromuscular signal sensor, the wearable band 510 may include alternative instructions for executing related instructions (e.g., providing sensed neuromuscular signal data to the watch body 520 via a different electronic device). The operation of the wrist wearable device 500 can be performed by the watch body 520 alone or in combination with the wearable band 510 (e.g., via corresponding processors and / or hardware components), or vice versa. In some embodiments, the operation of the wrist wearable device 500, the watch body 520, and / or the wearable band 510 can be combined with another communication coupling device (e.g., FIG. 7A to FIG. 7B; HIPD 700) is executed by one or more processors and / or hardware components.

[0121] As referenced below Figure 5B As described in the block diagram of FIG. 5 , the wearable band 510 and / or the body 520 may each include independent resources required to independently perform each function. For example, the wearable band 510 and / or the body 520 may each include a power source (e.g., a battery), a memory, a data storage device, a processor (e.g., a CPU), a communication device, a light source, and / or an input / output device.

[0122] Figure 5B A block diagram of computing system 530 corresponding to wearable band 510 and computing system 560 corresponding to watch body 520 is shown according to some embodiments. According to some embodiments, the computing system of wrist wearable device 500 includes a combination of components of computing system 530 of wearable band and components of computing system 560 of watch body.

[0123] The watch body 520 and / or the wearable band 510 may include one or more components shown in the computing system 560 of the watch body. In some embodiments, a single integrated circuit includes all or most of the components included in the computing system 560 of the watch body. Alternatively, in some embodiments, the components of the computing system 560 of the watch body are included in multiple integrated circuits that are communicatively coupled. In some embodiments, the computing system 560 of the watch body is configured to be coupled to the computing system 530 of the wearable band (e.g., via a wired connection or a wireless connection), which allows the computing systems (separately or as a single device) to share components, distribute tasks, and / or perform other operations described herein.

[0124] The computing system 560 of the watch body may include one or more processors 579, a controller 577, a peripheral device interface 561, a power system 595, and memory (e.g., memory 580), each of which is defined above and described in more detail below.

[0125] The power system 595 may include a charging input 596, a power management integrated circuit (PMIC) 597, and a battery 598, each of which is defined above. In some embodiments, the body 520 and the wearable band 510 may have respective charging inputs (e.g., charging inputs 596 and 557), respective batteries (e.g., batteries 598 and 559), and may share power with each other (e.g., the body 520 may power and / or charge the wearable band 510, and vice versa). Although the body 520 and / or the wearable band 510 may include respective charging inputs, when the two devices are coupled, a single charging input may charge the two devices. The body 520 and the wearable band 510 may be charged using various technologies. In some embodiments, the body 520 and the wearable band 510 may be charged using a wired charging assembly (e.g., a power cord). Alternatively or additionally, the body 520 and / or the wearable band 510 may be configured for wireless charging. For example, the portable charging device can be designed to match a portion of the watch body 520 and / or the wearable band 510 and wirelessly deliver available power to the battery of the watch body 520 and / or the wearable band 510. The watch body 520 and the wearable band 510 can have independent power systems (e.g., power systems 595 and 556) to enable each to operate independently. The watch body 520 and the wearable band 510 can also share power (e.g., one can charge the other) via respective PMICs (e.g., PMICs 597 and 558), which can share power through power and ground conductors and / or through wireless charging antennas.

[0126] In some embodiments, the peripheral device interface 561 may include one or more sensors 521, many of which are defined above. The sensor 521 may include one or more coupling sensors 562 for detecting when the watch body 520 is coupled to another electronic device (e.g., the wearable band 510). The sensor 521 may include an imaging sensor 563 (one or more cameras 525 and / or a separate imaging sensor 563 (e.g., a thermal imaging sensor)). In some embodiments, the sensor 521 includes one or more SpO2 sensors 564. In some embodiments, the sensor 521 includes one or more biopotential signal sensors (e.g., an EMG sensor 565 that may be disposed on a user-facing portion of the watch body 520 and / or the wearable band 510). In some embodiments, the sensor 521 may include one or more capacitive sensors 566. In some embodiments, the sensor 521 includes one or more heart rate sensors 567. In some embodiments, the sensor 521 includes one or more IMUs 568. In some embodiments, the one or more IMUs 568 may be configured to detect movement of a user's hand or other positions where the watch body 520 is placed or held.

[0127] In some embodiments, the peripheral device interface 561 includes a near field communication (NFC) component 569, a global positioning system (GPS) component 570, a long-term evolution (LTE) component 571, and / or a Wi-Fi and / or Bluetooth communication (WiFi / BT) component 572. In some embodiments, the peripheral device interface 561 includes one or more buttons 573 (e.g., Figure 5A 520 ), which, when selected by the user, cause operations to be performed at the watch body 520. In some embodiments, the peripheral device interface 561 includes one or more indicators, such as light emitting diodes (LEDs), to provide visual indications to the user (e.g., received messages, low battery, active microphone and / or camera).

[0128] The watch body 520 may include at least one display 505 for displaying visual representations of information or data to the user, including user interface elements and / or three-dimensional (3D) virtual objects. The display may also include a touch screen for inputting user inputs (e.g., touch gestures, sliding gestures, etc.). The watch body 520 may include at least one speaker 574 and at least one microphone 575 for providing audio signals to the user and receiving audio inputs from the user. The user may provide user inputs through the microphone 575 and may also receive audio output from the speaker 574 as part of a tactile event provided by the tactile controller 578. The watch body 520 may include at least one camera 525, including a front camera 525a and a rear camera 525b. The camera 525 may include an ultra-wide-angle camera, a wide-angle camera, a fisheye camera, a spherical camera, a telephoto camera, a depth sensing camera, or other types of cameras.

[0129] The computing system 560 of the watch body may include one or more haptic controllers 578 and associated components (e.g., haptic devices 576) for providing haptic events at the watch body 520 (e.g., vibration sensations or audio outputs in response to events at the watch body 520). The haptic controller 578 may communicate with one or more haptic devices 576, such as electroacoustic devices including speakers in one or more speakers 574 and / or other audio components that convert energy into linear motion and / or electromechanical devices (e.g., electromechanical devices such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators), or other haptic output generating components (e.g., components that convert electrical signals into haptic outputs on the device). The haptic controller 578 may provide haptic events that can be sensed by a user of the watch body 520 to the corresponding haptic actuators. In some embodiments, the one or more haptic controllers 578 may receive input signals from one of the multiple applications 582.

[0130] In some embodiments, computing system 530 and / or computing system 560 may include memory 580, which may be controlled by one or more controllers 577 and / or a memory controller of one or more processors 579. In some embodiments, the software components stored in memory 580 include one or more applications 582 configured to perform operations at the watch body 520. In some embodiments, the one or more applications 582 include games, word processors, messaging applications, call applications, web browsers, social media applications, media streaming applications, financial applications, calendars, clocks, etc. In some embodiments, the software components stored in memory 580 include one or more communication interface modules 583 as defined above. In some embodiments, the software components stored in memory 580 include one or more graphics modules 584 for presenting, encoding and / or decoding audio and / or video data; and one or more data management modules 585 for collecting, organizing and / or providing access to data 587 stored in memory 580. In some embodiments, one or more applications 582 and / or one or more modules may work in conjunction with each other to perform various tasks at the watch body 520.

[0131] In some embodiments, the software components stored in the memory 580 may include one or more operating systems 581 (e.g., Linux-based operating systems, Android operating systems, etc.). The memory 580 may also include data 587. The data 587 may include profile data 588A, sensor data 589A, media content data 590, and application data 591.

[0132] It should be understood that the computing system 560 of the watch body is an example of a computing system within the watch body 520, and that the watch body 520 may have more or fewer components, combine two or more components, and / or have a different configuration and / or arrangement of components than those shown in the computing system 560 of the watch body. The various components shown in the computing system 560 of the watch body are implemented in hardware, software, firmware, or a combination thereof, including one or more signal processing integrated circuits and / or application specific integrated circuits.

[0133] Turning to the computing system 530 of the wearable band, one or more components that may be included in the wearable band 510 are shown. The computing system 530 of the wearable band may include more or fewer components than those shown in the computing system 560 of the watch body, combine two or more components, and / or have a different configuration and / or arrangement of some or all components. In some embodiments, all or most of the components of the computing system 530 of the wearable band are included in a single integrated circuit. Alternatively, in some embodiments, the components of the computing system 530 of the wearable band are included in multiple integrated circuits that are communicatively coupled. As described above, in some embodiments, the computing system 530 of the wearable band is configured to be coupled to the computing system 560 of the watch body (e.g., via a wired connection or a wireless connection), which allows these computing systems (individually or as a single device) to share components, distribute tasks, and / or perform other operations described herein.

[0134] Similar to the computing system 560 of the watch body, the computing system 530 of the wearable band may include one or more processors 549, one or more controllers 547 (including one or more tactile controllers 548), a peripheral device interface 531 (which may include one or more sensors 513 and other peripherals), a power source (e.g., a power system 556), and a memory (e.g., a memory 550), which includes an operating system (e.g., an operating system 551), data (e.g., data 554 including profile data 588B, sensor data 589B), and one or more modules (e.g., a communication interface module 552, a data management module 553, etc.).

[0135] Based on the above definition, the one or more sensors 513 may be similar to the sensor 521 of the computing system 560. For example, the sensors 513 may include one or more coupling sensors 532, one or more SpO2 sensors 534, one or more EMG sensors 535, one or more capacitive sensors 536, one or more heart rate sensors 537, and one or more IMU sensors 538.

[0136] Peripheral device interface 531 may also include other components similar to those included in peripheral device interface 561 of computing system 560, including NFC component 539, GPS component 540, LTE component 541, Wi-Fi and / or Bluetooth communication (WiFi / BT) component 542, and / or one or more haptic devices 576 as described above with reference to peripheral device interface 561. In some embodiments, peripheral device interface 531 includes one or more buttons 543, display 533, speaker 544, microphone 545, and camera 555. In some embodiments, peripheral device interface 531 includes one or more indicators, such as LEDs.

[0137] It should be understood that the computing system 530 for the wearable band is an example of a computing system inside the wearable band 510, and the wearable band 510 may have more or fewer components, combine two or more components, and / or have a different configuration and / or arrangement of components than those shown in the computing system 530 for the wearable band. The various components shown in the computing system 530 for the wearable band may be implemented in one or a combination of hardware, software, and firmware including one or more signal processing integrated circuits and / or application specific integrated circuits.

[0138] about Figure 5A The wrist wearable device 500 is an example of a coupled wearable band 510 and a watch body 520, and therefore, the wrist wearable device 500 will be understood to include the components shown and described for the computing system 530 of the wearable band and the computing system 560 of the watch body. In some embodiments, the wrist wearable device 500 has a split structure (e.g., a split mechanical structure, or a split electrical structure) between the watch body 520 and the wearable band 510. In other words, all the components shown in the computing system 530 of the wearable band and the computing system 560 of the watch body can be accommodated or otherwise provided in the combined wrist wearable device 500 (e.g., a watch), or in various components of the watch body 520, the wearable band 510, and / or a portion of the wearable band (e.g., the coupling mechanism 516 of the wearable band 510).

[0139] The above technology can be used with any device for sensing neuromuscular signals (including FIG. 5A to FIG. 5B The invention is intended for use with an arm wearable device, but may also be used with other types of wearable devices for sensing neuromuscular signals (e.g., a body wearable device or a head wearable device that may have neuromuscular sensors closer to the brain or spine).

[0140] In some embodiments, the wrist wearable device 500 can be used in conjunction with head wearable devices (e.g., XR device 600 and MR device 610) and / or HIPD 700 described below, and the wrist wearable device 500 can also be configured to allow the user to control aspects of the artificial reality (e.g., by using EMG-based gestures to control user interface objects in the artificial reality and / or by allowing the user to interact with a touch screen on the wrist wearable device to control aspects of the artificial reality). Having thus described exemplary wrist wearable devices, attention is now turned to exemplary head wearable devices, such as XR device 600 and VR device 610.

[0141] Exemplary head wearable device

[0142] Fig. 6A , Figure 6B-1 , Figure 6B-2 and Figure 6C 6 shows an exemplary head wearable device according to some embodiments. The head wearable device may include, but is not limited to, an XR device 600 (e.g., an XR or smart eye-wearing device, such as smart glasses, smart monocles, smart contact lenses, etc.), an MR device 610 (e.g., a VR head-mounted viewer or a head-mounted display (HMD), etc.), or other eye-coupling devices. The XR device 600 and the MR device 610 are referenced herein. Figures 1 to 3B The head wearable device 110 is described as an example, so that the head wearable device should be understood to have features of the XR device 600 and / or the MR device 610, and vice versa. The XR device 600 and the MR device 610 can perform various functions and / or operations associated with browsing through the user interface and selectively opening applications and performing the above-referenced Figures 1 to 3B Describes the functionality and / or operation.

[0143] In some embodiments, an XR system (e.g., Figure 4A to Figure 4C-2 ; XR system 400a to 400c) includes an XR device 600 (such as Fig. 6A ) and / or MR device 610 (as shown Figure 6B-1 to Figure 6B-2 In some embodiments, the XR device 600 and the MR device 610 may include one or more analog components (e.g., components for presenting an interactive AR environment, such as a processor, a memory, and / or a presentation device including one or more displays and / or one or more waveguides), some of which will be referred to as Figure 6C The head wearable device may use a display projector (eg, display projector components 607A and 607B) and / or a waveguide to project data representations to a user. Some embodiments of the head wearable device do not include a display.

[0144] Fig. 6A An exemplary visual depiction of an XR device 600 (e.g., which may also be described herein as augmented reality glasses and / or smart glasses) is shown. The XR device 600 may be used with Fig. 6A600) work with additional electronic components not shown in the figure (e.g., wearable accessory devices and / or intermediate processing devices in electronic communication with or otherwise configured for use with XR device 600). In some embodiments, the wearable accessory device and / or intermediate processing device may be configured to couple with XR device 600 via a coupling mechanism in electronic communication with coupling sensor 624, where coupling sensor 624 can detect when the electronic device becomes physically or electronically coupled with XR device 600. In some embodiments, XR device 600 may be configured to couple with a housing (e.g., a portion of frame 604 or temple arm 605), which may include one or more additional coupling mechanisms configured to couple with additional accessory devices. Fig. 6A The components shown in may be implemented in hardware, software, firmware, or a combination thereof, including one or more signal processing components and / or application specific integrated circuits (ASICs).

[0145] The XR device 600 includes mechanical eyeglass components including a frame 604 configured to hold one or more lenses (e.g., one or two lenses 606-1 and 606-2). It will be appreciated by one of ordinary skill in the art that the XR device 600 may include additional mechanical components, such as a hinge configured to allow portions of the frame 604 of the XR device 600 to fold and unfold, a beam configured to span the gap between the lenses 606-1 and 606-2 and rest on the user's nose, a nose pad configured to rest on the bridge of the nose and provide support for the XR device 600, a temple cap configured to rest on the user's ear and provide additional support for the XR device 600, a temple arm 605 configured to extend from the hinge to the temple cap of the XR device 600, and the like. It will be further appreciated by one of ordinary skill in the art that some examples of the XR device 600 may not include any of the mechanical components described herein. For example, a smart contact lens configured to present XR to a user may not include any components of XR device 600.

[0146] Lenses 606-1 and 606-2 may be separate displays or display devices (e.g., waveguides for projected representations). Lenses 606-1 and 606-2 may act together or independently to present an image or a series of images to a user. In some embodiments, lenses 606-1 and 606-2 may operate in conjunction with one or more display projector assemblies 607A and 607B to present image data to a user. Although XR device 600 includes two displays, embodiments of the present disclosure may be implemented in an XR device having a single near-eye display (NED) or more than two NEDs.

[0147] XR device 600 includes electronic components, many of which are described below with respect to FIG. Figure 6C Describe in more detail. Fig. 6A 6, including sensors 623-1, 623-2, 623-3, 623-4, 623-5, and 623-6 that may be distributed along a majority of the frame 604 of the XR device 600. Figure 6C Different types of sensors are described. The XR device 600 also includes a left camera 639A and a right camera 639B located on different sides of the frame 604. And the eye-mounted device includes one or more processors 648A and 648B (e.g., an integrated microprocessor such as an ASIC) embedded in a portion of the frame 604.

[0148] Figure 6B-1 and Figure 6B-2 An exemplary visual depiction of an MR device 610 (e.g., a head-mounted display (HMD) 612, also referred to herein as an XR head-mounted viewer, an AR head-mounted viewer, a head wearable device, or an MR head-mounted viewer) is shown. The HMD 612 includes a front body 614 and a frame 616 (e.g., a band or strap) shaped to fit around the user's head. In some embodiments, the front body 614 and / or the frame 616 include one or more electronic components for facilitating presentation of and / or interacting with an XR and / or MR system (e.g., a display, a processor (e.g., processor 648A-1), an IMU, a tracking emitter or detector, or a sensor). In some embodiments, as Figure 6B-2 As shown, HMD 612 includes an output audio converter (e.g., output audio converter 618). In some embodiments, as Figure 6B-2 As shown, for example, one or more output audio transducers 618 and one or more components of the frame 616 (e.g., a portion or all of the frame 616 and / or the output audio transducer 618) can be configured to be attached and detached (e.g., detachably attached) from the HMD 612. In some embodiments, coupling the detachable component to the HMD 612 enables the detachable component to be in electronic communication with the HMD 612. The MR device 610 includes electronic components, many of which will be described below with respect to Figure 6C Describe in more detail.

[0149] Figure 6B-1 to Figure 6B-2The MR device 610 is also shown to have one or more cameras, such as a left camera 639A and a right camera 639B that can be similar to the left camera and the right camera on the frame 604 of the XR device 600. In some embodiments, the MR device 610 includes one or more additional cameras (e.g., cameras 639C and 639D), which can be configured to enhance the image data obtained by the cameras 639A and 639B by providing more information. For example, camera 639C can be used to provide color information that cannot be recognized by cameras 639A and 639B. In some embodiments, one or more of the cameras 639A to 639D can include an optional infrared (IR) cut filter that is configured to prevent IR light from being received at the corresponding camera sensor.

[0150] The MR device 610 may include a housing 690 that stores one or more components of the MR device 610 and / or additional components of the MR device 610. The housing 690 may be a modular electronic device configured to couple with the MR device 610 (or XR device 600) and to supplement and / or expand the capabilities of the MR device 610 (or XR device 600). For example, the housing 690 may include additional sensors, cameras, power supplies, and processors (e.g., processor 648A-2) that improve and / or increase the functionality of the MR device 610. Figure 6C Examples of different components included in housing 690 are described.

[0151] Alternatively or additionally, in some embodiments, the head wearable device such as the MR device 610 and / or the XR device 600 includes or is communicatively coupled to another external device (e.g., a paired device), such as the HIPD 700 (hereinafter referred to as the HIPD 700). FIG. 7A to FIG. 7B Discussion) and / or an optional neckband. The optional neckband can be coupled to the head wearable device via one or more connectors (e.g., a wired connector or a wireless connector). The head wearable device and the neckband can operate independently without any wired connection or wireless connection between them. In some embodiments, components of the head wearable device and components of the neckband can be located on one or more additional peripheral devices, a neckband, or some combination thereof that are paired with the head wearable device. In addition, the neckband is intended to represent any suitable type or form of paired device. Therefore, the following discussion of the neckband can also be applied to various other paired devices, such as smart watches, smart phones, wristbands, other wearable devices, handheld controllers, tablet computers, or laptop computers.

[0152] In some cases, pairing an external device such as an intermediate processing device (e.g., HIPD 700, an optional neckband and / or a wearable accessory device) with a head wearable device (e.g., XR device 600 and / or MR device 610) enables the head wearable device to achieve a form factor similar to a pair of glasses while still providing sufficient battery power and computing power to achieve expanded capabilities. Some or all of the battery power, computing resources, and / or additional features of the head wearable device can be provided by the paired device, or shared between the paired device and the head wearable device, thereby reducing the weight, thermal distribution, and form factor of the head wearable device as a whole, while still allowing the head wearable device to retain its desired functionality. For example, the intermediate processing device (e.g., HIPD 700) can allow components that would otherwise be included in the head wearable device to be included in the intermediate processing device (and / or wearable device or accessory device), thereby shifting the weight load from the user's head and neck to one or more other parts of the user's body. In some embodiments, the intermediate processing device has a large surface area over which to diffuse and disperse heat to the surrounding environment. Thus, the intermediate processing device may allow for greater battery power and computing power than a standalone head wearable device. Because the weight carried in the intermediate processing device is less intrusive to the user than the weight carried in the head wearable device, the user may tolerate wearing a lighter eye-mounted device and carrying or wearing a paired device for longer periods of time than the user would tolerate wearing a heavier eye-mounted device alone, thereby enabling the user to more fully integrate the XR environment into their daily activities.

[0153] In some embodiments, the intermediate processing device is communicatively coupled to the head wearable device and / or other devices. These other devices can provide certain functions (e.g., tracking, positioning, depth map construction, processing and / or storage, etc.) for the head wearable device. In some embodiments, the intermediate processing device includes a controller and a power supply. In some embodiments, the sensors of the intermediate processing device are configured to sense additional data that can be shared with the head wearable device in an electronic format (analog or digital).

[0154] The controller of the intermediate processing device processes information generated by the intermediate processing device and / or sensors on the head wearable device. For example, the intermediate processing device of HIPD 700 can process information generated by one or more of its sensors and / or information provided by other communication coupling devices. For example, the head wearable device may include an IMU, and the intermediate processing device (neckband and / or HIPD 700) can calculate all inertial operations and spatial operations from the IMU located on the head wearable device. Fig. 7A and Figure 7BAdditional examples of processing performed by a communicatively coupled device, such as HIPD 700, are provided.

[0155] XR systems may include various types of visual feedback mechanisms. For example, the display device in the XR device 600 and / or the display device in the MR device 610 may include one or more liquid crystal displays (LCD), light emitting diode (LED) displays, organic LED (OLED) displays, and / or any other suitable type of display screen. The XR system may include a single display screen for both eyes, or a display screen may be provided for each eye, which may provide additional flexibility for zoom adjustment or correction of refractive errors associated with user vision. Some XR systems also include an optical subsystem having one or more lenses (e.g., conventional concave or convex lenses, Fresnel lenses, or adjustable liquid lenses) through which the user can view the display screen. In addition to or instead of using a display screen, some XR systems include one or more projection systems. For example, the display device in the XR device 600 and / or the display device in the MR device 610 may include a micro-LED projector (e.g., using a waveguide) that projects light into the display device, such as a transparent combiner lens that allows ambient light to pass through. The display device may refract the projected light toward the user's pupil, and may enable the user to view both the XR content and the real world simultaneously. The XR system may also be configured with any other suitable type or form of image projection system. As described above, some XR systems may substantially replace one or more sensory perceptions of the user's real world with a virtual experience, rather than combining XR with actual reality.

[0156] Although the exemplary head-wearable devices are described herein as an XR device 600 and an MR device 610, respectively, either or both of the exemplary head-wearable devices described herein may be configured to present a fully immersive MR scene presented in substantially all of the user's field of view, in addition to or as an alternative to a more subtle augmented reality scene presented in a portion (less than all) of the user's field of view.

[0157] In some embodiments, the XR device 600 and / or the MR device 610 may include a tactile feedback system. The tactile feedback system can provide various types of skin feedback, including vibration, force, traction, shear, texture and / or temperature. The tactile feedback system can also provide various types of kinesthetic feedback, such as motion and compliance. Tactile feedback can be implemented using motors, piezoelectric actuators, fluid systems and / or various other types of feedback mechanisms. The tactile feedback system can be implemented independently of other XR devices, implemented in other XR devices, and / or in combination with other XR devices (e.g., wrist wearable devices that can be incorporated into headwear, gloves, tights, handheld controllers, environmental devices (e.g., chairs or foot pads), and / or any other type of device or system (e.g., wrist wearable device 500, HIPD 700, clothing based on smart textiles)) and / or other devices described herein.

[0158] Figure 6C A computing system 620 and an optional housing 690 are shown, each of which illustrates components that may be included in a head wearable device (e.g., XR device 600 and / or MR device 610). In some embodiments, more or fewer components may be included in the optional housing 690, depending on the practical constraints of the respective head wearable device being described. Additionally or alternatively, the optional housing 690 may include additional components that expand and / or enhance the functionality of the head wearable device.

[0159] In some embodiments, computing system 620 and / or optional housing 690 may include one or more peripheral device interfaces 622A and 622B, one or more power systems 642A and 642B (including charging input 643, PMIC 644, and battery 645), one or more controllers 646A and 646B (including one or more haptic controllers 647), one or more processors 648A and 648B (as defined above, including any of those examples provided), and memory 650A and 650B, all of which may be in electronic communication with each other. For example, one or more processors 648A and / or 648B may be configured to execute instructions stored in memory 650A and / or 650B, which instructions may cause a controller in one or more controllers 646A and / or 646B to cause operations to be performed at one or more peripheral devices of peripheral device interfaces 622A and / or 622B. In some embodiments, each of the operations described may occur based on power provided by power systems 642A and / or 642B.

[0160] In some embodiments, peripheral device interface 622A may include one or more devices configured as part of computing system 620, many of which have been described above with respect to Figure 5A and Figure 5B The wrist wearable device shown is defined and / or described. For example, the peripheral device interface can include one or more sensors 623A. Some exemplary sensors include: one or more coupling sensors 624, one or more acoustic sensors 625, one or more imaging sensors 626, one or more EMG sensors 627, one or more capacitive sensors 628, and / or one or more IMUs 629. In some embodiments, the sensor 623A also includes a depth sensor 667, a light sensor 668, and / or any other type of sensor defined above or described with respect to any other embodiment discussed herein.

[0161] In some embodiments, the peripheral device interface may include one or more additional peripheral devices, including one or more NFC devices 630, one or more GPS devices 631, one or more LTE devices 632, one or more Wi-Fi and / or Bluetooth (WiFi / BT) devices 633, one or more buttons 634 (e.g., including slidable or otherwise adjustable buttons), one or more displays 635A, one or more speakers 636A, one or more microphones 637A, one or more cameras 638A (e.g., including a first camera 639-1 to an nth camera 639-n similar to a left camera 639A and / or a right camera 639B), one or more tactile devices 640, and / or any other type of peripheral device defined above or described with respect to any other embodiments discussed herein.

[0162] The head wearable device may include various types of visual feedback mechanisms (e.g., presentation devices). For example, the display device in the XR device 600 and / or the display device in the MR device 610 may include one or more liquid crystal displays (LCDs), light emitting diode (LED) displays, organic LED (OLED) displays, micro-LEDs, and / or any other suitable type of display screen. The head wearable device may include a single display screen (e.g., configured to be viewed by both eyes) and / or may provide a separate display screen for each eye, which may provide additional flexibility for zoom adjustment or correction of refractive errors associated with user vision. Some embodiments of the head wearable device also include an optical subsystem having one or more lenses (e.g., conventional concave or convex lenses, Fresnel lenses, or adjustable liquid lenses) through which the user can view the display screen. For example, each display 635A may be coupled to each of the lenses 606-1 and 606-2 of the XR device 600. The displays 635A coupled to each of the lenses 606-1 and 606-2 may act together or independently to present an image or a series of images to the user. In some embodiments, the XR device 600 and / or the MR device 610 includes a single display 635A (eg, a near-eye display) or more than two displays.

[0163] In some embodiments, a first group of one or more displays 635A may be used to present an MR environment, and a second group of one or more display devices 635A may be used to present a virtual reality environment. In some embodiments, one or more waveguides are used in conjunction with presenting XR content to a user of an XR device 600 and / or an MR device 610 (e.g., as a means of delivering light from a display projector assembly and / or one or more displays 635A to the user's eyes). In some embodiments, one or more waveguides are fully or partially integrated into the XR device 600 and / or the MR device 610. In addition to or instead of using a display screen, some XR systems may include one or more projection systems. For example, a display device in an XR device 600 and / or a display device in an MR device 610 may include (e.g., using a waveguide) a micro-LED projector that projects light into a display device, such as a transparent combiner lens that allows ambient light to pass through. The display device may refract the projected light toward the user's pupil, and may enable the user to simultaneously view both the XR content and the real world. The head wearable device may also be configured with any other suitable type or form of image projection system. In some embodiments, additionally or alternatively, one or more waveguides are provided for one or more displays 635A.

[0164] In some embodiments of the head wearable device, ambient light and / or a real-world real-time view (e.g., a real-time feed of the surrounding environment that a user would normally see) can pass through display elements of the corresponding head wearable device that presents aspects of the XR system. In some embodiments, ambient light and / or the real-world real-time view can pass through a portion (not all) of the XR environment presented within the user's field of view (e.g., a portion of the XR environment that is co-located with physical objects in the user's real-world environment that are within a specified boundary (e.g., a guardian boundary) configured to be used by the user when interacting with the XR environment). For example, a visual user interface element (e.g., a notification user interface element) can be presented at the head wearable device, and a certain amount of ambient light and / or real-world real-time view (e.g., 15% to 50% of the ambient light and / or real-world real-time view) can pass through the user interface element so that the user can distinguish at least a portion of the physical environment on which the user interface element is displayed.

[0165] The head wearable device may include one or more external displays 635A for presenting information to the user. For example, the external display 635A may be used to display the current battery level, network activity (e.g., connected, disconnected), current activity (e.g., playing games, talking, meeting, or watching movies), and / or other relevant information. In some embodiments, the external display 635A may be used to communicate with other elements. For example, a user of the head wearable device may cause the external display 635A to present a do not disturb notification. The user may also use the external display 635A to share any information collected by one or more components of the peripheral device interface and / or generated by the head wearable device (e.g., during operation and / or execution of one or more applications).

[0166] The memory 650A may include instructions and / or data that may be executed by one or more processors 648A (and / or processor 648B of housing 690) and / or a memory controller of one or more controllers 646A (and / or controller 646B of housing 690). The memory 650A may include one or more operating systems 651, one or more applications 652, one or more communication interface modules 653A, one or more graphics modules 654A, one or more XR processing modules 655A, one or more eye relief adjustment modules 656A-656B for adjusting eye relief depth and indicating the eye relief depth to the wearer, and / or any other type of module or component defined above or described with respect to any other embodiment discussed herein.

[0167] The data 660 stored in the memory 650A may be used in conjunction with one or more of the applications and / or programs discussed above. The data 660 may include profile data 661, sensor data 662, media content data 663, XR application data 664, eye relief data 665 for adjusting eye relief depth and indicating the eye relief depth to the wearer, and / or any other type of data defined above or described with respect to any other embodiment discussed herein.

[0168] In some embodiments, the controller 646A of the head wearable device processes information generated by the sensor 623A on the head wearable device and / or another component of the head wearable device and / or another component communicatively coupled to the head wearable device (e.g., a component of the housing 690, such as a component of the peripheral device interface 622B). For example, the controller 646A can process information from the acoustic sensor 625 and / or the imaging sensor 626. For each detected sound, the controller 646A can perform a Direction-Of-Arrival (DOA) estimate to estimate the direction from which the detected sound arrived at the head wearable device. When one or more acoustic sensors 625 detect a sound, the controller 646A can populate an audio data set with information (e.g., represented by sensor data 662).

[0169] In some embodiments, a physical electronic connector can transmit information between a head wearable device and another electronic device, and / or between one or more processors 648A and a controller 646A of a head wearable device. This information can be in the form of optical data, electrical data, wireless data, or any other transmittable data form. Moving the processing of information generated by the head wearable device to an intermediate processing device can reduce weight and heat in the eye-mounted device, making the eye-mounted device more comfortable and safer for the user. In some embodiments, an optional accessory device (e.g., an electronic neckband or HIPD 700) is coupled to the head wearable device via one or more connectors. The connector can be wired or wireless, and can include electronic components and / or non-electronic (e.g., structural) components. In some embodiments, the head wearable device and the accessory device can operate independently, without any wired or wireless connection between them.

[0170] The head wearable device may include various types of computer vision components and subsystems. For example, the XR device 600 and / or the MR device 610 may include one or more optical sensors, such as a two-dimensional (2D) camera or a three-dimensional (3D) camera, a time-of-flight depth sensor, a single-beam or scanning laser rangefinder, a 3D laser radar (LiDAR) sensor, and / or any other suitable type or form of optical sensor. The head wearable device may process data from one or more of these sensors to identify the user's location and / or aspects of the user's real-world physical environment, including the location of real-world objects in the real-world physical environment. In some embodiments, the methods described herein are used to map the real world, provide context to the user about the real-world environment, and / or generate interactive virtual objects (which may be replicas or digital twins of real-world objects that can be interacted with in the XR environment), as well as various other functions. For example, Figure 6B-1 and Figure 6B-2 An MR device 610 is shown having cameras 639A to 639D that can be used to provide depth information for creating a voxel field and a 2D mesh to provide object information to a user for collision avoidance.

[0171] The optional housing 690 may include components similar to those described above with respect to the computing system 620. For example, the optional housing 690 may include a corresponding peripheral device interface 622B, which includes more or fewer components than those described above with respect to the peripheral device interface 622A. As described above, the components of the optional housing 690 may be used to enhance and / or expand the functionality of the head wearable device. For example, the optional housing 690 may include corresponding sensors 623B, speakers 636B, displays 635B, microphones 637B, cameras 638B, and / or other components for collecting and / or presenting data. Similarly, the optional housing 690 may include one or more processors 648B, controllers 646B, and / or memory 650B (including corresponding communication interface modules 653B, one or more graphics modules 654B, one or more XR processing modules 655B), which may be used alone and / or in combination with components of the computing system 620.

[0172] The above FIG. 6A to FIG. 6C The techniques described in the can be used with different head wearable devices. In some embodiments, the head wearable device (e.g., XR device 600 and / or MR device 610) can be used in conjunction with, for example, a wrist wearable device 500 (or a component of the wrist wearable device). Having thus described an example of a head wearable device, attention is now turned to an exemplary handheld intermediate processing device such as HIPD 700.

[0173] Exemplary Handheld Intermediate Processing Device

[0174] Fig. 7A and Figure 7B An exemplary handheld intermediate processing device (HIPD) 700 is shown in accordance with some embodiments. The HIPD 700 may perform various functions and / or operations associated with navigating through a user interface and selectively opening applications, etc., as well as performing the above-referenced Figure 4A to Figure 4C-2 Describes the functionality and / or operation.

[0175] Fig. 7A A top view 705 and a side view 725 of the HIPD 700 are shown. The HIPD 700 is configured to communicatively couple to one or more wearable devices (or other electronic devices) associated with a user. For example, the HIPD 700 is configured to communicatively couple to the user's wrist wearable device 500 (or components thereof, such as the watch body 520 and the wearable band 510), the XR device 600, and / or the MR device 610. The HIPD 700 can be configured to be held by the user (e.g., as a handheld controller), carried on the user's person (e.g., in their pocket, or in their bag), placed near the user (e.g., on their desk when sitting at their desk, or on a charging base), and / or placed at or within a predetermined distance from the wearable device or other electronic device (e.g., in some embodiments, the predetermined distance is the maximum distance at which the HIPD 700 can successfully communicatively couple to an electronic device such as a wearable device (e.g., 10 meters)).

[0176] HIPD 700 can perform various functions independently and / or in combination with one or more wearable devices (e.g., wrist wearable device 500, XR device 600, and / or MR device 610). HIPD 700 is configured to increase and / or improve the functionality of a communication coupling device such as a wearable device. HIPD 700 is configured to perform one or more functions or operations associated with: interacting with a user interface and application of a communication coupling device, interacting with an XR environment, interacting with an MR environment, and / or operating as a human-machine interface controller; and various functions and / or operations. In addition, as will be described in more detail below, the functions and / or operations of HIPD 700 may include, but are not limited to: task offloading and / or handover; hot offloading and / or handover; 6 degrees of freedom (6DoF) ray casting and / or gaming (e.g., using imaging devices or cameras 714A and 714B, which can be used for simultaneous localization and mapping (SLAM) and / or used with other image processing techniques); portable charging; messaging; image acquisition via one or more imaging devices or cameras (e.g., cameras 722A and 722B); sensing user input (e.g., sensing touch on multi-touch input surface 702); wireless communication and / or interconnection (e.g., cellular, near field, Wi-Fi, or personal area network); location determination; financial transactions; providing tactile feedback; alarms; notifications; biometric authentication; health monitoring; sleep monitoring. The above exemplary functions can be performed independently in HIPD 700 and / or in communication between HIPD 700 and another wearable device described herein. In some embodiments, functions may be performed in conjunction with an XR environment on the HIPD 700. As will be appreciated by those skilled in the art upon reading the description provided herein, the novel HIPD 700 described herein may be used with any type of suitable XR environment.

[0177] When the HIPD 700 is communicatively coupled with a wearable device and / or other electronic device, the HIPD 700 is configured to perform one or more operations initiated at the wearable device and / or other electronic device. In particular, one or more operations of the wearable device and / or other electronic device can be offloaded to the HIPD 700 for execution. The HIPD 700 performs one or more operations of the wearable device and / or other electronic device, and provides data corresponding to the completed operations to the wearable device and / or other electronic device. For example, a user can initiate a video stream using an XR device 600, and can offload back-end tasks (e.g., video rendering) associated with executing the video stream to the HIPD 700, which performs the back-end tasks and provides the corresponding data to the XR device 600 to perform the remaining front-end tasks associated with the video stream (e.g., presenting rendered video data via a display of the XR device 600). In this way, a HIPD 700 with more computing resources and greater thermal headroom than a wearable device can perform computationally intensive tasks for the wearable device, thereby improving the performance of the operations performed by the wearable device.

[0178] HIPD 700 includes a multi-touch input surface 702 located on a first side (e.g., a front surface), which is configured to detect one or more user inputs. In particular, the multi-touch input surface 702 can detect single-click input, multi-click input, sliding gestures and / or input, force-based and / or pressure-based touch input, maintained clicks, etc. The multi-touch input surface 702 is configured to detect capacitive touch input and / or force (and / or pressure) touch input. The multi-touch input surface 702 includes a first touch input surface 704 defined by a surface recess and a second touch input surface 706 defined by a substantially flat portion. The first touch input surface 704 may be arranged adjacent to the second touch input surface 706. In some embodiments, the first touch input surface 704 and the second touch input surface 706 may have different sizes, shapes, and / or cover different parts of the multi-touch input surface 702. For example, the first touch input surface 704 may be substantially circular, and the second touch input surface 706 may be substantially rectangular. In some embodiments, the surface recess of the multi-touch input surface 702 is configured to guide the user to handle the HIPD 700. In particular, the surface recess is configured so that the user holds the HIPD 700 vertically when holding the HIPD 700 in one hand (e.g., so that the imaging device or camera 714A and 714B being used is pointed at the ceiling or the sky). In addition, the surface recess is configured so that the user's thumb is located within the first touch input surface 704.

[0179] In some embodiments, different touch input surfaces include multiple touch input areas. For example, the second touch input surface 706 includes at least a first touch input area 708 located within the second touch input area 706 and a third touch input area 710 located within the first touch input area 708. In some embodiments, one or more touch input areas in these touch input areas are optional and / or defined by the user (for example, the user can specify the touch input area based on their preferences). In some embodiments, each touch input surface and / or touch input area is associated with a predetermined command set. For example, the user input detected in the first touch input area 708 causes the HIPD 700 to execute a first command, while the user input detected in the second touch input area 706 causes the HIPD 700 to execute a second command different from the first command. In some embodiments, different touch input surfaces and / or touch input areas are configured to detect one or more types of user input. Different touch input surfaces and / or touch input areas can be configured to detect the same or different types of user input. For example, the first touch input region 708 may be configured to detect force touch input (eg, magnitude of a user's press) and capacitive touch input, and the second touch input region 706 may be configured to detect capacitive touch input.

[0180] HIPD 700 includes one or more sensors 751 for sensing data used in performing one or more operations and / or functions. For example, HIPD 700 may include an IMU that is used in conjunction with cameras 714A, 714B for three-dimensional object manipulation (e.g., enlarging an object, moving an object, destroying an object, etc.) in an AR or MR environment. In non-limiting examples of sensors 751, HIPD 700 is a light sensor, a magnetometer, a depth sensor, a pressure sensor, and a force sensor. Figure 7B Additional examples of sensor 751 are provided.

[0181] HIPD 700 may include one or more light indicators 712 that provide one or more notifications to the user. In some embodiments, the light indicator is an LED or other type of lighting device. The light indicator 712 can be used as a privacy light to notify the user and / or other people near the user that the imaging device and / or microphone are active. In some embodiments, the light indicator is located near one or more touch input surfaces. For example, a light indicator can be placed around the first touch input surface 704. The light indicator can emit light in different colors and / or patterns to provide the user with one or more notifications and / or information about the device. For example, the light indicator located around the first touch input surface 704 can flash when the user receives a notification (e.g., a message), turn red when the HIPD 700 is out of power, operate as a progress bar (e.g., a light ring that turns off when a task is completed (e.g., 0% to 100%)), operate as a volume indicator, and the like.

[0182] In some embodiments, HIPD 700 includes one or more additional sensors located on another surface. Fig. 7A As shown, the HIPD 700 includes one or more sensors (e.g., sensor group 720) located on the edge of the HIPD 700. When the sensor group 720 is located on the edge of the HIPD 700, the sensor group 720 can be positioned at a predetermined tilt angle (e.g., 26 degrees), which allows the sensor group 720 to be tilted toward the user when placed on a table or other flat surface. Alternatively, in some embodiments, the sensor group 720 is located on the surface opposite to the multi-touch input surface 702 (e.g., the back). One or more sensors in the sensor group 720 will be discussed in detail below.

[0183] The side view 725 of HIPD 700 shows sensor group 720 and camera 714B. Sensor group 720 includes one or more cameras 722A and 722B, depth projector 724, ambient light sensor 728 and depth receiver 730. In some embodiments, sensor group 720 includes light indicator 726. Light indicator 726 can be used as a private indicator to let users and / or people around them know that the camera and / or microphone are active. Sensor group 720 is configured to capture the user's facial expressions so that the user can puppet a customized avatar (e.g., displaying emotions such as smiles and laughter on the avatar or the user's digital image). Sensor group 720 can be configured as a side stereo RGB system, a rear indirect time of flight (indirect Time-of-Flight, iToF) system or a rear stereo RGB system. As those skilled in the art will understand when reading the description provided herein, the novel HIPD 700 described herein can use different sensor group 720 structures and / or sensor group 720 placements.

[0184] In some embodiments, the HIPD 700 includes one or more haptic devices 771 ( Figure 7B ; e.g., a vibrotactile actuator). Sensor 751 and / or haptic device 771 may be configured to operate in conjunction with a plurality of applications and / or communicatively coupled devices, including but not limited to wearable devices, health monitoring applications, social media applications, gaming applications, and artificial reality applications (e.g., applications related to artificial reality).

[0185] HIPD 700 is configured to operate without a display. However, in an alternative embodiment, HIPD 700 may include a display 768 ( Figure 7B ). HIPD 700 may also include one or more optional peripheral buttons 767 ( Figure 7B ). For example, the peripheral button 767 can be used to turn the HIPD 700 on or off. In addition, the housing of the HIPD 700 can be formed of a polymer and / or an elastomer. The HIPD 700 can be configured to have a non-slip surface that allows the HIPD 700 to be placed on a surface without the user having to look after the HIPD 700. In other words, the HIPD 700 is designed so that the HIPD does not easily slip off the surface. In some embodiments, the HIPD 700 includes one or more magnets that couple the HIPD 700 to another surface. This allows the user to mount the HIPD 700 to different surfaces and provides the user with greater flexibility when using the HIPD 700.

[0186] As described above, the HIPD 700 may distribute and / or provide instructions for performing one or more tasks at the HIPD 700 and / or the communication coupling device. For example, the HIPD 700 may identify one or more back-end tasks to be performed by the HIPD 700 and one or more front-end tasks to be performed by the communication coupling device. Although the HIPD 700 is configured to offload and / or hand over tasks to the communication coupling device, the HIPD 700 may (e.g., via one or more processors, such as a central processing unit (CPU) 777; Figure 7B ) performs back-end tasks and front-end tasks. HIPD 700 can be used, but is not limited to, to perform enhanced calls (e.g., receiving and / or sending 3D or 2.5D real-time volumetric calls, real-time digital human representation calls, and / or avatar calls), discreet messaging, 6DoF portrait / landscape games, AR / MR object manipulation, AR / MR content display (e.g., presenting content via a virtual display), and / or other AR / MR interactions. HIPD 700 can perform the above operations alone or in combination with a wearable device (or other communicatively coupled electronic device).

[0187] Figure 7B A block diagram of a computing system (also referred to as a computer system) 740 of a HIPD 700 according to some embodiments is shown. The HIPD 700 described in detail above may include one or more components shown in the computing system 740 of the HIPD. The HIPD 700 will be understood to include the components of the computing system 740 for the HIPD shown and described below. In some embodiments, all or most of the components of the computing system 740 of the HIPD are included in a single integrated circuit. Alternatively, in some embodiments, the components of the computing system 740 of the HIPD are included in multiple integrated circuits that are communicatively coupled.

[0188] The computing system 740 of the HIPD may include a processor (e.g., a CPU 777, a GPU, and / or a CPU with integrated graphics), a controller 775, a peripheral device interface 750 including one or more sensors 751 and other peripheral devices, a power source (e.g., a power system 795), and a memory (e.g., a memory 778), which includes an operating system (e.g., an operating system 779), data (e.g., data 788), one or more applications (e.g., applications 780), and one or more modules (e.g., a communication interface module 781, a graphics module 782, a task and processing management module 783, an interoperability module 784, an XR processing module 785, a data management module 786, etc.). The computing system 740 of the HIPD also includes a power system 795, which includes a charging input / output 796, a PMIC 797, and a battery 798, all of which are defined above.

[0189] In some embodiments, the peripheral device interface 750 may include one or more sensors 751. The sensor 751 may include the same Figure 5B For example, sensors 751 may include imaging sensors 754, (optional) EMG sensors 756, IMUs 758, and capacitive sensors 760. In some embodiments, sensors 751 may include one or more pressure sensors 752 for sensing pressure data, an altimeter 753 for sensing the height of HIPD 700, a magnetometer 755 for sensing magnetic fields, a depth sensor 757 (or a time-of-flight sensor) for determining the difference between a camera and an image object, a position sensor 759 (e.g., a flexible position sensor) for sensing a relative displacement or change in position of a portion of HIPD 700, a force sensor 761 for sensing a force applied to a portion of HIPD 700, and a light sensor 762 for detecting the amount of illumination (e.g., an ambient light sensor). Sensors 751 may include Figure 7B One or more sensors not shown.

[0190] Reference to above Figure 5B Similar to the peripheral devices described above, the peripheral device interface 750 may also include an NFC component 763, a GPS component 764, an LTE component 765, a Wi-Fi and / or Bluetooth communication (WiFi / BT) component 766, a speaker 769, a tactile device 771, and a microphone 773. Fig. 7A As described above, HIPD 700 may optionally include a display 768 and / or one or more buttons 767. Peripheral device interface 750 may also include one or more cameras 770, a touch surface 772, and / or one or more light emitters 774. Fig. 7AThe multi-touch input surface 702 described is an example of a touch surface 772. The light emitter 774 may be one or more LEDs, lasers, etc., and the light emitter 774 may be used to project or present information to a user. For example, the light emitter 774 may include the light emitter 774 described above. Fig. 7A The light indicators 712 and 726 described above. The camera 770 (e.g., see Fig. 7A The cameras 714A, 714B and 722A, 722B described in the figure may include one or more wide-angle cameras, fisheye cameras, spherical cameras, compound eye cameras (e.g., stereo cameras and multi-cameras), depth cameras, RGB cameras, ToF cameras, RGB-D cameras (depth cameras and ToF cameras) and / or other available cameras. Camera 770 can be used for SLAM; 6DoF ray casting, gaming, object manipulation and / or other rendering; facial recognition and facial expression recognition, etc.

[0191] Similar to the above reference Figure 5B 1. With reference to the depicted computing system 560 of the body and computing system 530 of the wearable band, the computing system 740 of the HIPD may include one or more haptic controllers 776 and associated components (eg, haptic devices 771) for providing haptic events at the HIPD 700.

[0192] The memory 778 may include high-speed random access memory and / or non-volatile memory, such as one or more disk storage devices, flash memory devices or other non-volatile solid-state storage devices. The access of other components of the HIPD 700 (e.g., one or more processors and the peripheral device interface 750) to the memory 778 may be controlled by the memory controller of the controller 775.

[0193] In some embodiments, the software components stored in the memory 778 include one or more operating systems 779, one or more application programs 780, one or more communication interface modules 781, one or more graphics modules 782, and one or more data management modules 786, which are similar to those described above with reference to FIG. Figure 5B Describes the software component.

[0194] In some embodiments, the software components stored in memory 778 include a task and process management module 783 for identifying one or more front-end and back-end tasks associated with an operation performed by a user, executing one or more front-end and / or back-end tasks, and / or providing instructions to one or more communication-coupled devices that cause the execution of one or more front-end and / or back-end tasks. In some embodiments, task and process management module 783 uses data 788 (e.g., device data 790) to distribute one or more front-end and / or back-end tasks based on the computing resources, available power, thermal headroom, ongoing operations, and / or other factors of the communication-coupled devices. For example, task and process management module 783 may cause execution of one or more back-end tasks (operations performed at the communication-coupled XR device 600) at HIPD 700 based on determining that the operation is utilizing a predetermined amount (e.g., at least 70%) of the computing resources available at XR device 600.

[0195] In some embodiments, the software components stored in the memory 778 include an interoperability module 784 for exchanging and utilizing information received and / or provided to different communicatively coupled devices. The interoperability module 784 allows different systems, devices, and / or applications to connect and communicate in a coordinated manner without user input. In some embodiments, the software components stored in the memory 778 include an XR processing module 785 that is configured to process signals based at least on sensor data used in an AR and / or MR environment. For example, the XR processing module 785 can be used for 3D object manipulation, gesture recognition, facial recognition, and facial expression recognition, etc.

[0196] The memory 778 may also include data 788, which includes structured data. In some embodiments, the data 788 may include profile data 789, device data 790 (including device data of one or more devices coupled to the HIPD 700, such as device type, hardware, software, configuration, etc.), sensor data 791, media content data 792, and application data 793.

[0197] It should be understood that the computing system 740 of the HIPD is an example of a computing system within the HIPD 700, and that the HIPD 700 may have more or fewer components, combine two or more components, and / or have a different configuration and / or arrangement of components than those shown in the computing system 740 of the HIPD. The various components shown in the computing system 740 of the HIPD are implemented in hardware, software, firmware, or a combination thereof, including one or more signal processing and / or application specific integrated circuits.

[0198] The above FIG. 7A to FIG. 7BThe techniques described in the can be used with any device used as a human-machine interface controller. In some embodiments, the HIPD 700 can be used in conjunction with one or more wearable devices such as a head wearable device (e.g., XR device 600 and MR device 610) and / or a wrist wearable device 500 (or its components).

[0199] Any data collection performed by the devices described herein and / or any device configured to perform the various embodiments described above with reference to any of the diagrams or to cause the performance of these embodiments (hereinafter referred to as "devices") is performed with the user's consent in a manner that complies with all applicable privacy regulations. The user can choose to allow the device to collect data, or can choose to limit or deny the device from collecting data. The user can opt in or out of any data collection at any time. In addition, the user can choose to request deletion of any collected data.

[0200] It will be understood that although the terms “first”, “second”, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element.

[0201] The terms used herein are only used to describe specific embodiments and are not intended to limit the claims. As used in the description of the embodiments and the appended claims, the singular forms "a", "an" and "the" are also intended to include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and includes any and all possible combinations of one or more items in the associated listed items. It will also be understood that the terms "include" and / or "comprising" when used in this specification specify the presence of stated features, integers, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or combinations thereof.

[0202] As used herein, the term "if" may be interpreted to mean "when" or "upon" or "in response to determining" or "upon determining" or "in response to detecting" the stated antecedent is true, depending on the context. Similarly, the phrase "if it is determined that [the stated antecedent is true]" or "if [the stated antecedent is true]" or "when [the stated antecedent is true]" may be interpreted to mean "upon determining" or "in response to determining" or "upon determining" or "upon detecting" or "in response to detecting" the stated antecedent is true, depending on the context.

[0203] For the purpose of illustration, the foregoing description has been described with reference to specific embodiments. However, the illustrative discussion above is not intended to be exhaustive or to limit the claims to the precise forms disclosed. In view of the above teachings, many modifications and variations are possible. The embodiments are chosen and described in order to best explain the principles of operation and practical application, thereby enabling others skilled in the art to realize.

Claims

1. A head wearable device, comprising: lens system, and A facial interface, the facial interface comprising: a portion configured to be coupled to the lens system via an adjustment assembly, and a facial interface portion configured to contact the wearer's face, wherein: The adjustment assembly is configured to move the facial interface portion relative to the lens system to adjust a depth between a lens of the lens system and the wearer's face, including adjusting the depth to: (i) a first depth configured to accommodate a first facial profile associated with a first wearer, and (ii) a second depth configured to accommodate a second facial profile associated with a second wearer, wherein the first facial contour is different from the second facial contour; and button, the button being configured to: When the button is pressed, the button moves the facial interface portion relative to the lens system, and When the button is released, the button maintains the position of the facial interface portion relative to the lens system, Wherein, the button is located on the inner surface of the facial interface, wherein the inner surface of the facial interface is the surface facing the wearer when the wearer wears the head wearable device.

2. The head wearable device according to claim 1, wherein: The adjustment component is located on a first side of the facial interface, and the first side corresponds to a left side of the wearer's face, and the head wearable device further includes: A second adjustment component is positioned opposite the adjustment component such that the second adjustment component is located on a second side of the facial interface, and the second side corresponds to a right side of the wearer's face.

3. The head wearable device according to claim 1, wherein: The adjustment assembly also includes at least one actuator configured to move the facial interface portion relative to the lens system.

4. The head wearable device according to claim 1, wherein: The adjustment assembly further comprises two hooks and a tenon coupled to a spring, wherein: The tenon is configured to move between the two hooks when the spring is compressed to move the facial interface relative to the lens system, wherein: (i) when the tenon is located within a first of the two hooks, the tenon is associated with the first depth, and (ii) When the tenon is located in a second hook of the two hooks, the tenon located in the second hook is associated with the second depth.

5. The head wearable device according to claim 4, wherein: The tenon, the spring and the two hooks are configured so that when the head wearable device is worn, the tenon, the spring and the two hooks are not visible.

6. The head wearable device according to claim 4, wherein: The lens system and the facial interface are made of a first material, and the tenon, the spring and the two hooks are made of a second material.

7. The head wearable device according to claim 6, wherein: The first material is a metal material.

8. The head wearable device according to claim 6, wherein: The second material is a thermoplastic material.

9. The head wearable device according to claim 1, wherein: The depth between the lens of the lens system and the rear portion of the facial interface determines the eye relief between the lens system and the wearer's eye.

10. A facial interface comprising: a portion configured to be coupled to the lens system via an adjustment assembly, and a facial interface portion configured to contact the wearer's face, wherein: The adjustment assembly is configured to move the facial interface portion relative to the lens system to change the depth between the lens of the lens system and the wearer's face, including adjusting the depth to: (i) a first depth configured to accommodate a first facial profile associated with a first wearer, and (ii) a second depth configured to accommodate a second facial profile associated with a second wearer, wherein the first facial contour is different from the second facial contour; and button, the button being configured to: When the button is pressed, the button moves the facial interface portion relative to the lens system, and When the button is released, the button maintains the position of the facial interface portion relative to the lens system, Wherein, the button is located on the inner surface of the facial interface, wherein the inner surface of the facial interface is the surface facing the wearer when the wearer wears the head wearable device.

11. A method for adjusting eye relief for a facial interface, the method comprising: At a head wearable device including a facial interface portion configured to contact a wearer's face and a lens system configured to move relative to the facial interface via an adjustment assembly: moving the facial interface portion of the head wearable device relative to the lens system of the head wearable device to a first depth via the adjustment assembly, wherein the first depth is configured to accommodate a first facial profile associated with a first wearer; and and moving the facial interface portion of the head wearable device relative to the lens system of the head wearable device to a second depth via the adjustment assembly, wherein the second depth is configured to accommodate a second facial profile associated with a second wearer, wherein: The first facial profile is different from the second facial profile, and The buttons are configured as: When the button is pressed, the button moves the facial interface portion relative to the lens system, and When the button is released, the button maintains the position of the facial interface portion relative to the lens system, Wherein, the button is located on the inner surface of the facial interface, wherein the inner surface of the facial interface is the surface facing the wearer when the wearer wears the head wearable device.

12. The method according to claim 11, wherein: The adjustment component is located on a first side of the facial interface, and the first side corresponds to a left side of the wearer's face, and wherein the head wearable device further comprises: A second adjustment component is positioned opposite the adjustment component such that the second adjustment component is located on a second side of the facial interface, and the second side corresponds to a right side of the wearer's face.

13. The method according to claim 11, wherein: The adjustment assembly also includes at least one actuator configured to move the facial interface portion relative to the lens system.

14. The method according to claim 11, wherein: The adjustment assembly further comprises two hooks and a tenon coupled to a spring, wherein: The tenon is configured to move between the two hooks when the spring is compressed to move the facial interface relative to the lens system, wherein: (i) when the tenon is located within a first of the two hooks, the tenon is associated with the first depth, and (ii) When the tenon is located in a second hook of the two hooks, the tenon located in the second hook is associated with the second depth.

15. The method according to claim 14, wherein: The tenon, the spring and the two hooks are configured so that when the head wearable device is worn, the tenon, the spring and the two hooks are not visible.

16. The method according to claim 14, wherein: The lens system and the facial interface are made of a first material, and the tenon, the spring and the two hooks are made of a second material.

17. The method according to claim 16, wherein: The first material is a metal material.

18. The method according to claim 16, wherein: The second material is a thermoplastic material.

Images